You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Ryan Dlugosz <ry...@dlugosz.net> on 2004/09/28 22:14:41 UTC

everything autolearn=spam after 3.0 upgrade?

Hello -

Just recently noticed that all of the mail coming through my system has the
"autolearn=spam" tag in the SA header.  I run SA through MailScanner and had
been using 2.64 previous to 3.0.  I recently noticed an increase in spam that
has been getting through, and after some investigation saw that most messages,
regardless of their SA score, were getting autolearned=spam.

Now, the kind of strange part is that I added bayes_auto_learn 0 and then even
use_bayes 0 to my config.  The autolearn message is still appearing though...
seems like something about my config didn't jive with the upgrade.

Any thoughts as to where to look?  I'm afraid to turn the bayes stuff back on
if it's training improperly...  Here's an interesting line from the logs that
demonstrates what I'm talking about:

Sep 28 16:01:07 vps MailScanner[12314]: Message 1CCO9p-000831-Kx from
209.237.227.199 (HIDDEN@spamassassin.apache.org) to dlugosz.net is not spam,
SpamAssassin (score=0.05, required 6.5, autolearn=spam, FORGED_RCVD_HELO 0.05)


Thanks for any suggestions.
-Ryan

-- 
Ryan Dlugosz
ryan@dlugosz.net

http://dlugosz.net


Re: DNS-related tests don't seem to be working

Posted by Tom Yates <ma...@teaparty.net>.
On Tue, 28 Sep 2004, Tom Yates wrote:

> i've just upgraded to SA 3.0.0 (thanks, theo) on a RH9 box, and 
> effectiveness has dropped from <1% false negatives to about 5% false 
> negatives.  looking at the output, it suggests that DNS-related tests 
> (specifically SPF, but i also suspect the various blacklist tests) 
> aren't working.

in case anyone's searching the archives for a similar problem, the issue 
was the Net::DNS was too old a version.  this showed up when i ran 
"spamassassin -D" against a piece of unfiltered spam, and got output which 
included:

debug: Net::DNS version is 0.31, but need 0.34

to get SA working fully, including SPF tests, it was necessary to get from 
CPAN, build, and install the following modules:

Net-DNS-0.48.tar.gz
Mail-SPF-Query-1.997.tar.gz
Net-CIDR-Lite-0.15.tar.gz

(for those even less experienced than me: download, tar xvzf to unpack, cd 
to the new directory, perl Makefile.PL && make && make install).  don't 
forget to restart spamd afterwards.

doubtless later versions, and possibly earlier ones, would have done just 
as well, but this is what i used, and this is what works for me.  SA is 
back to <1% false negatives, and i'm ecstatic again.

thanks to all the SA developers - you rock!


-- 

   Tom Yates
   Cambridge, UK.

DNS-related tests don't seem to be working

Posted by Tom Yates <ma...@teaparty.net>.
i've just upgraded to SA 3.0.0 (thanks, theo) on a RH9 box, and 
effectiveness has dropped from <1% false negatives to about 5% false 
negatives.  looking at the output, it suggests that DNS-related tests 
(specifically SPF, but i also suspect the various blacklist tests) aren't 
working.

i've fed it a piece of false-negative spam which i know (from the email 
header checker at spftools.infinitepenguins.net) should definitely give a 
softfail, and yet the SA headers make no reference to this test at all.

i'm putting some of the output of spamd -D below; there an awful lot, but 
i can send the whole lot if someone's willing to plough through it!

any light anyone can shed on what's going on - are all DNS-related tests 
really being skipped, and if so, why? - will be gratefully received.



