![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
This is ridiculous!!
Dec. 1st, 2003 10:17 pmI just sent some email to some mailing lists on a particular server that hosts several lists I'm on. It got bounced because the IP address of my ISPs SMTP server was listed. That's bad enough. But these guys want a $50 donation to a charity to remove the address from the blacklist!!!
Yes, causing spammers to have trouble getting easily removed from blacklists is good. But this isn't the way to do it.
Especially when dealing with an address of a major ISP's SMTP server. It's punishing all the customers because *one* user is either infected or hasn't been caught yet.
Worse, the info they provide about the incident isn't sufficient for anyone to track down what user at the ISP did send the alleged spam.
I sent them a rather pointed note. And I'll be calling customer support at the ISP later. Not that I expect them to be much help.
If the folks running the blacklist don't come up with a reasonable response, I may call *their* ISP or hosting service.
Their intentions may be good, but their execution *sucks*.
Oh yeah, what triggered this? *ONE* message from the SMTP server's address to a spamtrap address.
I'm sorry, but blacklisting for that WITHOUT A HUMAN CHECKING FIRST is inexcusable.
Yes, causing spammers to have trouble getting easily removed from blacklists is good. But this isn't the way to do it.
Especially when dealing with an address of a major ISP's SMTP server. It's punishing all the customers because *one* user is either infected or hasn't been caught yet.
Worse, the info they provide about the incident isn't sufficient for anyone to track down what user at the ISP did send the alleged spam.
I sent them a rather pointed note. And I'll be calling customer support at the ISP later. Not that I expect them to be much help.
If the folks running the blacklist don't come up with a reasonable response, I may call *their* ISP or hosting service.
Their intentions may be good, but their execution *sucks*.
Oh yeah, what triggered this? *ONE* message from the SMTP server's address to a spamtrap address.
I'm sorry, but blacklisting for that WITHOUT A HUMAN CHECKING FIRST is inexcusable.
