Read the forum guidelines
Hopefully, the right people (that care) will see this, as it is causing Cox initiated message delivery failures for anyone doing SpamCop BL lookups.
Blacklisted SMTP server IP is 126.96.36.199. Other Cox SMTP servers appear to be fine, but I'm not going to go through all of them to check. We noticed this when one of our end users reported intermittent delivery failures from their Cox email account when trying to email their work account. http://www.spamcop.net/bl.shtml?188.8.131.52
00532 10:34:55.790 DNS Blacklist lookup: 184.108.40.206 is not listed in <bl.spamcop.net> - rcode(1)
00532 10:35:00.806 DNS Blacklist lookup: 220.127.116.11 listed in <bl.spamcop.net> Blocked - see http://www.spamcop.net/bl.shtml?18.104.22.168
From the header: Received: from eastrmimpo305.cox.net ([22.214.171.124]) by eastrmfepo201.cox.net
Hi Becky, this is mail client agnostic. My side is the third party mail gateway receiving e-mail from a Cox e-mail address. One of our spam checks hits against SpamCop and other Tier1 block lists. You can do a look-up directly at SpamCop or Multi-RBL to confirm the SpamCop blacklist (http://multirbl.valli.org/lookup/126.96.36.199.html).
Cisco Talos also reports the IP as having a poor reputation, which will impact delivery to other domains that use IP reputation as a spam prevention strategy. https://www.talosintelligence.com/reputation_center/lookup?search=188.8.131.52
Let me know if I can provide any further information.
Spamcop auto removes after 24 hours of no reports of spam.
Correct, and the timer keeps renewing, keeping it on the blacklist, so the issue is not resolved. The current timer reports 22 hours remaining.
In the past 90.1 days, it has been listed 38 times for a total of 43.3 days