I'm sick of making archive messages un-replyable and living in
perpetual fear of spam harvesters. So, I've been reading through the
anti-spambot guidelines at http://www.turnstep.com/Spambot. It appears
to me that the best way to protect archival addresses from spam
harvesting, while keeping them most usable for humans, is through a
CGI program.
The example form from their guidebook splits the email address into
two parts, the CGI program puts them back together, and returns a
mailto: link to the browser. The example form at
http://www.turnstep.com/Spambot/Programs/Nomailto.pl is:
<FORM METHOD="POST" ACTION="/cgi-bin/Nomailto.pl">
<INPUT TYPE="HIDDEN" NAME="spambot" VALUE="greg">
<INPUT TYPE="HIDDEN" NAME="beware" VALUE="turnstep.com">
<INPUT TYPE="SUBMIT" VALUE="Send me email!">
</FORM>
Implementing this trick with MHonArc means either hacking code or post
processing, since only the full email address is available in the
rcfile, and there is no mechanism to mangle it. I'd like to attempt
to patch MHonArc, because post processing large amounts of email is
too much of a logistics headache.
So the question is - any suggestions on how to best approach the
problem? Which section of code is best to look at, and what mechanism
is best for passing back email address fragments? (Should I try to
define new resources, for example?)
Any thoughts are appreciated.
Cheers,
Jeff
