> -----Original Message----- > From: Igor Pechtchanski [mailto:[EMAIL PROTECTED] > Sent: 23 September 2004 16:44
> On Thu, 23 Sep 2004, Dave Korn wrote: > > > > -----Original Message----- > > > From: cygwin-owner On Behalf Of Christopher Faylor > > > Sent: 23 September 2004 15:40 > > > <idle speculation> > > > Hmm. I wonder if I just replaced all of the '@'s with a png > > > of an '@', > > > if that would foil the spammers. > > > <pause> > > > Nope. Wouldn't work for the text archives. > > > </idle speculation> > > > > How about a big ascii-art one then? THaT WuLd BE SOOooOO > B1FF!!1! AND K00L!!1!2! > > You mean, like "`banner -c@ @`"? ;-) [EMAIL PROTECTED] /win/c/> `banner -c@ @` bash: @@@@: command not found AAAAAAARRRGHGHGHGHG!!!1!!!! ToO MANy QuOTEZ!:!:! ;-P~~~ > Ugh, I can just see the following pasted command line getting mungled: > > [EMAIL PROTECTED]>command.com something LOL, I was just thinking about what would happen if someone harvested that address and tried to spam it, and then I was thinking, hey, I wonder.... lookee what I found! http://www.command.com/ > (and that's just off the top of my head, there must surely be others). Yeh, that's why I suggested clamping down on the chars that would be accepted by replacing the .* with a [] charset. > IOW, it's not as easy as it seems at first. I know. Didn't even attempt to deal with emails of the form <[EMAIL PROTECTED]>. Sure there are lots of other corner cases too. It was a rough approximation JFTHOI. [ There are plenty of rfc822-detecting regexen out there, although not all of them are complete nor correct; http://www.google.com/search?hl=en&ie=UTF-8&q=regex+rfc822 ] cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
