Setup: OS Redhat Linux
Spamassassin 2.20 Running in spamd/spamc
mode through procmail(sendmail)
Still experimenting with getting my setup pretty close to a good
working config, but suddenly ran into some problems I'm having trouble
debugging.
spamd is started like this:
spamd -d -D -L -S
Procmail entry looks like this:
UL=/usr/local/bin
:0fw
| $UL/spamc
:0:
* ^X-Spam-Status: Yes
spam_a1.in
All seems to be working and I see mail going thru and getting marked
up. Some being sent to spam file and others going thru as expected.
All my edited configs are in /etc/mail/spamassassin/local.cf.
And I see evidence that it is being read by some of the scores I've
edited showing up in mail coming thru.
Now the part I can't get a good clue about:
Two of my edited rules are being ignored. I've restarted spamd
several times so thats not the issue.
I see no debug output that indicates a problem. I'm watching syslog
and catching every thing with `spamd' in it.
So my first question is where should I be looking for the debug
output? I've made no effort to direct it anywhere so it should be
defaulting to syslog shouldn't it? Or at least it should show up in
procmail.log, which is set to verbose.
Just to make real sure, here is the output of ps waux|grep spamd
root 4166 0.0 2.0 8444 2604 ? S 01:46 0:00 \
/usr/local/bin/perl /usr/local/bin/spamd -d -D -L -S
I'm not sure if the perl part was always in there. Is it normal?
I'm not getting any spamd debug output I can find other than some
syslog messages that appear NOT to be from the -D (debug) flag.
Things like:
May 31 01:50:11 reader spamd[4496]: clean message (0.0/2.0) for
reader:502 in 1 seconds.
May 31 02:00:05 reader spamd[4166]: connection from localhost [
127.0.0.1 ] at port 4029
Going back to the sandbox and running this same setup but in
spamassassin mode instead of spamd/spamc, I get nice debug messages in
procmail.log tha look like (in part):
[...]
debug: using "/usr/local/share/spamassassin" for default rules dir
debug: using "/etc/mail/spamassassin" for site rules dir
debug: using "/home/reader/.spamassassin" for user state dir
debug: using "/home/reader/.spamassassin/user_prefs" for user prefs file
debug: running header regexp tests; score so far=0
Failed to run header SpamAssassin tests, skipping some: syntax error
at (eval 6) line 11, near ") ~"
syntax error at (eval 6) line 19, near ") ~"
syntax error at (eval 6) line 568, near ";
}"
[...]
This looks like my problem but why am I not seeing any of this in
spamd/spamc mode? And even more important, how does one tell what
these `lines' refer to? What script is it a reference too? Shouldn't
there be something in the error messages that would stand some chance
of leading an investigator to the scene of the problem?
Seems pretty likely to be something in my edited rules which I've
included below. Two of them are being totally ignored. The virus
scan rule and texi list rule:
cat /etc/mail/spamassassin/local.cf
required_hits 2
auto_report_threshold 6000
score FROM_AND_TO_SAME 1.7
score Virus_scan_report 1.5
header Virus_scan_report Subject =~ /Virus found .* message/i
score CRON -100
header CRON X-Cr)on-Env =~ /\w/
score Default_score_texi_list 0.6
header Default_score_texi_list Sender =~ /owner-tex.*\@mathematic/
score FORGED_YAHOO_RCVD 1.45
score NO_REAL_NAME 0.53
score COPY_DVDS 1.8
score Repeat_Allcap_Free 1.5
body Repeat_Allcap_Free /FREE.*FREE/
score SLIGHTLY_UNSAFE_JAVASCRIP 1.5
score MSG_ID_ADDED_BY_MTA_2 1.3
score CRON -100
header CRON X-Cron-Env /\w/
score FW_LOG -100
header FW_LOG Subject /\[0030AB066D5C\]/
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
