Re: IMAP changes timestamp when moving an article to another group

[Steinar Bang <sb@dod.no>]

>>>>> Steinar Bang <sb@dod.no>:


> Does anyone know what happened to this issue?

> I haven't dared expire or move stuff in my nnimap folders for the last
> year or so...

To summarize: When expiring, or moving with "B m" messages between
nnimap on a dovecot server, the date is displayed wrongly in other IMAP
clients.

The Date: header on the message itself is unchanged, but the
INTERNALDATE gets the time of the move/copy operation.

Dovecot allows the INTERNALDATE to be specified during a copy (see Timo
Siriainens last reply text in [1]), and the feature request is that nnimap
specifices the INTERNALDATE during a copy.

I've looked at the git log of nnimap.el and it doesn't look like
anything related to this has been done since august 2016[2].

In fact, these two changes from march 2016 may be the cause of the date
not being preserved on move/expiry, since Timo Siriainen seems to
indicate that dovecot by default preserves the INTERNALDATE in a MOVE
between folders on the same server (see Timo Siriainens first reply text
in [1]), from the git log of nnimap.el:

commit d5427e71da28856c5e43396a37ffd0c906947499
Author: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date:   Mon Mar 14 20:23:30 2016 +0100

    Disable MOVE more for Dovecot

    * lisp/gnus/nnimap.el (nnimap-process-expiry-targets): Also
    disable MOVE when expirying.
    (nnimap-split-incoming-mail): And when splitting mail.

commit 8ed27bdf88cab134c26f3609c4d11c574f74705c
Author: Lars Magne Ingebrigtsen <larsi@gnus.org>
Date:   Mon Mar 14 20:21:02 2016 +0100

    Don't use MOVE on Dovecot

    * lisp/gnus/nnimap.el (nnimap-request-move-article): Don't use
    MOVE on Dovecot, since it's broken in many versions.
    (nnimap-quirks): Mark MOVE on Dovecot as non-working.


References:
[1] <https://www.dovecot.org/list/dovecot/2008-July/032170.html>
[2] <http://git.savannah.gnu.org/cgit/emacs.git/log/lisp/gnus/nnimap.el>