New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
spamcop.net not renewed, marking mails as SPAM
Many recipients are marking the emails as SPAM, the reason is that bl.spamcop.net is not responding (domain expired).
554 5.7.1 Service unavailable; Client host [x.x.x.x] blocked using bl.spamcop.net
Disable spamcop in your WHM/cPanel server:
sed -i 's/^acl_spamcop_rbl=.*/acl_spamcop_rbl=0/' /etc/exim.conf.localopts; /scripts/buildeximconf; /scripts/mailscannerupdate; /usr/local/cpanel/scripts/restartsrv_exim;
Comments
Oh damn...
Buy the domain when it releases. Then you can influence a portion of the global email system.
After that, write a blog post like this:
https://thehackerblog.com/the-io-error-taking-control-of-all-io-domains-with-a-targeted-registration/index.html
That's going to hurt a lot of peoples email.
I see, that’s affected hetrixtools.
Looks like its back
i see a parking page for expired domains. quite embarassing for cisco...
Renewed, DNS / TTL propagation...
Omg they eventually renewed it , correct nameserver now getting served.
Updated Date: 2021-01-31T16:04:06.00Z�����
Name Server: NS1-109.AKAM.NET
Name Server: NS1-11.AKAM.NET
Name Server: NS1-73.AKAM.NET
Name Server: NS1-90.AKAM.NET
Name Server: NS1-93.AKAM.NET
Name Server: USE1.AKAM.NET
Well that was fun.
If I remember correctly you use Spamcop at Mxroute.
Yup. This was the impact: https://freesocial.co/@mxroute/105651204938533809
We had the same problem on some of our servers.
RFO: spamcop's filters trapped the renewal notice so they didn't get the message it expired.
If a postmortem interests you on the impact of a mail service running spamcop, these numbers are good enough: https://status.mxroute.com/incident/49
So I guess all mail systems using spamcop have a single point of failure - a 10 buck domain name
@jar so with about 1/2 the emails coming in on lucy labelled spam by spamcop during that period from 1 sender - did your system detect them prior to spamcop failure as one of the heaviest inbounders and in need of investigation? Just curious (I'm a moron when it comes to email servers)
Truthfully I don't have any monitors on inbound behavior short of uptime. Usually don't have to, because any problem there tends to manifest in another way (and those all have creative monitoring). I'm in the middle right now between this being evidence that I need monitoring on that front or that I've effectively done away with the only thing that would have justified it. Probably leaning toward the latter, pending further evidence of a need.
My client is using Postie plugin in his WP site. He sends email from Gmail to specific [email protected] and Postie fetches it and publishes. But yesterday afternoon whole thing didn't work and I opened ticket with @seriesn
After sometime the mails got delivered. I thought it was some issue with NB. But today got update on the ticket about this post. Shall I sue them @deank
Of course, you should sue them.
It's the only way to show the world that you are indeed serious.
You should ask your provider to do push-ups. It's faster than suing.
The going rate is one push-up per hour of downtime.
On the other hand, you should #DeleteWordPress and use Blogger instead. Blogger has an email-to-post service with fewer moving parts and thus more stable.