1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
I suspect the cause is that during configuration, you may have added an MX record that points to amazonses.com .
More specifically, when doing domain verification and configuration, if you do not choose a custom subdomain for SES email, your current domain is provided as the MX record like:
MX domain.com 10 configname-smtp.region.amazonses.com
But if you set a custom FROM domain, like "appemail.domain.com", you can then remove the plain MX record from above that's killing your email, and use the one with the subdomain instead (which would look like):
MX appemail.domain.com 10 configname-smtp.region.amazonses.com
répondu il y a 2 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 8 mois
- demandé il y a 3 ans
- AWS OFFICIELA mis à jour il y a 7 mois
- AWS OFFICIELA mis à jour il y a 7 mois
