James Ervin <listuser(_at_)kites(_dot_)org> writes:
I have been getting the classic ^rom (^ denotes start of line and is not
actually a character I am finding in the mail file) at the beginning of a
line in many of my mail boxes. This is described as a file locking problem
in most of the docs due to the one second delay from writing the "F" and
the "rom". So I added a lock to the final delivery:
:0:
$DEFAULT
Since you're using the normal mbox-style spool, procmail uses dotlocks
when it performs its implicit delivery. If that really is the last
recipe in the rcfile, you can remove it completely and let procmail's
implicit delivery handle it for you.
Which gives me a lock when procmail attempts to deliver the mail at the end
of my recipes (no other recipes deliver mail, they just add headers or
redirect mail off site). I appear to be getting locking:
...
But, I still get several ^rom lines in many mail boxes several times a
week. This is driving me nuts. I host mail for several domains and am
facing some angry users who are getting trashed email.
Okay, so procmail is using dotlocks and some form of kernel lock (check
the output of "procmail -v"). What are the _other_ programs that touch
the mailspool using, do they all have at least one method in common, and
if NFS is involved are you sure that that locking method works reliably
over NFS?
Philip Guenther
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail