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.
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 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 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.
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.