toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

341
active users

#spf

1 post1 participant0 posts today
DomCom<p>Appel à proposition de sessions</p><p>30ème Congrès préhistorique de France<br><a href="https://archaeo.social/tags/Clermont" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Clermont</span></a>-Ferrand - juin 2026</p><p>Espaces contraints, espaces subis ? Les territoires préhistoriques à l’épreuve du milieu physique </p><p><a href="https://www.prehistoire.org/offres/gestion/actus_515_46324-632/appel-a-proposition-de-sessions-cpf-2026-espaces-contraints-espaces-subis-les-territoires-prehistoriques-a-l-epreuve-du-milieu-physique.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">prehistoire.org/offres/gestion</span><span class="invisible">/actus_515_46324-632/appel-a-proposition-de-sessions-cpf-2026-espaces-contraints-espaces-subis-les-territoires-prehistoriques-a-l-epreuve-du-milieu-physique.html</span></a></p><p><a href="https://archaeo.social/tags/congr%C3%A8s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>congrès</span></a> <a href="https://archaeo.social/tags/pr%C3%A9histoire" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>préhistoire</span></a> <a href="https://archaeo.social/tags/arch%C3%A9ologie" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>archéologie</span></a> <a href="https://archaeo.social/tags/archaeology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>archaeology</span></a> <a href="https://archaeo.social/tags/CPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPF</span></a> <a href="https://archaeo.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a></p>
John Goerzen<p><span class="h-card" translate="no"><a href="https://mastodon.social/@jeremiah_" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jeremiah_</span></a></span> <span class="h-card" translate="no"><a href="https://social.sdf.org/@elb" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>elb</span></a></span> <a href="https://floss.social/tags/NNCPNET" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NNCPNET</span></a>, the new <a href="https://floss.social/tags/NNCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NNCP</span></a>-based email network, now has a bidirectional, opt-in, Internet <a href="https://floss.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> bridge! <a href="https://salsa.debian.org/jgoerzen/docker-nncpnet-mailnode/-/wikis/bridge/intro" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">salsa.debian.org/jgoerzen/dock</span><span class="invisible">er-nncpnet-mailnode/-/wikis/bridge/intro</span></a></p><p>This gates Internet email to/from NNCP. The bridge is off by default. It is a full participant in <a href="https://floss.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>, <a href="https://floss.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a>, <a href="https://floss.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>, and <a href="https://floss.social/tags/TLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLS</span></a> in both directions.</p><p>Yes, now you can get Internet email straight to your <a href="https://floss.social/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RaspberryPi</span></a> ! (And even without this, your Pis can email each other!)</p>
Erik van Straten<p><span class="h-card" translate="no"><a href="https://troet.cafe/@patrickbenkoetter" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>patrickbenkoetter</span></a></span> : SPF, DKIM und DMARC funktionieren nicht.</p><p>Impersonitation ist zu einfach und zu viel wird kaputt gemacht.</p><p><a href="https://infosec.exchange/tags/Impersonation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Impersonation</span></a> <a href="https://infosec.exchange/tags/Spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Spam</span></a> <a href="https://infosec.exchange/tags/SpamBox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SpamBox</span></a> <a href="https://infosec.exchange/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://infosec.exchange/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://infosec.exchange/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a></p>
Jan Schaumann<p>System Administration</p><p>Week 8, The Simple Mail Transfer Protocol, Part III</p><p>In this video, we look at ways to combat Spam. In the process, we learn about email headers, the Sender Policy Framework (<a href="https://mstdn.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>), DomainKeys Identified Mail (<a href="https://mstdn.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a>), and Domain-based Message Authentication, Reporting and Conformance (<a href="https://mstdn.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>). <a href="https://mstdn.social/tags/SMTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMTP</span></a> doesn't seem quite so simple any more...</p><p><a href="https://youtu.be/KwCmv3GHGfc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/KwCmv3GHGfc</span><span class="invisible"></span></a></p><p><a href="https://mstdn.social/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SysAdmin</span></a> <a href="https://mstdn.social/tags/SRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SRE</span></a> <a href="https://mstdn.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DevOps</span></a></p>
Marcos Dione<p>"The stats we collect for the <a href="https://en.osm.town/tags/SpamAssassin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SpamAssassin</span></a> project (mass-scan results from participating sites) have long shown that spammers are more consistent at making <a href="https://en.osm.town/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>, <a href="https://en.osm.town/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a>, and <a href="https://en.osm.town/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> correct than are legitimate senders. DMARC in particular has no discernible benefit for most senders, so it is a useless signal.</p><p>Rejecting mail based solely on authentication failures of those deeply flawed authentication methods does more harm than good."</p><p><a href="https://www.jwz.org/blog/2025/03/dmarc-and-spf/#comment-257743" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">jwz.org/blog/2025/03/dmarc-and</span><span class="invisible">-spf/#comment-257743</span></a></p><p>EDIT: h/t <span class="h-card" translate="no"><a href="https://toad.social/@grumpybozo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>grumpybozo</span></a></span></p><p><a href="https://en.osm.town/tags/mail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mail</span></a></p>
Erik van Straten<p><span class="h-card" translate="no"><a href="https://toad.social/@grumpybozo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>grumpybozo</span></a></span> : I definitely am not angry with you (I very much agree).</p><p>Unfortunately many admins treat security solutions like they're a religion.</p><p>Some time age there was a hefty debate on a Dutch "mostly admins" site (<a href="https://tweakers.net" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tweakers.net</span><span class="invisible"></span></a>, I'd have to look up the exact thread) about the "correct" sending and receiving MTA configurations. There was no agreement.</p><p>Microsoft even used to ignore SPF/DKIM/DMARC if the sender was in the "safe senders" list (which the user's address book defaults to). What could possibly go wrong (later MS corrected that).</p><p>The screenshot below is from part of <a href="https://www.security.nl/posting/766069/DMARC+bypass+%28Outlook+only%3F%29#posting767981" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">security.nl/posting/766069/DMA</span><span class="invisible">RC+bypass+%28Outlook+only%3F%29#posting767981</span></a> (I wrote that Sept. 14, 2022).</p><p>Edited 23:36 UTC to add: {<br><a href="https://arxiv.org/abs/2302.07287" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">arxiv.org/abs/2302.07287</span><span class="invisible"></span></a><br>Forward Pass: On the Security Implications of Email Forwarding Mechanism and Policy<br>Enze Liu, Gautam Akiwate, Mattijs Jonker, Ariana Mirian, Grant Ho, Geoffrey M. Voelker, Stefan Savage<br>}</p><p><a href="https://infosec.exchange/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://infosec.exchange/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://infosec.exchange/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://infosec.exchange/tags/Arc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Arc</span></a> <a href="https://infosec.exchange/tags/WhatEver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WhatEver</span></a></p>
Erik van Straten<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@deepthoughts10" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>deepthoughts10</span></a></span> wrote: "email authentication like DMARC/SPF does one thing: it prevents impersonation of a specific domain (assuming policies are configured for reject or quarantine.)"</p><p>It does not even do that on my iPhone.</p><p>P.S. SPF was invented to prevent Joe Jobs (<a href="https://en.wikipedia.org/wiki/Joe_job" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">en.wikipedia.org/wiki/Joe_job</span><span class="invisible"></span></a>). Marketing idiots (including Bill Gates) said that it would kill spam. It killed forwarding instead.</p><p><span class="h-card" translate="no"><a href="https://toad.social/@grumpybozo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>grumpybozo</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@jwz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jwz</span></a></span> </p><p><a href="https://infosec.exchange/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://infosec.exchange/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://infosec.exchange/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://infosec.exchange/tags/ARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARC</span></a> <a href="https://infosec.exchange/tags/WhatEver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WhatEver</span></a></p>
Needa<p>Moment de solitude où je constate enfin que ma configuration <a href="https://piaille.fr/tags/Exim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Exim</span></a> perso <a href="https://piaille.fr/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> contenait une typo alors que le reste (<a href="https://piaille.fr/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>/#DMARC) était ok et ce depuis la migration, soit quasi 2 ans 🤡 <br>N'oubliez pas de tester vos propres outils ! <br>Cf. <a href="https://www.bortzmeyer.org/repondeurs-courrier-test.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bortzmeyer.org/repondeurs-cour</span><span class="invisible">rier-test.html</span></a></p>
nan0<p>Does anyone has a contact to the Joint Research Centre (<a href="https://chaos.social/tags/JRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JRC</span></a>) [0] or My Email Communications Security Assessment (<a href="https://chaos.social/tags/MECSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MECSA</span></a>) [1] (both from the <a href="https://chaos.social/tags/EU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EU</span></a>)?</p><p>I find the tool great... if it would parse <a href="https://chaos.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>/#IPv6 correctly und actually check for <a href="https://chaos.social/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNSSEC</span></a>...</p><p>I've tried emailing them, but no response :/</p><p>Links:<br>[0]: <a href="https://joint-research-centre.ec.europa.eu/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">joint-research-centre.ec.europ</span><span class="invisible">a.eu/</span></a><br>[1]: <a href="https://mecsa.jrc.ec.europa.eu/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">mecsa.jrc.ec.europa.eu/</span><span class="invisible"></span></a></p>
kuijsten<p>I've released an SPF filter for OpenSMTPD: <a class="mention u-url" href="https://netsend.nl/opensmtpd-filter-spf/" rel="nofollow noopener noreferrer" target="_blank">https://netsend.nl/opensmtpd-filter-spf/</a></p> <p><a class="mention u-url" href="https://honk.netsend.nl/o/opensmtpd" rel="nofollow noopener noreferrer" target="_blank">#opensmtpd</a> <a class="mention u-url" href="https://honk.netsend.nl/o/milter" rel="nofollow noopener noreferrer" target="_blank">#milter</a> <a class="mention u-url" href="https://honk.netsend.nl/o/spf" rel="nofollow noopener noreferrer" target="_blank">#spf</a></p>
Yes, But ⁉️<p><a href="https://mstdn.social/tags/Scooter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Scooter</span></a> <a href="https://mstdn.social/tags/Scooters" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Scooters</span></a> <a href="https://mstdn.social/tags/HeadGear" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HeadGear</span></a> <a href="https://mstdn.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a></p><p><a href="https://mstdn.social/tags/YesBut" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>YesBut</span></a> <a href="https://mstdn.social/tags/Comic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Comic</span></a> <a href="https://mstdn.social/tags/Comics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Comics</span></a> <a href="https://mstdn.social/tags/Meme" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Meme</span></a> <a href="https://mstdn.social/tags/Memes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Memes</span></a></p>
Wulfy<p>I am <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosting</span></a> a new <a href="https://infosec.exchange/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> engine on a new domain.<br>In preparation for a personal <a href="https://infosec.exchange/tags/Googlemail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Googlemail</span></a> exodus.</p><p>But even though I have my <a href="https://infosec.exchange/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> and <a href="https://infosec.exchange/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> record proper<br><a href="https://infosec.exchange/tags/Gmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Gmail</span></a> reject the test emails.<br>Without any bounces either, it just black holes them.</p><p>So over this week, I have a small script that randomly email random emails to Gmail to "build reputation".<br>We will see how that goes.</p>
Lukas Beran<p>𝐇𝐨𝐰 𝐭𝐨 𝐬𝐞𝐜𝐮𝐫𝐞 𝐲𝐨𝐮𝐫 𝐞𝐦𝐚𝐢𝐥 𝐰𝐢𝐭𝐡 𝐒𝐏𝐅, 𝐃𝐊𝐈𝐌 𝐚𝐧𝐝 𝐃𝐌𝐀𝐑𝐂</p><p>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.</p><p>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.</p><p>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.</p><p>We'll focus on three basic options for email security and deliverability that every organization should have implemented.</p><p>📺 Watch my YouTube video bellow 👇 👇 <br><a href="https://youtu.be/xtmDDl1rjOc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/xtmDDl1rjOc</span><span class="invisible"></span></a></p><p><a href="https://infosec.exchange/tags/cswrld" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cswrld</span></a> <a href="https://infosec.exchange/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>authentication</span></a> <a href="https://infosec.exchange/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://infosec.exchange/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a> <a href="https://infosec.exchange/tags/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a> <a href="https://infosec.exchange/tags/exchangeonline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>exchangeonline</span></a> <a href="https://infosec.exchange/tags/office365" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>office365</span></a></p>
Stephen Bannasch (316 ppm)<p>Got SPF, DKIM, and DMARC working … took a bit longer than I wanted because the domain is hosted on a separate larger server I don’t have direct control over and dns is on cloudflare so iteration is slower. Email is now making it successfully though to gmail and proton and no longer identified as spam.</p><p>1/x</p><p><a href="https://ruby.social/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a> <a href="https://ruby.social/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://ruby.social/tags/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a></p>
Peter N. M. Hansteen<p>Is SPF Simply Too Hard For Application Developers?<br>The Sender Policy Framework (SPF) is unloved by some, because it conflicts with some long-established SMTP email use cases. But is it also just too hard to understand and to use correctly for application developers? <a href="https://nxdomain.no/~peter/is_spf_too_hard_for_appdevs.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nxdomain.no/~peter/is_spf_too_</span><span class="invisible">hard_for_appdevs.html</span></a><br>(2016 but still holds) <a href="https://mastodon.social/tags/smtp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>smtp</span></a> <a href="https://mastodon.social/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://mastodon.social/tags/mail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mail</span></a> <a href="https://mastodon.social/tags/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spam</span></a> <a href="https://mastodon.social/tags/antispam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>antispam</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/spamd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spamd</span></a></p>
circl<p>TR-92 - Unused Domain Names and the Risks of Missing DNS SPF Records</p><p>Many organizations maintain a broad portfolio of domain names, acquired for branding, strategic planning, or defensive purposes. However, a significant portion of these domains often remains unused or lacks proper DNS configurations...</p><p>Read more <a href="https://www.circl.lu/pub/tr-92/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">circl.lu/pub/tr-92/</span><span class="invisible"></span></a></p><p><a href="https://social.circl.lu/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a> <a href="https://social.circl.lu/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>infosec</span></a> <a href="https://social.circl.lu/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://social.circl.lu/tags/domain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>domain</span></a> <a href="https://social.circl.lu/tags/phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>phishing</span></a> <a href="https://social.circl.lu/tags/scam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>scam</span></a> <a href="https://social.circl.lu/tags/netsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>netsec</span></a></p>
Patrick Ben Koetter 🕺🏼<p>2025 frage ich Kunden nicht mehr ob sie <a href="https://troet.cafe/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>, <a href="https://troet.cafe/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> und <a href="https://troet.cafe/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> implementieren wollen, sondern wieso sie es noch nicht getan haben.</p>
LavX News<p>Unveiling Email Security: The Surprising Truth Behind Sending Emails Without Credentials</p><p>What if you could send emails without entering any credentials? A deep dive into the mechanics of email security reveals vulnerabilities that could allow anyone to spoof identities. Discover how SPF, ...</p><p><a href="https://news.lavx.hu/article/unveiling-email-security-the-surprising-truth-behind-sending-emails-without-credentials" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.lavx.hu/article/unveiling</span><span class="invisible">-email-security-the-surprising-truth-behind-sending-emails-without-credentials</span></a></p><p><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>news</span></a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tech</span></a> <a href="https://mastodon.cloud/tags/EmailSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EmailSecurity</span></a> <a href="https://mastodon.cloud/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://mastodon.cloud/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a></p>
ferricoxide<p><span>I swear to god: since </span><a href="https://evil.social/tags/Google" rel="nofollow noopener noreferrer" target="_blank">#Google</a><span> decided that </span><i><span>my</span></i><span> email domain wasn't trustworthy (in spite of being older than Google, itself, and having </span><a href="https://evil.social/tags/SPF" rel="nofollow noopener noreferrer" target="_blank">#SPF</a><span>, </span><a href="https://evil.social/tags/DKIM" rel="nofollow noopener noreferrer" target="_blank">#DKIM</a><span> and </span><a href="https://evil.social/tags/DMARC" rel="nofollow noopener noreferrer" target="_blank">#DMARC</a><span> records, etc.), I've been receiving </span><i><span>more</span></i><span> spam from </span><a href="https://evil.social/@gmail" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@gmail</a><span>.com addresses.<br><br>Going to guess that, as they've made things more difficult for independent/small-scale domains to send emails to </span><a href="https://evil.social/tags/gMail" rel="nofollow noopener noreferrer" target="_blank">#gMail</a><span> and </span><a href="https://evil.social/tags/gSuite" rel="nofollow noopener noreferrer" target="_blank">#gSuite</a><span> users, more spammers are opening up accounts directly with Google to spam from.</span></p>
Ludovic :Firefox: :FreeBSD:<p>Learn and Test DMARC<br><a href="https://www.learndmarc.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">learndmarc.com/</span><span class="invisible"></span></a></p><p>Or how email works explained by an example, </p><p><a href="https://piaille.fr/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://piaille.fr/tags/ryoms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ryoms</span></a> <a href="https://piaille.fr/tags/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a> <a href="https://piaille.fr/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://piaille.fr/tags/smtp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>smtp</span></a></p>