<?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/"
		>
<channel>
	<title>Comments on: We only mail people who sign up!</title>
	<atom:link href="http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:06:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: J.D. Falk</title>
		<link>http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/comment-page-1/#comment-4134</link>
		<dc:creator>J.D. Falk</dc:creator>
		<pubDate>Mon, 12 Apr 2010 16:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1418#comment-4134</guid>
		<description>You&#039;ve seen the old story of Nadine, right?  http://www.honet.com/Nadine/

Many people never even consider that the fake address they&#039;re using might actually belong to a real person.  I&#039;ve pointed this out to friends on occasion, and they were shocked to realize they might be increasing someone else&#039;s spam.  It&#039;s not at all uncommon for that &quot;someone else&quot; to turn a suddenly over-popularized address into a spamtrap, feeding it directly into their anti-spam software.

If you&#039;re particularly concerned about people putting fake addresses into your web forms, give them the option to not include an address at all.  That way, you&#039;re not sending unwanted email.</description>
		<content:encoded><![CDATA[<p>You&#8217;ve seen the old story of Nadine, right?  <a href="http://www.honet.com/Nadine/" rel="nofollow">http://www.honet.com/Nadine/</a></p>
<p>Many people never even consider that the fake address they&#8217;re using might actually belong to a real person.  I&#8217;ve pointed this out to friends on occasion, and they were shocked to realize they might be increasing someone else&#8217;s spam.  It&#8217;s not at all uncommon for that &#8220;someone else&#8221; to turn a suddenly over-popularized address into a spamtrap, feeding it directly into their anti-spam software.</p>
<p>If you&#8217;re particularly concerned about people putting fake addresses into your web forms, give them the option to not include an address at all.  That way, you&#8217;re not sending unwanted email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Levine</title>
		<link>http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/comment-page-1/#comment-4131</link>
		<dc:creator>John Levine</dc:creator>
		<pubDate>Sun, 11 Apr 2010 21:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1418#comment-4131</guid>
		<description>Why is it called a spamtrap? If someone adds bob@bob.com to my mailing list and I
   don’t catch it

Because bob.com didn&#039;t ask you to send him mail, of course. From a recipient&#039;s point of view, they can&#039;t tell whether you&#039;re spamming them because a customer lied when they signed up or because you bought a spam list, and they don&#039;t care. Sleazy marketers have so thoroughly poisoned the well that assuming the worst is correct more often than not. And if customers distrust you enough to lie when they buy stuff, that suggests their opinion matches that of the people you&#039;re spamming.

This may be unfair, but in my experience, the louder that senders complain about unfairness, the cruddier their practices are.</description>
		<content:encoded><![CDATA[<p>Why is it called a spamtrap? If someone adds <a href="mailto:bob@bob.com">bob@bob.com</a> to my mailing list and I<br />
   don’t catch it</p>
<p>Because bob.com didn&#8217;t ask you to send him mail, of course. From a recipient&#8217;s point of view, they can&#8217;t tell whether you&#8217;re spamming them because a customer lied when they signed up or because you bought a spam list, and they don&#8217;t care. Sleazy marketers have so thoroughly poisoned the well that assuming the worst is correct more often than not. And if customers distrust you enough to lie when they buy stuff, that suggests their opinion matches that of the people you&#8217;re spamming.</p>
<p>This may be unfair, but in my experience, the louder that senders complain about unfairness, the cruddier their practices are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: laura</title>
		<link>http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/comment-page-1/#comment-4121</link>
		<dc:creator>laura</dc:creator>
		<pubDate>Fri, 09 Apr 2010 15:22:21 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1418#comment-4121</guid>
		<description>The issue is that many times those addresses don&#039;t go to a non-existent server. Often they go directly to a real server and to a real user.</description>
		<content:encoded><![CDATA[<p>The issue is that many times those addresses don&#8217;t go to a non-existent server. Often they go directly to a real server and to a real user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jordan Dossett</title>
		<link>http://blog.wordtothewise.com/2010/04/we-only-mail-people-who-sign-up/comment-page-1/#comment-4115</link>
		<dc:creator>Jordan Dossett</dc:creator>
		<pubDate>Fri, 09 Apr 2010 04:47:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1418#comment-4115</guid>
		<description>Why is it called a spamtrap?  If someone adds bob@bob.com to my mailing list and I don&#039;t catch it and then I do a send and it hits the non existent server while it is taxing on my end and irritating it does not lessen our send or lessen our ESP credibility or gray or black list any of the other sends... so why a spamtrap?  

I am kind of asking from a bit of a print designer background.  We are going to a big conference and just &quot;rented&quot; the attendee list for a one time snail mail blast.  Cool, no big deal.  Then to my shock I found out the list was riddled with almost 100 &quot;snail mail traps&quot; which are there to see if you mass produce the labels and mail to the list multiple times.

So I just wanted to check with you and ask if I am missing something on this idea of a spamtrap?  For the idea of confirming data entered on forms we are in the process now of changing over so that when someone enters their email (say bob@bob.com) it would confirm that at the least bob.com is a valid email server.  While it won&#039;t fix every problem it should help?

As always, love the reads. 
Jordan</description>
		<content:encoded><![CDATA[<p>Why is it called a spamtrap?  If someone adds <a href="mailto:bob@bob.com">bob@bob.com</a> to my mailing list and I don&#8217;t catch it and then I do a send and it hits the non existent server while it is taxing on my end and irritating it does not lessen our send or lessen our ESP credibility or gray or black list any of the other sends&#8230; so why a spamtrap?  </p>
<p>I am kind of asking from a bit of a print designer background.  We are going to a big conference and just &#8220;rented&#8221; the attendee list for a one time snail mail blast.  Cool, no big deal.  Then to my shock I found out the list was riddled with almost 100 &#8220;snail mail traps&#8221; which are there to see if you mass produce the labels and mail to the list multiple times.</p>
<p>So I just wanted to check with you and ask if I am missing something on this idea of a spamtrap?  For the idea of confirming data entered on forms we are in the process now of changing over so that when someone enters their email (say <a href="mailto:bob@bob.com">bob@bob.com</a>) it would confirm that at the least bob.com is a valid email server.  While it won&#8217;t fix every problem it should help?</p>
<p>As always, love the reads.<br />
Jordan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

