Ryan,
> The way I prefer to set it up is to have:
>
> '[possible-spam:_SCORE_]' added to the subject if it is above a value
> (let's say 4.9) which is currently defined in $sa_tag_level_deflt.
> ...
> I then want '***SPAM*** _SCORE_ (_REQD_) ' added if it hits
> $sa_tag2_level_deflt
> ...
> And the X-Spam* headers added NO MATTER WHAT..
>
> If I set $sa_tag_level_deflt to undef I get the X-Spam headers added
> every time (which is good) but every single email gets the
> possible-spam header that is defined in $sa_tag_level_deflt. If I set
> this value to 4.9 I get the desired subject header added but the
> X-Spam headers do not get added below this score (4.9).
> How would I go about having the X-Spam* headers added unconditionally
$sa_tag_level_deflt = undef;
> but every single email gets the
> possible-spam header that is defined in $sa_tag_level_deflt
That can be turned off:
@spam_subject_tag_maps = ();
> '[possible-spam:_SCORE_]' added to the subject if it is above a value
> (let's say 4.9) which is currently defined in $sa_tag_level_deflt.
$sa_tag2_level_deflt = 4.9;
@spam_subject_tag2_maps = ('[possible-spam:_SCORE_] ');
> I then want '***SPAM*** _SCORE_ (_REQD_) ' added if it hits
> $sa_tag2_level_deflt
$sa_tag3_level_deflt = 8;
@spam_subject_tag3_maps = ('***SPAM*** _SCORE_ (_REQD_) ');
> while at the same time being able to have Possible-Spam added at 4.9
> (or whatever number) and **SPAM** for tag2
The following is hard-wired:
- tag level starts adding X-Spam header fields;
- tag2 level labels passed mail as spam: turns NO into a YES,
and adds recipient address extensions if enabled;
- kill level blocks mail (unless *_lover) and quarantines it
> and the "evasive actions" at my kill level?
It is non-configurable, "evasive actions" are always at kill level.
> To simplify my question, is there a way to tell amavis to keep
> X-Spam-Flag set to NO until it reaches tag3?
Here is the requirement than cannot be met without
tweaking the code.
> Or as another option is there a way I can have an intermediary level
> in-between the default and tag2 just for the purpose of adding
> Possible-Spam at a non-spam level and keeping the headers in-tact
> below possible-spam so it always shows the spam headers?
There are two possibilities, but each requires tweaking the code.
- Either moving the NO/YES point from tag2 to tag3 threshold
(and keeping tag=undef, tag2=possible-spam, tag3=spam);
or
- Modifying adding of X-Spam header fields to happen regardless
of tag level (and using tag=possible-spam, tag2=spam)
The following change to 2.6.1 will probably achieve it:
--- amavisd~ 2008-06-29 02:37:58.000000000 +0200
+++ amavisd 2008-10-20 19:53:37.000000000 +0200
@@ -11125,4 +11125,5 @@
my($bypassed) = $r->bypass_spam_checks;
my($do_tag) = $r->is_in_contents_category(CC_CLEAN,1);
+ $do_tag = 1; # unconditionally
my($do_tag2) = $r->is_in_contents_category(CC_SPAMMY);
my($do_kill) = $r->is_in_contents_category(CC_SPAM);
Mark
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/
