Megabytemb / google-gdata

Automatically exported from code.google.com/p/google-gdata
0 stars 0 forks source link

Migration API returns "-1" with no reason #521

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
1. Use the migration API to upload an RFC822 message with charset=ISO-2022-JP 
or another language
2. Batch uploads...
3. Batch result code is "-1" with no reason. Entire batch is not processed and 
does not show up in the target account

What is the expected output? What do you see instead?
Expected: 200 & all's ok
Seen: "-1", ""

A sample RFC822 message that reliably causes this is available on request

See also:
http://www.0x61.com/forum/google-api-apps-f195/response-status-code-or-reason-fo
r-email-migration-api-t852647.html

Original issue reported on code.google.com by nick.wil...@sparkfun.com on 1 Jul 2011 at 5:40

GoogleCodeExporter commented 9 years ago
Can you attach your code here so that I can try to reproduce the issue?
Please also add the sample RFC822 message that can be used with your code.
Thanks

Claudio

Original comment by ccherub...@google.com on 3 Jul 2011 at 1:49

GoogleCodeExporter commented 9 years ago
Hi Claudio, attached is a sample message; our code pull from IMAP so it can't 
really be used here, but it's not dissimilar from the samples; the 
message/batch will fail when done both individually and with others.  99% of 
the mail works with the API, it's just the ones with unusual charsets that I've 
been having an issue with.

Original comment by n...@saguratus.com on 6 Jul 2011 at 5:15

Attachments:

GoogleCodeExporter commented 9 years ago
Hey Nick,

You can use base-64 encoding as a workaround for unusual charsets.
I just tried that with your sample message and it worked.
For reference, please check the .NET tab at:

http://code.google.com/googleapps/domain/email_migration/developers_guide_protoc
ol.html#MigratingWithClientLibrary

Original comment by ccherub...@google.com on 19 Jul 2011 at 10:17