Hello!
I'm experiencing an issue I cannot understand - I have a persistent HIGH importance DMARC configuration warning for my WorkMail domain (h......awsapps.com) that I cannot resolve.
Details:
- I have successfully configured DMARC, SPF, and DKIM for my primary domain (h......ai)
- All emails sent from both Amazon SES and WorkMail are now properly authenticating with my custom MAIL FROM domain (mail.h.....ai)
- Email headers confirm that authentication is passing for SPF, DKIM, and DMARC
- Despite this, I continue to see a HIGH importance warning in the SES console about DMARC configuration issues for h......awsapps.com
My understanding is that the h.......awsapps.com domain is automatically created and managed by WorkMail, and I cannot remove it. Since I'm only sending emails from my primary domain, this warning seems unnecessary but cannot be dismissed.
Questions:
- Is there a way to properly configure DMARC for the WorkMail domain without interfering with existing WorkMail functionality? Because AWS recommend only one custom mail record domain....
- If the domain is working as intended, is there a way to suppress this warning?
- Is this a known issue with WorkMail domains showing DMARC warnings even when not actively used for sending emails?
I guess I can just ignore it, but it's annoying and seems silly of AWS to show it, if it's not relevant or cannot be fixed.
Thank you for any help/advice.
Gareth.
amazing - thanks Robin. It just led me on a bit of a wild goose chase for a bit. And yes, I assumed I could just ignore once I had tested my config. Thanks again, Gareth