[ 
https://issues.apache.org/jira/browse/MIME4J-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052012#comment-13052012
 ] 

Stefano Bagnara commented on MIME4J-199:
----------------------------------------

Forgot to say that the fact that we accept a line starting with the boundary 
but not ending with CRLF as a valid boundary is already a lenient behaviour.

The strict behaviour should be to fail the parsing of that message as it is 
invalid (BTW I'm not sure this is really handled by the strict flag, but this 
is not importart WRT this issue).

The lenient behaviour is something we have to carefully choose. IIRC we have a 
testcase that checks for the current lenient behaviour so if we change it to 
support this use case, the older test will probably fail.

> does not find the pattern boundary.
> -----------------------------------
>
>                 Key: MIME4J-199
>                 URL: https://issues.apache.org/jira/browse/MIME4J-199
>             Project: JAMES Mime4j
>          Issue Type: Bug
>          Components: parser (core)
>    Affects Versions: 0.6
>            Reporter: Yong-Seong Kim
>         Attachments: screenshot-1.jpg
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> The name of sub-boundary to the upper boundary in the name + @ If you can not 
> retrieve the attachment area.
> modify : BufferedLineReaderInputStream.indexOf(final byte[] pattern, int off, 
> int len)
> see image.
> boundary="NextPart__5980.1307607747"
> boundary="NextPart__5980.13076077471"
> 'NextPart__5980.1307607747' is also searched as a search 
> NextPart__5980.13076077471.
> [ex 
> eml]--------------------------------------------------------------------------------------------------------------------------------
> Content-Type: multipart/mixed;
>       boundary="NextPart__5980.1307607747"
> This is a multi-part message in MIME format.
> --NextPart__5980.1307607747
> Content-Type: multipart/alternative;
>       boundary="NextPart__5980.13076077471"
> --NextPart__5980.13076077471
> Content-Type: text/plain;
>       charset="ks_c_5601-1987"
> Content-Transfer-Encoding: base64
> --NextPart__5980.13076077471
> Content-Type: text/html;
>       charset="ks_c_5601-1987"
> Content-Transfer-Encoding: base64
> ...
> --NextPart__5980.13076077471--
> --NextPart__5980.1307607747
> Content-Type: application/octet-stream;
>       name="1"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
>       filename="1"
> ...
> --------------------------------------------------------------------------------------------------------------------------------

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to