3 Answers
- Newest
- Most votes
- Most comments
0
That's default behaviour for Amazon SES, but you can override it. It's explained in detail in this documentation article: https://docs.aws.amazon.com/ses/latest/dg/mail-from.html
0
I already read this article but it imply to have a MX record created which will not be allowed by some of my client because they already have their. Is there an alternative? If I am taking the example of sendgrid they use a CNAME record to handle the envelop domain. When we need to authorize a sender domain, the client have to create :
- One CNAME for the envelop domain
- 2 CNAME for the DKIM
- Add the IP in the SPF record thanks,
answered 2 years ago
0
SPF verifies the Envelope domain and DKIM is applied to the authored message via a digital signature
Relevant content
- asked 7 years ago
- asked 4 years ago
- asked 4 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 8 months ago
