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] Resolved: (MIME4J-150) Mime4J does not support mandatory rfc5322 "obsolete" syntax
Date Sat, 24 Apr 2010 19:55:51 GMT

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

Stefano Bagnara resolved MIME4J-150.
------------------------------------

    Resolution: Fixed

The current code supports the basic scenario described in this issue (empty lines unfolding,
spaces before colon). I'm closing this and leave open MIME4J-115 so we can have a further
checkpoint before 0.8.

> Mime4J does not support mandatory rfc5322 "obsolete" syntax
> -----------------------------------------------------------
>
>                 Key: MIME4J-150
>                 URL: https://issues.apache.org/jira/browse/MIME4J-150
>             Project: JAMES Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.6
>            Reporter: Stefano Bagnara
>            Assignee: Stefano Bagnara
>             Fix For: 0.7
>
>
> The obsolete syntax from rfc5322 are normative wrt parsing.
> They are obsolete because compliant software MUST NOT write them, but the MUST be able
to parse them.
> http://tools.ietf.org/html/rfc5322#section-4
> This include at least:
> WSP after the header name
> lonely \r and \n in field values
> Unfolding of empty lines (only WSPs)
> and maybe more...

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