Mark wrote:
> Leaving %final_destiny_by_ccat to its default (not having a new
> value assigned to it in amavisd.conf, e.g. having it commented out),
> everything behaves as before, the $final_spam_destiny will be taken
> into effect if mail is spam.
> If a *_by_ccat is assigned to explicitly, then whatever is assigned to
> it controls which settings or config variables will be consulted
Did you unintentionally leave both $final_destiny and ccat entries
uncommented in amavisd.conf-sample? I am aware you discourage use
of amavisd.conf-sample as a method of configuring amavisd-new.
I assume only the last example will actually be used?:
$final_destiny_by_ccat{CC_BADH.',2'} = D_PASS; # BadHdr8bit
This last example looks reasonable (not that I understand at this
point what is really happening), so if it is the the only setting that
will be used I guess it would not matter much one way or the other.
Gary V
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
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/