dnsadmin at 1bigthink.com
Thu Feb 2 20:02:35 GMT 2006
At 02:48 PM 2/2/2006, you wrote:
>Richard Edge spake the following on 2/2/2006 11:08 AM:
> > 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
> > proceed.
> > Richard Edge
> > Senior Systems Administrator | Technology Services
> > Trinity Western University | t: 604.513.2089
> > f: 604.513.2038 | e: edge <at> twu.ca| www.twu.ca/technology
> > -----Original Message-----
> > From: mailscanner-bounces at lists.mailscanner.info
> > [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf Of Matt
> > Kettler
> > Sent: Thursday, February 02, 2006 10:34 AM
> > To: MailScanner discussion
> > Subject: Re: ALL_TRUSTED problems
> > Scott Silva wrote:
> >> dnsadmin 1bigthink.com 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.
> > --
>This thread has gotten very confusing! I take it there are 2 people with a
>similar problem, but more than likely 2 different solutions.
>I had a problem with a spamassassin install sometime back where it was
>defaulting to looking for its rules in /usr/etc/mail/spamassassin. It took
>days to track this down. If you have this problem, I fixed it with a symlink
>from /usr/etc/mail/spamassassin pointing to /etc/mail/spamassassin. Maybe way
>off, but a guess s all I have...
I could see how you got confused with this thread..
Richard started with a problem that does not seem to be solved..
that's him still scratching his head over there! His version of
MailScanner and SpamAssasin are either current or a late Beta of the
current 4.50 release.
We were both having problems with ALL_TRUSTED firing in the SA
reports, but for different reasons.
Matt resolved my problem with his last post: My SpamAssassin version
is not only a bit old, but has known bugs that fire the ALL_TRUSTED
rule in the way that I had observed.
Thanks ever so much again, ALL!
MailScanner/SpamAssassin upgrade on Saturday, so hopefully I can
watch the Superbowl undistracted on Sunday!
More information about the MailScanner