Whether 'bots' are smart enough yet to read ASCII or javascript yet has not been proven. Until it is, I feel I have a responsibility to prevent their access to addresses on a public site as best I can. That's why I use ASCII coding. While javascript capable browsers may be dominant, most can turn off its use, I'm just too lazy to 'sniff' for that, I just use what I know will work, even in a text-only browser.
I use
SPAMstopperin OS 9. I don't see it in the authors site right now, but I'll bet he can provide it. He does have a version for X, however. I'm sure there are other programs similar to this one. I like it because it has many options to 'encode' exactly what you want. The easiest would be to just encode the word 'mailto:' which seems to be the most common search word for bots. I use the 'Full Paranoid' choice, leaving nothing but ASCII for everything.
I recently made a page (not live yet) to allow registration for Vacation Bible School. Because of my concerns for cost (secure access costs about half as much as our yearly fees) and the vulnerablility of e-mail, I limited the form to just a phone number and a list of choices to be called for further info. I have seen other sites that ask for everybodys name (parent, child, emergency contact), phone numbers, addresses, age, and even
special health problems of the child!
I find that absurdly compromising of peoples information and possibly legally dangerous! Perhaps I'm just paranoid! I just don't see why we should make all this info so easily available to anyone, even if some of it is 'public' knowledge.
I had concerns that the CGI that handles the e-mailing of the form did not allow the 'hiding' of the e-mail addresses in the HTML. My only 'safety' is the hope that the bots don't look for the "@" character too much and that they probably won't recognize "hidMAIL_TO" as the same as "mailto".
Jim C.