Re: [angus-dev] Graph API implementation for Jakarta Mail

[Jason Mehrens <jason_mehrens@xxxxxxxxxxx>]

From what I can tell the TCK should be able to be run with a custom protocol.  The SMTP and IMAP values can be changed to load your provider. The quickstart instructions are a good starting point on running the TCK.

See:
1. https://github.com/jakartaee/mail-tck/blob/master/QuickStart.txt
2. https://github.com/jakartaee/mail-tck/blob/master/lib/ts.pluggability.jte

Jason

________________________________________
From: angus-dev <angus-dev-bounces@xxxxxxxxxxx> on behalf of István Verhás via angus-dev <angus-dev@xxxxxxxxxxx>
Sent: Wednesday, January 3, 2024 9:48 AM
To: angus-dev@xxxxxxxxxxx
Cc: István Verhás
Subject: Re: [angus-dev] Graph API implementation for Jakarta Mail

Hi Jason,

Thank you for your detailed response. I am sorry for the late answer but I had personal troubles in December.
I appreciate your opinions on how to start up. Until we make a decision I have a technical question.
What is the proposed way to make sure that our implementation is fully compatible with the Jakarta Mail 2.1 specification? Is the provided TCK capable of certifying it with a specific protocol implementation?
Is there any specific instruction on how to proceed?

Best regards,
Istvan



On Wed, Nov 22, 2023 at 6:16 PM Jason Mehrens <jason_mehrens@xxxxxxxxxxx<mailto:jason_mehrens@xxxxxxxxxxx>> wrote:
Verhás István,

Thanks for reaching out to the Angus Mail team!  Your SPI implementation sounds like a very neat project.  I assume this is using the Microsoft Graph API (https://learn.microsoft.com/en-us/graph/use-the-api) is that correct?

I don't think there are any new plans to included more providers in Angus Mail.  Lukas might be able to confirm that.

My concerns are:

1. Are how can we best maintain a new provider in the long run?  Is it best inside or outside of Angus Mail?
2. What type of release schedule do you expect the project to be on?
3. Should the first versions be released in its own repo and a later version be considered for contribution to Angus Mail?

If you do decide to publish it to its own repo then let us know so we can promote your SPI through the: https://eclipse-ee4j.github.io/angus-mail/ThirdPartyProducts

Jason

________________________________________
From: angus-dev <angus-dev-bounces@xxxxxxxxxxx<mailto:angus-dev-bounces@xxxxxxxxxxx>> on behalf of István Verhás via angus-dev <angus-dev@xxxxxxxxxxx<mailto:angus-dev@xxxxxxxxxxx>>
Sent: Tuesday, November 14, 2023 9:09 AM
To: angus-dev@xxxxxxxxxxx<mailto:angus-dev@xxxxxxxxxxx>
Cc: István Verhás
Subject: [angus-dev] Graph API implementation for Jakarta Mail

Hi,

We have worked on a project to connect our app to the Graph API using
the Jakarta Mail both to send and to receive emails. The
implementation is actually an SPI implementation for the Jakarta Mail.
We are going to release this library as an open source one, giving
back to the community. As far as we see we have two options. Either we
contribute this library to the Angus mail as a separate SPI specific
for Graph API or we can create a new open source project fully
separately as its own. Both have cons and pros. Before we decide the
way, our first question is whether would it be interesting for you to
contribute to the Angus mail at all?

--
Verhás István
Atlassian expert
email: istvan.verhas@xxxxxxxxxxx<mailto:istvan.verhas@xxxxxxxxxxx>
_______________________________________________
angus-dev mailing list
angus-dev@xxxxxxxxxxx<mailto:angus-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit https://accounts.eclipse.org


--
Verhás István
Atlassian expert
email: istvan.verhas@xxxxxxxxxxx<mailto:istvan.verhas@xxxxxxxxxxx>
[https://aday.news/site/assets/files/1035/220321_metainf_meetup_21_mailsignature_1.jpg]<https://meetup.meta-inf.hu/?lang=hu&utm_source=meta-inf-email&utm_medium=mailsignature&utm_campaign=atlassian-meetup-21>