Comment Re:Blacklists (Score 1) 663
First of all, they're not blocking SPAM by shutting down open relays. SPAM'ers do not require a system of relays to get their mail where it's going. Newsletter software and a Yahoo! Mail account will do that for you.
They're screwing people over just because they may not have a vast knowledge of mailing systems/software.
Remember: It doesn't take a genius to build a web site and buy a dedicated server. Heck, simple mistakes could be made simply by an inability to situate to an unfamiliar OS and the applications therein.
Some of the SPAM Blacklists won't remove the submission from their list, and now our customer's mail is often rejected simply because of a few lists inability to keep their data current.
The inability of these moderators/administrators is directly effecting an outside company simply because they don't feel the need to keep their data from going stale. If you don't have the time to manage a SPAM Blacklist; don't start one.
And I wrote the form-2-mail script myself. It was designed for just what you've explained. The addresses are stored in an array within the script, and are limited/protected. If spam'ers attempt to send spam through the system they will either get rejected by the a) referrer b) array limitations c) mail server or d) domain restrictions. I didn't just go pick it up at the first CGI directory that I came across.
And by the way, this article is about spam blacklists, so let's try to keep the criticizm to ourselves, or at least save it for a topic titled "Form-2-Mail Scripts", shall we?
If your customer configured the server wrong, making it an open relay, then it is that customer you should be collecting recovery costs from. In the future, be sure terms that specify this is in your contact that you have each customer sign. Be sure the spam and open relay issues are discussed with them before the service is turned on.
I also believe that Slashdot is for the sharing of information and opinions. I never asked you to suggest changes in how we deal with our customers.
They're screwing people over just because they may not have a vast knowledge of mailing systems/software.
Remember: It doesn't take a genius to build a web site and buy a dedicated server. Heck, simple mistakes could be made simply by an inability to situate to an unfamiliar OS and the applications therein.
Some of the SPAM Blacklists won't remove the submission from their list, and now our customer's mail is often rejected simply because of a few lists inability to keep their data current.
The inability of these moderators/administrators is directly effecting an outside company simply because they don't feel the need to keep their data from going stale. If you don't have the time to manage a SPAM Blacklist; don't start one.
And I wrote the form-2-mail script myself. It was designed for just what you've explained. The addresses are stored in an array within the script, and are limited/protected. If spam'ers attempt to send spam through the system they will either get rejected by the a) referrer b) array limitations c) mail server or d) domain restrictions. I didn't just go pick it up at the first CGI directory that I came across.
And by the way, this article is about spam blacklists, so let's try to keep the criticizm to ourselves, or at least save it for a topic titled "Form-2-Mail Scripts", shall we?
If your customer configured the server wrong, making it an open relay, then it is that customer you should be collecting recovery costs from. In the future, be sure terms that specify this is in your contact that you have each customer sign. Be sure the spam and open relay issues are discussed with them before the service is turned on.
I also believe that Slashdot is for the sharing of information and opinions. I never asked you to suggest changes in how we deal with our customers.
