<?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>Server Sitters Tech Corner &#187; Spam</title>
	<atom:link href="http://serversitters.com/technical/category/spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://serversitters.com/technical</link>
	<description>Outsourced Web Hosting Support</description>
	<lastBuildDate>Wed, 15 Dec 2010 12:03:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Spam Assasin 2010 Bug</title>
		<link>http://serversitters.com/technical/spam/spam-assasin-y10k-bug/</link>
		<comments>http://serversitters.com/technical/spam/spam-assasin-y10k-bug/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 18:25:47 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Spam]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=189</guid>
		<description><![CDATA[FH_DATE_PAST_20XX scores on all mails dated 2010 or later. There was a bug in SpamAssassin that hit Jan 1st, 2010. All emails were getting marked with the above error in SpamAssassin, and it was adding 3.5 to the spam score, thus getting blocked by most standard spamassassin configs. To fix this, simply run sa-update from [...]]]></description>
			<content:encoded><![CDATA[<p> FH_DATE_PAST_20XX scores on all mails dated 2010 or later.  </p>
<p>There was a bug in SpamAssassin that hit Jan 1st, 2010.  All emails were getting marked with the above error in SpamAssassin, and it was adding 3.5 to the spam score, thus getting blocked by most standard spamassassin configs.</p>
<p>To fix this, simply run sa-update from a linux command line.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/spam/spam-assasin-y10k-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AOL Blacklist</title>
		<link>http://serversitters.com/technical/spam/aol-blacklist/</link>
		<comments>http://serversitters.com/technical/spam/aol-blacklist/#comments</comments>
		<pubDate>Sat, 19 Dec 2009 02:08:02 +0000</pubDate>
		<dc:creator>Paul</dc:creator>
				<category><![CDATA[Spam]]></category>

		<guid isPermaLink="false">http://serversitters.com/technical/?p=108</guid>
		<description><![CDATA[The problem with AOL&#8217;s RBL and other blacklists is that they only list the final relay IP as the sending IP. This is a problem because client&#8217;s often forward their email to AOL or other ISP&#8217;s. Here&#8217;s an example: Client has the domain: yourdomain.com Client has setup test@yourdomain.com to forward to test@aol.com A spammer sends [...]]]></description>
			<content:encoded><![CDATA[<p>The problem with AOL&#8217;s RBL and other blacklists is that they only list the final relay IP as the sending IP.  This is a problem because client&#8217;s often forward their email to AOL or other ISP&#8217;s.</p>
<p>Here&#8217;s an example:<br />
Client has the domain: yourdomain.com<br />
Client has setup test@yourdomain.com to forward to test@aol.com</p>
<p>A spammer sends a message to test@yourdomain.com.  The message is received by the client&#8217;s server.  It is then forwarded to test@aol.com.  The client then logs in to aol and they view the message.  The message is nothing more than spam and they then click &#8220;Mark as Spam&#8221; or &#8220;Report Spam&#8221;.</p>
<p>Now since the last server to receive the message was their own domain, they&#8217;re telling AOL that they&#8217;re own domain just sent them spam.  Eventually this will lead to AOL and other RBL&#8217;s blocking their server!  The Internet is mature, but not mature enough for it to follow the forwarding path to notice that the client is trying to report the sender as a spammer and not their own server.  When this occurs we usually send the client the following:</p>
<p>Important AOL email forwarding issue &#8211;<br />
We&#8217;ve been contacted by AOL because your account has been reported for spamming.  We worked with them to resolve the issue.</p>
<p>To ensure this doesn&#8217;t happen again you should not use the Report as Spam button when checking your email through AOL.  You&#8217;re actually reporting yourself for spamming.</p>
<p>Here&#8217;s Why:<br />
You have your email account with us configured to forward to your aol email address.  When a spammer sends you an email message it&#8217;s received by our server.  Then your email account forwards it to AOL from our server.  You receive it at AOL and report it as spam.  Aol&#8217;s system isn&#8217;t smart enough to realize that you&#8217;re reporting the spammer from a forwarded message.  Instead since the message last went through your account on our server prior to being forwarded to AOL they think you&#8217;re reporting your own email address on our system as a source of spam.</p>
<p>Please discontinue reporting spam via AOL or we&#8217;ll be forced to remove the AOL forwarder on your account to ensure we don&#8217;t get in trouble for the spam complaints.</p>
]]></content:encoded>
			<wfw:commentRss>http://serversitters.com/technical/spam/aol-blacklist/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

