[issue21815] imaplib truncates some untagged responses

[Roundup Robot]

Roundup Robot added the comment:

New changeset 54b36229021a by R David Murray in branch 'default':
#21815: violate IMAP RFC to be compatible with, e.g., gmail
https://hg.python.org/cpython/rev/54b36229021a

--
nosy: +python-dev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Roundup Robot]

Roundup Robot added the comment:

New changeset 53271aa4d84c by R David Murray in branch 'default':
#21815: Make the doc change match what I actually did.
https://hg.python.org/cpython/rev/53271aa4d84c

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

Changes by R. David Murray :


--
resolution:  -> fixed
stage: commit review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

R. David Murray added the comment:

I rewrote the comments, and I changed the name of the test helper class from 
GmailHandler to BracketFlagHandler, since this is not gmail specific.  (There 
was a review comment about that that was missed, I guess).

I've applied this only to 3.6 because there is a backward compatibility 
concern, as I mention in the revised comments: if a server includes a ']' in 
the text portion, the new regex will parse it incorrectly.  (Which is why the 
rfc restriction exists in the first place.)  I'm hoping that this is very 
unlikely, but because it would be a nasty bug if it happens, I only feel 
comfortable applying it to 3.6.

Thanks Lita, and everyone who reviewed.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

R. David Murray added the comment:

When you think a patch is ready for commit, you can move it to commit review, 
which will put it in my queue (not that I've been getting to that very fast 
lately, but I'm going to try to be better about it...)

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

I've checked the patch: it looks good, applies cleanly to latest default and 
passes all the tests. I'm ok with merging this as is.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Sounds good.

On Tuesday, December 22, 2015, Maciej Szulik  wrote:

>
> Maciej Szulik added the comment:
>
> Lita can you please apply the changes from latest review (from
> SilentGhost). Especially the one regarding newline, which currently fails
> to apply this patch on default. If all those will be cleaned I'll recommend
> this patch for David for inclusion.
>
> --
>
> ___
> Python tracker >
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Lita can you please apply the changes from latest review (from SilentGhost). 
Especially the one regarding newline, which currently fails to apply this patch 
on default. If all those will be cleaned I'll recommend this patch for David 
for inclusion.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Here is a patch after SlientGhost's review. I have added back the newline and 
included the comments for the imaplib documentation.

--
Added file: 
http://bugs.python.org/file41395/imaplib_after_silentghost_review.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Applied the changes that berkerpeksag made. Please review, and let me know if 
further changes need to be made.

--
Added file: http://bugs.python.org/file41366/imaplib_after_review.patch

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Lita if you still have problems or want to ask questions reach out to me on 
IRC, I'm soltysh on freenode.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Had some trouble setting up my dev environment for Python. Definitely going
to work on it today and tomorrow.

On Tue, Dec 8, 2015 at 12:33 PM, Maciej Szulik 
wrote:

>
> Maciej Szulik added the comment:
>
> Perfect, thanks!
>
> --
>
> ___
> Python tracker 
> 
> ___
>

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

I apologize, I completely forgot. I will do it this week. Thanks for the
reminder!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Perfect, thanks!

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Hey Lita, final call ;) Can you address berkerpeksag comments from review? 
Otherwise, I'm planning to take ownership of this issue and resubmit your patch 
with addressed comments.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Hi Maciej,

I am not seeing berkerpeksag review...? What was his comment? I apologize, but 
I haven't used the bug tracker in awhile.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Berker Peksag]

Berker Peksag added the comment:

Hi Lita, my review comments are at http://bugs.python.org/review/21815/ (sorry, 
I forgot to add a comment here after I made the review)

--
nosy: +berker.peksag

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Lita always look for them next to your uploaded file, there's a review link 
that points to Rietveld Code Review Tool. There you'll find all those 
information, just for future use :)

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Maciej Szulik]

Maciej Szulik added the comment:

Lita thanks for your patch!. Are you able to address berkerpeksag comments from 
review? Otherwise if you don't mind I'll take it over and I'll do that.

--
nosy: +maciej.szulik

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Here is the patch merged together. I apologize for not getting it to you sooner.

--
Added file: http://bugs.python.org/file37245/imaplib_bracket_fix.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Berker Peksag]

Changes by Berker Peksag berker.pek...@gmail.com:


--
versions: +Python 3.4, Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Sure, let me combine it into one change.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Ezio Melotti]

Ezio Melotti added the comment:

Thanks for the patches Lita, however it's better if you can upload a single 
patch with all the required changes.  This will make it easier to apply/review 
it.

--
stage: test needed - patch review

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

pinging for another review. I have included tests for the patch as well as 
documentation!

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

