I don't think any ISP would reject an IP that is on the Spamhaus
list.you, clearly, have been living under several rocks for a very long
time.
we reject automagically on spamhaus, mail-abuse.org, and sorbs. really
appreciate their services.
randy
Our person in charge has consulted with their previous person in charge, and their response is this.
“problem began long before February 18th. The problem was that in 2022 they added our prefix 87.251.79.0/24 to the black list, and said that if there were no complaints for 30-60 days, the record would be deleted. we agreed, almost a year has passed, the record has remained. They tried several times to put pressure on our providers, but we always record any termination of the contract with large fines, not a single provider has done this, we pay a lot of money for the Internet, and no one wants to take risks, now spamhouse pressure on”
Actually, I didn’t know what a spamhouse was before this month, until we announced the IP in vultr
They claim they’ve been working on the issue, but I’ve found that they don’t respond to emails very well (I can only judge from this). Usually though, I tell them to take down the content, and then the content gets a different provider.
Also, it’s not clear to me whether we need to reply to emails sent from the spamhouse system. They claim that they took care of the content, but I personally think it’s because they didn’t respond to the email that spamhouse thinks they’re not doing it
<snip>
you are talking up the discussion with the wrong folks, really.
Please go see the spamhaus folk directly.
this company(s) is in the business of spam. they're just trying to
game nanog. discussing further a waste of pixels.
ranady
Hi Brandon,
Your next actions are to level up the security of your network, your organization, and your team. I’ll craft up a post with a checklist you can use.
If you don’t do this, then people on your team, your company, and your customers will continue to be “danger do not go there” listed. Spamhaus is not the only one providing easy tools to help organizations deploy “danger do not go there” list.
Step 1 on the list …. Deploy Exploitable Port Filtering on the edge of your network ….
[
Filtering Exploitable Ports and Minimizing Risk from the Internet and from Your Customers
senki.org
](Filtering Exploitable Ports and Minimizing Risk from the Internet and from Your Customers - SENKI)
The other steps I’ll put into a blog post.
Barry
Hello Barry,
Thanks for your blog.
I plan to block some ports on our router, which are shown in your blog.
Step 1 on the list …. Deploy Exploitable Port Filtering on the edge of your network ….
Some of our routers use Linux as the operating system, so I plan to use nftables to make some filtering rules.
Best,