 problem solved
The different behaviors we saw apparently were due to the mail routing after all. We'd attempted to route Zimbra event mail (calendar shares, meeting notices, etc) to an outside mail server. This seems to break Zimbra's calendar system -- if the Zimbra calendar can't put messages into a user's Zimbra inbox, that user won't be able to confirm meetings or accept shares, and the user's free/busy information will not be correct. |