Restore error with 1.9.1

[matheus1111]

Hi I’m trying to restore my database email that I’ve backup but I have the following error Pushing email body with id 1437845721884722102. Error: [Errno 13] Permission denied.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error IOError: [Errno 13] Permission denied

=== End of Exception traceback ===

I’ve tried a resume and each time I have this error. Of the 50K emails only around 2K were transferred to my new account Do you have any idea ? I’ve looked everywhere for a solution but didn’t find one

• What version of Gmvault do you use ?

1.9.1

• On what Operating System (Linux flavour, MacOSX, Win7/XP/Vista) ?

Windows 7

• Type of requests (Bug, documentation issue, features) ?

Bug

• Explain the request subject (issue details, feature details):

Restore issue

• In case of bug or issue, please detail how we can reproduce the problem:

My backup is on an external drive (D)

Here what I have in the conf file :

[General]

limit_per_chat_dir=2000

errors_if_chat_not_visible=False

nb_messages_per_batch=500

nb_messages_per_restore_batch=80

restore_default_location=DRAFTS

keep_in_bin=False

enable_imap_compression=False

Here is the command I’ve entered :

gmvault restore -d D:\Padawan_mail XXXXXX@gmail.com --resume

It starts ok :

gmvault-shell>gmvault restore -d D:\Padawan_mail XXXXX@gmail.com --resume

Use gmvault-db located in D:\Padawan_mail.

Create defaults in C:\Users\padawan/.gmvault/gmvault_defaults.conf. Please touch this file only if you know what to do.

Authentication performed with Gmail OAuth2 access token.

Get OAuth2 credential from C:\Users\padawan/.gmvault/XXXXX@gmail.com.oauth2.

Connect to Gmail server.

Start restoration (2016-05-20T23h04m16s).

Start emails restoration.

Restore emails in gmail account XXXXXX@gmail.com.

Read email info from D:\Padawan_mail gmvault-db.

Total number of elements to restore 59137.

Restart from gmail id 1437650532972907159.

Got all emails id left to restore. Still 57057 emails to do.

Processing next batch of 80 emails.

Pushing email body with id 1437651961842120389.

Pushing email body with id 1437652832436584249.

Pushing email body with id 1437655258601691646.

Pushing email body with id 1437655864818702977.

Pushing email body with id 1437656007652724239.

Pushing email body with id 1437656750049589572.

