It's ok now, the key has been add.

François
[email protected]
[email protected]

Le 21/07/2026 à 13:10, Markus Jung a écrit :
-1 for now, the key is not the one in https://dist.apache.org/repos/dist/release/geronimo/KEYS

should be an easy fix though for any PMC member ;)


Thanks

Markus

On 7/21/26 11:35, Richard Zowalla wrote:
Hi,

As discussed on the other mail thread and Slack, I act as a release manager this time although I am not part of the PMC. The final steps after a potential successful vote need to be done by a PMC member.

Nevertheless, I would like to call a vote on releasing Apache Geronimo Mail 1.1.0 - our implementation of the Jakarta Mail 2.1 specification.

Notable changes in this release:
       • [GERONIMO-6834] - geronimo-jakartamail_2.1_spec (1.0.0-M1) does not pass Jakarta Mail TCK SigTests for Java 11      • [GERONIMO-6884] - Jakarta mail behaves different from eclipse.angus      • [GERONIMO-6851] - The implementation for mail.mime.parameters.strict parameter is missing in jakarta\mail\internet\ParameterList.java class of geronimo-mail_2.1_spec-1.0.0-M1.jar in TomEE 9.1.0      • [GERONIMO-6835] - Fix Jakarta Mail TCK 2.0.1 for Geronimo Jakarta Mail Impl
     • [GERONIMO-6885] - Setup Mail TCK
     • [GERONIMO-6886] - Ensure to flush the buffered output stream introduced in GERONIMO-6882      • [GERONIMO-6887] - Include the relocated mime4j classes in the geronimo-mail_2.1_mail bundle
     • [GERONIMO-6888] - Migrate to JUnit 5
     • [GERONIMO-6889] - Upgrade to apache-mime4j-core 0.8.14
     • [GERONIMO-6890] - Raise build target to Java 11 of Geronimo Mail
     • [GERONIMO-6891] - Fix IMAPFolder.renameTo reporting failure after a successful rename      • [GERONIMO-6892] - IMAP APPEND used to deadlock because the client never flushes the literal announcement      • [GERONIMO-6893] - MessageCountListeners are never notified - Folder queues MessageCountEvents to the MessageChangedListener list      • [GERONIMO-6894] - Flags.retainAll adds flags from the argument and removes user flags despite Flags.Flag.USER      • [GERONIMO-6895] - Folder.fetch() fails on RFC-strict servers - header names emitted outside the BODY.PEEK[HEADER.FIELDS] section brackets      • [GERONIMO-6896] - getContentLanguage() throws NPE for IMAP messages whose BODYSTRUCTURE has no language field      • [GERONIMO-6897] - Folder.create() sends the uninitialized hierarchy separator, creating a mailbox named "name\0"      • [GERONIMO-6898] - store.getDefaultFolder().list() returns empty when the server hierarchy delimiter is not '/'      • [GERONIMO-6899] - Single-message Message.setFlags() never fires MessageChangedEvent      • [GERONIMO-6900] - Folder.close(false) loses \Deleted messages - use UNSELECT when the server supports RFC 3691      • [GERONIMO-6901] - Failed Folder.open() leaks the pooled connection, breaks Store.close() and hides FolderNotFoundException      • [GERONIMO-6902] - Folder.expunge() always returns an empty array - EXPUNGE responses extracted under the wrong keyword      • [GERONIMO-6903] - IMAP response parser drops the byte following a bare CR, corrupting the stream      • [GERONIMO-6904] - A garbled IMAP response leaves the connection poolable and poisons later commands      • [GERONIMO-6905] - IMAP response codes in brackets (PERMANENTFLAGS, UIDVALIDITY, UIDNEXT, UNSEEN) are never parsed      • [GERONIMO-6906] - Spec is missing the Jakarta Mail 2.1 API additions      • [GERONIMO-6907] - MIME handling deviates from the Jakarta Mail 2.1 spec


Source release (with .asc and .sha512):
https://dist.apache.org/repos/dist/dev/geronimo/javamail/1.1.0/

Maven staging repository:
https://repository.apache.org/content/repositories/orgapachegeronimo-1182/

Git tag:
https://github.com/apache/geronimo-mail/releases/tag/geronimo-mail_2.1_parent-1.1.0
62b24797c538e90a3854d31b2562cee2333a8a3e

Release verification: the build is green on JDK 21 and the full Jakarta
Mail 2.1 TCK passes (321/321) against these artifacts.

KEYS file:
https://downloads.apache.org/geronimo/KEYS

Please review and vote. The vote is open for at least 72 hours.

[ ] +1 Release these artifacts
[ ] +0 No opinion
[ ] -1 Do not release, because ...

Thanks,
Richard

Reply via email to