commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Siegfried Goeschl <>
Subject [VOTE] Release of commons-email-1.3 based on RC3
Date Fri, 04 May 2012 15:31:41 GMT

I would like to call a vote from commons-email-1.3 based on RC3

Changes in this version include:

New features:

o Update the current trunk to be binary compatible with the 
commons-email-1.2 release.  Issue: EMAIL-111. Thanks to Florian Pirchner.
o Added unit test to ensure that parsing the broken mime message does 
not cause an OutOfMemoryException.  Issue: EMAIL-110. Thanks to Thomas 
o HtmlmageEmail should support class path resources  Issue: EMAIL-108. 
Thanks to Elisabeth Kasimir, Alexander Kasimir.
o Added a MultiPartEmail.attach(File) method since attaching a file is a 
simple and common.
o Added MimeMessageParser and MimeMessageUtils.

Fixed Bugs:

o DataSourceFileResolverTest fails under IBM JDK 1.4 and 1.6 running on 
Windows.  Issue: EMAIL-112. Thanks to Peter Kofler.
o Maven Site fails with error in Checkstyle configuration.  Issue: 
EMAIL-113. Thanks to Peter Kofler.
o The patch actually broke sending emails over a secured connection - 
"MAIL_SMTP_SSL_ENABLE" activation. Tested the functionality using GMail, 
GMX and Office365 so the code is at least working for a couple of 
existing SMTP servers. Also added 'sslCheckServerIdentity' including 
setter and getter. Also added a chapter regarding "Security" to the user 
manual.  Issue: EMAIL-105. Thanks to Siegfried Goeschl.
o Added mime.types to META-INF - the definition is actually found in 
activation.jar but did not work.  Issue: EMAIL-107. Thanks to Claus 
Polanka, Michael Jakl.
o STARTTLS can be used even without authenticator.  Issue: EMAIL-106. 
Thanks to Bruno Harbulot.
o Clarified the meaning of setTLS() which actually sends a "STARTTLS" 
command from the client to the SMTP server. Please note that some 
"protected" variables were renamed which could break existing code. 
Issue: EMAIL-105. Thanks to Bruno Harbulot.
o Fixed HtmlEmail embed toLowerCase bug with Turkish locale.  Issue: 
EMAIL-102. Thanks to Okan Özeren.
o Specified Content-ID is now used when embedding a File object in an 
HtmlEmail.  Issue: EMAIL-101. Thanks to Andrew Starodub.
o Restore Java 1.4 compatibility.
o Throwing an IllegalStateException when setting mail session properties 
for an already created mail session because the settings would be 
ignored. Please note that this change could potentially break existing 
(but invalid) code.  Issue: EMAIL-96.
o Encoding and folding of headers is now done by commons-email.  Issue: 
EMAIL-98. Thanks to Mario Daepp.
o The default connection timeout is set to a reasonable default value of 
60 seconds.  Issue: EMAIL-100. Thanks to David Parks.
o Moving the various constants from 'EMail' to 'EmailConstants'
o All setters are returning "this" to simplify building an email. 
Issue: EMAIL-76. Thanks to Yu Kobayashi.
o Adding ImageHtmlEmail to create HTML emails with embedded images 
either downloaded from HTTP or from the local file system.  Issue: 
EMAIL-92. Thanks to Dominik Stadler.
o Calling buildMimeMessage() before invoking send() caused duplicated 
mime parts for HtmlEmail. The implementation now enforces that an email 
can be only used once and throw an exception when multiple invocations 
of buildMimeMessage() are detected.  Issue: EMAIL-95.
o Incorrect SMTP Port number shown in error message when an email fails 
to send due to a blocked port and SSL is used.  Issue: EMAIL-91. Thanks 
to Kevin Lester.

The files:

The artifacts are deployed to Nexus [1] (and [2]).

The tag:

The site:

Additional Notes:

o the RC is binary compatible to commons-email-1.2 whereas the remaining 
Clirr warnings stem from moving constants to an interface

Please take a look at the commons-email-1.3 artifacts and vote!

Please note:
This vote is "majority approval" with a minimum of three +1 votes (see [3]).

[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released, 
and why..............

Thanks in advance,

Siegfried Goeschl


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message