Re: saving from IMAP folder F to F deletes
- To: mutt-users@xxxxxxxx
- Subject: Re: saving from IMAP folder F to F deletes
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Wed, 17 Dec 2008 16:18:24 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=BEpIqEXd/nnj5iseLVT5Zf6CFKg=; b=JHYP 6XMsG9TssjthriwY0UW/Rvc77Lc/LxuFCjB3KZ3rfE9m5ADoPNNS3pWzbtoog1aO jFEcQHexQTeNFmogds/FNQiFs9RL1PdpFxC+/t74p+PVf/E9QTjMvGMr3nUdeE4M Wylf5qvejkOM0rEpvRaoyUmp8yOgoPtLbwLBXhE=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=CnuNABjCuKy8/iuQlJCCuweF+2vhZjRl4bXeNNiLW3/JlRrBfaw+jaQ9IpJIbCrh0T1EIji5CERPQ/B+10LczbN/Hj2/Vyl/E8jmeKpPxA3ViASU+40eJCCcTbR+jO8Ofr9oBmDXO7+9N855jI2Dk2uAb/v+ej8NjbFRDV1MQ2c=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20081217215809.GA7440@xxxxxxxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20081217211513.GA14974@xxxxxxxxxxx> <20081217213529.GR927@xxxxxxxxxxxxx> <20081217215809.GA7440@xxxxxxxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.18 (2008-11-30)
-----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-----