-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday, December 17 at 09:58 PM, quoth Steve Searle:
>> The way to test this is to see what happens when you use mutt's
>> <copy-message> function instead of <save-message> (by default,
>> copy-message is triggered by tapping C). When you copy a message
>> from a folder into the same folder, does your IMAP server produce a
>> duplicate message? If it doesn't, then we've found the problem:
>> it's not mutt, it's your IMAP server.
>
> Just to see what happnes (I am not the OP), I tried this myself. When
> trying to copy I get the following error message:
>
> imap_copy_messages [a0135 NO Can't copy mails inside same mailbox]?
>
> When trying to save I get the similar:
>
> imap_copy_messages [a0109 NO Can't copy mails inside same mailbox]?
>
> This is using a dovecot imap server on CentOS.
Interesting! I use a Dovecot (1.1.x) server on Debian, and it works
fine for me. Here's a snippet from my ~/.muttdebug0 file:
a0020 UID COPY 12393 "INBOX"
4< a0019 OK Idle completed.
4< a0020 OK [COPYUID 1173499967 12393 12399] Copy completed.
IMAP queue drained
4> a0021 IDLE
... it then goes about discovering that there's a new message.
While it may be interesting to find out why your server forbids a
perfectly legitimate operation like that, mutt ought to (and as far as
I know, *does*) notice that the COPY operation has failed and aborts
the <save-message> procedure at that point (i.e. does not then delete
the original).
It *appears* as though the OP's server is refusing to create a copy
(like your server is), but is (bizarrely) reporting success.
I suppose mutt could avoid this situation by simply refusing to copy
messages into the folder they came from, but that would be stupid -
sometimes I, the user, *want* to duplicate the message.
~Kyle
- --
It is not bigotry to be certain we are right; but it is bigotry to be
unable to imagine how we might possibly be wrong.
-- Gilbert Chesterton
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAklJeQ4ACgkQBkIOoMqOI16yjwCg0jPz8TXR3CZ/WNYqj8QK6jB7
TzoAn2bRsAAPm8CSNKBRO68XEFlgVaNz
=UKKI
-----END PGP SIGNATURE-----
