Hello:
I have been using [Pegasus Mail v4.73] under [Wine] in a Linux box for over 10 years without any issues other than maybe a PEBKAC once in a blue moon.
I have had a free email account at [gmx.net] for more or less the same time, same PMail version, same OS progressive releases, same box.
Up to this morning, I had never had any issues retrieving or sending email via POP3 / SMTP or reviewing the SPAM folder via IMAP.
As always with [PMail], a fast, smooth and uneventful retrieval.
This morning I was not able to retrieve mail from my [gmx.net] account (always with selective download, arguably PMail's best feature) or see my folders via IMAP.
The PMail POP3 Network protocol error pop-up says this:
"The host claims that either the user name or password you have supplied is invalid".
I checked and they are as always and was able to log into the [gmx.net] webmail page and review my emails without any problem.
Just in case, I changed my PW adding a special character to the string, checked it worked with webmail access and tried again with [PMail], but that was also a no-go.
This is what the [gmx.net] server says:
[code]
18:39:00.318: --- 2 Dec 2025, 18:39:00.318 ---
18:39:00.318: Connect to 'pop.gmx.net', timeout 150 seconds.
18:39:01.814: [] SSL/TLS session established
18:39:01.814: [] ECDHE-RSA-AES256-GCM-SHA384, TLSv1.2, Kx=ECDH, Au=RSA, Enc=AESGCM(256), Mac=AEAD
18:39:01.814: [] Peer's certificate name is '/C=DE/ST=Rheinland-Pfalz/L=Montabaur/O=1&1 Mail & Media GmbH/CN=mail.gmx.net'.
18:39:02.087: >> +OK POP server ready H migmx111 1MA4Kg-1vF1lE34g6-00BXHq
18:39:02.087: << USER 14067985
18:39:02.321: >> +OK password required for user "14067985"
<< 0016 PASS XXXXXXXXX
18:39:02.578: >> -ERR authentication failed
--- and after a short while ---
18:56:10.381: << RSET<cr><lf>
18:56:10.383: 26: SSL_read returned zero (socket was closed)
18:56:10.384: >>
18:56:10.384: [] OpenSSL secure session normally terminated.
18:56:10.385: --- Connection closed at 2 Dec 2025, 18:56:10.385. ---
18:56:10.386:
[/code]
It would seem that it is not a UserID ( ie: "14067985" ) problem as it gets an OK from the server.
The problem comes right after that. (ie: -ERR authentication failed)
This worked perfectly well yesterday, why not today?
Could it be that something has changed on that side?
I can wait and see if it fixes itself because it there's a glitch with the [gmx.net] servers (it is not a critical account) or contact them using Google translate as everything is in German, but it is not an easy task.
Unfortunately, creating a session log gave me the same output I posted above, so it has not been of any help.
I'd appreciate any input the list can give me.
Thanks in advance.
Best,
S.