Closed Bug 859383 Opened 11 years ago Closed 11 years ago

Aliases confuse Lightning about event ownership/invitations

Categories

(Calendar :: Provider: CalDAV, defect)

Product:
Calendar
Component:
Provider: CalDAV
Platform:
x86_64
Windows 8
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 865726

People

(Reporter: vlad, Unassigned)

Details

Thunderbird 17.0.5, Lightning 1.9.1

Mozilla's Zimbra server, CalDAV calendar.  I have a couple of aliases on the server -- my main account is vladimir@, I also have vlad@ and vvukicevic@ as aliases.

I set up a remote CalDAV calendar using https://mail.mozilla.com/dav/vladimir@mozilla.com/Calendar.  Everything is loaded fine, but I am unable to modify my attendance on any events.  If I create an event using Lightning, then I can adjust my attendance on it; if I create an event using the Zimbra web UI (or if someone invites me), I can't change attendance.

Lightning seems to be creating events using Organizer: vlad@mozilla.com; those are the ones that I can modify.  But the web UI and all invitations are coming to vladimir@mozilla.com; I can't modify those.  (Now that I think about it, this started when I got the vlad@ alias -- the vvukicevic@ alias sorted after vladimir@, so it wasn't an issue before.)

It doesn't matter what I switch my email setting to in calendar properties, nor does it matter if I do/don't have the other aliases attached as identities in the mail server settings.
Might be same as Bug 539916 / Bug 540410.
Hmm, yes, bug 540410 sounds very similar.  Can I somehow see the CalDAV communication to verify that it's the same?
Set advanced preference "calendar.debug.log" to true in Thunderbirds about:config dialog and restart. CalDAV communication should be logged to Error Console. For more information enable "calendar.debug.log.verbose" too.
This is a dup of bug 865726, which has much more detailed information in it.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.