To Craig - for some reason if I change the setting to pop.verizon.net port 995 I can’t get it to receive. Even with the updates - I can only receive using the old format: incoming.verizon.net port 110
Just a suggestion but, go in under Tools | Accounts and double check your pop3 and SMTP settings are set in the same manner as Craig listed in the previous post. When done you can check and see if its working by clicking on the diagnostics tab and then click on the diagnose button. If all is well then the POP3 and SMTP buttons will go green and show as OK. Hope that helps.
I got it to work. the POP3 port is 110 and the smtp port is 465…the old ones. I have it also set on Special Port Legacy. so far so good
I just figured out why pop.verizon.net 995 wasn’t working! Same reason the outgoing wasn’t - had to change it to special port legacy too! Duh!!!
I did “pop” and “smtp” 995, 465 and SSL legacy, and checked “use these credentials.” That along with the recently supplied update, and voila; it works. It finally sends. However, the “password” window continues to pop up. I cancel it out each time because hitting “Okay” brings it back immediately. So, I don’t know. Pretty annoying to have that window constantly popping up. It feels like a “check engine” light going on. Like a temporary fix that won’t last. Like wrapping some kind of elastic around an engine piece in your car and saying, “that oughta do it.” You know it won’t. I think I’m staying with Thunderbird until this gets corrected for real.
billbraudis: I don’t get the popup message window and it sends. the only thing that is different from what you did is that my pop is 110 not 995. Just a thought
Thanks, but didn’t verizon tell us to change from 110 to 995 a while ago for more security or something like that? I remember getting the emails about changing to 995. But I’ll try the 110 and see what happens. Thanks.
The new version workaround seems to be working for me. Using pop, smtp, 995, 465, and SSL legacy. Mails are sending, and no popups (so far).
Hi, I’m glad the workaround works, please let us know if you come across this or any other issues regarding eM Client, we’ll be happy to help.
Bill, the thing is Verizon’s servers are now not accepting the “more secure” authentication method (CRAM-MD5), the workaround we’ve released allows you to connect to the server without the use of this method. The same thing essentially is now working with Thunderbird, as the issue is held within it’s server settings, we can just workaround the issue.
Thank you for understanding,
Paul.
Hi Paul,
Thank you, it works.
Tom
Thanks for the explanation,Paul. -Bill
Still having problems with main screen,Server says invalid credentials.Have to keep canceling out.Sending / Receiving mail no problem
I just got around to installing the modified version and it seems to have solved the problem for me. Can send messages just as before the situation occurred last week. Thanks!
Hi Carol,What happens when you hit Send/Receive does the server recognize your user name and password
It worked for me after I switched to legacy SSL
I have the settings the same as everyone else.Send /Receive mail no problem.I think tomorrow I might do a fresh reinstall and see what happens
As I noted in my post earlier today, when I write a message and hit send, it goes to the Outbox and then it goes – no more dialog boxes about Authentication or needing a password. I have since sent a number of messages and have not had a problem.
Paul,
The workaround works! Thank you very much. Pasted below is the information and link from Paul that worked for me:
Official Response
Hi all, we’ve just released a workaround for the Verizon CRAM-MD5 issue that allows users to connect to the server without the use of this authentication method, please update your eM Client to this version of eM Client: http://www.emclient.com/dist/v6.0.21129/setup.msi
Check if the issue persists, and if so, please let us know as soon as possible.
Best regards,
Paul.
To late ,Once you fall out of love you can’t go back.
Just an update because I was one of the ones asking for a fix. I was so busy this week, I just got around to installing it, and it worked perfectly. Thanks so much for finding a fix to the problem! I really like eM Client and I am glad to be able to stick with it.