james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] Closed: (MIME4J-56) In nested multiparts outer boundaries are not recognized when parsing inner multiparts
Date Wed, 04 Feb 2009 20:52:01 GMT

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

Robert Burrell Donkin closed MIME4J-56.
---------------------------------------


Closing all issues fixed previously, after a brief review of each.

> In nested multiparts outer boundaries are not recognized when parsing inner multiparts
> --------------------------------------------------------------------------------------
>
>                 Key: MIME4J-56
>                 URL: https://issues.apache.org/jira/browse/MIME4J-56
>             Project: JAMES Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.4
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>             Fix For: 0.4
>
>         Attachments: mime4j.patch
>
>
> 5.1.2.  Handling Nested Messages and Multiparts
>    The "message/rfc822" subtype defined in a subsequent section of this
>    document has no terminating condition other than running out of data.
>    Similarly, an improperly truncated "multipart" entity may not have
>    any terminating boundary marker, and can turn up operationally due to
>    mail system malfunctions.
>    It is essential that such entities be handled correctly when they are
>    themselves imbedded inside of another "multipart" structure.  MIME
>    implementations are therefore required to recognize outer level
>    boundary markers at ANY level of inner nesting.  It is not sufficient
>    to only check for the next expected marker or other terminating
>    condition. 

-- 
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