Closed Bug 987276 Opened 11 years ago Closed 10 years ago

Zimbra 8.0.6 - Calendar invites not deleting from attendee's calendar when invite is canceled/modified

Categories

(Infrastructure & Operations Graveyard :: Servicedesk, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jbraddock, Assigned: jbraddock)

Details

Opening this bug for tracking the issue with Zimbra where Calendar invites do not get removed from some attendees calendars when the invite is canceled by the organizer (or a delegate of the organizers calendar).
INC0012731 - Has been created in Service Now for linkage.
Any news on this? I'm hitting this regularly :(
Tim - can you tell me what meetings you see this with and when you made the changes? I'll have to check the logs to figure out what's going on. Our logs only go back 2 weeks and were never able to troubleshoot this fully.
Sure, this happens with most (all?) of Gavin Sharp's cancellation or modification mails. Today he cancelled the "Desktop engineering backlog triage", I received an email but don't see any changes in Zimbra or the OS X Calendar app. Today he modified the meeting "Tim/Gavin 1-1" twice and neither of those changes made it into my calendar. Let me know if you need more information!
Hi Tim - Looks like when Gavin originally sent out the request - he did so with gsharp@mozilla.com. But when he updated the calendar item - he's doing it as gavin@mozilla.com and Zimbra doesn't like that. I'm trying to find the other meeting you gave as an example. 2014-06-03 10:59:43,031 INFO [LmtpServer-7078] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] calendar - Modifying CalendarItem: id=90858, folderId=10, method=REQUEST, subject="Tim/Gavin 1-1", UID=f9732517-1cc1-4d61-bcf2-2c3d178114a2, recurId=20140604T160000Z 014-06-03 10:59:43,031 WARN [LmtpServer-7078] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] calendar - Unable to process iCalendar attachment com.zimbra.cs.mailbox.BadOrganizerException$DiffOrganizerInComponentsException: For an appointment, instance ORGANIZER 'gavin@mozilla.com' should be same as main rule ORGANIZER 'gsharp@mozilla.com' -- 2014-06-03 11:08:40,188 INFO [LmtpServer-7079] [ip=10.20.77.30;] lmtp - Delivering message: size=3402 bytes, nrcpts=1, sender=gsharp@mozilla.com, msgid=<414892253.2252590.1401818919832.JavaMail.zimbra@mozilla.com> 2014-06-03 11:08:40,204 INFO [LmtpServer-7079] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] mailop - Adding Message: id=628036, Message-ID=<414892253.2252590.1401818919832.JavaMail.zimbra@mozilla.com>, parentId=-1, folderId=2, folderName=Inbox. 2014-06-03 11:08:40,211 INFO [LmtpServer-7079] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] calendar - Modifying CalendarItem: id=90858, folderId=10, method=REQUEST, subject="Tim/Gavin 1-1", UID=f9732517-1cc1-4d61-bcf2-2c3d178114a2, recurId=20140604T160000Z 2014-06-03 11:08:40,211 WARN [LmtpServer-7079] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] calendar - Unable to process iCalendar attachment com.zimbra.cs.mailbox.BadOrganizerException$DiffOrganizerInComponentsException: For an appointment, instance ORGANIZER 'gavin@mozilla.com' should be same as main rule ORGANIZER 'gsharp@mozilla.co
Hi Tim - Found the other meeting. You're getting the same error for that one too. But it looks like Justin who is also on the same meeting invite does not. I think this can be resolved if Gavin deletes you off the meeting and then re-adds you. Can we try that? 2014-06-03 10:58:25,178 INFO [LmtpServer-7077] [name=jdolske@mozilla.com;mid=501;ip=10.20.77.30;] calendar - Modifying CalendarItem: id=1525562, folderId=10, method=CANCEL, subject="Cancelled: Desktop engineering backlog triage", UID=1447f016-d585-4eb7-a97f-8bcb02ca2437, recurId=20140604T170000Z 2014-06-03 10:58:25,226 INFO [LmtpServer-7077] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.30;] calendar - Modifying CalendarItem: id=565129, folderId=10, method=CANCEL, subject="Cancelled: Desktop engineering backlog triage", UID=1447f016-d585-4eb7-a97f-8bcb02ca2437, recurId=20140604T170000Z 2014-06-03 11:29:23,280 INFO [qtp1011763082-1320302:http://10.20.77.36:8080/service/soap/ImportAppointmentsRequest] [name=ttaubert@mozilla.com;mid=334;ip=10.20.77.22;ua=ZimbraWebClient - FF32 (Mac)/8.0.6_GA_5922;] calendar - Modifying CalendarItem: id=565129, folderId=10, method=CANCEL, subject="Cancelled: Desktop engineering backlog triage", UID=1447f016-d585-4eb7-a97f-8bcb02ca2437, recurId=20140604T170000Z
(In reply to Jennifer Hayashi [:nej] from comment #5) > Looks like when Gavin originally sent out the request - he did so with > gsharp@mozilla.com. But when he updated the calendar item - he's doing it > as gavin@mozilla.com and Zimbra doesn't like that. I'm trying to find the > other meeting you gave as an example. Thanks for searching the two meetings, Jennifer! How can this happen? Is something misconfigured on Gavin's side? Can we catch those kinds of mistakes on the server side maybe?
Or can we maybe make Zimbra aware of 1:1 aliases?
Hi Tim - Zimbra should be aware of the aliases - I think most likely Gavin had ical or something configured to log in as gavin@mozilla.com instead of gsharp@mozilla.com. Or maybe he still does -- I'm surprised that Zimbra didn't complain. I'm not really sure how he was able to do that. But I would say going forward the best thing is always to log into things with your default ldap credentials instead of an alias as we are trying to integrate more of the systems into LDAP.
QA Contact: tfairfield → moconnor
I've only ever used the Zimbra web UI at https://mail.mozilla.com to send/update invites. I always log in with gsharp@mozilla.com. I have my mail set to send a "From"/"Reply To" (not sure which one) header of gavin@mozilla.com by default, but perhaps Zimbra's UI doesn't do that consistently for calendar invites, or something?
Product: mozilla.org → Infrastructure & Operations
Closing this out since we are no longer on Zimbra.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.