搜索 | 用户支持

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

详细了解

IMAP Folder retention policy does not work

  • 3 个回答
  • 9 人有此问题
  • 26 次查看
  • 最后回复者为 Wayne Mery

more options

On an folder of any IMAP account, I used Properties => Retention policy and defined a limit of 10 days.

Expected: A message should be deleted local as well as on the server, after 10 days. Result: Does not work, unless I manually Compact each folder.

Is there a way to compact all folders, through all accounts, or at least all folders of an account. This is about IMAP only. Under POP3 all works fine.

Grtnx. Ruud Uphoff

On an folder of any IMAP account, I used Properties => Retention policy and defined a limit of 10 days. Expected: A message should be deleted local as well as on the server, after 10 days. Result: Does not work, unless I manually Compact each folder. Is there a way to compact all folders, through all accounts, or at least all folders of an account. This is about IMAP only. Under POP3 all works fine. Grtnx. Ruud Uphoff

被采纳的解决方案

Compact doesn't really have anything to do with retention policy - they work independent, on different schedulers.

There are some bug reports - https://mzl.la/2xaGLJe - but I don't have time to go through them. But perhaps you can view some and pick one that fits your issue and offer some new helpful advice there

定位到答案原位置 👍 0

所有回复 (3)

more options

Right click an account and select Compact to compact that account. Select File-Compact to do all accounts.

There are some settings in Account settings that define the action when you delete a message. You might check those.

I am on an Android tablet so no access to Thunderbird and I do not remember he exact location.

more options

Compacting all folders does not apply the retention policy of all folders. like compacting each folder separately does .

The problem is the not working retention policy on IMAP. And I have different sub folders, each with a different retention policy.

more options

选择的解决方案

Compact doesn't really have anything to do with retention policy - they work independent, on different schedulers.

There are some bug reports - https://mzl.la/2xaGLJe - but I don't have time to go through them. But perhaps you can view some and pick one that fits your issue and offer some new helpful advice there