If I use a .forward like this, will procmail look for /etc/procmailrc if it doesn't find the file specified? TimH > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Patrick R. Wade > Sent: Thursday, August 30, 2001 11:21 AM > To: [EMAIL PROTECTED] > Subject: [EUG-LUG:2579] Re: procmailrc > > > On Thu, Aug 30, 2001 at 11:02:49AM -0700, Tim Howe wrote: > >Return-Path: <[EMAIL PROTECTED]> > > > >I already know that it is reading the system-wide rc file > first through > >a simular experiment. The section of the manpage that seems > to support > >this is the following: > ><quote> > >If no rcfiles and no -p have been specified on the command line, > >procmail will, _prior_ to reading $HOME/.procmailrc, > interpret commands > >from /etc/procmailrc (if present).... > ></quote> > > > >But the man page says -p is to Preserve any old environment. > >Not sure what that is getting at, so I didn't test it. > > Hm; looking further at that and at the synopsis in the > beginning of the > manpage, it seems to me that you can specify your .procmailrc on the > command line, so that the "If" condition is not met (i.e., an rcfile > is specified, so the /etc/procmailrc is not read first). > > >> >This is my .forward > >> >---- > >> >"|IFS=' ' && exec /usr/local/bin/procmail -f $p&&exec $p > >> -Yf-||exit 75 > >> >#thowe" > > This would then be > > "|IFS=' ' && exec /usr/local/bin/procmail $HOME/.procmailrc > ||exit 75 #thowe" > > > You lose some of the rewrite code, but i believe you can put > it into the > .procmailrc file; or you could experiment with gradually > adding it back. > > -- > "If my son wants to be a pimp when he grows up, that's fine > with me. I > hope he's a good one and enjoys it and doesn't get caught. > I'll support > him in this. But if he wants to be a network administrator, > he's out of > the house and not part of my family." Steve Wozniak, http://www.woz.org
