Re: A viable mutt

[Nicolas KOWALSKI <nicolas.kowalski@gmail.com>]

On Wed, Aug 20, 2008 at 04:19:57PM -0700, Steve Lamb wrote:
> 
>     One of the many faults I find with mutt is its IMAP 
> implementation.  In two words, it fails.  Copying individual messages 
> from the current folder to any other folder, especially trash, by 
> downloading the message and then uploading it back to the server over 
> the IMAP connection instead of issuing an IMAP copy operation is 
> horribly slow and inefficient.

Are you sure about this ?

In the mutt sources, imap/message.c, there is the function 
imap_copy_messages:

/* imap_copy_messages: use server COPY command to copy messages to another
 *   folder.
 *   Return codes:
 *      -1: error
 *       0: success
 *       1: non-fatal error - try fetch/append */
int imap_copy_messages (CONTEXT* ctx, HEADER* h, char* dest, int delete)


Indeed, when I copy one or several messages from one folder to 
another, the server log shows me mutt used a COPY command:

- one message:

<1219318281<a0045 UID COPY 9048 "Junk"
>1219318281>a0045 OK [COPYUID 1219310686 9048 3] Completed

- several messages:

<1219318299<a0046 UID COPY 9037:9048 "Junk"
>1219318299>a0046 OK [COPYUID 1219310686 9037:9048 4:15] Completed


- several messages at different positions:

<1219318385<a0087 UID COPY 9036:9039,9044:9048 "Junk"
>1219318385>a0087 OK [COPYUID 1219310686 9036:9039,9044:9048 16:24] Completed


It's all fine IMHO.

-- 
Nicolas