Sébastien, > Yes, you're right in fact we did it with spam_lover. > We wanted to do that because we will mix outgoing scan and inbound scan > for relay plateform and wanted a different behaviour. I think I was > looking for a very complicated solution and I didn't see that there was > very easy way to manage to do that.
The %final_destiny_by_ccat and the $final_*_destiny are dynamic settings. As such, they can be changed by a policy bank. You can have separate policy banks for outgoing vs. inbound mail, each with its own setting of final destiny. The point to keep in mind is: final destiny is a per-message setting, policy banks can change per-message settings, they affect each message as a whole (not per-recipient). The kill level, spam lovers, ... are per-recipient settings, they affect each recipient individually, they work correctly even for multi-recipient mail. As such they are somewhat more limited and more tricky to implement right, compared to per-message settings. Mark ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
