[Users] onet.pl pop3 STAT fails on Windows

[Colin Leroy]

Hi Theofilos,

> Is onet.pl a free email provider ? I went to their website but didn't
> understand a word :) so if that's possible, could you make me an
> account there and send me the password, so that I can try to
> troubleshoot myself ?

Thanks for opening an account for me. I've just tested the POP3 server
and everything seems to work fine, from Linux and from Windows, using
SSL, STARTTLS or plain-text connections. 

I used latest development versions of Claws Mail, but that code hasn't
changed in ages, and your version's pretty recent too.

Here's an example of what it looks like (and should look like) :

* Compte 'onet.pl' : Connexion au serveur POP3 :
  pop3.poczta.onet.pl:995.. 
[12:23:12] POP3< +OK Onet server ready.
[12:23:12] POP3> USER colinleroy at onet.pl
[12:23:12] POP3< +OK
[12:23:12] POP3> PASS ********
[12:23:17] POP3< +OK Logged in.
[12:23:17] POP3> STAT
[12:23:17] POP3< +OK 3 7874
[12:23:17] POP3> UIDL
[12:23:17] POP3< +OK
[12:23:17] POP3> LIST
[12:23:17] POP3< +OK 3 messages:
[12:23:17] POP3> QUIT
[12:23:17] POP3< +OK Logging out.

You mentioned it works using telnet from the Linux command line, but
did you try telnet from Windows ?

I am wondering if you could have an antivirus trying to transparently
proxy your mail connections, and somehow wrecking things.

Can you try the following ?

a) replace pop3.poczta.onet.pl with the IP address it should resolve
to, which is 213.180.147.145, in your Claws Mail's account settings

If that works, it is probably a proxying issue. 

If you have an antivirus, try to find and disable email protection, if
this exists...

To troubleshoot more, try from a Windows cmd.exe, the following:

nslookup pop3.poczta.onet.pl
(and check the responding nameserver's IP, too, if 127.0.0.1, this is
weird).

ping pop3.poczta.onet.pl

(the requests should go to 213.180.147.145)

telnet pop3.poczta.onet.pl 110
USER yourlogin at onet.pl
PASS yourpass
STAT
QUIT

Should get only +OK. For some reason, the guys at microsoft thought
it'd be a good idea to not have telnet on recent Windows (Vista and + I
think), so you'll first have to enable the telnet client using:

pkgmgr /iu:TelnetClient

(And for some reason, I had to issue that command twice for it to work).

Hope this helps!
-- 
Colin