• Contact details (emails to recontact you if you didn't use the github interface):

Thanks again for your help

PS : I’ve given full control to everyone to the folder where the database and the conf file are stored

[migueldeicaza]

I am having the same problem

[gaubert]

@matheus1111 @migueldeicaza I would need you to send me more information to solve that issue. On which plateform are you running gmvault (Win, Mac, Linux) ? And with which python version.

Please re-run the restore with the --debug option and send me either the create log file or the console output when it fails and try to use the --restart option to restart from where it failed:

$>gmvault restore foo.bar@gmail.com --debug --restart

I suspect that the email you are trying to restore has a Label that cannot be used. Could you check and send me the content of 1437656750049589572.meta and especially the "labels" field.

I might be wrong and the second solution might be a bug when a file is written but normally in this area of gmvault it should not write. It might also be a read access problem but if you are saying that all permissions have been given ?

Thanks

[matheus1111]

Hi I've tried with the new released here what I've now after having restored 4480 emails over 60K

Pushing email body with id 1445166607089353921. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

Here what there is in the meta file of

{"thread_ids": 1445773113811130403, "msg_id": " 9D76960CB48D38408B2D2C12F2248A236EEB54618F@FRVDX100.fr01.awl.atosorigin.net", "flags": ["\Seen"], "gm_id": 1445166607089353921, "internal_date": 1378221876, "x_gmail_received": null, "labels": ["\Important", "INBOX/JV1T/Atos"], "subject": "RE: [PADAWAN] CB and paypal Certificates U10398"}

1445166607089353921

Hope you can help Thanks I'm running gmvault on windows 7

2017-01-03 13:59 GMT+01:00 Guillaume Aubert notifications@github.com:

@matheus1111 https://github.com/matheus1111 @migueldeicaza https://github.com/migueldeicaza I would need you to send me more information to solve that issue. On which plateform are you running gmvault (Win, Mac, Linux) ? And with which python version.

Please re-run the restore with the --debug option and send me either the create log file or the console output when it fails and try to use the --restart option to restart from where it failed:

$>gmvault restore foo.bar@gmail.com --debug --restart

I suspect that the email you are trying to restore has a Label that cannot be used. Could you check and send me the content of 1437656750049589572.meta and especially the "labels" field.

I might be wrong and the second solution might be a bug when a file is written but normally in this area of gmvault it should not write. It might also be a read access problem but if you are saying that all permissions have been given ?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-270109152, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0S_CickIiwxEYk-HZyL5ZeH2sOX4ks5rOkZHgaJpZM4ItWCj .

[gaubert]

Hi,

Ok I need to check. I will get back to you in 5 days as I am very busy next week.

Best regards, Guillaume

On 15 January 2017 at 18:38, matheus1111 notifications@github.com wrote:

Hi I've tried with the new released here what I've now after having restored 4480 emails over 60K

Pushing email body with id 1445166607089353921. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

Here what there is in the meta file of

{"thread_ids": 1445773113811130403, "msg_id": " 9D76960CB48D38408B2D2C12F2248A236EEB54618F@FRVDX100.fr01. awl.atosorigin.net", "flags": ["\Seen"], "gm_id": 1445166607089353921, "internal_date": 1378221876, "x_gmail_received": null, "labels": ["\Important", "INBOX/JV1T/Atos"], "subject": "RE: [PADAWAN] CB and paypal Certificates U10398"}

1445166607089353921

Hope you can help Thanks I'm running gmvault on windows 7

2017-01-03 13:59 GMT+01:00 Guillaume Aubert notifications@github.com:

@matheus1111 https://github.com/matheus1111 @migueldeicaza https://github.com/migueldeicaza I would need you to send me more information to solve that issue. On which plateform are you running gmvault (Win, Mac, Linux) ? And with which python version.

Please re-run the restore with the --debug option and send me either the create log file or the console output when it fails and try to use the --restart option to restart from where it failed:

$>gmvault restore foo.bar@gmail.com --debug --restart

I suspect that the email you are trying to restore has a Label that cannot be used. Could you check and send me the content of 1437656750049589572.meta and especially the "labels" field.

I might be wrong and the second solution might be a bug when a file is written but normally in this area of gmvault it should not write. It might also be a read access problem but if you are saying that all permissions have been given ?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-270109152, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0S_CickIiwxEYk- HZyL5ZeH2sOX4ks5rOkZHgaJpZM4ItWCj .

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272710542, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAFykMNL2rT_6q0BZT7dqL2COWgD_Xaks5rSlmcgaJpZM4ItWCj .

[matheus1111]

Thanks I've launched a resume with the debug option, let see if I can see something else For the moment it seems to be working fine I'll keep you inform Kind Regards

2017-01-15 21:35 GMT+01:00 Guillaume Aubert notifications@github.com:

Hi,

Ok I need to check. I will get back to you in 5 days as I am very busy next week.

Best regards, Guillaume

On 15 January 2017 at 18:38, matheus1111 notifications@github.com wrote:

Hi I've tried with the new released here what I've now after having restored 4480 emails over 60K

Pushing email body with id 1445166607089353921. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

Here what there is in the meta file of

{"thread_ids": 1445773113811130403, "msg_id": " 9D76960CB48D38408B2D2C12F2248A236EEB54618F@FRVDX100.fr01. awl.atosorigin.net", "flags": ["\Seen"], "gm_id": 1445166607089353921, "internal_date": 1378221876, "x_gmail_received": null, "labels": ["\Important", "INBOX/JV1T/Atos"], "subject": "RE: [PADAWAN] CB and paypal Certificates U10398"}

1445166607089353921

Hope you can help Thanks I'm running gmvault on windows 7

2017-01-03 13:59 GMT+01:00 Guillaume Aubert notifications@github.com:

@matheus1111 https://github.com/matheus1111 @migueldeicaza https://github.com/migueldeicaza I would need you to send me more information to solve that issue. On which plateform are you running gmvault (Win, Mac, Linux) ? And with which python version.

Please re-run the restore with the --debug option and send me either the create log file or the console output when it fails and try to use the --restart option to restart from where it failed:

$>gmvault restore foo.bar@gmail.com --debug --restart

I suspect that the email you are trying to restore has a Label that cannot be used. Could you check and send me the content of 1437656750049589572.meta and especially the "labels" field.

I might be wrong and the second solution might be a bug when a file is written but normally in this area of gmvault it should not write. It might also be a read access problem but if you are saying that all permissions have been given ?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/gaubert/gmvault/issues/246#issuecomment-270109152 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0S_CickIiwxEYk- HZyL5ZeH2sOX4ks5rOkZHgaJpZM4ItWCj .

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272710542, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAFykMNL2rT_ 6q0BZT7dqL2COWgD_Xaks5rSlmcgaJpZM4ItWCj .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272721767, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0Y9Qbsw40AjPzC9jlq57J0YH5gwTks5rSoMDgaJpZM4ItWCj .

[matheus1111]

Hi Guillaume Here is a new error I have

Unbury email with gm_id 1470553323115667309. Pushing email body with id 1470553323115667309. Subject = Re: mariage. Before to Append email contents IMAP (normal) error message = APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']. t raceback:Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 132, in wrapper File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 802, in push_data File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.mod_imap", line 328, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imapclient.imapclient", line 987, in _command_and_check File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 337, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 1088, in _simple_command File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 918, in _command_complete error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']

