transport map from ldap

2019-09-19 Thread ab
Hi All. I would like the transport_maps to be driven from an ldap lookuop but i am unsure of the format it should be returning I have the following config and my /etc/postfix/ldap-transport.cf looks like this This returns the output when doing a postmap vq but is that correct for a tran

Re: transport map from ldap

2019-09-19 Thread Wietse Venema
ab: > Hi All. > > I would like the transport_maps to be driven from an ldap lookuop > but i am unsure of the format it should be returning > > I have the following config > > > and my /etc/postfix/ldap-transport.cf looks like this > > This returns the output when doing a postmap vq > > bu

Re: transport map from ldap

2019-09-19 Thread ab
Wow lots of my post got cut off, this is what i wrote. As you can see i am returning adamt...@foo.com relay:[smtp.foo.com] But the mail log is saying transport map error Hi All. I would like the transport_maps to be driven from an ldap lookuop but i am unsure of the format it should be re

Re: transport map from ldap

2019-09-19 Thread Wietse Venema
ab: > > Wow lots of my post got cut off, this is what i wrote. > > As you can see i am returning adamt...@foo.com relay:[smtp.foo.com] > But the mail log is saying transport map error > > > > Hi All. > > I would like the transport_maps to be driven from an ldap lookuop > but i am unsure of

Re: transport map from ldap

2019-09-19 Thread Adam Barnett
um... I have tried both adamt...@foo.com relay:[smtp.foo.com] and relay:[smtp.foo.com] as the the output of the ldap lookup and i just get status=deferred (mail transport unavailable) error Thanks -- __ Adam Barnett Systems Engineer Double Negative 160 Great

Re: transport map from ldap

2019-09-19 Thread Matus UHLAR - fantomas
I have tried both adamt...@foo.com relay:[smtp.foo.com] and relay:[smtp.foo.com] as the the output of the ldap lookup and i just get status=deferred (mail transport unavailable) error any other error in logs? IS the smtp.foo.com reachable? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; htt

Re: transport map from ldap

2019-09-19 Thread Adam Barnett
Hi, That is the only error Sep 19 14:59:54 foo postfix/error[103706]: 3C10828C082: to=, relay=none, delay=0.01, delays=0/0/0/0, dsn=4.3.0, status=deferred (mail transport unavailable) This is a MTA relay host Thanks -- __ Adam Barnett Systems Engineer Double Negative

Re: transport map from ldap

2019-09-19 Thread Wietse Venema
Adam Barnett: > Hi, > > That is the only error > > Sep 19 14:59:54 foo postfix/error[103706]: 3C10828C082: to=, > relay=none, delay=0.01, delays=0/0/0/0, dsn=4.3.0, status=deferred (mail > transport unavailable) > There is more than this. Wietse http://www.postfix.org/DEBUG_README.

Re: transport map from ldap

2019-09-19 Thread Adam Barnett
There was this error as well Sep 19 14:59:47 foo postfix/qmgr[103420]: warning: connect to transport private/f...@bar.comrelay: No such file or directory -- __ Adam Barnett Systems Engineer Double Negative 160 Great Portland Street,W1W 5QA T: 020-7268-5000 [ http

Re: transport map from ldap

2019-09-19 Thread Wietse Venema
Adam Barnett: > There was this error as well > > Sep 19 14:59:47 foo postfix/qmgr[103420]: warning: connect to transport > private/f...@bar.comrelay: No such file or directory > Right. That was for the malformed transport result with an email address at the beginning. What about the other

Re: transport map from ldap

2019-09-19 Thread Adam Barnett
When i changed the LDAP response to server_host = ldap://zimbraldap:389 server_port = 389 search_base = query_filter = (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s))(zimbraMailStatus=enabled)) result_attribute = mail,zimbraMailAlias version = 3 result_format=relay:[smtp.foo.com] start_t

Re: transport map from ldap

2019-09-19 Thread Bill Cole
On 19 Sep 2019, at 11:54, Adam Barnett wrote: When i changed the LDAP response to server_host = ldap://zimbraldap:389 server_port = 389 search_base = query_filter = (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s))(zimbraMailStatus=enabled)) result_attribute = mail,zimbraMailAlias See

Re: transport map from ldap

2019-09-19 Thread Viktor Dukhovni
> On Sep 19, 2019, at 2:37 PM, Bill Cole > wrote: > >> server_host = ldap://zimbraldap:389 >> server_port = 389 >> search_base = >> query_filter = >> (&(|(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s))(zimbraMailStatus=enabled)) >> result_attribute = mail,zimbraMailAlias > > See the ldap_t