Raphael Clifford wrote:
Daryl C. W. O'Shea wrote:
Actually, SpamAssassin 3.0.3 can't parse the first received header
either, due to the @ in front of the IP. Even if you were to set
trusted_networks all trusted would fire and there'd be no RBL lookups
etc.
Daryl
I think that is exactly r
Daryl C. W. O'Shea wrote:
Loren Wilton wrote:
I am not NAT'ed so I can see no reason why it is ALL_TRUSTED
I think I can:
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 19588 invoked from network); 20 May 2005 22:45:07 +0100
Received: from 82-35-6-77.cable.ubr01.hari.blueyonder.co.uk
(@
Loren Wilton wrote:
I am not NAT'ed so I can see no reason why it is ALL_TRUSTED
I think I can:
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 19588 invoked from network); 20 May 2005 22:45:07 +0100
Received: from 82-35-6-77.cable.ubr01.hari.blueyonder.co.uk (@82.35.6.77)
by secure.roshan.
I'm not sure why your score is changing, since the list of hit tests seems
to be the same. Two points though:
> (command "spamassassin spam.txt")
I had always thought it was "spamassassin I am not NAT'ed so I can see no reason why it is ALL_TRUSTED
I think I can:
> Delivered-To: [EMAIL PROTEC
I have a spam message (attached below) which is causing all kinds of
problems. The first is that the score is
(command "spamassassin spam.txt")
X-Spam-Status: No, score=-4.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=unavailable version=3.0.3
I am not NAT'ed so I can see no reason
