Sébastien, > I would like to have different final_spam_destiny by using sql lookup > (we try to setup a spam_destiny per user policy) > Actually, I've tried to add a final_spam_destiny column in my policy > table and it doesn't work, and I like to know if I had to change amavisd > code or if there is a trick to do that. Do I need to use spam_lovers > column in order to achieve that. > > We tried something like that with a custom conf hook, but it's seems > that destiny cannot be set, we also tried the same code in different > hook (befor_send, mail_done, new) and nothing works. > We want to know where final_spam_destiny is used and how can we set it.
Having a per-recipient final_spam_destiny setting is conceptually difficult, consider a combination of D_REJECT and D_BOUNCE for different recipients of the same message. What are you trying to achieve anyway? For most purposes there is no need for a per-recipient final_spam_destiny. For example: turning a D_BOUNCE or D_DISCARD into a D_PASS is effectively the same as declaring someone a spam lover or adjusting his kill level. Turning a D_BOUNCE into a D_DISCARD can be achieved by adjusting per-recipient's spam_dsn_cutoff_level. These are all per-recipient 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
