Sorry, I wasn't clear. The .forward example I gave was just to show that the .forward file was, in fact, getting invoked. (I thought someone had said that the .forward file is not invoked by evolution when reading mail.) I will, of course, use the simpler example .forward file that you mentioned when I get this all figured out and working. But just for this experiment I ran spamassassin directly from the .forward file because I wasn't sure if procmail was running correctly.
Even with the simpler .forward file, I can't get spamassassin to work. Any idea on what the log messages from procmail mean? Or how to fix them? Jack V. On Mon, 2003-03-10 at 17:41, Aram Mirzadeh wrote: > If you are already using procmail to filter through spamassassin why are > you trying to force it through with your .forward file? > > .forward should just be: > > "|exec /usr/bin/procmail" > > That's it folks. > > Let the scripts inside of your procmail receipts do the other work. > > Aram > > On Mon, 2003-03-10 at 19:49, Jack Veenstra wrote: > > It seems that the .forward file does get invoked when clicking the > > "Send/Receive" button in Evolution. > > > > I tried this .forward file: > > > > > > "|exec /usr/bin/procmail -f-", "|/bin/cat >> > > /user/veenstra/temp.mbox", "|/usr/bin/spamassassin -P >> > > /user/veenstra/temp.spam" > > > > > > And it copied the mail to "temp.mbox". It also created a file called > > "temp.spam" but it was empty. > > > > It also seems to call procmail. I got a logfile with the following > > messages in it: > > > > procmail: [6480] Mon Mar 10 16:26:19 2003 > > procmail: Assigning "LOGABSTRACT=all" > > procmail: Assigning "PATH=/bin:/usr/bin:/sbin:/usr/sbin" > > procmail: Match on "< 256000" > > procmail: Locking "spamassassin.lock" > > procmail: Executing "/usr/bin/spamassassin" > > /usr/bin/spamassassin: /usr/bin/spamassassin: cannot open > > procmail: Error while writing to "/usr/bin/spamassassin" > > procmail: Rescue of unfiltered data succeeded > > procmail: Unlocking "spamassassin.lock" > > procmail: No match on "^X-Spam-Status: Yes" > > procmail: Bypassed locking "/var/mail/veenstra.lock" > > procmail: Assigning "LASTFOLDER=/var/mail/veenstra" > > procmail: Opening "/var/mail/veenstra" > > procmail: Acquiring kernel-lock > > procmail: Notified comsat: "[EMAIL PROTECTED]:/var/mail/veenstra" > > >From [EMAIL PROTECTED] Mon Mar 10 16:26:19 2003 > > Subject: ONCE IN A LIFETIME!!! > > Folder: /var/mail/veenstra > > > > The error messages imply that either procmail or spamassassin is > > trying > > to write to /usr/bin/spamassassin. Why is that? My .procmailrc file > > looks like this: > > > > SHELL = /bin/sh > > MAILDIR = $HOME/Maildir > > LOGFILE = $HOME/Maildir/_logfile > > VERBOSE = yes > > LOGABSTRACT = all > > PATH = /bin:/usr/bin:/sbin:/usr/sbin > > > > :0fw: spamassassin.lock > > * < 256000 > > | /usr/bin/spamassassin > > > > :0: > > * ^X-Spam-Status: Yes > > probably-spam > > > > > > Any help on how to fix this? > > > > Jack V. > > > > _______________________________________________ evolution maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/evolution
