26 May
2016
26 May
'16
12:34 p.m.
On 05/26/2016 10:06 AM, Tim wrote:
Allegedly, on or about 26 May 2016, Samuel Sieb sent:
use pop3, not pop3s as the protocol.
That'll only work if the service provider has POP3 enabled. Their help page didn't list anything but secure connections. So, a failure to use POP3 has to be assessed with that in mind.
Please follow the thread. He was getting a command error when connecting with pop3s. I gave him a stunnel configuration so that he could use wireshark to see what the command is. stunnel will do the ssl part, so he needs to connect to stunnel with pop3, not pop3s.