I <[EMAIL PROTECTED]> wrote: > I guess my ideal mailing list archiver would mangle everything that fit an > email address regexp. Of course, the regexp might accidentally match > something in uuencoded text or something, so it should insert a line > somewhere in the message warning that mangling had been done. The message > could be a hyperlink to a page describing the mangling scheme. It should be > easy for a human to manually demangle, but impractical to write a SPAM-bot > to do it. For instance, you could include a special string in all the > mangled names which would be unique to each mailing list (and which > hopefully wouldn't appear in the URL). > > For instance, "[EMAIL PROTECTED]" might get mangled as something > like ":MANGLED:[EMAIL PROTECTED]:MANGLED:". Another scheme I've thought about in the past is replacing email addresses with entries into a table of mangled string translations. Like "[EMAIL PROTECTED]" would change to something like "MANGLED_STR=1394=" then you could get the table of mangled string translations by emailing an autoresponder or submitting a web form. The translations would be mailed to you only if you were a subscriber to the mailing list. The translations could be in the form of a sed script: s/MANGLED_STR=1=/MANGLED_STR/g # the escaping mechanism needs more thought... [...] [EMAIL PROTECTED]/g [...] The translations could also be available by subscription, so that you'd get a new copy each time a new string was mangled for the first time... ----------------------------------------------------------------------- Dan Harkless | To prevent SPAM contamination, please [EMAIL PROTECTED] | do not post this private email address SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
