From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: IMAP changes timestamp when moving an article to another group
Date: Fri, 15 Sep 2017 14:52:00 -0700 [thread overview]
Message-ID: <87377nmxz3.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86ingk9dek.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:
>> Steinar Bang <sb@dod.no> writes:
>
>>> Currently, I'm guessing, when dovecot w/mbox does a COPY, the mtime
>>> of the message file in the mbox folder will become time the file was
>>> created.
>
> Yes it will. I just asked on the dovecot mailing list.
>
>> Beats me, I guess... Is there a configuration knob you can twiddle in
>> Dovecot?
>
> I don't know. But I'm guessing that there isn't...?
>
> And if there isn't, the only ways to preserve INTERNALDATE on folder
> moves with nnimap in Gnus on dovecot with maildir, are:
>
> 1. Go back to using MOVE for dovecot, ie. reverting the March 2016
> changes to Gnus:
> http://git.savannah.gnu.org/cgit/emacs.git/commit/lisp/gnus/nnimap.el?id=d5427e71da28856c5e43396a37ffd0c906947499
> http://git.savannah.gnu.org/cgit/emacs.git/commit/lisp/gnus/nnimap.el?id=8ed27bdf88cab134c26f3609c4d11c574f74705c
>
> 2. Use APPEND instead of COPY so that INTERNALDATE can be specified
Hmm, the comments don't really say *what* brokenness the quirks were
meant to fix. I wouldn't feel confident at all in saying what the right
thing to do is. Maybe Lars will chime in...
next prev parent reply other threads:[~2017-09-15 21:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 2:36 notmuch is limited to a single local mail store, right? myglc2
2016-01-15 3:28 ` Eric Abrahamsen
2016-01-15 12:46 ` myglc2
2016-01-15 13:12 ` Erik Colson
2016-01-15 16:43 ` myglc2
2016-02-06 0:06 ` gnus async prefetch and nnimap Erik Colson
2016-02-06 1:13 ` Eric Abrahamsen
2016-02-06 1:15 ` Eric Abrahamsen
2016-08-01 21:29 ` IMAP changes timestamp when moving an article to another group Erik Colson
2016-08-01 23:49 ` Greg Troxel
2016-08-05 19:21 ` Steinar Bang
2016-08-16 13:22 ` Erik Colson
2017-09-05 16:14 ` Steinar Bang
2017-09-09 7:47 ` Steinar Bang
2017-09-09 15:12 ` Eric Abrahamsen
2017-09-10 10:03 ` Steinar Bang
2017-09-14 22:29 ` Eric Abrahamsen
2017-09-15 15:42 ` Steinar Bang
2017-09-15 21:52 ` Eric Abrahamsen [this message]
2018-04-11 20:25 ` Lars Ingebrigtsen
2018-04-11 22:08 ` Eric Abrahamsen
2016-01-15 5:30 ` notmuch is limited to a single local mail store, right? Adam Sjøgren
2016-01-15 7:49 ` Alan Schmitt
2016-01-15 8:17 ` Adam Sjøgren
2016-01-15 13:03 ` myglc2
2016-01-16 3:56 ` myglc2
2016-01-15 12:50 ` myglc2
2016-01-15 14:25 ` Peter Münster
2016-01-15 19:19 ` Adam Sjøgren
2016-01-15 20:21 ` Adam Sjøgren
2016-01-16 3:47 ` myglc2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87377nmxz3.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).