Une toolbox intéressante et très utile par les temps qui courent autour des BIMI, DMARC, DKIM, TXT, etc.

Lien de la source ==> https://lnkd.in/emCnGryq

#cybersecurity #toolbox #infosec #blueteam #bimi #dkim #dmarc

When I set up #SPF years ago, I was happy that it blocked so much #spam. Then I moved to requiring matching reverse DNS records (which I still have mixed feelings about) and that blocked all that spam and more.

After several days of having #DKIM and #DMARC verifiers, I observed only one piece of spam being blocked by these (with SPF also failing), while all professional spammers have valid DKIM signatures.

Maybe I should write more #email so I experience my messages being blocked or not.

Today: ripping out my old #DKIM and #DMARC processors, OpenDKIM / OpenDMARC, in favor of #rspamd. I can even drop Postgrey and parts of Postscreen.

Oh it's a pain to set up (you kinda have to wrap your head around hey they do configuration includes to separate site config from package config), but the all-in-one approach *with a web interface* for easy viewing is... Yeah I'm migrating.

Plus it also supports ARC, and seems to be faster at scanning than SpamAssassin.

#Postfix is happy. #email

You've done the right thing by your organization and made sure that #DMARC and #SPF (sender policy framework) records are set in an effort to reduce email spoofing, but all that good work could be undone if the SPF is too permissive in the stated IP range.

Such a situation was pointed out by Can I Phish CEO Sebastian Salla who scanned 1.8 million Australian domain records in search of #email #security snafus.

To read the complete article see:

https://www.zdnet.com/article/check-your-spf-records-wide-ip-ranges-undo-email-security-and-make-for-tasty-phishes/