social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.9K
active users

#spf

3 posts3 participants1 post today

Hey #email #nerds and #ServerAdmin people, I know about #DMARC, #SPF, and #DKIM and stuff. BUT.

Idea: system where email servers generate a #GUID identifier for that specific email and keep it in a database. Other servers and email clients can then just ping the #domain that the email says its from and confirm the real domain sent it.

Like, why couldn't this be a thing? Seems like it would completely stop those #spam emails that pretend to be from #PayPal or #banks.

Does anyone has a contact to the Joint Research Centre (#JRC) [0] or My Email Communications Security Assessment (#MECSA) [1] (both from the #EU)?

I find the tool great... if it would parse #SPF/#IPv6 correctly und actually check for #DNSSEC...

I've tried emailing them, but no response :/

Links:
[0]: joint-research-centre.ec.europ
[1]: mecsa.jrc.ec.europa.eu/

EU Science Hub
EU Science HubEU Science Hub homepageThe EU Science Hub - the website of the Joint Research Centre (JRC), the European Commission's science and knowledge service, providing scientific evidence throughout the whole policy cycle.

J'ai un nom de domaine chez #o2switch et depuis quelques jours, je ne peux plus envoyer de mails à mes contacts Gmail, à cause d'un problème de configuration SPF* ou DKIM.

Quand je lis cet article
faq.o2switch.fr/hebergement-mu
Ça n'a pas l'air simple à résoudre.

Parmi vous, les personnes qui lisez ce message, vous avez réussi à résoudre ce problème facilement chez o2switch ? Comment on fait ? 😬

* jusqu'à présent, le SPF était uniquement l'indice de protection d'une crème solaire 😁

Documentation · Authentification d'emailAuthentification d'email L'outil authentification d'email permet de configurer les DKIM et SPF pour l'ensemble des comptes mail de votre compte d'hébergement. Les DKIM et SPF permettent d'authentifier le serveur servant à envoyer votre message. Cela permet d'avoir une meilleure note sur les filtres antispam et limite l'usurpation de vos domaines (d'autres personnes envoyant illégitimement des messages avec votre domaine dans les entêtes).

✉️ 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 : afnic.fr/produits-services/for

𝐇𝐨𝐰 𝐭𝐨 𝐬𝐞𝐜𝐮𝐫𝐞 𝐲𝐨𝐮𝐫 𝐞𝐦𝐚𝐢𝐥 𝐰𝐢𝐭𝐡 𝐒𝐏𝐅, 𝐃𝐊𝐈𝐌 𝐚𝐧𝐝 𝐃𝐌𝐀𝐑𝐂

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 👇 👇
youtu.be/xtmDDl1rjOc

Irgendwie bin ich vielleicht einem Bug im #SPF-Modul von #Spamassassin auf der Spur. Ich habe heute 10 Stunden Dokus gelesen, mich durch den Perl-Quelltext gewühlt, verschiedene Konfigurationen ausprobiert und bestimmt 100 Testmails geschickt. Am Ende verhärtet sich der Verdacht, dass der Parser für die SPF-Regeln vielleicht ein Problem hat. Aber jetzt erst einmal Wochenende, Montag geht's weiter. Wenn ich das schaffe abzuschalten.

Is SPF Simply Too Hard For Application Developers?
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? nxdomain.no/~peter/is_spf_too_
(2016 but still holds) #smtp #spf #mail #spam #antispam #security #openbsd #spamd

nxdomain.noIs SPF Simply Too Hard For Application Developers?

TR-92 - Unused Domain Names and the Risks of Missing DNS SPF Records

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...

Read more circl.lu/pub/tr-92/

www.circl.luCIRCL » TR-92 - Unused Domain Names and the Risks of Missing DNS SPF RecordsTR-92 - Unused Domain Names and the Risks of Missing DNS SPF Records