I lock everything, per `man procmailex`.
LOCKEXT=.lock
:0 w: nmh-workers/$LOCKEXT
* ^TO_.*nmh-workers
| rcvstore +List/nmh-workers
Per the man page:
Procmail can deliver to MH folders directly, but, it does not update
the unseen sequences the real MH manages. If you want procmail to
update those as well, use a recipe like the following which will file
everything that contains the word spam in the body of the mail into an
MH folder called spamfold. Note the local lockfile, which is needed
because MH programs do not lock the sequences file. Asynchronous
invocations of MH programs that change the sequences file may
therefore corrupt it or silently lose changes. Unfortunately, the
lockfile doesn't completely solve the problem as rcvstore could be
invoked while `show' or `mark' or some other MH program is running.
This problem is expected to be fixed in some future version of MH, but
until then, you'll have to balance the risk of lost or corrupt
sequences against the benefits of the unseen sequence.
:0 :spamfold/$LOCKEXT
* B ?? spam
| rcvstore +spamfold
Simon Burge writes:
> Hi,
>
> I use procmail and rcvstore to automatically sort my incoming mail, and
> twice in the last month I've had my context file get corrupted overnight
> and all following mail got dropped on the floor. From my procmail log
> file, I see entries like:
>
> rcvstore: eof encountered in field "904"
> rcvstore: context is poorly formatted
--
Randy Primeaux
[EMAIL PROTECTED]
