On Thu, Aug 02, 2001 at 11:42:48PM -0400, Tim Holmes wrote:
I was a very happy user of Procmail for some time, then suddenly it
decided that didn't want to work any more!
Here are the headers to my .procmailrc and the permissions.
PATH=`which procmail` # Procmail Path
Well, for starters I can tell you this is wrong. Certainly you want the
directory containing procmail in your path (although if it isn't, and it isn't
launched directly by your MTA or with an explicit path in your .forward, the
.procmailrc will never be read anyway) but there are other binaries on the
system, existing in other directories, that you will want on your path as
well. Such as Sendmail (or other MTA), formail and lockfile (should be same as
the path to procmail however), possibly various shell utilities. The path
inside your procmailrc should be pretty much the same as your shell
environment.
MAILDIR=$HOME/mail # You'd better make sure it exists
DEFAULT=$MAIL # Default mailbox
LOGFILE=$HOME/mail/procmail.log
This could be shortned to $MAILDIR/procmail.log
LOCKFILE=$HOME/mail/.lockmail
Likewise this to $MAILDIR/.lockmail
The machine is a Mandrake 8.0 machine. It appears that Postfix is
configured to automatically send mail through procmail. I have procmail
running and working fine on a RedHat 7.1 machine and a FreeBSD machine.
(I had to create a .forward for FreeBSD, but it works fine.) Can
anybody advise or provide any idea of where to look? Thank you!
Have you turned on verbose logging? Procmail IS processing your mail, else
there'd be nothing in the logfile. Did you add a recipe toward the top of your
procmailrc that might be catching everything (bad regexp maybe)?
--
Andrew Edelstein - andrew(_at_)pure-chaos(_dot_)com
http://andrew.pure-chaos.com
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail