You'd be DoS-ing yourself and all the other customers of that ISP, because you'd be causing slowdowns and backlogs of their servers, while the spammers get off scott-free.
It's the standard dilemma: "'xyz' will make them notice, but it also may make them decide I'm a hacker." That is, if they do genuinely have a problem that needs to be fixed... where, exactly, is the fine line between protecting yourself, and causing a problem?
They wouldn't be able to do much, that's for sure. In this respect, you need to get a lot of work done on TarProxy and make it suitable for use in Enterprise/ISP environments ASAP, because otherwise people are going to be hurting themselves (and all the other customers of the same ISP), when they go to implement this tool.
This is actually one of the places where I expect to be able to be exceptionally helpful. While I don't have the time these days to dive into massive coding projects, I *am* good at those "silly things" like documentation and UI design.
---- : The tarproxy-list mailing list is archived at : http://www.mail-archive.com/tarproxy-list%40martiansoftware.com/ : : To unsubscribe from this list, follow the instructions at : http://www.martiansoftware.com/contact.html : : TarProxy's project page can be found at : http://www.martiansoftware.com/tarproxy
