Forum Discussion
EMAIL not going out from emClient
In recent days or a week or so my email is not going out from using the emclient email client. I am able to receive email. It fails for 2 different accounts but worked recently and I have made no changes.
I can send hughesnet email from webmail and from my cell phone.
I can send gmail, and other mail, from emclient. Just not hughesnet email.
SMTP is configured for port 587
Please help.
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.
You may also want to ask here: https://www.emclient.com/support
I will do that. Although emClient works fine for other non-hughesnet accounts, which seems to eliminate emClient as the culprit. I will, however, include it there.
Yes, you may be right and it may be the HN connection, but I imagine other people on that site may be on satellite and may be able to help. I hope others here on this site will chime in; they may know much more than I do, so keep checking!
these error messages:
both with and without SSL security enabled
8:13:31 AM "Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."
8:13:31 AM at MailClient.Protocols.Smtp.SmtpSendCommand.Connect(WorkerStatus status)
8:13:31 AM at MailClient.Protocols.Smtp.SmtpSendCommand.Execute(WorkerStatus status)
8:13:31 AM at MailClient.Commands.Command.Process(WorkerStatus status)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, 995POP 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.