R. David Murray added the comment:

Just to make sure I understand: the issue is that gmail may produce flags with 
[] in them, and imaplib currently fails to process such flags when it receives 
them from gmail?  

In principle I think we would not want to allow imaplib to be used to create 
such flags unless the user specifies some sort of I want to violate the RFC 
flag (which they might want to do, for example, to run tests against gmail :)  
But currently it looks like it can?  (I haven't looked at this in enough detail 
to be sure.)  If that's true we probably have to continue to allow it for 
backward compatibility reasons, but we should document the RFC violation and 
possible consequences (an IMAP server rejecting such flags).

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Rafał Stożek]

Rafał Stożek added the comment:

Yeah, basically. The flags with [] characters are added to gmail (in my
case) by OtherInbox's Organizer app. I contacted them but haven't heard
back yet.

On Wed, Jul 16, 2014 at 4:07 PM, R. David Murray rep...@bugs.python.org
wrote:


 R. David Murray added the comment:

 Just to make sure I understand: the issue is that gmail may produce flags
 with [] in them, and imaplib currently fails to process such flags when it
 receives them from gmail?

 In principle I think we would not want to allow imaplib to be used to
 create such flags unless the user specifies some sort of I want to violate
 the RFC flag (which they might want to do, for example, to run tests
 against gmail :)  But currently it looks like it can?  (I haven't looked at
 this in enough detail to be sure.)  If that's true we probably have to
 continue to allow it for backward compatibility reasons, but we should
 document the RFC violation and possible consequences (an IMAP server
 rejecting such flags).

 --

 ___
 Python tracker rep...@bugs.python.org
 http://bugs.python.org/issue21815
 ___


--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:


 R. David Murray added the comment:

 Just to make sure I understand: the issue is that gmail may produce flags
 with [] in them, and imaplib currently fails to process such flags when it
 receives them from gmail?

 This is correct. Gmail allows you to create flags with [], and the
Response_code regex doesn't process them properly.

 In principle I think we would not want to allow imaplib to be used to
 create such flags unless the user specifies some sort of I want to violate
 the RFC flag (which they might want to do, for example, to run tests
 against gmail :)  But currently it looks like it can?  (I haven't looked at
 this in enough detail to be sure.)  If that's true we probably have to
 continue to allow it for backward compatibility reasons, but we should
 document the RFC violation and possible consequences (an IMAP server
 rejecting such flags).

 Yes, currently we can. I've posted the code in order to do this. This is
basically the result.

 first_id = msg_ids.split()[0]
 mail.store(first_id, +FLAGS, [test])
('OK', [b'1 (FLAGS (\\Seen Answered [test] NotJunk $NotJunk [Brackets]
[testing2]))'])

However, I would think it would be the server's job to uphold this rule,
not the library. The server should return with a BAD response, but right
now, Gmail allows you to do this.

Should we throw a warning in the store method? Otherwise, I can update
the documenation in the store method stating that having '[]' is allowed
but violates the RFC protocol.

 --

 ___
 Python tracker rep...@bugs.python.org
 http://bugs.python.org/issue21815
 ___


--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

R. David Murray added the comment:

Postel's Law says: be conservative in what you do, be liberal in what you 
accept from others.  So the client should not violate the RFC when sending data 
to the server.  The server, on the other hand, by that law could accept dirty 
data if it can do something reasonable with it...except that in general the 
IMAP RFC in particular says don't do that.  IMAP servers are supposed to be 
IMAP RFC sticklers, even when accepting input.  So gmail is broken for some 
definition of broken, and so is imaplib.

Since the code has been this way for a long time, and gmail does in fact accept 
it, I think a doc warning about []s violating the RFC should be sufficient; a 
warning would probably just be annoying to little real benefit.

--
versions: +Python 3.4, Python 3.5

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Okay, sounds good. I will also create a patch in the documentation that 
explains this, as well as comment on the regex patch.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Here is a patch for test_imaplib.py, adding the test for brackets. It should 
fail with the current version of imaplib, but should pass with the 
imap_regex.patch.

--
Added file: http://bugs.python.org/file35977/test_imaplib.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Updated the documentation in imaplib.rst to describe the RFC violation.

--
versions:  -Python 3.4, Python 3.5
Added file: http://bugs.python.org/file35978/imap_doc.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Updated my regex patch to include a comment about how we are violating the RFC 
and allowing all characters rather thane excluding the ] character.

--
Added file: http://bugs.python.org/file35979/imap_regex.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

I have a patch for this. With my patch, the debug output is fixed.

--
keywords: +patch
Added file: http://bugs.python.org/file35962/imap_regex.patch

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Here is a log of the output.

--
Added file: http://bugs.python.org/file35963/imaplib_log_with_patch.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Jessica McKellar]

Jessica McKellar added the comment:

Thanks for the patch, Lita! Lita: I have some patch feedback for you at the end 
of this message.

--

Lita and I talked about this a bit via email; here's some additional context 
from that conversation:

There were a couple of questions to answer before working on a patch:

1. Are brackets allowed in flag names according to the RFC?
2. If brackets aren't allowed, do other popular IMAP services permit them 
anyway? If so, we should consider allowing them even though this deviates from 
the RFC.

To answer (1), my read of http://tools.ietf.org/html/rfc3501 is as follows:

a. Look at http://tools.ietf.org/html/rfc3501, search for PERMANENTFLAGS 
definition. Note use of flag-perm variable.

b. Search for flag-perm. Find it on page 85, in section 9, Formal Syntax. 
This is describing the formal syntax in Backus-Naur Form (BNF).

c. flag-perm = flag / \*

d. flag = \Answered / \Flagged / \Deleted /
\Seen / \Draft / flag-keyword / flag-extension
; Does not include \Recent

e. flag-keyword = atom

f. atom = 1*ATOM-CHAR

g. ATOM-CHAR = any CHAR except atom-specials

h. atom-specials = ( / ) / { / SP / CTL / list-wildcards /
quoted-specials / resp-specials

i. resp-specials = ]

My reading of this series of definitions is that ] is not allowed in flag 
names.

To answer (2), Lita ran some tests against GMail's IMAP service and found that 
it does let you create flags containing ].

--

Patch feedback:

1. Can you attach the script you used to probe GMail's IMAP service for what 
flag names were permitted?

2. Since this patch causes us to violate the RFC (but with good reason!), can 
you add a comment above the regex noting the violation and stating what 
characters we allow for flags and why?

3. This change need tests.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Ezio Melotti]

Changes by Ezio Melotti ezio.melo...@gmail.com:


--
nosy: +ezio.melotti
stage:  - test needed

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Yes! I agree, this change will need tests. I will start working on creating 
those now.

Here is test I did to create a flag with brackets.

import imaplib

mail = imaplib.IMAP4_SSL('imap.gmail.com')
mail.login('usern...@gmail.com', 'password') # Enter your login here
mail.select('test') # Mailbox selection. I have a test inbox with 6
# messages in it.
code, [msg_ids] = mail.search(None, 'ALL')
first_id = msg_ids.split()[0]
mail.store(first_id, +FLAGS, [test])
typ, response = mail.fetch(first_id, '(FLAGS)')
print(Flags: %s % response)
mail.close()
mail.logout()

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

Here is the code in order to see the bug.

imaplib.Debug = 5
mail = imaplib.IMAP4_SSL('imap.gmail.com')
mail.login(username, password) # Enter your login here
mail.select('test')

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Changes by Lita Cho lita@gmail.com:


--
nosy: +Lita.Cho, jesstess

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Lita Cho]

Lita Cho added the comment:

I was reading the RFC spec, and it looks like it doesn't specificy '[' and ']' 
are not allowed in the PERNANENTFLAGS names. 

I can try to add a fix for this. But if anyone else knows if you are not 
allowed to have '[' or ']' in flag names, please let me know.

--

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[R. David Murray]

Changes by R. David Murray rdmur...@bitdance.com:


--
components: +email
nosy: +barry, r.david.murray

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Rafał Stożek]

New submission from Rafał Stożek:

The regexp in Response_code checks for the existence of [] characters. The 
problem is that the strings may contain [] characters. I attach debug log which 
shows the data received from server and what the python extracted from it.

You can see that the PERNANENTFLAGS is truncated and everything from the ] 
character is lost:

(\Answered \Flagged \Draft \Deleted \Seen OIB-Seen-OIB/Social Networking 
$Phishing $Forwarded OIB-Seen-OIB/Home OIB-Seen-OIB/Shopping OIB-Seen-INBOX 
OIB-Seen-OIB/Business OIB-Seen-OIB/Entertainment $NotJunk $NotPhishing $Junk 
OIB-Seen-[Gmail

--
components: Library (Lib)
messages: 221091
nosy: rafales
priority: normal
severity: normal
status: open
title: imaplib truncates some untagged responses
type: behavior
versions: Python 2.7

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue21815] imaplib truncates some untagged responses

[Rafał Stożek]

Rafał Stożek added the comment:

Oops, forgot the file.

--
Added file: http://bugs.python.org/file35706/imaplib_log.txt

___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21815
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com