[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [imapsync] Size/Message Limitation?
|
From |
"Phil Pearl (Lobbes)" <phil at zimbra dot com> |
|
Subject |
Re: [imapsync] Size/Message Limitation? |
|
Date |
Tue, 8 Dec 2009 18:51:18 -0800 (PST) |
Inline...
> Hello Dereck,
>
> > $RCSfile: imapsync,v $ $Revision: 1.267 $ $Date: 2008/10/07 11:36:02
> $
> > and the module Mail::IMAPClient version used here is 2.2.9
>
> I suggest the Phil advice: use latest imapsync 1.286
> with latest 3.x Mail::IMAPClient
This should help, perhaps significantly. With that, you can take advantage of the reconnect logic that is available, I recommend:
--reconnectretry1 1 --reconnectretry2 1
> I don't know if it will solve your 10**6 issue.
>
> > Command line used :
> > /usr/bin/imapsync --host1 imap.gmail.com --ssl1
> > --user1 <login1> --password1 PWCHANGED --host2 127.0.0.1 --user2 <login2>
> > --password2 PWCHANGED --prefix2 INBOX.ENG. --authmech1 LOGIN --authmech2
> > LOGIN --syncinternaldates --folder Inbox --skipsize --nofoldersizes
> > --useheader Message-ID
>
> You can add --fast
Just remember that --fast will not sync flags, which may be OK depending upon your needs.
>
> > If I filter out some mail to different GMAIL labels, I can sync the
> > mail in those folders just fine up in range of 10,000 (thats the
> > most I have tested) emails. If I try to sync the [GMAIL]\All Mail
> > or put all archived mail back into INBOX, imapsync says 0 mail was
> > processed and 0 mail skipped... eventhough its has calculated there
> > to be over a million messages.
>
> It's a clearly a bug but I can't reproduce it.
>
> Can you try the --maxage option. May be it is a way to avoid moving
> your messages by hand in the 10000 folder.
>
> > debug and debugimap outputs loads of information, but does nothing
> > as to explain why it doesn't process the emails.
>
> No idea: my be memory, too long imap request/response ?.
> You're the first record talking about 10^6 messages in one folder.
The newer Mail::IMAPClient should hopefully provide better error messages on failure and possibly some better logging in debug too. There are certainly still bugs so please report back if you give it a try and things fail!
Phil