 |
Quickly
Parses Entire Message or only Specific Parts |
|
Easily parse the entire
message or specific parts. Options include parsing
entire message, message header only or message without the
header.
|
|
Incredibly
High Performance and Low Resource Consumption |
|
The library has been
engineered to obtain super fast performance, yet consume very
little system resources.
|
|
MIME Support |
|
Parses MIME messages
automatically and and provides access to every MIME part of
the message including header, body, alternative bodies,
attachments, images, digital signatures, etc.. MIME
parts may be loaded into RAM or saved to disk, and optionally
decoded.
|
|
UUencode
Support |
|
Parses UUencoded messages
automatically and and provides access to every
attachment. Attachments may be loaded into RAM or saved
to disk, and optionally decoded.
|
|
Base64, UUencode,
Quoted-Printable and BinHex Decoding |
|
The EasyMail Advanced API
enables you to automatically decode any part of the message
you choose.
|
|
Full Header
Parsing |
|
Fully parses the message
header, yielding access to the message subject, recipients,
priority, sender, custom header, dates, etc... Where
applicable, header information is broken into linked lists,
i.e. a linked list of message recipients.
|
|
HTML Message
Support |
|
Optionally decodes and
exports all HTML content of a message, into the appropriate
source files, so that it can be loaded by a standard HTML
reader or browser.
|
|
Scales Easily |
|
Scales easily to multi-user systems.
|
|
Interfaces with
SMTP, POP3, IMAP4 and MailStore Libraries |
|
Parses messages created with
the SMTP library, downloaded with the POP3
library or IMAP4 library, or stored
with the MailStore
library.
|
|
Other Features at a Glance
|
|
|
Detects any character set such as US-ASCII, ISO8859-1, ISO-2022-JP, etc... |
Click here and see what our
customers have to say...
|
|
|
|
|
|
|
|
|
RFC Conformity |
| The Parse822 library strictly
complies with the following RFC document specifications for Internet e-mail
messages: RFC-822, RFC-2045, RFC-2046 and RFC-2047 |
|
