You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/02/27 13:46:35 UTC

Re: forcing lower score

Mark Martinec writes:
> > "perldoc Mail::SpamAssassin::Conf", look for "whitelist".
> 
> This topic reminds me of my occasional desire to be able to supply
> individual score points (optional, overriding a default) with each
> whitelist_from* and whitelist_from_dkim entry, taking into account
> reputation of each sender, e.g.:
> 
>   whitelist_from_dkim  *@intl.paypal.com  paypal.com  -10
>   whitelist_from_dkim  *@amis.net         amis.net    -20
>   whitelist_from_dkim  *@yahoo.com        yahoo.com   -4.0
>   whitelist_from_dkim  *@yahoo.sg         yahoo.sg    -2.5
>   whitelist_from_dkim  *@gmail.com        gmail.com   -5
> 
> Would such a concept interfere with a custom of supplying
> score points in a 'score' directive only? Any alternative
> syntax approaches?

I like it. 

> In a long run, some more-general 'reputatation' mechanism
> may need to be invented.

whitelist_auth?  SpamAssassin 3.2.0 has a new setting:

    whitelist_auth      *@intl.paypal.com 

which applies to any/all of SPF/DK/DKIM/future methods, whichever
may fire first.

Maybe the best approach is to add this score system to just
whitelist_auth, and not the "legacy" individual whitelistings.

--j.