Operations may throw exceptions. In cases where the underlying Java code throws exceptions that are anticipated, these are translated into xUML exception signatures. For unexpected (not anticipated) exception in the Java code, you may receive a generic xUML exception. The anticipated exceptions and their codes are listed below.
Type/Domain
Code
Description
JMAIL
01
the connection to host cannot be established
JMAIL
02
a to-be-sent-attachment has no content
JMAIL
03
a binary to-be-sent-attachment has no filename
JMAIL
04
at least one recipient or the sender has an invalid address
JMAIL
05
the connected host does not provide the requested protocol
JMAIL
06
general uncaught exception while sending
JMAIL
07
a generically defined operation is not implemented for a specific protocol (e.g. sendMessage() via IMAP)
JMAIL
08
connection specifies an unknown/unsupported protocol
JMAIL
09
a specific folder cannot be found or is not supported
JMAIL
10
a requested attribute of messages is not supported (raised for exchange only)
JMAIL
11
message cannot be retrieved (raised for exchange only)
JMAIL
12
native message cannot be concerted to Mail class
JMAIL
13
raw message content is not available
JMAIL
14
general uncaught exception while retrieving
JMAIL
15
messaging exception while retrieving attached nested messages
JMAIL
16
general uncaught exception while deleting
JMAIL
17
a message cannot be found by its ID
JMAIL
18
general uncaught exception while moving
JMAIL
19
signature of signed content could not be verified
JMAIL
20
the specified keystore could not be loaded
JMAIL
21
PGP public key ring cannot be loaded
JMAIL
30
cryptographic operation failed due to IO exception, usually a provided key is not in PEM format
JMAIL
31
cryptographic pgp related exception
JMAIL
32
IPgpKeyProvider not registered or returned NULL, i.e. key could not be retrieved