806510 - Lightning confuses usernames for calendars and mailaccounts

Status: RESOLVED DUPLICATE of bug 865726

(Calendar :: Provider: CalDAV, defect)

Description

[Tom Louwrier]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121025210744

Steps to reproduce:

hi guys,

New here but active on Launchpad for some time.
Ubuntu user, running 12.04 amd64, updated daily so up to date.
Been using Tbird and Lightning happily for >5 years now. Recently things have degraded here and there.

I'm using 3 calendars on a Sogo-server, 2 of them for myself and one a group-calendar called 'sales'. The ones for myself are 'personal' and 'business'.
All calendars are linked to their own, different email addresses in two different domains:
- personal @ myname.com
- me.business @ company.com
- sales @ company.com
(This in itself has some issues, but I'll file another bug report on that.)

The accounts have usernames that differ from those in the mail addresses, this is due to my provider's way of managing domains and users:
- myname_com_personal (can be followed by @ provider.org but not really necessary)
- company_com_mebusiness (same)
- company_com_sales (same)


Actual results:

Recently Lightning started messing up usernames when sending out invitations and confirmations. I suspect this was when we recieved 1.8 some weeks ago.
It used to use the correct email addresses as given for the calendars. Now it constructs its own from the username as given for accessing the calendars and the domain that belongs to the original mail address, like
- company_com_mebusiness @ company.com
This is NOT as it should be since that email address does not exist. Replies and invitations either never arrive or fall into a catch-all mailbox (info @ company.com) and bother the people that manage that box.


Expected results:

All invitations and confirmations should use the email address that is specified as belonging to that particular calendar.
Lightning must be able to handle multiple calendars, using the correctly given data for each email address, useraccount and password combination.

Comment 1

[Tom Louwrier]

update:
I just found out that when I tick the 'Support Outlook and Outlook 2000/XP' box when accepting an invitation, the confirmation includes just me. The appointment, when opened in the Sogo-server based calendar shows '[e-mail]' (organiser) and '[e-mail]' (participant). This is correct.
The incorrect '[e-mail]' attendee is no longer introduced and thus will not get any messages when the appointment is modified or deleted.

Mind you: neither party is using Outlook nor Exchange. This is a Tbird/Lightning/Sogo setup. It does narrow down the source of the issue to the generic and/or CalDAV part of the protocol I think.

For now this is a workaround.

cheers
Tom

Comment 2

[Tom Louwrier]

Update again: recently (as in: last week or so) the workaround stopped working. Whenever I accept an invitation, the confirmation that is sent out contains both my correct email address and the self generated (??). This last one is both not correct and not wanted since I accepted this invitation for my private calendar only. It was sent to the associated email address only.

cheers
Tom


===========================================
MIME-version: 1.0
From: [e-mail]
To: [e-mail]
Date: Tue, 26 Feb 2013 15:03:14 GMT
Subject: Event Invitation Reply (Accepted): Arctic
 Challenge
Content-class: urn:content-classes:calendarmessage
Content-type: text/calendar; method=REPLY; charset=UTF-8
Content-transfer-encoding: 8BIT

BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
METHOD:REPLY
BEGIN:VTIMEZONE
TZID:Europe/Paris
X-LIC-LOCATION:Europe/Paris
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
CREATED:20130226T145015Z
LAST-MODIFIED:20130226T150314Z
DTSTAMP:20130226T150314Z
UID:73cb5e26-24de-486f-8d14-b9d79ef0fb00
SUMMARY:Arctic Challenge
ORGANIZER;RSVP=TRUE;CN=Her Name;PARTSTAT=ACCEPTED;ROLE=CH
 AIR;SCHEDULE-AGENT=CLIENT:mailto:[e-mail]
ATTENDEE;PARTSTAT=ACCEPTED;ROLE=REQ-PARTICIPANT;SENT-BY="mailto:[e-mail]":mailto:[e-mail]
DTSTART;TZID=Europe/Paris:20130316T150000
DTEND;TZID=Europe/Paris:20130316T160000
LOCATION:xxxxxxx
DESCRIPTION:herhaling op 17 maart aanvang 11.55
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR

Comment 3

[Tom Louwrier]

Update:
Is someone actually reading this?
Lightning is virtually unusable now. Sending invitations and confirmations are both done with wrongly constructed sender addresses. The Outlook compatibility option stopped working as a workaround.
Also the local caching is broken as is the relation email address - calendar.

All in all this means I get appointments placed in the wrong calendars, confirmations and updates are not processed and the whole of Tbird gets unworkably slow due to the constant on line updating.

I'm now going to see how either Evolution or Outlook perform. Lightning is obviously severely broken in several essential functions (caldav, caching, tbird integration, multiple calendars) and no one picks up on it. What a shame.

Comment 4

[Tom Louwrier]

Update:
Calendar caching issue was solved by moving to Lightning-extension 1.9.1.

The problem with the sender address when sending invites or when responding to one has gone worse though. I can/do now only send invitations and replies from one of the wrongly constructed (by Lightning) email addresses. This causes confusion for the receiving persons. Also I have had to make aliases in order to intercept mails and responses sent to the wrong address.

By now I'm running Tbird 23.0 (from the MozillaTeam PPA over at Launchpad) in order to try Lightning 2.5b2 (from Mozilla). Unfortunately this still does not solve the issues I'm having.

If there is anything I can do to further analyse this so someone can actually fix it, just ask.

cheers
Tom

Comment 5

[Ken Shaffer]

Just some ideas:

Go into calendar tab of TB and right-click on calendars and choose properties and check that refreshes occur less frequently, mine are all 30 minutes.

Lightning 2.6 has patches which can be applied to handle google's changes to authentication.  In fact, my understanding is any older version of lightning will not work with google calendars.  And, I believe TB 24 is needed too.

For email address problems, also check calendar properties, and check that the email address of the calendar is what you intend.

I've noticed in my TB that whatever calendar I last selected in the calendar tab before closing is now the default calendar.

Comment 6

[Philipp Preißer-Kewisch [:Fallen][☁️📆]]

I believe the sender address issue can be handled in: