Hughesnet Rejected by Outlook, now what?

[Scooter]

Well who wants to make excuses for this one, anybody?

nameomitted@outlook.com (after MAIL FROM): 550 5.7.1 Unfortunately, messages from [150.136.130.109] 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. [BN7NAM10FT060.eop-nam10.prod.protection.outlook.com]

And heres' the long version:

Arrival-Date: Sat, 28 Nov 2020 21:28:56 +0000
Reporting-MTA: dns; hughes.net

Remote-MTA: dns; outlook-com.olc.protection.outlook.com
Diagnostic-Code: smtp; 550 5.7.1 Unfortunately, messages from [150.136.130.109] 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. [BN7NAM10FT060.eop-nam10.prod.protection.outlook.com]
Action: failed
Status: 5.7.1
Final-Recipient: rfc822; nameomitted@outlook.com
Last-Attempt-Date: Sat, 28 Nov 2020 21:28:56 +0000

How long will it take for this to be blamed on my end?

[GabeU]

@Scooter 

Why would anyone blame it on your end?  The problem is stated in the message.    

Edit:  I just tried sending an email from my hughes.net account to my MSN account and received the same type of failure notification due to MSN's blocking of hughes.net, so you're not alone.

[Scooter]

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?

[kitnbob]

@Scooter 

I sent an email to my MSN box  from HughesNet and nuttin happened.

After I changed the SMTP ports and the SSL check box.

 it  bounced 12/1/2020

I'm convinced that MSN don't like Hughes.

Similarly, Earlier in the Year after Hughes was adjusting their bandwidths  for the "working at home' and "schooling"  users streaming all the bandwidth,  I would try to log on to my AOL email, (I'll Bet they werent doing schoolwork)

and the thingamajig would spin ALL day, eventually at precisely 5:00 PM (like a switch) I could retrieve mail from the IMAP mail server at AOL.com. dont have POP

I was convinced that Hughes don't like AOL

I realized there was nothing I could do about it, and told everybody to use mail@gmail,com

Your observations alerted me to the Outlook, MSN, Hotmail problem.

[Scooter]

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

[kitnbob]

Looks like this last error message was generated today.

Delete ALL of those problem messages OR (move them )  out of your OUT box.

I think the error messages will stop today.

Mine stopped when Windows Live quit trying to send mail to MSN.com

[kitnbob]

I have been testing the Windows Live and the Zimbra clients this morning.

I was testing two hughes addresses and successly mailing an account at MSN.com. and replying with outlook.live.com

1 hughes address was sending at port 465

2 hughes address was sending at port 587

I had No bounces

I had No server errors

I have nothing remaining in my Outbox  and no lost messages.

How did you do?  @Scooter 

I'm not using any bulk mailers

or using a spoofed email address 

are you?

[MarkJFine]

465 is the standard port for outbound email using SSL. It's what most clients set if you check the "Use SSL" box.
I'm guessing HughesNet also has 587 open as well. As long as either works, it's all good.

[kitnbob]

@MarkJFine 

I changed to those ports /SSL  this weekend I had heard they both work..  and they do..

The issue was that MSN was bouncing spam from hughes servers.

@GabeU  and myself both have MSN accounts

and both of us generated similar bounce messages on Fri or Sat

[MarkJFine]

Yeah, so I just figured out that the email system is now on Oracle Cloud. I'm guessing the extrication from Senacor didn't go smoothly. Judging from the old security problems with Senacor, I'm not surprised at all.

In the long run, the move to Oracle should be beneficial, but it's going to take time for it to bed in with the webmail application, external clients, and especially with a new spam detection system. Anything that used to work with the old Senacor server likely has to be completely redone - not a task for the meek.

[kitnbob]

@MarkJFine    and you are referring to the MSN mail system?

[MarkJFine]

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.

[Scooter]

---

@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?

---

---

---

[Scooter]

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.

[kitnbob]

I saved one from Tues Dec 1 but No errors today. Thursday

(after MAIL FROM): 550 5.7.1 Unfortunately, messages from [129.213.209.193] 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. [VI1EUR04FT047.eop-eur04.prod.protection.outlook.com]

---

------ This is a copy of the headers of the original message. ------

SMX-Results: classifications=clean
Received: from zmc-mailbox ([10.219.128.78]) by shared.hu1.smxemail.com
with ESMTP id 5FC68B4C-709C0273@mta4101.omr;
Tue, 01 Dec 2020 18:28:28 +0000
Date: Tue, 1 Dec 2020 18:28:26 +0000 (GMT)
From: kitnbob <kitnbob@hughes.net>
To: kitnbob <kitnbob@msn.com>
Message-ID: <1014964364.1044005.1606847306356.JavaMail.zimbra@hughes.net>
Subject: Testing servers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [97.73.80.50, 10.244.4.45]
X-Mailer: Zimbra 8.9.0_GA_1011 (ZimbraXWebClient - FF83 (Windows)/8.9.0_GA_1011)
Thread-Index: zM8iqjuOMVszmFRkqn6Y/aWXTwTe2g==
Thread-Topic: Testing servers

This came back to the webmail client  Zimbra because I hadnt changed my ports yet. on Windows Live  client

Isnt it saying that MSN is blocking Hughes?

[Scooter]

Yes

[kitnbob]

I did read explanations of errors that  was in the bounce message....    kinda interesting

---

@Scooter wrote:

Yes

---

http://mail.live.com/mail/troubleshooting.aspx#errors

[GabeU]

---

@kitnbob wrote:

No errors today. 

---

Same here.  Emails from hughes.net to my MSN address were being blocked the other day, but today they are going through.  That's progress on that part.  🙂

[MarkJFine]

When I said it was transitory, I meant that MSN could have been blocking HN since before the servers switched. If they keyed on the @Hughes.net domain it wouldn't care which IP it was coming from, and therefore wouldn't know that the servers changed.

However, since the new server is more secure, chances of it being a source of spam from users' malware or embedded spambots would be a lot lower. Therefore, in theory, there would be less chance of it being blocked on the receiving side, which was a horrendous problem - not just with MSN, either.

[kitnbob]

---

@Scooter wrote:

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). 

Cool  So ...   none of your messages were blocked today either

[Scooter]

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?