Error when reaching Gmail server. Wait 1 second(s) and retry up to 2 times. Disconnecting from Gmail Server and sleeping ... Reconnecting to the from Gmail Server. Get OAuth2 credential from C:\Users\padawan/.gmvault/BCKmathias@gmail.com.oauth2.

oauth2 creds = 1/5kIswMYyzpvKMd-cIfQDb8NwDj5ED7XAMWq25bkX86c Access Token is still valid auth_str generated: user=BCKmathias@gmail.com☺auth=Bearer ya29.CjDVA3J_AfPNTQ-ov6-KZci0nGp_hZZmy6aq9jyN3qvJBtv3DX2_HAQVAvzudU_HyBE☺☺ Successfully read oauth2 credentials with get_oauth2_credential_from_refresh_token

credential['value'] = user=BCKmathias@gmail.com☺auth=Bearer ya29.CjDVA3J_AfPNTQ-ov6-KZci0nGp_hZZmy6aq9jyN3qvJBtv3DX2_HAQVAvzudU_HyBE☺☺ Do not enable imap compression. Before to Append email contents IMAP (normal) error message = APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']. t raceback:Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 132, in wrapper File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 802, in push_data File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.mod_imap", line 328, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imapclient.imapclient", line 987, in _command_and_check File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 337, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 1088, in _simple_command File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 918, in _command_complete error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']

Error when reaching Gmail server. Wait 2 second(s) and retry up to 2 times. Disconnecting from Gmail Server and sleeping ... Reconnecting to the from Gmail Server. Get OAuth2 credential from C:\Users\padawan/.gmvault/BCKmathias@gmail.com.oauth2.

oauth2 creds = 1/5kIswMYyzpvKMd-cIfQDb8NwDj5ED7XAMWq25bkX86c Access Token is still valid auth_str generated: user=BCKmathias@gmail.com☺auth=Bearer ya29.CjDVA3J_AfPNTQ-ov6-KZci0nGp_hZZmy6aq9jyN3qvJBtv3DX2_HAQVAvzudU_HyBE☺☺ Successfully read oauth2 credentials with get_oauth2_credential_from_refresh_token

credential['value'] = user=BCKmathias@gmail.com☺auth=Bearer ya29.CjDVA3J_AfPNTQ-ov6-KZci0nGp_hZZmy6aq9jyN3qvJBtv3DX2_HAQVAvzudU_HyBE☺☺ Do not enable imap compression. Before to Append email contents IMAP (normal) error message = APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']. t raceback:Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 132, in wrapper File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 802, in push_data File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.mod_imap", line 328, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imapclient.imapclient", line 987, in _command_and_check File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 337, in append File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 1088, in _simple_command File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\imaplib", line 918, in _command_complete error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']

