Github messages for mblaze
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mrefile: preserve file times
Date: Fri, 15 May 2020 18:14:53 +0200	[thread overview]
Message-ID: <20200515161453.GzWBgrccUuWb5vc0bzvbGEZ11K-aUEeR3h5OZaKH9L0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-157@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

Closed issue by silby on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/157

Description:
When I use `mrefile(1)` to move a message to a different folder in my mail structure, the resulting file has a fresh modification time. This mtime ends up getting used by isync's `mbsync(1)` when sending the message back to my mail host with an IMAP `APPEND` with an explicit internal time. The result is a refiled message on the IMAP server with a fresh internal time, as opposed to the original time the message was received.

`mdeliver -M` extracts the `Date:` from each message to use as the mtime of the resulting file. `mutt(1)` appears to have similar behavior when copying messages. I propose `mrefile(1)` should behave this way as well, or optionally behave this way, to accurately perform the "move messages between folders" task.

(It's late and I am unable to think through whether this should really be the job of `mrefile(1)` or if `mbsync(1)` using `APPEND` instead of somehow using `COPY` is a bug.)

           reply	other threads:[~2020-05-15 16:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-157@inbox.vuxu.org>]

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=20200515161453.GzWBgrccUuWb5vc0bzvbGEZ11K-aUEeR3h5OZaKH9L0@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).