> > As Mark would say, IMAP-2004 is ancient and there were many > > features/fixes introduced since then. For example, I don't think > > IMAP-2004 had "mix" format, which IMHO is a "must have" nowadays. > > _______________________________________________ > Mix format? Why is that a "must have" nowadays? ... > As for other features/work -- does anyone know if another UW project is > picking > up imapw? It seems to be fairly widely used. > > It seems that Cyrus IMAP is the only open-source alternative available > that has > any 'traction'? I've been unwilling to abandon the "mbox" format > compatibility > provided by IMAP -- though heaven knows, how many 3rd party open-source > plug-ins don't handle the format (w/rt "From ") correctly all the time.
Why are you sticking with mbox? IMAP storage involves metadata storage, and by using mbox you are forcing imapd to embed the metadata as data, which is awkward. Nor does uw-imapd index this format, so opening a mailbox for the first time is slow. http://www.washington.edu/imap/documentation/formats.txt.html mix improves performance dramatically, partly because the different kinds of (meta)data are stored in separate files, and so can be accessed with different locking arrangements. Files are also kept small to make modifications fast and backing up efficient. http://www.washington.edu/imap/documentation/mixfmt.txt.html > Not sure I know of many that do. I get "ribbed" by occasional mbox chomping > by Perl-scripts using CPAN modules and some derivations based on > Berkeley Mail > 8.x -- like the 'Nail' version that provides Mail/mailx drop-in support. > (Maybe that means I'm not 'ribbed' by chomping, but 'nailed'??)...:-| All the more reason to move away from mbox ASAP. imapd's snarfing mechanism provides an excellent way to migrate. For example, you can begin by rebuilding with CREATEPROTO=mixproto and then doing mailutil create INBOX as a user who does not already have an INBOX. The next time they access INBOX the contents of their unix/mbox maildrop will be converted and transferred to this new mix-format INBOX. Having changed CREATEPROTO will also mean new mailboxes they create will be in mix-format. Once you have convinced yourself this is working well enough, you can use mixcvt to convert other existing mailboxes. Alternatively, you can use mixcvt with the INBOX instead of creating it and letting snarfing do the conversion. There are some differences in the results between these approaches. Cheers, - Joel _______________________________________________ Imap-uw mailing list [email protected] https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
