ALL_TRUSTED problems

Richard Edge Edge at
Thu Feb 2 01:08:58 GMT 2006

Nope, it gives no errors there either. With the -D option is gives me
the same information as previous. Another odd thing is that -D --lint
seems to respond to changes of "use_pyzor 0" to "use_pyzor 0" and back
as does "use_dcc 0" to "use_dcc 1". The -D --lint turns these functions
off and on as they should but I don't see any reference to these tests
in the maillog either.  

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 Glenn
Sent: Wednesday, February 01, 2006 4:41 PM
To: MailScanner discussion
Subject: Re: ALL_TRUSTED problems

On 01/02/06, Richard Edge <Edge at> wrote:
> If I change the line:
> To:
> Then the output from "spamassassin -p /etc/mail/ --lint"
> gives me a:
> [22778] warn: config: failed to parse line, skipping: core ALL_TRUSTED

> 0 [22778] warn: lint: 1 issues detected, please rerun with debug 
> enabled for more information
<me grasping at straws:-)>
Um, does it carp if you don't specify "-p /etc/mail/ "
too? You shouldn't need use it as a preference file</me grapsing at
straws:-)> anymore, since it should be part of the site rules... A plain
"spamassassin --lint" should suffice.
</me grasping at straws:-)>

-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se
MailScanner mailing list
mailscanner at

Before posting, read

Support MailScanner development - buy the book off the website! 

More information about the MailScanner mailing list