I'm getting fed up with the programming community's refusal to think like the enemy. Many web applications which have something to do with email (most of them) utilize techniques to obfuscate email addresses. Geeks also do it when they post to public forums thinking that it will protect them from spam. This whole canon of obfuscation is a total joke. Let me give you some examples of what people are doing and why it's dangerous. I say dangerous because a false sense of security is far worse than no security at all.
Movable Type
Movable Type utilizes a technology called spam_protect. It turns user@example.com into user@example.com. Those funny looking strings where the @ sign and . used to be are html encoded versions of the @ and . signs. The idea that this would prove to be anything more than a hiccup for a spammer is ludicrous. I'll just give you an example rule that a spam harvesting robot could use. If you find the string ".com" or ".org" or ".net" in a web page, search backward for the first space and capture that as an email address. Then either interpret the address through an html interpreter or simply do a search and replace for the two strings to turn them into @'s and .'s. I could write this in one line of code, and I can't program worth shit, definitely not well enough to write an efficient spam harvester.
php.net and every geek out there
So you've probably seen this clever technique where the @ sign is replaced with the word at and the . is replaced with the word dot. You'll find this on comments all over slashdot. This way the spam harvester can't merely look for an @ sing or a .com. I'm sorry, but this is never going to work. How often in normal text do you see any of these words being used. Dot, Com, Org, Net. Ok, net is probably common, but "dot". Looking for ".com" and looking for " dot com" seem about the same to me. Again, a harvester would bypass this trick with a single line of code.
Mailman and many other programs
The reason that this has come to my attention is two fold. One, I recently disabled the display of "obfuscated email addresses" through movable type, since a child could write around the obfuscation. I've just installed mailman for our mailing lists (a great program mind you), and it uses just as lame a system. This time it's combining the at for @ and dot for . with a mailto: tag with the full email address. This approach is the worst of all of them. When a human visits a page with email addresses they display as user at example dot com, but when a harvester views them (at an html level, not a viewable level) it has the full email address, user@example.com, right there with a mailto: tag in case it wasn't obvious enough that it was an email address.
I don't have a killer app solution here, but we need to get rid of this placebo shit and accept that we don't have an answer and that we're vulnerable. With the placebo it will just take that much longer for a real solution to be found and implemented.

So Jack just called me from ebay in San Jose. They just had a strong earthquake (6.5). 
