Forum Discussion
EMAIL not going out from emClient
- 5 years ago
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.
This is beyond my knowledge of this stuff. I wonder if MarkJFine could translate what this all means. EDIT: Again, you may want to post these errors on the product's website.
Honestly, I don't understand the problem if the SSL port being used is the one specified. I have no issues using any of the standard clients here.
For HughesNet POP (I don't recommend using IMAP):
POP incoming: mail.hughes.net, 995
POP outgoing: smtp.hughes.net, 465
For anyone else, you'd have to consult their instructions.
Other than that, the developer of the client may not have allowed for enough of a timeout window. That sometimes happens as well and might not account for latency on satellite.
- CNS5 years agoSophomore
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.- CNS5 years agoSophomore
UPDATE
Bypassed my satellite connection and sent using emClient via a smartphone hot spot - and, voila, it worked fine.
So it is either being blocked going out by my HughesNet satellite modem, or something with the satellite delay is affecting it. Doubtful it is the delay as other email accounts/servers work fine through the same modem.
Thoughts?
- MarkJFine5 years agoProfessor
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.
- CNS5 years agoSophomore
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.
Related Content
- 3 months ago
- 5 years ago
- 2 years ago