Understandable. We wouldn't be asking for some other avenue here if we didn't fully beleive in there being something funky going on here. If you'd like feel free to message me privately. The ticket number is SRX1342320250ID. Thanks for reaching out, we appreciate it.
Thanks, Dickie LaFlamme On Tue, Jun 7, 2016 at 2:27 PM, Michael Wise <michael.w...@microsoft.com> wrote: > > > Sorry, I’m missing the SRX…ID ticket number so I can figure out the most > recent issues here. > > We have a solid rule not to discuss the reasons for blocking, as we’re > forbidden to do, “Troubleshooting” for senders. > > I am interested in finding out what the refusal code was and getting that > documented, and also seeing if there are issues on OUR side. > > > > But in order to see that, I am going to need to know the ticket number. L > > > > Aloha, > > Michael. > > -- > > *Michael J Wise* | Microsoft | Spam Analysis | "Your Spam Specimen Has > Been Processed." | Got the Junk Mail Reporting Tool > <http://www.microsoft.com/en-us/download/details.aspx?id=18275> ? > > > > *From:* Dickie LaFlamme [mailto:rlafla...@dyn.com] > *Sent:* Tuesday, June 7, 2016 11:21 AM > *To:* Michael Wise <michael.w...@microsoft.com>; mailop@mailop.org > *Subject:* Re: [mailop] Microsoft holding IPs hostage? > > > > Michael, > > > > Per my message I posted: > > > > "We asked for a reasoning why, and after some stock responses, we > received a note back that they could not discuss the matter of the block." > > > > Maybe I was unclear. This was the ticket you're mentioning. I have an > email chain with your support that's pretty lengthy that ended with them > stating they would not discuss the matter of the block. I'm not sure what > more of a ticket I could open. > > > Thanks, > > Dickie LaFlamme > > _____________ > > For such matters, step #0 is to … Open A Ticket. > > You can speculate all you want, but nothing will move the issue to resolution > without first doing that. > > > > Nothing. > > > > Aloha, > > Michael. > > -- > > Michael J Wise | Microsoft | Spam Analysis | "Your Spam Specimen Has Been > Processed." | Open a HotMail > Ticket<http://go.microsoft.com/fwlink/?LinkID=614866&clcid > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fgo.microsoft.com%2ffwlink%2f%3fLinkID%3d614866%26clcid&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=hxlAXsJifwE0k7sXXdGCz8ePQOXJfrKdf4Tr%2bir5j4E%3d>>? > > > > From: mailop [mailto:mailop-bounces at mailop.org > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fchilli.nosignal.org%2fcgi-bin%2fmailman%2flistinfo%2fmailop&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZWtHg%2fJGeN%2bjEuJ1SLHsvx%2fDQBWDLdQ5q%2b3ny5RdAKg%3d>] > On Behalf Of Apsis Deliverability Team > > Sent: Tuesday, June 7, 2016 10:50 AM > > To: achiulli at salesforce.com > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fchilli.nosignal.org%2fcgi-bin%2fmailman%2flistinfo%2fmailop&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZWtHg%2fJGeN%2bjEuJ1SLHsvx%2fDQBWDLdQ5q%2b3ny5RdAKg%3d>; > mailop at mailop.org > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fchilli.nosignal.org%2fcgi-bin%2fmailman%2flistinfo%2fmailop&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZWtHg%2fJGeN%2bjEuJ1SLHsvx%2fDQBWDLdQ5q%2b3ny5RdAKg%3d> > > Subject: [mailop] New comment - [#503261] Re: Microsoft holding IPs > hostage? > > > > > > > > > > On Tue, Jun 7, 2016 at 1:47 PM, Dickie LaFlamme <rlafla...@dyn.com> wrote: > > Well we first saw the blockage via SNDS's "IP status page" - Blocked due > to user complaints or other evidence of spamming. > > > > Here's one of many diagnostic code we received > > > > Action: failed > > Status: 5.0.0 (undefined status) > > Remote-MTA: dns;mx3.hotmail.com > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fmx3.hotmail.com&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=K0yaFKCJB9kdvhH0hWC0QAURWA5vOB87%2fK5hs5S9AqI%3d> > (65.55.92.168) > > Diagnostic-Code: smtp;550 SC-001 (SNT004-MC3F40) Unfortunately, messages > from 208.76.62.88 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 > http://mail.live.com/mail/troubleshooting.aspx#errors > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fmail.live.com%2fmail%2ftroubleshooting.aspx%23errors&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=78jXRqFWDgyX8pLcJelQAXn1U8W6y7BqxK1jUJt3nKU%3d> > . > > X-PowerMTA-BounceCategory: other > > > Thanks, > > [image: Image removed by sender. Dyn logo, Dyn.com] > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fdyn.com%2f&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=5GI2EmN6zRmpADjOELq7MXp0HVrBpyYsrFmRHX9KEFE%3d> > [image: Image removed by sender.] > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ftwitter.com%2fdyn&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=jl9jRWyht9KwjV7bgaKbJosLakJ1BBZj2BkyqGUyEPY%3d> > > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ftwitter.com%2fdyninc&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=bTRqZN0mWfXobyQglUIX%2b8rhmtKHrDqfEIySpVA2G2A%3d>[image: > Image removed by sender. Dyn facebook account] > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ffacebook.com%2fdyn&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=Sv41npVOdyYLkcRLfsNRQW3zJfVgDkwrLX1W2E31NEk%3d> > > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ftwitter.com%2fdyninc&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=bTRqZN0mWfXobyQglUIX%2b8rhmtKHrDqfEIySpVA2G2A%3d>[image: > Image removed by sender. Dyn LinkedIn account] > <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flinkedin.com%2fcompany%2fdyn&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=%2b%2bZeIoC6%2fcLwOx9cL%2f3T%2fjg66rZRHmnkPBSJUrjC85g%3d> > > Dickie LaFlamme / Deliverability Specialist > [image: Image removed by sender.] +1 603-296-1952 <%2B1%20603-296-1952> > > > > On Tue, Jun 7, 2016 at 1:36 PM, Anthony Chiulli <achiu...@salesforce.com> > wrote: > > What error code are you receiving back from blocked mail? > > > *ANTHONY CHIULLI* > > Senior Consultant, Deliverability Services > > Salesforce > > Mobile: 303.817.6506 > > > > On Tue, Jun 7, 2016 at 11:26 AM, Dickie LaFlamme <rlafla...@dyn.com> > wrote: > > We recently experienced a customer ranges of IPs being blocked at > Microsoft, and haven't a clue as to why. > > Details are below, but I'm wondering if others are running into the same > issue: > > - Customers IPs are 208.76.62.[83-88]. Understandably, SenderScore isn't > the end all be all, but all scores are 97 with the only outlier being 94. > Our Google Postmaster tool has reported Green/Yellow for over 120 days. > > - This customer is a high quality sender who has been making strides > toward becoming even that much better by focusing on > key deliverability metrics. > > - We've reviewed this range of IPs via SNDS vigorously. For 89 days of > data, there's not a single day where complaints are < 0.1%. Over these 89 > days, 6.5 million messages have been sent, and over this time, only 8 trap > hits occurred from list attrition. We've had these IPs in their feedback > loop since inception and no spike or gradual increase has occurred in this > time. > > - We asked for a reasoning why, and after some stock responses, we > received a note back that they could not discuss the matter of the block. > > We've needed a closer look at this by Microsoft but are at a dead end. I'm > asking if anyone here has any avenue we can try to reach out to, or ideas > as we need to get insight but haven't got any answers. > > Thanks, > > Dickie LaFlamme / Deliverability Specialist / Dyn > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > <https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fchilli.nosignal.org%2fcgi-bin%2fmailman%2flistinfo%2fmailop&data=01%7c01%7cMichael.Wise%40microsoft.com%7c569e7f198bc64001632908d38f00a173%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ZWtHg%2fJGeN%2bjEuJ1SLHsvx%2fDQBWDLdQ5q%2b3ny5RdAKg%3d> > > > > > > >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
