> On Mon, 13 May 2002 15:00:46 +1000, Andrew Hatfield wrote: > > mbox is slow and not indexed > > That is certainly true. Oh yes.
> > > mbox is not robust or stable > > That is certainly not true. For all its (many) faults (and "many" can be > called an understatement), traditional UNIX mailbox format is probably the > single most robust and stable format ever devised. I have been experiencing (under numerous clients - OE, Mozilla, Outlook2K, Squirrel) I've experienced lost email quite regularly. Hence my comment. With large mailboxes (~25K mail items) system load can easily reach over 5 (PII 233, with SCSI disks), and that is just 2 users accessing 6 mailboxes at once. Also, you didn't answer any of the questions, just the comments. What headers will require their own fields? I was planning on something similar to CREATE TABLE tblMailbox_<User>_<Folder> ( ID tinyint (4) NOT NULL auto_increment, Message-ID varchar (50) NOT NULL, <other required fields>, <other headers>, <return paths>, <Body>, PRIMARY KEY (ID) ) Where the table name is created by the backend and User is the authenticated user and Folder is the individual subfolders (including INBOX, etc...). Am I missing something major here? Does this seem on the right track? What fields constitute <other required fields> ? -- Andrew Hatfield SecureONE - http://www.secureone.com.au/ President - South East Brisbane Linux Users Group http://www.seblug.org/ Development work available at http://development.secureone.com.au/
