Thanks for the help. Tried all of the suggestions, worked like a charm.
Dennis
Philip Guenther wrote:
dennis <dennis(_at_)pipper(_dot_)net> writes:
Had procmail working on Mandrake 8.2, now on Mandrake 9, it won't filter
and everything appears the same. Plus the logfile doesn't get written
to. I'm trying to use Postfix/Fetchmail/Procmail/Courier-imap
Is postfix properly configured to invoke procmail to perform local
delivery?
Here is the .procmailrc
PATH=/usr/bin:/bin:/usr/local/bin/:/usr/X11R6/bin
Remove that line: you shouldn't alter PATH unless there's something
actually missing from it or the order is wrong.
...
LOCKFILE=$PMDIR/lockfile.lock
This is almost certainly an error in understanding or completely
unnecessary. To quote the procmailrc(5) manpage:
LOCKFILE Global semaphore file. If this file already
exists, procmail will wait until it has gone
before proceeding, and will create it itself
(cleaning it up when ready, of course). If
more than one lockfile are specified, then the
previous one will be removed before trying to
create the new one. The use of a global lock-
file is discouraged, whenever possible use
locallockfiles (on a per recipe basis)
instead.
There's nothing in the rcfiles you quoted that require a global lockfile,
so you should not set LOCKFILE.
MAILDIR=$HOME/Maildir/
Procmail's MAILDIR variable has *nothing* to do with the maildir mailbox
format. What that assignment does is tell procmail to change its working
directory (ala the shell's 'cd' command) to $HOME/Maildir
If you want to tell procmail to default to delivering your mail to the
"$HOME/Maildir" directory, treating it as a maildir folder, then you
need to set the DEFAULT variable:
DEFAULT=$HOME/Maildir/
If that is correct for all users on the system, then you should recompile
procmail with the correct default. That way it can properly check the
permissions and ownership on the folder
This is the rc.subs for testing right now only one recipe
:0 $LOCKFILE
* ^Subject:.#palm
.palm/
Remove the $LOCKFILE bit. This is a maildir folder, so you don't need
to do any locking on it; indeed, that was the driving force behind the
design of maildir! Besides, you left out the second colon, so procmail
is treating the value or $LOCKFILE as a series of recipe flags...
Philip Guenther
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail