Christopher Crowley on Tue 9/04 14:49 -0500: > The locking mechanisms are not the same, and thereby there is no > coordinated locking system between qpopper and uw-imap.
If you use uw-imap with the mlock program from the UW imap-utils, building the IMAP server with LOCKPGM defined to it, it uses a hitchpost dotlock in the mail spool, just make it setgid mail along with mail writable spool dir. I think that should work, no? It appears that qpopper does use dotlocks in Qmaillock() at common/maillock.c:205. Better idea is to write an mlock replacement that uses flock() or fcntl with F_SETLK, but dotlock should work as long as only qpopper and uw-imap access your spool. Otherwise you definitely will see corruption if they don't cooperate and are run concurrently. also if you run server mode, all bets are off since the lock only occurs once at the beginning and then at the end of the dropcopy, so you have to turn that off. I still think the lock should surround the session and let MDA handle temporary errors, but maybe that is bad policy, I don't know.
