From: bdwalton@gmail.com (Ben Walton)
Subject: [sup-talk] sent source
Date: Wed, 6 May 2009 20:02:26 -0400 [thread overview]
Message-ID: <f96e0240905061702m43899549p5ea53b5b6c478b02@mail.gmail.com> (raw)
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 <bdwalton at gmail.com>
"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
---------------------------------------------------------------------------------------------------------------------------
next reply other threads:[~2009-05-07 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 0:02 Ben Walton [this message]
2009-05-07 13:23 ` William Morgan
2009-05-07 21:57 ` Ben Walton
2009-05-09 2:10 ` Ben Walton
2009-05-09 13:01 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f96e0240905061702m43899549p5ea53b5b6c478b02@mail.gmail.com \
--to=bdwalton@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox