Subject: switching from IMAP2.2bis to IMAP4rev1

From: Martin Spohn <[email-masked]>
Date: Mon, 17 Mar 1997 14:19:41 +0100 ()

Dear all,

last week I changed the IMAP server from IMAP2.2bis to IMAP4rev1 from UW. 
After that the performance was so bad (time to open a not too big IMAP
folder: some minutes, time to write the sent copy to an IMAP folder up to
15 minutes) that I had to switch back to IMAP2.2bis. 

These delays mainly occured with pine 3.91 clients. 
Is there an explanation for this behaviour? 
Does it depend from the client version?
Did anybody else experience this loss of performance when switching to
IMAP4?

TIA
------------------------------------------------------------------------------
Martin Spohn                     |
Universitaet Tuebingen           Z                         Tel. 07071 29 76970
Zentrum fuer Datenverarbeitung   D          E-mail: [email-masked]
Abteilung Netze                  V                         Fax: 07071 29  5912
Brunnenstr. 27, 72074 Tuebingen  |
------------------------------------------------------------------------------

---

From: [email-masked] (Carl W. Bell)
Date: Tue, 18 Mar 1997 11:38:26 -0600

In article
<[email-masked]>,

>Did anybody else experience this loss of performance when switching to

We encountered a small problem after installing UW's IMAP4rev1 server that
caused significant delays while opening folders with IMAP clients other
than pine.  In env_init() (within the file env_unix.c) calls are made to
getpwnam() to get the home directories for the accounts ftp, imappublic,
and imapshared.  We don't have those accounts on our system, but because
our /etc/passwd file is fairly large, it takes a while to search it only
to return nil.  I commented out the following code...

/*
   if (!ftpHome && (pw = getpwnam ("ftp")))
      ftpHome = cpystr (pw->pw_dir);
   if (!publicHome && (pw = getpwnam ("imappublic")))
      publicHome = cpystr (pw->pw_dir);
   if (!sharedHome && (pw = getpwnam ("imapshared")))
      sharedHome = cpystr (pw->pw_dir);
*/

...and things seem to be working ok.  Note that doing so might cause problems
elsewhere. (I haven't taken the time to really look into into it.)  A better
solution would probably be to create those accounts and make sure that they
are somewhere at the top of /etc/passwd.

-cb

_____________________________________________________________________________
Carl W. Bell                          <http://ackmo.baylor.edu/files/cb.html>
Senior Analyst/Programmer             Baylor University CCIS - Client Systems