- Newest
- Most votes
- Most comments
The FROM MAIL is a header that is added to the SMTP envelope, and the reverse DNS is related to the actual IP that is used to send your e-mail. The reason you need a valid reverse DNS is sometimes receiving mail servers will not accept SMTP e-mail from a sender that does not have a reverse DNS record. This is independent from the actual domain that is sending - as many domains can send email over the same IP address.
This is where e-mail authentication comes in - which is what Google require:
An SPF record is used to tell a receiver of your message which mail servers (IP Addresses) are allowed to send e-mail on your behalf. It is therefore important that you create an SPF record for SES in your sending domains DNS. AWS document how to do this for a custom mail-from address here: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-spf.html
Furthermore Google expects you to use DKIM to sign your messages. You can configure DKIM with SES by following the documentation here: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dkim.html
And lastly Google expect that you have a DMARC policy published telling recipients how to handle your email. Effectively this is a way to say that if an email is received from you, that is not either from an IP address that has been validated by an SPF record, or that has a valid DKIM signature may not be from you.
You can learn how to configure a DMARC policy for your SES here: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-dmarc.html
It is important to setup these carefully - if you want to ensure maximum delivery of your messages. Even then you will still receive SPAM complaints and bounces. To prevent these impacting your reputation with Google, I recommend that you always turn on the account wide suppression lists as documented here: https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html
You should also consider handling complaints and bounces to maintain the integrity of your sending reputation - using techniques discussed in this blog: https://aws.amazon.com/blogs/messaging-and-targeting/handling-bounces-and-complaints/
In addition to that, Please refer to below blogpost with regards to Bulk Sender Changes at Yahoo/Gmail. Blog clarifies any areas of confusion on this change and provides you with the information you need to be prepared for February 2024 from SES end.
An Overview of Bulk Sender Changes at Yahoo/Gmail
Relevant content
AWS OFFICIALUpdated 9 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago
But isn't reverse DNS what Google is announcing that they will require for senders above 5000 email pr day? "Important: The sending IP address must match the IP address of the hostname specified in the Pointer (PTR) record." Does aws ses have reverse DNS build in for verified domains or does the domain holder/owner need to add additional records in order to adhere to the reverse DNS requirement?