Amichai Rothman commented on JAMES-2656:

Backporting it would be great as well!

As long as it doesn't break anything for users on a minor release (i.e. maybe 
don't make it the default yet?) - but if it's present and configurable, people 
can start using it!

> 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

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

Reply via email to