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 (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
.
X-PowerMTA-BounceCategory: other

Thanks,

[image: Dyn logo, Dyn.com] <http://dyn.com/>
<http://twitter.com/dyn>    <http://twitter.com/dyninc>[image: Dyn facebook
account] <http://facebook.com/dyn>    <http://twitter.com/dyninc>[image:
Dyn LinkedIn account] <http://linkedin.com/company/dyn>

Dickie LaFlamme / Deliverability Specialist
 +1 603-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
>>
>>
>
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Reply via email to