32 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: OpenBSD 3.2 breaks Co...
FromSent OnAttachments
Sam VarshavchikJan 13, 2003 3:46 pm 
D. J. BernsteinJan 13, 2003 6:11 pm 
Sam VarshavchikJan 13, 2003 9:11 pm 
Russell NelsonJan 13, 2003 9:46 pm 
Sam VarshavchikJan 13, 2003 10:19 pm 
Russell NelsonJan 13, 2003 11:11 pm 
Sam VarshavchikJan 13, 2003 11:35 pm 
mw-l...@csi.huJan 14, 2003 7:40 am 
Sam VarshavchikJan 14, 2003 3:22 pm 
mw-l...@csi.huJan 14, 2003 11:13 pm 
Sam VarshavchikJan 15, 2003 5:11 am 
Matthias AndreeJan 15, 2003 9:55 am 
Matthias AndreeJan 15, 2003 12:59 pm 
Matthias AndreeJan 15, 2003 1:36 pm 
Sam VarshavchikJan 15, 2003 3:11 pm 
Matthias AndreeJan 15, 2003 4:13 pm 
Sam VarshavchikJan 15, 2003 4:47 pm 
Johan LindhJan 15, 2003 10:16 pm 
Peter C. NortonJan 15, 2003 11:52 pm 
Bill MichellJan 16, 2003 1:30 am 
Johan LindhJan 16, 2003 2:00 am 
Bill MichellJan 16, 2003 2:28 am 
Matthias AndreeJan 16, 2003 2:28 am 
Matthias AndreeJan 16, 2003 2:45 am 
David LaightJan 16, 2003 3:14 am 
Sam VarshavchikJan 16, 2003 5:01 am 
Johan LindhJan 16, 2003 6:28 am 
Matthias AndreeJan 16, 2003 9:47 am 
mw-l...@csi.huJan 16, 2003 12:48 pm 
Sam VarshavchikJan 16, 2003 2:55 pm 
mw-l...@csi.huJan 17, 2003 12:30 pm 
Matthias AndreeJan 18, 2003 5:05 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: OpenBSD 3.2 breaks Courier, Qmail.Actions...
From:Russell Nelson (nel@crynwr.com)
Date:Jan 13, 2003 11:11:47 pm
List:net.sourceforge.lists.courier-maildrop

Click on this URL to check the validity of nel@crynwr.com: http://q249.crynwr.com/nelson/1042528048.23966.63f797456aebb2fbab137777da5d7b5a

Sam Varshavchik writes:

Russell Nelson writes:

Sam Varshavchik writes:

Since filenames for messages in maildirs are generated based on the combination of the pid, and the current time, in seconds, there is now a race condition that will result in loss or corruption of mail. This breaks Courier and Qmail.

Not for qmail, it doesn't. In the unlikely event that corruption would occur, qmail-local sleeps two seconds and tries again. At that point, the pid is still the same and the time is different.

How exactly would qmail-local (which started at T+900 milliseconds) know that it needs to do that; when at T+700 milliseconds an app moved a file carrying the same filename from new to cur, and THAT file was delivered to new by another qmail-local process that had the same pid, but which exited at T+500 milliseconds?

Ahhhh, I see the problem. It's a definitional one, not a coding one. There's two things which are being assumed which are now seen to be not true. Various bits of code assume "that a file which is unique in one Maildir dir will be unique in all of them." Other bits of code assume that "No pid will be reused in the same second".