message is spam because it was sent from mailscanner...

[Furnish, Trever G]

> -----Original Message-----
> From: mailscanner-bounces at lists.mailscanner.info 
> [mailto:mailscanner-bounces at lists.mailscanner.info] On Behalf 
> Of Matt Kettler
> Sent: Friday, March 02, 2007 6:01 PM
> To: MailScanner discussion
> Subject: Re: message is spam because it was sent from mailscanner...
> 
> 
> Matt Kettler wrote:
> > Perhaps you should update your SA rules.
> > 
> > The current set of rules from sa-update has had INFO_TLD removed..
> > 
> 
> For further reference, this appears to have happened 
> somewhere between update
> 487253 published 12/15/2006, and 488380, published 12/19/2006.
> 
> Note that even though SpamAssassin 3.1.8 was published after 
> this change, it still contains more-or-less the original 
> 3.1.0 ruleset, with only the more serious bugfixes in it.

Hmmm.  Thanks for the info.  My last rules update was just the rules,
updated using sa-update, on February 13th.  That was also my *first* use
of sa-update -- had been doing full SA rip-out-and-replace upgrades
before then -- so I perhaps I missed something. :-(

Here are my versions:
[root at relay2 sysadm]# spamassassin --version
SpamAssassin version 3.1.3
  running on Perl version 5.8.0

[root at relay2 sysadm]# sa-update --version
sa-update version svn408695
  running on Perl version 5.8.0

I'll run another sa-update and then go looking for INFO_TLD.  I needed
to get in and find X_IP today regardless -- had a few ham hitting that
and I'm not finding much info on why the presence of an X-IP header
merits such a high score contribution.