[
https://issues.apache.org/jira/browse/JAMES-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681940#comment-17681940
]
Benoit Tellier commented on JAMES-2656:
---------------------------------------
Hello Amichai,
I understand your needs, but we are a rather small communities and running an
Apache release process is a long process. Help to smooth the process is
welcome, don't hesitate to further enage with the community to help getting a
more frequent release schedule ;-)
That being said, we are finalizing details on James 3.8.0 release, which should
happen in the next few months.
In the meantime we could backport this work to 3.7.x which should be easier to
release.
> 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-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
