------ Original Message ------
Received: Tue, 15 Feb 2005 01:21:21 AM EST
From: Robert Menschel <[EMAIL PROTECTED]>
To: FH <[EMAIL PROTECTED]>Cc: users@spamassassin.apache.org
Subject: Re[2]: Care and feeding instructions for SpamAssassin?


> Next time you get one of those spam that sneaks through, run
> > spamassassin -D <email >output 2>debug.out

There must be a disconnect somewhere. I just did this w/ a "drugs online" spam
I just received.  When it first came in it had a rating of 1.9, I saved it as
a file (not an mbox) on the server and ran the above command and it reported a
12.5!!!  After running sa-learn on the mbox I saved the email to it didn't
change anything (the above still reported a 12.5).  I then "bounced" the
message back to myself and when it hit the incoming mailbox again this time it
was autolearned as ham and rated as 0.4.  Running it back through the above
command again that only scored a 7.9 :( ?!?

So just to double check I'm doing this right:

- Mail comes in to the server and is picked up by postfix (running as
postfix).
- It's passed off to procmail via "mailbox_command = /bin/procmail" in the
postfix/main.cf file.
- Procmail calls spamc which passed off the mail to spamd (running as spamd
and started via an init.d script that runs "spamd -d -u spamd" at startup).
- That runs it through spamassassin and marks it up if appropropriate and then
dumps it into the mailbox.
- Not getting into what the other users are doing, if I get an unmarked spam I
save it to a mailbox (I use [PC-]Pine btw in case that makes a difference) and
occasionally run "sa-learn --showdots --spam --mbox spam" as root on that
file.

This is how it's supposed to work right?  I did a "find" for journal, seen and
toks and only came back w/ those in the expected place
(/var/spool/spamassassin).  The only other spamassassin files I found that
looked "out of place" (aka not the config file or the share/rules files) were
in the ~root/.spamassassin

drwx------   2 root     other        512 Feb 14 14:18 ./
drwxr-xr-x  13 root     other        512 Feb 15 15:42 ../
-rw-------   1 root     other      24576 Feb 15 18:09 auto-whitelist
-rw-------   1 filter   filter         0 Dec 25 09:45 auto-whitelist.dir
-rw-------   1 root     other          6 Feb 15 18:09 auto-whitelist.mutex
-rw-------   1 filter   filter      1024 Dec 25 09:45 auto-whitelist.pag
-rw-------   1 root     other         58 Jan  4 14:52 bayes.lock
-rw-------   1 root     other       2030 Jan  4 11:02
bayes.lock.OLD.MACHINE.NAME.2623
-rw-------   1 root     other       4292 Jan  4 14:59
bayes.lock.OLD.MACHINE.NAME.4734
-rw-------   1 root     other         58 Jan  4 14:59
bayes.lock.OLD.MACHINE.NAME.4739
-rw-------   1 root     other         29 Jan  4 15:00
bayes.lock.OLD.MACHINE.NAME.4743
-rwx------   1 root     other       1175 Dec 24 23:52 user_prefs*

The OLD.MACHINE.NAME is the name of the server while I was setting it
up/testing it, it's something different now.  The user_prefs file has
essentially nothing in it (it's all #d out).  

Any hints clues suggestions are appreciated.
Thanks


Reply via email to