<?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: How to Deal With Email Spam?</title>
	<atom:link href="http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/</link>
	<description>Follow Steph through his real estate and business journeys</description>
	<lastBuildDate>Wed, 25 Jan 2012 18:09:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: FollowSteph.com - InBoxer - Email Spam Filter for Outlook</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-41323</link>
		<dc:creator>FollowSteph.com - InBoxer - Email Spam Filter for Outlook</dc:creator>
		<pubDate>Thu, 13 Mar 2008 17:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-41323</guid>
		<description>[...] really frustrated with the levels of spam my personal emails were receiving so I wrote a blog post asking what others were doing to reduce their email spam. Someone suggested SpamBayes, a free open source solution, which worked great for a while but then [...]</description>
		<content:encoded><![CDATA[<p>[...] really frustrated with the levels of spam my personal emails were receiving so I wrote a blog post asking what others were doing to reduce their email spam. Someone suggested SpamBayes, a free open source solution, which worked great for a while but then [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-3935</link>
		<dc:creator>Steph</dc:creator>
		<pubDate>Tue, 09 Jan 2007 00:38:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-3935</guid>
		<description>Hi Ronny,

That&#039;s quite a spam filtering system you&#039;ve built yourself. Can I assume then that you get a substantial amount of spam? I can&#039;t imagine going through all this trouble for just a few hundred, or even a few thousand, spam emails per day...

Also, one thing I personally don&#039;t like is the challenge-response system. This might work on a personal level, but when it comes to a company&#039;s face, I have to disagree with it. The onus should be on the company, not the individual to contact you. Enough said, this was already debated above. 

Otherwise I think you have a very powerful spam prevention system. Have you every looked at creating a commercial product based on this?</description>
		<content:encoded><![CDATA[<p>Hi Ronny,</p>
<p>That&#8217;s quite a spam filtering system you&#8217;ve built yourself. Can I assume then that you get a substantial amount of spam? I can&#8217;t imagine going through all this trouble for just a few hundred, or even a few thousand, spam emails per day&#8230;</p>
<p>Also, one thing I personally don&#8217;t like is the challenge-response system. This might work on a personal level, but when it comes to a company&#8217;s face, I have to disagree with it. The onus should be on the company, not the individual to contact you. Enough said, this was already debated above. </p>
<p>Otherwise I think you have a very powerful spam prevention system. Have you every looked at creating a commercial product based on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronny Skog</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-3859</link>
		<dc:creator>Ronny Skog</dc:creator>
		<pubDate>Sat, 06 Jan 2007 22:31:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-3859</guid>
		<description>After doing a lot of experimenting with various spam filter systems here is the solution that work best for me:

1.First all emails get filtered through a whitelist. The software I&#039;m using can scan through my archived emails and address book and add all emails on installation. After this, everyone I send a email to automatically get white listed.
2.Then the rest of the emails go through a White rules filter, the exact opposite of a spam filter. Emails containing my name or company name are accepted (email addresses are easy to harvest, but very few spammers are able to get my name and address unless you give it to them). Emails sent from my website (using a secure contact form with hidden &quot;to&quot; email) is accepted. On my site I also ask customers contacting me by regular email to put a verification code in the subject line (if you click the link this code will be inserted automatically). All emails containing this code is accepted.

This covers everyone I ever received or sent email to plus practically all my customers who contact me through my website. Whats left are people contacting me out of the blue without using my site.

3. These emails are filtered through a Bayesian filter. The filter also allow for rule based filtering. I&#039;m using rules to filter out sexually explicit words in the subject and image spam (Most Bayesian filters are not very good in detecting image spam.).
4. Emails getting a very high spam score from the Bayesian filter get deleted automatically.
5.The rest of the emails are checked for spoofed from addresses (using SPF records).
6.The emails passing this final test will receive a challenge response message just to make sure no real emails ever get caught in the spam box without giving the sender an option to get his message through. Of course no email is ever challenged twice.

This combination works quite well because:

A.) Everyone already known to me get through with no filtering. I provide options for everyone not already known to me to get trough via my website. 99% of all legitimate emails will reach me through this whitelist/rules system.
B.) Most real emails not caught by my white list/rules will be accepted by my Bayesian filter and reach my inbox with no hassle or need for people to verify themselves.
C.) The Challenge response email assures no valid email ever will just disappear. At the same time the automatic deletion of forged emails and high spam score emails reduces the amount of challenges sent and minimizes the drawbacks of traditionally configured challenge response systems that indiscriminately will just send lots of emails to everyone not on your whitelist.</description>
		<content:encoded><![CDATA[<p>After doing a lot of experimenting with various spam filter systems here is the solution that work best for me:</p>
<p>1.First all emails get filtered through a whitelist. The software I&#8217;m using can scan through my archived emails and address book and add all emails on installation. After this, everyone I send a email to automatically get white listed.<br />
2.Then the rest of the emails go through a White rules filter, the exact opposite of a spam filter. Emails containing my name or company name are accepted (email addresses are easy to harvest, but very few spammers are able to get my name and address unless you give it to them). Emails sent from my website (using a secure contact form with hidden &#8220;to&#8221; email) is accepted. On my site I also ask customers contacting me by regular email to put a verification code in the subject line (if you click the link this code will be inserted automatically). All emails containing this code is accepted.</p>
<p>This covers everyone I ever received or sent email to plus practically all my customers who contact me through my website. Whats left are people contacting me out of the blue without using my site.</p>
<p>3. These emails are filtered through a Bayesian filter. The filter also allow for rule based filtering. I&#8217;m using rules to filter out sexually explicit words in the subject and image spam (Most Bayesian filters are not very good in detecting image spam.).<br />
4. Emails getting a very high spam score from the Bayesian filter get deleted automatically.<br />
5.The rest of the emails are checked for spoofed from addresses (using SPF records).<br />
6.The emails passing this final test will receive a challenge response message just to make sure no real emails ever get caught in the spam box without giving the sender an option to get his message through. Of course no email is ever challenged twice.</p>
<p>This combination works quite well because:</p>
<p>A.) Everyone already known to me get through with no filtering. I provide options for everyone not already known to me to get trough via my website. 99% of all legitimate emails will reach me through this whitelist/rules system.<br />
B.) Most real emails not caught by my white list/rules will be accepted by my Bayesian filter and reach my inbox with no hassle or need for people to verify themselves.<br />
C.) The Challenge response email assures no valid email ever will just disappear. At the same time the automatic deletion of forged emails and high spam score emails reduces the amount of challenges sent and minimizes the drawbacks of traditionally configured challenge response systems that indiscriminately will just send lots of emails to everyone not on your whitelist.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steph</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-843</link>
		<dc:creator>Steph</dc:creator>
		<pubDate>Thu, 19 Oct 2006 16:39:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-843</guid>
		<description>Thank you everyone for the great feedback, it&#039;s been really helpful!

Here are some additional thoughts. Personally, I don&#039;t really know that much about email, nor do I really want to. Although it&#039;s &lt;b&gt;A&lt;/b&gt; core &lt;b&gt;part&lt;/b&gt; of my business, it&#039;s not &lt;b&gt;THE&lt;/b&gt; core of my business. The less resources I need to allocate to handling this issue the better. 

At this stage as we&#039;re still fairly small, I can&#039;t afford to have someone playing and configuring the mailserver. I looked at SpamAssassin and to me the biggest issue is that although it appears very effective, it requires a substantial amount of time and effort. As well, upgrades seem to be anything but seemless... This is not something I want to do, or allocate resources to. The benefits do not outweigh these higher costs. Maybe when I reach 10,000-20,000 spam emails a day, but for now it&#039;s not worth it (our support and customer service emails are handled by another system).

Patrick, from &lt;a href=&quot;http://microisvjournal.wordpress.com/&quot; rel=&quot;nofollow&quot;&gt;MicroISV on a Shoestring&lt;/a&gt;, suggested an &lt;a href=&quot;http://microisvjournal.wordpress.com/2006/10/19/dealing-with-email-spam/&quot; rel=&quot;nofollow&quot;&gt;alternative solution called Popfile&lt;/a&gt; which he says is much easier to use. After the praise he gives it, I have no doubt! I looked into this option a little, and it looks interesting. I&#039;m going to give &lt;a href=&quot;http://spambayes.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;SpamBayes&lt;/a&gt; a little more time before trying something else, but this will probably be my next option unless something else attracts my attention.

Another suggestion was grey listing. Although I appreciate this suggestion, it unfortunately puts the onus back again on the person trying to reach me, which I don&#039;t really agree with.

As well Ali suggested I limit the number of email addresses supplied for &lt;a href=&quot;http://www.LandlordMax.com&quot; rel=&quot;nofollow&quot;&gt;LandlordMax&lt;/a&gt;. This is fine when we were smaller, but as grew we needed more differentiation. Also, since you might not be as aware of how our support system works, none of the support emails come to me. We&#039;ve already purchased a customer support system (&lt;a href=&quot;http://www.userscape.com&quot; rel=&quot;nofollow&quot;&gt;HelpSpot&lt;/a&gt; which &lt;a href=&quot;http://www.followsteph.com/2006/06/20/helpspot-versus-fogbugz/&quot; rel=&quot;nofollow&quot;&gt;I recommend&lt;/a&gt;). This is only for emails addressed to me from this blog and my company (and some internal email addresses from our project management system, support system, etc.). The spam we get for LandlordMax is actually filtered through HelpSpot&#039;s Bayersian filter, which is working great now that it&#039;s been trained. 

So far I have to admit I like &lt;a href=&quot;http://spambayes.sourceforge.net/&quot; rel=&quot;nofollow&quot;&gt;SpamBayes&lt;/a&gt;. It took minutes to install, didn&#039;t require any server configurations, and is very effective. Because of the quantity of emails I receive, it didn&#039;t take nearly as long as I thought it would to train. Within a day I&#039;ve already noticed a significant drop in spam emails in my inbox. Of course there have been many false positives, but these are already starting to drop significantly! I suspect that within a week or so it&#039;ll be at a point where I&#039;ll be content enough to leave things as they are.

The less amount of effort I have to spend to resolve this issue the better. This is not my company&#039;s core competency, nor this does really bring in any additional revenue (it does however prevents me from losing revenues). This is like building a customer service system because it&#039;s interesting rather than what pays the bills. It&#039;d be fun, but I can&#039;t justify it.

I&#039;ll definitely post a follow-up article in a month or so to let you all know how it&#039;s going. And please do continue to offer suggestions, it&#039;s really helping me! And I&#039;m sure many of the other people who come here are finding it useful too! Thanks again for all the help :)</description>
		<content:encoded><![CDATA[<p>Thank you everyone for the great feedback, it&#8217;s been really helpful!</p>
<p>Here are some additional thoughts. Personally, I don&#8217;t really know that much about email, nor do I really want to. Although it&#8217;s <b>A</b> core <b>part</b> of my business, it&#8217;s not <b>THE</b> core of my business. The less resources I need to allocate to handling this issue the better. </p>
<p>At this stage as we&#8217;re still fairly small, I can&#8217;t afford to have someone playing and configuring the mailserver. I looked at SpamAssassin and to me the biggest issue is that although it appears very effective, it requires a substantial amount of time and effort. As well, upgrades seem to be anything but seemless&#8230; This is not something I want to do, or allocate resources to. The benefits do not outweigh these higher costs. Maybe when I reach 10,000-20,000 spam emails a day, but for now it&#8217;s not worth it (our support and customer service emails are handled by another system).</p>
<p>Patrick, from <a href="http://microisvjournal.wordpress.com/" rel="nofollow">MicroISV on a Shoestring</a>, suggested an <a href="http://microisvjournal.wordpress.com/2006/10/19/dealing-with-email-spam/" rel="nofollow">alternative solution called Popfile</a> which he says is much easier to use. After the praise he gives it, I have no doubt! I looked into this option a little, and it looks interesting. I&#8217;m going to give <a href="http://spambayes.sourceforge.net/" rel="nofollow">SpamBayes</a> a little more time before trying something else, but this will probably be my next option unless something else attracts my attention.</p>
<p>Another suggestion was grey listing. Although I appreciate this suggestion, it unfortunately puts the onus back again on the person trying to reach me, which I don&#8217;t really agree with.</p>
<p>As well Ali suggested I limit the number of email addresses supplied for <a href="http://www.LandlordMax.com" rel="nofollow">LandlordMax</a>. This is fine when we were smaller, but as grew we needed more differentiation. Also, since you might not be as aware of how our support system works, none of the support emails come to me. We&#8217;ve already purchased a customer support system (<a href="http://www.userscape.com" rel="nofollow">HelpSpot</a> which <a href="http://www.followsteph.com/2006/06/20/helpspot-versus-fogbugz/" rel="nofollow">I recommend</a>). This is only for emails addressed to me from this blog and my company (and some internal email addresses from our project management system, support system, etc.). The spam we get for LandlordMax is actually filtered through HelpSpot&#8217;s Bayersian filter, which is working great now that it&#8217;s been trained. </p>
<p>So far I have to admit I like <a href="http://spambayes.sourceforge.net/" rel="nofollow">SpamBayes</a>. It took minutes to install, didn&#8217;t require any server configurations, and is very effective. Because of the quantity of emails I receive, it didn&#8217;t take nearly as long as I thought it would to train. Within a day I&#8217;ve already noticed a significant drop in spam emails in my inbox. Of course there have been many false positives, but these are already starting to drop significantly! I suspect that within a week or so it&#8217;ll be at a point where I&#8217;ll be content enough to leave things as they are.</p>
<p>The less amount of effort I have to spend to resolve this issue the better. This is not my company&#8217;s core competency, nor this does really bring in any additional revenue (it does however prevents me from losing revenues). This is like building a customer service system because it&#8217;s interesting rather than what pays the bills. It&#8217;d be fun, but I can&#8217;t justify it.</p>
<p>I&#8217;ll definitely post a follow-up article in a month or so to let you all know how it&#8217;s going. And please do continue to offer suggestions, it&#8217;s really helping me! And I&#8217;m sure many of the other people who come here are finding it useful too! Thanks again for all the help <img src='http://www.followsteph.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anon</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-840</link>
		<dc:creator>anon</dc:creator>
		<pubDate>Thu, 19 Oct 2006 11:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-840</guid>
		<description>we use amavisd with spamassassin as spam-filter. works like a charm and is highly configurable. spamassassin doesn&#039;t have to delete all the spam, if you don&#039;t like it to; you can also just add the sa-checks as additional header in the mail and let your client do the sorting-out, for example.
i just installed another nice plugin for spamassassin, FuzzyOCR. this script uses a free ocr-app to check images in mails for words as &quot;commercial&quot;, &quot;free&quot; and so on. works like a charm - all those f*ing image-spam-mails get caught and sorted out.</description>
		<content:encoded><![CDATA[<p>we use amavisd with spamassassin as spam-filter. works like a charm and is highly configurable. spamassassin doesn&#8217;t have to delete all the spam, if you don&#8217;t like it to; you can also just add the sa-checks as additional header in the mail and let your client do the sorting-out, for example.<br />
i just installed another nice plugin for spamassassin, FuzzyOCR. this script uses a free ocr-app to check images in mails for words as &#8220;commercial&#8221;, &#8220;free&#8221; and so on. works like a charm &#8211; all those f*ing image-spam-mails get caught and sorted out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-836</link>
		<dc:creator>James</dc:creator>
		<pubDate>Thu, 19 Oct 2006 08:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-836</guid>
		<description>1000s a day!

I too recommend SpamBayes for Outlook. It works beautifully for me, catching around 300 spams a day with no errors.</description>
		<content:encoded><![CDATA[<p>1000s a day!</p>
<p>I too recommend SpamBayes for Outlook. It works beautifully for me, catching around 300 spams a day with no errors.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave K</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-835</link>
		<dc:creator>Dave K</dc:creator>
		<pubDate>Thu, 19 Oct 2006 08:33:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-835</guid>
		<description>A combination of approaches gives the best results. Maintaining white / black lists ensures that you can kill messages you know are spam and ensure receipt of messages from trusted sources. Use bayesian filtering to attempt to sort out the rest and any message from a source not on the black list which the filter junks should be sent a validation request.

Joel had one of his interns implement bayesian filtering for FogBugz, a &lt;a href=&#039;http://www.fogcreek.com/FogBugz/Downloads/KamensPaper.pdf&#039; rel=&quot;nofollow&quot;&gt; paper&lt;/a&gt; is available.</description>
		<content:encoded><![CDATA[<p>A combination of approaches gives the best results. Maintaining white / black lists ensures that you can kill messages you know are spam and ensure receipt of messages from trusted sources. Use bayesian filtering to attempt to sort out the rest and any message from a source not on the black list which the filter junks should be sent a validation request.</p>
<p>Joel had one of his interns implement bayesian filtering for FogBugz, a <a href='http://www.fogcreek.com/FogBugz/Downloads/KamensPaper.pdf' rel="nofollow"> paper</a> is available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-833</link>
		<dc:creator>Ali</dc:creator>
		<pubDate>Thu, 19 Oct 2006 06:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-833</guid>
		<description>Howdy Steph,

The first step is changing to two email addresses, one which receives all support requests, pre-sale enquiries, feedback, and all enquiries originating from your website.

The other one should receive all emails from people you meet in person. For example, if you meet someone in the elevator who might be a potential client, you would give him this email address. This is also the one which is printed on your business cards etc. This one shouldn&#039;t be available anywhere on your website.

The next step is, adding a contact form to your website, and removing all mailto: links and other mentions of the first email address. The contact form would email you whenever someone uses it, with a known string such as &#039;Web Support:&#039; in the subject. Then you would configure your email client to filter all email, except those with &#039;Web Support:&#039; in the subject to be sent to your junk folder.

Since the second email is never revealed on the web, you won&#039;t get any spam (or, only a little spam) on it. And since the first one is only supposed to be used from the contact form, you won&#039;t have to worry about other emails.

Just the best I could come up with. Also, if you really hate this problem, why not scratch your own itch and build a decent spam-fighting prodocut for your uISV? ;0)</description>
		<content:encoded><![CDATA[<p>Howdy Steph,</p>
<p>The first step is changing to two email addresses, one which receives all support requests, pre-sale enquiries, feedback, and all enquiries originating from your website.</p>
<p>The other one should receive all emails from people you meet in person. For example, if you meet someone in the elevator who might be a potential client, you would give him this email address. This is also the one which is printed on your business cards etc. This one shouldn&#8217;t be available anywhere on your website.</p>
<p>The next step is, adding a contact form to your website, and removing all mailto: links and other mentions of the first email address. The contact form would email you whenever someone uses it, with a known string such as &#8216;Web Support:&#8217; in the subject. Then you would configure your email client to filter all email, except those with &#8216;Web Support:&#8217; in the subject to be sent to your junk folder.</p>
<p>Since the second email is never revealed on the web, you won&#8217;t get any spam (or, only a little spam) on it. And since the first one is only supposed to be used from the contact form, you won&#8217;t have to worry about other emails.</p>
<p>Just the best I could come up with. Also, if you really hate this problem, why not scratch your own itch and build a decent spam-fighting prodocut for your uISV? ;0)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CWionzek</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-832</link>
		<dc:creator>CWionzek</dc:creator>
		<pubDate>Thu, 19 Oct 2006 04:34:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-832</guid>
		<description>An option someone hooked me onto a little while ago is the concept of &quot;Greylisting&quot;.

Basically it just tells a mailserver that you&#039;re busy and to resend the message in 5 minutes (or however long). Spam email servers aren&#039;t built to deal with this kind of thing, since they&#039;re blowing through email as fast as humanly possible...so supposedly this puts a huge damper on the spam you receive.

The only flaw I&#039;ve seen with it (aside from non-compliant servers just not returning your mail at all) is that you&#039;ve got a five-minute wait delay in your email. Perhaps you can combine this with some form of Whitelisting to let certain people straight through the filtering?</description>
		<content:encoded><![CDATA[<p>An option someone hooked me onto a little while ago is the concept of &#8220;Greylisting&#8221;.</p>
<p>Basically it just tells a mailserver that you&#8217;re busy and to resend the message in 5 minutes (or however long). Spam email servers aren&#8217;t built to deal with this kind of thing, since they&#8217;re blowing through email as fast as humanly possible&#8230;so supposedly this puts a huge damper on the spam you receive.</p>
<p>The only flaw I&#8217;ve seen with it (aside from non-compliant servers just not returning your mail at all) is that you&#8217;ve got a five-minute wait delay in your email. Perhaps you can combine this with some form of Whitelisting to let certain people straight through the filtering?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dealing With Email Spam &#171; MicroISV on a Shoestring</title>
		<link>http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/comment-page-1/#comment-831</link>
		<dc:creator>Dealing With Email Spam &#171; MicroISV on a Shoestring</dc:creator>
		<pubDate>Thu, 19 Oct 2006 03:39:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.followsteph.com/2006/10/18/how-to-deal-with-email-spam/#comment-831</guid>
		<description>[...] Steph of LandLordMax fame recently posted about how to deal with email spam.  This just happens to be the focus of my day job (we&#8217;re busy exploiting the synergies of a new paradigm of&#8230; actually, no, I don&#8217;t work in Dilbert&#8217;s office).  I use spam filtering religiously on all my email accounts (4 at last count) and it saves me roughly 2,000 spam a day (my business email address is forwarded to by my college email address, which was widely circulated back when I was young and stupid). [...]</description>
		<content:encoded><![CDATA[<p>[...] Steph of LandLordMax fame recently posted about how to deal with email spam.  This just happens to be the focus of my day job (we&#8217;re busy exploiting the synergies of a new paradigm of&#8230; actually, no, I don&#8217;t work in Dilbert&#8217;s office).  I use spam filtering religiously on all my email accounts (4 at last count) and it saves me roughly 2,000 spam a day (my business email address is forwarded to by my college email address, which was widely circulated back when I was young and stupid). [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

