The powers that be would like to send customised virus notification based on which OEM brand the customer belongs to. Naturally one solution would be to run multiple amavisd processes on the servers, on different ports, and hence different amavis.conf files.
But I do not mind fiddling with the sources to perhaps find a better way. As we use LDAP for our backend, I was planning to include additional attributes from which I can detect the customers' brand. (lets say GroupID as an example). Can anyone think of a way to then specify a different notify_virus_recips_templ based on this? I'm guessing that this is probably a little bit of a special case. One idea would be to define a $group variable and allow it to be used with notify_virus_recips_templ="notify_$group.txt", but I would then need to delay loading of the template file until it was required. Perhaps there are better solutions to gain the feature that they want? Lund -- Jorgen Lundman | <[EMAIL PROTECTED]> Unix Administrator | +81 (0)3 -5456-2687 ext 1017 (work) Shibuya-ku, Tokyo | +81 (0)90-5578-8500 (cell) Japan | +81 (0)3 -3375-1767 (home) ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ 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/
