<?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>Racker Hacker &#187; spamassassin</title>
	<atom:link href="http://rackerhacker.com/tag/spamassassin/feed/" rel="self" type="application/rss+xml" />
	<link>http://rackerhacker.com</link>
	<description>Words of wisdom from a server administrator</description>
	<lastBuildDate>Wed, 16 May 2012 12:55:04 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Basic procmail configuration with spamassassin filtering</title>
		<link>http://rackerhacker.com/2008/08/13/basic-procmail-configuration-with-spamassassin-filtering/</link>
		<comments>http://rackerhacker.com/2008/08/13/basic-procmail-configuration-with-spamassassin-filtering/#comments</comments>
		<pubDate>Wed, 13 Aug 2008 17:00:48 +0000</pubDate>
		<dc:creator>Major Hayden</dc:creator>
				<category><![CDATA[Blog Posts]]></category>
		<category><![CDATA[postfix]]></category>
		<category><![CDATA[procmail]]></category>
		<category><![CDATA[sendmail]]></category>
		<category><![CDATA[spamassassin]]></category>

		<guid isPermaLink="false">http://rackerhacker.com/?p=326</guid>
		<description><![CDATA[I've used this extremely basic procmail configuration a million times, and it's a great start for any server configuration. It passes e-mails through spamassassin (if they're smaller than 256KB) and then filters any e-mail marked as spam to /dev/null: LOGFILE=/var/log/procmail.log DROPPRIVS=yes :0fw &#124; /usr/bin/spamc :0 * ^X-Spam-Status: Yes /dev/null Of course, you can make this [...]<p><a href="http://rackerhacker.com/2008/08/13/basic-procmail-configuration-with-spamassassin-filtering/">Basic procmail configuration with spamassassin filtering</a> is a post from: Major Hayden's <a href="http://rackerhacker.com">Racker Hacker</a> blog. 
<p>Thanks for following the blog via the RSS feed. Please don't copy my posts or quote portions of them without attribution.</p></p>
]]></description>
			<content:encoded><![CDATA[<p>I've used this extremely basic procmail configuration a million times, and it's a great start for any server configuration.  It passes e-mails through spamassassin (if they're smaller than 256KB) and then filters any e-mail marked as spam to /dev/null:</p>
<p><code>LOGFILE=/var/log/procmail.log<br />
DROPPRIVS=yes</p>
<p>:0fw<br />
| /usr/bin/spamc</p>
<p>:0<br />
* ^X-Spam-Status: Yes<br />
/dev/null</code></p>
<p>Of course, you can make this much more complicated with some additional customization.</p>
<p><a href="http://rackerhacker.com/2008/08/13/basic-procmail-configuration-with-spamassassin-filtering/">Basic procmail configuration with spamassassin filtering</a> is a post from: Major Hayden's <a href="http://rackerhacker.com">Racker Hacker</a> blog. 
<p>Thanks for following the blog via the RSS feed. Please don't copy my posts or quote portions of them without attribution.</p></p>
]]></content:encoded>
			<wfw:commentRss>http://rackerhacker.com/2008/08/13/basic-procmail-configuration-with-spamassassin-filtering/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>High iowait on RHEL 4 with Plesk and SpamAssassin</title>
		<link>http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/</link>
		<comments>http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/#comments</comments>
		<pubDate>Thu, 31 Jan 2008 18:38:58 +0000</pubDate>
		<dc:creator>Major Hayden</dc:creator>
				<category><![CDATA[iowait]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[plesk]]></category>
		<category><![CDATA[spamassassin]]></category>

		<guid isPermaLink="false">http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/</guid>
		<description><![CDATA[One of my biggest complaints on RHEL 4 is the large resource usage by the version of SpamAssassin that is installed. When it runs, it uses a ton of CPU time and causes a lot of disk I/O as well. When running top, you may see multiple spamd processes. For a high-volume e-mail server (like [...]<p><a href="http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/">High iowait on RHEL 4 with Plesk and SpamAssassin</a> is a post from: Major Hayden's <a href="http://rackerhacker.com">Racker Hacker</a> blog. 
<p>Thanks for following the blog via the RSS feed. Please don't copy my posts or quote portions of them without attribution.</p></p>
]]></description>
			<content:encoded><![CDATA[<p>One of my biggest complaints on RHEL 4 is the large resource usage by the version of SpamAssassin that is installed.  When it runs, it uses a ton of CPU time and causes a lot of disk I/O as well.  When running top, you may see multiple spamd processes.  For a high-volume e-mail server (like the one I administer), this is simply unacceptable.</p>
<p>I decided to do something about it, and here are the steps:</p>
<p><strong>First,</strong> you will need two RPMs:<br />
Latest <a href="http://dag.wieers.com/rpm/packages/spamassassin/">SpamAssassin RPM from Dag</a><br />
The <a href="http://autoinstall.plesk.com/">psa-spamassassin RPM from SWSoft/Parallels</a>.</p>
<p>Once you have them both on the server, install the new SpamAssassin package from Dag:</p>
<p><code># rpm -Uvh spamassassin-(version).el4.rf.(arch).rpm</code></p>
<p>At this point, Plesk's spamassassin scripts will be non-functional, but the next step will fix it:</p>
<p><code># rpm -Uvh --force psa-spamassassin-(version).(arch).rpm</code></p>
<p><strong>NOTE: DO NOT REMOVE the psa-spamassassin RPM.  This will begin stripping your system of all SpamAssassin configurations and it cannot be reversed!</strong></p>
<p>Plesk's SpamAssassin scripts have been restored at this point in the process.  Now, we need to do the part that really makes SpamAssassin work efficiently:</p>
<p><code># sa-update; sa-compile;</code></p>
<p>This will update the SpamAssassin rules, and it will compile the rules with re2c (you may also need to <a href="http://dag.wieers.com/rpm/packages/re2c/">get this RPM from Dag</a>).  This compilation means less disk access, and less CPU time being used to process e-mails.</p>
<p>To activate the compiled rules within SpamAssassin, uncomment the plugin line in /etc/mail/spamassassin/v320.pre:</p>
<p><code># Rule2XSBody - speedup by compilation of ruleset to native code<br />
#<br />
loadplugin Mail::SpamAssassin::Plugin::Rule2XSBody</code></p>
<p>Please bear in mind that this process is done <em>at your own risk</em>.  This may cause issues getting support from SWSoft or your hosting company.  This has been tested on Red Hat Enterprise Linux 4 64-bit with Plesk 8.1.1, 8.2.0, and 8.2.1 with SpamAssassin 3.2.3 and 3.2.4. </p>
<p><a href="http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/">High iowait on RHEL 4 with Plesk and SpamAssassin</a> is a post from: Major Hayden's <a href="http://rackerhacker.com">Racker Hacker</a> blog. 
<p>Thanks for following the blog via the RSS feed. Please don't copy my posts or quote portions of them without attribution.</p></p>
]]></content:encoded>
			<wfw:commentRss>http://rackerhacker.com/2008/01/31/high-iowait-on-rhel-4-with-plesk-and-spamassassin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

