As Bryan said, specify a path. You may also like to know that you can make backups of mail with procmail... and commenting the heck out of procmail is good. In fact, I should put more comments in mine. Here's my user-level .procmailrc, in the interest of completeness: MAILDIR=$HOME/mail DEFAULT=/var/spool/mail/jack LOGFILE=$HOME/Procmail/log PMSRC=$HOME/Procmail VERBOSE=no LOGABSTRACT=yes LINEBUF=8192
# Create a backup cache of 50 most recent messages in case of mistakes LOGABSTRACT=no :0 c $PMSRC/backupmail :0 ci | cd $PMSRC/backupmail && rm -f dummy `ls -t msg.* | sed -e 1,50d` # Anti-spam measures. # SpamAssassin rule # The condition line ensures that only messages smaller than 250 kB # (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam # isn't bigger than a few k and working with big messages can bring # SpamAssassin to its knees. # Sourceforge and some other sites have started to run SpamAssassin on # their own mail, so this rule lets us skip re-running it here. :0fw * < 256000 * !^X-Spam-Flag: YES | /usr/bin/spamc # Mails with a score of 15 or higher are almost certainly spam (with 0.05% # false positives according to rules/STATISTICS.txt). Let's put them in a # safe place, like /dev/null # After a few days, I'm adjusting this down to 10. :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\* /dev/null # Sometimes Mickeysoft users will send attachments hidden inside of TNEF files. # This script translates those back to regular MIME attachments. :0fw | /usr/local/bin/tnefclean.pl -f On Wed, 2003-10-15 at 08:58, Bryan Phinney wrote: > On Wednesday 15 October 2003 11:26 am, Praedor Atrebates wrote: > > I just do not ever see messages that pass through spamassassin regardless > > of whether they are spam or not. > > > > My current /etc/procmailrc contains: > > ------------------------------- > > > > :0: > > > > * !<email address> > > * !<list address> > > * !<etc, etc> > > * <256000 > > > > | spamc -f > > > > -------------------------------- > > I would suggest changing this slightly to | /usr/bin/spamc -f instead, make > sure that you are explicitly giving it the command just in case your path > variables aren't set right and it can't find the command or worse, finds the > wrong one. > > Also, is the procmail lockfile working with SpamAssassin. I always get error > messages when SpamAssassin runs as root and Procmail tries to use the default > lockfile, usually I just don't use a lockfile with SA since by the time mail > gets to that, I want it to pass through all remaining recipes. (that would > be the trailing ":" character on the recipe. Mine just shows as: > > :0f > * <256000 > | /usr/bin/spamc -f -- Jack Coates Monkeynoodle: A Scientific Venture...
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
