Some days, I think this would be useful in the fight against spammers: <http://www.guntruck.com/DavyCrockett.html>
On Wed, 22 Jan 2003 13:37:21 -0600, [EMAIL PROTECTED] wrote: >Lynn, > >While I dislike GoDaddy very much, your comment is exactly >why I feel GoDaddy and other registrars do have legitamate >reasons to make their whois "selectively available". > >Contracts aside, I'm guessing ICANN is in a bit of a bind >on this one since both spammers *AND REGISTRARS* misuse >the Whois system -- And I classify such registrars as >spammers since many do send me renewal spam as well as >physical mail. > >I feel ICANN should address Registrar misuse of other >registrars Whois first and *THEN* address contractual >obligations ... But I've no idea how the handle pure >spammers other than bandwidth limiting .... > >Just my 2 cents. > >Charles > > >On Wed, 22 Jan 2003 10:04:29 -0800 >�"Lynn W. Taylor" <[EMAIL PROTECTED]>�wrote: >>Oh, please! >> >>I get enough spam without making it easier for the >>bastards to parse WHOIS. >> >>On Wed, 22 Jan 2003 11:42:55 +0100, Csongor Fagyal wrote: >>>[EMAIL PROTECTED] wrote: >>> >>>> >>>>�I've sucessfully written a Whois Parser which I maintain >>>>to this day >>>>�.... Thanks to all the idiot spammers who mine Whois for >>>>email >>>>�addresses I have found the following, >>>> >>>>�1) To make Whois Parsing very difficult Several >>>>registrars dynamically >>>>�change, >>>> >>>>�a) the Whois field prefixes b) the order that Whois >>>>sections appear >>>>�(tech first one time then reg the next time) >>>>�c) the actual formating of a fields contents (!) >>>> >>>>�2) Several registrars will temporarily block your IP >>>>after just a very >>>>�few Whois accesses. >>>>�So, from experiance, I can say writing a Whois parser >>>>these days is >>>>�*VERY* difficult! >>> >>>I say it's the 21st century, and you cannot get XML WHOIS >>>output. That's >>>just nonsense. >>> >>>- Cs. >> >>
