On Wed, 17 Sep 2014 11:50:43 +0200
Reindl Harald wrote:
> what i want to achieve is 4 levels of negative score for
> both - FROM and TO just because it makes sense to handle
> some mailing lists different without whitelist them completly
> and the same for different RCPT, one user is living in asia
> and needs complete different settings
>
> there is also a need to handle "securityfocus" ML different
> to "postfix-users" without completly whitelist them
A lot of people don't put mailing lists through Spamassassin, most of
them have already been spam filtered, and to get the best results you
have to extend your internal network and maintain it. And in my
experience most list related spam is off-list anyway.
> finally offer in the existing webinterface (self-written) a drop-down
> for each listed address/domain as well as define the score for each
> level in the general settings to adjust
>
> as usal the cronjob builds "local.cf" from a template and that
> settings
If you are going to autogenerate them into local.cf you can generate
header rules just as easily. The chief advantage of what you are
asking for would be for users to set in ~/.spamassassin.
> score USER_IN_MOST_SPAM_FROM -4
> header USER_IN_MOST_SPAM_FROM
> eval:check_from('USER_IN_MOST_SPAM_FROM')
>
> score USER_IN_ALMOST_ALL_SPAM_FROM -6
> header USER_IN_ALMOST_ALL_SPAM_FROM
> eval:check_from('USER_IN_ALMOST_ALL_SPAM_FROM')
The terminology seems a bit defeatist. Would you really let through
almost all spam at a threshold of 11.0?
