Nice we won the race, got lots of new members and all seems to be going smoothly - Berkley even seems to be somewhat under control 😉
I have spent the past week getting the colo center where gygabite.com is located out of the SPEWS database.
The owner of the place took on a client that got them a lot of attention, all bad.
There are people out there who are on a mission, these people sit and monitor certain 'business owners' and their domains. Whenever a domain gets hosted somewhere they report it to SPEWS. They include all netblocks owned by the hosting company.
So all class C networks of the place got listed in SPEWS. Then the companies that block net traffic based on the SPEWS database started rejecting connections from my server, because it uses IP addresses within the listed netblocks.
Whether you think this is right, wrong or otherwise there's one thing for sure - it does cause a restraint of trade. It's a real life throw the baby out with the bathwater situation.
Bottom line was that the data center unplugged the "offensive" client and now things are getting back to normal.
SPEWS is a major knee jerk reaction to the spam problem, borne out of the frustrations of having laws passed that are unenforced and the crazy spammers going completely out of control. It makes me see a real value in 'private email' systems, where the server determines if email is aceptable to you or not and only delivers that which is acceptable. I know some of these are in the works, I know someone who is developing such a system now and have arranged to be the first to use and host it when it is ready.
Hopefully the beta testing period won't last too long and he can get it out where it can start to do some good.
I have spent the past week getting the colo center where gygabite.com is located out of the SPEWS database.
The owner of the place took on a client that got them a lot of attention, all bad.
There are people out there who are on a mission, these people sit and monitor certain 'business owners' and their domains. Whenever a domain gets hosted somewhere they report it to SPEWS. They include all netblocks owned by the hosting company.
So all class C networks of the place got listed in SPEWS. Then the companies that block net traffic based on the SPEWS database started rejecting connections from my server, because it uses IP addresses within the listed netblocks.
Whether you think this is right, wrong or otherwise there's one thing for sure - it does cause a restraint of trade. It's a real life throw the baby out with the bathwater situation.
Bottom line was that the data center unplugged the "offensive" client and now things are getting back to normal.
SPEWS is a major knee jerk reaction to the spam problem, borne out of the frustrations of having laws passed that are unenforced and the crazy spammers going completely out of control. It makes me see a real value in 'private email' systems, where the server determines if email is aceptable to you or not and only delivers that which is acceptable. I know some of these are in the works, I know someone who is developing such a system now and have arranged to be the first to use and host it when it is ready.
Hopefully the beta testing period won't last too long and he can get it out where it can start to do some good.
