toad.social

donburi<a href="https://floss.social/@artfulrobot" class="u-url mention" rel="nofollow noopener" target="_blank">@artfulrobot</a> Why exim4? Indeed, there is no good reason for that. Only Debian thinks there is... more than twenty years after Exim version 3 went out-of-date.<a href="https://universeodon.com/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a>

artfulrobotQuite pleased with my automated <a href="https://floss.social/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> delivery monitoring!In the case of low success % it gives a breakdown of per-domain fails and other info, too.I'm using it with the <a href="https://floss.social/tags/CiviMail" class="mention hashtag" rel="nofollow noopener" target="_blank">#CiviMail</a> component of <a href="https://floss.social/tags/CiviCRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#CiviCRM</a> <a href="https://floss.social/tags/exim4" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim4</a> (why must it be called that, nobody uses v3!)

artfulrobotHey <a href="https://fosstodon.org/tags/openSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSource</a> <a href="https://fosstodon.org/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> / <a href="https://fosstodon.org/tags/exim4" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim4</a> users **NOW** is a good time to apply a <a href="https://fosstodon.org/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> fix for your exim. Released 2 hours ago. If you use <a href="https://fosstodon.org/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#debian</a>, the updates are in the repos already.

NeedaBon du coup, je finis ma soirée <a href="https://piaille.fr/tags/EXIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#EXIM</a> et j'ai l'impression que pour l'intégration Let's Encrypt /TLS, ça relève encore du bricolage de droits ? Si vous connaissez une meilleure solution, je prends

NeedaMoment de solitude où je constate enfin que ma configuration <a href="https://piaille.fr/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> perso <a href="https://piaille.fr/tags/DKIM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DKIM</a> contenait une typo alors que le reste (<a href="https://piaille.fr/tags/SPF" class="mention hashtag" rel="nofollow noopener" target="_blank">#SPF</a>/#DMARC) était ok et ce depuis la migration, soit quasi 2 ans 🤡 N'oubliez pas de tester vos propres outils ! Cf. <a href="https://www.bortzmeyer.org/repondeurs-courrier-test.html" rel="nofollow noopener" translate="no" target="_blank">https://www.bortzmeyer.org/repondeurs-courrier-test.html</a>

ptyPrepare to update <a href="https://chaos.social/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a><a href="https://seclists.org/oss-sec/2025/q1/148" rel="nofollow noopener" translate="no" target="_blank">https://seclists.org/oss-sec/2025/q1/148</a><a href="https://chaos.social/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a>

🆘Bill Cole 🇺🇦Disturbing (data-dependent) bug in password handling by <a href="https://toad.social/tags/Exim" class="mention hashtag" rel="tag">#Exim</a> hit the exim-users list today. Hopefully the dev team have a handle on fixing it, but it really makes me glad for Postfix's arms-length relationship with <a href="https://toad.social/tags/SASL" class="mention hashtag" rel="tag">#SASL</a>. Just the idea that an authn system would (accidentally) have a mechanism for the subject to create a logical list separator for the MTA by crafting a password is crazymaking.<a href="https://toad.social/tags/Infosec" class="mention hashtag" rel="tag">#Infosec</a>

David Cantrell 🏏And the <a href="https://fosstodon.org/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> config is even older! That originated as exim 2 running on an <a href="https://fosstodon.org/tags/SGI" class="mention hashtag" rel="nofollow noopener" target="_blank">#SGI</a> <a href="https://fosstodon.org/tags/Indy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Indy</a>, which was copied to exim2 on <a href="https://fosstodon.org/tags/Redhat" class="mention hashtag" rel="nofollow noopener" target="_blank">#Redhat</a> (I think) running on a <a href="https://fosstodon.org/tags/Tadpole" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tadpole</a> <a href="https://fosstodon.org/tags/Sparcbook" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sparcbook</a>, then copied to exim 2 on <a href="https://fosstodon.org/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> (which it is now on) and upgraded to exim 3 and then exim 4 with numerous tweaks along the way. Needless to say it's a goddamn mess.

