james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <mime4j-...@james.apache.org>
Subject [jira] [Resolved] (MIME4J-165) provide partial information when Max Line Limit exceeded during field reading and skip to next field
Date Tue, 29 Mar 2011 17:59:06 GMT

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

Oleg Kalnichevski resolved MIME4J-165.
--------------------------------------

    Resolution: Fixed

@Rohan

I introduced optional FieldBuilder interface that can used to build MIME fields from individual
lines. Concrete implementations of this interface can choose to truncate MIME fields that
exceed a particular limit or to ignore certain fields altogether.

Please review and let me know if that resolves the issue for you.

@All

Folks, please review the changes and let me know if you find anything disagreeable. Given
this new mechanism we can now have different strategies for building MIME fields (for instance
one that supports obsolete syntax and one that does not) 

Oleg

> provide partial information when Max Line Limit exceeded during field reading and skip
to next field
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MIME4J-165
>                 URL: https://issues.apache.org/jira/browse/MIME4J-165
>             Project: JAMES Mime4j
>          Issue Type: Improvement
>    Affects Versions: 0.6
>         Environment: Java 6
>            Reporter: Rohan Hart
>            Priority: Minor
>             Fix For: 0.7
>
>
> Should the field buffer limit be reached it would be useful to be able to optionally
recover whatever field body was read in.  Further field reading should continue from the next
field.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message