Im sorry, I went back and read your original post I thought this was too simple.
On Aug 14, 2013, at 11:29 AM, Jonathan Engbrecht wrote:
> …..snip > The attribute is not itself the name of the next transport.
thats a problem. postfix will need a legit ip or hostname. you would have to do
some
On Aug 15, 2013, at 9:54 AM, Jonathan Engbrecht wrote:
> Yes, I have the ability to make the required changes to our ldap.
ok, so pick and open attribute and fill in either the IP or FQDN
then edit your master.cf and your ldap_transport.
point your transport lookup to the LDAP server with t
Yes, I have the ability to make the required changes to our ldap. I was
mostly curious if it was possible to set up a mapping in a non-hackish
manner that didn't necessitate directory changes.
Thanks all for the responses.
On Thu, Aug 15, 2013 at 9:18 AM, jeffrey j donovan
wrote:
>
> On Aug 14
On Aug 14, 2013, at 1:37 PM, Jonathan Engbrecht wrote:
> there is no mailHost attribute in ldap (or *any* attribute that is the "next
> hop" dns name). I need to map an attribute in ldap to something that *isn't*
> in ldap.
>
> (yes, this could be done with ldap modifications (and probably w
Hi,
> there is no mailHost attribute in ldap (or *any* attribute that is the
> "next hop" dns name). I need to map an attribute in ldap to something that
> *isn't* in ldap.
You could define transports with the names from LDAP as SMTP transports
in master.cf and then use these names from within y
there is no mailHost attribute in ldap (or *any* attribute that is the
"next hop" dns name). I need to map an attribute in ldap to something that
*isn't* in ldap.
(yes, this could be done with ldap modifications (and probably will have to
be). I'd just like to confirm that I can't do it without)
On Aug 14, 2013, at 11:29 AM, Jonathan Engbrecht wrote:
> We have an attribute in our ldap that I'd like to use to determine the "next
> hop" for mail transport. The attribute is not itself the name of the next
> transport.
>
> Is there a way to set up a mapping for this?
>
> ie:
>
> dn:
We have an attribute in our ldap that I'd like to use to determine the
"next hop" for mail transport. The attribute is not itself the name of the
next transport.
Is there a way to set up a mapping for this?
ie:
dn: xxx...
routingattribute: foo
route messages with this attribute to smtp:bar.c