David Cantrell 🏏The approximately four generations deprecated VM that handles my email is finally being killed off by my ISP, and I can't really say that I blame them. I have about a month to find a new email provider for <a href="https://fosstodon.org/tags/SMTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMTP</a> and <a href="https://fosstodon.org/tags/IMAP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMAP</a>. No, I'm not going to host it myself again. Suggestions? So far <a href="https://fosstodon.org/tags/Fastmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fastmail</a> looks like it's not complete and utter dogshit although obviously it will never be as capable as my tangled mess of custom <a href="https://fosstodon.org/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> and <a href="https://fosstodon.org/tags/procmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#procmail</a>.

IT NewsMore than 1.5 million email servers running Exim vulnerable to critical attacks - Enlarge More than 1.5 million email servers are vulnerable to... - <a href="https://arstechnica.com/?p=2036607" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/?p=2036607</a> <a href="https://schleuss.online/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerabilities</a> <a href="https://schleuss.online/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://schleuss.online/tags/exploits" class="mention hashtag" rel="nofollow noopener" target="_blank">#exploits</a> <a href="https://schleuss.online/tags/biz" class="mention hashtag" rel="nofollow noopener" target="_blank">#biz</a>⁢ <a href="https://schleuss.online/tags/email" class="mention hashtag" rel="nofollow noopener" target="_blank">#email</a> <a href="https://schleuss.online/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a>

LinuxiacNew Exim 4.98 MTA addresses critical SMTP vulnerabilities. Includes crucial updates for DKIM handling and SMTP security. <a href="https://linuxiac.com/exim-4-98-mta-patches-over-30-bugs/" rel="nofollow noopener" translate="no" target="_blank">https://linuxiac.com/exim-4-98-mta-patches-over-30-bugs/</a><a href="https://mastodon.social/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> <a href="https://mastodon.social/tags/mta" class="mention hashtag" rel="nofollow noopener" target="_blank">#mta</a> <a href="https://mastodon.social/tags/smtp" class="mention hashtag" rel="nofollow noopener" target="_blank">#smtp</a>

Mark Gardner<a href="https://kolektiva.social/@AnarchoDoggo" class="u-url mention" rel="nofollow noopener" target="_blank">@AnarchoDoggo</a> <a href="https://social.edist.ro/@silberfuchs" class="u-url mention" rel="nofollow noopener" target="_blank">@silberfuchs</a> <a href="https://fedi.seriousbusiness.international/users/swaggboi" class="u-url mention" rel="nofollow noopener" target="_blank">@swaggboi</a> <a href="https://social.sdf.org/tags/Perl" class="mention hashtag" rel="nofollow noopener" target="_blank">#Perl</a> did not “give” the world <a href="https://social.sdf.org/tags/PCRE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PCRE</a>; Philip Hazel wrote it for the <a href="https://social.sdf.org/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> mail transport agent software in 1997.I like to refer to it as “*Partially* Compatible Regular Expressions.” Here is the project’s documentation on (some) areas where it will disappoint you: <a href="https://PCRE.org/current/doc/html/pcre2compat.html" rel="nofollow noopener" translate="no" target="_blank">https://PCRE.org/current/doc/html/pcre2compat.html</a>

Bernard Quatermass<a href="https://vmst.io/@jalefkowit" class="u-url mention" rel="nofollow noopener" target="_blank">@jalefkowit</a> lovely to see this article.It’s an honour to help keep the <a href="https://ehlo.exim.org/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> torch alive.

artfulrobotOh no. I think I've got to reconfigure <a href="https://fosstodon.org/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> a bit. Maybe I'll stick needles up behind my nails and use the keyboard like that to focus my mind on something other than the pain of this task!I use exim a lot, but the config has a real lack of logic/structure, the syntax is written by someone who criticises Perl for being too readable and testing it is cumbersome.I don't have the spoons to try to transfer my needs/knowledge to postfix. Email delivery is just so darned complex.<a href="https://fosstodon.org/tags/exim4" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim4</a>

