On 2014-08-22 07:52, Linda Walsh wrote:
Carlos E. R. wrote:
procmail: Couldn't determine implicit lockfile from "/usr/lib/dovecot/dovecot-lda"
It also says this about that error message:
Couldn't determine implicit lockfile from "x" There were no `>>' redirectors to be found, using simply `$LOCKEXT' as locallockfile. .... :0 aw: | $DELIVER -m _Lists/D-os-en
It knows that there is a pipe , so it looks for the redirect to file at the end of the line to find out what is the destination "folder" of the recipe to create a lock with that name, and not finding one, it simply creates one with the default name of ".lock", which ends being a global lock and breaks parallelization of procmail....
---- This is why I never converted to procmail...ARG!...
Is that for a maildir format?
Nope.
I.e. if you are delivering messages to a directory, doesn't sound like mbox, but if it's a dir, do you need locking?
It is an mbox file: "_Lists/D-os-en". There is no ending "/", so it is mbox, not maildir.
(app would use open+excl to get uniq filename lock)...
If you are relying on specific filenames in the dir, why aren't they in the recipe?
But they are. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)