I need something more scalable then this (Ie: all Postfix email address
information is currently stored in MySQL db).
Besides it worked before so I don't understand what is happening now.
I'm wondering if it's a bug or an over zelous rule in the latest Spam
Assassin.
> You could alternately work around the problem by using soft whitelisting.
> In amavisd.conf-sample is a section @score_sender_maps. Use that
> example (if you don't have this already in amavisd.conf you could copy
> the example there) and insert your sender there.
>
> Then simply give ths sender a negative score of a few points.
>
> @score_sender_maps = ({ # a by-recipient hash lookup table
>
> #stuff
>
> '.' => [ # the _first_ matching sender determines the score boost
>
> { # a hash-type lookup table (associative array)
> '[EMAIL PROTECTED]' => -4.0,
> '[EMAIL PROTECTED]' => -3.0,
> '[EMAIL PROTECTED]' => -3.0,
> },
>
> #stuff
>
> ], # end of site-wide tables
> });
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
AMaViS-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
