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)" <ji...@apache.org> on 2019/03/28 03:33:00 UTC
[jira] [Closed] (MAILBOX-388) [DeletedMessagesVault] retention
implementation
[ https://issues.apache.org/jira/browse/MAILBOX-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tellier Benoit closed MAILBOX-388.
----------------------------------
> [DeletedMessagesVault] retention implementation
> -----------------------------------------------
>
> Key: MAILBOX-388
> URL: https://issues.apache.org/jira/browse/MAILBOX-388
> Project: James Mailbox
> Issue Type: New Feature
> Reporter: Trần Tiến Đức
> Priority: Major
> Fix For: 3.4.0
>
>
> After MAILBOX-381
> DeletedMessagesVault also need to support delete mails after they expire, an able to configure Retention Period. DeletedMessagesVault APIs need to be added:
> {code:java}
> interface DeletedMessagesVault {
> Task deleteExpiredMessagesTask();
> }{code}
> - You will need to create `DeletedMessagesVaultConfiguration` which is an immutable object and carries a property of retention period.
> - Your DeletedMessagesVault impl should have a property of `DeletedMessagesVaultConfiguration`, to use it while performing search expired messages in `deleteExpiredMessagesTask()`
> - Update your contract and tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org