I'm using imapproxy 1.2.2rc2 with Courier IMAP 3.03 and do not have such problems. I get an occassional error about the client closing the connection to soon but haven't noticed any problems in squirrelmail based on that so I pretty much ignore it now. 1.2.1 produced the same error. I have noticed that imapproxy will cause a few wierd behaviours every now and then. Most of them stem from the fact that Squirrelmail was written to assume a new connection is being made every time and imapproxy isn't really making a new connection each time, it's holding on to old connections. I had also tried imapproxy with another IMAP Server, Mercury/32 and found that it caused a number of weird errors and problems so I had to disable it (which is to bad because Mercury could use the boost, it's orders of magnitude slower than Courier with a heavy workload on each). You might just have to live without imapproxy, or give 1.2.2rc2 a try, I've found it to be fairly stable, it's mostly bug fixes if you disable the SELECT cacheing feature.
Jay -- Jay Lee Network / Systems Administrator Information Technology Dept. Philadelphia Biblical University -- I propose we leave math to the machines and go play outside. --Calvin Bojan Baros said: > Hello SM users... > > I recently installed imapproxy (1.2.1) on my Debian Unstable box, and > I am using it with the SM 1.4.2. > > For couple of days, everything worked perfectly, and I was enjoying > the benefits of the faster email browsing and page loads. Today > though, I started seeing some problems with "Protocol Errors", > specifically: > > May 6 11:03:00 Salsa in.imapproxyd[32212]: LOGIN: '"bojan"' > (217.160.226.22:54684) on new sd [12] > May 6 11:03:00 Salsa imaplogin: LOGIN, user=bojan, > ip=[::ffff:127.0.0.1], protocol=IMAP > May 6 11:03:01 Salsa in.imapproxyd[32212]: IMAP_Line_Read(): Protocol > error. Line begins with LF. > May 6 11:03:01 Salsa in.imapproxyd[32212]: Raw_Proxy(): Failed to > read line from client on socket 11 > May 6 11:03:01 Salsa in.imapproxyd[32212]: LOGOUT: '"bojan"' from > server sd [12] > > I disabled the proxy and pointed SM straight to imap, and everything > works perfectly (as you can see ;). > > Anyways, this is probably imapproxy problem, and I was wondering if > anyone ever ecountered it, knows how to resolve it or knows if the new > imapproxy version (currently in RC state) will fix this. > > > Thanks, > Bojan > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Sleepycat Software > Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to > deliver higher performing products faster, at low TCO. > http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 > -- > squirrelmail-users mailing list > List Address: [EMAIL PROTECTED] > List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 > List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
