[
https://issues.apache.org/jira/browse/MIME4J-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved MIME4J-177.
------------------------------------
Resolution: Fixed
At least for the preamble this is resolved and my dkim issue is fixed. I had no
time to deeply study the epilogue status.
> 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.
