Console error messages...

Matt Kettler mkettler at EVI-INC.COM
Fri Jan 24 20:02:23 GMT 2003

Agreed, MS calls the SpamAssassin API directly and doesn't call spamc/spamd
or the command-line spamassassin.

Looks like he's also got some kind of procmail deal calling spamc/spamd.
Whoops.. probably don't want to run SA twice on your mail :)

In any event, those messages would imply that he's got typoes, probably
small ones with bad side effects, in his spamassassin config. Typically
things like forgetting a / at the end of a regex does this.

My solution for keeping my ruleset clean and well checked is to use a
symlink root's /root/.spamassassin/user_prefs to the MailScanner
spam.assassin.prefs.conf file, this way I can always lint the same rules
MailScanner is using when I run spamassassin on the command line as the
root user.

I never, ever, edit a spamassassin config without linting it afterwards..
the silliest typos can make half your ruleset be ignored.

spamassassin --lint -LD

This should not complain about having to skip rules, if it does, check what
you just changed.

At 07:42 PM 1/24/2003 +0000, Julian Field wrote:
>>RH 7.3 w/sendmail 8.11.6
>>My console messages get written to /var/log/maillog ok
>>/var/log/maillog.3:Jan  4 15:46:19 smithers spamd[628]: Failed to run
>>header SpamAssassin tests, skipping some: syntax error
>>at (eval 16) line 75, near ") ~" syntax error at (eval 16) line 81, near
>>") ~" syntax error at (eval 16) line 147, near ") ~" syntax error at
>>(eval 16) line 150, near "}       }"
>But MailScanner doesn't use spamd... (it works faster than that)

More information about the MailScanner mailing list