From mboxrd@z Thu Jan 1 00:00:00 1970 From: bdwalton@gmail.com (Ben Walton) Date: Wed, 6 May 2009 20:02:26 -0400 Subject: [sup-talk] sent source Message-ID: Hi All, I wanted to poll for thoughts on how to handle a generic mbox as the sent source. My concern is how to deal with file locking...this is one of the nastier aspects of mbox files. The cop-out approach is to allow the user to select any mbox source configured as the outbox and admonish them not to use it for incoming mail too...that puts us in the same place as ~/.sup/sent.mbox is now. Doing this does open sup to user error though and the potential for trashed mboxes. The next option is to play with locks, but that's not straight forward at all. Dovecot, as an example, allows a configuration knob for the admin to set the order in which the different mechanisms are used. This works as long as all of the mbox consumers use the same sequence. There is still lots of room for error here (NFS, etc). Option 3 is to simply limit the mbox sent source to the SentLoader class which means that 'regular' mbox files available to the user can't be a destination for sent mail. None of these solutions is perfect, and all suck compared to their maildir or imap counterparts (I'm not even going to bother with ssh+mbox). What do other 'suppers' think about this? Thanks -Ben -- --------------------------------------------------------------------------------------------------------------------------- Ben Walton "With or without religion, good people can behave well and bad people can do evil; but for good people to do evil?that takes religion. " -Steven Weinberg ---------------------------------------------------------------------------------------------------------------------------