Quinn ComendantWho's making a LLM-based spam filter plugin for <a href="https://mastodon.social/tags/Spamassassin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Spamassassin</a> or <a href="https://mastodon.social/tags/Rspamd" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rspamd</a>?Gmail has advanced AI-based filtering. Now that LLMs are becoming democratized, I'm ready for a self-hosted AI spam filter.It seems much more popular to publish research papers on the viability of LLM-based spam filtering than it is to build LLM-based spam filtering software. Here are dozens of papers: <a href="https://www.arxiv-sanity-lite.com/?rank=pid&pid=2206.02443" rel="nofollow noopener" translate="no" target="_blank">https://www.arxiv-sanity-lite.com/?rank=pid&pid=2206.02443</a> Nothing on GitHub, yet.<a href="https://mastodon.social/tags/llm" class="mention hashtag" rel="nofollow noopener" target="_blank">#llm</a> <a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener" target="_blank">#ai</a> <a href="https://mastodon.social/tags/spam" class="mention hashtag" rel="nofollow noopener" target="_blank">#spam</a> <a href="https://mastodon.social/tags/phishing" class="mention hashtag" rel="nofollow noopener" target="_blank">#phishing</a> <a href="https://mastodon.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#SelfHosting</a> <a href="https://mastodon.social/tags/postfix" class="mention hashtag" rel="nofollow noopener" target="_blank">#postfix</a> <a href="https://mastodon.social/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> <a href="https://mastodon.social/tags/sendmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#sendmail</a> <a href="https://mastodon.social/tags/qmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#qmail</a>

DFN-CERT<a href="https://infosec.exchange/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> released 4.97.1 to address the recent SMTP Smuggling vuln (CVE-2023-51766).<a href="https://lists.exim.org/lurker/message/20231228.211920.dd3e6d22.en.html" rel="nofollow noopener" translate="no" target="_blank">https://lists.exim.org/lurker/message/20231228.211920.dd3e6d22.en.html</a>

DFN-CERTcr;lf: SMTP smuggling / email spoofing involving different MTAs possibleDetails at <a href="https://infosec.exchange/tags/37c3" class="mention hashtag" rel="nofollow noopener" target="_blank">#37c3</a> later today <a href="https://events.ccc.de/congress/2023/hub/en/event/smtp_smuggling_spoofing_e-mails_worldwide/" rel="nofollow noopener" translate="no" target="_blank">https://events.ccc.de/congress/2023/hub/en/event/smtp_smuggling_spoofing_e-mails_worldwide/</a>SEC consult blog post here: <a href="https://sec-consult.com/blog/detail/smtp-smuggling-spoofing-e-mails-worldwide/" rel="nofollow noopener" translate="no" target="_blank">https://sec-consult.com/blog/detail/smtp-smuggling-spoofing-e-mails-worldwide/</a><a href="https://infosec.exchange/tags/Postfix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Postfix</a> comments and releases new versions <a href="https://www.postfix.org/smtp-smuggling.html" rel="nofollow noopener" translate="no" target="_blank">https://www.postfix.org/smtp-smuggling.html</a> <a href="https://www.postfix.org/announcements/postfix-3.5.23.html" rel="nofollow noopener" translate="no" target="_blank">https://www.postfix.org/announcements/postfix-3.5.23.html</a> <a href="https://www.postfix.org/announcements/postfix-3.6.13.html" rel="nofollow noopener" translate="no" target="_blank">https://www.postfix.org/announcements/postfix-3.6.13.html</a> <a href="https://www.postfix.org/announcements/postfix-3.7.9.html" rel="nofollow noopener" translate="no" target="_blank">https://www.postfix.org/announcements/postfix-3.7.9.html</a> <a href="https://www.postfix.org/announcements/postfix-3.8.4.html" rel="nofollow noopener" translate="no" target="_blank">https://www.postfix.org/announcements/postfix-3.8.4.html</a><a href="https://infosec.exchange/tags/Sendmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sendmail</a> has a Snapshot 8.18.0.2 with a new configuration option available for testing <a href="https://groups.google.com/g/comp.mail.sendmail/c/zwJW9907Zgo" rel="nofollow noopener" translate="no" target="_blank">https://groups.google.com/g/comp.mail.sendmail/c/zwJW9907Zgo</a><a href="https://infosec.exchange/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> does some work behind the scenes: <a href="https://lists.exim.org/lurker/thread/20231223.193645.5f50f60a.de.html" rel="nofollow noopener" translate="no" target="_blank">https://lists.exim.org/lurker/thread/20231223.193645.5f50f60a.de.html</a> <a href="https://github.com/Exim/exim/commit/cf1376206284f2a4f11e32d931d4aade34c206c5" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Exim/exim/commit/cf1376206284f2a4f11e32d931d4aade34c206c5</a> <a href="https://github.com/Exim/exim/commit/5bb786d5ad568a88d50d15452aacc8404047e5ca" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Exim/exim/commit/5bb786d5ad568a88d50d15452aacc8404047e5ca</a>oss-sec thread here: <a href="https://seclists.org/oss-sec/2023/q4/306" rel="nofollow noopener" translate="no" target="_blank">https://seclists.org/oss-sec/2023/q4/306</a>

