From: Greg Troxel <gdt@lexort.com>
To: Erik Colson <eco@ecocode.net>
Cc: ding@gnus.org
Subject: Re: IMAP changes timestamp when moving an article to another group
Date: Mon, 01 Aug 2016 19:49:47 -0400 [thread overview]
Message-ID: <smubn1c9hic.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <m2a8gwrxem.fsf_-_@ecocode.net> (Erik Colson's message of "Mon, 01 Aug 2016 23:29:05 +0200")
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Erik Colson <eco@ecocode.net> writes:
> When I use gnus-summary-move-article [Bm] to move an article into
> another group on a dovecot imap server, the timestamp in other clients
> gets changed to actual date/time. The header of the article still
> represents the correct timestamp though (and so does gnus). But the
> timestamp is faulty when accessing the group through Mail.app on my Mac.
I have noticed this as well, but I was never clear on whether the
received date was wrong or if it was just that clients other than gnus
were sorting on the wrong date.
This seems to be the IMAP received tiemstamp:
http://serverfault.com/questions/588618/maintain-email-timestamp-when-transferring-between-email-servers-using-an-email
http://www.dovecot.org/list/dovecot/2008-July/032165.html
> Is this dovecot related ? or can I configure gnus somehow to not change
> the timestamp ? For info, when moving mail between groups from within
> Mail.app everything is handled correctly (also in gnus).
As I understand it from the dovecot mail message above, gnus should
probably use APPEND when moving and set the date to match the source
message.
Another view is that the current behavior is right because the message's
received date is the time it was copied into the account.
But, I think preserving the received date on copy is probably more
useful overall.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 180 bytes --]
next prev parent reply other threads:[~2016-08-01 23:49 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 [this message]
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
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=smubn1c9hic.fsf@linuxpal.mit.edu \
--to=gdt@lexort.com \
--cc=ding@gnus.org \
--cc=eco@ecocode.net \
/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).