Rework postfixTransportTable
postfixTransportTable attribute is populated from FD interface, but it's stored like this in LDAP:
dn: cn=mail,ou=servers,ou=systems,dc=domain,dc=tld [...] postfixTransportTable: 0:domain.com smtp:mx1.domain.tld postfixTransportTable: 1:domain.net smtp:mx2.domain.net
This format is unfortunatly not usable by postfix as is, because of the way postfix ldap_table are done (the relay host needs to be the only value of a uniq attribute). One way to fix this would be to create one sub-entry (in this example, sub entries of the cn=mail,ou=servers,ou=systems,dc=domain,dc=tld object) per transport rule. For example:
dn: cn=mail,ou=servers,ou=systems,dc=domain,dc=tld [...]
dn: associatedDomain=domain.com,cn=mail,ou=servers,ou=systems,dc=domain,dc=tld [...] host: mx1.domain.tld
dn: associatedDomain=domain.net,cn=mail,ou=servers,ou=systems,dc=domain,dc=tld [...] host: mx2.domain.net
(associatedDomain and host are just examples, I'm not sure which objectClass would be the best for these entries)
(from redmine: issue id 2690, created on 2013-08-31, closed on 2013-09-11)
- Changesets:
- Revision 6641aa28 by Côme Chilliet on 2013-09-04T12:27:44.000Z:
Fixes: #2690 Changed the way transport table are stored in the schema
- Revision a6c24101 by Côme Chilliet on 2013-09-04T12:28:06.000Z:
Fixes: #2690 Fixed postfix transport table handling
- Revision 37c42e5b by Côme Chilliet on 2013-09-04T12:28:13.000Z:
Fixes: #2690 postfix service adjustments
- Revision 31a85e09 by Côme Chilliet on 2013-09-04T12:31:26.000Z:
Fixes: #2690 Changed the way transport table are stored in the schema
- Revision 84b2c6cf by Côme Chilliet on 2013-09-04T12:31:41.000Z:
Fixes: #2690 Fixed postfix transport table handling
- Revision 87b2bc6a by Côme Chilliet on 2013-09-04T12:31:54.000Z:
Fixes: #2690 postfix service adjustments
- Custom Fields:
- Bug in version: 1.0.7
- Uploads: