#23647: Increase imaplib's MAXLINE to accommodate modern mailbox sizes.

This commit is contained in:
R David Murray 2015-03-22 16:17:46 -04:00
parent beed8402ca
commit 936da2a796
2 changed files with 8 additions and 5 deletions

View File

@ -45,11 +45,12 @@ AllowedVersions = ('IMAP4REV1', 'IMAP4') # Most recent first
# Maximal line length when calling readline(). This is to prevent # Maximal line length when calling readline(). This is to prevent
# reading arbitrary length lines. RFC 3501 and 2060 (IMAP 4rev1) # reading arbitrary length lines. RFC 3501 and 2060 (IMAP 4rev1)
# don't specify a line length. RFC 2683 however suggests limiting client # don't specify a line length. RFC 2683 suggests limiting client
# command lines to 1000 octets and server command lines to 8000 octets. # command lines to 1000 octets and that servers should be prepared
# We have selected 10000 for some extra margin and since that is supposedly # to accept command lines up to 8000 octets, so we used to use 10K here.
# also what UW and Panda IMAP does. # In the modern world (eg: gmail) the response to, for example, a
_MAXLINE = 10000 # search command can be quite large, so we now use 1M.
_MAXLINE = 1000000
# Commands # Commands

View File

@ -18,6 +18,8 @@ Core and Builtins
Library Library
------- -------
- Issue #23647: Increase impalib's MAXLINE to accommodate modern mailbox sizes.
- Issue #23539: If body is None, http.client.HTTPConnection.request now sets - Issue #23539: If body is None, http.client.HTTPConnection.request now sets
Content-Length to 0 for PUT, POST, and PATCH headers to avoid 411 errors from Content-Length to 0 for PUT, POST, and PATCH headers to avoid 411 errors from
some web servers. some web servers.