...

...

The current status (updated 11/2006) is available through SVN \[http://svn.apache.org/repos/asf/jakarta/commons/proper/email/trunk/STATUS.html here\].

...

Recently fixed issues (last updated Feb

...

22 2007)

Bug fixes

email 1.0 doesn't handle HTML embedding or attachments correctly. This is really bad, and is reason enough for a 1.1 release.

_(Added in rev 510708)_ \[https://issues.apache.org/jira/browse/EMAIL-50 EMAIL-50\]: HTML mail doesn't display correctly (the issue says in Outlook 2000, but the display fails on every common mail client I tried). It's not an Outlook-specific error. A patch is available that fixes this and has been tested on several different clients; also, the new patch adheres properly to the MIME specs in RFC 2045-2049 where email 1.0 did not. The fix also resolves two other open issues:

• Wiki Markup
  \[https://issues.apache.org/jira/browse/EMAIL-28 EMAIL-28\]: HTML attachments don't work correctly.

• Wiki Markup
  \[https://issues.apache.org/jira/browse/EMAIL-52 EMAIL-52\]: Don't embed the same URL multiple times in the same email. \\

...

Character set fixes/support

email 1.0 provided limited support for different charsets, and it's generated four issues.

_(Added in rev 510275)_ \[https://issues.apache.org/jira/browse/EMAIL-1 EMAIL-1\]: Default email charset not used for text content. A patch has been uploaded that defines three different cases for this behavior and tests/fixes each.

_(Added in rev 510715)_ \[https://issues.apache.org/jira/browse/EMAIL-54 EMAIL-54\]: Propose a new Charset enum. The current patch uses the JDK 1.4 java.nio.charset.Charset class to validate user-supplied charset names. This removes the need for a separate enumeration of "supported" classes and greatly reduces the headache of maintaining the support as the JVM continues to evolve. This also incorporates fixes for two other open issues:

• Wiki Markup
  \[https://issues.apache.org/jira/browse/EMAIL-25 EMAIL-25\]: Can't set charset for a single address.

• Wiki Markup
  \[https://issues.apache.org/jira/browse/EMAIL-14 EMAIL-14\]: Support a couple specific charsets. \\

...

Build fixes

...

/enhancements

email 1.0 doesn't handle HTML embedding or attachments correctly. This is really bad, and is reason enough for a 1.1 release.

_(Added in rev 510706)_ \[https://issues.apache.org/jira/browse/EMAIL-5062 EMAIL-5062\]: HTMLEnforce mail doesn't display correctly (the issue says in Outlook 2000, but the display fails on every common mail client I tried). It's not an Outlook-specific error. A patch is available that fixes this and has been tested on several different clients; also, the new patch adheres properly to the MIME specs in RFC 2045-2049 where email 1.0 did not. The fix also resolves two other open issues:1.4 source/bytecode in ant and maven 1 builds

...

...

\[https://issues.apache.org/jira/browse/EMAIL-28 EMAIL-28\]: HTML attachments don't work correctly.

_(Added in rev 510704)_ \[https://issues.apache.org/jira/browse/EMAIL-

...

63 EMAIL-

...

63\]: 

...

Submitted 

...

maven 

...

2 pom.xml.

Open issues (last updated Feb 22 2007)

These are the currently open issues organized according to category.

New feature requests

\[https://issues.apache.org/jira/browse/EMAIL-35 EMAIL-35\]: Allow [DataSources] to be directly embedded in [HtmlEmails]. Patch available.

...

(BenSpeakmon) I'm not convinced that it's useful to support attaching one subclass of Email to another subclass – that is, the original report creates an HtmlEmail and then wants to attach that to a MultiPartEmail. The current design of commons-email would make this very tricky, but aside from that I don't see the general usefulness of doing so. One case where I do see a use for this would be when the user wants to attach a MimeMessage he got from somewhere (like a server or a filestore) to a subclass of Email. This would mean adding MultiPartEmail.addMimeMessage() methods which would then be attached like the current addPart() methods. (We'd have to have different names, since MimeMessage doesn't share a common interface ancestor with MimeMultipart.) I'll look into this option.

Build fixes/enhancements

\[https://issues.apache.org/jira/browse/EMAIL-6264 EMAIL-6264\]: Enforce 1.4 source/bytecode in ant and maven 1 builds

\[https://issues.apache.org/jira/browse/EMAIL-63 EMAIL-63\]: Submitted maven 2 pom.xml.

\[https://issues.apache.org/jira/browse/EMAIL-64 EMAIL-64\]: use a different test email server from a live project, not a dead one use a different test email server from a live project, not a dead one. Patch available to use wiser from the \[http://subethasmtp.tigris.org/ subethasmtp project\]. subethasmtp's maintainer has no interest in putting the JDK 1.4-compatible version into maven, so we'll have to handle that.

...

Release Plan

A commons-email 1.1 release is in the planning stages.