<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Kommentare zu: About obfuscating email addresses</title>
	<atom:link href="http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/</link>
	<description>From the land of wobbly windows</description>
	<lastBuildDate>Tue, 07 Feb 2012 07:32:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>Von: peterix</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6218</link>
		<dc:creator>peterix</dc:creator>
		<pubDate>Wed, 07 Oct 2009 21:18:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6218</guid>
		<description>Heh. Obfuscating e-mails is totally wrong. You lose the usability of clickable mail links and the bots get it anyway.

And then you get spam no matter what you do. A better spam filter is the answer.</description>
		<content:encoded><![CDATA[<p>Heh. Obfuscating e-mails is totally wrong. You lose the usability of clickable mail links and the bots get it anyway.</p>
<p>And then you get spam no matter what you do. A better spam filter is the answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Martin&#8217;s Blog&#187; Blogarchiv &#187; How to secure your email address correctly on the web</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6187</link>
		<dc:creator>Martin&#8217;s Blog&#187; Blogarchiv &#187; How to secure your email address correctly on the web</dc:creator>
		<pubDate>Wed, 07 Oct 2009 09:11:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6187</guid>
		<description>[...] is a follow-up post to my yesterdays post that obfuscating an email address does not work and is useless. Many comments on the blog post [...]</description>
		<content:encoded><![CDATA[<p>[...] is a follow-up post to my yesterdays post that obfuscating an email address does not work and is useless. Many comments on the blog post [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Malte Stretz</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6184</link>
		<dc:creator>Malte Stretz</dc:creator>
		<pubDate>Wed, 07 Oct 2009 08:51:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6184</guid>
		<description>@Martin: The data is still valid and obfuscation still works, exactly for the reasons @Steve wrote. I run a bunch of spam traps which contain both obfuscated and unobfuscated addresses. The latter hardly get any spam.

One reason is that you can&#039;t just run a RE over the whole net and recognize all subtle ways to find mail addresses.  Your Bot also can&#039;t really execute all JavaScript it finds.  Well, it could, but why should a harvester do so when he&#039;s got enough addresses without doing so.  Maybe one day this approach will be broken but until now it works fine (except for the people having to correct the addresses manually but that&#039;s not really much work).

Anyway, what I wanted to write was a reply to @Keopa: KMail 1.9 already had such a feature, I think its gone in KDE4 (can&#039;t try currently):  You could insert an address in the format foo at example dot com into the recipient field and it Just Worked :)</description>
		<content:encoded><![CDATA[<p>@Martin: The data is still valid and obfuscation still works, exactly for the reasons @Steve wrote. I run a bunch of spam traps which contain both obfuscated and unobfuscated addresses. The latter hardly get any spam.</p>
<p>One reason is that you can&#8217;t just run a RE over the whole net and recognize all subtle ways to find mail addresses.  Your Bot also can&#8217;t really execute all JavaScript it finds.  Well, it could, but why should a harvester do so when he&#8217;s got enough addresses without doing so.  Maybe one day this approach will be broken but until now it works fine (except for the people having to correct the addresses manually but that&#8217;s not really much work).</p>
<p>Anyway, what I wanted to write was a reply to @Keopa: KMail 1.9 already had such a feature, I think its gone in KDE4 (can&#8217;t try currently):  You could insert an address in the format foo at example dot com into the recipient field and it Just Worked <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Peter Grasch</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6178</link>
		<dc:creator>Peter Grasch</dc:creator>
		<pubDate>Wed, 07 Oct 2009 07:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6178</guid>
		<description>I still think that obfuscating is a good idea when e.g. posting in technical forums. I have never seen anyone stumped by something like:
&quot;Contact me at grasch ate simon-listens ° org&quot; (which is what I use quite often and I get no spam to that address at all.

And if someone is too lazy to edit the e-Mail address and start the mail program manually instead of clicking on a link I most likely don&#039;t want to know what he had to say anyways :).

However, I agree that obfuscation is no solution when e.g. dealing with customers. However, as most non-tech users browse with javascript on, I use a javascript to print the rot13 encoded e-Mail address and provide a noscript alternative which is obfuscated. That way even the hardcore links-users can see an e-Mail address and spam bots are having a hard enough time to (apparently) loose interest.

Greetings,
Peter</description>
		<content:encoded><![CDATA[<p>I still think that obfuscating is a good idea when e.g. posting in technical forums. I have never seen anyone stumped by something like:<br />
&#8220;Contact me at grasch ate simon-listens ° org&#8221; (which is what I use quite often and I get no spam to that address at all.</p>
<p>And if someone is too lazy to edit the e-Mail address and start the mail program manually instead of clicking on a link I most likely don&#8217;t want to know what he had to say anyways <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>However, I agree that obfuscation is no solution when e.g. dealing with customers. However, as most non-tech users browse with javascript on, I use a javascript to print the rot13 encoded e-Mail address and provide a noscript alternative which is obfuscated. That way even the hardcore links-users can see an e-Mail address and spam bots are having a hard enough time to (apparently) loose interest.</p>
<p>Greetings,<br />
Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Martin</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6173</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Wed, 07 Oct 2009 06:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6173</guid>
		<description>@Peter: sorry the data is more than two years old. I would not count on it being still valid.

@Yawar: yes like reCAPTCHA. I just looked at the site and it seems to have some accessibility problems and it uses a kind of already broken CAPTCHA.</description>
		<content:encoded><![CDATA[<p>@Peter: sorry the data is more than two years old. I would not count on it being still valid.</p>
<p>@Yawar: yes like reCAPTCHA. I just looked at the site and it seems to have some accessibility problems and it uses a kind of already broken CAPTCHA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Peter</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6167</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 07 Oct 2009 00:06:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6167</guid>
		<description>The point you start to be wrong is when you say &quot;I assume that the bots...&quot;  Just have a look at what an empirical investigation on this problem results in:

http://koeln.ccc.de/schnucki/
http://www.0x11.net/schnucki/

Cheers, Peter</description>
		<content:encoded><![CDATA[<p>The point you start to be wrong is when you say &#8220;I assume that the bots&#8230;&#8221;  Just have a look at what an empirical investigation on this problem results in:</p>
<p><a href="http://koeln.ccc.de/schnucki/" rel="nofollow">http://koeln.ccc.de/schnucki/</a><br />
<a href="http://www.0x11.net/schnucki/" rel="nofollow">http://www.0&#215;11.net/schnucki/</a></p>
<p>Cheers, Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Yawar</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6165</link>
		<dc:creator>Yawar</dc:creator>
		<pubDate>Tue, 06 Oct 2009 23:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6165</guid>
		<description>I came across this site recently: http://scr.im/

It&#039;s like a URL-shortener for email addresses, with the added benefit of CAPTCHA protection for the address. For example here&#039;s my address: http://scr.im/yawar</description>
		<content:encoded><![CDATA[<p>I came across this site recently: <a href="http://scr.im/" rel="nofollow">http://scr.im/</a></p>
<p>It&#8217;s like a URL-shortener for email addresses, with the added benefit of CAPTCHA protection for the address. For example here&#8217;s my address: <a href="http://scr.im/yawar" rel="nofollow">http://scr.im/yawar</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Timm</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6152</link>
		<dc:creator>Timm</dc:creator>
		<pubDate>Tue, 06 Oct 2009 18:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6152</guid>
		<description>@Martin: Full Ack! The worst thing about it is the time I have to invest in order to &quot;manually&quot; de-obfuscate the adresses. As if we didn&#039;t have a hard enough time fighting the SPAM in our own mailboxes...

BTW, if I were a Spammer, I wouldn&#039;t even go through the trouble of using a bot, let alone programming one. I&#039;d just use one of the semi-public listings already containing the millions of addresses I need.</description>
		<content:encoded><![CDATA[<p>@Martin: Full Ack! The worst thing about it is the time I have to invest in order to &#8220;manually&#8221; de-obfuscate the adresses. As if we didn&#8217;t have a hard enough time fighting the SPAM in our own mailboxes&#8230;</p>
<p>BTW, if I were a Spammer, I wouldn&#8217;t even go through the trouble of using a bot, let alone programming one. I&#8217;d just use one of the semi-public listings already containing the millions of addresses I need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Martin</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6145</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6145</guid>
		<description>@Steve: I would like to see the fact that bots do not execute JS :-) I&#039;d say that&#039;s an assumption. Nevertheless it&#039;s a nice idea, but the same problem as for all such ideas: as soon as all users use this approach it is broken. What we need is a general solution for the problem to not play hide and seek any more.</description>
		<content:encoded><![CDATA[<p>@Steve: I would like to see the fact that bots do not execute JS <img src='http://blog.martin-graesslin.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  I&#8217;d say that&#8217;s an assumption. Nevertheless it&#8217;s a nice idea, but the same problem as for all such ideas: as soon as all users use this approach it is broken. What we need is a general solution for the problem to not play hide and seek any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Steve</title>
		<link>http://blog.martin-graesslin.com/blog/2009/10/about-obfuscating-email-addresses/comment-page-1/#comment-6142</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 06 Oct 2009 16:00:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martin-graesslin.com/blog/?p=361#comment-6142</guid>
		<description>I would say that Thomas McGuire is correct.  It&#039;s low hanging fruit vs not-so-low.  Some obfuscators are quite easy to guess, and are therefore almost as &quot;low&quot;, but in my experience it&#039;s definately better than not obfuscating at all.

I&#039;ve had success with a completely different method.  I use a relatively simple JavaScript routine and inline document.write() calls, and avoid having any recognisable email addresses in the source (and the &#039;@&#039; character doesn&#039;t appear anywhere).

This relies on the fact that bots may read the source (including JS) but don&#039;t actually execute any JavaScript.  The result is a clickable mailto: link, and I haven&#039;t had any more spam to those addresses since doing that.

Of course, once there&#039;s no more low-hanging fruit, the nasty people will reach up higher, or maybe get a ladder.  If that happens, I&#039;ll have to be more creative.

Steve</description>
		<content:encoded><![CDATA[<p>I would say that Thomas McGuire is correct.  It&#8217;s low hanging fruit vs not-so-low.  Some obfuscators are quite easy to guess, and are therefore almost as &#8220;low&#8221;, but in my experience it&#8217;s definately better than not obfuscating at all.</p>
<p>I&#8217;ve had success with a completely different method.  I use a relatively simple JavaScript routine and inline document.write() calls, and avoid having any recognisable email addresses in the source (and the &#8216;@&#8217; character doesn&#8217;t appear anywhere).</p>
<p>This relies on the fact that bots may read the source (including JS) but don&#8217;t actually execute any JavaScript.  The result is a clickable mailto: link, and I haven&#8217;t had any more spam to those addresses since doing that.</p>
<p>Of course, once there&#8217;s no more low-hanging fruit, the nasty people will reach up higher, or maybe get a ladder.  If that happens, I&#8217;ll have to be more creative.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>

