Pop and Smtp password not recognized after upgrade to V10

After upgrade i dont have access to my pop and smtp server ,
my pop3 log
17:07:26.399|001| eM Client 10.0.3266+7060eeaac9 (Windows)
17:07:26.421|001| Account’s UID is 413affbf-b67e-452c-8633-1534d92d4d00
17:07:26.442|001| AccountBase.ChangeOnlineState : State changed to ONLINE due User
17:07:26.628|020| POP3 S: +OK Dovecot ready.
17:07:26.651|020| POP3 C: CAPA
17:07:26.679|020| POP3 S: +OK
17:07:26.702|020| POP3 S: CAPA
17:07:26.725|020| POP3 S: TOP
17:07:26.748|020| POP3 S: UIDL
17:07:26.772|020| POP3 S: RESP-CODES
17:07:26.796|020| POP3 S: PIPELINING
17:07:26.820|020| POP3 S: AUTH-RESP-CODE
17:07:26.844|020| POP3 S: USER
17:07:26.868|020| POP3 S: SASL PLAIN LOGIN GSSAPI
17:07:26.892|020| POP3 S: .
17:07:26.914|020| POP3 C: AUTH GSSAPI
17:07:26.949|020| POP3 S: + <Paramètre supprimé pour des raisons de confidentialité.>
17:07:26.976|020| POP3 C: <Paramètre supprimé pour des raisons de confidentialité.>
17:07:28.508|020| POP3 S: -ERR [AUTH] Authentication failed.

any idea for help ? My Pop and Smtp server works with plain text authentification .

After upgrade i dont have access to my pop and smtp server

I see you are getting “POP3 Authentication failed” using the latest eM Client V10.0.3266 , so could possibly be a wrong port or security policy depending on what your server supports.

What’s your POP server address, port and security policy.

Also what version of Windows do you have.

Thanks for your answer, my server address is mail.pultec.fr i use the port 995 with ssl/tls for POP3 and port 465 with ssl/tls for Smtp , this work fine before update and also with other mail clients . is it possible that the problem comes from certificates?

Ok if you are already using the following POP port settings, then yes could be your certificate.

POP (Secure)
Port 995 = Use SSL/TLS on special port (legacy)

SMTP
Port 465 = Use SSL/TLS on special port (legacy)

For a test, “try with the non secure POP ports” (if your server supports that) to see if that even works.

POP (Non Secure)
Port 110 = Use SSL/TLS if available

SMTP (Non Secure)
Port 25 = Use SSL/TLS if available

Ok after test, pop on port 110 dont work , smtp on port 25 with User and password dont work, without user and password work fine .

Another test, i have also 1 Win 11 computer, after install em client v10 dont work same errors , after install V9 work fine ?

Ok that is weird your POP mail account “now only works in V9” and not in the V10 even on your other Windows 11 computer, with any of those POP Secure or Unsecure mail port settings.

Hopefully someone else on this forum can assist you further from your log.

Cyberzork thank you for your help, after some thought I suspect that in V10 the password transfer is not done in plain text mode. I can’t find any settings for these parameters (password in plain text).

hello, same problem here, did you fix in some way? seems to me it’s a GSSAPI related problem, the client wants to use KErberos it to authenticate instead of PLAIN
I’m stuck with no SMTP allowed
thanks!

Diego

no solution, I’m also blocked and waiting for a solution.

1 Like

I have the same problem…

@diego.martin

seems to me it’s a GSSAPI related problem, the client wants to use KErberos it to authenticate instead of PLAIN

Sounds like that might be the problem as doesn’t appear to be anything to do with the POP server settings or name and password.

Need eM Client support to check the logs.

I got if fixed server side disabling GSSAPI auth

before:

SMTP S: 250-AUTH=PLAIN LOGIN GSSAPI

after:

SMTP S: 250-AUTH PLAIN LOGIN

GSSAPI was not well implemented server side so I asked support to disable it

the problem is eM Client won’t let us select authentication method manually (thunderbird does, heck even Outlook does)

hope it helps

Diego

2 Likes

Diego thank you for your feedback. Unfortunately I don’t have access to the server-side configuration, is there any way of configuring the client for plain text access?

If you carnt see an option in your mailbox server end to disable GSSAPI as @diego.martin advised, I would contact your mailbox technical support staff who should be then able to do that for you.

Version 9 used the GSSAPI mechanism only for single sign-on.

With version 10, we started using GSSAPI even for password-based logins if the server offers it. There was an increasing number of servers that require Windows token-based authentication (GSSAPI or NTLM) and don’t support plain-text logins.

Unfortunately, there are misconfigured servers in the wild that offer the GSSAPI mechanism despite not being able to authenticate with it. So far we had a single-digit number of reports of such servers and it mostly involved SMTP servers. For those users the workaround is to place --force-smtp-auth PLAIN in the Advanced Options in the Diagnostic tab of the account settings. Unfortunately, we don’t have such override for POP3 servers. We recommend contacting the server administrator to fix the settings not to offer GSSAPI when it’s not really supported.

2 Likes

Filip thank you your solution for smtp works perfectly, for the pop/imap service if someone uses Dovecot for management removing gssapi in the line auth_mechanisms = plain login # gssapi in the dovecot.conf file solves the problem after Dovecot service restart.