This class represents a MIME style email message.
It implements the Message abstract class and the MimePart interface.
Clients wanting to create new MIME style messages will instantiate an empty
MimeMessage object and then fill it with appropriate attributes and content.
Service providers that implement MIME compliant backend stores may want to
subclass MimeMessage and override certain methods to provide specific
implementations. The simplest case is probably a provider that generates
a MIME style input stream and leaves the parsing of the stream to this
class.
MimeMessage uses the InternetHeaders class to parse and store the toplevel
RFC 822 headers of a message.
A note on RFC 822 and MIME headers
RFC 822 header fields must contain only US-ASCII characters. MIME allows
non ASCII characters to be present in certain portions of certain headers,
by encoding those characters. RFC 2047 specifies the rules for doing this.
The MimeUtility class provided in this package can be used to to achieve
this.
Callers of the
setHeader
,
addHeader
, and
addHeaderLine
methods are responsible for enforcing the MIME
requirements for the specified headers. In addition, these header fields
must be folded(wrapped) before being sent if they exceed the line length
limitation for the transport(1000 bytes for SMTP). Received headers may
have been folded. The application is responsible for folding and unfolding
headers as appropriate.
addFrom
public void addFrom(Address[] addresses)
throws MessagingException
Add the specified addresses to the existing "From" field.
If the "From" field does not already exist, it is created.
- addFrom in interface Message
addresses
- the senders of this message
addHeader
public void addHeader(String name,
String value)
throws MessagingException
Add this value to the existing values for this header_name.
Note that RFC 822 headers must contain only US-ASCII characters,
so a header that contains non US-ASCII characters must have been
encoded as per the rules of RFC 2047.
- addHeader in interface Part
name
- header namevalue
- header value
addRecipients
public void addRecipients(Message.RecipientType type,
String addresses)
throws MessagingException
Add the given addresses to the specified recipient type.
type
- Recipient typeaddresses
- Addresses
createInternetHeaders
protected InternetHeaders createInternetHeaders(InputStream is)
throws MessagingException
Create and return an InternetHeaders object that loads the headers
from the given InputStream.
Subclasses can override this method to return a subclass of
InternetHeaders, if necessary.
This implementation simply constructs and returns an InternetHeaders
object.
is
- the InputStream to read the headers from
getAllHeaderLines
public Enumeration getAllHeaderLines()
throws MessagingException
Get all header lines as an Enumeration of Strings.
A Header line is a raw RFC 822 header-line, containing both the "name"
and "value" field.
- getAllHeaderLines in interface MimePart
getAllHeaders
public Enumeration getAllHeaders()
throws MessagingException
Return all the headers from this Message as an enumeration of Header
objects.
Note that certain headers may be encoded as per RFC 2047 if they contain
non US-ASCII characters and these should be decoded.
This implementation obtains the headers from the
headers
InternetHeaders object.
- getAllHeaders in interface Part
- array of header objects
getAllRecipients
public Address[] getAllRecipients()
throws MessagingException
Get all the recipient addresses for the message.
Extracts the TO, CC, BCC, and NEWSGROUPS recipients.
- getAllRecipients in interface Message
getContent
public Object getContent()
throws IOException,
MessagingException
Return the content as a Java object.
The type of this object is dependent on the content itself.
For example, the native format of a "text/plain" content is usually
a String object. The native format for a "multipart" message is always
a Multipart subclass. For content types that are unknown to the
DataHandler system, an input stream is returned as the content.
This implementation obtains the content from the DataHandler,
that is, it invokes
getDataHandler().getContent()
.
- getContent in interface Part
getContentID
public String getContentID()
throws MessagingException
Returns the value of the "Content-ID" header field.
Returns null if the field is unavailable or its value is absent.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getContentID in interface MimePart
MimeBodyPart.getContentID()
getContentLanguage
public String[] getContentLanguage()
throws MessagingException
Get the languages specified in the "Content-Language" header field
of this message.
The Content-Language header is defined by RFC 1766.
Returns null if this field is unavailable or its value is absent.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getContentLanguage in interface MimePart
MimeBodyPart.getContentLanguage()
getContentStream
protected InputStream getContentStream()
throws MessagingException
Produce the raw bytes of the content.
This method is used during parsing, to create a DataHandler object
for the content. Subclasses that can provide a separate input stream
for just the message content might want to override this method.
This implementation just returns a ByteArrayInputStream constructed
out of the content byte array.
MimeBodyPart.getContentStream()
getContentType
public String getContentType()
throws MessagingException
Returns the value of the RFC 822 "Content-Type" header field.
This represents the content-type of the content of this message.
This value must not be null. If this field is unavailable,
"text/plain" should be returned.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getContentType in interface Part
getDataHandler
public DataHandler getDataHandler()
throws MessagingException
Return a DataHandler for this Message's content.
The implementation provided here works as follows. Note the use of the
getContentStream
method to generate the byte stream for
the content. Also note that any transfer-decoding is done automatically
within this method.
getDataHandler() {
if (dh == null) {
dh = new DataHandler(new MimePartDataSource(this));
}
return dh;
}
class MimePartDataSource implements DataSource {
public getInputStream() {
return MimeUtility.decode(
getContentStream(), getEncoding());
}
....
}
- getDataHandler in interface Part
getDescription
public String getDescription()
throws MessagingException
Returns the "Content-Description" header field of this Message.
This typically associates some descriptive information with this part.
Returns null if this field is unavailable or its value is absent.
If the Content-Description field is encoded as per RFC 2047,
it is decoded and converted into Unicode.
If the decoding or conversion fails, the raw data is returned as-is.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getDescription in interface Part
MimeBodyPart.getDescription()
getDisposition
public String getDisposition()
throws MessagingException
Returns the value of the "Content-Disposition" header field.
This represents the disposition of this part.
The disposition describes how the part should be presented to the user.
If the Content-Disposition field is unavailable, null is returned.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getDisposition in interface Part
MimeBodyPart.getDisposition()
getEncoding
public String getEncoding()
throws MessagingException
Returns the content transfer encoding from the "Content-Transfer-Encoding"
header field.
Returns null if the header is unavailable or its value is absent.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getEncoding in interface MimePart
MimeBodyPart.getEncoding()
getFileName
public String getFileName()
throws MessagingException
Get the filename associated with this Message.
Returns the value of the "filename" parameter from the
"Content-Disposition" header field of this message.
If it's not available, returns the value of the "name" parameter
from the "Content-Type" header field of this BodyPart.
Returns null if both are absent.
- getFileName in interface Part
MimeBodyPart.getFileName()
getFlags
public Flags getFlags()
throws MessagingException
Return a Flags object containing the flags for this message.
Note that a clone of the internal Flags object is returned, so modifying
the returned Flags object will not affect the flags of this message.
- getFlags in interface Message
- Flags object containing the flags for this message
getFrom
public Address[] getFrom()
throws MessagingException
Returns the value of the RFC 822 "From" header fields.
If this header field is absent, the "Sender" header field is used.
If the "Sender" header field is also absent, null is returned.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getFrom in interface Message
getHeader
public String[] getHeader(String name)
throws MessagingException
Get all the headers for this header_name.
Note that certain headers may be encoded as per RFC 2047 if they
contain non US-ASCII characters and these should be decoded.
This implementation obtains the headers from the
headers
InternetHeaders object.
- getHeader in interface Part
name
- name of header
- array of headers
getHeader
public String getHeader(String name,
String delimiter)
throws MessagingException
Get all the headers for this header name, returned as a single String,
with headers separated by the delimiter.
If the delimiter is null, only the first header is returned.
- getHeader in interface MimePart
name
- the name of the headerdelimiter
- the delimiter
- the value fields for all headers with this name
getInputStream
public InputStream getInputStream()
throws IOException,
MessagingException
Return a decoded input stream for this Message's "content".
This implementation obtains the input stream from the DataHandler,
that is, it invokes
getDataHandler().getInputStream()
.
- getInputStream in interface Part
MimeBodyPart.getInputStream()
getLineCount
public int getLineCount()
throws MessagingException
Return the number of lines for the content of this message.
Return -1 if this number cannot be determined.
Note that this number may not be an exact measure of the content length
and may or may not account for any transfer encoding of the content.
This implementation returns -1.
- getLineCount in interface Part
getMatchingHeaderLines
public Enumeration getMatchingHeaderLines(String[] names)
throws MessagingException
Get matching header lines as an Enumeration of Strings.
A Header line is a raw RFC 822 header-line, containing both the "name"
and "value" field.
- getMatchingHeaderLines in interface MimePart
getMatchingHeaders
public Enumeration getMatchingHeaders(String[] names)
throws MessagingException
Return matching headers from this Message as an Enumeration of Header
objects.
This implementation obtains the headers from the
headers
InternetHeaders object.
- getMatchingHeaders in interface Part
getMessageID
public String getMessageID()
throws MessagingException
Returns the value of the "Message-ID" header field.
Returns null if this field is unavailable or its value is absent.
This implementation uses the
getHeader
method
to obtain the requisite header field.
getNonMatchingHeaderLines
public Enumeration getNonMatchingHeaderLines(String[] names)
throws MessagingException
Get non-matching header lines as an Enumeration of Strings.
A Header line is a raw RFC 822 header-line, containing both the "name"
and "value" field.
- getNonMatchingHeaderLines in interface MimePart
getNonMatchingHeaders
public Enumeration getNonMatchingHeaders(String[] names)
throws MessagingException
Return non-matching headers from this Message as an Enumeration of Header
objects.
This implementation obtains the headers from the
headers
InternetHeaders object.
- getNonMatchingHeaders in interface Part
getRawInputStream
public InputStream getRawInputStream()
throws MessagingException
Return an InputStream to the raw data with any Content-Transfer-Encoding
intact.
This method is useful if the "Content-Transfer-Encoding" header is
incorrect or corrupt, which would prevent the
getInputStream
method or
getContent
method from returning the correct data.
In such a case the application may use this method and attempt to decode
the raw data itself.
This implementation simply calls the
getContentStream
method.
MimeBodyPart.getRawInputStream()
getReceivedDate
public Date getReceivedDate()
throws MessagingException
Returns the Date on this message was received.
Returns null if this date cannot be obtained.
Note that RFC 822 does not define a field for the received date.
Hence only implementations that can provide this date need return
a valid value.
- getReceivedDate in interface Message
getRecipients
public Address[] getRecipients(Message.RecipientType type)
throws MessagingException
Returns the recipients specified by the type.
The mapping between the type and the corresponding RFC 822 header
is as follows:
- Message.RecipientType.TO
- "To"
- Message.RecipientType.CC
- "Cc"
- Message.RecipientType.BCC
- "Bcc"
- MimeMessage.RecipientType.NEWSGROUPS
- "Newsgroups"
Returns null if the header specified by the type is not found or if its
value is empty.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getRecipients in interface Message
type
- the type of recipient
getReplyTo
public Address[] getReplyTo()
throws MessagingException
Return the value of the RFC 822 "Reply-To" header field.
If this header is unavailable or its value is absent,
then the getFrom
method is called and its value is returned.
This implementation uses the getHeader
method
to obtain the requisite header field.
- getReplyTo in interface Message
getSender
public Address getSender()
throws MessagingException
Returns the value of the RFC 822 "Sender" header field.
If the "Sender" header field is absent,
null
is returned.
This implementation uses the
getHeader
method to obtain
the required header field.
- JavaMail 1.3
getSentDate
public Date getSentDate()
throws MessagingException
Returns the value of the RFC 822 "Date" field. This is the date on which
this message was sent. Returns null if this field is unavailable or its
value is absent.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getSentDate in interface Message
getSize
public int getSize()
throws MessagingException
Return the size of the content of this message in bytes.
Return -1 if the size cannot be determined.
Note that this number may not be an exact measure of the content size
and may or may not account for any transfer encoding of the content.
This implementation returns the size of the
content
array
(if not null), or, if
contentStream
is not null, and the
available
method returns a positive number, it returns
that number as the size. Otherwise, it returns -1.
- getSize in interface Part
getSubject
public String getSubject()
throws MessagingException
Returns the value of the "Subject" header field.
Returns null if the subject field is unavailable or its value is absent.
If the subject is encoded as per RFC 2047, it is decoded and converted
into Unicode. If the decoding or conversion fails,
the raw data is returned as is.
This implementation uses the
getHeader
method
to obtain the requisite header field.
- getSubject in interface Message
isMimeType
public boolean isMimeType(String mimeType)
throws MessagingException
Is this Part of the specified MIME type? This method compares only the
primaryType and subType.
The parameters of the content types are ignored.
For example, this method will return true when comparing a Part
of content type "text/plain" with "text/plain; charset=foobar".
If the subType of mimeType is the special character '*', then
the subtype is ignored during the comparison.
- isMimeType in interface Part
MimeBodyPart.isMimeType(String)
isSet
public boolean isSet(Flags.Flag flag)
throws MessagingException
Check whether the flag specified in the flag argument is set in this
message.
This implementation checks this message's internal flags object.
- isSet in interface Message
flag
- - the flag
- value of the specified flag for this message
parse
protected void parse(InputStream is)
throws MessagingException
Parse the InputStream setting the headers and content fields
appropriately.
Also resets the modified flag.
This method is intended for use by subclasses that need to control
when the InputStream is parsed.
is
- The message input stream
reply
public Message reply(boolean replyToAll)
throws MessagingException
Get a new Message suitable for a reply to this message.
The new Message will have its attributes and headers set up
appropriately. Note that this new message object will be empty,
i.e., it will not have a "content". These will have to be suitably
filled in by the client.
If
replyToAll
is set, the new Message will be addressed
to all recipients of this message. Otherwise, the reply will be
addressed to only the sender of this message(using the value of
the
getReplyTo
method).
The "Subject" field is filled in with the original subject prefixed
with "Re:"(unless it already starts with "Re:"). The "In-Reply-To"
header is set in the new message if this message has a "Message-Id"
header. The ANSWERED flag is set in this message.
- reply in interface Message
replyToAll
- reply should be sent to all recipients of this message
- the reply Message
saveChanges
public void saveChanges()
throws MessagingException
Updates the appropriate header fields of this message to be consistent
with the message's contents.
If this message is contained in a Folder, any changes made to this
message are committed to the containing folder.
If any part of a message's headers or contents are changed,
saveChanges
must be called to ensure that those changes
are permanent. Otherwise, any such modifications may or may not be
saved, depending on the folder implementation.
Messages obtained from folders opened READ_ONLY should not be modified
and
saveChanges
should not be called on such messages.
This method sets the
modified
flag to true,
the
save
flag to true, and then calls the
updateHeaders
method.
- saveChanges in interface Message
setContent
public void setContent(Object o,
String type)
throws MessagingException
A convenience method for setting this Message's content.
The content is wrapped in a DataHandler object. Note that a
DataContentHandler class for the specified type should be available
to the JavaMail implementation for this to work right. i.e., to do
setContent(foobar, "application/x-foobar")
, a
DataContentHandler for "application/x-foobar" should be installed.
Refer to the Java Activation Framework for more information.
- setContent in interface Part
o
- the content objecttype
- Mime type of the object
MimeBodyPart.setContent
setContentID
public void setContentID(String cid)
throws MessagingException
Set the "Content-ID" header field of this Message.
If the cid parameter is null, any existing "Content-ID" is removed.
cid
- the content-id value to set, or null to remove
setDescription
public void setDescription(String description)
throws MessagingException
Set the "Content-Description" header field for this Message.
If the
description
parameter is null,
then any existing "Content-Description" fields are removed.
If the description contains non US-ASCII characters, it will be encoded
using the platform's default charset. If the description contains only
US-ASCII characters, no encoding is done and it is used as-is.
Note that if the charset encoding process fails, a MessagingException is
thrown, and an UnsupportedEncodingException is included in the chain of
nested exceptions within the MessagingException.
- setDescription in interface Part
description
- content-description
MimeBodyPart.setDescription
setDescription
public void setDescription(String description,
String charset)
throws MessagingException
Set the "Content-Description" header field for this Message.
If the
description
parameter is null,
then any existing "Content-Description" fields are removed.
If the description contains non US-ASCII characters, it will be encoded
using the specified charset. If the description contains only
US-ASCII characters, no encoding is done and it is used as-is.
Note that if the charset encoding process fails, a MessagingException is
thrown, and an UnsupportedEncodingException is included in the chain of
nested exceptions within the MessagingException.
description
- content-descriptioncharset
- the charset to use
MimeBodyPart.setDescription
setDisposition
public void setDisposition(String disposition)
throws MessagingException
Set the "Content-Disposition" header field of this Message.
If disposition
is null,
any existing "Content-Disposition" header field is removed.
- setDisposition in interface Part
disposition
- the disposition value to set, or null to remove
MimeBodyPart.setDisposition(String)
setFlags
public void setFlags(Flags flag,
boolean set)
throws MessagingException
Set the flags for this message.
This implementation modifies the flags field.
- setFlags in interface Message
setFrom
public void setFrom()
throws MessagingException
Set the RFC 822 "From" header field using the value of the
InternetAddress.getLocalAddress
method.
- setFrom in interface Message
setFrom
public void setFrom(Address address)
throws MessagingException
Set the RFC 822 "From" header field.
Any existing values are replaced with the given address.
If address is null, this header is removed.
- setFrom in interface Message
address
- the sender of this message
setHeader
public void setHeader(String name,
String value)
throws MessagingException
Set the value for this header_name.
Replaces all existing header values with this new value.
Note that RFC 822 headers must contain only US-ASCII characters,
so a header that contains non US-ASCII characters must have been
encoded by the caller as per the rules of RFC 2047.
- setHeader in interface Part
name
- header namevalue
- header value
setRecipients
public void setRecipients(Message.RecipientType type,
String addresses)
throws MessagingException
Set the specified recipient type to the given addresses.
If the address parameter is null, the corresponding recipient field
is removed.
type
- Recipient typeaddresses
- Addresses
setRecipients
public void setRecipients(Message.RecipientType type,
Address[] addresses)
throws MessagingException
Set the specified recipient type to the given addresses.
If the address parameter is null, the corresponding recipient field
is removed.
- setRecipients in interface Message
type
- Recipient typeaddresses
- Addresses
setReplyTo
public void setReplyTo(Address[] addresses)
throws MessagingException
Set the RFC 822 "Reply-To" header field.
If the address parameter is null, this header is removed.
- setReplyTo in interface Message
addresses
- Addresses
setSender
public void setSender(Address address)
throws MessagingException
Set the RFC 822 "Sender header field. Any existing values are replaced
with the given address. If address is null
, this header is
removed.
address
- the sener of this message
- JavaMail 1.3
setSentDate
public void setSentDate(Date date)
throws MessagingException
Set the RFC 822 "Date" header field.
This is the date on which the creator of the message indicates that
the message is complete and ready for delivery.
If the date
parameter is null, the existing "Date" field
is removed.
- setSentDate in interface Message
date
- the date value to set, or null to remove
setSubject
public void setSubject(String subject)
throws MessagingException
Set the "Subject" header field.
If the subject contains non US-ASCII characters, it will be encoded
using the platform's default charset. If the subject contains only
US-ASCII characters, no encoding is done and it is used as-is.
If the subject is null, the existing "Subject" field is removed.
Note that if the charset encoding process fails, a MessagingException is
thrown, and an UnsupportedEncodingException is included in the chain of
nested exceptions within the MessagingException.
- setSubject in interface Message
subject
- the subject
setSubject
public void setSubject(String subject,
String charset)
throws MessagingException
Set the "Subject" header field.
If the subject contains non US-ASCII characters, it will be encoded
using the specified charset. If the subject contains only
US-ASCII characters, no encoding is done and it is used as-is.
If the subject is null, the existing "Subject" field is removed.
Note that if the charset encoding process fails, a MessagingException is
thrown, and an UnsupportedEncodingException is included in the chain of
nested exceptions within the MessagingException.
subject
- the subjectcharset
- the charset
setText
public void setText(String text)
throws MessagingException
Convenience method that sets the given String as this part's content,
with a MIME type of "text/plain".
If the string contains non US-ASCII characters, it will be encoded
using the platform's default charset. The charset is also used to set
the "charset" parameter.
Note that there may be a performance penalty if text is large, since
this method may have to scan all the characters to determine what
charset to use.
If the charset is already known, use the
setText
method
that takes the
charset
parameter.
- setText in interface MimePart
- setText in interface Part
MimeBodyPart.setText
setText
public void setText(String text,
String charset)
throws MessagingException
Convenience method that sets the given String as this part's content,
with a MIME type of "text/plain" and the specified charset.
The given Unicode string will be charset-encoded using the specified
charset. The charset is also used to set the "charset" parameter.
- setText in interface MimePart
updateHeaders
protected void updateHeaders()
throws MessagingException
Called by the saveChanges
method to actually update
the MIME headers.
The implementation here sets the Content-Transfer-Encoding header
(if needed and not already set), the Mime-Version header
and the Message-ID header.
Also, if the content of this message is a MimeMultipart,
its updateHeaders
method is called.
MimeBodyPart.updateHeaders()
writeTo
public void writeTo(OutputStream os)
throws IOException,
MessagingException
Output the message as an RFC 822 format stream.
Note that, depending on how the message was constructed, it may use a
variety of line termination conventions. Generally the output should be
sent through an appropriate FilterOutputStream that converts the line
terminators to the desired form, either CRLF for MIME compatibility and
for use in Internet protocols, or the local platform's line terminator
for storage in a local text file.
This implementation calls the
writeTo(OutputStream, String[])
method with a null ignore
list.
- writeTo in interface Part
writeTo
public void writeTo(OutputStream os,
String[] ignoreList)
throws IOException,
MessagingException
Output the message as an RFC 822 format stream, without specified
headers. If the saved flag is not set, the saveChanges
method is called. If the modified
flag is not set and
the content
array is not null, the content
array is written directly, after writing the appropriate message headers.