users are not presented with an option to accept, decline, or tentative appointments

[bbarnett]

As the topic says, sometimes users are not presented with an option to accept, decline, or tentative an appointment. The do receive a meeting request email, but in some cases that email offers no options for accepting, declining, or tentative.

However, the user can go to their calendar and right click on the appointment in question, and _then_ select one of the above options. This works fine, without issue.

Anyone else seeing this?

[gmsmith]

Are these user also Blackberry users? If so there is a bug that has been resolved in 5.03 (pending) that addresses this particular user. The bug is: Bug 19868 - BB: Accept/Decline not showing on many invites on BES-enabled accounts

[G00FIN42]

If yes, we have found that applying latest patches to all PCs resolves this issue.

If some users are on SP2 while others are on SP3 or some have the latest outlook only patches and others don't we see the issue but as soon as we patch everyone to the latest level we don't see the issue.

Never have seen the issue in Zimbra web client.

[gmsmith]

I assumed the issue was with the web client...why would you use anything else?

[G00FIN42]

I totally agree, I try daily to show my users how they can work smarter with Zimbra than they could ever dream of with Outlook.

Thanks to Zimbra Development Team and support community.

I really do appreciate everything you do.

[bbarnett]

Yes, this is with the web client, and yup.. with BES users.

Any idea when 5.0.3 (or whatever the . is), will be released?

[bbarnett]

I'm still seeing this issue, and issues like it, with BES users.

Can we put a fast track on this, please?

[bbarnett]

I've added a comment to the original bug, but I don't see how to re-open it. Should I simply post a new bug?

[uxbod]

I would file a new bug but including a reference to the original one aswell. This will help the Zimbra PM and developers.

[gmsmith]

I would also file a ticket with support. We have multiple 5.06 environments that aren't showing that behavior, perhaps there is something unique to your setup.