Thanks for your reply... going in search of now
On the DNS issues, I have personally experienced this and believe the LDAP auth failures were due to DNS not resolving properly. This caused either failure to authenticate or simple bind failure messages constantly but would come right by itself or a restart. Usually happens when network load is high and DNS is getting hammered.
Today I set it up a little different. It is installed on a 10.5 server so I set up that server to be a DNS server authoritive for itself and forwarding all other traffic. I also used the IP of the external LDAP instead of hostname in zimbra.
After setting accounts up I tested it and they authenticate very fast now. It is working beautifully fingers crossed X
Apart from needing to get mail back etc the only problem I have now is in some areas of admin which I think is because I have set the web port to 81. If I try to click view mail for a user I get an error. If I add 81 to the url it works fine.
Before you ask, I had to use 81 so I could load a page first to let our users know that they were on IPC Webmail. I got lots of complaints before that they couldnt access webmail after I changed from another server even though I told them all
) well you get that! so I now load a simple graphic first then redirect to zimbra webmail which is in a frame. take a look and you will see what I mean.
Welcome to IPC Webmail
This keeps the zimbra branding but also lets our users know where they are.
Quote:
Originally Posted by Hivos  |
Bugzilla
Wiki
Source
restore 
Linear Mode
