Now 2 Weeks 4 Days - emails won't send

[Scooter]

Have you tried 

Clearing history, cache, cookies on your browser?

Changing the settings as per this post?

Yes, I've cleared all cookies cache etc. on two different computers. Pffft

The difference between port 25 and port 110 VS 465 (with SSL) and 995 (with SSL), is the finer points of the error message:

WITH 465 & 995 with SSL the error messages are:

Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'mail.hughes.net', Server: 'smtp.hughes.net', Protocol: SMTP, Port: 465, Secure(SSL): Yes, Error Number: 0x800CCC0F

Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'mail.hughes.net', Server: 'mail.hughes.net', Protocol: POP3, Port: 995, Secure(SSL): Yes, Error Number: 0x800CCC0F

Thus with these settings I can neither send nor receive.

However, if I revert to 25 &110 (with NO SSL) I can at least receive and I get only one (not two), but similar error messsage:

Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'mail.hughes.net', Server: 'smtp.hughes.net', Protocol: SMTP, Port: 25, Secure(SSL): No, Socket Error: 10053, Error Number: 0x800CCC0F

To be clear, on two different computers, with port 25 and port 110, no SSL I can receive but not send.

With ports changed to 465 & 995, with SSL I can neither send nor receive and simply get an extra bonus error message.

I'm surfing the web just fine and everything else is working just dandy, so it ain't on my end people, stop making excuses and get it fixed. Pitiful

What's next? Have you cleaned the bird poop off your dish, are the saucer people in the way?  Flux capacitor?

[maratsade]

"What's next? Have you cleaned the bird poop off your dish, are the saucer people in the way?  Flux capacitor?"

No, next you have to flush the Bussard collectors and then re-initialise the main holomatrix. 

The techs are aware of the issue and are working on it -- but it may take time, as the company doesn't seem to have any Hogwarts graduates on the payroll and must resort to engineers. 

The reason I asked if you (edit: or whoever it was) had done those other things is because they have worked for some people. 

[MarkJFine]

Didn't say if you rebooted the modem or not, which would clear the DNS cache.

SSL won't work at all if the DNS is corrupted.

[Scooter]

Representives of HughesNet informed me that they did it remotely, twice.

However, an internet service provider that can't support email is akin to a beer company not being able to fill and cap a bottle.

So you tell me, did they? How can I tell?

It's been working just fine on port 25 and 110 with no SSL for about 13 years, until about November 4th.

I din't do nuffin.

I guess we're waiting on Space X to get there with a big hammer and get after it.

[maratsade]

"However, an internet service provider that can't support email is akin to a beer company not being able to fill and cap a bottle."

They are supporting email -- they are working on the issue. 

[Scooter]

If I told "Vinnie the finger" or Fat Pauly that I still don't have the money 12 days later, but I was "working on the issue" they may find that slightly unacceptable.

12 days? Really? When do we start measuring this fiasco in weeks?

[maratsade]

Unfortunately, it takes as long as it takes. Maybe they'll have an update for you tomorrow, maybe not.  Stay away from Vinnie the Finger -- you don't know where the finger has been. 

[Scooter]

[Scooter]

14 Days Now - Bueller? Bueller?

[AndyB]

Email has been working fine for past 8 months, however since last week I cannot send emails, I can only receive emails.

macOS - Mail application

Outgoing SMTP settings:

User Name: accountname@hughes.net

Host Name: smtp.hughes.net

Port: 587

TLS/SSL: checked

Authentication: Password