helvede.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Velkommen til Helvede, fediversets hotteste instance! Vi er en queerfeministisk server, der shitposter i den 9. cirkel. Welcome to Hell, We’re a DK-based queerfeminist server. Read our server rules!

Server stats:

171
active users

#spf

0 posts0 participants0 posts today
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>
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>
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>
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>
Stéphane Bortzmeyer<p>Cours <a href="https://mastodon.gougere.fr/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> / <a href="https://mastodon.gougere.fr/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> / <a href="https://mastodon.gougere.fr/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>. Je leur raconte quoi de joli ?</p>
Harald Hannelius :verified:<p>A partner higher ed has a mailing list on <a href="https://mementomori.social/tags/ExchangeOnline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ExchangeOnline</span></a> . So their <a href="https://mementomori.social/tags/SMTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMTP</span></a> server contacts ours and says "Hello, here's an e-mail from your domain". Our <a href="https://mementomori.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> says no thanks (are we actually the only ones blocking based on SPF?). </p><p>The listserver should rewrite headers and use a return-path address from their domain. The From: header can have our user's emailaddress (think this breaks DKIM though?). </p><p>Good luck for our partner in fixing this on their end. They probably have to set up a <a href="https://mementomori.social/tags/MTA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MTA</span></a> and route all outgoing mail through that. Ms won't fix.</p>
Florian Bierhoff<p>Claudia Plattner, President of German BSI, has just been featured in an article on email security in eco's dotmagazine. It's a wake up call and invitation to enhance email security in a joined effort :blobs:</p><p>I like it :ablobsmile:</p><p><a href="https://www.dotmagazine.online/issues/digital-security-trust-consumer-protection/enhancing-email-security" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">dotmagazine.online/issues/digi</span><span class="invisible">tal-security-trust-consumer-protection/enhancing-email-security</span></a></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/DANE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DANE</span></a> <a href="https://infosec.exchange/tags/TLSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLSA</span></a> <a href="https://infosec.exchange/tags/MTASTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MTASTS</span></a> <a href="https://infosec.exchange/tags/TLSRPT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLSRPT</span></a> <a href="https://infosec.exchange/tags/Mailsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mailsecurity</span></a> <a href="https://infosec.exchange/tags/TeamBSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TeamBSI</span></a> <span class="h-card" translate="no"><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bsi</span></a></span></p>
Stéphane Bortzmeyer<p>Là, on a un champion : un serveur de messagerie qui voit (grâce à <a href="https://mastodon.gougere.fr/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>) que l'adresse est usurpée et, pour le dire, envoie un message… à l'adresse usurpée.</p>
Florian Bierhoff<p>The Internet Security Days 2024 marked the starting point for a new effort by eco and <span class="h-card" translate="no"><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bsi</span></a></span> to raise adoption of modern email security standards across Germany and worldwide. I'm honored that I was allowed to shape some of the contents of this great event and mailsecurity is finally getting the attention it deserves 💌 :blobcatthx: </p><p><a href="https://international.eco.de/news/internet-security-days-2024-it-security-for-email-ai-and-nis2/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">international.eco.de/news/inte</span><span class="invisible">rnet-security-days-2024-it-security-for-email-ai-and-nis2/</span></a></p><p><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/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/DANE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DANE</span></a> <a href="https://infosec.exchange/tags/TLSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLSA</span></a> <a href="https://infosec.exchange/tags/MTASTS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MTASTS</span></a> <a href="https://infosec.exchange/tags/TLSRPT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TLSRPT</span></a> <a href="https://infosec.exchange/tags/Mailsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mailsecurity</span></a> <a href="https://infosec.exchange/tags/TeamBSI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TeamBSI</span></a></p>
Afnic<p>🗓️ Formation Sécuriser son courrier électronique grâce au DNS avec DKIM, DMARC, SPF les 10 et 11 octobre ou 5 et 6 décembre 2024.</p><p>✅ Programme complet et inscriptions sur <a href="https://www.afnic.fr/produits-services/formations/dkim-dmarc-spf-securiser-son-courrier-electronique-grace-au-dns/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">afnic.fr/produits-services/for</span><span class="invisible">mations/dkim-dmarc-spf-securiser-son-courrier-electronique-grace-au-dns/</span></a></p><p><a href="https://mastodon.social/tags/Formation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Formation</span></a> <a href="https://mastodon.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://mastodon.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://mastodon.social/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> <a href="https://mastodon.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a></p>
Milouse 😺🚀<p>Quelqu’un aurait une explication simple de fonctionnement des règles "a" et "mx" dans une déclaration <a href="https://boitam.eu/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> dans ses <a href="https://boitam.eu/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> ? Est-ce que ça vérifie que le domaine de l’adresse email possède un enregistrement a ou mx qui pointe sur la même IP que le serveur d’envoi de l’email ou "juste" qu’il existe un enregistrement a et mx, quelle que soit l’IP en question? 🤔</p>
Lars Marowsky-Brée 😷<p>Once you correctly configure your own SPF/DKIM setup and switch on reject/quarantine, you get to debug *everyone else's* misconfigured email forwarding or mailing list setup 🥰 </p><p>Yay?</p><p><a href="https://mastodon.online/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://mastodon.online/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> <a href="https://mastodon.online/tags/cursed" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cursed</span></a></p>
Peter N. M. Hansteen<p>RFC7505 Means Yes, Your Domain Can Refuse to Handle Mail. Please Leave Us a TXT If You Do. </p><p>Reprise from 2021, now also trackerless - <a href="https://nxdomain.no/~peter/rfc7505_means_yes_you_can_refuse_to_handle_mail.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nxdomain.no/~peter/rfc7505_mea</span><span class="invisible">ns_yes_you_can_refuse_to_handle_mail.html</span></a> <a href="https://mastodon.social/tags/NULLMX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NULLMX</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/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> # security <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/spam" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spam</span></a> <a href="https://mastodon.social/tags/RFC7505" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC7505</span></a> <a href="https://mastodon.social/tags/SMTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMTP</span></a> (and converting from G's wysiwyg editor droppings is painful fyi)</p>
Aslak Raanes<p>Burde ikke <a href="https://mastodon.social/tags/Vy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Vy</span></a> legge lista litt høyere for vy.no-avsender for kvitteringer o.l.?</p><p><a href="https://internet.nl/mail/vy.no/1305185/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">internet.nl/mail/vy.no/1305185</span><span class="invisible">/</span></a></p><p><a href="https://mastodon.social/tags/allheimen" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>allheimen</span></a> <a href="https://mastodon.social/tags/samferdsel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>samferdsel</span></a> <a href="https://mastodon.social/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</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/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a> <a href="https://mastodon.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a></p>
Patrick Ben Koetter 🕺🏼<p>Inwiefern ist DMARC und insbesondere sind dessen Report-Formate aggregate und forensic mit den Anforderungen der DSGVO vereinbar? Katharina Küchler (Anwältin, eco Verband) und ich (E-Mail Experte, Leiter Kompetenzgruppe E-Mail eco) sind dieser Frage im vollständig überarbeiteten Rechtsgutachten des <a href="https://troet.cafe/tags/eco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>eco</span></a> Verbandes nachgegangen.</p><p>Möge es für alle hier von Nutzen sein!</p><p>Deutsch:<br><a href="https://www.eco.de/download/238585/" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://www.</span><span class="">eco.de/download/238585/</span><span class="invisible"></span></a></p><p>Englisch:<br><a href="https://international.eco.de/download/238605" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">international.eco.de/download/</span><span class="invisible">238605</span></a></p><p><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> <a href="https://troet.cafe/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://troet.cafe/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://troet.cafe/tags/eco" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>eco</span></a></p>
Stéphane Bortzmeyer<p>Si vous aimez analyser les en-têtes et le code source du courrier électronique, le message de Macron Travail prévenant que vos données ont été piratées est très intéressant.</p><p><a href="https://mastodon.gougere.fr/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://mastodon.gougere.fr/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://mastodon.gougere.fr/tags/cybers%C3%A9curitay" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersécuritay</span></a></p>
Jan Schaumann<p>Every so often, I need to chase down some aspect of email validation (<a href="https://mstdn.social/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a>, <a href="https://mstdn.social/tags/DMKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMKIM</span></a>, <a href="https://mstdn.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>, ...). This involves a number of <a href="https://mstdn.social/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> records and queries, but I may forget just which ones. So here's a quick <a href="https://mstdn.social/tags/SMTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SMTP</span></a>/DNS cheatsheet:</p>
Patrick Ben Koetter 🕺🏼<p>An alle, die mit E-Mail zu tun haben und die es amtlich richtig™ machen wollen: Das <span class="h-card"><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bsi</span></a></span> hat die Technische Richtlinie BSI TR-03182 „Email Authentication“ <a href="https://bsi.bund.de/dok/tr-03182-en" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="">bsi.bund.de/dok/tr-03182-en</span><span class="invisible"></span></a> veröffentlicht, welche beschreibt wie <a href="https://troet.cafe/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a>, <a href="https://troet.cafe/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a> und <a href="https://troet.cafe/tags/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a> eingesetzt werden müssen, damit sie konform mit der TR sind und einen Audit für eine BSI-Zertifizierung bestehen können.</p><p>Weshalb ich das schreibe? Ihr lest den troet des stolzen Autors, der 1,5 Jahre mit dem BSI an der TR getüftelt hat.</p>