Differences between version 5 and revision by previous author of SpamAssassinNotes.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 5 | Last edited on Friday, June 23, 2006 11:15:00 am | by CraigBox | Revert |
| Older page: | version 3 | Last edited on Monday, July 4, 2005 4:11:46 pm | by PhilMurray | Revert |
@@ -1,8 +1,4 @@
-!![SpamAssassin] Notes
-
-----
-
!! How to make SpamAssassin run on your local e-mail machine (with [Evolution] in mind)
* get and install SpamAssassin, test that it works by piping a good email and a spam email through it
* check that fetchmail(1) works, write a <tt>.fetchmailrc</tt> file
@@ -39,17 +35,19 @@
<verbatim>
*/5 * * * * /home/localuser/bin/getmail
</verbatim>
-----
-
-The
ClamAV Plugin
+!! SpamAssassin's
ClamAV Plugin
This plugin submits the entire email to a locally running [ClamAV] server for virus detection. If a virus is found, it returns a positive return code to indicate spam and sets the header <tt>X-Spam-Virus: Yes ($virusname)</tt>. If you'd like to sort virus emails to a separate folder, create a rule looking for this header.
+
+This isn't necessarily the best way to run [ClamAV]; for example, your MailTransferAgent, if it has a method to call SpamAssassin, probably has a method to call [ClamAV] too.
+
It requires
* [ClamAV] installed so that scanning a mail with <tt>clamscan</tt> works
* the [File::Scan::ClamAV | http://search.cpan.org/dist/File-Scan-ClamAV/] [Perl] module
+
To install, create the files in <tt>/etc/mail/spamassassin/</tt>. You can adjust the default score of 10 in <tt>clamav.cf</tt> if you like. Restart the <tt>spamd</tt> daemon if you're using that, and you should be all set.
<tt>clamav.cf</tt>::
@@ -112,11 +110,8 @@
}
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
@@ -132,14 +127,12 @@
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
-----
!! I'm running spamassassin from my MTA, and I get the error <tt>spam acl condition: cannot parse spamd output</tt> or similar.
This occurs if you have upgraded perl, and not restarted spamd. Try restarting spamd and see if it solves the problem. It could also be a version mismatch, in which case you'll have to upgrade whichever process is calling spamassassin
-----
!! I'm running spamassassin on [Debian] and get this error <tt>Cannot open bayes databases /home/jimbobdobalina/.spamassassin/bayes_* R/O: tie failed:</tt> (or similar)
Fix:
@@ -155,7 +148,56 @@
</verbatim>
Restart spamassassin, and voila!
+!!Web based spam management
+
+[Maia Mailguard|http://renaissoft.com/maia/] is a web-based interface and quarantine management system for amavisd-new, which allows users to manage their own spam. It has all the pitfalls of amavis, but might suit your needs.
+
+!!Making Razor go
+
+Is Razor running?
+
+Uncomment it in /etc/spamassassin/v310.pre and you're effectively away. If you want to be able to submit, you have to [create an account|http://wiki.apache.org/spamassassin/InstallingRazor].
+
+!!Making DCC go
+
+Is DCC running? Have you uncommnented it in /etc/spamassassin/v310.pre?
+
+<verbatim>
+# spamassassin -t -D < /tmp/spam
+<snip>
+[8407] dbg: dcc: dccifd is not available: no r/w dccifd socket found
+[8407] dbg: dcc: check timed out after 5 seconds
+</verbatim>
+
+Default Ubuntu/Debian installation, SA probably can't find the <tt>dccifd</tt> file - add to /etc/spamassassin/local.cf:
+
+<verbatim>
+# Enable DCC
+use_dcc 1
+dcc_home /var/lib/dcc
+</verbatim>
+
+!!Making Pyzor go
+
+Is Pyzor running? Have you uncommnented it in /etc/spamassassin/v310.pre?
+
+<verbatim>
+# spamassassin -t -D < /tmp/spam
+<snip>
+[8615] dbg: util: executable for pyzor was found at /usr/bin/pyzor
+[8615] dbg: pyzor: pyzor is available: /usr/bin/pyzor
+[8615] dbg: info: entering helper-app run mode
+[8615] dbg: pyzor: opening pipe: /usr/bin/pyzor check < /tmp/.spamassassin8615OvQ1ymtmp
+[8617] dbg: util: setuid: ruid=0 euid=0
+[8615] dbg: pyzor: killed stale helper [8617]
+[8615] dbg: pyzor: [8617] terminated: exit=0x000f
+[8615] dbg: info: leaving helper-app run mode
+[8615] dbg: pyzor: check timed out after 5 seconds
+</verbatim>
+
+The old Pyzor server has disappeared. Locate .pyzor/servers (systemwide on Debian/Ubuntu, it's under /root/.pyzor/servers) and replace the contents with <tt>82.94.255.100:24441</tt>. Don't run <tt>pyzor discover</tt> again, as it will overwrite the contents with the broken server. (Thanks to [this Nabble post|http://www.nabble.com/Pyzor-issue-since-upgrade-to-3.1.3-t1742083.html] for the answer)
----
-CategoryAntiSpam CategoryNotes
+CategoryAntiSpam %%%
+
CategoryNotes
