On Sun, 17 Jul 2005 11:05:06 +0100, Stephen Illingworth <[EMAIL PROTECTED]>
wrote:
> John Reese wrote:
>> Morning. I've been running into an error message pertaining to SSL
>> that I don't understand, and I was hoping someone had some insight.
>> Gmail provides POP access over SSL on port 587, so
John Reese wrote:
> Morning. I've been running into an error message pertaining to SSL
> that I don't understand, and I was hoping someone had some insight.
> Gmail provides POP access over SSL on port 587, so I tried to use
> poplib.POP_SSL, with the following results:
GMail uses port 995.
--
h
John Reese wrote:
> Morning. I've been running into an error message pertaining to SSL
> that I don't understand, and I was hoping someone had some insight.
> Gmail provides POP access over SSL on port 587, so I tried to use
> poplib.POP_SSL, with the following results:
[snip]
> Any suggestions
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED]:~/doc$ telnet pop.gmail.com 587
> Trying 64.233.185.111...
> Connected to pop.gmail.com.
> Escape character is '^]'.
> 220 mx.gmail.com ESMTP 13sm5173422wrl
>
> This rather looks like an unencrypted SMTP connection to me. Indeed,
>
John Reese wrote:
> Morning. I've been running into an error message pertaining to SSL
> that I don't understand, and I was hoping someone had some insight.
> Gmail provides POP access over SSL on port 587, so I tried to use
> poplib.POP_SSL, with the following results:
[...]
> socket.sslerror: (1
Morning. I've been running into an error message pertaining to SSL
that I don't understand, and I was hoping someone had some insight.
Gmail provides POP access over SSL on port 587, so I tried to use
poplib.POP_SSL, with the following results:
%python
Python 2.4.1 (#1, May 16 2005, 15:19:29)
[G
