3 ms·
DMARC isn't for sending email successfully, it's for preventing other people from impersonating your domain. Without it, there's nothing stopping anybody from s
by brightball 3mo ago
DMARC isn't for sending email successfully, it's for preventing other people from impersonating your domain. Without it, there's nothing stopping anybody from sending an email saying it is from you@qurren.com. SPF tried. DKIM tried. Both of them had gaps.
When you use them together and have a DMARC policy that requires one of them or the other for successful delivery, it's the best current solution.
- qurren 3mo agoExcept I think I've had 1:1 personal e-mails from my domain go into a legitimate recipient's spam filter just because I didn't have DMARC set up and their mail server was flagging that "DMARC not set up == spammy domain"
- drdexebtjl 3mo agoThat is perfectly reasonable. Set it up correctly.
- bombcar 3mo agoIt is so much easier to set these things up with a frontier AI to walk you through the Byzantine steps.
- denkmoon 3mo agoIt takes an afternoon to set up DKIM and DMARC from scratch on a debian VPS. Yeah it's a little bit byzantine but it's not rocket science.
- qurren 3mo agoYeah I did that. Now it seems I have to set up DKIM2 and DMARC2 and DCRAP3 and DSHIT4 for another afternoon instead of just going to work and getting shit done.
- denkmoon 3mo agoGood heavens an entire other afternoon after a decadal standards update. You’ll have to spend an afternoon upgrading off XP at some point too.
- bombcar 3mo agoToo many admins just had it set to “no valid DMARC? Spam” instead of the more proper “failed DMARC? spam”. Which is subtly different.
- TZubiri 3mo agoRight, and when you don't configure DMARC successfully and the recipient requires DMARC, then you cannot send email successfully.