←back to thread

Understanding SPF, DKIM, and DMARC: A Simple Guide

(github.com)
443 points miles | 2 comments | 17 Jun 24 17:35 UTC | HN request time: 0.41s | source
Show context
detourdog ◴[17 Jun 24 21:20 UTC] No.40711202[source]▶
When I first implemented the above the next step was going to be ARC.

Does anyone have thoughts on ARC?

https://www.validity.com/blog/how-to-explain-authenticated-r...

replies(1): >>40711295 #
jabroni_salad ◴[17 Jun 24 21:30 UTC] No.40711295[source]▶
It's only really needed if you need to robo-forward stuff between domains. For example if you set up a domain but want to receive emails to your usual gmail.

I noticed that cloudflare's email forwarder uses an ARC record and it works a treat.

replies(2): >>40711377 #>>40716866 #
1. lxgr ◴[17 Jun 24 21:40 UTC] No.40711377[source]▶
I recently noticed this when debugging email delivery issues for a family member who have their own TLD, but forward everything to Gmail.

Unfortunately, the mail server of the forwarding domain doesn't seem to support ARC, so Gmail frequently throws away everything that doesn't have a DMARC header, since without DMARC the only other option is SPF, which doesn't work for forwarding.

replies(1): >>40711585 #
2. jabroni_salad ◴[17 Jun 24 22:00 UTC] No.40711585[source]▶
A lot of small businesses in my area have been bit by that this year. I have to give hostgator/bluehost/godaddy etc kudos for having an email forwarder work reliably for so long but I wish they were more proactive about getting their customers compliant with this.

Also it's kinda messed up how much of the small business sector is relying on AOL webmail to operate.