Lightning uses wrong email address with calendar
Categories
(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)
Tracking
(Not tracked)
People
(Reporter: je, Unassigned)
Details
+++ This bug was initially created as a clone of Bug #1304358 +++
This happens in Thunderbird 68.5.0 and 68.6.0 on Windows 10 with the integrated Lightning Add-On.
Steps to reproduce:
I have an owncloud account for contacts and calendar.
I have two email accounts configured in Thunderbird, mail-A and mail-B.
I attached the woncloud calendar via caldav and assigned my email address mail-A in the properties dialog to this calendar. Then I entered a new appointment and invited other persons.
Actual results:
In the "invite attendees"-Dialog mail-B is shown as the organizer's address and
the invited persons get an invitation with my email address mail-B.
Expected results:
The invited persons should get invitations with the email address I assigned to the calendar (mail-A).
Comment 1•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 2•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 3•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is --
(Backlog,) indicating it has has not been previously triaged, the bug's Severity is being updated to --
(default, untriaged.)
Comment 4•5 years ago
|
||
The severity of these bugs was changed, mistakenly, from normal
to S3
.
Because these bugs have a priority of --
, indicating that they have not been previously triaged, these bugs should be changed to Severity of --
.
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 5•2 years ago
|
||
I can't reproduce this bug any more.
Description
•