Problems with 5.1.1 milter

Mark Sapiro mark at
Mon Oct 8 02:17:20 UTC 2018

Shawn Iverson wrote:

> There's a performance fix in this commit that should help with most of
> this.  The crashing is likely from partially written messages in the
> milterin queue as a result of not writing the file in a single pass.  I
> hope to get a few more issues resolved before doing another release.

I've been doing a bit more testing. I installed the above change, and
even with that I see this issue.

I submit a message whose headers end with

MIME-Version: 1.0
Content-Type: multipart/alternative;

And the resultant message after MailScanner has headers ending with

MIME-Version: 1.0
Content-Type: multipart/alternative;
X-msapiro-MailScanner-ID: 12CA95A5DC.AD7FE
X-msapiro-MailScanner: Found to be clean
X-msapiro-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
        score=1.132, required 6, DKIM_SIGNED 0.10,
        RCVD_IN_DNSWL_NONE -0.00, T_DKIM_INVALID 0.01, T_MIME_MALF 0.01,
X-msapiro-MailScanner-SpamScore: s
X-msapiro-MailScanner-From: mark at
X-Spam-Status: No

I.e. the MailScanner report headers are inserted before the last line of
the headers rather than appended after. This is not always a problem,
but in this case, it causes the 'boundary=' to be separated from the
'Content-Type:' which is a problem.

Mark Sapiro <mark at>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

More information about the MailScanner mailing list