<?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"
	>
<channel>
	<title>Comments on: SpamSieve test drive</title>
	<atom:link href="http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/</link>
	<description>by Mark Mayo</description>
	<pubDate>Fri, 12 Mar 2010 02:29:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: mark</title>
		<link>http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/#comment-1935</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Fri, 11 Mar 2005 16:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/#comment-1935</guid>
		<description>That's a neat tip. Thx! I do use Maildir, so I may try this out and see how well SpamAssassin does with better training. I've also tried dspam out recently, and it seemed to be quite good as well. One thing I really like about SpamSieve now that I've been using it for a couple weeks is the corpus browser. Really handy to drill down to some words and see how they're categorized. The instant stats screen is nice too. The big problem with a spam filter that runs on the client, however, is that you always need to leave the client running. Well, it's a problem if you're like me and check your email from a variety of computers, anyways. Latest stats:

Filtered Mail
522 Good Messages
8696 Spam Messages (94%)
468 Spam Messages Per Day

SpamSieve Accuracy
1 False Positives
83 False Negatives (99%)
99.1% Correct

Corpus
1684 Good Messages
2385 Spam Messages (59%)
129844 Total Words

Rules
1605 Blocklist Rules
863 Whitelist Rules</description>
		<content:encoded><![CDATA[<p>That&#8217;s a neat tip. Thx! I do use Maildir, so I may try this out and see how well SpamAssassin does with better training. I&#8217;ve also tried dspam out recently, and it seemed to be quite good as well. One thing I really like about SpamSieve now that I&#8217;ve been using it for a couple weeks is the corpus browser. Really handy to drill down to some words and see how they&#8217;re categorized. The instant stats screen is nice too. The big problem with a spam filter that runs on the client, however, is that you always need to leave the client running. Well, it&#8217;s a problem if you&#8217;re like me and check your email from a variety of computers, anyways. Latest stats:</p>
<p>Filtered Mail<br />
522 Good Messages<br />
8696 Spam Messages (94%)<br />
468 Spam Messages Per Day</p>
<p>SpamSieve Accuracy<br />
1 False Positives<br />
83 False Negatives (99%)<br />
99.1% Correct</p>
<p>Corpus<br />
1684 Good Messages<br />
2385 Spam Messages (59%)<br />
129844 Total Words</p>
<p>Rules<br />
1605 Blocklist Rules<br />
863 Whitelist Rules</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Adams</title>
		<link>http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/#comment-1915</link>
		<dc:creator>Chris Adams</dc:creator>
		<pubDate>Thu, 10 Mar 2005 02:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.vmunix.com/mark/blog/archives/2005/02/21/spamsieve-test-drive/#comment-1915</guid>
		<description>I found it's easier to simply continue training SpamAssassin - the way I work is simply by having a cron entry run sa-learn on read messages in my inbox and spam folders. When a message is miscategorized simply move it to the appropriate folder and make sure it's marked as seen:

find ~/Maildir -type d -maxdepth 1 -mindepth 1 ! -iname .Trash ! -iname .Spam ! -iname .unblocked-spam ! -iname .junk -exec find {} 
-type f -mtime -3 -name \*S \; &#124; sa-learn --ham -f -

find ~/Maildir/.Spam/cur/ -name \*S &#124; sa-learn --spam -f -

Note that this approach assumes you use a Maildir-based IMAP server; for a pure IMAP approach I've actually used the Perl Mail::Box module to make an IMAPS connection and loop over the appropriate mailboxes - the only drawback to that approach is that it requires you to either run it interactively or store your mail password in a file (yech).</description>
		<content:encoded><![CDATA[<p>I found it&#8217;s easier to simply continue training SpamAssassin - the way I work is simply by having a cron entry run sa-learn on read messages in my inbox and spam folders. When a message is miscategorized simply move it to the appropriate folder and make sure it&#8217;s marked as seen:</p>
<p>find ~/Maildir -type d -maxdepth 1 -mindepth 1 ! -iname .Trash ! -iname .Spam ! -iname .unblocked-spam ! -iname .junk -exec find {}<br />
-type f -mtime -3 -name \*S \; | sa-learn &#8211;ham -f -</p>
<p>find ~/Maildir/.Spam/cur/ -name \*S | sa-learn &#8211;spam -f -</p>
<p>Note that this approach assumes you use a Maildir-based IMAP server; for a pure IMAP approach I&#8217;ve actually used the Perl Mail::Box module to make an IMAPS connection and loop over the appropriate mailboxes - the only drawback to that approach is that it requires you to either run it interactively or store your mail password in a file (yech).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
