-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
restore-group: "400: Unable to parse the raw message - invalid" #349
Comments
I also found this thread on your google group. The user reports having problems with Hangouts (Chat) messages, and that could be the problem here also. |
The Google APIs generally don't support backup/restore of Google Chat messages and those messages are excluded from the initial backup by default. If you are using a custom --search rule on the backup you should add If the error is happening on something other than a chat message then I'll need to see specific examples of failing messages in order to repro the issue. |
Yes, you'd want to exclude Chat from the Takeout. They can't be migrated back into Gmail or Groups in any meaningful form. |
I understand thanks. Would it be possible for GYB to detect such chat messages and skip them with a proper warning? The message it outputs right now is a bit worrisome and confusing... Also the documentation does not say much about Chat messages, except in the "--action count" section. |
Full steps to reproduce the issue:
Expected outcome (what are you trying to do?):
All emails are imported, except those that are too big
Actual outcome (what errors or bad behavior do you see instead?):
A LOT of "400: Unable to parse the raw message - invalid"
Additional info:
There's not much help on this on the net.... All I found was this SO article but that doesn't help a mere user ;)
The text was updated successfully, but these errors were encountered: