rpg-works
09-01-2002, 11:29 AM
Disclaimer: I don't work for RackShack, or EV1. This posting is not directed specifically at HostPacket's situation, but rather, the number of postings that have come about critical of RackShack's policy of pulling a server on a second spamming offense.
In addition to running RPG-Works.Net I work for an ISP (not EV1) as a technician. Part of my responsibilities include handling spam reports. My employer has a great number of dialup users, web hosting clients, and broadband customers. We typically get a spam complaint (for the whole group) every week or two. Usually it's because of a customer setting up an open relay. Most reports come from SpamCop.
I also have RPG-Works.Net hosted with RackShack.
Here's my strategy for keeping from running afoul of this policy:
1) My services aren't the cheapest. Spammers typically look for the cheapest provider. Don't set yourself up as the cheapest provider. Offer a quality service at a fair price.
2) I don't offer instant activation: spammers also look for this. I hand screen all applications for new accounts. It's far easier to keep spammers out in the first place than to deal with them once they've done their deed.
3) Spam complains, should I ever get any, go to me not RackShack. The trick is to have RackShack set up your reverse DNS for your server's IP to your domain. They'll do this -- if you're a RackShack customer just put in a ticket requesting it.
Because of this, SpamCop (and most other spam reporting tools) will send messages to abuse@rpg-works.net. This box is checked regularly. I am my own abuse desk. No one has spammed yet from my service, but if they do, I will be the first to know, and their account will be swiftly terminated. If someone spams from my service, I will deal with it faster than RackShack ever could, and RackShack has no need to disconnect the server.
The key to avoiding getting into trouble is to avoid spammers in the first place, and make sure SpamCop reports are getting sent to abuse@yourdomain.com, not abuse@rackshack.net.
In addition to running RPG-Works.Net I work for an ISP (not EV1) as a technician. Part of my responsibilities include handling spam reports. My employer has a great number of dialup users, web hosting clients, and broadband customers. We typically get a spam complaint (for the whole group) every week or two. Usually it's because of a customer setting up an open relay. Most reports come from SpamCop.
I also have RPG-Works.Net hosted with RackShack.
Here's my strategy for keeping from running afoul of this policy:
1) My services aren't the cheapest. Spammers typically look for the cheapest provider. Don't set yourself up as the cheapest provider. Offer a quality service at a fair price.
2) I don't offer instant activation: spammers also look for this. I hand screen all applications for new accounts. It's far easier to keep spammers out in the first place than to deal with them once they've done their deed.
3) Spam complains, should I ever get any, go to me not RackShack. The trick is to have RackShack set up your reverse DNS for your server's IP to your domain. They'll do this -- if you're a RackShack customer just put in a ticket requesting it.
Because of this, SpamCop (and most other spam reporting tools) will send messages to abuse@rpg-works.net. This box is checked regularly. I am my own abuse desk. No one has spammed yet from my service, but if they do, I will be the first to know, and their account will be swiftly terminated. If someone spams from my service, I will deal with it faster than RackShack ever could, and RackShack has no need to disconnect the server.
The key to avoiding getting into trouble is to avoid spammers in the first place, and make sure SpamCop reports are getting sent to abuse@yourdomain.com, not abuse@rackshack.net.
