If you're not using sql prefs, I think you'd need put a similar entry in Section V of the config (before the whitelist/blacklist area of that subsection).
Ryan Moore ---------- Perigee.net Corporation 704-849-8355 (sales) 704-849-8017 (tech) www.perigee.net
Jonathan Nichols wrote:
Ryan Moore wrote:
Your postfix isn't stripping them right? I use amavisd-new and it works like a charm. I do have $sa_tag_level_deflt set to -999, so it adds headers to every email, but $sa_tag2_level_deflt and $sa_kill_level_deflt are set to 7. I think the default for just $sa_tag is 0, so a plain test message will likely score below 0 and not get any headers added.
Gah, I HOPE this doesn't make this message into HTML - I'm trying out Mozilla Thunderbird for the first time. If it makes it HTML, screw it, I'll use Pine again. :P
here's the SA section of my /etc/amavisd.conf:
# Turn on SpamAssassin debugging (output to STDERR, use with 'amavisd debug')
$sa_debug = 0; # defaults to false
# SpamAssassin settings
# $sa_local_tests_only is passed to Mail::SpamAssassin::new as a value # of the option local_tests_only. See Mail::SpamAssassin man page. # If set to 1, no tests that require internet access will be performed. # $sa_local_tests_only = 1; # (default: false) #$sa_auto_whitelist = 1; # turn on AWL (default: false)
$sa_mail_body_size_limit = 64*1024; # don't waste time on SA if mail is larger
# (less than 1% of spam is > 64k)
# default: undef, no limitations
#default values, can be overridden by more specific lookups, e.g. SQL
$sa_tag_level_deflt = -999.0; # add spam info headers if at, or above that level
$sa_tag2_level_deflt = 5.0; # add 'spam detected' headers at that level
#$sa_kill_level_deflt = $sa_tag2_level_deflt; # triggers spam evasive actions
# at or above that level: bounce/reject/drop,
# quarantine, and adding mail address extension
# The $sa_tag_level_deflt, $sa_tag2_level_deflt and $sa_kill_level_deflt
# may also be hashrefs to hash lookup tables, to make static per-recipient
# settings possible without having to resort to SQL or LDAP lookups.
# a quick reference: # tag_level controls adding the X-Spam-Status and X-Spam-Level headers, # tag2_level controls adding 'X-Spam-Flag: YES', and editing Subject, # kill_level controls 'evasive actions' (reject, quarantine, extensions); # it only makes sense to maintain the relationship: # tag_level <= tag2_level <= kill_level
# string to prepend to Subject header field when message exceeds tag2 level
$sa_spam_subject_tag = '***SPAM***'; # (defaults to undef, disables)
# (only seen when spam is not to be rejected
# and recipient is in local_domains*)
#$sa_spam_modifies_subj = 1; # may be a ref to a lookup table, default is true
# Example: modify Subject for all local recipients except [EMAIL PROTECTED] #$sa_spam_modifies_subj = [qw( [EMAIL PROTECTED] . )]; $sa_spam_modifies_subj = 0;
#-------------
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
