Drafts can't be read in Thunderbird Daily.

STR:

1. Open the drafts folder of an e-mail account in the folder pane
2. click on a row in the message list

Expected:

The message reader shows the draft.

Actual:

Completely white message pane. The console shows the following error:

Uncaught (in promise)
Exception { name: "NS_ERROR_ILLEGAL_VALUE", message: "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsIMsgMessageService.messageURIToMsgHdr]", result: 2147942487, filename: "chrome://messenger/content/aboutMessage.js", lineNumber: 130, columnNumber: 0, data: null, stack: "displayMessage@chrome://messenger/content/aboutMessage.js:130:29\ndisplayMessage@chrome://messenger/content/about3Pane.js:2642:32\n_onSelect@chrome://messenger/content/about3Pane.js:1986:23\nhandleEvent@chrome://messenger/content/about3Pane.js:1952:14\nonSelectionChanged@chrome://messenger/content/tree-view-listbox.mjs:1565:10\n_selectSingle@chrome://messenger/content/tree-view-listbox.mjs:1399:12\nconnectedCallback/<@chrome://messenger/content/tree-view-listbox.mjs:819:14\n", location: XPCWrappedNative_NoHelper }
aboutMessage.js:130

Works for me.

I did a screen recording showing the problem:
https://www.youtube.com/watch?v=FM_2f4dFN4k

Works for me as well. Tried -safe-mode?

Yes, same issue in Safe Mode. Thunderbird 102 is not affected.
Tested on macOS 13.2 and a localized build of Thunderbird Daily (German).

But it seems that only my Gmail account is affected. I tested again on another mail account and it worked. Then I tested a new draft on my Gmail account and I got the same error.

Unfortunately mozregression is completely broken for Thunderbird on macOS 13 (bug 1817001) so I manually tested older builds, all with new profile. It works until the last build with Supernova disabled and is broken since the first build with Supernova enabled.

Let me know if there is something else I should test.

WFM also on macOS 12

It's very interesting that it's not reproducible for any of you. I now tested on a different MacBook (Intel instead of M1, macOS 13.1 instead of 13.2, this time an en-US build instead of a DE build, again with a new Thunderbird profile) and there is exactly the same issue.

add [supernova] to whiteboard 20230217_1525

Is it possible that the problem is the umlaut in the folder name "Entwürfe" (that's the German term for "Drafts")? Since the error is the following:

Exception { name: "NS_ERROR_ILLEGAL_VALUE", message: "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE)

… in aboutMessage.js:130 I used the debugger to read the value. The "uri" in MailServices.messageServiceFromURI(uri) is:

"imap-message://soeren.hentzschel%40googlemail.com@imap.gmail.com/[Google Mail]/Entwürfe#2227"

And this looks wrong where the umlaut is. This would also explain why you all can't reproduce the issue since I guess you don't have an umlaut in the name of the drafts folder.

If I execute the following code in the console I throws the same error:

let uri = 'imap-message://soeren.hentzschel%40googlemail.com@imap.gmail.com/[Google Mail]/Entwürfe#2227';
let messageService = MailServices.messageServiceFromURI(uri);
let gMessage = messageService.messageURIToMsgHdr(uri);

But if I change it to the following there is no longer an error and I get a valid "gMessage":

let uri = 'imap-message://soeren.hentzschel%40googlemail.com@imap.gmail.com/[Google Mail]/Entwürfe#2227';
let messageService = MailServices.messageServiceFromURI(uri);
let gMessage = messageService.messageURIToMsgHdr(uri);

And while the visible folder name for my other accounts is "Entwürfe" as well, the internal URI does not contain an umlaut, it's for example "imap-message://kontakt%40soeren-hentzschel.at@89.58.61.70/Drafts#6". That explains why I can only reproduce with my Gmail account.

mailnews.imap.jsmodule=true (default since 2023-02-22, Daily only) fixes this issue, but it causes bug 1818253 and bug 1818272 for Gmail and, more critical, bug 1818247 for Yahoo! Mail.

Is it possible that the problem is the umlaut in the folder name "Entwürfe" (that's the German term for "Drafts")?

That seems quite likely to me. I guess I'll be signing up for a new Gmail account in German.

I can't reproduce anymore.

Oh good, that's one less thing to worry about! It does make me wonder what changed though…

Hi Geoff,

I did run mozregression with forced mailnews.imap.jsmodule=false to find out what fixed this issue. It was fixed by bug 1818676.