Here at our company we have moved off of our old IMAP/Postfix email solution and have implemented Zimbra. We are all very pleased with it thus far, but there are some critical issues that we are either not understanding or have missed something somewhere.
The main issue revolves around our password expiration policies at the company. We handle very sensitive data and as a result our passwords expire every 30 days. When a user logs into our web application that we use here, it prompts them to update their password with a new one. After the password is changed is it stored in an LDAP backend. Zimbra is currently using that LDAP backend to authenticate with no issues.
All email clients such as the zimbra web client, iphone mail client, outlook, thunderbird, and blackberry clients will prompt the user when the currently stored password (which is now expired) is not working. The user then puts in the new password that they just set in the web application and it is good for another 30 days.
The issue is with the Zimbra Desktop client. Most of our corporate users are using the Zimbra Desktop client and when the currently stored password is not working, Zimbra Desktop gives no indication to the user. The users usually sit there for almost half a day wondering why they are not getting messages, only to call IT and have someone tell them that they need to go to setup, click edit, put in the new password, and click save.
Are there any plans to fix this, or are we missing a setting somewhere? Thanks in advance to anyone that can help.