[
https://issues.apache.org/jira/browse/MIME4J-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hendrik Saly updated MIME4J-243:
--------------------------------
Description:
Develop and integrate a strict RFC822 parser. Currently Mime4J is RFC2822 only
(without obsolete syntax support as far as i can see).
I created a first version for a JavaCC grammar here
https://github.com/salyh/james-mime4j/blob/4ca4a809f2deed56777c529a03e34d086309c74d/dom/src/main/jjtree/org/apache/james/mime4j/field/address/rfc822/RFC822AddressParser.jjt
Some basics tests are here (although not steamlined/nice yet)
https://github.com/salyh/james-mime4j/commit/4ca4a809f2deed56777c529a03e34d086309c74d
was:Develop and integrate a strict RFC822 parser
Summary: Implement strict RFC822 parser (was: Strict RFC822 parser)
> Implement strict RFC822 parser
> ------------------------------
>
> Key: MIME4J-243
> URL: https://issues.apache.org/jira/browse/MIME4J-243
> Project: James Mime4j
> Issue Type: New Feature
> Components: dom
> Reporter: Hendrik Saly
> Priority: Critical
>
> Develop and integrate a strict RFC822 parser. Currently Mime4J is RFC2822
> only (without obsolete syntax support as far as i can see).
> I created a first version for a JavaCC grammar here
> https://github.com/salyh/james-mime4j/blob/4ca4a809f2deed56777c529a03e34d086309c74d/dom/src/main/jjtree/org/apache/james/mime4j/field/address/rfc822/RFC822AddressParser.jjt
> Some basics tests are here (although not steamlined/nice yet)
> https://github.com/salyh/james-mime4j/commit/4ca4a809f2deed56777c529a03e34d086309c74d
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
