Re: What might suddenly provoke this poplib error?

[The OP has stated that the problem has been fixed. The following are generic comments about troubleshooting.] On 2022-10-14 11:31:56 +1300, dn wrote: > On 14/10/2022 01.47, Chris Green wrote: > >File "/usr/lib/python3.10/poplib.py", line 157, in _getresp > > raise

Re: What might suddenly provoke this poplib error?

Peter J. Holzer wrote: > [-- text/plain, encoding quoted-printable, charset: us-ascii, 28 lines --] > > On 2022-10-13 13:47:07 +0100, Chris Green wrote: > > I have a short python3 program that collects E-Mails from a 'catchall' > > mailbox, sends the few that might be interesting to me and dumps

Re: What might suddenly provoke this poplib error?

MRAB wrote: [snip boring code] > > > > It seems to be saying that the POP3 server has a problem, if so there's not > > much I can do about it as it's my hosting provider's mail server. Is it > > really saying the server has a problem? > > > As you've already ascertained that it's a server

Re: What might suddenly provoke this poplib error?

On 14/10/2022 01.47, Chris Green wrote: I have a short python3 program that collects E-Mails from a 'catchall' mailbox, sends the few that might be interesting to me and dumps the rest. It has suddenly (after working for some years) started throwing the following:- Traceback (most recent

Re: What might suddenly provoke this poplib error?

On 2022-10-13 13:47:07 +0100, Chris Green wrote: > I have a short python3 program that collects E-Mails from a 'catchall' > mailbox, sends the few that might be interesting to me and dumps the > rest. > > It has suddenly (after working for some years) started throwing the > following:- [...] >

Re: What might suddenly provoke this poplib error?

On 2022-10-13 13:47, Chris Green wrote: I have a short python3 program that collects E-Mails from a 'catchall' mailbox, sends the few that might be interesting to me and dumps the rest. It has suddenly (after working for some years) started throwing the following:- Traceback (most recent

What might suddenly provoke this poplib error?

I have a short python3 program that collects E-Mails from a 'catchall' mailbox, sends the few that might be interesting to me and dumps the rest. It has suddenly (after working for some years) started throwing the following:- Traceback (most recent call last): File

Re: What might suddenly provoke this poplib error?

A further little bit of information, I tried running getCatchall.py from the command prompt and there was a long wait before it output the same error message. I.e. it looks rather as if the server is not responding to requests. (A 'long wait' is a minute or two) -- Chris Green · --

[issue486079] poplib contains unuseable code

Change by admin : -- github: None -> 35603 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue403329] Update poplib to use re

Change by admin : -- github: None -> 33759 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue12706] timeout sentinel in ftplib and poplib documentation

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Change by Ned Deily : -- Removed message: https://bugs.python.org/msg342092 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Ned Deily added the comment: New changeset 942cc04ae44825ea120e3a19a80c9b348b8194d0 by larryhastings (Ned Deily) in branch '3.4': [3.4] bpo-32981: Fix catastrophic backtracking vulns (GH-5955) (#6035) https://github.com/python/cpython/commit/942cc04ae44825ea120e3a19a80c9b348b8194d0

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

