0N/A NOTES
0N/A =====
0N/A
121N/A JavaMail(TM) API ${mail.version} release
0N/A ------------------------------
0N/A
121N/AWelcome to the ${mail.version} release of the JavaMail API implementation.
0N/A
0N/APlease refer to CHANGES.txt for a list of the changes since the
0N/Aprevious release.
0N/A
324N/APlease see the FAQ at http://www.oracle.com/technetwork/java/javamail/faq/
0N/A
0N/AProtocol Providers
0N/A------------------
0N/A
0N/AThe JavaMail API jar file "mail.jar" includes the full JavaMail API
479N/Aimplementation and the Sun protocol providers - IMAP, SMTP, and
0N/APOP3. The simplest way to use the JavaMail API is to just use the
0N/Amail.jar file and ignore the other jar files in this package.
0N/A
0N/AIn some cases it may be desirable to minimize the size of the JavaMail
0N/AAPI code used by an application (e.g., when downloading with an applet).
0N/AIn this case you might want to include the "mailapi.jar" file, which
0N/Aincludes *no* protocol providers, along with just the jar file for the
0N/Aprotocol provider you need. For example, an applet that only needs to
0N/Asend mail could use the "mailapi.jar" file and the "smtp.jar" file.
0N/A
0N/AAn important note when using the separate protocol provider jar files:
0N/A
0N/A- You can't mix and match the Sun protocol providers between different
0N/A releases of the JavaMail API. The Sun protocol providers depend on
0N/A implementation-specific utility APIs within the mailapi.jar file.
0N/A (Third party protocol providers that don't depend on these APIs
0N/A should work fine.)
0N/A
0N/A
479N/ANOTE: The Sun protocol provider documentation is available in javadoc format,
479N/A see docs/javadocs/index.html in the directory where you extracted
0N/A the JavaMail API zip file. This documentation describes how to
0N/A use features of the Sun protocol providers to directly access
0N/A some features of the SMTP, IMAP, and POP3 protocols that are
0N/A not otherwise supported by the standard JavaMail API.
0N/A
0N/A
479N/AGmail IMAP Provider
479N/A-------------------
479N/A
479N/AThis release includes an EXPERIMENTAL Gmail IMAP provider.
479N/ANormal use of Gmail is handled by the standard "imap" protocol
479N/Aprovider, but the new "gimap" protocol provider supports additional
479N/AGmail-specific non-standard features. See the javadocs for the
479N/Acom.sun.mail.gimap package for details. Note that the gimap.jar file
479N/Aneeds to be added to your CLASSPATH to use this new provider.
479N/A
479N/A
0N/ASASL Support
0N/A------------
0N/A
0N/AOn systems that support the Java SASL API (javax.security.sasl, JSR-28),
0N/Asuch as J2SE 5.0 and later, the IMAP provider can use the SASL API to
0N/Afind an appropriate authentication mechanism. The SASL API also allows
0N/Ayou to plug in support for custom authentication mechanisms. See The
0N/AJava SASL API Programming and Deployment Guide at
324N/Ahttp://download.oracle.com/javase/6/docs/technotes/guides/security/sasl/sasl-refguide.html
0N/Afor details on developing custom SASL mechanisms. See the javadocs for
0N/Athe com.sun.mail.imap package for the properties required to enable and
0N/Aconfigure SASL support.
0N/A
0N/A
0N/ADSN Support
0N/A-----------
0N/A
0N/AThis release of JavaMail includes EXPERIMENTAL support for creating
0N/Aand parsing Delivery Status Notifications, as defined by RFC 3462
0N/Aand RFC 3464. To make use of this support you need to include dsn.jar
0N/Ain your CLASSPATH along with mail.jar. See the javadocs for the
0N/Acom.sun.mail.dsn package for more details.
0N/A
121N/AThe DSN package also provides support for creating and parsing Message
121N/ADisposition Notifications, as defined by RFC 3798.
121N/A
0N/AThe APIs unique to this package should be considered EXPERIMENTAL.
0N/AThey may be changed in the future in ways that are incompatible with
0N/Aapplications using the current APIs.
0N/A
0N/A
185N/ANTLM Support
185N/A------------
185N/A
185N/AThis release of JavaMail includes EXPERIMENTAL support for the
185N/AMicrosoft NTLM authentication mechanism used by Exchange. See the
185N/Afile NTLMNOTES.txt for details.
185N/A
185N/A
185N/AOSGi Support
185N/A------------
185N/A
185N/AThe JavaMail jar files are now OSGi bundles. Please let us know
185N/Aof any problems using JavaMail with OSGi.
185N/A
185N/A
0N/AHow to submit bug reports
0N/A-------------------------
0N/A
0N/AIf you've found a bug, or if you just need help figuring out how to use
0N/Athe JavaMail API, please try to include the following information in
0N/Ayour message to us:
0N/A
0N/A - a program or code snippet that shows the problem
0N/A - the platform you are using
0N/A - the mail server (vendor name, version number) you are using
0N/A - your environment variable settings
0N/A - a stack trace, if appropriate
0N/A - a protocol trace, after turning on session debugging, if appropriate
0N/A
0N/AMost of the problems reported to us fail to include enough of the above
0N/Ainformation to allow us to diagnose your problem. It will save you and
0N/Aus time if you include this information in your first message to us.
0N/A
0N/ABy far the most common problems we see are:
0N/A
0N/AYour problem: Something doesn't work right when talking to my mail server.
0N/AOur response: Turn on session debugging and send us the protocol trace.
0N/A See the demo program documentation for how to turn on
0N/A session debugging for the demo programs. In your own
0N/A program, call "session.setDebug(true);".
0N/A
0N/AYour problem: javax.mail or javax.activation classes not found when compiling.
0N/AOur response: You didn't set CLASSPATH correctly to find mail.jar and
0N/A activation.jar. See README.txt.
0N/A
0N/AYour problem: NoSuchProviderException - No such provider for rfc822.
0N/AOur response: You unjar'ed mail.jar. Don't.
0N/A
0N/AYour problem: How do I create a message with an attachment?
0N/AOur response: Create a message with a MimeMultipart content. See the
0N/A sendfile.html and msgmultisendsample.java demo programs.
0N/A
324N/APlease check the FAQ at http://www.oracle.com/technetwork/java/javamail/faq/
0N/Abefore submitting bug reports.
0N/A
0N/ASend your bug reports to:
0N/A
276N/A javamail_ww@oracle.com
0N/A
0N/A
0N/A
0N/A
0N/AA list of the known limitations, bugs, issues:
0N/A----------------------------------------------
0N/A
0N/A1. This version of JavaMail will only work in applets when using
324N/A the Java(TM) Plug-in
324N/A (http://www.oracle.com/technetwork/java/index-jsp-141438.html),
121N/A which is part of the current Java Runtime Environment (JRE)
324N/A available from Oracle at:
324N/A http://www.oracle.com/technetwork/java/javase/downloads/index.html
0N/A
0N/A2. Internationalization. Parameter encoding in MIME headers, as
0N/A specified by RFC2231, *has* been implemented. Note that
0N/A this covers only certain special cases not covered by the MIME
0N/A specification. MIME specifies encoding of text in the Subject
0N/A and address headers, and JavaMail fully supports such encoding.
732N/A Some mailers don't support RFC2231.
0N/A
732N/A To disable RFC2231 support in parameter lists, set the System
0N/A properties mail.mime.encodeparameters and mail.mime.decodeparameters
732N/A to "false".
0N/A
0N/A3. We've received reports of IMAP authentication failures on the
0N/A Microsoft Exchange Server 5.5, enterprise edition. This is due to
0N/A a bug in the Microsoft server and the "Service Pack 1 for Exchange
0N/A Server 5.5" apparently fixes this server bug. The service pack can
0N/A be downloaded from the Microsoft website.
0N/A
0N/A4. Due to a problem in the Microsoft Exchange IMAP server, insufficient
0N/A number of bytes may be retrieved when reading big messages. There
0N/A are two ways to workaround this Exchange bug:
0N/A
0N/A (a) The Exchange IMAP server provides a configuration option called
0N/A "fast message retrieval" to the UI. Simply go to the site, server
0N/A or recipient, click on the "IMAP4" tab, and one of the check boxes
0N/A is "enable fast message retrieval". Turn it off and the octet
0N/A counts will be exact. This is fully described at
0N/A http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q191504
0N/A
0N/A (b) Set the "mail.imap.partialfetch" property to false. You'll have
0N/A to set this property in the Properties object that you provide to
0N/A your Session.
0N/A
0N/A5. Certain IMAP servers do not implement the IMAP Partial FETCH
0N/A functionality properly. This problem typically manifests as corrupt
0N/A email attachments when downloading large messages from the IMAP
0N/A server. To workaround this server bug, set the
0N/A "mail.imap.partialfetch"
0N/A property to false. You'll have to set this property in the Properties
0N/A object that you provide to your Session.
0N/A
0N/AServers tested with:
0N/A--------------------
0N/A
0N/A The IMAP implementation works with IMAP4 and IMAP4rev1 servers.
0N/A The current release has been tested with:
324N/A Oracle Beehive
121N/A Sun Java System Messaging Server version 7.0
0N/A UW IMAP4 server version 2003.339
0N/A Cyrus IMAP4 server version 1.6.19
810N/A Microsoft Exchange 2010
0N/A
0N/A Previous releases have been tested with:
0N/A Sun Java System Messaging Server version 5.2
121N/A Sun Java System Messaging Server version 6.3
0N/A Sun Internet Mail Server version 2.0, 3.2, and 4.0
0N/A Netscape Messaging Server version 3.01 and 4.1
0N/A Microsoft Exchange
0N/A Microsoft MCIS Mail Server
0N/A Lotus Notes
0N/A Software.com IMAP server
0N/A Qualcomm Worldmail
0N/A
0N/A The current release of the SMTP implementation has been tested with:
0N/A Sendmail version 8.13.8
324N/A Oracle Beehive
121N/A Sun Java System Messaging Server version 7.0
810N/A Microsoft Exchange 2010
0N/A
0N/A Previous releases have been tested with:
0N/A Sendmail version 8.6 and 8.9.1
0N/A Sun Java System Messaging Server version 5.2
121N/A Sun Java System Messaging Server version 6.3
0N/A Sun Internet Mail Server version 3.2 and 4.0
0N/A Netscape Messaging Server version 3.01 and 4.1
0N/A Microsoft Exchange
0N/A Microsoft MCIS Mail Server
0N/A Qualcomm Worldmail
0N/A
0N/AHow to give feedback
0N/A--------------------
0N/A
0N/APlease send your feedback to this email-address:
0N/A
276N/A javamail_ww@oracle.com
0N/A
732N/ACheck out our website at https://javamail.java.net.
0N/A
121N/AYou can also find help in the JavaMail forum:
121N/A
810N/A https://community.oracle.com/community/java/java-ee-java-enterprise-edition/javamail
121N/A
0N/A
0N/A------------------------------------------------------------------