This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tahnoon
Recipients barry, r.david.murray, tahnoon
Date 2013-06-17.09:34:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371461656.34.0.478016323324.issue18153@psf.upfronthosting.co.za>
In-reply-to
Content
Hi David

Adding the following post and response from the davmail author/ maintainers site. He seems to have fixed it in davmail and suggests the following fix in imaplib.py if there is a desire to amend it to allow stray spaces

Le 15/06/2013 08:19, tahnoon a écrit :

    Hi Mickael. I've continued to post on https://bugs.python.org and the
    imaplib maintainer has agreed to look at fixing this on imaplib if I
    can provide the appropriate unit test to replicate the problem. I'm
    not really a programmer so any pointers you can give me on how to set
    up a server simulation that approximates davmail or if you have one
    already set up as part of your development that would help solve this
    at the client end. Thanks

Well, it's not easy to reproduce without a backend Exchange server.
Basically it should accept multiple spaces after star in untagged response.

untested fix of imaplib.py:
replace
Untagged_response = re.compile(r'* (?P[A-Z-]+)( (?P.))?')
with
Untagged_response = re.compile(r'*[ ]+(?P[A-Z-]+)( (?P.))?')

Note that I disabled this non standard behavior in latest DavMail
release, you can enable it in DavMail settings (KeepAlive).

Not sure if that closes this issue or if you still think a test case is needed?
History
Date User Action Args
2013-06-17 09:34:16tahnoonsetrecipients: + tahnoon, barry, r.david.murray
2013-06-17 09:34:16tahnoonsetmessageid: <1371461656.34.0.478016323324.issue18153@psf.upfronthosting.co.za>
2013-06-17 09:34:16tahnoonlinkissue18153 messages
2013-06-17 09:34:15tahnooncreate