On 12/7/21 9:49 AM, Jayson Smith wrote:
Hi,


Just over two weeks since I found myself on Microsoft's blocklist and was manually removed, I find myself back on their blocklist again. Possibly coincidentally, this morning MXToolbox informed me that Linode has apparently found itself back on Uceprotectl3. Does anyone know if Microsoft considers that particular blacklist when deciding to blocklist an IP? Naturally, I've submitted a deliverability support ticket, and will probably have to wait several hours for the result.


Uceprotectl3 and Uceprotectl2 are not respected blacklists. Many people view them as extortion. Microsoft does not use them (pretty much no one does). I have a server that's on Uceprotectl3 and periodically is on Uceprotectl2 and Microsoft is not blocking it.


As always, I'm not doing anything wrong (that I know of at least). Even if someone had hacked my server, my hypothesis is that they'd have to be a very careful and methodical hacker if their aim were to get me blocklisted by Microsoft and only Microsoft. If my server were spewing out spam, I ought to be hitting Spamhaus/SORBS/etc. spam traps left and right. Trust me, one time I was hacked, my server was sending out spam and I didn't know it, and I quickly found myself on Spamhaus XBL.


Any thoughts?


Dealing with Microsoft blocks is always a pain. It requires patience and persistence, but if you persevere, they will eventually unblock you.


--
Mark Sapiro <m...@msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

Reply via email to