Mailing-List: contact mime4j-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mime4j-dev@james.apache.org
Message-ID: <1876800590.527811269700947589.JavaMail.jira@brutus.apache.org>
Date: Sat, 27 Mar 2010 14:42:27 +0000 (UTC)
From: "Stefano Bagnara (JIRA)" <mime4j-dev@james.apache.org>
To: mime4j-dev@james.apache.org
Subject: [jira] Created: (MIME4J-177) The parser invoke preamble token/event
 even when no preamble exists in the message
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

The parser invoke preamble token/event even when no preamble exists in the message
----------------------------------------------------------------------------------

                 Key: MIME4J-177
                 URL: https://issues.apache.org/jira/browse/MIME4J-177
             Project: JAMES Mime4j
          Issue Type: Bug
          Components: parser (core)
    Affects Versions: 0.6
            Reporter: Stefano Bagnara
            Assignee: Stefano Bagnara
             Fix For: 0.7


The token stream sends T_PREAMBLE tokens even when there is no preamble in the message making impossible to distinguish between messages with no preamble and messages with an empty preamble.

T_PREAMBLE should be called only when a preamble exists:

The rfc define multipart-body as:
     multipart-body := [preamble CRLF]
                       dash-boundary transport-padding CRLF
                       body-part *encapsulation
                       close-delimiter transport-padding
                       [CRLF epilogue] 

So preamble is optional (if the is a CRLF before the first boundary then you have a preamble).


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.