Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: IMAP changes timestamp when moving an article to another group
Date: Sun, 10 Sep 2017 12:03:24 +0200	[thread overview]
Message-ID: <86d16ydg5v.fsf@dod.no> (raw)
In-Reply-To: <87r2vfnbwm.fsf@ericabrahamsen.net>

>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:

> I looked at the link, but I still don't really see where he's saying
> that you can specify the INTERNALDATE.

You're right.  I misread, he says that about the APPEND command.

> The IMAP specs certainly don't indicate that any additional arguments
> are possible with a MOVE command.

No, that was mbox-specific implementation on part of dovecot: if the
move command is used, the file is just moved from one directory to the
other (ie. on a GNU/linux filesystem: the inode is untouched) and mtime
is preserved, and therefore INTERNALDATE is preserved.

However in March 2016 in the git history of nnimap.el there were some
changes where Gnus stopped using MOVE on dovecot.

> You can specify a date with APPEND, but the only time Gnus uses that
> is when replacing an article, not MOVEing (so far as I can tell)...

Yes, I saw that when I was reading the specs of COPY yesterday (after I
had posted the message you're responding to).

However dovecot could (and really should) pick the date out of the Date
field of the source message when doing a COPY and use that as the mtime
of the new mbox file. 

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.




  reply	other threads:[~2017-09-10 10:03 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 [this message]
2017-09-14 22:29                               ` Eric Abrahamsen
2017-09-15 15:42                                 ` Steinar Bang
2017-09-15 21:52                                   ` Eric Abrahamsen
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=86d16ydg5v.fsf@dod.no \
    --to=sb@dod.no \
    --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).