| |||||||||||||||||||||||||||||||
|
server so that I can direct users to their appropriate back-end servers for final delivery. It appears to be working, but if I update the mailHost attribute in the user's LDAP entry, it does not take effect until I do a "postfix reload". Shouldn't the change be dynamic and not require a reload? I used tcpdump to watch traffic going to our LDAP server (Sun IPlanet). It takes a minute or so, but I then see a request to to the LDAP server, and it returns the correct mailHost value. However, the new mailHost value is not being used for the transport. It continues to use the old value for the transport. If I do a postfix reload, it starts using the new value from LDAP. Is there some sort of caching going on? If so, can I disable it or turn down the TTL? How else can I debug this? The postmap -q command returns the correct entry each time. I'm using the Postfix that comes bundles with Red Hat Enterprise Linux 4. I believe it is Postfix version 2.2.10. -Shawn
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com