If the logic below is correct - the reason the spamassassin rule works is because you're not writing to a spool, but filtering (piping) to a program.
-Rick -- Rick Johnson, RHCE - [EMAIL PROTECTED] Linux/WAN Administrator - Medata, Inc. (from home) PGP Key: https://mail.medata.com/pgp/rjohnson.asc ----- Original Message ----- From: "Brad Alpert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, November 17, 2002 4:51 PM Subject: RE: Procmail processing problem > 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 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
