Arvinn Løkkebakken wrote:
> I aggree, and this is probably the reason most of the times. I just
> felt it was necessary to comment on your *never*. It_is_likely that
> ALL_TRUSTED will misfire as long as it trusts unparseable headers
> containing whatever IP-addresses. Generally we should acknowle
apache.org'
> Subject: Re: negative score from ALL_TRUSTED
>
> At 09:07 AM 3/31/2005, Arvinn Løkkebakken wrote:
>
> >>You have a broken trust path. ALL_TRUSTED should *never*
> match email
> >>from outside your network.
> >>
&
Matt Kettler wrote:
At 09:07 AM 3/31/2005, Arvinn Løkkebakken wrote:
You have a broken trust path. ALL_TRUSTED should *never* match email
from outside your network.
But it does anyway, even when trust path is set correctly:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Hmm. Well, that h
At 09:07 AM 3/31/2005, Arvinn Løkkebakken wrote:
You have a broken trust path. ALL_TRUSTED should *never* match email
from outside your network.
But it does anyway, even when trust path is set correctly:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Hmm. Well, that happens if and only if
Matt Kettler wrote:
You have a broken trust path. ALL_TRUSTED should *never* match email
from outside your network.
But it does anyway, even when trust path is set correctly:
http://bugzilla.spamassassin.org/attachment.cgi?id=2508
Happens when spamassassin fails to parse the Received header(s)
ROY,RHETT G wrote:
> I just had a spam get through with a negative score from ALL_TRUSTED.
>
> # The message was never sent via an untrustworthy host.
> header ALL_TRUSTED eval:check_all_trusted()
> describe ALL_TRUSTEDDid not pass through any untrusted hosts
> tflags ALL_TRUSTED n
