The Two Types of DynECT Email Delivery Clients

11.04.2011 By

Home » Blog Home » Email » The Two Types of DynECT Email Delivery Clients

We’ve been asked by many current DynECT Managed DNS clients and partners to define the ideal customer for our booming new service known as DynECT Email Delivery. We support both transactional (automated application triggered) and bulk senders (we power ESPs, large marketing senders) of all sizes and budgets. Not unlike DNS, we charge based on volumes and have premium, affordable and scalable options for every type of sender.

Before I dive in and fully define these customer types, let me expound on our strategy behind moving into this new and exciting space.

One question that is extremely important for a business offering a new service to their enterprise client base to answer: “Is it the same buyer?” When we decided to bring our Standard SMTP service (basic, self sign-up, low volume senders) up market to the enterprise (premium reporting and monitoring features, full API, throttling, ISP relations, high volume senders), we asked and answered that important question to ensure we were putting a complimentary product in front of our treasured core DNS clients.

Before we made this deliberate move, we asked our most loyal and trusted clients what they thought…and they loved the idea. Some contemporaries have bet on DDoS, some on CDN, a few on IPAM and others on web application monitoring. We’re betting hard on email delivery and inbox monitoring.

Email Delivery - Dyn

The two types of DynECT Email Delivery clients

Type A

The first type is the customer paying little-to-no attention to their email. They’ve most likely set up postfix on a server, have moved onto other technical challenges and have zero insight into email metrics.

They might not have the time, expertise, staff or interest in diving in and proactively and constantly evolving their outbound emall efforts. In no way are they prepared for scale but we are. They need Dyn.

Type B

The second type is the customer who is paying a great deal of attention to their email, but is struggling to establish consistent inbox placement, solid IP reputation and high sender scores. These are the clients who are investing great internal resources (people, hardware, staff) toward the avoidance of spamtraps and blacklists and are in the market for a focused expert to partner with. They aren’t quite focused enough. Scale might be killing them. This type needs Dyn too.

For both types of customers, email delivery success (aka email deliverability) is extremely important to the user experience associated with their brand and the overall bottom line of their business. Email is a powerful communication asset and getting messages through can mean the difference between engagement and disengagement — the latter of which is a customer service killer.

Do you fit either type? Not quite sure if DynECT Email Delivery would be a benefit for your biz? To learn more, existing clients can contact their Account Manager and new clients can hit us up at anytime, regardless of where your business is located around the world. Whether it’s the U.S., the UK, Australia, Germany or the tip of Antarctica, we want to improve your delivery rates.

Related Posts

Kyle York is the Chief Revenue Officer for Dyn, the IaaS (Internet Infrastructure-as-a-Service) leader in Managed DNS and Email Delivery services. Follow on Twitter: kyork20 and DynInc.

Enjoyed this post? Share It!

  • Spicedham

    I have the Dyn Standard SMTP service (and it works well), however, it is INCREDIBLY STUPID that the username and password to log into the SMTP server is is the same as the username and password that is used to log in to the users DYNDNS account, and apparently, it cannot be configured seperatly.

    Either the coders at DYNDNS are too srupid to realize that this is a huge security issue, or DYNDNS simply does not care about the security of their customer’s account data:

    1) This SMTP username and password can (and usually is) sent to the server via plain text.

    2) If used from a script on a shared server or service, the script will contain the username and password to the users DYNDNS account (and not just the smtp logon and password).

    Of course, that is all the information someone needs to hijack the user’s DYNDNS account, retrieve sensitive account information, or even have a hayday by ordering additional services and running up someone’s credit card bill.

    In these days, this kind of setup is just plain idiot-icy, and the people who
    designed and approved it should be sent packing.

    In short, its a great service with a hugely poor security model.

    All that is needed is the requirement for someone to setup a username/password
    to be used on the SMTP server that is separate form the username/password
    used to access the main DYNDNS account.

    Joe

    • http://twitter.com/kyork20 Kyle York

      Thanks for the candid note. We love passion. I saw your email go into our support team, so the team will respond there. Take care, Joe.