Steps to Improve Email Delivery
About
Email delivery is becoming increasingly complicated, so its important to take steps to ensure your email client is properly configured so that valid emails are deliverable.
Bounce notifications
UltraCart utilizes Amazon SES for our transactional email delivery.
The following bounce reasons may affect delivery to your email address:
BounceType | Bounce SubType | Description | Special Notes |
|---|---|---|---|
|
| The recipient's email provider sent a hard bounce message, but didn't specify the reason for the hard bounce. | Important! When UltraCart receives this type of bounce notification, we will immediately mark the recipient's email address as undeliverable. |
|
| The recipient's email address is on the Amazon SES suppression list because it has a recent history of producing hard bounces. For information about removing an address from the Amazon SES suppression list, see Using the Amazon SES global suppression list. |
|
|
| The recipient's email provider sent a general bounce message. You might be able to send a message to the same recipient in the future if the issue that caused the message to bounce is resolved.
| Note If you send an email to a recipient who has an active automatic response rule (such as an "out of the office" message), you might receive this type of notification. Even though the response has a notification type of |
|
| The recipient's email provider sent a bounce message because the recipient's inbox was full. You might be able to send to the same recipient in the future when the mailbox is no longer full. |
|
|
| The recipient's email provider sent a bounce message because the message you sent contains content that the provider doesn't allow. You might be able to send a message to the same recipient if you change the content of the message. |
|
|
| The recipient's email provider sent a bounce message because the message contained an unacceptable attachment. For example, some email providers may reject messages with attachments of a certain file type, or messages with very large attachments. You might be able to send a message to the same recipient if you remove or change the content of the attachment. |
|
Steps to improve email delivery
The following are steps that you can take to improve the deliverability of the UltraCart email notifications to your email address/client.
Add UltraCart addresses to your email client contacts list
Please make sure that you have added our email addresses to your email clients contact list:
Whitelist the Ultracart Public IP addresses:
For more details on whitelisting IP addresses in Gmail, see:
https://www.maketecheasier.com/blacklist-whitelist-ip-addresses-gmail/
Set up DKIM to prevent email spoofing
Please review the following knowledgebase article form Google regarding the generation and configuration of your own DKIM key:
https://support.google.com/a/answer/174124?hl=en
Steps to set up DKIM
Generate the domain key for your domain at the URL above.
Add the public key to your domain's DNS records. Email servers can use this key to verify your messages' DKIM signatures.
Turn on DKIM signing to start adding a DKIM signature to all outgoing messages.
Setup SPF record verification
Sender Policy Framework (SPF) is an email authentication method that specifies the mail servers authorized to send email for your domain. SPF helps protect your domain from spoofing, and helps ensure that your messages are delivered correctly. Mail servers that get mail from your domain use SPF to verify that messages that appear to come from your domain actually are from your domain.
For more details see: https://support.google.com/a/answer/33786
SPF help prevents spoofing—Spammers can forge your domain or organization to send fake messages that appear to come from your organization. This is called spoofing. Spoofed messages can be used for malicious purposes, for example to communicate false information, to send out harmful software, or to trick people into giving out sensitive information. SPF helps receiving servers verify that mail sent from your domain is actually from your organization, and is sent by a mail server authorized by you.
SPF helps deliver messages to recipients’ inboxes—SPF helps prevent messages from your domain from being delivered to spam. If your domain doesn’t use SPF, receiving mail servers can’t verify that messages appearing to be from your domain actually are from you. Receiving servers might send valid messages to recipients' spam folders, or might reject valid messages.
Step 1: Create your TXT record for SPF
A TXT record for SPF defines the mail servers that are allowed to send mail for your domain.
A single domain can have only one TXT record for SPF. However, the TXT record for a domain can specify multiple servers and domains that are allowed to send mail for the domain.
TXT record contents
If all email from your organization is sent from G Suite, use this line of text for your TXT record:
v=spf1 include:_spf.google.com ~all
If you send mail in one or more of these ways in addition to G Suite, you must create a custom TXT record for SPF:
You send mail from other servers.
You use a third-party mail provider.
Your website uses a service that generates automatic emails, for example you have a "Contact us" form.
Create your TXT record using the information in Server information for your TXT record and TXT record format.
About settings that are managed by your domain host: https://support.google.com/a/answer/35232
Related Documentation:
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/notification-contents.html#bounce-types