為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Thunderbird does not delete save drafts after email is sent

  • 3 回覆
  • 5 有這個問題
  • 12 次檢視
  • 最近回覆由 andover1

more options

Why is it that Thunderbird 102.13 keeps the drafts around for messages that I have already sent? It is darn frustrating to have to go into my IMAP account and get rid of drafts that TB automatically saved for messages that I have sent hours or days ago.

Why is it that Thunderbird 102.13 keeps the drafts around for messages that I have already sent? It is darn frustrating to have to go into my IMAP account and get rid of drafts that TB automatically saved for messages that I have sent hours or days ago.

被選擇的解決方法

This happens because you have Thunderbird to save drafts periodically. Each save becomes a separate draft. A possible workaround is to set your draft folder to use local storage.

從原來的回覆中察看解決方案 👍 1

所有回覆 (3)

more options

選擇的解決方法

This happens because you have Thunderbird to save drafts periodically. Each save becomes a separate draft. A possible workaround is to set your draft folder to use local storage.

more options

Thanks. I guess that is better it is just that I would of preferred the ability to continue to edit a saved draft on my phone in the mail app on the phone if I am away from my desktop. At least now I do not have all the saved copies in TB after I send the email.

more options

(Thunderbird 115.3.1 64bit, Windows 10) Had the same issue and found a workaround in the bugtracker: https://bugzilla.mozilla.org/show_bug.cgi?id=549274#c35 where it says one should not point email drafts and templates to the same folder but two distinct ones instead. I initially changed it to point both to the same drafts folder but that caused the problem. After resetting the folders to distinct ones Thunderbird handles saving email drafts and deleting them after sending the email perfectly fine again. It's just a pity that this bug seems to exist for over 14 years...