On Mon, 2004-08-09 at 12:46, Gregory Seidman wrote:
> On Mon, Aug 09, 2004 at 01:50:15AM -0700, Brian Nelson wrote:
> } On Sun, Aug 08, 2004 at 08:24:34PM +0200, John L Fjellstad wrote:
> } > Brian Nelson <pyro@debian.org> writes:
> } > >> > 6. It must have a decent expiry system.
> } > >>
> } > >> You don't need a mailclient to have a decent expiry system if you are
> } > >> using Maildir. Since all new mail goes into {MAILBOXNAME}/new and all
> } > >> read mail goes into {MAILBOXNAME}/cur, you can use this script to delete
> } > >> all read mail over a certain date:
> } > >
> } > > That's not necessarily true. OfflineIMAP puts all mail in cur.
> } >
> } > Well, if you were using offlineimap, I would think you would do the
> } > script on the imap server rather than the client.
> }
> } Modifying the backend Maildir behind the IMAP server's back is A Very
> } Bad Idea(tm)...
>
> Um, no, actually, it isn't. One of the big wins of maildir is that
> concurrent access does not require locking. There is no reason not to
> mess with the backend maildir when the IMAP server is running. Indeed, I
> can run mutt on the backend maildir, Thunderbird connected via IMAP, and
> squirrelmail all concurrently, and everything works just fine.
Actually, it'd be good if you ran some type of File Alteration Monitor
Daemon... if you know what I mean. But it is not absolutely needed.
--
greg, greg@gregfolkert.net
The technology that is
Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part