Welcome to Dyn’s Email Delivery Getting Started Guide!
To login to Email Delivery, you will need to create a DynID, if you don’t already have one. You should also consider adding 2-factor authentication for added security.
Overview of Email Delivery Basic Setup
|1. Create one or more Approved Senders. These are the email addresses that will appear in the ‘From’ line of the email.|
|2. Set your DNS manager to include DKIM and SPF authorization credentials for your Authorized Sender account(s).|
|3. Setup (and test) your SMTP connection to send Email from your system through Email Delivery.|| Postfix and SendMail are two popular SMTP products.
|4. Send email!||NOTE: If an SMTP connection to Dyn’s email servers is idle or paused for more than 10 seconds (no emails being sent), the connection will be closed. A new connection to Dyn’s servers will need to be established to continue sending.|
|5. Analyze reports to get a view of sent email, bounces, spam complaints, and opens.|
Important Things to Note
Each email you wish to send through Email Delivery requires the same credentials you already have set up in the Control Panel.
We optimize our incoming mail servers for delivery speed based on message size. For a total message size including headers, attachments and embedded images less than 1MB use
smtp.dynect.net. For a total message size greater than 1MB use
smtp-large.dynect.net. The total maximum message size that can be sent is 10MB. We support TLS on port 25 or 587. Specify your Email Delivery account username and password, in plain text.
NOTE: Messages will be refused if sent to smtp.dynect.net and total message size is greater than 1MB.
Lastly, if you have any user-defined variables you wish to include with your emails, specify them as custom headers in email. Email Delivery provides four user-defined variables to allow the sending of data. Email Delivery, upon receiving each email, parses the originator, the recipient, the subject, content and other email headers, and submits the message to the appropriate queue for delivery. When extracting the message body, we look for both “plain” messages and multipart (MIME) email.
The only reason a message would not be submitted to the queue for sending, is if the recipient is on the suppression list, meaning they had previously hard-bounced or had submitted a spam complaint against the same sender email address.
Identifying Parts of the Interface
These two pages outline all of the interface objects and views.
|Email Dashboard||The Dashboard is the first view listed on the far left of the menu bar.|
|Email Delivery Control Panel||The black menu bar at the top of each view. Used to navigate around the Email Delivery product.|
What do you want to know?
Each of these topics relates to a specific view in the Email Delivery portal. Select a topic to see more information about the page and its content.
|Add or review approved senders, email addresses allowed to send emails through your email delivery account.|
|View and understand the various data fields on each report.|
|The Integration view covers (1) Email API Key Generation, (2) Postback URLs, and (3) Custom X-Headers.|
|Where the Master account can review the sub-accounts on your email delivery account.|
|Add sub-accounts to increase flexibility and security on your email delivery account.|
|Review your email reputation based on your last 30 days of activity.|
|Determine which accounts share an IP address and which accounts have a dedicated IP address.|
|Maintain your sending reputation by reviewing the list of suppressed email addresses.|