Hi Febs, I don't know if this will help but we used a tool (written in Perl) that took user's inbox and folders and totally moved everything to another mailbox via IMAP. I tested this with Google Apps for Education and it worked great. I modified the source code and created a new EXE in Perl because I wanted to save the log files just incase there were issues. I then wrote a mult-threaded application in C# and launched mutilple instances of the Perl EXEso many mailing boxes could sync in parallel. I can elaborate more if needed, if this is something that can help you I would be glad to share it.
Regards Fred On May 30, 6:31 am, Claudio Cherubino <[email protected]> wrote: > Hi, > > CAPTCHAs can appear for various reasons when our automated systems believe > that the requests are behaving in a suspicious way. > One of the reasons could be that the tool is performing authentication many > times in a short period of time instead of retrieving a single > authentication token to be reused in all requests. > > If you exceed the rate of messages per hour and per day you don't get a > CAPTCHA, but instead the calls return with a 503 response code, which asks > you to slow down the requests. > Hope it helps > > Claudio > > On Mon, May 30, 2011 at 11:09 AM, febs <[email protected]>wrote: > > > > > Hello, > > We are testing the Emailchemy tool ( > >http://www.weirdkid.com/products/emailchemy/) to migrate our user's > > emails to google Apps. > > After loads of emails uploaded successfully for hundreds of users, > > Emailchemy started to log that a captcha was required: > > > com.google.gdata.client.GoogleService$CaptchaRequiredException > > > We asked the developer about this, and he suggested that maybe we are > > exceeding the rate of messages per hour and per day. Unfortunately the only > > limit we could read on the documentation is of "one email per second, per > > user"; and nothing else. > > > Please, we do need to know if the captcha requests are triggered by the > > exceeding of any limit; and if so, to know what those limits are. In that > > way we could try to tune our uploads in such a way that no human > > intervention is required and that we can migrate our whole domain (that's > > 50.000+ users, 120.000+ mailboxes) automatically. > > > For your information, unfortunately the IMAP migration tool by Google was > > deprecated; and the Google Apps Migration for Microsoft Exchange tool is > > faulty and doesn't accept more than 1000 users a time - it crashes badly if > > we try to, and the only answer we got from its official support was to load > > 50+ batches on virtual machines. We can't handle that and that's why we're > > testing a third party solution. > > > Please help us by letting us know how to avoid any captcha and human > > intervention while migrating our whole domain's email. > > > Thanks > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google Apps Domain Information and Management APIs" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/google-apps-mgmt-apis?hl=en.- Hide quoted > >text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Google Apps Domain Information and Management APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-apps-mgmt-apis?hl=en.
