![]() ![]() emlįiles so the gyb restore could stamp the affected emails with the correctĪTM, since there is at-least 1 message out of 32K that I could spot checkĪs being affected, I couldn't really trust the entire restore because I Msg-db.sqlite ?) which messages are affected? or maybe a command lineįurther more would it be possible to manually edit the downloaded. You have a very unique and awesome piece of utility which I don't know why Need the email histories to reflect what really took place. The screenshot there's no way for Google to know that the message was from Well there is NO Date: header on the original message that I can see so You are receiving this because you commented. Google is reporting the correct sent date so the correct sent date is saved Please let me know what else I could provide?ĭo you think this is an issue with the export step because in my browser, It should have been Jan 22, 2019, not sure why this date isn't on the On Mon, at 9:41 AM panmail wrote:Īnd the imported email header which has yesterday's date. I'll try the export again and see if the issue persists with the same email. To Google without a date header, however that was done it looks like the There's no date header on the original message, it's not an export issue, You are receiving this because you authored the thread. ![]() Google is reporting the correct sent date so the correct sent date is So there's an "internal date" kept somewhere by Gmail and this doesn't get The screenshot there's no way for Google to know that the message was I'll try the export again and see if the issue persists with the same "internal date" was set but the Date header was not. That would explain why Google had to add a Date: header itself. Accounts With 2-Step Verification EnabledĪccount Recovery Walk-ThroughOver the last few years, Google's account recovery process has become more dynamic.īasedThis article will help guide one through the process of recovering a lost Google Gmail account and, if needed, securing the account so that is it less likely to be compromised again. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |