The block does look pretty bleak...

        http://www.senderbase.org/lookup/?search_string=109.228.14.0/24

Also, you should generally consider that any mitigation Hotmail applies comes 
with an implied, "Please allow 24 - 48 hours ..."
Because, unfortunately, it does.

Aloha,
Michael.
-- 
Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been 
Processed." | Got the Junk Mail Reporting Tool ?

-----Original Message-----
From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Richard Doyle
Sent: Thursday, September 22, 2016 9:24 AM
To: mailop@mailop.org
Subject: Re: [mailop] Problems sending to Hotmail.com etc

Another host (109.228.14.111) in your /24 is on the CBL. Perhaps you are being 
punished for the sins of your neighbors.


On 09/22/2016 01:24 AM, Paul Smith wrote:
> One of our clients is having trouble sending to Hotmail.com (and 
> possibly Outlook.com etc as well). I'm confident they aren't sending 
> spam and they don't run mailing lists etc.
> 
> This is a typical SMTP session transcript
> 
> 21/9/2016 14:56:16.553 - M000000a3<220 SMTP server ready
> 21/9/2016 14:56:17.069 - M000000a3>EHLO mail.partingtons.com
> 21/9/2016 14:56:17.756 - M000000a3<250-BAY004-MC3F56.hotmail.com
> (3.22.0.10) Hello [109.228.14.209]
> 21/9/2016 14:56:17.756 - M000000a3<250-SIZE 36909875
> 21/9/2016 14:56:17.756 - M000000a3<250-PIPELINING
> 21/9/2016 14:56:17.756 - M000000a3<250-8bitmime
> 21/9/2016 14:56:17.756 - M000000a3<250-BINARYMIME
> 21/9/2016 14:56:17.756 - M000000a3<250-CHUNKING
> 21/9/2016 14:56:17.756 - M000000a3<250-STARTTLS
> 21/9/2016 14:56:17.756 - M000000a3<250-AUTH LOGIN
> 21/9/2016 14:56:17.756 - M000000a3<250-AUTH=LOGIN
> 21/9/2016 14:56:17.756 - M000000a3<250 OK
> 21/9/2016 14:56:17.756 - M000000a3>STARTTLS
> 21/9/2016 14:56:17.897 - M000000a3<220 SMTP server ready
> 21/9/2016 14:56:18.381 - M000000a3>EHLO mail.partingtons.com
> 21/9/2016 14:56:18.522 - M000000a3<250-BAY004-MC3F56.hotmail.com
> (3.22.0.10) Hello [109.228.14.209]
> 21/9/2016 14:56:18.522 - M000000a3<250-SIZE 36909875
> 21/9/2016 14:56:18.522 - M000000a3<250-PIPELINING
> 21/9/2016 14:56:18.522 - M000000a3<250-8bitmime
> 21/9/2016 14:56:18.522 - M000000a3<250-BINARYMIME
> 21/9/2016 14:56:18.522 - M000000a3<250-CHUNKING
> 21/9/2016 14:56:18.522 - M000000a3<250-AUTH LOGIN
> 21/9/2016 14:56:18.522 - M000000a3<250-AUTH=LOGIN
> 21/9/2016 14:56:18.522 - M000000a3<250 OK
> 21/9/2016 14:56:18.522 - M000000a3>MAIL FROM:<u...@partingtons.com>
> 21/9/2016 14:56:18.663 - M000000a3<550 SC-001 (BAY004-MC3F56) 
> Unfortunately, messages from 109.228.14.209 weren't sent. Please 
> contact your Internet service provider since part of their network is 
> on our block list. You can also refer your provider to 
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.live.com%2Fmail%2Ftroubleshooting.aspx%23errors&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5041f01df00b4419e21d08d3e306aa61%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636101590179134080&sdata=tNwUBW0xoPkGKNhtMLrpYu99Cdcgr5X46HTF%2BSjzfoE%3D&reserved=0.
> 
> We contacted Microsoft using the online form, and the response we got 
> wasn't very helpful...
> ---------------
> As previously stated, your IP(s) (109.228.14.209)  has been already 
> mitigated.  I do apologize, but I am unable to provide any details 
> about this situation since we do not have the liberty to discuss the 
> nature of the block.
> At this point, I would suggest that you review and comply with 
> Outlook.com's technical standards. This information can be found at
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fpostma
> ster.live.com%2FGuidelines.aspx&data=02%7C01%7Cmichael.wise%40microsof
> t.com%7C5041f01df00b4419e21d08d3e306aa61%7C72f988bf86f141af91ab2d7cd01
> 1db47%7C1%7C0%7C636101590179134080&sdata=unguLOIOYYTOd%2BKBu3Ge5AobuD2
> 2ZOTu9JNCNZvNqh4%3D&reserved=0 We regret that we are unable to provide 
> any additional information or assistance at this time.
> 
> Best regards,
> Jeeva
> Outlook.com Deliverability Support
> ----------------
> 
> As far as we can tell, the server does comply with Outlook.com's 
> technical standards according to that document apart from Sender-ID 
> (does anyone apart from MS use that?) and SPF. We're setting up SPF 
> for them now, but that shouldn't be mandatory. The server is a 
> dedicated server hosted with Fasthosts so shouldn't be on a dynamic IP 
> address range.
> 
> Any ideas of other things to try?
> 
> 
> 
> 
> _______________________________________________
> mailop mailing list
> mailop@mailop.org
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchill
> i.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailop&data=02%7C01%7C
> michael.wise%40microsoft.com%7C5041f01df00b4419e21d08d3e306aa61%7C72f9
> 88bf86f141af91ab2d7cd011db47%7C1%7C0%7C636101590179134080&sdata=cy27mn
> qVXHsqrhjRA6CUuMMO0Nt%2FajkeJ%2FXrWlw6KPI%3D&reserved=0


_______________________________________________
mailop mailing list
mailop@mailop.org
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchilli.nosignal.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fmailop&data=02%7C01%7Cmichael.wise%40microsoft.com%7C5041f01df00b4419e21d08d3e306aa61%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636101590179144082&sdata=9WEd0qVvgaIp3dKRJCeLc49nIAANWfxNdjqEluw%2Fmqw%3D&reserved=0
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Reply via email to