Subject missing when I open .eml file
I use Thunderbird to open an eml file that I generate with X-Unsent: 1 and to: from: subject: and body. This has worked fine for prior versions of Thunderbird after installing the X-unsent add-on but after one of the recent updates when I open the .eml file the subject line is blank. I opened the same .eml file with another email client and the subject line is there.
The issue just started with the last update that I did. I am on 115.3.1 (64-bit).
Todas as respostas (7)
Lets see, support for this was added in version 91 from Bug 166541 after over 20 years in the wilderness.
So of course I have to ask the obvious question. When you open the EML in a text editor like notepad++ do you see a Subject: heading in the EML file.
Open the error console (ctrl+Shift+J) clear in by pressing the trash icon on the toolbar and then open the file. Are there any errors in the console related to opening the file?
The right thing is to start with the obvious. Here is what I see:
X-Unsent: 1 X-Sender: "xxxxxx" <xxx@xx.com> X-Receiver: "Email Send" <send@secure.com> MIME-Version: 1.0 From: "xxxxx xxxxx" <xxxx@***.com> To: "Email Send" <send@secure.***.com> Date: 6 Oct 2023 18:29:49 -0700 Subject: #006070 - 10.6.23 Content-Type: multipart/mixed;
boundary=--boundary_2_2be27d04-9bfc-4a09-9770-65b51227747f
I don't see any errors related to opening the file.
Alterado por floydsloat em
I don't see any error related to opening the file. Here is the section that includes the subject:
X-Unsent: 1 X-Sender: "xxxxxx" <***@xx.com> X-Receiver: "Email Send" <send@secure.***.com> MIME-Version: 1.0 From: "xxxxx xxxxx" <xxxx@xxxxx.com> To: "Email Send" <send@secure.***.com> Date: 6 Oct 2023 18:29:49 -0700 Subject: Methods #006070 - 10.6.23 Content-Type: multipart/mixed;
boundary=--boundary_2_2be27d04-9bfc-4a09-9770-65b51227747f
It may be a guess, but do all the subject have an # in them? I do think we are getting to the point of filing a bug report as this is a tool I have never heard of so it obviously has a very limited use case.
They do but taking the # out did not make a difference.
floydsloat said
They do but taking the # out did not make a difference.
So much for that bright idea.
I think file a bug report. Link here if you like to make up some of the background. Please also post a link to the bug here. I might like to follow along on this one. Despite never having heard of the option until now it does have possibilities.
There was already a bug report https://bugzilla.mozilla.org/show_bug.cgi?id=1856166
Thanks for your help, this was my first time using mozilla support.