Yes, I have seen this. Quite annoying when you enforce TLS outbound. :)
> Am 31.12.2020 um 10:48 schrieb Stefan Bauer via mailop <mailop@mailop.org>: > > > Hi, > > one of our pub-ip seems to be blocked by MS. Side effect is, that > olc.protection... is not offering starttls in this case. > Anyone else seen that? > > # telnet eur.olc.protection.outlook.com. 25 > Trying 104.47.18.161... > Connected to eur.olc.protection.outlook.com. > Escape character is '^]'. > 220 AM7EUR06FT011.mail.protection.outlook.com Microsoft ESMTP MAIL Service > ready at Thu, 31 Dec 2020 09:21:40 +0000 > ehlo mydomain.com > 250-AM7EUR06FT011.mail.protection.outlook.com Hello [116.203.31.6] > 250-SIZE 49283072 > 250-PIPELINING > 250-DSN > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250-BINARYMIME > 250-CHUNKING > 250 SMTPUTF8 > > SNDS reports: > > 116.203.31.6,116.203.31.6,Yes,Blocked due to user complaints or other > evidence of spamming > > However the real data is only available the next day on > https://sendersupport.olc.protection.outlook.com/snds/data.aspx > . How does one deal with that situation? > > We monitor our outgoing mails but did not catch/see any malicious/spammy mail > recently from this node/host. > > Stefan > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
