<?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>/dev/root &#187; Linux</title>
	<atom:link href="http://devroot.org/category/linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://devroot.org</link>
	<description>Rants of a grumpy sysadmin living in London.</description>
	<lastBuildDate>Mon, 26 Jul 2010 11:25:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>IPV6 baby!</title>
		<link>http://devroot.org/2010/02/17/ipv6-baby/</link>
		<comments>http://devroot.org/2010/02/17/ipv6-baby/#comments</comments>
		<pubDate>Wed, 17 Feb 2010 13:24:41 +0000</pubDate>
		<dc:creator>lynxman</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Networking]]></category>

		<guid isPermaLink="false">http://devroot.org/?p=78</guid>
		<description><![CDATA[devroot.org is now being served in IPv6 as well thanks to sixxs.net]]></description>
			<content:encoded><![CDATA[<p>devroot.org is now being served in IPv6 as well thanks to <a href="http://sixxs.net">sixxs.net</a></p>
]]></content:encoded>
			<wfw:commentRss>http://devroot.org/2010/02/17/ipv6-baby/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IBM xServer 305 on CentOS 4 &#8211; Kernel incompatibilities</title>
		<link>http://devroot.org/2007/02/05/ibm-xserver-305-on-centos-4-kernel-incompatibilities/</link>
		<comments>http://devroot.org/2007/02/05/ibm-xserver-305-on-centos-4-kernel-incompatibilities/#comments</comments>
		<pubDate>Mon, 05 Feb 2007 10:39:43 +0000</pubDate>
		<dc:creator>lynxman</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[IBM]]></category>
		<category><![CDATA[Kernel]]></category>

		<guid isPermaLink="false">http://devroot.org/2007/02/05/ibm-xserver-305-on-centos-4-kernel-incompatibilities/</guid>
		<description><![CDATA[After a horrible week fighting against CentOS 4 and our firewalls deployment. I&#8217;ve found several incompatibilities (albeit already documented) with this machines and CentOS 4. There were 2 different problems affecting this machines. Keyboard not working after kernel boot, non responsive. This happens even when installing the machine, I had to install this machine in [...]]]></description>
			<content:encoded><![CDATA[<p>After a horrible week fighting against CentOS 4 and our firewalls deployment. I&#8217;ve found several incompatibilities (albeit already documented) with this machines and CentOS 4.</p>
<p>There were 2 different problems affecting this machines.</p>
<p><strong>Keyboard not working after kernel boot, non responsive.</strong></p>
<p>This happens even when installing the machine, I had to install this machine in graphical mode (it works when booting in graphical mode) but it didn&#8217;t work at all on a forced text installation.</p>
<p>This bug can be solved disconnecting the USB subsystem in the BIOS, after that the keyboard is operative again.</p>
<p><strong>Machine freezes with a kernel panic after approx 24h. of operation, no logs or traces left.</strong></p>
<p>This one was a hard bone to catch! Did a memory test, updates both BIOS and network cards firmware to the last version and did several extended checks on the hardware, there was not a single error.</p>
<p>After roaming around the RedHat and CentOS forums for a while looking for an answer, I saw a similar error in RedHat RHEL4 (the one CentOS is based on) about an xServer that had the same problem. It seems the problem is realted with the old version of ACPI this motherboard has, and it only happens with 2.6.9-42.x.EL versions of the kernel, just adding the <em>noapic</em> option in /etc/grub.conf to the kernel boot solved the issue.</p>
<p><code>title CentOS (2.6.9-42.0.8.EL)<br />
root (hd0,0)<br />
kernel /vmlinuz-2.6.9-42.0.8.EL ro noapic root=LABEL=/<br />
initrd /initrd-2.6.9-42.0.8.EL.img</code></p>
]]></content:encoded>
			<wfw:commentRss>http://devroot.org/2007/02/05/ibm-xserver-305-on-centos-4-kernel-incompatibilities/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>SpamAssassin : Tweaks for new Spam methods</title>
		<link>http://devroot.org/2006/12/12/spamassassin-tweaks-for-new-spam-methods/</link>
		<comments>http://devroot.org/2006/12/12/spamassassin-tweaks-for-new-spam-methods/#comments</comments>
		<pubDate>Tue, 12 Dec 2006 14:45:04 +0000</pubDate>
		<dc:creator>lynxman</dc:creator>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[rules]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Spamassassin]]></category>

		<guid isPermaLink="false">http://devroot.org/2006/12/12/spamassassin-tweaks-for-new-spam-methods/</guid>
		<description><![CDATA[There have been lately a huge increase in spam due mainly to botnets, spammers also have shifted their spam methods, using embedded images and obfuscating techniques to avoid OCRs. This two factors together mean that I&#8217;ve got a lot more work maintaining my spamassassin installation :) and also that the standard config or some deviations [...]]]></description>
			<content:encoded><![CDATA[<p>There have been lately a huge increase in spam due mainly to botnets, spammers also have shifted their spam methods, using embedded images and obfuscating techniques to avoid OCRs.</p>
<p>This two factors together mean that I&#8217;ve got a lot more work maintaining my spamassassin installation :) and also that the standard config or some deviations on the scoring is not good enough, even with score tweaking I still got lots of Stocks and embedded gif spam, after some checking around I found some solutions in <a title="Rules Emporium" href="http://www.rulesemporium.com/" target="_blank">Rules Emporium</a>. Also updating is a must so try always to keep up to date, right now I&#8217;m running <a title="Spam Assassin" href="http://spamassassin.apache.org" target="_blank">Spam Assassin 3.1.7</a>.<br />
Finally after some tweaking and more tweaking I arrived to this config:</p>
<ul>
<li>Auto White-list and Bayes using MySQL DB Engine</li>
<li>user_pref integrated into our user control panel</li>
<li>Razor2 integration</li>
<li>SPF Integration</li>
<li>Score tweaking</li>
<li>New rules added using <a title="Rules Emporium" href="http://www.rulesemporium.com/" target="_blank">Rules Emporium</a> ImageInfo and Stock Rules</li>
</ul>
<p>With this method the false positives have gone down and the stock and image spam is being stopped (finally!).</p>
<p>The <a title="Rules Emporium" href="http://www.rulesemporium.com/" target="_blank">Rules Emporium</a> ImageInfo plugin consumes a lot less CPU than using an OCR plug-in and even if it&#8217;s based on broader rules it catches even the hardest embedded image spam, you can get the plugin <a title="ImageInfo plugin" href="http://www.rulesemporium.com/plugins.htm" target="_blank">here</a>. Also the stock ruleset got rid of most of the stock spam that I was receiving, this spam is quite hard to guess indeed! You can get the ruleset <a title="Stocks Ruleset" href="http://www.rulesemporium.com/rules/70_sare_stocks.cf" target="_blank">here</a>.<br />
Here is the final tweaked local.cf config in SpamAssassin</p>
<p><code> required_score 3<br />
report_safe 0<br />
rewrite_header Subject [SPAM]<br />
use_dcc 0 # DCC is quite useless<br />
use_razor2 # Activate Razor 2 module<br />
razor_timeout 10<br />
lock_method flock # For local bayes files<br />
use_bayes 1<br />
use_auto_whitelist 1<br />
bayes_store_module Mail::SpamAssassin::BayesStore::SQL<br />
bayes_sql_dsn DBI:mysql:spamassassin:bayesdb<br />
bayes_sql_username mail bayes_sql_password xxxxx<br />
bayes_auto_expire 1<br />
bayes_auto_learn_threshold_spam 3.5<br />
bayes_auto_learn_threshold_nonspam 0.1<br />
bayes_use_hapaxes 1<br />
bayes_journal_max_size 20000 # This doesn't affect SQL<br />
bayes_expiry_max_db_size 50000 # This doesn't affect SQL<br />
auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList<br />
user_awl_dsn DBI:mysql:spamassassin:bayesdb<br />
user_awl_sql_username mail<br />
user_awl_sql_password xxxxx<br />
user_awl_sql_table awl<br />
user_scores_dsn DBI:mysql:spamassassin:control_panel<br />
user_scores_sql_username mail<br />
user_scores_sql_password xxxxx<br />
report_contact abuse@devroot.org<br />
# Score increases (manually change scores)<br />
score RAZOR2_CHECK 2.000<br />
score RAZOR2_CF_RANGE_51_100 2.000<br />
score BAYES_99 3.500<br />
score BAYES_90 3.000<br />
score BAYES_80 2.500<br />
score HTML_IMAGE_ONLY_04 3.000<br />
score HTML_IMAGE_ONLY_08 2.500<br />
score HTML_IMAGE_ONLY_12 2.000<br />
score HTML_IMAGE_ONLY_16 1.500<br />
score HTML_IMAGE_ONLY_20 1.000<br />
score HTML_IMAGE_ONLY_24 0.500<br />
score MIME_HTML_ONLY 1.100 </code></p>
<p>Also it&#8217;s important to have this modules loaded in your v310.pre file:</p>
<p><code> loadplugin Mail::SpamAssassin::Plugin::Pyzor<br />
loadplugin Mail::SpamAssassin::Plugin::Razor2<br />
loadplugin Mail::SpamAssassin::Plugin::SpamCop<br />
loadplugin Mail::SpamAssassin::Plugin::AWL<br />
loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold<br />
loadplugin Mail::SpamAssassin::Plugin::WhiteListSubject<br />
loadplugin Mail::SpamAssassin::Plugin::MIMEHeader<br />
loadplugin Mail::SpamAssassin::Plugin::ReplaceTags<br />
loadplugin Mail::SpamAssassin::Plugin::ImageInfo # RulesEmporium </code></p>
<p>The way to install the additional config and plugins should be as follows:</p>
<p>Copy the new .cf (configuration) files into the directory where SpamAssassin keeps the configuration in your install. In Red Hat machines this directory is <em>/usr/share/spamassassin</em>.</p>
<p>Copy the new .pm (modules) into the SpamAssassin PlugIn module which is by default <em><span class="moz-txt-slash"><span class="moz-txt-tag">/</span>usr/lib/perl5/vendor_perl/5.8.3/Mail/SpamAssassin/Plugin<span class="moz-txt-tag">/ </span></span></em><span class="moz-txt-slash"><span class="moz-txt-tag">(this directory of course, is for Perl version 5.8.3, change the version to the one you have installed).</span></span><em><span class="moz-txt-slash"><span class="moz-txt-tag"><br />
</span></span></em></p>
<p>Don&#8217;t forget to restart SpamAssassin after adding the new files!</p>
<p>It&#8217;s always a good idea to start <em>spamd</em> with -D after activating modules, since most of the times you&#8217;re missing a perl module which one of your modules have a dependency with.</p>
<p>This configuration is not really CPU hungry so it&#8217;s great for people who are running on a tight server budget.</p>
]]></content:encoded>
			<wfw:commentRss>http://devroot.org/2006/12/12/spamassassin-tweaks-for-new-spam-methods/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
