#3878: mtime to -1 for about 1% of the mails
-------------------------+----------------------
Reporter: uxmutt | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: maildir/mh | Version:
Keywords: utime mtime |
-------------------------+----------------------
About 1% of my archived mails (1907/196025) have a mtime of -1:
{{{[~/mail/archives/cur]☭ ls -lt|tail -n 10
-rw------- 1 ubitux ubitux 7.6K Jan 1 1970
1452383627.26316_261.leki:2,S
-rw------- 1 ubitux ubitux 2.4K Jan 1 1970
1452383628.26316_263.leki:2,S
-rw------- 1 ubitux ubitux 2.4K Jan 1 1970
1452383628.26316_265.leki:2,S
-rw------- 1 ubitux ubitux 2.7K Jan 1 1970
1452383628.26316_267.leki:2,S
-rw------- 1 ubitux ubitux 3.9K Jan 1 1970
1452383628.26316_269.leki:2,S
-rw------- 1 ubitux ubitux 3.4K Jan 1 1970
1452383634.26316_271.leki:2,S
-rw------- 1 ubitux ubitux 2.3K Jan 1 1970
1452383634.26316_273.leki:2,S
-rw------- 1 ubitux ubitux 1.8K Jan 1 1970
1471445179.26860_951.leki:2,RS
-rw------- 1 ubitux ubitux 1.9K Jan 1 1970
1471445179.26860_955.leki:2,S
-rw------- 1 ubitux ubitux 1.5K Jan 1 1970
1471445179.26860_957.leki:2,S
[~/mail/archives/cur]☭ stat 1452383634.26316_271.leki:2,S
File: '1452383634.26316_271.leki:2,S'
Size: 3439 Blocks: 8 IO Block: 4096 regular file
Device: 811h/2065d Inode: 16281338 Links: 1
Access: (0600/-rw-------) Uid: ( 1000/ ubitux) Gid: ( 1000/ ubitux)
Access: 2016-09-24 15:02:18.260230544 +0200
Modify: 1970-01-01 00:59:59.000000000 +0100
Change: 2016-01-10 00:53:54.375530819 +0100
Birth: -
[~/mail/archives/cur]☭ stat -c '%Y' 1452383634.26316_271.leki:2,S
-1
[~/mail/archives/cur]☭
}}}
Some information about the situation:
- This is not the case in my {{{INBOX}}} Maildir, but the number of mails
(181) is not significant enough to say if the issue happens only when
moving it to {{{archives}}}.
- The actual mails dates spread from 2013 to nowadays so not a bug "once
in a lifetime".
- The mails have not much special characteristics but none of them seems
to come from mailing-lists, which makes me think the issue might be
related to content parsing somehow (the {{{Date:}}} field don't seem to be
broken, but they might have been fixed - see next point)
- working on a copy of these mails makes me believe moving these mails
back and forth between Maildirs will solve their timestamps, but I'd
prefer not to do it until I understand the source of the issue
- {{{-1}}} is a curious mtime, and I believe the issue to be related to
{{{mutt_decrease_mtime()}}} somehow. Unfortunately I'm not familiar enough
with the codebase to figure out what could fail or triggers the problem.
- The mails are delivered directly by OpenSMTPd which uses a
straightforward write and let live on, which is then directly read by
mutt.
--
Ticket URL: <https://dev.mutt.org/trac/ticket/3878>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
