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 "Amichai Rothman (Jira)" <se...@james.apache.org> on 2023/01/29 06:26:00 UTC
[jira] [Commented] (JAMES-2656) Implement a JPAMailRepository
[ https://issues.apache.org/jira/browse/JAMES-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681687#comment-17681687 ]
Amichai Rothman commented on JAMES-2656:
----------------------------------------
It's been 4+ months since the PR was merged... is there an ETA on when this will be released?
> Implement a JPAMailRepository
> -----------------------------
>
> Key: JAMES-2656
> URL: https://issues.apache.org/jira/browse/JAMES-2656
> Project: James Server
> Issue Type: New Feature
> Components: jpa, MailStore & MailRepository
> Affects Versions: master, 3.2.0
> Reporter: Benoit Tellier
> Priority: Major
> Labels: feature
> Time Spent: 7.5h
> Remaining Estimate: 0h
>
> Mail Repository allows the long term storage of emails.
> They are currently used for several uses:
> - Keep mail triggering processing errors (kinda dead-letter)
> - Keep user non-displayed SPAM
> - Storage medium for Data Leak Prevention
> Currently, as highlishted by Garry Hurley on the user mailing list, JPA users are forced to rely on a file based implementation, which is clearly not optimal.
> We should implement a JPAMailRepository in `server/data/jpa`. It should be tested against the `MailRepositoryContract`.
> If any help is needed, please don't hesitate to reach us on Gitter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org