Update imaplib.py to account for additional padding

[edwardmbsmith]

BPO	37407
Nosy	@warsaw, @bitdancer, @edwardmbsmith
PRs	gh-81588:Update imaplib.py to account for additional padding #14388

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2019-06-26.05:28:49.394>
labels = ['type-bug', 'expert-email', '3.9']
title = 'Update imaplib.py to account for additional padding'
updated_at = <Date 2019-06-26.05:28:49.394>
user = 'https://github.com/edwardmbsmith'

bugs.python.org fields:

activity = <Date 2019-06-26.05:28:49.394>
actor = 'edwardmbsmith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2019-06-26.05:28:49.394>
creator = 'edwardmbsmith'
dependencies = []
files = []
hgrepos = []
issue_num = 37407
keywords = []
message_count = 1.0
messages = ['346584']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'edwardmbsmith']
pr_nums = ['14388']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue37407'
versions = ['Python 3.9']

[edwardmbsmith]

Regex for imaplib should account for IMAP servers which return one or two whitespaces after the * in responses. For example when using davmail as an interpreter between exchange to IMAP

Acceptable response is as follows:

  58:24.54 > PJJD3 EXAMINE INBOX
  58:24.77 < * 486 EXISTS
  58:24.78      matched r'\* (?P<data>\d+) (?P<type>[A-Z-]+)( (?P<data2>.*))?' => ('486', 'EXISTS', None, None)
  58:24.78 untagged_responses[EXISTS] 0 += ["486"]

Davmail response:

57:50.86 > KPFE3 EXAMINE INBOX
  57:51.10 < *  953 EXISTS
  57:51.10 last 0 IMAP4 interactions:
  57:51.10 > KPFE4 LOGOUT

See additional whitespace after the * on line 2

To be fixed by allowing the regex to account for one or two whitespaces

br'\*[ ]{1,2}(?P<data>\d+) (?P<type>[A-Z-]+)( (?P<data2>.*))?'

[vadmium]

Issue #117152 was opened about the same problem with the same server, with a similar workaround of ignoring two or more spaces. But that was closed because it’s not compliant with the protocol.

[vadmium]

Perhaps close this in favour of #62353, open with more discussion since 2013