Re: [AMaViS-user] : @local_domains_maps and LDAP

2009-02-16 Thread Quanah Gibson-Mount
--On Thursday, February 12, 2009 4:23 PM +0100 Mark Martinec mark.martinec+ama...@ijs.si wrote: No need to have a static @local_domain_maps prepared from data in LDAP. Thanks, we've worked out a solution that doesn't involve using @local_domain_maps. --Quanah -- Quanah Gibson-Mount

Re: [AMaViS-user] : @local_domains_maps and LDAP

2009-02-12 Thread Mark Martinec
Quanah, The question has to do with the having @local_domains_maps being populated from LDAP instead of hard coded. That's what I don't see being possible with Amavis in its current state. Populating @local_domains_maps is a wrong question, and represents a non-database approach. The question

Re: [AMaViS-user] @local_domains_maps and LDAP

2009-02-12 Thread Michael Hall
On Mon, Feb 02, 2009 at 11:50:46AM -0800, Quanah Gibson-Mount wrote: --On Monday, February 02, 2009 9:40 AM -0800 Quanah Gibson-Mount qua...@zimbra.com wrote: The question comes from our desire to not put X-SPAM headers on local domains, usually listed in @local_domains_maps. This

Re: [AMaViS-user] : @local_domains_maps and LDAP

2009-02-11 Thread Quanah Gibson-Mount
--On February 3, 2009 12:57:46 PM -0800 Quanah Gibson-Mount qua...@zimbra.com wrote: Thanks, although the point I'm trying to get at here, is to avoid doing things exactly like what you are doing. I.e., Amavis understands and uses LDAP. Therefore, one should be able to configure it to

Re: [AMaViS-user] : @local_domains_maps and LDAP

2009-02-03 Thread Hugo Slabbert (i-worx)
don't know if that's useful to you as you were referring just to LDAP in general rather than to an Exchange environment in particular, but hopefully it's of some use. Date: Mon, 02 Feb 2009 11:50:46 -0800 From: Quanah Gibson-Mount qua...@zimbra.com Subject: Re: [AMaViS-user] @local_domains_maps

Re: [AMaViS-user] : @local_domains_maps and LDAP

2009-02-03 Thread Quanah Gibson-Mount
--On Tuesday, February 03, 2009 12:43 PM -0800 Hugo Slabbert (i-worx) hugo.slabb...@i-worx.ca wrote: Hi Quanah, I don't have a solid answer for you, as I've not implemented this for amavisd-new, but maybe I can point you in the right direction. I modified some existing Perl scripts that

Re: [AMaViS-user] @local_domains_maps and LDAP

2009-02-02 Thread Quanah Gibson-Mount
--On Saturday, January 31, 2009 5:06 PM +0100 Mark Martinec mark.martinec+ama...@ijs.si wrote: Quanah, I would like to have amavis query the list of domains from our LDAP server. However, after reading over README.lookups and README.ldap, I don't see an obvious way to do this. The amavis

Re: [AMaViS-user] @local_domains_maps and LDAP

2009-02-02 Thread Quanah Gibson-Mount
--On Monday, February 02, 2009 9:40 AM -0800 Quanah Gibson-Mount qua...@zimbra.com wrote: The question comes from our desire to not put X-SPAM headers on local domains, usually listed in @local_domains_maps. This becomes a problem, however, in an environment where you're hosting thousands of

Re: [AMaViS-user] @local_domains_maps and LDAP

2009-01-31 Thread Mark Martinec
Quanah, I would like to have amavis query the list of domains from our LDAP server. However, after reading over README.lookups and README.ldap, I don't see an obvious way to do this. The amavis schema (http://www.ijs.si/software/amavisd/LDAP.schema) is geared toward individual account

Re: [AMaViS-user] @local_domains_maps and LDAP

2009-01-30 Thread Quanah Gibson-Mount
--On Tuesday, December 18, 2007 11:26 AM -0800 Quanah Gibson-Mount qua...@zimbra.com wrote: I would like to have amavis query the list of domains from our LDAP server. However, after reading over README.lookups and README.ldap, I don't see an obvious way to do this. The amavis schema

[AMaViS-user] @local_domains_maps and LDAP

2007-12-18 Thread Quanah Gibson-Mount
I would like to have amavis query the list of domains from our LDAP server. However, after reading over README.lookups and README.ldap, I don't see an obvious way to do this. The amavis schema (http://www.ijs.si/software/amavisd/LDAP.schema) is geared toward individual account objects,