Penguin

Differences between version 13 and revision by previous author of SpamAssassin.

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 13 Last edited on Tuesday, June 7, 2005 5:56:25 pm by CraigBox Revert
Older page: version 11 Last edited on Sunday, January 9, 2005 12:42:46 pm by GreigMcGill Revert
@@ -1,7 +1,9 @@
 [SpamAssassin | http://spamassassin.apache.org] is a neat [Email] filter that tags incoming mails it thinks are spam. Its aggressiveness can be configured, and it comes with a decent default level. It's written in [Perl] and is licensed under the same license as Perl itself. You can use procmail(1) to run SpamAssassin, or you might want to use MailScanner to run it on all your incoming mail. You might even want to plug VipulsRazor into it. 
  
 (Note, this product will assassinate [Spam], but will leave [SPAM] well alone!) 
+  
+As of version 3.0, SpamAssassin supports [SURBL] natively.  
  
 ----- 
  
 !! How to make SpamAssassin run on your local e-mail machine (with [Evolution] in mind) 
@@ -115,4 +117,22 @@
  1; 
  </verbatim> 
  
 GreigMcGill has found that MaiaMailguard is an excellent meta tool for managing your anti spam solution. 
+  
+-----  
+!!Inappropriate ioctl for device in your debug logs under Sarge/Hoary  
+  
+<verbatim>  
+debug: using "/root/.spamassassin" for user state dir  
+debug: lock: 29656 created /root/.spamassassin/auto-whitelist.lock.firewall.itpartners.co.nz.29656  
+debug: lock: 29656 trying to get lock on /root/.spamassassin/auto-whitelist with 0 retries  
+debug: lock: 29656 link to /root/.spamassassin/auto-whitelist.lock: link ok  
+debug: Tie-ing to DB file R/W in /root/.spamassassin/auto-whitelist  
+debug: unlock: 29656 unlink /root/.spamassassin/auto-whitelist.lock  
+debug: open of AWL file failed: Cannot open auto_whitelist_path /root/.spamassassin/auto-whitelist: Inappropriate ioctl for device  
+</verbatim>  
+  
+You're using old format database files.  
+  
+The perl version change effected a change of the BDB version being used. The bayes_seen and bayes_toks fixes are BDB files and  
+can be fixed by doing an db4.x_upgrade on them. sarge/hoary use Berkely DB 4.2, and you can install the db4.2-util package. with HTML