james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Updated: (MIME4J-152) Zero parts multipart messages are parsed as 1 empty part multipart messages
Date Wed, 30 Dec 2009 13:21:29 GMT

     [ https://issues.apache.org/jira/browse/MIME4J-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefano Bagnara updated MIME4J-152:
-----------------------------------

    Attachment: testmsgs-missingboundaries.zip

The original test with fixed expected results, and 2 new test messages to prove different
scenarios and prove the previous inconsistency.

> Zero parts multipart messages are parsed as 1 empty part multipart messages
> ---------------------------------------------------------------------------
>
>                 Key: MIME4J-152
>                 URL: https://issues.apache.org/jira/browse/MIME4J-152
>             Project: JAMES Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>            Priority: Minor
>             Fix For: 0.8
>
>         Attachments: testmsgs-missingboundaries.zip
>
>
> Mime4j currenlty parse a message having only the start boundary as an empty message (zero
parts) but at the same time parse a message with no boundary (no start and no end) as a message
with 1 empty part.
> This is clearly wrong.
> We also already have a missing-inner-boundary.msg in our testsuite but the expectation
files are wrong.

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


Mime
View raw message