+++ /dev/null
-In no particular order:
-
-* ~h searches download the entire folder, setting everything to \Seen in
- the process.
- --> Use SEARCH? or at least try to use .PEEK when doing scans. I've been
- thinking of going to always PEEK anyway, but then you'd have to store
- updates for every message you touched. Maybe a config option?
-
-* No checks are performed on long commands to make sure that they are
- still correct after they've been made to fit in their buffers.
- Tagged message sets can exceed the fixed space we've allocated for
- them in large mailboxes. Time to move to dynamic string allocation,
- at least for these commands.
-
-* Mutt doesn't handle timeouts or dropped connections gracefully. You
- may see occasional segfaults. Solving this cleanly requires some major
- architectural updates. Until that happens, I recommend you keep
- backup copies of messages you're composing from within your editor.
- Tommi Komulainen's keepalive patch for edit sessions may work for you,
- though. Committed to CVS late November 1999, I think.
-
-* Mutt is uninterruptible during socket calls. We should handle SIGINT.
-
-* Server copy currently doesn't take into account uncommitted changes in
- messages about to be copied. Sync first.
- --> walk tagged or individual message looking for changes, sync those?
- may require further additions to imap_make_msg_set and breaking up
- imap_sync_mailbox, otherwise shouldn't be too bad. Not currently a
- major priority, though - noone's gotten bit by this.
-
-* The mutt_pretty routines don't work well when the delimiter isn't '/'.
-
-Brendan Cully <brendan@kublai.com>
-Updated 20000731
-EXTRA_DIST = BUGS README TODO
-
INCLUDES = -I$(top_srcdir) -I$(top_srcdir)/intl
noinst_LIBRARIES = libimap.a
+++ /dev/null
-IMAP in mutt should be considered beta quality. For the most part it
-works well, but it is still not quite as stable or as full-featured
-as some of the other drivers. I believe it is now acceptable for
-daily use (and that's how I use it now, currently against Cyrus 1.6.24 and
-previously against UW-IMAP 4.7 and 2000).
-
-You may still lose some work if you are suddenly disconnected from your
-server (but your mailboxes should be fine). Currently accessing the same
-IMAP folder with multiple clients is not supported - it may work, but
-no guarantees. There are still several non-critical known bugs, see
-http://bugs.guug.de/ for the current list.
-
-You may also be disappointed in mutt's handling of very large IMAP mailboxes.
-To build the message index mutt must fetch a subset of headers from every
-message in the mailbox, which costs time and network traffic linear to the
-number of messages in your mailbox.
-
-Nevertheless in general mutt is quite a fast and fully-featured IMAP client.
-It tries to be polite to IMAP servers as well, opening few connections and
-avoiding needless polls of the server, unlike certain other popular IMAP
-clients by certain large corporations :)
-
-Mutt supports almost all official authentication and security protocols for
-IMAP, including SSL/TLS, native CRAM-MD5 and GSSAPI routines, and a SASL
-plugin which can handle just about everything else.
-
-Please report bugs to mutt-dev@mutt.org and/or brendan@kublai.com. Version,
-options, stack-trace and .muttdebug files are a plus.
-
-Brendan Cully <brendan@kublai.com>
-20010506