Errors in Thunderbird folder listing date/time
by rnturn from LinuxQuestions.org on (#5K4F1)
Well, this wasn't what I had planned for tonight...
I have a folder in Thunderbird that has a series of emails that, according to T-bird, all arrived at 10:49 this evening. It's very unlikely that 93 emails all arrived at that very moment. I've checked the mail headers. The oldest message is from late March, the latest affected message is from last week (not quite three month's worth of emails are affected). Only the recent emails in the folder are showing incorrect dates/times; there are plenty of others in the folder that are listed with their correct arrival date/time. As a test I sent myself an email and manually dragged it into the affected folder but its date/time stamp was not affected.
I've restarted T-bird. No effect. I've tried the "Repair folder" option. Now there are 93 messages that appear to have arrived at 10:55. I created a temporary folder and moved them all into the new folder thinking that T-bird might re-read the headers and display the correct date/time. No such luck; now all the files have 11:08 timestamps. Everything I've tried so far does nothing to the individual emails to correct their arrival time as displayed by T-bird.
T-bird is up-to-date as far as OpenSUSE (still on Leap 15.2 for another week or two) is concerned.
When I jump over to the IMAP server, I find that there are, hmm, 93 email files in the folder that begin with "1623816504." which corresponds to "15 Jun 2021 23:08:24". So it's an IMAP snafu?
Questions:
Any ideas what might have happened to cause this odd renaming?
What would cause the IMAP server to rename a set of files in this way?
Would it be safe to (after making a backup of the files, of course) extract the date/time stamp from the headers of the affected emails, convert that to UNIX epoch time, and rename each email file accordingly? There's a record for each of the email files in "courierimapuiddb" which I'd need to "fix" as well. (For the curious: there are (surprise!) 93 such records in that file.) Related question: Could any manipulations like this cause Courier to take issue with the renamed files?)
Any hints/suggestions welcomed.
TIA...
I have a folder in Thunderbird that has a series of emails that, according to T-bird, all arrived at 10:49 this evening. It's very unlikely that 93 emails all arrived at that very moment. I've checked the mail headers. The oldest message is from late March, the latest affected message is from last week (not quite three month's worth of emails are affected). Only the recent emails in the folder are showing incorrect dates/times; there are plenty of others in the folder that are listed with their correct arrival date/time. As a test I sent myself an email and manually dragged it into the affected folder but its date/time stamp was not affected.
I've restarted T-bird. No effect. I've tried the "Repair folder" option. Now there are 93 messages that appear to have arrived at 10:55. I created a temporary folder and moved them all into the new folder thinking that T-bird might re-read the headers and display the correct date/time. No such luck; now all the files have 11:08 timestamps. Everything I've tried so far does nothing to the individual emails to correct their arrival time as displayed by T-bird.
T-bird is up-to-date as far as OpenSUSE (still on Leap 15.2 for another week or two) is concerned.
When I jump over to the IMAP server, I find that there are, hmm, 93 email files in the folder that begin with "1623816504." which corresponds to "15 Jun 2021 23:08:24". So it's an IMAP snafu?
Questions:
Any ideas what might have happened to cause this odd renaming?
What would cause the IMAP server to rename a set of files in this way?
Would it be safe to (after making a backup of the files, of course) extract the date/time stamp from the headers of the affected emails, convert that to UNIX epoch time, and rename each email file accordingly? There's a record for each of the email files in "courierimapuiddb" which I'd need to "fix" as well. (For the curious: there are (surprise!) 93 such records in that file.) Related question: Could any manipulations like this cause Courier to take issue with the renamed files?)
Any hints/suggestions welcomed.
TIA...