Error when reaching Gmail server. Wait 4 second(s) and retry up to 2 times. Catched IMAP Error APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit'] APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit'] Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1119, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 189, in wrapper File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.imap_utils", line 124, in reconnect error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit'] Error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit'].

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 69, in handle_restore_imap_error error: APPEND command error: BAD ['[TOOBIG] Message too large. https://support.google.com/mail/answer/6584#limit']

=== End of Exception traceback ===

usage: gmvault [-h] [-v] {sync,restore,check,export} ...

2017-01-15 23:55 GMT+01:00 WSE Production mathias.milin@gmail.com:

Thanks I've launched a resume with the debug option, let see if I can see something else For the moment it seems to be working fine I'll keep you inform Kind Regards

2017-01-15 21:35 GMT+01:00 Guillaume Aubert notifications@github.com:

Hi,

Ok I need to check. I will get back to you in 5 days as I am very busy next week.

Best regards, Guillaume

On 15 January 2017 at 18:38, matheus1111 notifications@github.com wrote:

Hi I've tried with the new released here what I've now after having restored 4480 emails over 60K

Pushing email body with id 1445166607089353921. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

Here what there is in the meta file of

{"thread_ids": 1445773113811130403, "msg_id": " 9D76960CB48D38408B2D2C12F2248A236EEB54618F@FRVDX100.fr01. awl.atosorigin.net", "flags": ["\Seen"], "gm_id": 1445166607089353921, "internal_date": 1378221876, "x_gmail_received": null, "labels": ["\Important", "INBOX/JV1T/Atos"], "subject": "RE: [PADAWAN] CB and paypal Certificates U10398"}

1445166607089353921

Hope you can help Thanks I'm running gmvault on windows 7

2017-01-03 13:59 GMT+01:00 Guillaume Aubert notifications@github.com:

@matheus1111 https://github.com/matheus1111 @migueldeicaza https://github.com/migueldeicaza I would need you to send me more information to solve that issue. On which plateform are you running gmvault (Win, Mac, Linux) ? And with which python version.

Please re-run the restore with the --debug option and send me either the create log file or the console output when it fails and try to use the --restart option to restart from where it failed:

$>gmvault restore foo.bar@gmail.com --debug --restart

I suspect that the email you are trying to restore has a Label that cannot be used. Could you check and send me the content of 1437656750049589572.meta and especially the "labels" field.

I might be wrong and the second solution might be a bug when a file is written but normally in this area of gmvault it should not write. It might also be a read access problem but if you are saying that all permissions have been given ?

Thanks

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://github.com/gaubert/gmvault/issues/246#issuecomment-270109152 , or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0S_ CickIiwxEYk- HZyL5ZeH2sOX4ks5rOkZHgaJpZM4ItWCj .

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272710542, or mute the thread https://github.com/notifications/unsubscribe-auth/ AAAFykMNL2rT_6q0BZT7dqL2COWgD_Xaks5rSlmcgaJpZM4ItWCj .

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272721767, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0Y9Qbsw40AjPzC9jlq57J0YH5gwTks5rSoMDgaJpZM4ItWCj .

[gaubert]

It seems that since they are pushing Google Drive, Google has restricted the size of the attachments. It cannot be bigger than 25 MB. Can you check how big is the 1470553323115667309.eml.gz file uncompressed in the database (gmvault-db/db). Do a find to look for the file.

For that I cannot do anything. What you can do is to quarantine the file move 1470553323115667309.eml.gz and 1470553323115667309.meta to the quarantine directory.

[matheus1111]

Hi Yes you are right 25,7 Mo :)

2017-01-16 16:19 GMT+01:00 Guillaume Aubert notifications@github.com:

It seems that since they are pushing Google Drive, Google has restricted the size of the attachments. It cannot be bigger than 25 MB. Can you check how big is the 1470553323115667309.eml.gz file uncompressed in the database (gmvault-db/db). Do a find to look for the file.

For that I cannot do anything. What you can do is to quarantine the file move 1470553323115667309.eml.gz and 1470553323115667309.meta to the quarantine directory.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-272889337, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0STrujGInrQxo0vN1nJon7omFzL5ks5rS4prgaJpZM4ItWCj .

[gaubert]

ok good. I will catch that error in the next version but I don't know what to do about it. I can only quarantine the email because it is too big. A more sophisticated plan could be to make the attachment persistent in Google Doc. But this is for the future.

[matheus1111]

