Release Notes: This release includes an auxiliary class that can parse and extract e-mail addresses from message headers that usually contain addresses like From:, To:, Cc:, and Bcc: .
Release Notes: A bug was fixed to make the parser correctly handle the content-type header with white spaces in the boundary definition. Another bug was fixed to correctly handle base64 encoded message bodies that are longer than the message buffer size.
Release Notes: A bug that was preventing parsing multiple messages with the same object was fixed.
Release Notes: A bug was fixed to avoid erroneous attempts to decode empty message headers.
Release Notes: The class can now parse the necessary header values to extract the filenames of embedded file parts and attachment parts included in a message, so the developer can easily save the message files with the original file names.
Release Notes: The parser now tolerates errors of unsupported or incorrect message body encodings.
Release Notes: The parser is now more tolerant when dealing with malformed messages with syntax errors that do not comply to RFC 2822, like messages with broken quoted-printable headers and bodies or invalid header names. The parser can now skip syntax errors and return a list of warnings instead of failing to parse the message completely.
Release Notes: A bug in the detection of message end when parsing messages from string data was fixed. A workaround was added to handle messages that do not have a line break at the end. A unit test script was added to verify that the class can correctly parse all kinds of messages.
Release Notes: A workaround was added to avoid a failure to parse messages with malformed header encodings.
Release Notes: This revision can decode headers using UTF-8 or any other character set encoded using base64.