Unable to find valid certification path to requested target
Applies to:
NA
Description:
Occurs while connecting to mail server over SSL
Cause:
You have tried to connect to my mail server over SSL using invalid certificate.
Error List
Error List for the ‘JAVA-Mail’ Category
java.lang.VerifyError: llegal use of nonvirtual function call
Applies to:
Linux
Description:
Occurs while trying to run program on Linux
Cause:
You have tried to run program on Linux and got a very strange error message and the program failed.
Classes in com.sun.mail cannot be found
Applies to:
NA
Description:
Occurs when classes in com.sun.mail cannot be found
Cause:
The most common cause of problems like this is having more than one copy of mail.jar in your CLASSPATH or available to your application.
Can't find a service provider for "smtp" or "imap" or address type "rfc822"
Applies to:
NA
Description:
Occurs when servlet can’t find JavaMail classes
Cause:
Usually this is because JavaMail can’t access the configuration files in mail.jar, possibly because of a security permission problem.
Trouble logging into Microsoft Exchange server
Applies to:
NA
Description:
Occurs when logging into Microsoft Exchange server
Cause:
You were sure that You used the correct username and password while logging into Microsoft Exchange server, but trouble occurred.
JavaMail does not properly encode and decode filenames in non-ASCII character sets
Applies to:
NA
Description:
Occurs while encoding and decoding filenames in non-ASCII character sets
Cause:
The filename is stored as a parameter in MIME headers. Encoded filenames of the form =?ISO-8859-15?B?5OTkLUluZm8ucGRm?= are not part of the MIME spec. A filename of the form =?A?B?C?= is a perfectly valid filename, not an incorrectly encoded filename. JavaMail does not encoded and decode filenames by default because doing so would violate the MIME spec.
The base MIME spec does not allow for encoding parameters. RFC 2231 defines a new way to include encoded paramters, including filenames, in MIME headers. It is not compatible with the de facto way that many applications illegally encode filenames. Even though JavaMail supports RFC 2231, that alone does not allow JavaMail to interoperate with these existing programs. As far as I know, very few existing programs support RFC 2231.
If you choose to violate the MIME spec, in order to interoperate with other programs that also violate the MIME spec, JavaMail gives you all the tools you need to do so. Starting with JavaMail 1.4, setting the System properties “mail.mime.encodefilename” and “mail.mime.decodefilename” to “true” will cause JavaMail to encode and decode the filename parameter.
The IMAP provider loses data when fetching messages with large attachments
Applies to:
NA
Description:
Occurs when fetching messages with large attachments
Cause:
This is due to bugs in the partial fetch implementation of your IMAP server.
OutOfMemory error when loading large binary attachemens
Applies to:
NA
Description:
Occurs when loading large binary attachments
Cause:
You have tried to load large binary attachments.
UnsupportedDataTypeException when invoking getContent() on a bodypart
Applies to:
NA
Description:
Occurs when invoking getContent() method on a bodypart.
Cause:
You have tried to invoke getContent() method on a bodypart.
UnsupportedEncodingException when invoking getContent() on a bodypart that contains text data
Applies to:
NA
Description:
Occurs when invoking getContent() method on a bodypart that contains text data.
Cause:
Textual bodyparts (i.e., bodyparts whose type is “text/plain”, “text/html”, or “text/xml”) return Unicode String objects when getContent() is used. Typically, such bodyparts internally hold their textual data in some non Unicode charset. JavaMail (through the corresponding DataContentHandler) attempts to convert that data into a Unicode string. The underlying JDK’s charset converters are used to do this. If the JDK does not support a particular charset, then the UnsupportedEncodingException is thrown.