Problems connecting via POP3

joss

I mostly use an email client to get my mail via pop3.
Once in a while it would not be able to connect, and it turned out to be because vivaldi had installed a new certificate. I would open my client's settings, add the new certificate to trusted, and all would be good again.
Approximately a week ago, the client could not connect with the mail server via pop3. I hadn't changed any settings. This time there is no new certificate to trust. I can still log in via webmail - no change there .
Given the timing I am wondering if it has to do with the changes to the IMAP servers (8 days ago today) mentioned above. Has something also changed for pop3 access?
pop3.vivaldi.net
plain passwords
security: required, Starttls

sending
smtp.vivaldi.net
use submission port 587

Thanks in advance

joss

Just to add some information, with these settings in my client I can send email via vivaldi.net (as has been the case for years), but I still cannot access my mailbox using pop3 to check incoming.

Perhaps whoever runs the vivaldi mail server(s) can give me a hint?

jane.n

Can you tell us which email client you're using and what the error message says exactly when the connection fails?

joss

Logging into POP server. CAPA
SSL negotiation failed. The connection with the server has been lost. Cause: (5)
Error reading from network. Cause: Connection closed by foreign host.
Eudora 7.1.0.9

jane.n

Thanks for the info. We looked into it and Eudora looks like a very old mail client, which hasn't received any updates in years. It's possible that the client doesn't support the necessary TLS protocols. For security reasons, we stopped supporting TLS 1.0 and 1.1 last September, so the client needs to be able to support TLS 1.2 or higher.

Have you considered switching to a more modern mail client, for example, Vivaldi browser's built in mail client Vivaldi Mail.

Pathduck

@jane-n Don't tell me you had to search for what Eudora was

Eudora was amazing, great and wonderful but I do suspect time has run out for the venerable old lady...

jane.n

@Pathduck said in Problems connecting via POP3:

Don't tell me you had to search for what Eudora was

I did

joss

@jane-n
Yes, Eudora has been around for a while. However, it worked until a little over a month ago. If the deprecation of TLS 1.0 & 1.1 last September was the problem, then it should have stopped working at that time, no?

Pathduck

@joss I did some digging and found this:
https://www.askwoody.com/forums/topic/did-eudora-smtp-auth-change/
https://sourceforge.net/p/hermesmail/discussion/general/thread/407979bc26/
Some possible fixes there, but you've possibly seen it before?

It appears this is a client error, and the client (Eudora) needs to fix this. I tested with a really simple client, OpenSSL to port 110 and logging in and listing messages works fine:

$ openssl s_client -quiet -starttls pop3 -connect pop3.vivaldi.net:110
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = R3
verify return:1
depth=0 CN = imap.vivaldi.net
verify return:1
+OK Dovecot ready.
capa
+OK
CAPA
TOP
UIDL
RESP-CODES
PIPELINING
AUTH-RESP-CODE
USER
SASL PLAIN LOGIN
.
user pathduck
+OK
pass xxx
+OK Logged in.
list
+OK 2 messages:
1 282287
2 700128
.
stat
+OK 2 982415
quit
+OK Logging out.

joss

@Pathduck
Thank you for your response.

After updating the software, without success, I found in the Hermes doc that one must also specify Alternate Port in the settings. That did the trick.
Usable again.