This is now resolved, we are once again accepting your spam reports, which reports to senders' network owners and helps populate the SpamCop blocklist.
We are aware of an issue in which SpamCop does not accept user submissions. The fix will be tested and deployed no later than August 12, 2024.
The SpamCop blocklist is still functional due to its other data sources.
We apologize for any inconveniences this causes.
The #SpamCop website will be down for 5-10 minutes for network maintenance between 2023-10-20 18:00 PDT and 2023-10-21 01:00 PDT (1a-8a UTC Saturday).
This will not affect the blocklist.
The #SpamCop website will experience another 10-15 minute downtime as we upgrade some networking hardware on Friday 2023-09-22 at 8:00p-11:00p PDT (3a-6a UTC Saturday).
As before, the blocklist and email processing will not be affected.
Late Friday night, the #SpamCop website will undergo scheduled maintenance with 10-15 minutes of downtime between 8:00p and 11:00p PDT (3a - 6a UTC Saturday).
The blocklist and email processing will not be affected.
SpamCop.net has some infrastructure issues at the moment and some of its services are intermittent. There is no risk of false convictions from this incident.
@gumnos@SpamCop_net While my primary server can still send to them without any problem at all.
So … I know that it’s not a routing nor firewalling problem.
I’ve not yet fired up tcpdump / Wireshark to analyze things.
🤔
I love how emails from @LinkedIn tell me I can reply to the email to reply to the sender, but when I do, their mail-server 500-rejects mine.
My Care-o-Meter™: 📉
Hey @SpamCop_net is there a reason reported spam emails are not being actioned? No emails with analysed reporting links now for days.
Something is broken.
@paul2dart Yes! Some attacks are too fast or too distributed to get listed in time, but even then the reports we generate to network providers can help limit future abuse.
@axellpunkt@freepik We need the RFC 5322 email headers (not the HTML <head>) in addition to the MIME/HTML content. The Received: headers tell us who sent the spam. See #Message_format" target="_blank" rel="nofollow noopener">en.wikipedia.org/wiki/Email#Mes… and the links in the page you screenshot.
@shendison@Intuit@QuickBooks Our users and traps have been experiencing invoice spam from this @Intuit infrastructure. One of these two IPs has already had its listing auto-expire.
Anyone having trouble getting @Intuit@QuickBooks invoices / PO's etc. to be received today? It took me about 45 minutes, but I finally found that @SpamCop_net is blocking them, and some (many) ISP's simply cannot deliver their mail. Can someone please fix this?
The SpamCop.net network upgrade has been broken into two phases. The second phase will take place tonight, to be a 5–15 minute outage between 2022-03-11 23:00 and 2022-03-12 03:00 EST (−0500).
Again, this will not affect the blocklist.
The SpamCop.net website (not the SCBL blocklist!) will undergo a network upgrade tonight (2022-03-10). There will be a 5–15 minute outage between 23:00–23:59 EST (−0500).
This was recently retweeted by somebody. This problem was resolved that week and safeties were put in place to prevent it from recurring.
Also: servers that properly sought responses of 127.0.0.2 (as noted at spamcop.net/fom-serve/cach…) suffered no ill effect.