1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
You'll need to setup a specific TXT record that allows amazonses.com to send emails on behalf of your custom domain. If you have already followed the instruction here to add the custom record, then you'll need to give some time for DNS records to propagate so that SES can see the updated records.
This process usually take a few minutes, but it may take up to 72 hours. Once the domain setup is verified, you'll receive an email from SES informing you that the domain is setup correctly.
beantwortet vor 10 Monaten
I did all those, received the emails saying that everything is correct. Yet, the advisor still says that.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 2 Jahren
I also have this issue. All my MAIL FROM set up is showing as verified and I have confirmed that the correct SPF records exist, but still Advisor reports "SPF record for Amazon SES was not found" for some of my domains (but not all). Any ideas how to resolve this?
Have the same issue. Anyone found a solution. Tested with https://www.kitterman.com/spf/validate.html and TXT record was found and formatting verified. Anyone ?
Same issue here. Mxtoolbox https://mxtoolbox.com/SuperTool.aspx sees the SPF record plain as day.
@Zsolt @Gavin @Jens did this get resolved for you? Hoping this is a DNS propagation issue as described by the docs and @Burhan... but I doubt it because it's been 2+ days and prior DNS changes with my host go through in 24 hrs... plus obviously Mxtoolbox is seeing the SPF record.