HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
would be great if Jakarta mail API is used so we can have it inline with mail functionality in our Domino apps
I am the author of Squirrel for Domino (https://squirrel.k43.ch). This Java server addin reads messages from POP3 and IMAP servers and transfers these messages to the Domino user.
Squirrel requires the current Jakarta mail API to support OAuth 2.0 authentification aginst the POP3/IMAP hosts (e.g. Microsoft 365). The currently distributed mail.jar in /ndext/ is based on javax.mail.* and is outdated. It does not support OAuth 2.0 and is no longer supported. Therefore, I need to include the newer jakarta.mail.* API with Squirrel.
My request is that Domino and Traveler should be updated to use the current jakarta.mail.* and jakarta.activation.* package (API compatible with javax.mail) to prevent class conflicts with other applications using mail APIs (server addins, java agents, etc) as the Java classes are loaded and shared between all JVM applications. Squirrel (and other Java applications using the current mail APIs) are not able to run on the same Domino server with HCL Traveler which uses javax.mail.*.
Thank you.
Andy Brunner
Can you share a specific use case where Traveler's current Java Mail API caused an issue? What application or functionality are you trying to enable that requires Jakarta Mail?