"Problem is Hughes is timing out every single time. "
Hughes has a router problem in Idaho: one of their telcom servers is down. If you go to a command line prompt and type in TRACERT SMTP.HUGHES.NET you might be able to see where your packets die.
By the way, Hughes custom er service / support has no idea they have this problem, and telling them about the problem is non-productive. Asking them to change their router tables to route around the dead server will be met with incomprehension: they have no idea how their routing works.
"It's been 110/25 for years and just quit 7 days ago."
Yes: it is not a socket number / port number issue: it is a spam throttle issue at Hughes. Sadly, they have no idea how to reset the flag. They also have no idea the spam throttle exists, which suggests they are using a third-party anti-spam service provider.
I am having the same [F 11] problem with my Apple mail. I have been sent up and down the chain of "technical support" and at my wits end. I've posted another thread on this a week ago with my SMTP logs in it which are "being reviewed." We'll see if they figure it out. I've done every suggestion in both the Apple and Hughesnet knowledge base from 2 years ago to now. Nothing has worked. I refuse to pay $69 for Home Tech Support when I know it is on their end. Maybe if enough of us give them the solution they can figure it out. UGH.
Liz, IT has ALWAYS been set at port 25, works to forward mail from hughes to Gmail but does not send from hughes using Outlook.
I changed nothing, I did nothing and then last night...I added another email to the growing list that failed to send and tried to send them........and they were sent. So yes....this is/was a hughes issue. Desertphile is right. It has happened before but usually worked a few minutes later....this time took 10-12 days before it finally sent them.
I'm so sorry, I had port 25 stuck in my head when I replied to you. I meant for you to try switching to port 587, as instructed in the link I sent you. Please let me know if you're able to send e-mails after switching to port 587.
Again, I'm sorry for causing confusion, I edited my original reply so that others aren't confused, too.
Did my post answer your question? Accept as Solution to help others find it faster.--------------------------------->
". I have been sent up and down the chain of "technical support" and at my wits end."
Hughes customer support only follow scripts; they are ignorant about how the email servers work. The problem is that your email address has been put on a temporary anti-spammer list; Hughes customer support will tell you that your email address "is in good standing" but it is not: customer support is wrong. Everyone at Hughes customer support will insist it is your problem and not theirs. The problem appears to reside on a third-party anti-spammer service that Hughes uses--- and no one at customer support even knows there is that service in place.
Customer support assumes we are all morons who just woke up one morning and changed the email client settings on all of our computers for no reason, and without knowing we were doing it while we did it.
"I changed nothing, I did nothing and than last night...I added another email to the growing list that failed to send and tried to send them........and they were sent."
Yes; if you change the email address, and nothing else, in your email client then your emails will be sent; if you change the email address back to the blocked on, emails will not send.
As noted, someone fraudulently used your email address to send spam with; that address was then blocked at Hughes' end. Customer Support has no idea this is the problem, but it is. I have spend many days on the telephone discussing the problem with Hughes but, frankly, 90% of staff there have very little knowledge about how their systems and servers work.
It's a spam block. Good luck getting Hughes to acknowledge this fact.
On the plus side, the spam block gets removed eventually after about 31 days.
Replies can be removed by community moderators if they contain inappropriate content or private information. Amanda, a moderator for HughesNet, gave this reason for the change: spam So, when I pointed out that the problem is the spam blocker Hughes uses, that's spam? Really? Good gods that's hilarious! My complaining about spam is spam..... LOL!
"I'm so sorry, I had port 25 stuck in my head when I replied to you. I meant for you to try switching to port 587, as instructed in the link I sent you. Please let me know if you're able to send e-mails after switching to port 587."
I suspect you might be learning impaired. The problem is *NOT* the socket / port number: the problem is the spam blocker Hughes is using.
I really hate being forced to diagnose HughesNet's tech problems, since *THEY* are being paid to solve them and not me. The problem is at the anti-spam supplier "Fortinet" which is using a "FortiMail" email gateway to handle HughesNet email. The spam lock is on that gateway: something Hughes customer support knows nothing about and can do nothing to solve the problem.