Hello Ted,
This issue is caused by the wrong server settings at the account provider’s side. We changed the authentication process to CRAM-5. If the server is wrongly set and responds to eM Client that is is capable of CRAM-5 authentication (even though it is not in fact) eM client can’t go back to simple auth and tries to use CRAM-5. This causes the error.
Please contact the mail provider to help you with correcting the server setting.
Regards,
Russel
IF emclient does not come up with a fix this is a horrific epic falure
Yes - as I’ve already stated, I’m 92yo and not fully computer and IT literate but I have difficulty understanding why a an organisation would design a ‘new’ system that is unable to cope with the common usage system
It’s not that eM Client is not compatible with “common” systems, it’s that servers are configured incorrectly to report they are CRAM-5 compliant when, in fact, they are not. So it’s really not an eM Client issue per se, but one of poor server configuration.
It would be nice, however, if eM Client could provide a workaround to this problem, as it is very difficult to have mail providers even admit they have an issue, let alone have them fix it.
Write a reply> Thanks Jay - you have explained things very succinctly - at last I think I understand. It seems that I have to change my ISP or my eM Client as “ne’er the twain shall meet” - neither one will give way. Unfortunately I have to choose my ISP as I have recently committed to another 12 months service. I now have to “find” another email program provider that will connect with my ISP and provide me with a full service - I was using Win Live Mail but that started to give me problems and there is no longer any support for it. eM Client seemed to be the answer. Dream on! Thanks and best wishes