You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Jon Kvebaek <jk...@klanen.no> on 2005/12/15 16:03:59 UTC
Messages without received headers and ALL_TRUSTED
Hi,
we get quite a few messages that have no Received: headers. These seem
to cause ALL_TRUSTED to fire (with a negative score of course), which
isn't exactly what I want. Any idea on how I should deal with this
correctly?
--
Jon Kvebaek <jk...@klanen.no>
Mobil: +47 992 19 829
Unanimiter et constanter Oslo
Re: Messages without received headers and ALL_TRUSTED
Posted by Nick Leverton <nj...@leverton.org>.
On Thu, Dec 15, 2005 at 03:16:22PM +0000, Duncan Hill wrote:
> On Thursday 15 December 2005 15:03, Jon Kvebaek wrote:
> > Hi,
> > we get quite a few messages that have no Received: headers. These seem
> > to cause ALL_TRUSTED to fire (with a negative score of course), which
> > isn't exactly what I want. Any idea on how I should deal with this
> > correctly?
>
> How on earth do you get an e-mail with no received header? At a minimum, your
> own SMTP server should be stamping in a header with where the mail came
> from...
I believe one of the milter setups defaults to calling SA before adding
the Received header. The solution is almost certainly in the list
archives as this is an FAQ (though I don't use milter so I don't know
the answer, apologies).
Nick
Re: Messages without received headers and ALL_TRUSTED
Posted by Duncan Hill <sa...@nacnud.force9.co.uk>.
On Thursday 15 December 2005 15:03, Jon Kvebaek wrote:
> Hi,
> we get quite a few messages that have no Received: headers. These seem
> to cause ALL_TRUSTED to fire (with a negative score of course), which
> isn't exactly what I want. Any idea on how I should deal with this
> correctly?
How on earth do you get an e-mail with no received header? At a minimum, your
own SMTP server should be stamping in a header with where the mail came
from...
Re: Messages without received headers and ALL_TRUSTED
Posted by Matt Kettler <mk...@evi-inc.com>.
Jon Kvebaek wrote:
> Quoting Matt Kettler <mk...@evi-inc.com>:
>
>
>>Jon Kvebaek wrote:
>>
>>>Hi,
>>>we get quite a few messages that have no Received: headers. These
>>
>>seem
>>
>>>to cause ALL_TRUSTED to fire (with a negative score of course),
>>
>>which
>>
>>>isn't exactly what I want. Any idea on how I should deal with this
>>>correctly?
>>>
>>
>>What version of SpamAssassin? I know this was a problem for some
>>releases, but I
>>believe it's fixed in 3.1.0 and 3.0.5.
>
>
> We're currently on SpamAssassin version 3.0.4. I suppose an upgrade
> might be called for.
For reference, here's the bug that was reported about this:
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3949
Basically 3.0.5 has a back-port of the code from 3.1.0, which works a lot better
than the stuff in 3.0.0-3.0.4.
In 3.0.0-3.0.4 ALL_TRUSTED really works as a "no untrusted". Which has problems
if there's errors parsing the Received: headers, or if there's no headers at all.
In 3.0.5 and 3.1.0 you need: one or more trusted, no untrusted, and no unparseable.
Re: Messages without received headers and ALL_TRUSTED
Posted by "Daryl C. W. O'Shea" <sp...@dostech.ca>.
Jon Kvebaek wrote:
> Quoting Matt Kettler <mk...@evi-inc.com>:
>
>> Jon Kvebaek wrote:
>>> Hi,
>>> we get quite a few messages that have no Received: headers. These
>> seem
>>> to cause ALL_TRUSTED to fire (with a negative score of course),
>> which
>>> isn't exactly what I want. Any idea on how I should deal with this
>>> correctly?
>>>
>> What version of SpamAssassin? I know this was a problem for some
>> releases, but I
>> believe it's fixed in 3.1.0 and 3.0.5.
>
> We're currently on SpamAssassin version 3.0.4. I suppose an upgrade
> might be called for.
3.0.5 does include code to not trigger ALL_TRUSTED if it can't parse one
of the received headers, which will help some setups in some cases, but
not many if your own headers are successfully parsed by SA.
> I'll check the milter tip as well.
Before you had said that you were receiving mail without received
headers and someone else mentioned that you may be using a milter that
doesn't at least fake a received header.
Your milter MUST at least fake a received header. If it isn't, this is
what you want to fix.
Daryl
Re: Messages without received headers and ALL_TRUSTED
Posted by Jon Kvebaek <jk...@klanen.no>.
Quoting Matt Kettler <mk...@evi-inc.com>:
> Jon Kvebaek wrote:
> > Hi,
> > we get quite a few messages that have no Received: headers. These
> seem
> > to cause ALL_TRUSTED to fire (with a negative score of course),
> which
> > isn't exactly what I want. Any idea on how I should deal with this
> > correctly?
> >
>
> What version of SpamAssassin? I know this was a problem for some
> releases, but I
> believe it's fixed in 3.1.0 and 3.0.5.
We're currently on SpamAssassin version 3.0.4. I suppose an upgrade
might be called for.
I'll check the milter tip as well.
--
Jon Kvebaek <jk...@klanen.no>
Mobil: +47 992 19 829
Unanimiter et constanter Oslo
Re: Messages without received headers and ALL_TRUSTED
Posted by Matt Kettler <mk...@evi-inc.com>.
Jon Kvebaek wrote:
> Hi,
> we get quite a few messages that have no Received: headers. These seem
> to cause ALL_TRUSTED to fire (with a negative score of course), which
> isn't exactly what I want. Any idea on how I should deal with this
> correctly?
>
What version of SpamAssassin? I know this was a problem for some releases, but I
believe it's fixed in 3.1.0 and 3.0.5.