[
https://issues.apache.org/jira/browse/TIKA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109066#comment-13109066
]
Jukka Zitting commented on TIKA-640:
------------------------------------
Note that along with TIKA-716 and Mime4J version 0.7 the configuration object
is now called MimeConfig instead of MimeEntityConfig.
> RFC822Parser should configure Mime4j not to fail reading mails containing
> more than 1000 chars in one headers text (even if folded)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: TIKA-640
> URL: https://issues.apache.org/jira/browse/TIKA-640
> Project: Tika
> Issue Type: Wish
> Components: parser
> Affects Versions: 0.9
> Environment: All
> Reporter: Jens Wilmer
> Assignee: Jukka Zitting
> Labels: mail, rfc822parser
> Fix For: 0.10
>
> Attachments: TIKA-640.patch
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Standard configuration of Mime4j accepts only 1000 characters per line and
> 1000 charackters per header. The streaming approach of tika should not need
> theese limitations, an exception is being thrown and none of the data read is
> available.
> Solution:
> Replace all occurences of:
> Parser parser = new RFC822Parser();
> by:
> MimeEntityConfig config = new MimeEntityConfig();
> config.setMaxLineLen(-1);
> config.setMaxContentLen(-1);
> Parser parser = new RFC822Parser(config);
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
