<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Spam on kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/spam/</link><description>Recent content in Spam on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/spam/index.xml" rel="self" type="application/rss+xml"/><item><title>Rspamd 4.1.0: Security Fixes, a Reworked MX Check, and a Breaking Symbol Rename</title><link>https://blog.kalfaoglu.net/posts/2026-06-07-rspamd-410-security-mx-rework-en/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-06-07-rspamd-410-security-mx-rework-en/</guid><description>&lt;p&gt;Rspamd 4.1.0 dropped on June 5 — a major release tagged &amp;ldquo;recommended upgrade for all users&amp;rdquo; by the development team. There&amp;rsquo;s enough in it that&amp;rsquo;s immediately relevant to anyone running a mail server to warrant reading the changelog before blindly upgrading.&lt;/p&gt;
&lt;h2 id="the-security-fixes"&gt;The security fixes&lt;/h2&gt;
&lt;p&gt;This release addresses several memory-safety issues that can be triggered by crafted incoming mail.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;S/MIME DoS via recursive PKCS7&lt;/strong&gt;: A deeply nested &lt;code&gt;application/pkcs7-mime&lt;/code&gt; message re-entered the parser without incrementing the nesting counter. In practice this means a malicious sender could craft a message that exhausts your rspamd worker&amp;rsquo;s stack. The fix gates S/MIME re-entry against the existing &lt;code&gt;max_nested&lt;/code&gt; limit.&lt;/p&gt;</description></item></channel></rss>