> MOVE is unimplementable unless messages are stored in > a method that permits messages to be moved from one mailbox to another. > IMAP explicitly does not place such requirements upon the message store.
I must admit I do not understand that argument well. I gave just an example with possible implementation with maildir format - move file without reading it. But it does not mean that the mailbox format driver can actually copy the message to new mailbox and delete it from the old one, since it can do no better. Just an IO overhead, but this is up to admin to decide, what format he likes, and that's the main reason why people make out new formats - to let them support the features they need efficiently. But put that aside, it does not matter: Just a while ago there was discussion on this list regarding CAPABLITY command and the fact, that the capabilities can change after login time, when the message store format is already known and defined. I do not mind to have MOVE command as an extension, together with other fancy things which not all servers/message stores support. But to have it in base protocol would be nice. Just nice, not absolute must. > Even if added to IMAP, a MOVE command would *not* preserve > the UID (which some people say they want). It can't; the semantics > of UID preclude that. That's obvious, I agree. Cheers, Marek. -- ----------------------------------------------------------------- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/imap-list.html -----------------------------------------------------------------
