> On Wed, 19 May 2004, Thomas Smith wrote: >> At the risk of being redundant, imap-utils *will* work for imap-2001a > > Yes > >> and >> is *required* as it's not bundled with this version of UW IMAP? > > No. You can use the modern programs (such as mailutil).
How do I get mailutil seperate from UW IMAP? I've looked at the FTP site and can only find imap-utils. >> Do newer versions of UW-IMAP require modifying the CREATEPROTO= >> variable in the osdeps Makefile? (This is suggested in the IMAP-FAQ.) > > If you want a different default for newly-created mailboxes, yes. Does this mean that mbx-formatted mailboxes will have to be manually enabled for each user account that's created if this value does not default to mbx? Is there a way to set the default in some other way? (I don't have access to the source from my hosting provider--see below for more info on this.) >> (It may seem odd that I'm using an older version of UW IMAP. Fact is, >> I'm using a hosting provider running Ensim WEBppliance Pro on Redhat >> 7.3. They're currently testing more current versions of Ensim on >> Fedora Core 1--hopefully they'll roll it out soon as it uses more >> current versions of UW IMAP.) > > Why can't you just install an updated version from the UW FTP server? Ensim uses a proprietary API that enables UW IMAP to chroot to a domains' "root" directory. (Every domain has its own chroot environment. Their setup thus enables every domain to have their own /etc/passwd, /etc/group, /etc/procmailrc, and so on.) My concern is twofold: 1) In order to upgrade their UW IMAP install, I'd have to install the new RPMs on the host server (which is dedicated to me), update existing domains' chroot environments, and update the template filesystem so that the new, current UW IMAP binaries are copied and/or hardlinked to newly created domains. 2) Some users have experienced problems after enabling maildir support on their accounts. The problems typically occurred after Ensim upgrades and/or updates and, in most cases, caused wierd mail problems such as the server no longer understood maildirs and started writing files to mbox. This isn't a good senerio for a production environment. My goal is to enable a more efficient mailbox protocol than mbox while making as few server modifications as possible. I have yet to implement the mbx protocol so I'm not certain what changes need to be made to an account to enable it. It appears to me that there are only a couple, though.