Thanks again Yes I think that automatically push the errors like this in quarantine would be a good idea to avoid stopping the restore process Thanks

2017-01-17 11:27 GMT+01:00 Guillaume Aubert notifications@github.com:

ok good. I will catch that error in the next version but I don't know what to do about it. I can only quarantine the email because it is too big. A more sophisticated plan could be to make the attachment persistent in Google Doc. But this is for the future.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-273093902, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0RjoZ71u07S7R-xtb3DPaEnMZwZrks5rTJeMgaJpZM4ItWCj .

[matheus1111]

Hi Guillaume FYI I have this kind of error too if it can help for upgrating gmvault in the future (I'm like a beta tester :) ) Pushing email body with id 1473250625992543525. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

If it can help here is the meta file {"thread_ids": 1473250625992543525, "msg_id": "CAPxs= y4vjQ4rMvFcAppeum-StLqA5NR-0HuM6LV3tXVbMa72ow@mail.gmail.com", "flags": ["\Seen"], "gm_id": 1473250625992543525, "internal_date": 1405004883, "x_gmail_received": null, "labels": ["\Important", "\Inbox"], "subject": "Fwd: HR - developer recruitment"}

I have put it in quaratine to continue the process :)

2017-01-17 11:28 GMT+01:00 WSE Production mathias.milin@gmail.com:

Thanks again Yes I think that automatically push the errors like this in quarantine would be a good idea to avoid stopping the restore process Thanks

2017-01-17 11:27 GMT+01:00 Guillaume Aubert notifications@github.com:

ok good. I will catch that error in the next version but I don't know what to do about it. I can only quarantine the email because it is too big. A more sophisticated plan could be to make the attachment persistent in Google Doc. But this is for the future.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-273093902, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0RjoZ71u07S7R-xtb3DPaEnMZwZrks5rTJeMgaJpZM4ItWCj .

[gaubert]

Thks this one has been corrected in v.19.2 . See #246

[matheus1111]

Hi Guillaume Quick Question Just noticed something is that normal that the resume doesn't restart from the last correct id

Pushing email body with id 1498967660317462600. Pushing email body with id 1498967854387806441. Pushing email body with id 1498968150771567804. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

gmvault-shell>gmvault restore -d i:\email_PDW_ALEX bckalexandre03@gmail.com --resume

Use gmvault-db located in i:\email_PDW_ALEX.

Create defaults in C:\Users\mathias/.gmvault/gmvault_defaults.conf. Please touch this file only if you know what to do. Authentication performed with Gmail OAuth2 access token.

Get OAuth2 credential from C:\Users\mathias/.gmvault/bckalexandre03@gmail.com.oauth2.

Connect to Gmail server.

Start restoration (2017-01-24T19h28m24s).

Start emails restoration.

Restore emails in gmail account bckalexandre03@gmail.com. Read email info from i:\email_PDW_ALEX gmvault-db. Total number of elements to restore 44326. Restart from gmail id 1498958237988345300. Got all emails id left to restore. Still 28966 emails to do.

Processing next batch of 80 emails.

Pushing email body with id 1498958287854220603. Pushing email body with id 1498958372651892953. Pushing email body with id 1498958446807300101. Pushing email body with id 1498958472822733009. Pushing email body with id 1498958507729443969. Pushing email body with id 1498958638266351722.

2017-01-18 11:22 GMT+01:00 Guillaume Aubert notifications@github.com:

Thks this one has been corrected in v.19.2 . See #246 https://github.com/gaubert/gmvault/issues/246

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-273438392, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0eR85Yjm4WokBaczN5rToZ1wRJDiks5rTef9gaJpZM4ItWCj .

[gaubert]

Yes, emails are batched restored by group of 80 emails if I remember correctly and only this is the first email id which used to do the restart. So this is normal. Thanks for the help. Progressing on v1.9.2

On 24 January 2017 at 19:31, matheus1111 notifications@github.com wrote:

Hi Guillaume Quick Question Just noticed something is that normal that the resume doesn't restart from the last correct id

Pushing email body with id 1498967660317462600. Pushing email body with id 1498967854387806441. Pushing email body with id 1498968150771567804. Error: argument of type 'NoneType' is not iterable.

