Login | ViewVC Help
View File | Revision Log | Show Annotations | Download File | View Changeset | Root Listing
root/javautils/ViaThinkSoft Java Utils/lib/javamail-1.4.3/NOTES.txt
Revision: 7
Committed: Mon Jun 14 07:55:39 2010 UTC (10 years ago) by daniel-marschall
Content type: text/plain
File size: 8993 byte(s)
Log Message:
Java Mail komplett hinzugefĆ¼gt

File Contents

# Content
2 =====
4 JavaMail(TM) API 1.4.3 release
5 ------------------------------
7 Welcome to the 1.4.3 release of the JavaMail API implementation.
9 Please refer to CHANGES.txt for a list of the changes since the
10 previous release.
12 Please see the FAQ at http://java.sun.com/products/javamail/FAQ.html
14 Protocol Providers
15 ------------------
17 The JavaMail API jar file "mail.jar" includes the full JavaMail API
18 implementation and *all* the Sun protocol providers - IMAP, SMTP, and
19 POP3. The simplest way to use the JavaMail API is to just use the
20 mail.jar file and ignore the other jar files in this package.
22 In some cases it may be desirable to minimize the size of the JavaMail
23 API code used by an application (e.g., when downloading with an applet).
24 In this case you might want to include the "mailapi.jar" file, which
25 includes *no* protocol providers, along with just the jar file for the
26 protocol provider you need. For example, an applet that only needs to
27 send mail could use the "mailapi.jar" file and the "smtp.jar" file.
29 An important note when using the separate protocol provider jar files:
31 - You can't mix and match the Sun protocol providers between different
32 releases of the JavaMail API. The Sun protocol providers depend on
33 implementation-specific utility APIs within the mailapi.jar file.
34 (Third party protocol providers that don't depend on these APIs
35 should work fine.)
38 NOTE: The Sun protocol provider documentation that was previously
39 included in this file is now available in javadoc format, see
40 docs/javadocs/index.html in the directory where you extracted
41 the JavaMail API zip file. This documentation describes how to
42 use features of the Sun protocol providers to directly access
43 some features of the SMTP, IMAP, and POP3 protocols that are
44 not otherwise supported by the standard JavaMail API.
47 SASL Support
48 ------------
50 On systems that support the Java SASL API (javax.security.sasl, JSR-28),
51 such as J2SE 5.0 and later, the IMAP provider can use the SASL API to
52 find an appropriate authentication mechanism. The SASL API also allows
53 you to plug in support for custom authentication mechanisms. See The
54 Java SASL API Programming and Deployment Guide at
55 http://java.sun.com/j2se/1.5.0/docs/guide/security/sasl/sasl-refguide.html
56 for details on developing custom SASL mechanisms. See the javadocs for
57 the com.sun.mail.imap package for the properties required to enable and
58 configure SASL support.
61 DSN Support
62 -----------
64 This release of JavaMail includes EXPERIMENTAL support for creating
65 and parsing Delivery Status Notifications, as defined by RFC 3462
66 and RFC 3464. To make use of this support you need to include dsn.jar
67 in your CLASSPATH along with mail.jar. See the javadocs for the
68 com.sun.mail.dsn package for more details.
70 The DSN package also provides support for creating and parsing Message
71 Disposition Notifications, as defined by RFC 3798.
73 The APIs unique to this package should be considered EXPERIMENTAL.
74 They may be changed in the future in ways that are incompatible with
75 applications using the current APIs.
78 NTLM Support
79 ------------
81 This release of JavaMail includes EXPERIMENTAL support for the
82 Microsoft NTLM authentication mechanism used by Exchange. See the
83 file NTLMNOTES.txt for details.
86 OSGi Support
87 ------------
89 The JavaMail jar files are now OSGi bundles. Please let us know
90 of any problems using JavaMail with OSGi.
93 How to submit bug reports
94 -------------------------
96 If you've found a bug, or if you just need help figuring out how to use
97 the JavaMail API, please try to include the following information in
98 your message to us:
100 - a program or code snippet that shows the problem
101 - the platform you are using
102 - the mail server (vendor name, version number) you are using
103 - your environment variable settings
104 - a stack trace, if appropriate
105 - a protocol trace, after turning on session debugging, if appropriate
107 Most of the problems reported to us fail to include enough of the above
108 information to allow us to diagnose your problem. It will save you and
109 us time if you include this information in your first message to us.
111 By far the most common problems we see are:
113 Your problem: Something doesn't work right when talking to my mail server.
114 Our response: Turn on session debugging and send us the protocol trace.
115 See the demo program documentation for how to turn on
116 session debugging for the demo programs. In your own
117 program, call "session.setDebug(true);".
119 Your problem: javax.mail or javax.activation classes not found when compiling.
120 Our response: You didn't set CLASSPATH correctly to find mail.jar and
121 activation.jar. See README.txt.
123 Your problem: NoSuchProviderException - No such provider for rfc822.
124 Our response: You unjar'ed mail.jar. Don't.
126 Your problem: How do I create a message with an attachment?
127 Our response: Create a message with a MimeMultipart content. See the
128 sendfile.html and msgmultisendsample.java demo programs.
130 Please check the FAQ at http://java.sun.com/products/javamail/FAQ.html
131 before submitting bug reports.
133 Send your bug reports to:
135 javamail@sun.com
140 A list of the known limitations, bugs, issues:
141 ----------------------------------------------
143 1. This version of JavaMail will only work in applets when using
144 the Java(TM) Plug-in (http://java.sun.com/products/plugin),
145 which is part of the current Java Runtime Environment (JRE)
146 available from Sun at http://java.sun.com/javase/downloads/index.jsp.
148 2. Internationalization. Parameter encoding in MIME headers, as
149 specified by RFC2231, *has* been implemented. Note that
150 this covers only certain special cases not covered by the MIME
151 specification. MIME specifies encoding of text in the Subject
152 and address headers, and JavaMail fully supports such encoding.
153 Most mailers don't support RFC2231.
155 To enable RFC2231 support in parameter lists, set the System
156 properties mail.mime.encodeparameters and mail.mime.decodeparameters
157 to "true".
159 3. We've received reports of IMAP authentication failures on the
160 Microsoft Exchange Server 5.5, enterprise edition. This is due to
161 a bug in the Microsoft server and the "Service Pack 1 for Exchange
162 Server 5.5" apparently fixes this server bug. The service pack can
163 be downloaded from the Microsoft website.
165 4. Due to a problem in the Microsoft Exchange IMAP server, insufficient
166 number of bytes may be retrieved when reading big messages. There
167 are two ways to workaround this Exchange bug:
169 (a) The Exchange IMAP server provides a configuration option called
170 "fast message retrieval" to the UI. Simply go to the site, server
171 or recipient, click on the "IMAP4" tab, and one of the check boxes
172 is "enable fast message retrieval". Turn it off and the octet
173 counts will be exact. This is fully described at
174 http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q191504
176 (b) Set the "mail.imap.partialfetch" property to false. You'll have
177 to set this property in the Properties object that you provide to
178 your Session.
180 5. Certain IMAP servers do not implement the IMAP Partial FETCH
181 functionality properly. This problem typically manifests as corrupt
182 email attachments when downloading large messages from the IMAP
183 server. To workaround this server bug, set the
184 "mail.imap.partialfetch"
185 property to false. You'll have to set this property in the Properties
186 object that you provide to your Session.
188 Servers tested with:
189 --------------------
191 The IMAP implementation works with IMAP4 and IMAP4rev1 servers.
192 The current release has been tested with:
193 Sun Java System Messaging Server version 7.0
194 UW IMAP4 server version 2003.339
195 Cyrus IMAP4 server version 1.6.19
197 Previous releases have been tested with:
198 Sun Java System Messaging Server version 5.2
199 Sun Java System Messaging Server version 6.3
200 Sun Internet Mail Server version 2.0, 3.2, and 4.0
201 Netscape Messaging Server version 3.01 and 4.1
202 Microsoft Exchange
203 Microsoft MCIS Mail Server
204 Lotus Notes
205 Software.com IMAP server
206 Qualcomm Worldmail
208 The current release of the SMTP implementation has been tested with:
209 Sendmail version 8.13.8
210 Sun Java System Messaging Server version 7.0
212 Previous releases have been tested with:
213 Sendmail version 8.6 and 8.9.1
214 Sun Java System Messaging Server version 5.2
215 Sun Java System Messaging Server version 6.3
216 Sun Internet Mail Server version 3.2 and 4.0
217 Netscape Messaging Server version 3.01 and 4.1
218 Microsoft Exchange
219 Microsoft MCIS Mail Server
220 Qualcomm Worldmail
222 How to give feedback
223 --------------------
225 Please send your feedback to this email-address:
227 javamail@sun.com
229 Check out our website at http://java.sun.com/products/javamail
231 You can also find help in the JavaMail forum:
233 http://forums.sun.com/forum.jspa?forumID=43
236 ------------------------------------------------------------------