On Sun, Oct 25, 2009 at 8:28 PM, sidney <sidn...@gmail.com> wrote:Thanks for the additional analysis and details. Given what you've
> I had to close the GMail tab to get to stop the repeating error, then
> I searched for the date range again and changed the label of the
> message to a new one I created. Now that is the only mail message in
> that folder and clicking on it to display it still produces the error.
> It certainly seems like Google's problem. Would a correct workaround
described, it does seem like the best thing for Larch to do is to
ignore messages that trigger this error. The hard part, though, is
identifying them. When Larch scans headers in a folder, it does a
batch fetch of up to 1024 headers at a time, and the entire batch will
fail with this error if just one of the messages is corrupt. In order
to find the corrupt message, Larch would have to gradually decrease
the size of the batch until the fetch succeeds and the culprit is
identified, which could take a while.
Still, it'd be better for Larch to work around the problem slowly than
The only blocker now is that I'll need to be able to reproduce the
I don't suppose you'd be willing to try forwarding me your corrupt
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.