whitelist_from vs blacklist_from

[Antonio DeLaCruz <td...@homenet.tzo.com>]

How can I make spamassassin not look at the blacklist_from addresses if it finds
a user listed in whitelist_from?  Or another way, how can I exclude one user
from getting the USER_IN_BLACKLIST score?

I have in my user_prefs file:

whitelist_from bob@aol.com

blacklist_from *@aol.com

spamassassing seems to look at the blacklist_from first and then quits looking
if there is a match.  So when I get a message from bob@aol.com, it tags it as
spam.  I want to be able to exclude bob from the *@aol.com without having to
remove the *@aol.com.


Thanks,

Antonio DeLaCruz





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: whitelist_from vs blacklist_from

[Matt Kettler <mk...@comcast.net>]

At 04:55 PM 5/16/2005, Antonio DeLaCruz wrote:
>How can I make spamassassin not look at the blacklist_from addresses if it 
>finds
>a user listed in whitelist_from?

You can't. (read on)

>  Or another way, how can I exclude one user
>from getting the USER_IN_BLACKLIST score?

No.


>I have in my user_prefs file:
>
>whitelist_from bob@aol.com
>
>blacklist_from *@aol.com
>
>spamassassing seems to look at the blacklist_from first and then quits looking
>if there is a match.  So when I get a message from bob@aol.com, it tags it as
>spam.


Really, that message should match both USER_IN_BLACKLIST and 
USER_IN_WHITELIST, so the scores should offset each other.

Can you check the X-Spam-Status?

Re: whitelist_from vs blacklist_from

[Marco Maske <ma...@netcologne.de>]

Antonio DeLaCruz wrote:
> How can I make spamassassin not look at the blacklist_from addresses if it finds
> a user listed in whitelist_from?  Or another way, how can I exclude one user
> from getting the USER_IN_BLACKLIST score?
> 
> I have in my user_prefs file:
> 
> whitelist_from bob@aol.com
> 
> blacklist_from *@aol.com
> 
> spamassassing seems to look at the blacklist_from first and then quits looking
> if there is a match.  So when I get a message from bob@aol.com, it tags it as
> spam.  I want to be able to exclude bob from the *@aol.com without having to
> remove the *@aol.com.

If you running SA with amavisd-new (since 2.0) then look at _soft_ w/b listing:

@score_sender_maps in amavisd.conf

# The essential difference is that scores from _all_ matching by-recipient
# lookups (not just the first that matches) are summed to give the final
# score boost. That means that both the site and domain administrators,
# as well as the recipient can have a say on the final score.


Or you can use the _hard_ w/b listing in amavisd-new:

The per-recipient lookups take precedence over the global lookups.

$per_recip_blacklist_sender_lookup_tables = {
'.my1.example.com'    => [qw( !bob@aol.com .aol.com )],
'.my2.example.com'    => [qw( .aol.com )],
};


from the FAQ amavisd-new:
# + White and blacklisting in amavisd-new and as provided by SA are similar in
#   concept, but different in implementation. Both can coexist, use the mechanism
#   that best suits the needs.
#   - The w/b listing in SA works on information from the header (e.g. on the
#     mail author -- the From: header field), and contributes large positive or
#     negative score points to the score being computed.
#   - The (hard) w/b listing in amavisd-new works on envelope sender address
#     (i.e. the return-path). If triggered, the call to SA is skipped to save
#     time, as it would not have a chance to overrule the w/b list decision
#     already taken.
#   - The (soft) w/b listing in amavisd-new (the @score_sender_maps, since 2.0)
#     also works on envelope sender address, but only modifies the spam score
#     as returned by SA, and does not bypass calling SA.

P.S.:
There are several other ways to do that in amavisd-new. I hope my examples can help.

Look in your docs for amavisd.conf-sample. That is the traditional style, chatty
configuration file with many easy explained good examples.

-- 
Ciao Marco, registered GNU/Linux-User 313353