Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move from JavaMail to JakartaMail #131

Merged
merged 7 commits into from
Sep 20, 2023
Merged

Move from JavaMail to JakartaMail #131

merged 7 commits into from
Sep 20, 2023

Conversation

philmcmahon
Copy link
Contributor

What does this change?

Most of the work in this PR was done by @srbd

JavaMail has reached end of life and has been replaced by jakarta mail. This PR introduces jakarta mail to Giant, including the Mbox provider JAR file which has to be manually compiled and checked in (see https://eclipse-ee4j.github.io/angus-mail/Mbox-Store)

Unfortunately, we've yet to succesfully ingest an mbox file using either jakarta mail or the latest version of java mail. Our assumption is that MBOX is a poorly defined format, so it's hard to get something that works for all MBOX files. The motivation for this PR isn't to actually fix anything :( but I have tested it with a normal .EML file which it appears to handle without any problems - so it shouldn't be making anything worse!

How to test

Tested on playground, seems to exhibit the same behaviour as JavaMail..!

How can we measure success?

We'll benefit from future updates to jakarta mail

Copy link
Contributor

@srbd srbd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 LGTM thanks for finishing off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants