Adrian Offerman<p>op SIDN.nl:<br>Vier moderne mail-systemen voor self-hosting -- Beveiligingsstandaarden voor mail universeel ondersteund<br><a href="https://www.sidn.nl/nieuws-en-blogs/vier-moderne-mailsystemen-voor-self-hosting" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">sidn.nl/nieuws-en-blogs/vier-m</span><span class="invisible">oderne-mailsystemen-voor-self-hosting</span></a></p><p>Inmiddels zijn er meerdere software-pakketten beschikbaar die én alle beveiligingsstandaarden out-of-the-box ondersteunen én makkelijk op te zetten zijn. In dit artikel bespreken we vier moderne open-source mail-pakketten voor self-hosting: <a href="https://mastodon.offerman.com/tags/Mox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mox</span></a>, <a href="https://mastodon.offerman.com/tags/Chasquid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chasquid</span></a>, <a href="https://mastodon.offerman.com/tags/Stalwart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Stalwart</span></a> en <a href="https://mastodon.offerman.com/tags/Maddy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Maddy</span></a>.</p><p><a href="https://mastodon.offerman.com/tags/SPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SPF</span></a> <a href="https://mastodon.offerman.com/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://mastodon.offerman.com/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://mastodon.offerman.com/tags/DANE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DANE</span></a> <a href="https://mastodon.offerman.com/tags/STARTTLS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>STARTTLS</span></a> <a href="https://mastodon.offerman.com/tags/MTA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MTA</span></a>-STS <a href="https://mastodon.offerman.com/tags/InternetSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InternetSecurity</span></a></p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@stalwartlabs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stalwartlabs</span></a></span></p>
Recent searches
No recent searches
Search options
Only available when logged in.
det.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon Server des Unterhaltungsfernsehen Ehrenfeld zum dezentralen Diskurs.
Administered by:
Server stats:
2.1Kactive users
det.social: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.2
#dkim
1 post · 1 participant · 0 posts today
EMDiscussions<p><span class="h-card" translate="no"><a href="https://social.stefanberger.net/@stefan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stefan</span></a></span> The easiest way I know to check an XML report:</p><p><a href="https://us.dmarcian.com/xml-to-human-converter/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">us.dmarcian.com/xml-to-human-c</span><span class="invisible">onverter/</span></a></p><p><a href="https://mastodon.social/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</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/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></p>
Stefan :veritrek:<p>Interesting. Got my first <a href="https://social.stefanberger.net/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> report today.. from Google.<br>Never got something like this before. Think it’s related to my changed DNS settings when I switched to <span class="h-card" translate="no"><a href="https://social.mailbox.org/@mailbox_org" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mailbox_org</span></a></span></p><p>Looks good I guess with all the *pass* for DKIM and SPF. There is a link in the xml to this URL <a href="https://support.google.com/a/answer/2466580" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">support.google.com/a/answer/24</span><span class="invisible">66580</span></a></p><p>Will check how to read to xml..</p>
The New Oil<p><a href="https://mastodon.thenewoil.org/tags/Phishers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Phishers</span></a> abuse <a href="https://mastodon.thenewoil.org/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> <a href="https://mastodon.thenewoil.org/tags/OAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAuth</span></a> to spoof Google in <a href="https://mastodon.thenewoil.org/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> replay attack</p><p><a href="https://www.bleepingcomputer.com/news/security/phishers-abuse-google-oauth-to-spoof-google-in-dkim-replay-attack/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">bleepingcomputer.com/news/secu</span><span class="invisible">rity/phishers-abuse-google-oauth-to-spoof-google-in-dkim-replay-attack/</span></a></p><p><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</span></a></p>
Efani<p>⚠️ Phishers have found a clever way to spoof Google — and their emails pass all security checks.</p><p>A new DKIM replay phishing attack abuses Google’s own OAuth infrastructure to send fake messages that look 100% legitimate, including passing DKIM authentication.</p><p>What happened:<br>- A phishing email was sent from “no-reply@google.com” <br>- It appeared in the user’s inbox alongside real Google security alerts <br>- The message linked to a fake support portal hosted on sites[dot]google[dot]com — a Google-owned domain <br>- The attacker used Google OAuth to trigger a real security alert to their inbox, then forwarded it to victims </p><p>Why this matters:<br>- DKIM only verifies the headers, not the envelope — allowing this spoof to work <br>- The phishing site was nearly indistinguishable from Google’s actual login portal <br>- Because the message was signed by Google and hosted on a Google domain, it bypassed most users’ suspicions <br>- Similar tricks have been used with PayPal and other platforms, raising broader concerns </p><p>Google has since acknowledged the issue and is working on a fix. But this attack is a reminder:</p><p>Even the most secure-looking emails can be fraudulent. <br>Even Google-signed emails can be weaponized.</p><p>🛡️ At <span class="h-card" translate="no"><a href="https://infosec.exchange/@Efani" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Efani</span></a></span>, we advocate for layered defense — because no one layer is ever enough.</p><p><a href="https://infosec.exchange/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cybersecurity</span></a> <a href="https://infosec.exchange/tags/Phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Phishing</span></a> <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> <a href="https://infosec.exchange/tags/OAuth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OAuth</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/EmailSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EmailSecurity</span></a> <a href="https://infosec.exchange/tags/EfaniSecure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EfaniSecure</span></a> <a href="https://infosec.exchange/tags/ThreatIntel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ThreatIntel</span></a></p>
The DefendOps Diaries<p>Imagine getting a Google alert that's anything but real. Hackers are reusing DKIM-signed emails via Google OAuth to bypass security—are our inboxes truly safe? Read on to uncover how this crafty loophole is exploited.</p><p><a href="https://thedefendopsdiaries.com/exploiting-google-oauth-the-dkim-replay-attack-threat/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thedefendopsdiaries.com/exploi</span><span class="invisible">ting-google-oauth-the-dkim-replay-attack-threat/</span></a></p><p><a href="https://infosec.exchange/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a><br><a href="https://infosec.exchange/tags/emailsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>emailsecurity</span></a><br><a href="https://infosec.exchange/tags/phishing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>phishing</span></a><br><a href="https://infosec.exchange/tags/googleoauth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>googleoauth</span></a><br><a href="https://infosec.exchange/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</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>
l<p>At least <a href="https://fosstodon.org/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> is an authentication mechanism designed to prevent email address spoofing, i.e. using a domain that you don't own in the From field that you send. It is not designed to prevent spam and it is clear from the specification that authors are aware of it: <a href="https://www.rfc-editor.org/rfc/rfc6376#section-8.6" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">rfc-editor.org/rfc/rfc6376#sec</span><span class="invisible">tion-8.6</span></a></p>
N-gated Hacker News<p>Wow, who knew <a href="https://mastodon.social/tags/spammers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spammers</span></a> were the real email security ninjas? 🤦♂️ Apparently, their <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/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a>, and <a href="https://mastodon.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> game is on point, while the rest of us are still trying to figure out why we can't open <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> without JavaScript. 🐢💻<br><a href="https://toad.social/@grumpybozo/114213600922816869" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">toad.social/@grumpybozo/114213</span><span class="invisible">600922816869</span></a> <a href="https://mastodon.social/tags/emailsecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>emailsecurity</span></a> <a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HackerNews</span></a> <a href="https://mastodon.social/tags/ngated" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ngated</span></a></p>
Hacker News<p>Spammers are better at SPF, DKIM, and DMARC than everyone else</p><p><a href="https://toad.social/@grumpybozo/114213600922816869" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">toad.social/@grumpybozo/114213</span><span class="invisible">600922816869</span></a></p><p><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HackerNews</span></a> <a href="https://mastodon.social/tags/Spammers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Spammers</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/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/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cybersecurity</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>
Cybso<p>Mein Mailserver macht jetzt endlich auch <a href="https://osna.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> und hat einen <a href="https://osna.social/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a>-Eintrag. Hab das viel zu lange vor mir her geschoben, aber weil das nun auch für den betrieblichen Mailserver gefordert war, musste mein privater als Übungsobjekt herhalten 😊</p><p>War gar nicht so schwierig wie befürchtet.</p>
Éric V.<p>For <a href="https://mamot.fr/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> configuration and <a href="https://mamot.fr/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> check, the European Commission provides a great tool: MECSA <a href="https://mecsa.jrc.ec.europa.eu/en/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">mecsa.jrc.ec.europa.eu/en/</span><span class="invisible"></span></a><br>conclusion: I still have some improvements to implement on my own server<br><a href="https://mamot.fr/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sysadmin</span></a> <a href="https://mamot.fr/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linux</span></a> <a href="https://mamot.fr/tags/postfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>postfix</span></a> <a href="https://mamot.fr/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> <a href="https://mamot.fr/tags/DMARC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DMARC</span></a> <a href="https://mamot.fr/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNSSEC</span></a> <a href="https://mamot.fr/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosting</span></a></p>
Martin Schmitt<p><a href="https://mastodon.online/tags/Datev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Datev</span></a> hat Probleme, <a href="https://mastodon.online/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> eines Kunden von mir zu validieren. Es steht die Vermutung im Raum, dass das daran liegen könnte, dass einer meiner authoritativen Nameserver auch <a href="https://mastodon.online/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tor</span></a>-Relay (ohne Exit) ist. Wir testen deshalb jetzt mal 4 Wochen ohne ihn. Welche Gründe könnte es geben, auf Enterprise-Ebene die Firewall mit irgendwelchen Just-because-I-can-RBLs von Hobbyisten zu betanken? BITTE NUR FALSCHE ANTWORTEN.</p>
Delta Chat<p><span class="h-card" translate="no"><a href="https://jura.social/@mathilde" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mathilde</span></a></span> <a href="https://chaos.social/tags/chatmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>chatmail</span></a> server users don't have these problems because they don't even need to know their password or email address. Messages in delta chat are stored locally and the server only stores them for a limited time, up to 20 days by default, so all devices have a chance to download the message. Blocklists are also not used, the only requirements are <a href="https://chaos.social/tags/DKIM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DKIM</span></a> signature and <a href="https://chaos.social/tags/OpenPGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenPGP</span></a> encryption.</p>
Roman Schaller<p><span class="h-card" translate="no"><a href="https://jawsome.nevy.xyz/@nev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nev</span></a></span> Same here. <a href="https://stalw.art/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">stalw.art/</span><span class="invisible"></span></a> was my choice. Works so far. But be careful with <a href="https://mastodon.green/tags/spf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>spf</span></a> and <a href="https://mastodon.green/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a>. It is important to set those up correctly. Otherwise your mails will be marked as spam.</p>
Julien Riou<p>I've Got Mail <a href="https://bonesmoses.org/2025/ive-got-mail/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bonesmoses.org/2025/ive-got-ma</span><span class="invisible">il/</span></a></p><p><a href="https://hachyderm.io/tags/email" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>email</span></a> <a href="https://hachyderm.io/tags/postfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>postfix</span></a> <a href="https://hachyderm.io/tags/postgrey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>postgrey</span></a> <a href="https://hachyderm.io/tags/dovecot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dovecot</span></a> <a href="https://hachyderm.io/tags/roundcube" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>roundcube</span></a> <a href="https://hachyderm.io/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a> <a href="https://hachyderm.io/tags/dkim" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dkim</span></a> <a href="https://hachyderm.io/tags/dmarc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dmarc</span></a> <a href="https://hachyderm.io/tags/mailinabox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mailinabox</span></a> <a href="https://hachyderm.io/tags/mailu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mailu</span></a> <a href="https://hachyderm.io/tags/mailcow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mailcow</span></a> <a href="https://hachyderm.io/tags/stalwart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>stalwart</span></a> <a href="https://hachyderm.io/tags/protonmail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>protonmail</span></a> <a href="https://hachyderm.io/tags/python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>python</span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload