i got the new guide also last week…
I had to manually navigate to C:\Users\substitute your username here\AppData\Roaming\eM Client\Logs
from Thunderbird and manually select the log files to attach.
I don’t think one can change the default log folder - but Paul might know a way.
The AppData folder may be a system folder and not normally visible thru Explorer.
Kind of ironic that the eM logs obviously aren’t meant to document an “I cannot send out error” lol.
It’s going to make it much harder for users to send Paul their logs regarding this problem, I should think.
Obviously he’s working hard on the problem.
App Data is a hidden folder and you have to enable “Show hidden folders” option in Microsoft Explorer.
However you can change the logging folder in Tools > Settings > Advanced.
Hope this helps, thank you,
Paul.
Hi again,
we’re working on finding a possible solution for this issue, but we’ve came across other clues that this issue is in fact related to Verizon’s server settings.
Please see for more information here: http://www.dslreports.com/forum/r29435575-Can-t-send-email-get-550-5.7.1-Authentication-Required , It seems like Verizon is having issues with the encrypted authentication, it’s possible that while using thunderbird you might not be using the CRAM-MD5 method.
Even more information here: http://www.aqua-mail.com/forum/index.php?topic=2631.0
Our best suggestion here is again, trying to resolve the issue with Verizon’s support.
Thank you for understanding,
Paul.
Look for an email from carigk I just sent you the log file.
Exact same problem, sadly
Well I finally switched my outgoing smtp to my gmail account and I got the sending function to work. It is a bummer when both entities are pointing the finger at each other to blame and we, the customer, are stuck twiddling our thumbs. Can’t you guys somehow get together and fix this…it is interesting that if Verizon did some update that is responsible then it is only effecting emClient and no one else…makes one pause…
I have the same problem, followed your directions. New version did not fix. I have the logs, but of course, I can’t send them to you. Catch 22.
Ron, I have tried the gmail setting and I can’t get that to work either. I set it up as:
smtp.gmail.com and changed it to “use credentials” with my gmail info. What port do I set the gmal to? Maybe that is why I can’t get it to work?
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.
I just installed it and it still doesn’t work. Used the new smtp.verizon 465 and then tried the old one outgoing.verizon.net 25 Neither worked for me.
Yes 
I am no longer getting an error message, but post-workaround eMclient is not sending any of my mail. It downloads, but won’t send.
I still get the same error message. I tried setting the SMTP Security Policy to Do not use encryption as well as Use SSL/TLS if available and neither works.
Installed the update and nothing has changed. Exact same problem.
I just completed the install and tested with a send to myself and to another person, both completed successfully. No changes were made to my setup, they are still set the same including the “SSL/TLS on special port (Legacy)”. Don’t know why everyone else is still experiencing the problem and wished I could help.
I think you just figured it out!!! I didn’t have mine set to “special port legacy” - I had it set to “if available” - I changed it to your setting and the emails were sent!!! Hopefully that is it!!
Well, that now makes two of us hopefully there will be more. I also closed the app, reopened the app and, sent another email and it worked perfectly. So far so good.
Yes Yes Yes you are a genius!!! Special Port Legacy was the issue.
For POP use pop.verizon.net port 995. For SMTP use smtp.verizon.net port 465. Use SSL/TLS on special port legacy for both.Thanks Paul McGregor for for creating the fix!!!
Yee Haw!!! We are now three and growing. THANK YOU Paul McGregor, I was not looking forward to having to change email clients as I’m liking eMClient a whole lot!!! Being the curious type could you provide a little info on what you found to be the problem? Just curious and interested. At any rate, I hope everyone else is or has been able to get their’s to work and we can put this bad dog to bed.
Now having a problem with the main screen asking for authentication,keep having to hit cancel wount accept password