imapproxy maintains a stateful connection between the imap server and the web server, so that a reconnection/authentication to imap isn't needed every time the webmail user does something. Saves cpu cycles bigtime...

BTW: we use horde/imp for our webmail

Jeff Earickson Colby College

On Wed, 7 Sep 2005, Marc Perkel wrote:

Date: Wed, 07 Sep 2005 06:29:47 -0700 From: Marc Perkel marc@perkel.com To: Jakob Hirsch jh@plonk.de Cc: dovecot@dovecot.org Subject: Re: [Dovecot] web-based mail

Jakob Hirsch wrote:

...

...

Now I want to setup and web-based in addition to the default pop3 and imap client access - what u guys can recommend?

depends on how much functionality you want. I like squirrelmail, it's easy to set up, fast and extensible.

And if you have lots of users, you should also consider adding imapproxy.

What is imapproxy and why do I want it?

-- Marc Perkel - marc@perkel.com

Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

I didn't install it, our web guy did. I don't think it took him too long, and no there is no downside that I'm aware of. Jeff

On Wed, 7 Sep 2005, Marc Perkel wrote:

Date: Wed, 07 Sep 2005 06:45:32 -0700 From: Marc Perkel marc@perkel.com Cc: dovecot@dovecot.org Subject: [Dovecot] imapproxy

Jeff A. Earickson wrote:

...

imapproxy maintains a stateful connection between the imap server and the web server, so that a reconnection/authentication to imap isn't needed every time the webmail user does something. Saves cpu cycles bigtime...

BTW: we use horde/imp for our webmail

Jeff Earickson Colby College

Is it hard to install? Is there any down side to it?

On Wed, 2005-09-07 at 06:45 -0700, Marc Perkel wrote:

...

imapproxy maintains a stateful connection between the imap server and the web server, so that a reconnection/authentication to imap isn't needed every time the webmail user does something. Saves cpu cycles bigtime...

BTW: we use horde/imp for our webmail

Is it hard to install? Is there any down side to it?

Just don't let regular users connect to it. Its design is to run everything in one process, so a security hole in it could give the attacker full access everyone's IMAP traffic. If only trusted webmail app can access it, there are a lot less potential ways to break it.

On Tue, 13 Sep 2005 11:04:29 -0400 Jonathan Vanasco wrote:

We used horde based mail until it started having severe browser issues with some versions of MS IE

Then we moved to ISMail, which worked until MS patched IE, then it broke too

So we had some users on horde and some on ISMail

that was annoying, people kept forgetting what to use

so then we moved to Squirrelmail, which has no features really, other than working right

The issues above weren't with horde or ISMail - although I REALLY liked ISMail - it was with stupid people internally who didn't keep their browsers up to date, and MS for creating new bugs when fixing old ones

i haven't had any issues in almost 2 years of squirrelmail

In the "For what its worth" department, if you have MS IE users and are providing SSL to them (like say, via https:), you *REALLY* need to know and understand IE's SSL bustedness with regard to keep-alives and such:

http://www.modssl.org/docs/2.8/ssl_faq.html#ToC49

Addressing that fixed all the problems I had with IE users a while ago. Horde just happens to hit that magic condition a lot with IE. After turning keepalives off for MSIE, complaints stopped about Horde not working.

-Jeff

--

Jeff Ballard ballard@engr.wisc.edu 608-265-5090 Unix Systems Manager, Computer-Aided Engineering Center