1853535 - Thunderbird (CalDav / Lightning) ... wrongly replaces ORGANIZER

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Robert Hartmann]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/118.0

Steps to reproduce:

Let others create an invitation inside Outlook(Exchange Account) with me as attendee.
I recieve invitation mail in Thunderbird and accept the appointment for storing in a Horde Groupware calendar 5.2.22 via Thunderbird.

Actual results:

I recieve a second mail, where the organizer of the event is informed, that I had accepted.
These second mail has an attachement, called "invite.ics", where the original value of Organizer has been replaced by my account-information.
Since I had accepted tha appointment using Thunderbird's accept button,
I think the wrongly changed value of ORGANIZER has been done by Thunderbird.

Expected results:

ORGANIZER value should be untouched while accepting by attendees.
And the invitation reponse should recieve at organizer.

Maybe Thunderbird is innocent and Horde changes the values which has been transmitted via Thunderbird correctly.
But I do not know.

I know, that horde itself has bugs (fixed but sadly not released for many years)
where in consequence ORGANIZER value becomes changed:

• https://bugs.horde.org/ticket/13664#c4 (November 2014)

• https://bugs.horde.org/ticket/13664#c11 (October 2018)

• https://bugs.horde.org/ticket/13790 (January 2015: ICAL and stepts to reproduce)

• https://bugs.horde.org/ticket/3965#c15 (January 2015: stepts with TB/Lightning to reproduce)

• https://bugs.horde.org/ticket/3965#c17 (Fix for Hordes Organizerbug)

• Fix for Horde was merged 2015 : https://github.com/horde/horde/pull/167

So bug is fixed for Horde 6, but when it get released ... who knows: https://www.horde.org/apps/groupware/roadmap
(Currently latest release of horde is 5.2.22 from year 2017, but if it includes the organizer bugfix, I do not know.)

Meanwhile perhaps on Thunderbird there could be a tweak to save correct organizers value?

Comment 1

[Robert Hartmann]

In https://github.com/horde/horde/pull/167#issuecomment-164710756 , there is told,
which parts of problem "wrongly changed ORZANIZER" hat been solved in Horde.

But with Thunderbird before version 115
or TB 119.0a1 (2023-09-15),
or TB 118-Patch-Testing-Version from https://bugzilla.mozilla.org/show_bug.cgi?id=1850732#c17
the value of ORGANIZER changed wrongly by importing.

Comment 2

[Magnus Melin [:mkmelin]]

From bug 459683?

Comment 3

[Robert Hartmann]

(In reply to Magnus Melin [:mkmelin] from comment #2)

From bug 459683?

Well, in bug 459683 there was written:

   "Target Milestone: --- → 114 Branch"

If I accept i.e. an MS-Outlook/Exchange or Cisco WebEx invitation with TB 102.15.1 - or older TB versions - to become an ATTENDEE
than the ORGANIZER value has been changed to be me .
(if all other ATTENDEES were informed, that I become wrongly the ORGANIZER, I do not know. I should ask them ... )

Since that wrong behavior persist in TB 119.0a1 (2023-09-17), I am at least sure that changes from fixed bug 459683 are not the reason in first place.

Comment 4

[Robert Hartmann]

I test an other Calendar-Server (nextcloud) .
Here I can see, that Thunderbird 115.2.2 does not freeze like in bug 1849540 and it does not exchange the ORGANIZER - value:
The correct ORGANIZER gets a reply where I am beeing ATTENDEE and not wrongly ORGANIZER.

But Thunderbird logs that information in error console:

 Calendar: Could not find definition for (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna 2 CalTimezoneService.jsm:135
 Calendar: No unique email address for lookup! calItipUtils.jsm:1115
 Element.releaseCapture() sollte nicht mehr verwendet werden. Verwenden Sie Element.releasePointerCapture() stattdessen. Weitere Informationen unter https://developer.mozilla.org/docs/Web/API/Element/releasePointerCapture menupopup.js:160:13
 <Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/reactjs/react-redux/releases/tag/v2.0.0 for the migration instructions. react-redux.js:881:13
    Redux 3
    React 13

Comment 5

[Magnus Melin [:mkmelin]]

Right, those console errors are not ideal.
Closing as WFM per comment 4.