Sent a friend that uses outlook.com for her emails a message and got this note back
550 OU-001Mail rejected by Outlook.com for policy reasons. If you are not an email/network admin please contact your Email/Internet Service Provider for help. For more information about this block and to request removal please go to: http://www.spamhaus.org.
What is going on?
550 OU-001Mail rejected by Outlook.com for policy reasons. If you are not an email/network admin please contact your Email/Internet Service Provider for help. For more information about this block and to request removal please go to: http://www.spamhaus.org.
What is going on?
Posted 2 years ago
Bev, Champion
Just had another one this time with this code
If I send to myself I receive it. I sent it to a second address that I have and it came through.
I checked my IP number through http://whatismyipaddress.com/blacklist-check and it has 12 APEWS.org with a red exclamation.
I checked my IP number through http://whatismyipaddress.com/blacklist-check and it has 12 APEWS.org with a red exclamation.
The host at this IP address (69.168.102.197) is emitting spam mails. That's the Zimbra mail server (or Synacor).
See:
https://www.spamhaus.org/sbl/query/SBL357316
And refer it to exedelistens - note their DNS record doesn't look to healthy either (really DirecTV???)
See:
https://www.spamhaus.org/sbl/query/SBL357316
And refer it to exedelistens - note their DNS record doesn't look to healthy either (really DirecTV???)
(Edited)
I am sorry I do not understand the stuff at the link you sent me. Can you give me more info?
In summary, the Zimbra mail server has been blacklisted by the Spamhaus Block List - any mail servers (e.g. Outlook) that utilize Spamhaus block lists will likely not accept any incoming mail from Exede/Wildblue which is hosted on Zimbra's servers. Simply refer it and the link to exedelistens@viasat.com - Zimbra will need to handle it and restore their already weak reputation.
That server is blocked in numerous others also:
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a69.168.102.197&run=toolpage
That's a Zimbra/Synacor IP address not yours - all you can do is hope they correct it. Spamhaus removal instructions for Zimbra/Synacor are at the end of the link:
https://www.spamhaus.org/sbl/query/SBL357316
In addition as noted above the DNS record doesn't match the email addresses from which mail is being sent which can also cause problems with dome spam detectors - a sample of that mismatch is shown in the above link also - mail purporting to be from a DirecTV server but the sender is purported to be a wildblue address.
You're not supposed to understand it, ViaSat and Synacor are supposed to ;)
Edited to provide further detail to ViaSat and Synacor - the bill is in the mail ;)
That server is blocked in numerous others also:
https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a69.168.102.197&run=toolpage
That's a Zimbra/Synacor IP address not yours - all you can do is hope they correct it. Spamhaus removal instructions for Zimbra/Synacor are at the end of the link:
https://www.spamhaus.org/sbl/query/SBL357316
In addition as noted above the DNS record doesn't match the email addresses from which mail is being sent which can also cause problems with dome spam detectors - a sample of that mismatch is shown in the above link also - mail purporting to be from a DirecTV server but the sender is purported to be a wildblue address.
You're not supposed to understand it, ViaSat and Synacor are supposed to ;)
Edited to provide further detail to ViaSat and Synacor - the bill is in the mail ;)
(Edited)
Went through the phone for escalation and Exede says that there is an outage? So now we wait? Does this sound right?
No, that does not compute. An outage has absolutely nothing to do with your issue - unless an outage is affecting escalation.
Hopefully, a moderator will jump in and forward the information to the appropriate parties - everything they need to know is posted above, I can only lead them to water not make them drink.
Hopefully, a moderator will jump in and forward the information to the appropriate parties - everything they need to know is posted above, I can only lead them to water not make them drink.
it did not sound right to me either. This was escalation team via phone call. Hope a moderator will respond here.
Bev, Champion
The easy solution is to get an alternate email account, like gmail.com for use with that recipient. It may be a while before Zimba gets it fixed since DirecTv spam really does go through that server and, lots of people mark those emails as junk or spam, so it keeps getting reported as a spam server.
Bev, thanks, I am trying to keep in touch with them through another email address. We shall see how that goes. I can get email from them. Just can't get my mail through to them.
(Edited)
Bev, Champion
Well, you aren't alone, same issue just bit me too - sending to an outlook address again. LOL
Good luck, appears you'll need to smack someone in the head with a 2 x 4. Then once Synacor does go through the removal process, sit around and wait until the change propagates - this one couldn't be clearer from:
https://www.spamhaus.org/sbl/query/SBL357316
I don't think it's a DirecTV email server (although Synacor does host DirecTV on that same physical server) just a DNS record or alias mismatch on Synacor's end.
FWIW, Exede and Wildblue should be using mail.exede.syn-alias.com and mail.wildblue.syn-alias.com
https://www.spamhaus.org/sbl/query/SBL357316
I don't think it's a DirecTV email server (although Synacor does host DirecTV on that same physical server) just a DNS record or alias mismatch on Synacor's end.
FWIW, Exede and Wildblue should be using mail.exede.syn-alias.com and mail.wildblue.syn-alias.com
(Edited)
Bev, Champion
They will fix it, at least for a while, in a week or two, maybe. Oh well use another email service to email outlook people for now.
Brad, Viasat Employee
We're looking into it. Sorry guys!
Thanks, Brad.
Bev, I think that Old Labs is barking up the right tree. Just nothing that I can do to fix it. Hoping that Exede steps up the game.
Bev, Champion
Thanks Brad, it was a reply to an Outlook.com address that bounced on me so, seems to be mostly Outlook (MSN) having a problem with Zimba.
I had the issue with an outlook.com address but also new.rr.com message that came back included 
Bev, Champion
That is the server, if you follow the link, enter that IP address, then follow the next link given, it explains what happened to blacklist the server IP address.
Exede staff are aware of it, so I'm sure it will be dealt with as quickly as possible. It was fine 2 weeks ago, now bouncing emails to someone I was able to email 2 weeks ago without issue. It will be fixed soon.
Exede staff are aware of it, so I'm sure it will be dealt with as quickly as possible. It was fine 2 weeks ago, now bouncing emails to someone I was able to email 2 weeks ago without issue. It will be fixed soon.
(Edited)
I do not understand what I am suppose to do. This is the note. So is Exede working through this link?
Removal Procedure
Removal Procedure
To have record SBL357316 (69.168.102.197/32) removed from the SBL, the Abuse/Security representative of synacor.com (or the Internet Service Provider responsible for supplying connectivity to 69.168.102.197/32) needs to contact the SBL Team by email (use this link) to explain how the abuse problem has been terminated (we need to know exactly how the issue has been dealt with and that this abuse problem is fully terminated). If the abuse problem that caused this listing has been terminated we will normally remove the listing from the SBL without delay.It is essential that emails to the SBL Team about this SBL listing include this exact ticket information in the email Subject:
so I assume I just have to wait for who knows how long.
Bev, Champion
Pretty much, yes but, that shouldn't take too long. Just need the right people to verify that the problem has been dealt with, that that spam won't be sent again and, time for Spamhuas to get the server off the blacklist. I've seen that happen inside a week, but might be two weeks if it's a bit harder to stop the problem.
Oh by the way, I found a really big and really strong 2x4 and, put it on autosmack - it will get the job done. :)
Oh by the way, I found a really big and really strong 2x4 and, put it on autosmack - it will get the job done. :)
(Edited)
Lord, I hope so. Seems that someone does not have very good security.
Probably why we are getting so much SPAM, this needs Exede's attention now. Not later, or weeks, this is the kind of thing that really is frustrating. To just say "well go get a free temporary email for now" is not a great solution. Emails today are kind of embedded in all we do. Do something right now as a priority. It is enough to deal with all the outages all the time, fix the email issue Exede. If I have to change my email again; which is a task now as much as that email is used for everything from our banking to our college. Embarrassing that I am getting these messages. I do not want to wait weeks.
Arrival-Date: Tue, 25 Jul 2017 08:05:52 -0400
Reporting-MTA: dns; smtp02.viasat.aga.synacor.com
Last-Attempt-Date: Tue, 25 Jul 2017 08:05:52 -0400
Final-Recipient: rfc822; Paula.Barber@esc.edu
Action: failed
Remote-MTA: dns; esc-edu.mail.protection.outlook.com
Diagnostic-Code: smtp; 550 5.7.1 Service unavailable, Client host [69.168.102.197] blocked using Spamhaus. To request removal from this list see http://www.spamhaus.org/lookup.lasso (AS16012611) [BL2FFO11OLC001.protection.gbl]
Status: 5.7.1
Arrival-Date: Tue, 25 Jul 2017 08:05:52 -0400
Reporting-MTA: dns; smtp02.viasat.aga.synacor.com
Last-Attempt-Date: Tue, 25 Jul 2017 08:05:52 -0400
Final-Recipient: rfc822; Paula.Barber@esc.edu
Action: failed
Remote-MTA: dns; esc-edu.mail.protection.outlook.com
Diagnostic-Code: smtp; 550 5.7.1 Service unavailable, Client host [69.168.102.197] blocked using Spamhaus. To request removal from this list see http://www.spamhaus.org/lookup.lasso (AS16012611) [BL2FFO11OLC001.protection.gbl]
Status: 5.7.1
I can receive emails. That has not been affected. I just can't send them without them being blocked and bouncing back.
Bev, Champion
Steve Frederick-VS1/Beam314, Champion
The bigger question for Zimbra/Synacor is why does email sent from an Exede or Wildblue account identify itself as being sent from DirecTV? All email headers shown here and elsewhere (like the other forum) show that to be the case.
In and of itself that's a red flag for spam detection (frequently an indication of email open relay used by SPAMMERS).
Fix that configuration error and you probably fix the problem immediately for Exede/Wildblue users - DirecTV users are on their own.
The IP addresses for mail.exede.net and mail.wildblue.net don't currently show as being on any blacklists - which is where email should be originating for Exede/Wildblue users respectively, not from mail.directv.net.
In and of itself that's a red flag for spam detection (frequently an indication of email open relay used by SPAMMERS).
Fix that configuration error and you probably fix the problem immediately for Exede/Wildblue users - DirecTV users are on their own.
The IP addresses for mail.exede.net and mail.wildblue.net don't currently show as being on any blacklists - which is where email should be originating for Exede/Wildblue users respectively, not from mail.directv.net.
(Edited)
Bev, Champion
Follow the link in the bounce notice, enter the host IP, follow that link; it only identifies it as the same host as DirecTV, in the report is the email address the spam was sent from - it isn't DirecTv.
Exactly! The origin domains are supposed to match!
It doesn't matter that they are on the same physical server (or host as you've put it) - they are different domains (or possibly sub domains which should be isolated).
You should not be able to send email via DirecTV (unless having an actual email account with them) - that's called open relay and is frowned upon by most reputable email systems. It's that type of error that results in a server IP being blacklisted - we're not talking about client IP addresses being blocked here.
This issue only applies to outgoing email not incoming, but maybe Zimbra/Synacor should be using Spamhaus to check for incoming SPAM to address that constant complaint. Seems to be working great for others ;)
It doesn't matter that they are on the same physical server (or host as you've put it) - they are different domains (or possibly sub domains which should be isolated).
You should not be able to send email via DirecTV (unless having an actual email account with them) - that's called open relay and is frowned upon by most reputable email systems. It's that type of error that results in a server IP being blacklisted - we're not talking about client IP addresses being blocked here.
This issue only applies to outgoing email not incoming, but maybe Zimbra/Synacor should be using Spamhaus to check for incoming SPAM to address that constant complaint. Seems to be working great for others ;)
(Edited)
Bev, Champion
Actually, glad it wasn't the email domain of the sender of the spam that was blocked specifically. Had that happened, we might not be able to send email to ANYONE until it is fixed. Seems mostly MSN hosted email addresses are bouncing us right now, that beats everyone.
Brad, Viasat Employee
Brad, Viasat Employee
Just got word that my emails to outlook are not being delivered again. None are coming back though.
Bev, Champion
Just sent one to an address that bounced for me, asking her to confirm receipt. She got my email straight away. I don't think it's a Viasat problem anymore. Mail to MSN powered addresses seems fine now.
If you have a second wildblue/exed.net address try sending form that one and see if it's just one address it isn't getting through from. May be something going on with that one address and outlook.
If you have a second wildblue/exed.net address try sending form that one and see if it's just one address it isn't getting through from. May be something going on with that one address and outlook.
So far it is only one address that I know about and it is to Outlook.com. I have always been able to get my exede.net mail to and from so that has not been an issue.
I am thinking since I am not getting the mail to outlook.com notice bounced back may be something else?
I am thinking since I am not getting the mail to outlook.com notice bounced back may be something else?
The email could have been temporarily un-deliverable and would go into a hold queue for retrying at a later time. In that case you don't receive a non-delivery notice until all retries have been exhausted - time between retires (and number of retires) is largely dependent on how the outgoing server is configured.
A co-worker of mine in the office next to mine used to have this problem, he'd send email to me and never get a response from me - of course I was just trying to make him get up off his butt and step next door to ask if I got his email ;)
A co-worker of mine in the office next to mine used to have this problem, he'd send email to me and never get a response from me - of course I was just trying to make him get up off his butt and step next door to ask if I got his email ;)
Thanks, seems to be delivering again so that may be exactly what happened. Thanks Bev and Old Labs.