[imp] ImapProxy at medium-sized installation.

Christopher Crowley ccrowley at tulane.edu
Wed Dec 11 16:24:31 PST 2002


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I tried implementing ImapProxy ( an imap persistence daemon designed
to work with IMP: http://www.kuleuven.net/projects/imapproxy/ ) on my
IMP webserver.  

The idea is great, instead of logging in to the mail server for each
e-mail message, an imap process is maintained on the mail server by
an intermediate daemon. 

But, after about 15 minutes of  use, ImapProxy hung. I saw it was
using substantial CPU, but wasn't able to gather much additional
data.  I plan to revist the test, dedicating an Ultra-60 w/ 2 CPU and
2Gb RAM server to the ImapProxy server.

Has anyone succesfully implemented ImapProxy in an environment of
1000 concurrently active sessions, and 6,000 daily IMP users?

The reason I am exploring this route is there appears to be a
constraint at the e-mail server in our installation.  IMAP clients
using Netscape, Eudora, and Outlook aren't perceiving delays.  But,
IMP users are seeing slow page load times on mail queries when the
IMAP server is busy.  The Apache server for IMP is providing rapid
page delivery, and the other Horde modules in use ( Kronolith, Turba,
Vacation, etc.) have sufficient performance.

Thanks in advance for any information you are able to share.

Christopher Crowley
TIS Network Services
Tulane University
ccrowley@tulane.edu
504.314.2535
PGP Key ID: 0x7CF18FDB

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>

iQA/AwUBPfe7G80q7cR88Y/bEQJpwwCaA+TixVT9TCM+vTcqIAQol0F1UgIAn367
07/diXA+dv6J/SUm5Efe2+O7
=rZmn
-----END PGP SIGNATURE-----



More information about the imp mailing list