STINNER Victor added the comment: FYI I tracked this vulnerability at: http://python-security.readthedocs.io/vuln/cve-2018-1060_difflib_and_poplib_catastrophic_backtracking.html -- nosy: +vstinner ___ Python tracker

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Ned Deily added the comment: > Is this ready to close? The fixes are now available from the cpython repo for all current security and maintenance branches (3.4 to 3.7 plus 2.7). They are now released in 3.6.5rc1 and will be available in the next releases of other branches:

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Larry Hastings added the comment: Is this ready to close? -- ___ Python tracker ___ ___

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Larry Hastings added the comment: New changeset 937ac1fe069a4dc8471dff205f553d82e724015b by larryhastings (Ned Deily) in branch '3.5': [3.5] bpo-32981: Fix catastrophic backtracking vulns (GH-5955) (#6034)

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Larry Hastings added the comment: New changeset 942cc04ae44825ea120e3a19a80c9b348b8194d0 by larryhastings (Ned Deily) in branch '3.4': [3.4] bpo-32981: Fix catastrophic backtracking vulns (GH-5955) (#6035)

[issue32981] Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061)

Change by Ned Deily <n...@python.org>: -- keywords: +security_issue nosy: +larry priority: normal -> critical title: Catastrophic backtracking in poplib and difflib -> Catastrophic backtracking in poplib (CVE-2018-1060) and difflib (CVE-2018-1061) versions: +Python 2.7

[issue32981] Catastrophic backtracking in poplib and difflib

Change by Ned Deily : -- pull_requests: +5797 ___ Python tracker ___ ___ Python-bugs-list

[issue32981] Catastrophic backtracking in poplib and difflib

Change by Ned Deily : -- pull_requests: +5796 ___ Python tracker ___ ___ Python-bugs-list

[issue32981] Catastrophic backtracking in poplib and difflib

Benjamin Peterson added the comment: New changeset c9516754067d71fd7429a25ccfcb2141fc583523 by Benjamin Peterson in branch '3.6': [3.6] bpo-32981: Fix catastrophic backtracking vulns (GH-5955)

[issue32981] Catastrophic backtracking in poplib and difflib

Benjamin Peterson added the comment: New changeset e052d40cea15f582b50947f7d906b39744dc62a2 by Benjamin Peterson in branch '2.7': [2.7] bpo-32981: Fix catastrophic backtracking vulns (GH-5955)

[issue32981] Catastrophic backtracking in poplib and difflib

Benjamin Peterson added the comment: New changeset 0902a2d6b2d1d9dbde36aeaaccf1788ceaa97143 by Benjamin Peterson (Miss Islington (bot)) in branch '3.7': bpo-32981: Fix catastrophic backtracking vulns (GH-5955)

[issue32981] Catastrophic backtracking in poplib and difflib

Change by Benjamin Peterson : -- pull_requests: +5737 ___ Python tracker ___ ___

[issue32981] Catastrophic backtracking in poplib and difflib

Change by Benjamin Peterson : -- pull_requests: +5736 ___ Python tracker ___ ___

[issue32981] Catastrophic backtracking in poplib and difflib

Benjamin Peterson added the comment: New changeset 0e6c8ee2358a2e23117501826c008842acb835ac by Benjamin Peterson (Jamie Davis) in branch 'master': bpo-32981: Fix catastrophic backtracking vulns (#5955)

[issue32981] Catastrophic backtracking in poplib and difflib

Change by miss-islington : -- keywords: +patch pull_requests: +5735 stage: -> patch review ___ Python tracker

[issue32981] Catastrophic backtracking in poplib and difflib

Change by Raymond Hettinger : -- nosy: +tim.peters ___ Python tracker ___ ___

[issue32981] Catastrophic backtracking in poplib and difflib

ot; } ], "suffix" : "##" }, "pattern" : "\\s*#?\\s*$", "filesIn" : [ [ "Lib/difflib.py" ] ], "nPumpsFor10Sec" : "48325" } -- components: Library (L

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Change by Christian Heimes : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed type: -> behavior ___ Python tracker

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: New changeset 8d4d17399fb82801eaaca5beeb97a19908b40222 by Christian Heimes in branch '2.7': bpo-31518: Change TLS protocol for Debian (#3661) https://github.com/python/cpython/commit/8d4d17399fb82801eaaca5beeb97a19908b40222 --

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: New changeset aab225840360719516eca55a7a69cfee45aee2af by Christian Heimes in branch '3.6': bpo-31518: Change TLS protocol for Debian (#3660) https://github.com/python/cpython/commit/aab225840360719516eca55a7a69cfee45aee2af --

[issue12706] timeout sentinel in ftplib and poplib documentation

Change by Marcel Widjaja : -- pull_requests: +5156 stage: needs patch -> patch review ___ Python tracker ___

[issue12706] timeout sentinel in ftplib and poplib documentation

Greg added the comment: Completely forgot about this, please take my patch and submit a pr On Fri, Dec 29, 2017 at 10:55 AM, Marcel Widjaja wrote: > > Marcel Widjaja added the comment: > > Greg, I wonder if you are planning

[issue12706] timeout sentinel in ftplib and poplib documentation

Marcel Widjaja added the comment: Greg, I wonder if you are planning to submit a PR for your patch? If not, I'm plan to take your patch, make some minor adjustment and submit a PR. -- nosy: +mawidjaj ___ Python tracker

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: PR 3660 and PR 3661 address most of the failing tests. The two failures in msg302531 are discussed in issue #31453. -- ___ Python tracker

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Matthias Klose added the comment: Christian, I assume you'd like to see a test which can be done at *runtime*, not *buildtime*. Assuming you have that openssl upstream patch available in your build dependency, would that help with the detection? If yes, I'll talk to Debian's and Ubuntu's

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Changes by Christian Heimes : -- pull_requests: +3650 ___ Python tracker ___ ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Changes by Christian Heimes : -- keywords: +patch pull_requests: +3649 stage: -> patch review ___ Python tracker ___

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: Two tests are failing in 3.7 branch: == ERROR: test_PROTOCOL_TLS (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Christian Heimes added the comment: 3.7 does no longer use PROTOCOL_TLSv1 except for test_ssl.py, see #31346 By the way Debian Sid/Buster broke support for SSL and TLS < 1.2. see #31453. There is no way to enable the protocols from Python. -- versions: -Python 3.7

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

Matthias Klose added the comment: failing tests: https://ci.debian.net/data/packages/unstable/amd64/p/python3.6/latest-autopkgtest/log.gz -- ___ Python tracker

[issue31518] ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally

nosy: christian.heimes, doko priority: normal severity: normal status: open title: ftplib, urllib2, poplib, httplib, urllib2_localnet use ssl.PROTOCOL_TLSv1 unconditionally versions: Python 2.7, Python 3.6, Python 3.7 ___ Python tracker <rep...@bugs.python.

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

STINNER Victor added the comment: > The bug should now be catched. Oops, I wanted to write: "should now be fixed", sorry! -- ___ Python tracker ___

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

STINNER Victor added the comment: The bug should now be catched. -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

STINNER Victor added the comment: New changeset 800e4b7ad6b6f86c17408429852dfb47493d366e by Victor Stinner in branch '2.7': bpo-30329: Catch Windows error 10022 on shutdown() (#1538) (#1624) https://github.com/python/cpython/commit/800e4b7ad6b6f86c17408429852dfb47493d366e --

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

Changes by STINNER Victor : -- pull_requests: +1713 ___ Python tracker ___ ___

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

STINNER Victor added the comment: New changeset c9ba45d1b71d86321e5422e8a2cbe6e52aaba6f4 by Victor Stinner in branch '3.5': bpo-30329: Catch Windows error 10022 on shutdown() (#1538) (#1621) https://github.com/python/cpython/commit/c9ba45d1b71d86321e5422e8a2cbe6e52aaba6f4 --

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

STINNER Victor added the comment: New changeset aaa053652556aa4e59cb68f3983a09ced1d1fe2a by Victor Stinner in branch '3.6': bpo-30329: Catch Windows error 10022 on shutdown() (#1538) (#1620) https://github.com/python/cpython/commit/aaa053652556aa4e59cb68f3983a09ced1d1fe2a --

[issue30329] poplib and imaplib should catch "OSError: [WinError 10022] An invalid argument was supplied" on shutdown

Changes by STINNER Victor <victor.stin...@gmail.com>: -- components: +Library (Lib) title: test_imaplib.test_login_cram_md5(): OSError: [WinError 10022] An invalid argument was supplied on AMD64 Windows8.1 Non-Debug 3.6 -> poplib and imaplib should catch "OSError: [

[issue12706] timeout sentinel in ftplib and poplib documentation

Berker Peksag added the comment: Documentation changes look good to me. However, I'd prefer using socket._GLOBAL_DEFAULT_TIMEOUT in the timeout parameter of FTP.connect(). -- keywords: +easy nosy: +berker.peksag versions: +Python 3.5, Python 3.6, Python 3.7 -Python 2.7, Python 3.2,

Re: How to program round this poplib error?

, in _getline > raise error_proto('line too long') > poplib.error_proto: line too long > > > Does anyone have any idea how I can program around this somehow? This is bug "https://bugs.python.org/issue23906;. Following a recommendation from "Laura Creighton", I work around it by import poplib; poplib._MAXLINE=5 -- https://mail.python.org/mailman/listinfo/python-list

Re: How to program round this poplib error?

using bare "except:". > Always specify which exceptions you are trying to catch. > Yes, I know, but it doesn't really relate to the problem does it. > In this case, I think there are two problems. Firstly, I think > whoever implemented poplib mis-read the POP3 specification,

Re: How to program round this poplib error?

Mark Lawrence wrote: > On 10/03/2016 12:04, c...@isbd.net wrote: > > I have a (fairly simple) Python program that scans through a > > 'catchall' E-Mail address for things that *might* be for me. It sends > > anything that could be for me to my main E-Mail and discards

Re: How to program round this poplib error?

, I can't even identify > it so that the trap could report the error and tell me which message > was causing it. You really, really should not be using bare "except:". Always specify which exceptions you are trying to catch. In this case, I think there are two problems. Firstly, I thi

Re: How to program round this poplib error?

On 10/03/2016 12:04, c...@isbd.net wrote: I have a (fairly simple) Python program that scans through a 'catchall' E-Mail address for things that *might* be for me. It sends anything that could be for me to my main E-Mail and discards the rest. However I *occasionally* get an error from it as

How to program round this poplib error?

I have a (fairly simple) Python program that scans through a 'catchall' E-Mail address for things that *might* be for me. It sends anything that could be for me to my main E-Mail and discards the rest. However I *occasionally* get an error from it as follows:- Traceback (most recent call

[issue23906] poplib maxline behaviour may be wrong

R. David Murray added the comment: If maxline is too small, messages won't get through. If maxline is too large *huge* messages will get through...and the DDOS danger of exhausting the server's resources will occur. So, we really ought to provide a way to limit the maximum message size

[issue23906] poplib maxline behaviour may be wrong

shiyao.ma added the comment: Instead of setting a MAXSIZE for the email body, rasing up the MAXLINE might be more meaningful. Consider the case of MAXSIZE, it's essentially the same as MAXLINE. If MAXSIZE is relatively small, some messages won't pass through. If the MAXSIZE is relatively

[issue16041] poplib: unlimited readline() from connection

R. David Murray added the comment: It has been, see the referenced issue. Now we just need someone to write a patch. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041

[issue23906] poplib maxline behaviour may be wrong

R. David Murray added the comment: Note that the max message size solution can be applied to the maintenance releases as a fix for this issue by choosing a suitable large default message size. The 'feature' part is just the part exposing the size limit in the library API...that part is a

[issue16041] poplib: unlimited readline() from connection

Stephen Coulson added the comment: Broke for me today. Hacked the _MAXLINE to get around it. I don't see any size limit on multi-line in rfc. Only requirement is dot-stuffing. I think this fix might need a rethink. -- nosy: +scoulson ___ Python

[issue23906] poplib maxline behaviour may be wrong

Chris Smowton added the comment: Created #24706 to describe the unflushed connection problem. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___

[issue23906] poplib maxline behaviour may be wrong

Chris Smowton added the comment: Why wouldn't that fix the problem? The issue is poplib not tolerating server behaviour seen in the wild, and if you limit by message size not line length you shouldn't see this problem? (Side note, I'm surprised not to have been emailed when you replied, any

[issue24706] poplib: Line too long error causes knock-on failure to retrieve all subsequent messages

New submission from Chris Smowton: As mentioned in #23906, when poplib bails from receiving a message with a 'line too long' error it neither flushes nor re-establishes the TCP connection. This means that subsequent commands fail because instead of the expected response we receive part

[issue23906] poplib maxline behaviour may be wrong

R. David Murray added the comment: Sorry, I was unclear. In order to implement maximum message size we have to do a bit more to the logic than just use the max message size as the readline limit. But it does seem like the right approach to me. --

[issue16041] poplib: unlimited readline() from connection

Chris Smowton added the comment: +1 to the above; suggest this should be rolled back and replaced with a total message size limit. -- nosy: +Chris Smowton ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041

[issue23906] poplib maxline behaviour may be wrong

what you're actually trying to defend against here. You could also either use the +OK XXX octets line to set a more conservative limit (and fail fast if it announces intent to send more than your limit). As above the workaround was to insert import poplib; poplib._MAXLINE = 100 at the top

[issue23906] poplib maxline behaviour may be wrong

R. David Murray added the comment: Could you open a separate bug for the recovery problem, please? Using a maximum message size would not solve this problem, but it would give the library user control of when it failed, so it is a good feature request. --

[issue16041] poplib: unlimited readline() from connection

Ingo Ruhnke added the comment: This fix has broken mail retrieval from both gmx.de, gmail.com and plenty of other provider. It manifests in getmail as: Retrieval error: server for BrokenUIDLPOP3SSLRetriever:1860...@pop.gmx.net:995 is broken; offered message 239 but failed to provide it.

[issue23906] poplib maxline behaviour may be wrong

Ingo Ruhnke added the comment: This also breaks mail retrieval from both gmx.de and gmail.com (two rather large and popular mail provider). After setting _MAXLINE in/usr/lib/python2.7/poplib.py to some arbitrary higher number mail retrieval from both services worked fine again. This this

[issue23906] poplib maxline behaviour may be wrong

Changes by R. David Murray rdmur...@bitdance.com: -- versions: +Python 3.4, Python 3.5, Python 3.6 -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___

[issue23906] poplib maxline behaviour may be wrong

problems, quite aside from the length of message body lines, so we ended up with a very large MAXLINE there. It may be that we have no choice except to do something similar in poplib. An interesting question in this context is what smtp servers do. since if anyone was going to reject messages

[issue23906] poplib maxline behaviour may be wrong

Changes by Remy Blank remy.bl...@pobox.com: -- nosy: +rblank ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue23906 ___ ___ Python-bugs-list mailing

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

Roundup Robot added the comment: New changeset 6ea762200e27 by R David Murray in branch 'default': #21804: Add RFC 6856 (UTF8) support to poplib. https://hg.python.org/cpython/rev/6ea762200e27 -- nosy: +python-dev ___ Python tracker rep

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

R. David Murray added the comment: Thanks, Milan. -- resolution: - fixed stage: commit review - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21804 ___

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

Changes by R. David Murray rdmur...@bitdance.com: -- stage: - commit review type: - enhancement ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21804 ___

[issue16041] poplib: unlimited readline() from connection

Roundup Robot added the comment: New changeset 339f877cca11 by Benjamin Peterson in branch '2.7': in poplib, limit maximum line length that we read from the network (closes #16041) https://hg.python.org/cpython/rev/339f877cca11 -- resolution: - fixed stage: patch review - resolved

[issue16041] poplib: unlimited readline() from connection

Matthias Klose added the comment: this looks ok to me, can we apply this for 2.7.9? -- nosy: +doko ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041 ___

[issue16041] poplib: unlimited readline() from connection

Berker Peksag added the comment: Here is a patch for 2.7. -- nosy: +berker.peksag stage: needs patch - patch review Added file: http://bugs.python.org/file36970/issue16041_27.diff ___ Python tracker rep...@bugs.python.org

[issue16041] poplib: unlimited readline() from connection

Changes by Berker Peksag berker.pek...@gmail.com: Added file: http://bugs.python.org/file36971/issue16041_27.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041 ___

[issue16041] poplib: unlimited readline() from connection

Changes by Berker Peksag berker.pek...@gmail.com: Removed file: http://bugs.python.org/file36970/issue16041_27.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041 ___

[issue16041] poplib: unlimited readline() from connection

Changes by Georg Brandl ge...@python.org: -- versions: -Python 3.1 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041 ___ ___ Python-bugs-list

[issue16041] poplib: unlimited readline() from connection

Roundup Robot added the comment: New changeset 76be07730f8d by Georg Brandl in branch '3.2': Issue #16041: CVE-2013-1752: poplib: Limit maximum line lengths to 2048 to https://hg.python.org/cpython/rev/76be07730f8d -- ___ Python tracker rep

[issue16041] poplib: unlimited readline() from connection

Changes by Georg Brandl ge...@python.org: -- versions: -Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16041 ___ ___ Python-bugs-list

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

Milan Oberkirch added the comment: I got the Exception policy of the POP3 class wrong (ignore my review comment on that) and needed to add 'UTF8' to the list of optional commands. -- Added file: http://bugs.python.org/file35823/poputf8-v2.patch ___

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

New submission from Milan Oberkirch: The poplib classes already use Unicode internally (for everything but capability names). So to implement the UTF8 part of RFC 6856 we only need to enable the user to switch to UTF-8 mode if supported by the server. -- components: email files

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

Changes by Milan Oberkirch milan...@oberkirch.org: Removed file: http://bugs.python.org/file35686/poputf8.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21804 ___

[issue21804] Implement thr UTF8 command (RFC 6856) in poplib.

Changes by Milan Oberkirch milan...@oberkirch.org: Added file: http://bugs.python.org/file35687/poputf8.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21804 ___

[issue12706] timeout sentinel in ftplib and poplib documentation

Greg added the comment: In the definition of FTP.connect(), I've changed the code to actually use None as a lack-of-explicit-timeout sentinel instead of -999. For FTP and FTP_TLS, I've changed the documentation to reflect what the code is doing. -- keywords: +patch nosy: +εσχατοκυριος

[issue20549] Use specific asserts in mailbox, smtplib and poplib tests

Roundup Robot added the comment: New changeset 1c3fcba31708 by Serhiy Storchaka in branch '2.7': Issue #20549: Use specific asserts in mailbox, smtplib and poplib tests. http://hg.python.org/cpython/rev/1c3fcba31708 New changeset bd1d6916b689 by Serhiy Storchaka in branch '3.3': Issue #20549

[issue20549] Use specific asserts in mailbox, smtplib and poplib tests

Serhiy Storchaka added the comment: Thank you for your review David. -- assignee: - serhiy.storchaka resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org

[issue20549] Use specific asserts in mailbox, smtplib and poplib tests

New submission from Serhiy Storchaka: The proposed patch makes the mailbox, smtplib and poplib modules tests use more specific asserts. This will provide more useful failure report. -- components: Tests files: test_mailbox_asserts.patch keywords: easy, patch messages: 210546 nosy

[issue20549] Use specific asserts in mailbox, smtplib and poplib tests

R. David Murray added the comment: Looks good to me. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20549 ___ ___

[issue20352] Add support for AUTH command to poplib

Daniël van Eeden added the comment: As far as I understood the RFC: A client should send CAPA and check if there is a SASL tag in the response (e.g. SASL PLAIN). === +OK Dovecot ready. AUTH PLAIN base64_encoded_info +OK Logged in. LIST

[issue20352] Add support for AUTH command to poplib

R. David Murray added the comment: imaplib has an API for handling that kind of thing. Maybe we can model the poplib support off of that API. It would be nice to be consistent, assuming it in fact makes sense for poplib as well. -- ___ Python

[issue20352] Add support for AUTH command to poplib

status: open title: Add support for AUTH command to poplib versions: Python 2.7 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue20352 ___ ___ Python-bugs-list mailing

[issue20352] Add support for AUTH command to poplib

R. David Murray added the comment: This is basically rfc 5034 support? Sounds like a good idea. I'm going to mark this issue as 'easy' because it isn't a whole lot of code, but for anyone who wants to tackle it, know that understanding the RFC and getting it *right* is not necessarily

[issue19784] No SSL match_hostname() in poplib

Roundup Robot added the comment: New changeset 1ce752754280 by Christian Heimes in branch 'default': Issue #19784: poplib now supports SSLContext.check_hostname and server name http://hg.python.org/cpython/rev/1ce752754280 -- nosy: +python-dev

  1   2   >