urgrue <urgrue(_at_)tumsan(_dot_)fi> writes:
it's me again.
looks like procmail uses /var/spool/mail/.<username>.lock
Nope. Procmail uses /var/spool/mail/<username>.lock
but my pop daemon uses /var/spool/mail/.<username>.pop
I doubt it. That's almost certainly 'merely' the POP server's temporary
file for holding the open mailbox, not the lockfile it uses while reading
and writing the spool file itself.
You should read your POP server's documentation and/or source and
find what kernel locking methods it uses, if any, and whether it uses
dotlocking at all. Compare that to the "procmail -v" output to see
whether they have an overlaping kernel lock method.
could this be the culprit? what can i do about it? it doesnt look like
either program lets me choose.
You may need to recompile one or both of the programs. However, if POP
daemon and procmail are both 'standard' for your distribution, then your
vendor should have verified that they work together.
procmail mailing list