Quoting Ben Lutgens (blutgens at sistina.com): > > design does not lead to a distributed processing model. The bottleneck will > > always be the mbox file and the write-exclusive lock to it. > > Yeah, too bad there's not a filesystem that supports byte-range locking > (that I know of) A better solution, IMHO, would be to strip the archiving part of mailman out and make it a seperate process. Thus, you'd be able to distribute the receiving/delivery and archiving/web processes. The hard "hit" on the list server is appending files to the huge mbox files. But the next hardest "hit" is all the search engines spidering the archives. -- Minneapolis St. Paul Twin Cities MN | Phone : (952)943-8700 http://www.mn-linux.org Minnesota Linux | Fax : (952)943-8500 Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9