Most probably that's true. But wouldn't the log show a choke if it tried to write, and couldn't find the right folder?
I'm the only user on the machine, other than root. I wanted to get system-wide procmail going and finetune things next. I've changed the recipe to send the ^Subject:.*Test to /dev/null, and the emails still make it to the mail folder. So it would seem to me that the ruleset isn't operational, although things do seem to process otherwise. As I mentioned earlier, the rule that invokes spamassassin does pick up and process. I'm stumped. Brad > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Rick Johnson > Sent: Sunday, November 17, 2002 6:31 PM > To: [EMAIL PROTECTED] > Subject: Re: Procmail processing problem > > > Brad Alpert wrote: > > > Can you get any other recipe to work? And would > > > > > > :0: > > > * ^Subject:.* > > > spam > > > > > > catch your message? > > > > No it didn't. > > > > The only rule that works is the spamassassin one, in the sense that > > procmailrc properly calls it, applies the spam scores, and > then injects > > the message back. > > > > None of the pure procmail recipes have any effect. > > I'm going on a limb here - but aren't folder specific recipes only > appropriate in /home/<user>/.procmailrc? Otherwise > ~/mail/spam would need to > exist for everyone (assuming that MAILROOT=~/mail) > > -Rick -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
