On Thu, 16 May 2002, Jack Gao wrote: > MAILDIR=$HOME/mail
This just causes procmail to perform a "cd $HOME/mail". > DEFAULT=$HOME/mbox So far so good, although it might be easier to let imapd move the messages from the "real" spool file into the mbox file via the mbox driver. > LOGFIE=$MAILDIR/from Fie! That should of course say LOGFILE. Was this a copying error, or is it wrong in /etc/procmailrc? > LOCKFILE=$HOME/.lockmail Mark is correct that this is not right, but it has nothing to do with the choice of name. Assigning to LOCKFILE creates a global lockfile immediately at the time of the assignment; effectively you're serializing procmail -- no two procmail processes can run at once -- but this has *no* effect on locking out other programs, such as imapd, from accessing the mbox file. You should delete that LOCKFILE assignment. The final question is whether the delivery to DEFAULT is accomplished by falling off the end of the procmailrc, or whether there is an explicit recipe with $DEFAULT as the delivery target? In the latter case you will need to specify imapd-compatible locking in the recipe itself. In the former case procmail's default dot-locking strategy should be compatible with the way imapd does locking, once you get rid of the LOCKFILE setting. However, I'd still recommend that you *not* set DEFAULT and let imapd take care of moving the mail to the home directory.
