Change can be scary, especially when it comes to Internet Infrastructure. Even when switching would be a better solution in every possible aspect, being comfortable and taking the path of less resistance is an easy way out. We’ve all done this, both at work and in our personal lives. How many times have you thought about trying a different service but stopped because of the path to get to your final destination?
We get it and when it comes to DNS & Email Delivery, we often hear the question, “How easy is it to move to Dyn?” That’s why Chris Gonyea and I are going to bring you separate posts on how it’s easy as Boston Cream Pie to move to DynECT Managed DNS and Email Delivery services.
We begin with DynECT Email Delivery and with these five steps, you’ll be sending and experiencing improved deliverability before you know it.
How do I choose a sending protocol?
DynECT Email Delivery offers various methods of integration for sending mail. The easiest for most already sending mail either internally or through another ESP is through our SMTP servers. All you need to do is to update SMTP relay host address to smtp.dynect.com and add your DynECT username and password.
You can also use our sending API if you don’t have / choose not to send through an outgoing SMTP server. The use of the send API makes it easier than ever to integrate transactional email into your website while maintaining bulk marketing emails through a separate system. We have a step-by-step guide for both of these methods in our help and support documentation to make integration a breeze.
How can I determine a metrics strategy?
DynECT accounts can be customized in order to separate metrics into logical segments for your business operations. Determine how you would like to segment your email sending and create sub-accounts and approved senders to match this strategy. This can always be changed later once you get going, but it’s good to have a game plan going in. A simple strategy that works for most might be:
- Sub Account – Marketing Emails
- Sender – email@example.com
- Sub Account – Business Operations
- Sender – firstname.lastname@example.org
- Sender – email@example.com
Check out this recent post on getting the most out of email metrics for some ideas.
How do I integrate for future list management?
DynECT Email Delivery has integration options that enable the sender to integrate their business information systems with their DynECT Email Delivery accounts.
- Postback URLs — When activated, any time an email is bounced or spam complaint is received, these URLs are activated to execute any custom script on your servers you would like. We’re still waiting for someone to integrate a Spam Complaint to a USB rocket launcher, so please let us know!
- Custom X-Headers — After established in your DynECT Email Delivery account, you can add customized x-headers to your email messages in order to better track data in opens, clicks, complaints and more! This data can help with better list segmentation and customizing email content for your end recipients.
Beyond these integration methods, all the information in the portal including email sent, delivered, bounced, complaints, opens and clicks are available through the REST API. This will enable you to integrate all data available into your current infrastructure with ease.
How do I setup authentication?
There are two types of authentication that are available and suggested for use with DynECT Email Delivery: SPF and DomainKeys. An interesting thing to note here is that we suggest utilizing DomainKeys, not to be misunderstood as DKIM (DomainKeys Identified Mail). There actually is a difference, but it’s one less thing you’ll have to worry about now once you become a DynECT Email Delivery client.
- SPF — This is a method of eliminating forged mail. ISPs check this to make sure the Dyn IP addresses sending your mail are authorized to send mail on behalf of your domain. To establish an SPF record, there is an SPF wizard that will show you the record which needs to be added to your domain’s DNS (Domain Name System) setup.
- Domain Key — Use of the domain key authentication validates the message back to the domain through the use of comparing encrypted public and private keys. To establish the domain key, there is a domain key wizard that will show you the record which needs to be added to your domain’s DNS setup.
Depending on your DNS setup, you may need to wait some time for your modified DNS records to propagate before sending.
Verify and get sending!
Now that you’ve followed these setup instructions and waited for your DNS records to propagate, you’re ready to send some test emails and verify your metrics. Send an email, to an email account which you have access, to ensure you have the proper account setup, approved sender and authentication setup. If there’s an issue with your message, it will appear in your DynECT account under the issues report.
Be sure to test an open and click (if you have this enabled) and if you see any issues, be sure to check your open and closing HTML and BODY tags of your email. We also have postback test options within the DynECT account to test bounces and complaints without having to truly bounce or mark your own email as spam. Be sure to try these as well! After verifying, you’re set to begin sending!