logoalt Hacker News

klodolph • yesterday at 8:26 PM • 2 replies • view on HN

I set up DMARC on my personal domain so long ago I can't even remember when I did it. 10 years+?

I had kinda assumed that a lot of providers would start rejecting domains without DMARC support. I'm surprised it's happening this late.


Replies

teekert • yesterday at 8:40 PM

This was my second hackernews submit [0]! So, not even https in 2014 :)

When I ran that server, outlook.com was also the only one that would blackhole my email for no known reason. Support was unhelpful and also could not point to any reason. I've since given up, but for a short time it was glorious, email to family would not leave the lan and we could send attachments of arbitrary size.

[0] https://news.ycombinator.com/item?id=7708882

mike_hearn • yesterday at 8:52 PM

You adopted it the moment it was announced? Really?

Is there a risk some people on this thread are mixing up DKIM and DMARC?

DKIM = proving that an email was sent from a specific domain using cryptography. Good for spam fighting and deliverability.

DMARC = telling receivers how to handle mail that fails authentication.

DMARC is primarily useful for large, complex organizations where email admins may not be aware of everyone inside the org who is sending mail that advertises the domain in the From header, or organizations that might be targeted by impersonation attacks (e.g. phishing). Being able to tell recipients "yes we absolutely have our act together so feel free to reject or spamfolder unauthenticated email" is great for killing phishing campaigns, and being able to request reports is great for finding that one sales org that signed up for a guerrilla marketing SaaS that's impersonating them.

But for small personal domains the value isn't that high.