pine slower than mutt on local Courier IMAP?

pine slower than mutt on local Courier IMAP?

Post by Matej Cep » Mon, 28 Jul 2003 23:41:52


I thought that one of advantages of pine (v. 4.44) over mutt
(1.3.28i) would be speed over IMAP folders. Now I have here local
courier-imap server and pine seems to be _much_ slower than mutt
over exactly the same messages? Any explanation, please?


        Matej Cepl

Matej Cepl,
GPG Finger: 89EF 4BC6 288A BF43 1BAB  25C3 E09F EF25 D964 84AC
138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488

As a rule of thumb, the more qualifiers there are before the name
of a country, the more corrupt the rulers. A country called The
Socialist People's Democratic Republic of X is probably the last
place in the world you'd want to live.
        -- Paul Graham discussing (not only) Nigerian spam


pine slower than mutt on local Courier IMAP?

Post by Vwake » Tue, 29 Jul 2003 07:39:34


>I thought that one of advantages of pine (v. 4.44) over mutt (1.3.28i)
>would be speed over IMAP folders.

Yes. Pine is known for it's imap functionality.

Quote:>Now I have here local courier-imap server and pine seems to be _much_
>slower than mutt over exactly the same messages? Any explanation,

No. Unless you provide facts/figures to back up your claim. Search the
archives of c.m.p and see if similiar problems have been answered

Tip --> Goto '' and select 'Groups' and type 'pine imap
slow' and hit 'enter'. You might want to try different variations of the
word slow like 'slows', 'slower', 'slowest', etc



pine slower than mutt on local Courier IMAP?

Post by Steve Huber » Wed, 30 Jul 2003 07:05:03

The man who wrote the code is not here for a few weeks but the suspicion
would be that pine is having trouble dealing with the responses from the
Courier IMAP server. Pine is probably having to download the messages to
do the search locally because of something that does not match the IMAP
standards in the response from the server.

If you enable more debugging in pine (pine -d9) we could probably see that
happening in the debug file.

Networks and Distributed Computing, Univ. of Washington, Seattle


1. mutt and local Maildir++ spool that conforms to courier's "standards"


we are currently converting from an old sendmail/qpopper based setup
(which I never used, my e-mail gets forwarded to my personal box via
SMTP) to a exim/courier-imap/pop based setup wich all employees
(including me *g*) will use. At the moment, I use mutt to access my
local e-mail spool via IMAP; mutt is running on the mail server

However, I'd like to get rid of that IMAP step because I tend to get a
lot of _LARGE_ messages (for example, one of my boxes decided to send
me a 100 MB mail last night which took me two minutes to delete since
mutt read in all the message over the IMAP link before giving me the
opportunity to delete). These operations tend to be a _LOT_ faster
when mutt is directly operating on the local Maildir.

However, the layout that Courier IMAP needs for proper access to the
folders/subfolders makes a lot of mutt's features uncomfortable and/or
even unuseable. That format is described in
Basically, it requires that all folder names start with a period, and
subfolders are named with the slash replaced with a period too. Thus,
a folder that can be accessed via IMAP as INBOX/internal/servers/mail
is physically located in $MAIL/.internal.servers.mail. Additionally,
courier-IMAP requires that all folders are located directly below the
system maildrop. Thus, the system maildrop maildir would be $MAIL,
giving $MAIL/{new|tmp|cur} directly besides the folders and subfolders
in the IMAP mailbox.

When accessing a mailspool conforming to courier's rules directly with
mutt, it impossible, for example, to use the folder browser, all
folder activity is to be done by directly typing the folder name
including the leading period, only assisted by tab completion. This is
a severe loss of useablility for the mutt user. How hard would it be
for mutt to directly support path delimiters other than "/", making
the browser support folders and subfolders in a maildir++, and saving
the user from typing "c=." instead of simply "c=" to change a mailbox.
I even find the mandatory prefix of "=" to avoid mail being saved to a
path relative to the home directory annoying.

I'd like to hear comments about these issues. Thanks in advance.


-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber          |   " Questions are the         | Mailadresse im Header
Karlsruhe, Germany  |     Beginning of Wisdom "     | Fon: *49 721 966 32 15
Nordisch by Nature  | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29

2. Ideal Cache size for Caviar 250M / 64k cache?

3. Pine filters and Courier IMAP

4. New York City - CCIE Study Group

5. Pine 4.44 and Pushing pinerc to Courier IMAP


7. Pine, remote courier IMAP server, generic client login

8. Postscript Conversion?

9. One more whine with pine -- non-Search over Collection on Courier IMAP

10. PHP IMAP->Courier-IMAP problem: imap_expunge()

11. Maildir/ IMAP server (NOT Courier-IMAP)

12. Directory structure restoration from cyrus-imap to courier-imap