- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
I solved the the 'MAIL FROM record is not aligned' error by changing the SPF and DKIM alignments in the DMARC record from strict (s) to relaxed (r), i.e. changed adkim=s;aspf=s to adkim=r;aspf=r.
I've just started using SES's Virtual Delivery Manager and I'm getting the 'MAIL FROM record is not aligned' error, which is effectively the same problem. Every email contains two 'from' addresses, 'envelope from' and 'header from.'
The 'header from' field usually contains the email address displayed to the recipient as the expected 'reply to' address.
The 'envelope from' field, often referred to as the 'MAIL FROM,' is a return path, which is the return address hidden in the email message header that instructs mail servers or inbox service providers (ISPs) where to return messages if they bounce. This address is used for email delivery.
In Amazon SES, emails typically come from <mail_id>@<region>.amazonses.com.
Once you've configured a 'Custom MAIL FROM domain' then the email will come from <mail_id>@<custom_mail_from_domain>.
Neither of the domains used in either of these configurations are the same as the 'header from' field domain. This means that I don't think I'll ever be able to resolve the 'MAIL FROM record is not aligned' error.
If you check your email using https://mxtoolbox.com/deliverability/, you should see that there are no issues if everything is configured correctly.
Bear in mind that each email provider uses different spam detection algorithms, so results will vary depending on which service you are sending emails too. Email is delivery isn't a yes/no, true/false game, it varies.
With SPF alignment for DMARC, the 'envelope from/MAIL FROM' field is used not the 'header from,' and with DMARC either SPF or DKIM needs to align for an email to pass the DMARC check.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Thanks for posting the progress. That sounds more like a workaround than a fix though. At least I don't see why it would require a relaxed setting. Do you know more by now?