On Mon, 2004-03-01 at 03:06, Bob Mortimer wrote:
> On Sunday 29 Feb 2004 11:11 pm, Bill Randle wrote:
>
[snip]
> > Also, when it runs, you'll see log entries like this ($log_level = 2):
> >
> > Feb 29 15:01:19 filter amavis[13571]: (13571-01) spam_scan: hits=23.422
> > tests=BANG_MORE,BAYES_99,DCC_CHECK,FVGT_b_GVR,FVGT_m_IMAGE_ONLY_SPAM,
> > FVGT_s_VIAGRI,HTML_50_60,HTML_IMAGE_ONLY_02,HTML_MESSAGE,LOCAL_DRUGS_DIET,
> > LOCAL_DRUGS_SLEEP,MRWIGGLY,RM_st_iso8859,T_NUM_IN_DOMAIN_4,T_NUM_IN_DOMAIN_
> >46, T_NUM_IN_DOMAIN_6
>
> Yes, also found these entries. My amavisd.conf is (I thought!) set up to just
> pass the mail on. but I thought it should be adding the X-Spam-Status:
> header, which it isn't. I'll try reverting back to delivering to a different
> address or quarantining spam.
In your amavisd.conf file, set $sa_tag_level_deflt to -99.0 to get
the X-Spam-Status header added to all emails.
> >From looking at all this it looks like amavisd doesn't use spamd but uses
> >the
> the Mail::SpamAssassin module which I thought was slower. Also passing direct
> from amavisd to spamassassin loses the ability to use a local config file for
> SA (apart from the options in amavisd.conf).
It's not slower because amavisd preloads the SpamAssassin module once at
startup,
similar to what spamd does. The performance hit comes when loading the
SA module for each messages.
You can still have a local.cf and user_prefs file even when amavisd is
used. Just put user_prefs in a .spamassassin directory under amavisd's
home directory (the same place your bayes databases are). For instance,
on my system:
# ls -l /var/lib/amavis/.spamassassin
total 20588
-rw-r----- 1 amavis amavis 37134 Mar 1 07:48 bayes_journal
-rw-r----- 1 amavis amavis 20934656 Mar 1 07:48 bayes_seen
-rw------- 1 amavis amavis 4521984 Mar 1 07:48 bayes_toks
-rw-r----- 1 amavis amavis 762 Jan 18 11:32 user_prefs
What you don't get (any maybe this is what you were alluding to) is
per user preferences.
-Bill