On Fri, 10 May 2002, Rick Block wrote: >Bart Schaefer wrote: >I want to allow the user to delete the message, so I can't just >disallow storing the \deleted flag. I really, truly, want >to distinguish user action COPY from user action MOVE. The >destination mailbox is not actually a message repository (hence, >moving a message there makes no sense and should be denied); copying >a message there has a particular side effect related to the message >being copied. You might argue this is outside the scope of imap4, >but allowing this is tremendously useful. The server can support
It's obviously not tremendously useful for the rest of the community! You are using the IMAP protocol to allow users to access a depository which isn't actually a message repository. You're already beyond the intended scope of the IMAP protocol! How can you expect changes to be made because of a policy in your non-standard backend? I'd like full rollback transaction support, because my backend is an Oracle database. And I'd like the protocol to allow compression and decompressing of objects, because my GUI allows users to compress messages. You are *completely* free to implement your own special-modified-hacked non-compliant IMAP server (there are *lots* of those around), with MOVE functioning /exactly/ like you want, but is it /reasonable/ for the protocol to meet /your/ needs? Andy -- Andreas Aardal Hanssen
