Forum Discussion
EMAIL not going out from emClient
It looks like the email client has recommended a solution that works, and appears to be working now.
One of the options in the SMTP setup is "Use SSL on a special legacy port".
I'm not sure what the means, in detail, but it worked when changed.
Thanks for everyone's help and for your patience with my ignorance.
I tried those port settings with and without SSL. Same errors. Also posted on emClient support page.
Baffling.
Is there anything else that can be affecting hughesnet server connection? Same email client works for gmail and for another domain (all going through my satellite connection). and I can send/receive hughesnet email from cell phone and webmail.
Definitely email client and hughesnet send only related.
An earlier post you made said: "SMTP is configured for port 587". I believe you have to have SSL on HughesNet as with most email these days.
Also, the port should be 465 for SSL, not 587 as you stated. You may want to double check again. You may want to ensure that authentication is set to use the same the receive setting.
Another thought: You might want to make sure your outgoing certificate settings aren't messed up. First try with no certificate with neither any signing algorythm nor any encryption engaged.
Now set as you state - still not working. Seems like all combinations of ports and SSL enabled/disabled do not send.
What is the proper setting for PORTS and SSL? I operating in POP mode.
This has worked for nearly 20 years and all of a sudden .. boom.
I have changed the ports as indicated and ensure the authentication is correct. and tried all flavors of SSL. None of it works.
Can someone post the "correct" settings (or at least the options) of Ports and SSL on/off for POP mode? I think I have tried every combination.
This has worked for 20 years and then ... boom.I posted the correct settings precisely. I have them set that way in Outlook and it works with no issues. I'm afraid there's something wrong with your client. It's possible it's either not setting the correct port (using the default instead) or some other issue.It was recommended some days ago that you contact your client's developer as a fallback to try to figure out the probkem. If you've not done that, well, there's nothing anyone can do for you other than what's already been done/discussed. Good luck.
Yes, I have done that, as I said I would. And have started working with them.
