Bastian,
> I tried to user different final_spam_destiny settings on multiple
> domains, but it seems not to work.
> What I tried before:
> $final_spam_destiny = {
> ".domain1.com"=>"D_PASS",
> ".domain2.com"=>"D_PASS",
> "."=>"D_REJECT"
> };
> But these settings are totally ignored by amavis.
> What am I doing wrong here?
The $final_spam_destiny is a plain scalar variable,
it is not a per-recipient @*_maps -type of a lookup table.
(and even if it were, the "D_PASS" right-hand side is
wrong, it should not be a string "D_PASS", but a constant
integer D_PASS)
The usual mechanism to block (D_BOUNCE or D_REJECT) by
default, but allow for exceptions is to declare some
recipients (or domains) as spam lovers, e.g.:
$final_spam_destiny = D_REJECT;
# (note, use D_REJECT only in a pre-queue setup,
# otherwise a D_BOUNCE or D_DISCARD should be used!)
@spam_lovers_maps = (
{ ".domain1.com" => 1,
".domain2.com" => 1,
"." => 0,
}
);
You'd probably also want:
@bypass_spam_checks_maps = @spam_lovers_maps;
Declaring recipient a spam lover effectively turns
a $final_spam_destiny to D_PASS for this message.
Mark
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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/