debug: config: read file /usr/share/spamassassin/10_misc.cf
debug: config: read file /usr/share/spamassassin/20_anti_ratware.cf
debug: config: read file /usr/share/spamassassin/20_body_tests.cf
debug: config: read file /usr/share/spamassassin/20_compensate.cf
debug: config: read file /usr/share/spamassassin/20_dnsbl_tests.cf
debug: config: read file /usr/share/spamassassin/20_drugs.cf
debug: config: read file /usr/share/spamassassin/20_fake_helo_tests.cf
debug: config: read file /usr/share/spamassassin/20_head_tests.cf
debug: config: read file /usr/share/spamassassin/20_html_tests.cf
debug: config: read file /usr/share/spamassassin/20_meta_tests.cf
debug: config: read file /usr/share/spamassassin/20_phrases.cf
debug: config: read file /usr/share/spamassassin/20_porn.cf
debug: config: read file /usr/share/spamassassin/20_ratware.cf
debug: config: read file /usr/share/spamassassin/20_uri_tests.cf
debug: config: read file /usr/share/spamassassin/23_bayes.cf
debug: config: read file /usr/share/spamassassin/25_body_tests_es.cf
debug: config: read file /usr/share/spamassassin/25_hashcash.cf
debug: config: read file /usr/share/spamassassin/25_spf.cf
debug: config: read file /usr/share/spamassassin/25_uribl.cf
debug: config: read file /usr/share/spamassassin/30_text_de.cf
debug: config: read file /usr/share/spamassassin/30_text_fr.cf
debug: config: read file /usr/share/spamassassin/30_text_nl.cf
debug: config: read file /usr/share/spamassassin/30_text_pl.cf
debug: config: read file /usr/share/spamassassin/50_scores.cf
debug: config: read file /usr/share/spamassassin/60_whitelist.cf
debug: using "/etc/mail/spamassassin" for site rules dir
debug: config: read file /etc/mail/spamassassin/local.cf
debug: plugin: loading Mail::SpamAssassin::Plugin::URIDNSBL from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x83cbad8)
debug: plugin: loading Mail::SpamAssassin::Plugin::Hashcash from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::Hashcash=HASH(0x8b92248)
debug: plugin: loading Mail::SpamAssassin::Plugin::SPF from @INC
debug: plugin: registered Mail::SpamAssassin::Plugin::SPF=HASH(0x8b703a0)
[...]
debug: received-header: 'from' 127.0.0.1 has reserved IP
debug: received-header: cannot use DNS, do not trust any hosts from here on
debug: received-header: relay 127.0.0.1 trusted? yes internal? no
[...]
debug: is spam? score=-3.1 required=4
debug: tests=ALL_TRUSTED,BAYES_50,HTML_30_40,HTML_MESSAGE,MIME_HTML_ONLY
debug: subtests=__CT,__CTE,__CTYPE_HTML,__HAS_MSGID,__HAS_SUBJECT,__HAS_X_MAILER,__HAS_X_PRIORITY,__MIME_HTML,__MIME_VERSION,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__SANE_MSGID,__TAG_EXISTS_BODY,__TAG_EXISTS_HTML
logmsg: clean message (-3.1/4.0) for madhatta:500 in 3.7 seconds, 2119 bytes.
logmsg: result: . -3 - ALL_TRUSTED,BAYES_50,HTML_30_40,HTML_MESSAGE,MIME_HTML_ONLY scantime=3.7,size=2119,mid=<05...@risby.gatekeeper.ltd.uk>,bayes=0.500000000434935,autolearn=ham


-- 

   Tom Yates
   Cambridge, UK.

Re: everything autolearn=spam after 3.0 upgrade?

Posted by Ryan Dlugosz <ry...@dlugosz.net>.
Ryan Dlugosz said:
> Michele Neylon : Blacknight Solutions said:
>> Which version of MailScanner are you using?
>> The more recent releases have been patched to address this anomaly
>
> Hm... I've got mailscanner-4.31.6-1

FYI - upgrading to the latest stable MailScanner (4.33.1) resolved my issues. 
Thanks to Michele for the help!

-Ryan

-- 
Ryan Dlugosz
ryan@dlugosz.net

http://dlugosz.net


Re: everything autolearn=spam after 3.0 upgrade?

Posted by Ryan Dlugosz <ry...@dlugosz.net>.
Michele Neylon : Blacknight Solutions said:
> Which version of MailScanner are you using?
> The more recent releases have been patched to address this anomaly

Hm... I've got mailscanner-4.31.6-1

I could update this evening to the more recent version, but it seems like this
isn't something that MailScanner is doing... doesn't that output come from SA?


-- 
Ryan Dlugosz
ryan@dlugosz.net

http://dlugosz.net


Re: everything autolearn=spam after 3.0 upgrade?

Posted by "Michele Neylon : Blacknight Solutions" <mi...@blacknightsolutions.com>.
On Tue, 2004-09-28 at 16:14 -0400, Ryan Dlugosz wrote:
> Hello -
> 
> Just recently noticed that all of the mail coming through my system has the
> "autolearn=spam" tag in the SA header.  I run SA through MailScanner and had
> been using 2.64 previous to 3.0.  I recently noticed an increase in spam that
> has been getting through, and after some investigation saw that most messages,
> regardless of their SA score, were getting autolearned=spam.
> 
> Now, the kind of strange part is that I added bayes_auto_learn 0 and then even
> use_bayes 0 to my config.  The autolearn message is still appearing though...
> seems like something about my config didn't jive with the upgrade.
> 
> Any thoughts as to where to look?  I'm afraid to turn the bayes stuff back on
> if it's training improperly...  Here's an interesting line from the logs that
> demonstrates what I'm talking about:
> 
> Sep 28 16:01:07 vps MailScanner[12314]: Message 1CCO9p-000831-Kx from
> 209.237.227.199 (HIDDEN@spamassassin.apache.org) to dlugosz.net is not spam,
> SpamAssassin (score=0.05, required 6.5, autolearn=spam, FORGED_RCVD_HELO 0.05)

Which version of MailScanner are you using?
The more recent releases have been patched to address this anomaly

-- 
Mr Michele Neylon
Blacknight Solutions
http://www.blacknight.ie
059 9137101


-- 
Email scanned by Blacknight for viruses and dangerous content.
Visit http://www.blacknight.ie for more information