amavisd-new, mailscanner, and several other tools that call SA directly don't actualy use the output of SA.. They add the tags and such themselves, so these are settings you need to set in the config for the tool calling spamassassin, not spamassassin itself.
For amavisd-new you probably want to use tag_level and kill_level to get the effect of "always_add_report".
At 03:31 PM 3/19/2003 -0500, Pete O'Hara wrote:
Hi,
I am calling the Spamassassin modules directly from amavsd-new run as a content filter via Postfix (not running spamd). I have read Mail::SpamAssassin::Conf and a couple of other sources and haven't come up with the answers. What I am seeing is that score settings in /etc/mail/spamassassin/local.cf are taking effect but the other settings such as
always_add_report 1 report_safe 0 clear_report_template report _SUMMARY_ rewrite_subject 1 subject_tag **SPAM** hits:_HITS_ reqd:_REQD_
not taking affect on local users that do not call /usr/sbin/spamassassin via procmailrc. Is this the expected behaviour or is there something wrong with my configuration? Feel free to RTFM if this is obvious stuff :)
TIA, Pete
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
