> Thomas Smith wrote: > >>I converted all of my mbox mailboxes to mbx. I've noticed an increase >> in performance for my web-based IMAP client. However, I continue to >> have a problem that existed prior to the conversion. >> >>As I understand it, mbx is more memory efficient than mbox. This being >> the case, shouldn't it consume less RAM while a mailbox is being read >> by an IMAP client? This doesn't seem to be happening in my situation. >> >>For example, I use SquirrellMail for webmail. There are system-wide >> resource restrictions on RAM usage preventing any user from utilizing >> more than 8 MB of RAM via SquirrellMail. >> >>My Sent folder would always exceed this amount when I selected "View >> All"--there are over 3700 emails stored there. I continue to get the >> error after the conversion to mbx. >> >>Am I missing something or did I misinterprete what I read? >> >> >> >> > why don't you see if you can use something like cyrus-imap instead of > UW-imap. I found it's much better. I started using UW when I first > started working on linux. But after a while, I learned cyrus is a much > better choice for performance and reliability. > At least that's my opinion......see for yourself.
>From what other posters have written, it doesn't seem to be an IMAP server issue. Rather, it's a SquirrellMail and PHP issue. SquirrellMail is caching data in RAM and PHP's RAM restrictions are causing problems when SquirrellMail loads large mailboxes. I think a better choice for my situation would be to change webmail clients to something more efficient. Or find ways to fine tune SquirrellMail to reduce or eliminate these problems. That said, as I've posted previously on another thread, my web hosting provider uses a mixed OpenSource and proprietary setup. This makes it difficult to load "custom" software. The decision I made was to optimize what they've provided me to work with.
