newjoiseyboy

I suggest adding a reply to this other thread as the SpamCop staff/admins were watching it:

@Calion, I believe that is correct. My email got marked as bouncing spamcop emails on the 26th of February which is when I think this all started.

Aha. I found this thread which is relevant. Seems a few bits got dropped on the floor, and things are working for other people already. I was just 4 days late to finding out.

Yeah, maybe I should do that at this point. I don't believe I've ended up blocking legitimate mail before now -- never had this happen with SpamCop before -- but I wanted to put this out there in the event there was an actual security issue, just in case.

Yeah, I looked at your link earlier. That's got nothing to do with what I posted. Somebody was trying to get you to send them Bitcoin. They haven't hacked anything.

Oh, I think that's different. I get those to my domain from time to time, that's just your regular crypto threat-phishing email.

I have my system set up to forward spam to SpamCop, which I did earlier today and was expecting to get report notifications. When I didn't, I logged in and I saw that my system had bounced mail from SpamCop. I didn't see what had gone wrong at first, because the error message was incomplete, and I saw that the only report I had in the queue was a bit of spam from 4 days ago. I double-checked my logs, and my system bounced SpamCop's report email because the IP is now listed with Spamhaus. The report is still active, and I'm not sure I should necessarily whitelist SpamCop's IPs if the contents of this report are accurate. I do not recall seeing this from SpamCop's servers before, so I figure, better safe than sorry. In the meantime, I can use the form to submit email so I don't trigger any more bounces, until this is resolved. Feb 26 17:08:21 <myserver> postfix/smtpd[20277]: NOQUEUE: reject: RCPT from unknown[184.94.240.88]: 554 5.7.1 Service unavailable; Client host [184.94.240.88] blocked using zen.spamhaus.org; https://www.spamhaus.org/query/ip/184.94.240.88; from=<spamid.6800685979@bounces.spamcop.net> to=<me@mydomain.com> proto=ESMTP helo=<vmx.spamcop.net> Let me know if there's a better place to fire this report.