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.)