Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

ftiersch's avatar

MAIL FROM domain on AWS SES

Hey,

I have a problem with AWS. I have setup a SES domain to send emails (which works flawlessly) but sometimes mails bounce because of spam. So a couple weeks ago I activated DKIM which also works great.

Now I'm trying to change the MAIL FROM domain and have setup a subdomain to use (mail.thedomain.com) and added the necessary MX and SPF records to the DNS but Amazon is not able to pick it up.

I tried a lookup with mxtoolbox.com and the values are shown there just the way it's supposed to be but the status in the AWS console doesn't change from "pending".

Any hints why this might be the case?

Cheers!

0 likes
7 replies
Sinnbeck's avatar

It could be caused by TTL. If amazon does not query the nameserver directly the old setting will be cached on their local nameservers. If that is the case, all you can do is wait

Btw. Mxtoolbox queries the nameserver directly and therefor does not have issues with TTL.

If that isn't the, feel free to post the domains. I will gladly take a look

ftiersch's avatar

Well, I changed the DNS setting also a couple weeks ago (same time as DKIM which was recognized in minutes) so I hope it's not that :D

Sure.

The TLD is baufragen.de and the FROM domain is mail.baufragen.de

Thanks!

Sinnbeck's avatar

That does indeed look correct. (as I don't have the dkim selector I cannot check that). And ttl is very low and I don't suppose you just changed it

What part is pending at the aws console? The whole domain or a specific part?

ftiersch's avatar

Only the MAIL FROM part. DKIM is verified and working. Also the emails are working but they are currently being sent from some AWS subdomain which is the default and I think that's triggering some Spam filters which is why I'd like to set the MAIL FROM domain.

I'm just not sure how to get around that problem :)

Sinnbeck's avatar
Sinnbeck
Best Answer
Level 102

I'm unsure of how Amazon does this, but perhaps they hit the wrong mx and somehow failed. Could you remove the extra mx record and "try again"?

ftiersch's avatar

You're a genius! Man... No idea why I haven't tried that before.

Please or to participate in this conversation.