On Feb 6, 2009, at 9:57 AM, Mark Martinec wrote: >> And for clarity, I'm not asking about using part of mynetworks. I'm >> asking about setting a policy based on the remote IP address *other* >> than what's in mynetworks. Just like you can set policy based on the >> TCP port used, why not different remote IP ranges? > > I understood. No reason not to, it just needs to be done. > > A data structure / syntax needs to be devised which can return a > right-hand-side value from an IP-based lookup (not just a boolean), > and lookup_ip_acl() would need to be extended to support it. > I started working on it more than once, but a clean, not too > convoluted syntax and yet reasonably efficient for a search > proved hard to come up.
I'm not sure that non-boolean is required. Why not just replicate mynetworks? For a quick off the cuff gander, something like this: @mynetworks = (x,y,z); @othertrusted = (a,b,c); remotenet_policy['othertrusted'] = 'TRUSTED'; -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
