On 3/8/19 3:01 PM, Scott Mutter wrote:
So I'm back, because I'm getting absolutely no where with Outlook Support.
Here is a log of the SMTP transaction:
--SNIP--
# telnet hotmail-com.olc.protection.outlook.com 25
550 5.7.1 Unfortunately, messages from [67.222.128.248] 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.
[SN1NAM02FT029.eop-nam02.prod.protection.outlook.com]
The error message does say to "contact your ISP since part of their
network is on our block list" and it didn't say your IP address is on
their block list.
As mentioned in our previous response, we do not see anything offhand with the
IP (67.222.128.248) that would be preventing your mail from reaching our
customers.
Ok yes, being inordinately nitpicky, but if you take the MS responses
verbatim, they also said they don't see any problem with your specific
IP address which could still be true if the problem is with your upstream.
In fact, if I look up a Sender Score for this IP I get:
Insufficient Email Seen
I just don't see anything that points to any reason why this IP would be
blacklisted. My guess would be that it's a relatively new IP address that
Microsoft is seeing as sending messages, and thus it's being punished for
having no reputation.
The MS error is clear in what is saying. As many as the MS errors are,
I would expect a different error for insufficient reputation.
But that's just a guess on my part because Microsoft seems unwilling to explain
in adequate terms - instead just giving a broad response.
I have some deadwood entries in a block list here dating back to 2010
(yes they need to be pruned out) for IP ranges that used to be listed as
being under Tailor Made Servers, now listed as DFW Datacenter. I'm not
currently experiencing problems from those ranges but Talos / Senderbase
currently shows some trouble in DFW's 209.236.112.0/20. Maybe MS has
some correspondingly old entries that are giving you trouble with your
address in 67.222.128.0/19 because of the DFW association.
If you're getting connectivity through DFW and you're having trouble
it's possible that others are having trouble through them also. Would
seem like a good idea to escalate through them as well.
-
John J.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
