Subject line is replaced by dots upon saving drafts or templates
I create a new blank message, type something into the subject field, save, and close the window. My drafts folder displays the new message, but instead of my subject line there are three dots. When I open the draft again, the subject line indeed consists of three dots. Replacing the dots again by some text does not solve the problem, after saving it will still have three dots. Thus, I cannot save subject lines in drafts. The same for templates. What's going wrong here?
This is on Windows 10, newest Thunderbird release version 78.9.1 (32-bit).
Chosen solution
This is a known problem when e2ee is set up for the account, and when you open the saved draft in a new window. The original subject is not restored in that case.
As a workaround, select the saved draft in the thread pane and toggle the message pane with F8. This will restore the subject. Press F8 again to turn off the message pane.
I'd hope that this will be fixed at some point, but we're not there yet.
Read this answer in context 👍 1All Replies (3)
Please restart Thunderbird in SAfe Mode and see if the issue is still present. https://support.mozilla.org/en-US/kb/safe-mode-thunderbird
Please report back on results.
IF the problem still exists then.... Perhaps it would be a good idea, if you were to add some additional information to this bug. You will need to register in order to post comment. The original person was using Linux but are using Windows, so this is not OS specific and tha is the sort of information they would need. Also, please mention whether this is in an imap or pop account. https://bugzilla.mozilla.org/show_bug.cgi?id=1696515
Seçilmiş Həll
This is a known problem when e2ee is set up for the account, and when you open the saved draft in a new window. The original subject is not restored in that case.
As a workaround, select the saved draft in the thread pane and toggle the message pane with F8. This will restore the subject. Press F8 again to turn off the message pane.
I'd hope that this will be fixed at some point, but we're not there yet.
@Toad-Hall: thanks! The issue seems to be exactly what christ1 describes, so it is already known and reportet. @christ1: thank you, the F8 works, this seems to be it.