|Home >> All >> javax >> [ mail Javadoc ]|
|||javax.mail.event.* (24)||||javax.mail.internet.* (28)||||javax.mail.search.* (24)|
javax.mail: Javadoc index of package javax.mail.
javax.mail.event: Classes modelling a mail system.
javax.mail.internet: Classes modelling a mail system.
javax.mail.search: Classes modelling a mail system.
Folder: An abstract representation of a folder in a mail system; subclasses would implement Folders for each supported protocol. Depending on protocol and implementation, folders may contain other folders, messages, or both as indicated by the HOLDS_FOLDERS 55 and HOLDS_MESSAGES 55 flags. If the immplementation supports hierarchical folders, the format of folder names is implementation dependent; however, components of the name are separated by the delimiter character returned by getSeparator() 55 . The case-insensitive folder name "INBOX" is reserved to refer to the primary folder for the current user ...
Session: OK, so we have a final class in the API with a heck of a lot of implementation required... let's try and figure out what it is meant to do. It is supposed to collect together properties and defaults so that they can be shared by multiple applications on a desktop; with process isolation and no real concept of shared memory, this seems challenging. These properties and defaults rely on system properties, making management in a app server harder, and on resources loaded from "mail.jar" which may lead to skew between differnet independent implementations of this API.
Flags: Representation of flags that may be associated with a message. Flags can either be system flags, defined by the Flag inner class, or user-defined flags defined by a String. The system flags represent those expected to be provided by most folder systems; user-defined flags allow for additional flags on a per-provider basis. This class is Serializable but compatibility is not guaranteed across releases.
FetchProfile: A FetchProfile defines a list of message attributes that a client wishes to prefetch from the server during a fetch operation. Clients can either specify individual headers, or can reference common profiles as defined by FetchProfile.Item .
InternetAddress: A representation of an Internet email address as specified by RFC822 in conjunction with a human-readable personal name that can be encoded as specified by RFC2047. A typical address is "email@example.com" and personal name "Joe User"
SearchTerm: Base class for Terms in a parse tree used to represent a search condition. This class is Serializable to allow for the short term persistence of searches between Sessions; this is not intended for long-term persistence.
MailDateFormat: Formats ths date as specified by draft-ietf-drums-msg-fmt-08 dated January 26, 2000 which supercedes RFC822. The format used is EEE, d MMM yyyy HH:mm:ss Z and locale is always US-ASCII.
BodyTerm: Term that matches on a message body. All parts that have a MIME type of "text/*" are searched.
Address: This abstract class models the addresses in a message. Addresses are Serializable so that they may be serialized along with other search terms.
Part: Note: Parts are used in Collections so implementing classes must provide a suitable implementation of equals and hashCode.
MessageCountAdapter: An adaptor that receives message count events. This is a default implementation where the handlers perform no action.
ConnectionAdapter: An adaptor that receives connection events. This is a default implementation where the handlers perform no action.
FolderAdapter: An adaptor that receives connection events. This is a default implementation where the handlers perform no action.
TransportAdapter: An adaptor that receives transport events. This is a default implementation where the handlers perform no action.
Multipart: A container for multiple BodyParts .
FlagTerm: Term for matching message javax.mail.Flags .
PasswordAuthentication: A data holder used by Authenticator to contain a username and password.
InternetHeaders: Class that represents the RFC822 headers associated with a message.
MessageCountEvent: Event indicating a change in the number of messages in a folder.
MessageContext: The context in which a piece of message content is contained.
StoreEvent: Event representing motifications from the Store connection.
NewsAddress: A representation of an RFC1036 Internet newsgroup address.