Socket error problem

[David LeBlanc]

Ok, that solved the problem. It was caused by the app using it's own version
of sockets; overriding the default implementation to create something called
a "TimeoutSocket", which don't work on Windows for some reason (something to
worry about later if necessary). Fortunately, all that was required to go
back to using standard sockets was to remove the override. After chasing
down a few additional bugs (it seems to ignore it's own config options or
the doc isn't good enough to describe how to set them properly), it now
actually slurps mail!! :)

The author of the package said it would never work on Windows - hah! :)
(Actually, I'm not even going to bother with the QT GUI interface, although
I'm sure that's doable as well.)

Thanks for the help!

David LeBlanc
Seattle, WA USA

> -----Original Message-----
> From: martin at v.loewis.de [mailto:martin at v.loewis.de]
> Sent: Sunday, June 09, 2002 14:03
> To: David LeBlanc
> Cc: python-list at python.org
> Subject: Re: Socket error problem
>
>
> "David LeBlanc" <whisper at oz.net> writes:
>
> > I've put print statements around all this before I first tryed
> the ml, but
> > here they are again:
>
> This is still not the right place.
>
> >         print 'poplib._init__: self.host = %s ' % self.host,
> 'self.port =
> > %s' % self.port
>
> Notice that host and port are not passed directly to socket. Instead,
> getaddrinfo is used
>
> >         for res in socket.getaddrinfo(self.host, self.port, 0,
> > socket.SOCK_STREAM):
> >             af, socktype, proto, canonname, sa = res
> >             try:
>
> Please add a line printing res inside of this try statement. Also add
> a print statement between the socket call and the connect call, so
> that we know which call it is that fails.
>
> Regards,
> Martin