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? 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? (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? (in case not obvious, I know nothing about procmail but thought I try some general Q's....) There are times I think about trying to get rid of my email script (1st written in perl ~ 89?). I certainly wouldn't design it the same way today... ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org