Marcel WaldvogelAfter having been informed by <a href="https://piaille.fr/@mathieui" class="u-url mention" rel="nofollow noopener" target="_blank">@mathieui</a> that <a href="https://waldvogel.family/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> is also affected, I compiled a list of what <a href="https://waldvogel.family/tags/SECConsult" class="mention hashtag" rel="nofollow noopener" target="_blank">#SECConsult</a> documented and what has been found out in the meantime. SEC Consult documented 11 mail systems (software and/or providers; many with millions of accounts) vulnerable to some form of <a href="https://waldvogel.family/tags/SMTPSmuggling" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMTPSmuggling</a>. But they only informed 3. With <a href="https://waldvogel.family/tags/Exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#Exim</a> also vulnerable (apparently presumed "clean" by SEC Consult), the list is now 12. <a href="https://netfuture.ch/2023/12/smtp-smuggling-status/" rel="nofollow noopener" translate="no" target="_blank">https://netfuture.ch/2023/12/smtp-smuggling-status/</a>

Siderea, Sibylla BostoniensisI have unfairly maligned <a href="https://universeodon.com/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a>'s honor. This is a <a href="https://universeodon.com/tags/procmail" class="mention hashtag" rel="nofollow noopener" target="_blank">#procmail</a> problem. Or at least procmail is the identified patient.The problem seems to be that procmail feels very strongly about the system mailbox (/var/spool/mail/$whatever). If it doesn't exist, it attempts to create it. If it can't create it, it throws an error (and the message bounces). If it doesn't need to create it but can't access it, it throws a different error. If it can access it but doesn't like its permissions, also error.

Jan Wildeboer 😷:krulorange:<a href="https://social.wildeboer.net/tags/exim" class="mention hashtag" rel="nofollow noopener" target="_blank">#exim</a> is tracking this in their bug report at <a href="https://bugs.exim.org/show_bug.cgi?id=3063" rel="nofollow noopener" translate="no" target="_blank">https://bugs.exim.org/show_bug.cgi?id=3063</a> and a fix has been committed at <a href="https://git.exim.org/exim.git/commit/5bb786d5ad568a88d50d15452aacc8404047e5ca" rel="nofollow noopener" translate="no" target="_blank">https://git.exim.org/exim.git/commit/5bb786d5ad568a88d50d15452aacc8404047e5ca</a> - thx <a href="https://infosec.exchange/@QuatermassTools" class="u-url mention" rel="nofollow noopener" target="_blank">@QuatermassTools</a> for the info! <a href="https://infosec.exchange/@QuatermassTools/111637108410087826" rel="nofollow noopener" translate="no" target="_blank">https://infosec.exchange/@QuatermassTools/111637108410087826</a>

Recent searches

Search options

Administered by:

Server stats:

#exim