mid URLs in email bodies do not resolve
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
People
(Reporter: nathanielmbeaver, Unassigned)
References
Details
(Whiteboard: [fixed by bug 1723645])
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0
Steps to reproduce:
- Send an email to myself containing this mid URL:
mid:f8051cc8637cf3ff79661f382.63e939ed07.20201229132457.576ef659f7.6f044b64@mail65.atl231.mcsv.net
-
Open the message containing the mid URL.
-
Click on the mid URL in the message body.
Actual results:
The message corresponding to the mid URL did not open. I got this console output:
IPDL protocol error: Handler returned error code!
###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetFutureClientSource Processing error: message was deserialized, but the handler returned false (indicating failure)
Expected results:
The message corresponding to the mid URL should open, in this case an email on 2020-12-29 from noreply@thunderbird.net with subject "New Year, New Inbox".
I know that this should work because when I open it from the command line like this, it opens the corresponding message in a new tab just fine:
thunderbird mid:f8051cc8637cf3ff79661f382.63e939ed07.20201229132457.576ef659f7.6f044b64@mail65.atl231.mcsv.net
Similarly, when I open it with xdg-open, it opens just fine also:
xdg-open mid:f8051cc8637cf3ff79661f382.63e939ed07.20201229132457.576ef659f7.6f044b64@mail65.atl231.mcsv.net
| Reporter | ||
Comment 1•4 years ago
|
||
Also happens with HTML emails
Comment 2•4 years ago
|
||
It's supposed to be fixed by bug 1724292, but I don't know why it doesn't work on 91. From what I see,
Cc["@mozilla.org/uriloader/content-handler;1?type=application/x-mid"].createInstance(Ci.nsIContentHandler) works on trunk but not on 91, that means somehow MidContentHandler is not registered correctly on 91.
| Reporter | ||
Comment 3•4 years ago
|
||
Thanks for the update, I can confirm that internal mid links work fine for me with the 94.0b2 beta.
Comment 4•4 years ago
|
||
91.2.1 will include the fix, thanks.
Updated•4 years ago
|
Description
•