On Mon, Feb 13, 2012 at 01:24:25PM -0700, Michael M Slusarz wrote:
Except you are most likely NOT leveraging the truly interesting part of imapproxy - the ability to restore the IMAP connection state via the XPROXYREUSE status response. This is a significant performance improvement since it also reduces processing load on the client side (everything before/including authentication needs to be done whether using imapproxy or not, so there is no client-side savings for these commands).
Thanks for this info, good to know. I'll check with inverse/sogo if this is something they use/intend to use..
additional advantage. Note that the XPROXYREUSE-enabled MUA must be the exclusive user of the imapproxy instance for this feature to work correctly.
Not a problem. Assuming it doesn't also need to be the only imap user of the account/folder.
BTW: do you also have information on the state of select caching in the up-imapproxy? I got some very negative comments when googling it, and the changelog didn't suggest there had been any improvements since..
-jf