You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2019/07/11 12:57:00 UTC

[jira] [Closed] (JAMES-2811) DeletedMessageVault implemetation of retention

     [ https://issues.apache.org/jira/browse/JAMES-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tellier Benoit closed JAMES-2811.
---------------------------------

> DeletedMessageVault implemetation of retention
> ----------------------------------------------
>
>                 Key: JAMES-2811
>                 URL: https://issues.apache.org/jira/browse/JAMES-2811
>             Project: James Server
>          Issue Type: Sub-task
>            Reporter: Tellier Benoit
>            Priority: Major
>             Fix For: 3.4.0
>
>
> - calculating buckets for retention
> - delete buckets by BlobStore API
> - clean corresponding metadata in JAMES-2807
> If bucket period can not be divided by retention period (for example: bucket period = 1 month, retention period = 1.5 month). Then calculate possible buckets then delete messages matching retention criterion inside them.
> For the new implementation: maybe retention job doesn't need to use **vault.usersWithVault()** which is designed to fit with **mail repository version** in **DeleteByQueryExecutor** to perform retention. If can, we can remove that method and update the **DeleteByQueryExecutor**.
> Asa reminder, the retention will be performed through webadmin task (already implemented) triggered by some external scheduling mechanism.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org