Uhm -- I believe MBX is mailbox format and that is the problem this guy is having. It does not support concurrent access because imapd is started via inetd for each access. Courier runs as a daemon and can handle any number of connections (more or less). As far as inodes go, it is up to the admin to setup the filesystem to handle that. You could use a different filesystem or perhaps format the partition with lots of inodes. I can say that I have had no trouble with inodes. All my mail drops into Maildir on my /home partition and it works great. I set quotas accordingly. Visi.com runs Courier IMAP on their primary mail cluster without trouble or incident. Tom Veldhouse ----- Original Message ----- From: "Scott Dier" <dieman at ringworld.org> To: <tclug-list at mn-linux.org> Sent: Wednesday, August 07, 2002 9:09 AM Subject: [TCLUG] Re: Concurrent clients and IMAP > On Wed, 2002-08-07 at 07:33, Thomas T. Veldhouse wrote: > > Try converting to Maildir format from mbox. In other words, cease using the > > Washington University wu-imap and instead use Courier. This runs as a > > daemon and will handle multiple connections to the same mailbox at the same > > time. It also has its own POP3 daemon if you want to enable it. > > Or, stop wasting your inodes and use MBX[*] with uw-imapd. I only use > Maildir on the client side because offlineimap forces me to. I should > look into running a local imapd instance and port offlineimap to talk > MBX too. Maildir sucks. Slow. MUA's don't act the same compared to > mbox or imap. Eats inodes. > > [*] Offer not valid on NFS. > > -- > Scott Dier <dieman at ringworld.org> http://www.ringworld.org/ > > _______________________________________________ > Twin Cities Linux Users Group Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list >