New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMAP4 SSL isn't working #45823
Comments
The SSL version of the imap4 client isnt' working under 3.0. After I import imaplib
conn = imaplib.IMAP4_SSL("mailbox.rwth-aachen.de", 993) After a while I stopped the attempt with CTRL+C
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1137, in __init__
IMAP4.__init__(self, host, port)
File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 184, in __init__
self.welcome = self._get_response()
File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 907, in
_get_response
resp = self._get_line()
File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1000, in
_get_line
line = self.readline()
File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1170, in readline
char = self.sslobj.read(1)
File "/home/heimes/dev/python/py3k/Lib/ssl.py", line 160, in read
return self._sslobj.read(len)
KeyboardInterrupt |
I'll take a look at it this weekend. Bill On Nov 21, 2007 1:27 AM, Christian Heimes <report@bugs.python.org> wrote:
>
> New submission from Christian Heimes:
>
> The SSL version of the imap4 client isnt' working under 3.0. After I
> applied the patch from http://bugs.python.org/issue1210 I tried to
> connect to an IMAP server over SSL. The connection hangs.
>
> import imaplib
> conn = imaplib.IMAP4_SSL("mailbox.rwth-aachen.de", 993)
>
> After a while I stopped the attempt with CTRL+C
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1137, in __init__
> IMAP4.__init__(self, host, port)
> File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 184, in __init__
> self.welcome = self._get_response()
> File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 907, in
> _get_response
> resp = self._get_line()
> File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1000, in
> _get_line
> line = self.readline()
> File "/home/heimes/dev/python/py3k/Lib/imaplib.py", line 1170, in readline
> char = self.sslobj.read(1)
> File "/home/heimes/dev/python/py3k/Lib/ssl.py", line 160, in read
> return self._sslobj.read(len)
> KeyboardInterrupt
>
>
|
I'm still getting this with the latest SSL module fixes. I'm guessing |
Here's a fix for the 3K branch. |
Bill's patch does appear to fix the ssl-related problem. imaplib is still broken in py3k, though, due |
But that's bpo-1210, which is still open. David, do you want to Meanwhile, do we still need this issue to be open? |
On Jan 31, 2008, at 12:42 PM, Bill Janssen wrote:
I see that you are correct that 1210 is the bytes/str issue.
Unless I'm missing something, the patch "b" that you posted |
I guess I'll check it in. There's no effective test case for the When I try connecting to my local IMAP server, I get >>> c = imaplib.IMAP4("127.0.0.1")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/local/python/3k/src/Lib/imaplib.py", line 190, in __init__
raise self.error(self.welcome)
imaplib.error: b'* OK [CAPABILITY IMAP4rev1 LOGINDISABLED STARTTLS]
UpLib IMAP Server (V4r1) ready.'
>>> I think this is bug 1210. However, it is able to connect to an |
I've committed the patch. |
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: