Attila, > BTW, don't you plan a "reverse" AM.PDP protocol, where amavisd would be > the client and an external program the server? > For the first iteration passing only as much information from the e-mail > as possible would be more than enough (at least for me at the moment ;) > and then it could be extended to handle policy decisions (setting > amavisd variables for example), or whatever. > So there could be some states (pre anything, pre virus filtering, pre > spam filtering, post filtering, etc) where the amavis policy server > (analog to the postfix one) could decide about further processing, or > change amavisd parameters, the e-mail itself, or whether the mail should > be scanned for viruses, spams, etc. Or something similar. > This would allow a more general approach than the current lookup methods > offer, I think.
It might be useful, but it won't happen soon, mainly because I don't have an immediate need for it and there are always other things that seem more urgent or are more readily achievable. I'll keep the idea in mind, and see if it can ripe into something tangible. Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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/
