I've Got Mail https://bonesmoses.org/2025/ive-got-mail/
I've Got Mail https://bonesmoses.org/2025/ive-got-mail/
oh my g-d i can't believe i broke my #DMARC records for some domains. how embarrassing.
Has anyone here on #fedi figured out the correct recipe for dealing with #OpenPGP, #DMARC and #mailman ?
The problem, by default mailman will modify messages and this will break the dkim signature.
https://gitlab.com/mailman/mailman/-/issues/1079
Mailman provides two DMARC mitigation options (other option is reject or discard which is not useful in this case).
1. Replace the from address with list address
2. Wrap original message in an envelope
thunderbird flags 1 and fails 2.
#askfedi #gnupg #gpg #thunderbird
Okay, obviously even #Cloudflare isn't able to interpret #DMARC policies and sends out bounce mails if someone hijacks your domain to send spam/malware.
Hey everyone! Big news: the PCI DSS 4.0 deadline is coming up fast! This time, DMARC is becoming mandatory for *anyone* handling credit card data. I know, it sounds like a pain, but trust me, it's *super* important. Phishing is still a massive threat, unfortunately.
So, what's the deal with DMARC? Think of it as a bouncer for your inbox. It helps block those sneaky, fake emails. Seriously, without DMARC, your company's basically an open invitation for cybercriminals.
A lot of folks are probably thinking, "Nah, doesn't apply to me." Nope! Even small businesses *have* to implement DMARC. It's a must-do!
Now, I'm curious: Do you guys already have DMARC set up? And if you do, what tools are you using? Let's share some insights!
Le courrier électronique est une cible privilégiée pour le spam, le phishing et autres formes d'escroqueries.
Découvrez DKIM, DMARC et SPF, trois techniques d’authentification de l’émetteur qui s’inscrivent dans la boîte à outils des organisations qui cherchent à lutter durablement contre ces abus.
Prochaines sessions : 27 et 28 mars 2025
22 et 23 mai 2025
Découvrez le programme complet et inscrivez-vous ici : https://www.afnic.fr/produits-services/formations/dkim-dmarc-spf-securiser-son-courrier-electronique-grace-au-dns/
now also available in English:
DMARC mail security protocol gets an update -- New tags added, old tags dropped, and a new alignment and discovery algorithm introduced
https://www.sidn.nl/en/news-and-blogs/dmarc-mail-security-protocol-gets-an-update
The main differences between the updated protocol and the current version are the inclusion of three new tags, the withdrawal of three existing tags, and replacement of the algorithm used for DMARC policy discovery and alignment by a new algorithm.
op SIDN.nl:
DMARC-beveiligingsprotocol voor mail krijgt een update -- Nieuwe tags erin, oude tags eruit en een nieuw alignment-zoekalgoritme
https://www.sidn.nl/nieuws-en-blogs/dmarc-beveiligingsprotocol-voor-mail-krijgt-een-update
De belangrijkste wijzigingen betreffen de introductie van drie nieuwe tags, de uitfasering van drie bestaande tags, en de vervanging van het zoekalgoritme voor de DMARC-policy en alignment door een nieuw algoritme.
𝐇𝐨𝐰 𝐭𝐨 𝐬𝐞𝐜𝐮𝐫𝐞 𝐲𝐨𝐮𝐫 𝐞𝐦𝐚𝐢𝐥 𝐰𝐢𝐭𝐡 𝐒𝐏𝐅, 𝐃𝐊𝐈𝐌 𝐚𝐧𝐝 𝐃𝐌𝐀𝐑𝐂
Email is usually a critical part of corporate communication these days. Without a functional email, companies can lose orders and therefore money for example. Therefore, email security should be a very high priority. But equally, increasing email deliverability should be very important.
In today's video, we'll look at how to increase email security from the perspective of protecting your domain. In other words, so that an outsider can't impersonate you, send emails under your domain, and thereby damage your company's reputation or credibility by, for example, sending out spam or, heaven forbid, fake invoices for payment from your domain.
We'll also look at how to increase the deliverability of your messages. That is to say, so that regular emails leaving your domain are delivered to the recipient, and don't fall into spam or get completely thrown away by the recipient's mail server.
We'll focus on three basic options for email security and deliverability that every organization should have implemented.
Watch my YouTube video bellow
https://youtu.be/xtmDDl1rjOc
A year after Google & Yahoo started requiring #DMARC, the adoption rate of the email authentication specification has doubled; $& yet, 87% of domains remain unprotected.
https://www.darkreading.com/remote-workforce/google-dmarc-push-email-security-challenges
Rate of DMARC adoption doubles thanks to bulk sender requirements #CyberSecurity #DMARC #Email
https://betanews.com/2025/02/05/rate-of-dmarc-adoption-doubles-thanks-to-bulk-sender-requirements/
Email servers: Stalwart claims to replace the different programs (Postfix, Dovecot, SpamAssassin, OpenDKIM, etc) by one program.
"Installing is simple'" (curl | sudo bash…)
Bonus: there is an integrated analysis of #DMARC reports :-)
Learn and Test DMARC
https://www.learndmarc.com/
Or how email works explained by an example,
mail-tester.com: A free service to test if an email is likely to be marked as spam
https://www.mail-tester.com/
#filtering #testing #email #dmarc #spam #dkim #spf #+
Warum du für ungenutzte Domains SPF- und DMARC-Records setzen solltest!
https://www.kuketz-blog.de/warum-du-fuer-ungenutzte-domains-spf-und-dmarc-records-setzen-solltest/