|
email encode good practice???
I am wondering how easy it would be to thwart the email encoding by a bot....
1. A bot crafted to grab anything with the word "mail" in it would grab the encoded value... sendEmail('736F6D656F6E65406578616D706C652E636F6D')
2. Since email.js is easy to download or recreate since it is simply base16 encoding, a spammer could run these encoded values through a second program that mimics email.js to uncover the email.
Is my thought processed flawed?
My three thoughts for protecting against this are:
1. Don't do anything. This is more work than it's worth for a spammer.
2. Redo the sendEmail to use some other encoding and not publish this encoding. Of course if someone discovered my .js file then I am toast again ( very low probability).
3. Create an email page that takes in information from the user and executes server side code to email thus hiding all possibility of a spam bot being able to gather any kind of worthwile information. (What I currently do...)
Thoughts from anyone on my flawed/good ideas would be greatly appreciated...
Kevin |