[PATCH] Output more detailed error on corrupt LocalStatus
christocoleman at yahoo.com
Wed May 4 12:59:09 BST 2011
On Tue, 3 May 2011 11:13:28 -0700 (PDT), chris coleman <christocoleman at yahoo.com> wrote:
> It uses some python 2.6 syntax for the exception handling, and compile failed.
Ohh right, for python 2.5 you would need to use it as you did. Nice
> Indeed that corrupt line is there. but it's a sequence of non-consecutive numbers... Here is an excerpt:
Actually, all other lines are OK, they just have no flags. The only
damaged line is:
I suspect that it is supposed to mean:
but I have no clue how those spurious "0" and the "1" entered the
> The big question: how do you recommend regenerating these damaged lines of data without losing any email in this user's INBOX?
Try the above.
> Will an email be deleted if it doesn't have its corresponding number in this file?
No, but you will get another crash when it tries to access an email that
is not listed in here and you will know which one was missing :-).
> Or... is it the opposite, will this file automatically regenerate the missing number of any email that is not listed in it ?
I did what you recommend, fixed the line 40230:S in the LocalStatus/INBOX file, and ran 6.3.3.
"Copy message xxxxx IMAP[INBOX] -> MappedIMAP[INBOX]"
It copied probably 100 messages from remote to local (this is expected... ) until it got to message 55428.
It's sitting there for over 5 minutes now.. clearly it has hung.
What do you recommend ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OfflineIMAP-project