1393012 - Meeting accept sent from default mail account and not from the account the invite was sent to

Status: RESOLVED DUPLICATE of bug 475886

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Description

[reginaldlather]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170821193225

Steps to reproduce:

Received a webex meeting invite to my business account and accepted meeting/conference request.


Actual results:

The acknowledgement was sent via my personal(default) account and not my business account. Now someone whom I'm doing business with also has access to my personal email too.


Expected results:

Acknowledgement should have been sent form the account which received the request.

Comment 1

[[:MakeMyDay]]

To work around this problem, make sure you have configured one writable calendar per email identity and associate it with the respective email address.

Comment 2

[bintoro]

(In reply to [:MakeMyDay] from comment #1)
> To work around this problem, make sure you have configured one writable
> calendar per email identity and associate it with the respective email
> address.

Not working for me. Or am I doing it wrong? Changing the email address of a particular calendar (under the calendar's properties in Lightning) seems to have no bearing on the address that is sent out when accepting an invitation.

Comment 3

[[:MakeMyDay]]

Of cause, the effect is limited to the events in that calendar - make sure you do it for all your calendars (and at best, just one calendar per address). Caldav calendars may specify an email address for the calendar owner serverside - if this is the case and you haven't configured that address as an identity in TB, this might cause Lightning to fall back to the default address. Apart from that, there are other edge cases where it's currently technically impossible to detect the "right" email address to send a reply - this involves serverside moved emails to different accounts or invitations received as bcc. To overcome that to the extend possible is bug 475886 about.

Unless you hit such an edge case, please head over to support.mozilla.org to get help to sort out what to reconfigure in your TB/Lightning configuration.