Raffaele Gambelli commented on MIME4J-265:


sorry but I don't understand if you think it is a real issue and so if you 
think to resolve it, I would have the need to know it and possibly when.

Really thanks, bye



> Possible wrong calculation of header length
> -------------------------------------------
>                 Key: MIME4J-265
>                 URL: https://issues.apache.org/jira/browse/MIME4J-265
>             Project: James Mime4j
>          Issue Type: Bug
>    Affects Versions: 0.7.2
>            Reporter: Raffaele Gambelli
>            Priority: Major
>              Labels: headers
> I've implemented a sort of mail server and I have many threads listening for 
> incoming emails.
> I'm using mime4j to parse javamail Message.
> I had only one case of:
> Caused by: org.apache.james.mime4j.io.MaxHeaderLengthLimitException: Maximum 
> header length limit exceeded
>  at 
> org.apache.james.mime4j.stream.DefaultFieldBuilder.append(DefaultFieldBuilder.java:63)
>         at 
> org.apache.james.mime4j.stream.MimeEntity.readRawField(MimeEntity.java:212)
>         at 
> org.apache.james.mime4j.stream.MimeEntity.nextField(MimeEntity.java:258)
> Looking at the code of DefaultFieldBuilder, it seems that the check over line 
> length is not done on the single line but on the overall header, I'm refering 
> to this line:
> {code:java}
> if (this.maxlen > 0 && this.buf.length() + len >= this.maxlen) {
> {code}
> Why should you add "this.buf.length" ?
> I know that there is no limit on header length, but only in its lines.
> I can't attach my eml for privacy reasons but I can confirm that I have no 
> too much long line
> Thanks

This message was sent by Atlassian JIRA

Reply via email to