Yes. I'm sure.
Scenario is this.
I set up the server in test mode (parallel to our main email system) and called the domain zimbra.mycompany.com
I set up domain masquerading so that emails going to external contacts would get SMTP headers rewritten to mycompnay.com so that return emails would not fail. I set up a test group of user accounts. Those users sent and received emails for a few weeks.
While the domain masquerading worked OK for SMTP headers, an issue came to light when we sent out calendar invites, they still contained the internal email addresses of the invitees. This lead to the internal email addresses becoming known externally.
To avoid this conflict, I renamed the domain to be mycompany.com within the Zimbra utilities. All users email addresses changed correctly, and I set their mail host to be zimbra.mycompany.com so that emails sent internally would go to the zimbra host rather than the original still running in parallel hail host.
All new addressing works correctly - for both internal and external users.
I addes a second block of users to the server.
Again, everything is working correctly.
However, for those users that existed prior to the domain name change, when writing email and using AutoComplete, if the addressee is one of the original zimbra users, two email addresses are thrown up.
user@zimbra.mycompany.com and
user@mycompany.com - both with the little GAL symbol beside their email address.
I have deleted all emails sent and received, contacts, etc. from one of the user accounts, and it does not appear to matter. When that account writes an email, it still shows both the old GAL entry and the new GAL entry for the addressee.
It seems obviuos that these email addresses are being cached somewhere - probably in some recently used email addresses cache - and this is what I would like to be able to clear out.
Thanks