>It was called [EMAIL PROTECTED] and the spams are very clearly archived. And >it did get hit pretty hard towards the end.
Holy mackeral, that's a lot of spam! I did a correlation check against my control lists (and java-linux just for good measure) and one of your last ten spams appeared on another list. That spam was from a pre-antispambot harvest. So, I suspect the vast majority of your list's spam was not due to mail-archive.com exposure. >Actually you can probably liberate some code. The bonsai code over at >mozilla.org uses javascript to do exactly this. They display email >addresses as foo%bar.com and dynamically convert it to a usable mailto: Hmm... what a horrible solution, deliberately ignoring straightforward w3c compatibility standards, adding an unnessary indirection, increasing system complexity, and requiring a vastly more sophisticated client. My engineering sensibilities are apalled. (They keep suggesting shooting the spammers.) But that may be the way to go. Especially if I can put the obfuscated email address in the mailto: and just have a javascript function automagically do the conversion. After a quick look at bansai it was not obvious to me what they were doing (they seem to have javascript and a cgi program joined at the hip for this + some added functionality.) I don't suppose you'd be interested in providing a pure javascript code example? Another thing I was thinking of was providing email addresses as jeff<strong>@</strong>jab.org without a mailto: link. Think that would be as effective as jeff%jab.org and cause less confusion? Jeff
