Ged Posted February 26, 2023 Share Posted February 26, 2023 "A Forum for those things that just plain go wrong or don't work as advertised." Seems to cover it. This weekend SpamCop's emailed acknowledgements of our reports started to come from a new IP, 184.94.240.88. Mail server log extract: Feb 25 22:59:51 mail6 xm[8046]: 31PMxYmR020727: [184.94.240.88], SPF RECORD [v=spf1 ip4:184.94.240.89 ip4:184.94.240.112 ip4:204.15.80.0/22 -all] Feb 25 22:59:51 mail6 xm[8046]: 31PMxYmR020727: [184.94.240.88], [AS16417], spf [mfrom] test results for [spamid.0@bounces.spamcop.net] Feb 25 22:59:51 mail6 xm[8046]: 31PMxYmR020727: [184.94.240.88], [AS16417], spf [mfrom] result fail (Mechanism '-all' matched) SPF FAIL, not to mention no PTR record $ dig +short -x 184.94.240.88 $ and the IP being on eight of the blocklists that I use. Our system auto-reported 19 of these to SpamCop before I managed to stop it... :( Quote Link to comment Share on other sites More sharing options...
franki Posted March 1, 2023 Share Posted March 1, 2023 Yes, it seems that the SPF has already been fixed: https://forum.spamcop.net/topic/48876-is-the-filtering-service-broken/#comment-163024 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.