Roland wrote:

> All what I write  in the part @score_sender_maps it has no effect.

> also that has no effect:
> #$blacklist_sender_re = new_RE(
> @blacklist_sender_maps = new_RE(
>   qr'^(bulkmail|offers|cheapbenefits|earnmoney|foryou|greatcasino)@'i,
>   qr'^(investments|lose_weight_today|market.alert|money2you|
> MyGreenCard)@'i,
>   qr'^(new\.tld\.registry|opt-out|opt-in|optin|
> saveonlsmoking2002k)@'i,
>   qr'^(specialoffer|specialoffers|stockalert|stopsnoring|wantsome)@'i,
>   qr'^(workathome|yesitsfree|your_friend|greatoffers)@'i,
>   qr'^(inkjetplanet|marketopt|MakeMoney|eimer|subscribe)\d*@'i,
>   qr'^(eimer|bulkmail|subscribe)@'i,
> );

That is more helpful. There are quite a few possible methods so it did
require you to be specific. In @score_sender_maps you can soft whitelist
by giving a negative score and soft blacklist by giving a positive
score but you have to be sure it's the envelope sender (not
necessarily the sender in the From: header line) you are white/black
listing. However, raising the score may not block spam if your
kill_level is high. Lowering it *may* bring it below tag2_level.

White/black lists are only for spam. If you are expecting it to also
pass/block banned files, viruses and/or bad headers then you should
realize it wont.

If I were to add an envelope sender to @score_sender_maps in an
appropriate section, like so:

[...]
#  read_hash("/var/amavis/sender_scores_sitewide"),

   { # a hash-type lookup table (associative array)
     '[EMAIL PROTECTED]'     =>      .111,
     '[EMAIL PROTECTED]'                        => -3.0,
     '[EMAIL PROTECTED]'              => -3.0,
[...]


It should show where it adds the score: (+0.111)

X-Spam-Status: No, score=0.774+0.111 tagged_above=-992 required=6.31
        tests=[ADDR_FREE=0.078, ALL_TRUSTED=-2.82, AWL=1.327,
        BAD_CREDIT=0.252, EXCUSE_10=0.38, EXCUSE_19=0.357,
        HTML_IMAGE_RATIO_04=0.184, HTML_MESSAGE=0.001, HTML_TITLE_EMPTY=0.045,
        MARKETING_PARTNERS=0.718, URI_OFFERS=0.252]

If you have $final_spam_destiny = D_PASS; (or recipient is a
spam_lover) then spam will still be delivered even if it is blacklisted.

Here I placed the same sender in a blacklist, but because of D_PASS,
it still gets delivered:

X-Spam-Status: Yes, score=x+0.111 tagged_above=-992 required=6.31 BLACKLISTED
        tests=[]

Note that spamassassin also has a number of whitelist/blacklist
settings (that are not based on envelope sender):
http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html#whitelist_and_blacklist_options

It would also help to be specific on what you did, what you expected
would happen - or what you would like to happen, and some sort of
example where it did not do what you expected it to.
        
Gary V


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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/

Reply via email to