Hey, I would just like to say that this tool is a real lifesaver for me and it's working well aside from one annoying little snag. I am getting duplicates.
I am using version 1.50 as confirmed by gyb --version
Full steps to reproduce the issue:
Export gmail data using google takeout with the "Include all messages" option, which includes Hangouts chats.
Unzip the file to get the mbox.
Restore the mbox file to a different gmail account using these arguments:
gyb --email --action restore-mbox --local-folder --label-restored
Expected outcome:
I am expecting it to add the messages contained in the mbox file to my other gmail account.
Actual outcome:
It keeps giving me the "backing off for 60 seconds" message and taking a long time, but I do see the emails coming into my gmail. However, I noticed that I was getting a lot of messages under the Chats_restored tag, and I realized that I was getting duplicates. I see 6-7 copies of messages. Some of them have timestamps that are less than a minute apart.
My hypothesis is that the command sends a batch of 15 and mistakenly believes that it failed and does it again after waiting for a few seconds, thus producing duplicates. It's a manageable inconvenience, but I thought that I should call attention to this issue.
Hey, I would just like to say that this tool is a real lifesaver for me and it's working well aside from one annoying little snag. I am getting duplicates.
I am using version 1.50 as confirmed by gyb --version
Full steps to reproduce the issue:
Expected outcome: I am expecting it to add the messages contained in the mbox file to my other gmail account.
Actual outcome: It keeps giving me the "backing off for 60 seconds" message and taking a long time, but I do see the emails coming into my gmail. However, I noticed that I was getting a lot of messages under the Chats_restored tag, and I realized that I was getting duplicates. I see 6-7 copies of messages. Some of them have timestamps that are less than a minute apart.
My hypothesis is that the command sends a batch of 15 and mistakenly believes that it failed and does it again after waiting for a few seconds, thus producing duplicates. It's a manageable inconvenience, but I thought that I should call attention to this issue.