About Scooter

This email would continue to get rejected, with various error messages but finally went through later this week.   I hard headedly stuck with port 465, overall, I've had better luck with that, for what it's worth.   and it's continued to behave since, Wed or Thurs?     ... View more

kit, you seem like good people and your kind words are welcome, if that thing with bob doesn't work out, holla.   But the way it works (or doesn't) is it leaves the outbox, get's rejected by Outlook and slings back like a boomerang. Thus while it did exit the box, it then went into the ditch.   Thanks Hughes.   The excuse today could be sunspots, earths wobble, monkeys in the trees? ... View more

Yes ... View more

@MarkJFine wrote: Referring to all the problems in general. Not sure if the MSN problem is a transitory one (holdover from Senacor) or a new one. What I do know is that the new one clearly doesn’t like non-SSL posting of email, which has been an industry standard for a number of years. That has created a lot of security problems, and likely led to being blocked all over the internet. Changing that may have caused some initial confusion, but it will be better in the long run. Better in the long run? Better for who? Can you describe this Utopia of that which you speak?   ... View more

kitnbob - nothing is in my outbox.   Most of the time I'm responding to emails sent to me, or occasionally generating a new one. (Clearly from relatives, buyers, sellers, clients, jokers and tokers that use outlook.com). I try again every couple of days and post the results. We want fresh results here, lest someone inform me that it was too many days ago to investigate. Try again.   ... View more

@MarkJFine wrote: Referring to all the problems in general. Not sure if the MSN problem is a transitory one (holdover from Senacor) or a new one. What I do know is that the new one clearly doesn’t like non-SSL posting of email. Well Mark, what's the excuse for not posting SSL email?   ... View more

Coca-Cola finally realized that new Coke sucked and would bankrupt the company, so they brought back the original. Common sense is a super power now. We are screwed, this upgrade is killing me. What excuse you got for me today?   Tell me that Elon is gonna light the fuse on a new satellite for you that'll actually send email.   If you call the help line, they're all busy looking for the cobra that got out of the basket.   Arrival-Date: Thu, 03 Dec 2020 00:01:30 +0000 Reporting-MTA: dns; hughes.net Action: failed Final-Recipient: rfc822; nameomitted@outlook. Remote-MTA: dns; outlook-com.olc.protection.outlook.com Diagnostic-Code: smtp; 550 5.7.1 Unfortunately, messages from [150.136.206.90] weren't sent. Please contact your Internet service provider since part of their network is on our block list (S3150). You can also refer your provider to http://mail.live.com/mail/troubleshooting.aspx#errors. [DM6NAM11FT026.eop-nam11.prod.protection.outlook.com] Status: 5.7.1 Last-Attempt-Date: Thu, 03 Dec 2020 00:01:30 +0000   ------ This is a copy of the headers of the original message. ------ SMX-Results: classifications=clean Received: from YOUR-2CA16646B7 ([72.168.176.118]) by smtp.hughes.net with ESMTP (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) id 5FC82AD5-E4051015@mta4104.omr; Thu, 03 Dec 2020 00:01:30 +0000 Content-Type: multipart/alternative; boundary="McgpRPqh7I=_tkoauoEBIF0q1kdZQCWtSx" MIME-Version: 1.0 References: <BN3PR05MB26427C61D52271FCFF447939A1F30@BN3PR05MB2642.namprd05.prod.outlook.com> <3DD9259D-1EE4-40DB-A92B-06A2B86F9F90@beckykantz.com> <DM5PR0601MB3783A73DD5E79575E28B8720C0F30@DM5PR0601MB3783.namprd06.prod.outlook.com> Date: Wed, 2 Dec 2020 18:01:21 -0600 Message-ID: <1UWLUYVp8U.1J5vpjfKRkx@your-2ca16646b7> In-Reply-To: <DM5PR0601MB3783A73DD5E79575E28B8720C0F30@DM5PR0601MB3783.namprd06.prod.outlook.com> From:<nameomitted@hughes.net> To: "<nameomitted@outlook.com> Subject: Re: COVID-19 update 12.1.20 ... View more

Brother Gabe, most folks show up here after an excruciating, absurd waste of time on phone support, where no one seems to comprehend what the problem is. After suffering through all of that, again it's "Have you cleared cookies, cache?" "Have you power cycled the modem? "When was the last time you changed the oil?" "What about the thermostat?"   None of which addresses the problem. Like the overnight tsunami of spam email that has recently begun.   Hughes refuses to acknowledge nor accept any responsibility. It's the customers fault, tree is blocking it, the customer let their email get "out there", you must update the browser, now you have the "wrong" port, etc. etc.   No one is going to step up and admit the changes made November 3rd are garbage.   Let's just see if this gets fixed, shall we? ... View more

Outlook may not be for everybody but this was my work around:    https://community.hughesnet.com/t5/Tech-Support/Now-2-Weeks-4-Days-emails-won-t-send/td-p/129346/page/3 ... View more

@GabeU wrote:       Many ISPs have done the same due to lack of usage.   Name as many as you can.       ... View more

I've spent most of today trying to get an answer, some have said they were going to call back, some have said contact Microsoft and connnected me to them, no one knew what "smtp.hughes.net" or what port should be anything. Just got off the phone and new response is working on it try back in an hour. HAHAHA   I haven't been able to send since November 3rd. Stopped receiving this afternoon.  Hmph.   C'mon people.  P.S. I was previously told port 25 and port 110 with no SSL, did that change?   ... View more