=== Exception traceback === Traceback (most recent call last): File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 750, in run File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmv_cmd", line 625, in _restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 901, in restore File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 1145, in restore_emails File "c:\Users\toto\Dev\gmvault\build\gmv_runner\out00-PYZ.pyz\gmv.gmvault", line 84, in handle_restore_imap_error TypeError: argument of type 'NoneType' is not iterable

=== End of Exception traceback ===

gmvault-shell>gmvault restore -d i:\email_PDW_ALEX bckalexandre03@gmail.com --resume

Use gmvault-db located in i:\email_PDW_ALEX.

Create defaults in C:\Users\mathias/.gmvault/gmvault_defaults.conf. Please touch this file only if you know what to do. Authentication performed with Gmail OAuth2 access token.

Get OAuth2 credential from C:\Users\mathias/.gmvault/bckalexandre03@gmail.com.oauth2.

Connect to Gmail server.

Start restoration (2017-01-24T19h28m24s).

Start emails restoration.

Restore emails in gmail account bckalexandre03@gmail.com. Read email info from i:\email_PDW_ALEX gmvault-db. Total number of elements to restore 44326. Restart from gmail id 1498958237988345300. Got all emails id left to restore. Still 28966 emails to do.

Processing next batch of 80 emails.

Pushing email body with id 1498958287854220603. Pushing email body with id 1498958372651892953. Pushing email body with id 1498958446807300101. Pushing email body with id 1498958472822733009. Pushing email body with id 1498958507729443969. Pushing email body with id 1498958638266351722.

2017-01-18 11:22 GMT+01:00 Guillaume Aubert notifications@github.com:

Thks this one has been corrected in v.19.2 . See #246 https://github.com/gaubert/gmvault/issues/246

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-273438392, or mute the thread https://github.com/notifications/unsubscribe-auth/ AS0D0eR85Yjm4WokBaczN5rToZ1wRJDiks5rTef9gaJpZM4ItWCj .

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-274893019, or mute the thread https://github.com/notifications/unsubscribe-auth/AAAFyi67_zgTDWOqthb5AN_YIsql-VIdks5rVkOEgaJpZM4ItWCj .

[migueldeicaza]

My issue happened on Mac.

[gaubert]

@migueldeicaza @matheus1111 you can test the latest beta version here (beta windows and mac os x package available): https://www.dropbox.com/sh/d5ceo77juacr03y/AACUGcTt6Um-6j6JmBizGPA2a?dl=0

or from the branch gmv-1.9.2

Help required for testing to see if I missed something. Many thanks for the testing.

[matheus1111]

Hi Guillaume I'll try it this week and get back to you Kind Regards

2017-02-05 15:05 GMT+01:00 Guillaume Aubert notifications@github.com:

@migueldeicaza https://github.com/migueldeicaza @matheus1111 https://github.com/matheus1111 you can test the latest beta version here (beta windows and mac os x package available): https://www.dropbox.com/sh/d5ceo77juacr03y/AACUGcTt6Um-6j6JmBizGPA2a?dl=0

or from the branch gmv-1.9.2

Help required for testing to see if I missed something. Many thanks for the testing.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/gaubert/gmvault/issues/246#issuecomment-277521887, or mute the thread https://github.com/notifications/unsubscribe-auth/AS0D0RYNInsNkHYHKTDzMCsDekvxIy96ks5rZddBgaJpZM4ItWCj .

[gaubert]

@matheus1111 @migueldeicaza Please wait before to test. I have discovered a restore side effect bug (it will not damage your email box. No worries). I will let you know when it has been fixed. Sorry about that

[gaubert]

@matheus1111 @migueldeicaza version 1.9.2-beta-1 available for test and fixing many additional problems (especially in the restore). Please test it and let me know if this is fine within 6 days. Many thanks. It should now work.

https://www.dropbox.com/sh/d5ceo77juacr03y/AACUGcTt6Um-6j6JmBizGPA2a?dl=0

[flop25]

Hello sorry to ask on such a lengthy thread, but is there a way to skip errors especially the TOOBIG ones or do the gmvault betas handle better such errors?

[gaubert]

@flop25 the beta-1 version should handle it now. Could you please try it and let me know ? Thanks.

[flop25]

1.9.2-beta-1 seems to correct those issues. Sorry the huge delay