[PATCH] Output more detailed error on corrupt LocalStatus

[Sebastian Spaeth]

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
catch. 

> Indeed that corrupt line is there.  but it's a sequence of non-consecutive numbers... Here is an excerpt:
> 
> 40213:
> 40214:
> 40215:
> 40217:R
> 40218:S
> 40229:S
> 4023(0x00)(0x00)P(0x00)(0x01)(0x00)(0x00)(0x00)0:S
> 40261:S
> 40262:S
> 40264:
> 40269:S
> 40270:
> 40276:
> 40279:R

Actually, all other lines are OK, they just have no flags. The only
damaged line is:

4023(0x00)(0x00)P(0x00)(0x01)(0x00)(0x00)(0x00)0:S

I suspect that it is supposed to mean:
40230:S

but I have no clue how those spurious "0" and the "1" entered the
picture.

> 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 ?

No.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/offlineimap-project/attachments/20110504/fbc622e2/attachment-0001.sig>