ALL_TRUSTED problems

Richard Edge Edge at
Thu Feb 2 19:08:02 GMT 2006

In my situation, I am already at SA 3.1.0. Should I try something
drastic like uninstalling SA and doing a new install or forcing an
install over the existing installation. If so what is the best way to

Richard Edge
Senior Systems Administrator | Technology Services
Trinity Western University | t: 604.513.2089
f: 604.513.2038 | e: edge <at>| 

-----Original Message-----
From: mailscanner-bounces at
[mailto:mailscanner-bounces at] On Behalf Of Matt
Sent: Thursday, February 02, 2006 10:34 AM
To: MailScanner discussion
Subject: Re: ALL_TRUSTED problems

Scott Silva wrote:
> dnsadmin spake the following on 2/2/2006 8:08 AM:
>> At 07:59 PM 2/1/2006, you wrote:
>> debug: SpamAssassin version 3.0.3
>> Thanks,
>> Glenn Parsons
> Have you considered upgrading to spamassassin 3.1.0?

Or at least upgrade to 3.0.5. All other version of SA 3.0 have MAJOR
bugs in the ALL_TRUSTED code. 3.0.5 has a back-port of 3.1.0's
algorithm, which deals better with parsing problems.

3.0.0-3.0.4 - ALL_TRUSTED = no untrusted relays.

3.0.5-3.1.0 - ALL_TRUSTED = at least 1 trusted relay, no untrusted
relays and no unparseable relays.

The version in 3.0.0-3.0.4 will false-fire with ALL_TRUSTED if there are
no parseable headers.
MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website! 

More information about the MailScanner mailing list