Hi all,
I recently installed SA on a mail server, only applying globally right now -- no individual user configurations. I've discovered that when I add "whitelist_from ..." entries to the local.cf file, SA let's spam in that is marked above the hit threshold. With the entries removed from the file, such spam is blocked again. Perhaps I'm missing something, or putting the whitelist_from entries in the wrong file. Anyway, I'd appreciate your help. I've included a copy of the local.cf below.
skip_rbl_checks 1 required_hits 5.0 auto_report_threshold 30 rewrite_subject 0 report_header 1 use_terse_report 1 defang_mime 0 dns_available yes razor2_add_header 1 use_razor2 1 ok_languages all
(The whitelist from entries, when in the file, follow like this)
whitelist_from [EMAIL PROTECTED] whitelist_from [EMAIL PROTECTED] [...]
1) what ancient version are you running? auto_report_threshold has been dead since something like 2.31. Please if you have a version of SA that is old enough to have this feature set it to something insane like 900. This feature was removed from SA at the explicit request of the razor developers, as auto-reporting using SA is technically poison to the razor database. If your version is recent, get rid of the unsupported commands.
2) Your statement that it "lets through spam above the threshold" seems strange.. whitelist_from only affects the score of a message, it should not affect anything else.
I suspect you really have a situation where your configfile is invalid.. is your version new enough to support --lint (2.40 or newer)??. if so, run spamassassin --lint and look at the output..
if it's really older than 2.40, my only recommendation is to upgrade first, and use --lint to fix your config...
Running anything so absurdly old as 2.2x or 2.3x is irresponsible administration, if for no other reason than any bugs which corrupt mail that have been fixed in the past year (and yes there have been some) aren't in your system. I'm not a strict proponent of "upgrade as soon as a new version is out" but I am a proponent of "upgrade anytime the a newer version appears to be stable and well tested".. The scoreset for SA "ages" and becomes less effective as time goes on, and bugs appear and get fixed so you cannot treat SA as an "install once run forever" product.
For example, one potential mail-loss causing bug that was fixed in 2.43: 2002-10-14 17:48 jmason
* spamd/: libspamc.c, libspamc.c: bug 1107: spamc with -e could
lose mail if spamd was down. fix by anomie
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
