[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rewriting header incorrectly?

From: Michael Wyraz
Subject: Re: Rewriting header incorrectly?
Date: Wed, 02 Dec 2009 17:00:00 +0100
User-agent: Thunderbird (Windows/20090812)

Hi Steve,

both patches are not from me but from distribution maintainers.

The first (  is about a missing whitespace and a missing closing bracket. The result is a "UNPARSEABLE_RELAY" which can lead to high spam score if so configured.

The 2nd is that milter passes the mail to spamassassin before postfix write it's "received" header (applies only if spam check is made during smtp dialog). So in this phase there's no information about the authenticated user. If you have checks for dynamic ip or so, this leads to high score because the mails appears to be from an non-authenticated user. There's a patch available at but if relies on "auth_ssf" macro which is not available on postfix (so it's better to use the "auth_authen" macro instead which is a minimal change).

Depending on the distribution you use, these patches my already be included.

On Wed, 2009-12-02 at 10:33 +0100, Michael Wyraz wrote:

please have a look to my post on the mailing list:
There are links to two patches dealing with the header.

And please please please make a new release :-)

Regards, Michael.

__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4653 (20091201) __________

E-Mail wurde geprüft mit ESET NOD32 Antivirus.

Spamass-milt-list mailing list
There is no useful information at that link/post.

Proof of concept, examples, how to recreate, what issue it gives with
spam scoring.

Without being rude I've run this milter with Spamassassin for over a
year on a single machine handling 3/4 of a million messages a day and I
don't get a single issue with it.

Exactly what is the problem?

Spamass-milt-list mailing list

__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4655 (20091202) __________

E-Mail wurde gepr�ft mit ESET NOD32 Antivirus.


__________ Hinweis von ESET NOD32 Antivirus, Signaturdatenbank-Version 4655 (20091202) __________

E-Mail wurde geprft mit ESET NOD32 Antivirus.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]