james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Rusin (JIRA)" <server-...@james.apache.org>
Subject [jira] [Updated] (IMAP-374) Strange problem with a huge request from client
Date Thu, 25 Apr 2013 08:58:17 GMT

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

Andrzej Rusin updated IMAP-374:
-------------------------------

    Description: 
This description is invalid, please jump to #comment-13640497

I believe (based on some observations) that:

A) maximum client command line length in James IMAP is 8192 as defined in org.apache.james.protocols.netty.AbstractChannelPipelineFactory.MAX_LINE_LENGTH.

B) I do not think that IMAP RFC limits the line length, at least I did not find any reference
of that.

C) James IMAP does not seem to reply with BAD when it sees a too long line.

D) Some clients send quite long lines (I just saw one about 23000 characters and sky is the
limit) and they probably expect some answer, hanging indefinitely.

So:

1. If B is true, then we should not practically really limit in A; or rather the limit should
be really high. And looks like 640K is not enough for everyone anymore ;)

2. Probably C should be fixed.

  was:
This description is invalid, please jump to #comment-13641558

I believe (based on some observations) that:

A) maximum client command line length in James IMAP is 8192 as defined in org.apache.james.protocols.netty.AbstractChannelPipelineFactory.MAX_LINE_LENGTH.

B) I do not think that IMAP RFC limits the line length, at least I did not find any reference
of that.

C) James IMAP does not seem to reply with BAD when it sees a too long line.

D) Some clients send quite long lines (I just saw one about 23000 characters and sky is the
limit) and they probably expect some answer, hanging indefinitely.

So:

1. If B is true, then we should not practically really limit in A; or rather the limit should
be really high. And looks like 640K is not enough for everyone anymore ;)

2. Probably C should be fixed.

    
> Strange problem with a huge request from client
> -----------------------------------------------
>
>                 Key: IMAP-374
>                 URL: https://issues.apache.org/jira/browse/IMAP-374
>             Project: James Imap
>          Issue Type: Bug
>          Components: Protocol
>            Reporter: Andrzej Rusin
>            Assignee: Eric Charles
>
> This description is invalid, please jump to #comment-13640497
> I believe (based on some observations) that:
> A) maximum client command line length in James IMAP is 8192 as defined in org.apache.james.protocols.netty.AbstractChannelPipelineFactory.MAX_LINE_LENGTH.
> B) I do not think that IMAP RFC limits the line length, at least I did not find any reference
of that.
> C) James IMAP does not seem to reply with BAD when it sees a too long line.
> D) Some clients send quite long lines (I just saw one about 23000 characters and sky
is the limit) and they probably expect some answer, hanging indefinitely.
> So:
> 1. If B is true, then we should not practically really limit in A; or rather the limit
should be really high. And looks like 640K is not enough for everyone anymore ;)
> 2. Probably C should be fixed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message