<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Word to the Wise &#187; TWSD</title>
	<atom:link href="http://blog.wordtothewise.com/tag/twsd/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.wordtothewise.com</link>
	<description>Email, Delivery, Spam and more</description>
	<lastBuildDate>Tue, 07 Feb 2012 23:24:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>What not to do</title>
		<link>http://blog.wordtothewise.com/2012/02/what-not-to-do/</link>
		<comments>http://blog.wordtothewise.com/2012/02/what-not-to-do/#comments</comments>
		<pubDate>Wed, 01 Feb 2012 20:48:56 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[TWSD]]></category>
		<category><![CDATA[unsubscribe]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=3775</guid>
		<description><![CDATA[There&#8217;s a London concert promoter that&#8217;s been spamming our old sales address for 5 or 6 years now. I&#8217;ve sent in complaints, I&#8217;ve tried to unsubscribe, and the mail still keeps coming. They managed to get through my filters, again, this morning. In a fit of frustration I tweeted about how frustrated I was that [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s a London concert promoter that&#8217;s been spamming our old sales address for 5 or 6 years now. I&#8217;ve sent in complaints, I&#8217;ve tried to unsubscribe, and the mail still keeps coming. They managed to get through my filters, again, this morning. In a fit of frustration I tweeted about how frustrated I was that they would not stop spamming me.</p>
<p>Well, that got someone&#8217;s attention. The person managing their twitter account tweeted at me with an email address and a suggestion to send him my address so he could take care of it. I sent the mail as asked and even got a reply.</p>
<p>Unfortunately, the reply was &#8220;I clicked the unsubscribe link at the bottom of the message for you.&#8221;</p>
<p>I dunno, maybe his mouse is a magic mouse and, somehow, the click from that magic mouse will be more effective than a click from my not-magic mouse. I&#8217;m not holding out much hope, though. I have no doubt that my sales address will keep getting invited to raves in London long after I retire.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2012/02/what-not-to-do/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Spamming ESPs</title>
		<link>http://blog.wordtothewise.com/2011/12/spamming-esps/</link>
		<comments>http://blog.wordtothewise.com/2011/12/spamming-esps/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 18:36:39 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Industry]]></category>
		<category><![CDATA[ESPs]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=3691</guid>
		<description><![CDATA[In my mailbox there is a definite uptick in spam from ESPs advertising their services. Today&#8217;s email was from a company that has the following in their anti-spam policy: To send email to anyone using [ESP name], you must have clearly obtained their permission. We consider qualifying methods for obtaining permission are as follows: An [...]]]></description>
			<content:encoded><![CDATA[<p>In my mailbox there is a definite uptick in spam from ESPs advertising their services.</p>
<p>Today&#8217;s email was from a company that has the following in their anti-spam policy:</p>
<blockquote><p>To send email to anyone using [ESP name], you must have clearly obtained their permission. We consider qualifying methods for obtaining permission are as follows:</p>
<ul>
<li> An email newsletter subscription form on your web site.</li>
<li> An opt-in checkbox within a form. This checkbox must not be checked by default, the person completing the form must willingly select the checkbox to indicate they want to hear from you.</li>
<li> If someone completes an offline form like a survey or enters a competition, you can only contact them if it was explained to them that you would be contacting them by email AND they ticked a box indicating they would like you to contact them.</li>
<li> Customers who have purchased from you within the last 2 years.</li>
<li> If someone gives you their business card and you have explicitly asked for permission to add them to your list, you can contact them.</li>
</ul>
</blockquote>
<p>Apparently this only counts for customers, as I have never heard of this company before receiving the spam.</p>
<p>I&#8217;m sure they&#8217;ll argue it wasn&#8217;t spam, it was a holiday greeting, and in fact everything above the fold was wishing me a Happy Christmas. But, down at the bottom was a message.</p>
<blockquote><p>PS: Still not sorted your customers Christmas cards out?</p>
<p>You could send every one of them a fun ecard in no time at all… just click here to contact [ESP] today.</p></blockquote>
<p>I don&#8217;t know anyone at this ESP. They hit an address that was only ever published on a website and was removed from use more than 5 years ago. It was never entered into any forms. I have never purchased from them.</p>
<p>It&#8217;s so blatantly spam, couched in a &#8220;HOLIDAY GREETING!&#8221; It&#8217;s not the first one I&#8217;ve gotten. It&#8217;s not even the first one I&#8217;ve gotten this year.</p>
<p>EDIT: <a href="http://blog.wordtothewise.com/2011/12/spamming-esps-the-followup/">Make sure to read the followup</a></p>
<p>How can this ESP claim with a straight face that they expect customers to only send opt-in mail? How can they claim they force customers to follow good practices when they don&#8217;t? This message even violates CAN SPAM &#8211; failing to have a postal address included.</p>
<p>At least I know what to answer if any client ever asks me about this particular ESP and what I know about them. &#8220;Well, they are spammers themselves.&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2011/12/spamming-esps/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Does it look like you&#8217;re spamming?</title>
		<link>http://blog.wordtothewise.com/2011/11/does-it-look-like-youre-spamming/</link>
		<comments>http://blog.wordtothewise.com/2011/11/does-it-look-like-youre-spamming/#comments</comments>
		<pubDate>Tue, 08 Nov 2011 17:06:01 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=3578</guid>
		<description><![CDATA[There are lots of terribly complicated rules in email marketing and retention. &#8220;Only send email to people who opted-in&#8221;, &#8220;Never use a pink background&#8221;[1], &#8220;Have a working unsubscription link&#8221;, &#8220;Don&#8217;t put FREE in the subject line&#8221;[1]. Another one should be &#8220;How does what you&#8217;re doing look to a typical recipient?&#8221;. I&#8217;ve received several pieces of [...]]]></description>
			<content:encoded><![CDATA[<p>There are lots of terribly complicated rules in email marketing and retention. &#8220;Only send email to people who opted-in&#8221;, &#8220;Never use a pink background&#8221;[1], &#8220;Have a working unsubscription link&#8221;, &#8220;Don&#8217;t put FREE in the subject line&#8221;[1].</p>
<p>Another one should be &#8220;How does what you&#8217;re doing look to a typical recipient?&#8221;.</p>
<p>I&#8217;ve received several pieces of spam recently from senders who were ticking quite a lot of the &#8220;email best practices&#8221; checkboxes, but who completely blew it by not looking at it from the recipients point of view. The mistakes they&#8217;ve made, and the things to learn from them, and much the same, so I&#8217;ll just give one example.</p>
<p><strong>&#8220;Likes Music&#8221; is not the same as &#8220;Likes Groupon Clones&#8221;</strong></p>
<p>I&#8217;ve been a subscriber to our local radio station&#8217;s mailing list for years &#8211; promos KFOG is running, local gigs, that sort of thing, all in a newsletter sort of format. They recently sent out an ad for a Groupon clone called &#8220;SweetJack&#8221; &#8211; on it&#8217;s own, not as part of a newsletter. I&#8217;m not interested, and I think it&#8217;s a fairly poor pitch and won&#8217;t work well for their demographic, but fair enough. A couple of weeks later I start getting spam from SweetJack, thanking me for signing up &#8211; to the tagged email address I&#8217;d only given to KFOG. And no mention of KFOG at all.</p>
<p>Most recipients are just going to see this as spam out of the blue from SweetJack, and hammer on the &#8220;This is Spam&#8221; button until it goes away. That&#8217;s dreadful for SweetJack&#8217;s reputation, and is going to hurt their delivery.</p>
<p>Recipients paying more attention are going to notice that the first they heard of SweetJack was an out of the ordinary promo by KFOG, and then they start getting spam from SweetJack. They&#8217;re likely to assume that KFOG sold their email addresses to SweetJack &#8211; and that they&#8217;re sending their spam to an email address that only KFOG has in my case confirms that. That&#8217;s going to be dreadful for SweetJack&#8217;s reputation <em>and</em> going to damage the relationship between KFOG and their existing subscribers. A dreadful idea.</p>
<p>Digging down deeper, it seems that while KFOG being bought out by media behemoth Cumulus Media a few years back didn&#8217;t damage their on-air content, it did change the amount of respect they have for their subscribers. SweetJack is a new Groupon clone started by Cumulus Media. They did have legitimate access to the KFOG mailing lists, sorta. It&#8217;s probably not an AUP or privacy violation. It&#8217;s just the sort of thing an eager marketing guy at the corporate owners would think was a great idea, to leverage the value of their existing subscribers.</p>
<p>But it would have been a pretty bad idea had they carried it out perfectly, with clear messaging and transparency to the recipients. And they blew their one opportunity to do it well, and I&#8217;m betting that most of the recipients have SweetJack categorized as &#8220;spammers&#8221;, both mentally and in their mail clients.</p>
<p>1. Not a real email marketing rule.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2011/11/does-it-look-like-youre-spamming/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Not lazy, just annoyed</title>
		<link>http://blog.wordtothewise.com/2011/10/not-lazy-just-annoyed/</link>
		<comments>http://blog.wordtothewise.com/2011/10/not-lazy-just-annoyed/#comments</comments>
		<pubDate>Tue, 18 Oct 2011 00:49:28 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[ISPs]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=3515</guid>
		<description><![CDATA[I don&#8217;t usually send in spam reports, but I submitted a couple in the last few weeks. Somehow an address of mine is on a bunch of rave / club lists in London. You want to know what is happening at London clubs this week? It&#8217;s all there in my spam folder. This mail finally [...]]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t usually send in spam reports, but I submitted a couple in the last few weeks. Somehow an address of mine is on a bunch of rave / club lists in London. You want to know what is happening at London clubs this week? It&#8217;s all there in my spam folder. </p>
<p>This mail finally hit my annoyance threshold, so I&#8217;ve been submitting reports and complaints to the senders the last few weeks. The mail, with full headers, goes with an explanation that the address that received it was harvested off a website more than 5 years ago and never opted in to receive any mail. </p>
<p>One of the ISPs I sent the report to has a web form where the complainant and the customer can see the report and both can comment on it. The customer replied to my complaint on it. </p>
<blockquote><p>Email compliant with best practice, lazy user. Have clicked the unsubscribe link for them</p></blockquote>
<p>As you can imagine this annoyed me. I mean, I&#8217;m really happy they&#8217;re going to stop sending me spam advertising clubs a 12 hour plane flight away, but they could do that without claiming that I was a lazy user. </p>
<p>I replied to the complaint. </p>
<blockquote><p>Despite what your customer says I am not a &#8220;lazy user.&#8221; The email was sent to an address harvested off a website more than 5 years ago. I never signed up for it, I never asked for it.</p>
<p>Your customer is a spammer.
</p></blockquote>
<p>To the ISP&#8217;s credit, they did take the complaint a lot more seriously than their customer. </p>
<blockquote><p>Network access to server has been suspended</p></blockquote>
<p>Boy, did that change the customer&#8217;s tune.</p>
<blockquote><p>I will speak again to my customer and seek clarification from them as to the source of my email. My comment was in relation to email content such as headers and unsubscribe details</p></blockquote>
<p>While I know it&#8217;s tempting to treat every complaint as a &#8220;lazy user&#8221; who just won&#8217;t unsubscribe, it can be a very bad idea. It&#8217;s not that I&#8217;m too lazy to hit the unsubscribe button, it&#8217;s that the sender is clearly a spammer, either buying or harvesting address lists. Why should I trust that spammer to actually honor an unsubscribe? I don&#8217;t. Thus, I send in a complaint. </p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2011/10/not-lazy-just-annoyed/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>TWSD: I can haz ethix marketing</title>
		<link>http://blog.wordtothewise.com/2011/07/twsd-i-can-has-ethix-marketing/</link>
		<comments>http://blog.wordtothewise.com/2011/07/twsd-i-can-has-ethix-marketing/#comments</comments>
		<pubDate>Thu, 14 Jul 2011 22:27:10 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Asides]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=3178</guid>
		<description><![CDATA[I&#8217;m getting slammed by spam advertising URLs at http://perfectdeliveries.com/ from Ethix Marketing LLC 711 S. Carson Street Suite 4 Carson City, Nevada 89701 The kicker? They&#8217;re violating CAN SPAM while they&#8217;re doing it. Seriously, sending mail out through open relays and proxies with forged From: addresses is a violation of CAN SPAM. And they&#8217;re spamming [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m getting slammed by spam advertising URLs at http://perfectdeliveries.com/ from</p>
<p>Ethix Marketing LLC<br />
711 S. Carson Street Suite 4<br />
Carson City, Nevada 89701</p>
<p>The kicker? They&#8217;re violating CAN SPAM while they&#8217;re doing it. Seriously, sending mail out through open relays and proxies with forged From: addresses is a violation of CAN SPAM. And they&#8217;re spamming for ambulance chasers.</p>
<p>Spammers, eh?</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2011/07/twsd-i-can-has-ethix-marketing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>TWSD: lie about the source of address</title>
		<link>http://blog.wordtothewise.com/2010/12/twsd-lie-about-the-source-of-address/</link>
		<comments>http://blog.wordtothewise.com/2010/12/twsd-lie-about-the-source-of-address/#comments</comments>
		<pubDate>Tue, 14 Dec 2010 00:03:37 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[legitimate email marketer]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=2253</guid>
		<description><![CDATA[A few months ago I got email from Staff of Norman Rockwell Museum of Vermont, to an addresses scraped off one of my websites. At the bottom it says: You are receiving this email because you have ordered from us, or emailed us in the past. We take your privacy seriously,and promise never to give [...]]]></description>
			<content:encoded><![CDATA[<p>A few months ago I got email from Staff of Norman Rockwell Museum of Vermont, to an addresses scraped off one of my websites. At the bottom it says:</p>
<blockquote><p>You are receiving this email because you have ordered from us, or emailed us in the past. We take your privacy seriously,and promise never to give your personal information to any other company.</p></blockquote>
<p>Most people probably wouldn&#8217;t know that for the lie it is, as they don&#8217;t have special addresses on their websites. But in this case, I know it is a lie. I know I have never ordered from the Norman Rockwell Museum of Vermont. I know that laura-web is an address up on a website. It&#8217;s not used to send mail. It&#8217;s not used to purchase anything.</p>
<p>&#8220;You opted in to receive mail&#8221; is one of the oldest spammer lies out there. I always discourage clients from using wording like this. If the client doesn&#8217;t have enough information to fill in the blanks &#8220;you ordered from us in October&#8221; or &#8220;you signed up in June&#8221; then there isn&#8217;t really any reason to add it in. If the user doesn&#8217;t remember ordering from them, then they&#8217;re going to look like a spammer.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/12/twsd-lie-about-the-source-of-address/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>TWSD: SEO Spamming</title>
		<link>http://blog.wordtothewise.com/2010/11/twsd-seo-spamming/</link>
		<comments>http://blog.wordtothewise.com/2010/11/twsd-seo-spamming/#comments</comments>
		<pubDate>Fri, 19 Nov 2010 19:20:49 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Industry]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=2276</guid>
		<description><![CDATA[It&#8217;s no secret that I get a lot of spam. It&#8217;s no secret that some catches my eye enough to actually write about it here. Today&#8217;s spam is an email that actually made me laugh, though. Somewhere, some gardening site paid a lot of money for search engine optimization and got ripped off. We own [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s no secret that I get a lot of spam. It&#8217;s no secret that some catches my eye enough to actually write about it here. Today&#8217;s spam is an email that actually made me laugh, though. Somewhere, some gardening site paid a lot of money for search engine optimization and got ripped off.</p>
<p>We own the site samspade.org. It&#8217;s down now, victim of a major hardware crash, but this was a site with a number of tools for tracking spammers. This morning, I got email about SamSpade.</p>
<blockquote><p>My name is Tina from &lt;some random gardening site&gt;.</p>
<p>I am the SEO and marketing manager over here.</p>
<p>As you probably know, having backlinks from related sites helps increase your rankings in Google.</p>
<p>Well, I was just doing a search on Google.com for &#8220;Samspade&#8221; and your site popped up! This is you, right?</p>
<p>http://www.wordtothewise.com</p>
<p>Well, check it out&#8230;</p>
<p>Since we both target a similar audience, Google will give us BOTH extra love if we each place a simple link to one another.</p>
<p>Not a lot of work and plenty of benefit to both of us.</p>
<p>I know you probably get requests like this all the time, I know I sure do. So, to stand out, I went above and beyond by setting up a customized page telling my site visitors about your great site! <img src='http://blog.wordtothewise.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p></blockquote>
<p>Poor Tina. Her SEO optimization software mistakenly keyed off of the &#8220;spade&#8221; in our domain name and decided that we sold weeding tools. Not so much. Of course, the company that &#8220;Tina&#8221; bought her software from is well versed in spamming, both SEO and email. The domains are all obfuscated behind whois protection. The domain the mail came from doesn&#8217;t exist. They&#8217;re using gmail as a contact address. They&#8217;re hosted on LiquidWeb.</p>
<p>Maybe it&#8217;s not poor Tina after all. Maybe this isn&#8217;t just some poor person trying to get a leg up. Maybe it really is just a major spammer looking to spam their new website. Poorly. And with no finesse.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/11/twsd-seo-spamming/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Would you buy a used car from that guy?</title>
		<link>http://blog.wordtothewise.com/2010/10/would-you-buy-a-used-car-from-that-guy/</link>
		<comments>http://blog.wordtothewise.com/2010/10/would-you-buy-a-used-car-from-that-guy/#comments</comments>
		<pubDate>Wed, 20 Oct 2010 15:05:34 +0000</pubDate>
		<dc:creator>laura</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Confirmed (double) opt-in]]></category>
		<category><![CDATA[data]]></category>
		<category><![CDATA[data hygiene]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=2137</guid>
		<description><![CDATA[There are dozens of people and companies standing up and offering suggestions on best practices in email marketing. Unfortunately, many of those companies don&#8217;t actually practice what they preach in managing their own email accounts. I got email today to an old work email address of mine from Strongmail. To be fair it was a [...]]]></description>
			<content:encoded><![CDATA[<p>There are dozens of people and companies standing up and offering suggestions on best practices in email marketing. Unfortunately, many of those companies don&#8217;t actually practice what they preach in managing their own email accounts.</p>
<p>I got email today to an old work email address of mine from Strongmail. To be fair it was a technically correct email. Everything one would expect from a company handling large volumes of emails.  It&#8217;s clear that time and energy was put into the technical setup of the send. If only they had put even half that effort into deciding who to send the email to. Sadly, they didn&#8217;t.</p>
<p>My first thought, upon receiving the mail, was that some new, eager employee bought a very old and crufty list somewhere. Because Strongmail has a reputation for being responsible mailers, I sent them a copy of the email to abuse@. I figured they&#8217;d want to know that they had a new sales / marketing person who was doing some bad stuff.</p>
<p>I know how frustrating handling abuse@ can be, so I try to be short and sweet in my complaints. For this one, I simply said, &#8220;Someone at Strongmail has appended, harvested or otherwise acquired an old email address of mine. This has been added to your mailing list and I&#8217;m now receiving spam from you. &#8221;</p>
<p>They respond with an email that starts with:</p>
<p>&#8220;Thank you for your thoughtful response to our opt-in request. On occasion, we provide members of our database with the opportunity to opt-in to receive email marketing communications from us.&#8221;</p>
<p>Wait. What? Members of our database? How did this address get into your database?</p>
<p>&#8220;I can&#8217;t be sure from our records but it looks like someone from StrongMail reached out to you several years ago.  It&#8217;s helpful that you let us know to unsubscribe you.  Thank you again.&#8221;</p>
<p>There you have it. According to the person answering email at abuse@ Strongmail they sent me a message because they had sent mail to me in the past. Is that really what you did? Send mail to very old email addresses because someone, at some point in the past, sent mail to that address? And you don&#8217;t know when, don&#8217;t know where the address came from, don&#8217;t know how it was acquired, but decided to reach out to me?</p>
<p>How many bad practices can you mix into a single send, Strongmail? Sending mail to addresses where you don&#8217;t know how you got them? Sending mail to addresses that you got at least 6 years ago? Sending mail to addresses that were never opted-in to any of your mail? And when people point out, gently and subtly, that maybe this is a bad idea, you just add them to your global suppression list?</p>
<p>Oh. Wait. I know what you&#8217;re going to tell me. All of your bad practices don&#8217;t count because this was an &#8216;opt-in&#8217; request. People who didn&#8217;t want the mail didn&#8217;t have to do anything, therefore there is no reason not to spam them! They ignore it and they are dropped from your list. Except it doesn&#8217;t work that way. Double opt-in requests to someone has asked to be subscribed or is an active customer or prospect is one thing. Requests sent to addresses of unknown provenance are still spam.</p>
<p>Just for the record, I have a good idea of where they got my address. Many years ago Strongmail approached Word to the Wise to explore a potential partnership. We would work with and through Strongmail to provide delivery consulting and best practices advice for their customers. As part of this process we did exchange business cards with a number of Strongmail employees. I suspect those cards were left in a desk when the employees moved on. Whoever got that desk, or cleaned it out, found  those cards and added them to the &#8216;member database.&#8217;</p>
<p>But wait! It gets even better. Strongmail was sending me this mail, so that they could get permission to send me email about <em>Email and Social Media Marketing Best Practices</em>. I&#8217;m almost tempted to sign up to provide me unending blog fodder for my new series entitled &#8220;Don&#8217;t do this!&#8221;</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/10/would-you-buy-a-used-car-from-that-guy/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Content based filtering</title>
		<link>http://blog.wordtothewise.com/2010/09/content-based-filtering/</link>
		<comments>http://blog.wordtothewise.com/2010/09/content-based-filtering/#comments</comments>
		<pubDate>Tue, 07 Sep 2010 21:54:53 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Delivery Improvement]]></category>
		<category><![CDATA[Blocking]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1933</guid>
		<description><![CDATA[A spam filter looks at many things when it&#8217;s deciding whether or not to deliver a message to the recipients inbox, usually divided into two broad categories &#8211; the behaviour of the sender and the content of the message. When we talk about sender behaviour we&#8217;ll often dive headfirst into the technical details of how [...]]]></description>
			<content:encoded><![CDATA[<p>A spam filter looks at many things when it&#8217;s deciding whether or not to deliver a message to the recipients inbox, usually divided into two broad categories &#8211; the behaviour of the sender and the content of the message.</p>
<p>When we talk about sender behaviour we&#8217;ll often dive headfirst into the technical details of how that&#8217;s monitored and tracked &#8211; history of mail from the same IP address, SPF records, good reverse DNS, send rates and ramping, polite SMTP level behaviour, DKIM and domain-based reputation and so on. If all of those are OK and the mail still doesn&#8217;t get delivered then you might throw up your hands, fall back on &#8220;it&#8217;s content-based filtering&#8221; and not leave it at that.</p>
<p>There&#8217;s just as much detail and scope for diagnosis in content-based filtering, though, it&#8217;s just a bit more complex, so some delivery folks tend to gloss over it. If you&#8217;re sending mail that people want to receive, you&#8217;re sure you&#8217;re sending the mail technically correctly and you have a decent reputation as a sender then it&#8217;s time to look at the content.</p>
<p>You want your mail to look just like wanted mail from reputable, competent senders and to look different to unwanted mail, viruses, phishing emails, botnet spoor and so on. And not just to mechanical spam filters &#8211; if a postmaster looks at your email, you want it to look clean, honest and competently put together to them too.</p>
<p>Some of the distinctive content differences between wanted and unwanted email are due to the content as written by the sender, some of them are due to senders of unwanted email trying to hide their identity or their content, but many of them are due to the different quality software used to send each sort of mail. Mail clients used by individuals, and content composition software used by high quality ESPs tends to be well written and complies with both the email and MIME RFCs, and the unwritten best common practices for email composition. The software used by spammers, botnets, viruses and low quality ESPs tends not to do so well.</p>
<p>Here&#8217;s a (partial) list of some of the things to consider:</p>
<p><span id="more-1933"></span></p>
<p><strong>MIME Structure</strong></p>
<p>Good email tends to be either plain text or a multipart mail consisting of two versions of the same message, one in HTML and one in plain text.</p>
<p>Bad email often doesn&#8217;t have the plain text part. Either it&#8217;s missing altogether, or it&#8217;s completely different (much shorter) content than the HTML part.</p>
<p><strong>Text Encoding</strong></p>
<p>Bad email often tries to hide it&#8217;s content from spam filters. One common way of doing this is to use base64 encoding for text where quoted-printable encoding would be appropriate.</p>
<p>Lazy software developers sometimes base64 encode everything, as it&#8217;s less work than deciding which encoding is appropriate for a message part. Doing that looks dishonest or incompetent to filters and postmasters.</p>
<p><strong>Images</strong></p>
<p>Another way bad email tries to hide it&#8217;s content is by misuse of images. The most obvious example of this is mail that consists of just a single huge image &#8211; sometimes that&#8217;s just because it&#8217;s easier for the graphic designer to do that way, but more often it&#8217;s a spammer trying to hide their content from filters. Either way, it&#8217;s much less likely to be delivered.</p>
<p>Including CAN-SPAM required boilerplate (such as the postal address) purely as an image is another thing that&#8217;s distinctive to bad email. Bad email hides the contact address in that way so as to avoid people being able to search based on it to track their behaviour across brands and shell companies, and to stop people using it to key targeted spam filters on. Good email doesn&#8217;t need to do that.</p>
<p><strong>HTML Structure</strong></p>
<p>If your email is completely unreadable with images not displayed, it&#8217;s not going to be a good marketing piece in the (common) case that images aren&#8217;t shown. Including appropriate ALT text for each image not only makes it look better to recipients when images are turned off, it also makes it look more legitimate to postmasters with ticketing systems that don&#8217;t display images, or only show the raw HTML. It sometimes makes spam filters happier too.</p>
<p>That&#8217;s just one example of sending &#8220;good&#8221; html.</p>
<p><strong>Phishy URLs</strong></p>
<p>Bad email sent by phishers often includes links that look like &lt;a href=&#8221;http://phisher.ru/&#8221;&gt;bank.com&lt;/a&gt;, where the message is trying to look like legitimate email from bank.com, but it&#8217;s sending readers to phisher.ru instead. &lt;a href=&#8221;http://bank.com.whatever.phisher.ru/&#8221;&gt;bank.com&lt;/a&gt; is an even more obvious attempt to defraud the recipient.</p>
<p>Otherwise good email sent by naive ESPs often includes links that look like &lt;a href=&#8221;http://click.esp.com?trackdata=xxxx&amp;target=bank.com/&#8221;&gt;bank.com&lt;/a&gt;. To a spam filter, that looks much the same as a typical phishing URL, and the delivery is not going to go well.</p>
<p><strong>Bad Phrasing or Appearance</strong></p>
<p>Even if 100% of your recipients desperately wait for every issue of your newsletter there are some phrases that will cause you more problems than others. &#8220;Looking spammy&#8221; is one of the worst things for your email if you need to discuss a delivery issue with a postmaster or a filter vendor &#8211; if it &#8220;looks like spam&#8221; they&#8217;re much less likely to believe it&#8217;s really wanted by recipients.</p>
<p>If your newsletter is about &#8220;Moustache Rides&#8221; (real example, I&#8217;m not making this up) then you might not be able to fix the phrasing, but you should try and make the rest of the newsletter look professionally put together, as much as you can anyway.</p>
<p><strong>URL Reputation</strong></p>
<p>If two emails received &#8220;look similar&#8221; and the recipient complained about the first one, it&#8217;s likely the second one will be unwanted too. But mechanically detecting similar content is complex and expensive to do, so a common trick is to &#8220;fingerprint&#8221; each email by looking for distinctive features in it, and considering messages that share a fingerprint to be similar.</p>
<p>One of the simpler fingerprints to use is the URLs used in links in the mail, more specifically the hostnames of the links. If someone is sending bad email and you send email using the same URLs or hostnames, it&#8217;s likely to be treated poorly.</p>
<p><strong>Fiddly Trivia</strong></p>
<p>There are lots of other fiddly little things that spam filters key on too. You shouldn&#8217;t obsess about them too much, but it&#8217;s worth being aware of the sort of things that can make a difference. SpamAssassin <a href="http://spamassassin.apache.org/tests_3_3_x.html" target="_blank">publish some of the rules they use</a>. If you look at the rules, look at the scores too &#8211; a rule with a score of 0.001 isn&#8217;t very relevant.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/09/content-based-filtering/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tagged Email Addresses</title>
		<link>http://blog.wordtothewise.com/2010/07/tagged-email-addresses/</link>
		<comments>http://blog.wordtothewise.com/2010/07/tagged-email-addresses/#comments</comments>
		<pubDate>Mon, 12 Jul 2010 23:19:30 +0000</pubDate>
		<dc:creator>steve</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Industry]]></category>
		<category><![CDATA[buying leads]]></category>
		<category><![CDATA[buying lists]]></category>
		<category><![CDATA[tagged]]></category>
		<category><![CDATA[TWSD]]></category>

		<guid isPermaLink="false">http://blog.wordtothewise.com/?p=1718</guid>
		<description><![CDATA[A tagged email address is any email address that provides some additional information to the recipient when they receive email sent to that address &#8211; typically something about who they originally gave that email address to or what the email address was intended to be used for. As a very simple example, someone may have [...]]]></description>
			<content:encoded><![CDATA[<p>A tagged email address is any email address that provides some additional information to the recipient when they receive email sent to that address &#8211; typically something about who they originally gave that email address to or what the email address was intended to be used for.</p>
<p>As a very simple example, someone may have a &#8220;real&#8221; email address provided by their ISP and a gmail address. If they only ever sign up for bulk email using their gmail account then they know that any bulk email they receive at their ISP email address is not mail they signed up for, and hence that it&#8217;s spam.</p>
<p>A more flexible way of having multiple email addresses is what&#8217;s known as <a title="Email Addressing FAQ" href="http://www.faqs.org/faqs/mail/addressing/" target="_blank">&#8220;boxing&#8221; or &#8220;tagging&#8221;</a> &#8211; being able to make up new variants of your email address on the fly. How that&#8217;s done varies depending on the mail system you use, but typically you&#8217;ll be able to add a string to the end of your email address, separated by a &#8220;+&#8221; or a &#8220;-&#8221;. For example, if my main email address is steve@blighty.com I can create a tagged address like steve-blogspam@blighty.com. They&#8217;ll both be delivered to my inbox by default, or I can use the tag to route the mail to another mailbox (either using the filtering rules in my mail client, or something like <a href="http://www.procmail.org/" target="_blank">procmail</a> or <a href="http://en.wikipedia.org/wiki/Sieve_(mail_filtering_language)" target="_blank">sieve</a> running on the mailserver).</p>
<p>Because I&#8217;ve never sent mail from the email address steve-blogspam@blighty.com, nor given it to anyone, nor even mentioned it anywhere other than this blog post I know that any email I get to it was sent by a spammer who harvested it from this page or the blog rss feed. On the other end of the spectrum I have tagged email addresses that I&#8217;ve created specifically to give to one of our vendors, and so I know that if I see email sent to that tagged address it&#8217;s almost certainly mail from that vendor, and I should have it skip my spam filters and send it directly to my inbox or a mailbox specifically for mail from vendors.</p>
<p>I&#8217;ve talked previously about some of the <a href="http://blog.wordtothewise.com/2009/03/what-is-an-email-address-part-two/" target="_blank">implications of address tagging for ESPs</a>, both for signup and list hygiene, and Laura has talked about <a href="http://blog.wordtothewise.com/2008/05/disposable-or-temporary-addresses/" target="_blank">tagged, disposable and temporary addresses</a> from a recipient perspective. Today I&#8217;m going to touch on another aspect of them &#8211; they mean that if you harvest addresses, or purchase addresses, sooner or later you&#8217;re going to get caught.</p>
<p>Last month I got a mail from a senior account executive (aka &#8220;salesweasel&#8221;) at Cisco/WebEx:</p>
<blockquote><p>Hello Steve,<br />
I am the Cisco WebEx Solutions Specialist responsible for supporting your region.<br />
Are you available this week or next for a brief discussion of your current business objectives?<br />
I would like to share some creative ideas about how you can reduce expenses and increase productivity throughout your organization.<br />
Please reply with the best time to reach you.<br />
Best regards,</p></blockquote>
<p>I don&#8217;t recall ever having any relationship with WebEx, and we swapped out all our Cisco networking gear quite some years ago. It could be that I gave them a business card at a trade show or somesuch, as I was vaguely looking at web conferencing providers a couple of years back &#8211; but it&#8217;s a bit odd that it doesn&#8217;t have my full name, nor does the salesweasel seem to know who my employer is. Sure enough, the mail wasn&#8217;t sent to either my personal or work addresses &#8211; it was sent to a tagged address. If that tagged address had been steve-webex or steve-cisco that would have told me that I probably had given it to them at some point in the distant past.</p>
<p>It wasn&#8217;t, though. Instead it was a tagged address that had only ever been used for one thing &#8211; it was used to register a domain that&#8217;s used primarily to host the CBL blacklist&#8217;s website. So WebEx or, more likely, the salesweasel is harvesting email addresses from whois in order to send spam to them, or is buying lists of addresses from someone who did. Given that they&#8217;d have to violate their agreement with the .org domain registry to do that, it&#8217;s clearly unethical business behaviour (and possibly even <a href="http://www.law.cornell.edu/uscode/18/1030.html" target="_blank">punishable by a fine or imprisonment of no more than one year</a>).</p>
<p>I just caught a potential vendor playing fast and loose with privacy. At the very least, that makes it unlikely I&#8217;d use them unless I got a really good explanation as to how this happened, and how they&#8217;d prevent it happening in the future.</p>
<p>It&#8217;s bad marketing, and the more technically literate your target demographic is the more likely they are to catch this sort of behaviour, and the more they&#8217;ll hold it against you. If your company doesn&#8217;t have a policy against this sort of address acquisition, it&#8217;s a good time to think about one (&#8220;Don&#8217;t do that.&#8221;). And if you do have one, check that your salesweasels are aware of it, and that it applies to email addresses bought from <a href="http://blog.wordtothewise.com/2009/09/marketing-to-businesses/" target="_blank">jigsaw</a> or <a href="http://blog.wordtothewise.com/2010/07/appendleads-is-not-unusual/" target="_blank">appendleads</a> or <a href="http://blog.wordtothewise.com/2008/11/two-reasons-not-to-buy-a-list/" target="_blank">zoominfo or emailappenders</a> just as much as it does to that CD of fifty million email addresses they bought from a guy in a bar.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.wordtothewise.com/2010/07/tagged-email-addresses/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

