Randall Gellens on Fri 30/11 15:48 -0800: > > Based on our past testing, and knowing that some customers leave > > multiple machines checking POP every few minutes, we're fairly sure > > that if somebody starts a webmail (or any other) IMAP session on one > > of those accounts, with qpopper running in server mode, their > > mailspool will be corrupted in minutes. > > Someone (and I apologize for forgetting who that was) suggested an > option for Qpopper to hold the spool lock for the duration of the > session.
Yes that was me, I did end up starting at a patch but then after some tracing I saw that it was still unlocking the spool in the middle, I missed something in the locking code...I was running through gdb and then I got distracted and never finished it. If you want to take a look at what I had, here you go...if you finish fixing it please let me know... > That might be a good way around this problem, assuming IMAPD locks the > spool. If I remember right, the UW imapd uses a hitchpost-style dotlock out of the box and needs to be hacked to use the advisory kernel locks. It has been a while, I'm doing different stuff now.
