1604935 - "A unique identity matching the From address was not found", when some accounts refence the same email address

Status: UNCONFIRMED

(Thunderbird :: Message Compose Window, defect)

Description

[Lukas Ruf]

Attachment: 2019-12-18_messagee_pop-up.png

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

Steps to reproduce:

I have several email accounts.
In some of them, I make use of the same eamail adresses

Actual results:

Since upgrading Thunderbird, TB complains that it would not be possible to find a unique account.

Expected results:

The should be a check-box to inform TB that I don't care about that mapping and that I should not be bothered again by that pop-messaage.

Comment 1

[Lukas Ruf]

If I can disable these warning, I am glad with it.

Comment 2

[Wayne Mery (:wsmwk)]

upgrade from 60 to 68?

Comment 3

[Lukas Ruf]

Sorry, if I mistyped anthing.

I am using 68.3.1 on Windows 10.

Comment 4

[Wayne Mery (:wsmwk)]

Right. I was unclear. We know you are on version 68. What we need to know is, what version where you using prior to this breaking - 60 or 68.something ?

Also, do you use the conversations addon?

Comment 5

[Magnus Melin [:mkmelin]]

That message isn't part of Thunderbird code. Must be some add-on.

Comment 6

[Jorg K (CEST = GMT+2)]

That message isn't part of Thunderbird code. Must be some add-on.

Hmm, did you check the code base? I actually reviewed the bug introducing this:
https://searchfox.org/comm-central/rev/f08bdc6ce3c909f9f377f8ad74aae7c2425e9dc8/mail/locales/en-US/chrome/messenger/messengercompose/composeMsgs.properties#482

Lukas, this can happen if you share an IMAP inbox with many differently configured clients. We'd need to know your exact setup.

Comment 7

[Lukas Ruf]

This is right. My setup is as follows:

• One dovecot imap-server & one davical CalDAV-server
• One primary workstation with Thunderbird/Lightning
• A bunch of iOS / Android smartphones and tablets accessing the same IMAP-Server accounts.

Particular with my setup is, that I make use of a specific account for my mobiles. Reason: I am no able to manage the 150+ emails I received per workday on my mobiles; hence I forward selected emails to my mobile-specific account too. On TB, I access that imap mailbox besides my "regular" mailbox to benefit from the ease of handling. To both, the specific and the regular mailboxes, the same email address is assigned, which obviously leads to the error message.

Thus: I understand the message -- but why does Thunderbird bother me with that message -- I have been running exact this setup since 2014 without any problem. Has there been any change that makes Thunderbird dependent on the label (=email address) which was not there before?
(This is the reason why I tagged my but report by the subject in use).

Alternatively, is there a "reminder function" which keeps Thunderbird warning me -- but does not remind me of that fact more than once?

Thanks in advance.

Comment 8

[Jorg K (CEST = GMT+2)]

I still don't understand what happened here. The message in question and the functionality were implemented in bug 394216.

Before that bug, what happened was this. If you saved a draft with different (Thunderbird) clients into the same IMAP Drafts mailbox, when editing the draft again on a different client, it used the identity from the X-Identity-Key header, and that could have corresponded to a different e-mail address on a different client. Simple example:

Client 1:
[e-mail] - ID1
[e-mail] - ID2

Client 2:
[e-mail] - ID2
[e-mail] - ID1

If you save a draft from client 1 as [e-mail] and then edited again with client 2, it would have gone out as [e-mail].

That's changed now in TB 60 already. We now try to match the TB identity based on the e-mail address, hence the message if no corresponding address is found.

So I still need more detail of what exactly is happening in your case. And the summary of the bug is confusing, too: "Unclear conception regarding mapping a reply to a unique email address" - what reply?

Comment 9

[Lukas Ruf]

On my PC I run one TB-instance with several IMAP eMail-Accounts. The following setup shows my use (I use the same email address, [e-mail]) with both Accounts, with Account 1, I use the same email address twice with different identities to ease the handling of meta information like signatures.

Account 1:
[e-mail] - ID1
[e-mail] (short sig) - ID2
[e-mail] - ID3

Account 2:
[e-mail] - ID1

(Account 2 is primarily used to do maintenance of all the emails on my mobile devices since I prefer TB on a large screen).

Is is possible for TB to do a match of the TB identity per Account?

While I understand your response, thanks for that, I would like to get rid of that warning message -- but keep the setup with the different IDs.

Comment 10

[Jorg K (CEST = GMT+2)]

Sorry, this is still not clear. What action exactly causes the notification? Can you just write the steps down. Can you also clarify your example. Do you have the same e-mail signature [e-mail] for account 1 and 2?

For the record, the code trying to find the correct identity is here:
https://searchfox.org/comm-central/rev/2b1d1a5035c455aad12f56fdadab3bb748d7e44d/mail/components/compose/content/MsgComposeCommands.js#3104-3195

Comment 11

[Wayne Mery (:wsmwk)]

Lukas?

(In reply to Jorg K (CEST = GMT+2) from comment #10)

Sorry, this is still not clear. What action exactly causes the notification? Can you just write the steps down. Can you also clarify your example. Do you have the same e-mail signature [e-mail] for account 1 and 2?

For the record, the code trying to find the correct identity is here:
https://searchfox.org/comm-central/rev/2b1d1a5035c455aad12f56fdadab3bb748d7e44d/mail/components/compose/content/MsgComposeCommands.js#3104-3195

Comment 12

[Lukas Ruf]

Yes, for various process-related reasons, I do have multiple accounts in TB that have the same e-mail address assigned to them.

Each TB account has its own IMAP-serverside account.

Regarding the exact steps:
In one TB-Account, a start writing an email or a reply
When I save the draft message, restart TB, and the continue editting the email in the same TB-account, the aforementioned error message pops up

My interpretation
Since I do continue editting a previously saved draft message in the same TB-account, TB should limit the scope of its search for an email address to the specific TB-account -- and thus not run into this problem, and display the error message.