为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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...