On Tue, Sep 10, 2002 at 11:32:14AM -0600, Carl Baldwin wrote:
Well, I have received plenty of answers about how to use mutt with
imap. This works somewhat. Here are some problems with using mutt
with imap that I've encountered.
- It doesn't work with the mutt 'tunnel' variable. imapd should run
by calling it from the command line and read/writing from its
stdout/stdin. The tunnel variable specifies a command to be
executed to run an imapd in this way on a remote (or even local)
machine. mutt cannot login when using this method.
You don't need the mutt tunnel. Here's an excerpt from my .muttrc.
# Can be imap instead of imaps if you want.
- I really want to run mutt on my maildir directories without going
through imap. mutt is very fast in handling maildir directories
especially doing regular expression searches and while imap is great
for remote access to a mailbox I'm sorry to say that when I'm on a
machine where the mailboxes are local imap slows this down
Mutts pretty fast at handling imap, too. However I can see what you mean
about it being slower at actually having to do regexp searches through
PS I guess at this point I'm not really looking for a short term
solution. I'm looking for someone who knows something about the
subject who might be able to tell me why things were done the way they
Mostly because that's what happened. Djb came up with maildirs, which
just started out as a mail storage format and different folks found
different ways of extending it. Oh, well. If you wrote an RFC with
interoperability and talked the the various implementors and they
liked it, you could, perhaps, see some changes over the next year or
two. Personally I'm pretty happy with using an IMAP server as my mail
store and letting it worry about these things.
The 5 year plan:
In five years we'll make up another plan.
Or just re-use this one.