We recently saw that "S3150" on 3 IPs part of 3 larger netblocks.
For all of them we opened a ticket and they "mitigated the IP": I
tried collecting more info to no avail, of course :-( .

Weird thing is at least one of them has always been *green* on SNDS
and had not abuse reports at all in the recent months.
That IP is part of a 9IP shared pool, so sending the same emails of
the other neighbour IPs and it is the only one that was blocked with
that error.
That IP was a low volume IP (200-400 daily email) and I randomly
picked few emails from the days before the block and I have not been
able to identify spammy emails.

I asked in the ticket if they could give some hint about the issue as
I can't find spammy emails, I didn't receive abuses and SNDS says
everything was good before (and everything is still good for the twin
IPs) but they simply mitigated and ignored my questions.

So, +1 to your questions.

Stefano

On Tue, 11 May 2021 at 14:07, Benoit Panizzon via mailop
<[email protected]> wrote:
>
> Dear List
>
> One of our main smtp outbound ip addresses is blocked by microsoft.
>
> host outlook-com.olc.protection.outlook.com[104.47.10.33] said: 550 5.7.1
> Unfortunately, messages from [157.161.12.84] 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.
> [DB5EUR03FT006.eop-EUR03.prod.protection.outlook.com] (in reply to MAIL
> FROM command)
>
> I checked our JMRP entries. This IP is listed as one of our
> mailservers. The complaint rate is < 0.1% but it had 2 'trap' hits and
> is in status red.
>
> Our abuse desk email address is registered for the ARF feedback loop
> for the ip range in question.
>
> We usually get a lot of feedback loop emails, mostly false positives of
> Mirosoft users mixing up 'junk' with their trash folder or similar, or
> moving all their old mail to 'junk' causing an avalanche of complaints
> being sent. I opened several cases with Microsoft about this, but never
> got any solution offered (as a sidenote rant)
>
> But no, there were no complaints about: 157.161.12.84 received.
>
> Does anyone know, how to get hold of the emails that caused this
> blocking?
>
> Mit freundlichen Grüssen
>
> -Benoît Panizzon-



-- 
Stefano Bagnara
Apache James/jDKIM/jSPF
VOXmail/Mosaico.io/VoidLabs
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop

Reply via email to