Docjar: A Java Source and Docuemnt Enginecom.*    java.*    javax.*    org.*    all    new    plug-in

Quick Search    Search Deep
Home >> All >> gnu >> mail

•gnu.mail.handler.* (13)•gnu.mail.providers.* (24)•gnu.mail.treeutil.* (3)•gnu.mail.util.* (12)

Package Samples:

• gnu.mail.handler
• gnu.mail.providers.imap
• gnu.mail.providers.maildir
• gnu.mail.providers.mbox
• gnu.mail.providers.nntp
• gnu.mail.providers.pop3
• gnu.mail.providers
• gnu.mail.providers.smtp
• gnu.mail.treeutil
• gnu.mail.util

Classes:

• QInputStream: Provides RFC 2047 "B" transfer encoding. See section 4.2: The "Q" encoding is similar to the "Quoted-Printable" content- transfer-encoding defined in RFC 2045. It is designed to allow text containing mostly ASCII characters to be decipherable on an ASCII terminal without decoding. Any 8-bit value may be represented by a "=" followed by two hexadecimal digits. For example, if the character set in use were ISO-8859-1, the "=" character would thus be encoded as "=3D", and a SPACE by "=20". (Upper case should be used for hexadecimal digits "A" through "F".) The 8-bit hexadecimal value 20 (e.g., ISO-8859-1 ...
• QOutputStream: Provides RFC 2047 "B" transfer decoding. See section 4.2: The "Q" encoding is similar to the "Quoted-Printable" content- transfer-encoding defined in RFC 2045. It is designed to allow text containing mostly ASCII characters to be decipherable on an ASCII terminal without decoding. Any 8-bit value may be represented by a "=" followed by two hexadecimal digits. For example, if the character set in use were ISO-8859-1, the "=" character would thus be encoded as "=3D", and a SPACE by "=20". (Upper case should be used for hexadecimal digits "A" through "F".) The 8-bit hexadecimal value 20 (e.g., ISO-8859-1 ...
• Base64InputStream: A Base64 content transfer encoding filter stream. From RFC 2045, section 6.8: The Base64 Content-Transfer-Encoding is designed to represent arbitrary sequences of octets in a form that need not be humanly readable. The encoding and decoding algorithms are simple, but the encoded data are consistently only about 33 percent larger than the unencoded data.
• Base64OutputStream: A Base64 content transfer encoding filter stream. From RFC 2045, section 6.8: The Base64 Content-Transfer-Encoding is designed to represent arbitrary sequences of octets in a form that need not be humanly readable. The encoding and decoding algorithms are simple, but the encoded data are consistently only about 33 percent larger than the unencoded data.
• Multipart: A JAF data content handler for the multipart/* family of MIME content types. This provides the basic behaviour for any number of MimeMultipart-handling subtypes which simply need to override their default constructor to provide the correct MIME content-type and description.
• Application: A JAF data content handler for the application/* family of MIME content types. This provides the basic behaviour for any number of byte-array-handling subtypes which simply need to override their default constructor to provide the correct MIME content-type and description.
• Text: A JAF data content handler for the text/* family of MIME content types. This provides the basic behaviour for any number of text-handling subtypes which simply need to override their default constructor to provide the correct MIME content-type and description.
• NNTPRootFolder: The "root" folder of the NNTP newsgroup list. The NNTP folder namespace is taken to be a flat namespace. This object allows us to retrieve folders corresponding to each newsgroup in that space.
• RFC2822OutputStream: An output stream that ensures that lines of characters in the body are limited to 998 octets (excluding CRLF). This is required by RFC 2822, section 2.3.
• MboxOutputStream: A filter stream that can escape mbox From_ lines in message content. This will only work reliably for messages with <4096 bytes in any one line.
• ReadOnlyMessage: Abstract read-only message. The superclass of mail provider messages that do not support message editing in-place.
• NNTPTransport: An NNTP transport provider. This uses an NNTPConnection to handle all the protocol-related functionality.
• NNTPStore: An NNTP store provider. This uses an NNTPConnection to handle all the protocol-related functionality.
• ApplicationOctetStream: A JAF data content handler for the application/octet-stream MIME content type.
• MailboxURLConnection: A URLConnection that can be used to access mailboxes using the JavaMail API.
• MultipartAlternative: A JAF data content handler for the multipart/alternative MIME content type.
• Message: A JAF data content handler for the message/* family of MIME content types.
• UUDecoderStream: A stream that does UU Decoding. UU-Decoding is defined in the MIME rfcs.
• MultipartRelated: A JAF data content handler for the multipart/related MIME content type.
• MultipartSigned: A JAF data content handler for the multipart/signed MIME content type.
• MultipartMixed: A JAF data content handler for the multipart/mixed MIME content type.
• MessageRFC822: A JAF data content handler for the message/rfc822 MIME content type.
• StatusSource: An interface for defining that an object can pass status messages.
• TextPlain: A JAF data content handler for the text/plain MIME content type.
• TextHtml: A JAF data content handler for the text/html MIME content type.

Home | Contact Us | Privacy Policy | Terms of Service