The mbox parser *should* still recover from this. *unless* the file
really is corrupted everywhere else too (like all
the From lines are borked). i.e. at worst you might get some messages
which are bunged up, but after the next From line it should re-sync.
In what way do you mean it cannot read the mbox at all? You get no
messages showing up at all?
Is it a very big mbox, could you send me (directly) a copy (compressed)
to check/verify?
!Z
On 11 Apr 2001 14:28:01 -0400, Jeffrey Stedfast wrote:
> Sounds like you didn't correctly remove the offending message. We really
> don't suggest editing mbox files unless you really know what you are
> doing.
>
> Jeff
>
> On 11 Apr 2001 09:34:32 -0700, Phil Schwartz wrote:
> >
> > I had an existing local/Inbox/mbox and related files using evo 0.9. I
> > recently received a message that upon viewing it would crash evo
> > everytime. I couldn't even highlight it and then delete it because evo
> > would still try to display it (which would result in a crash). After
> > repeating this problem 5 or 6 times I decided to edit to mbox file
> > directly and remove the offending message. However, upon doing so, evo
> > could no longer read the mbox at all. I tried moving the
> > mbox.ev-summary and mbox.ibex files out of the way, thinking that evo
> > would recreate them from the raw mbox file. However, this was not the
> > case.
> >
> > Is there any way to salvage this situation?
> >
> > I tried importing the modified file but that crashed too. D'oh.
> >
> > Phil
> >
> >
> > _______________________________________________
> > evolution maillist - [EMAIL PROTECTED]
> > http://lists.helixcode.com/mailman/listinfo/evolution
>
>
> _______________________________________________
> evolution maillist - [EMAIL PROTECTED]
> http://lists.helixcode.com/mailman/listinfo/evolution
_______________________________________________
evolution maillist - [EMAIL PROTECTED]
http://lists.helixcode.com/mailman/listinfo/evolution
