I ran into this problem and I think I can tell you one way to re-produce it.
I logged in to my regular Ubuntu 8.10 box from another linux box (SuSE 10.3) using ssh -X. I ran evolution in remote XTerm mode for a couple of days (I was having issues with the video on the main box).
On the remote box, the shell I used to start the remote XWindow session reported some errors (maybe about a hundred) of two kinds:
(evolution:5533): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering....
I got about 90 of those in the screen rollback summary from the remote shell history.
Now, when I switched back to my Ubuntu HH box, evolution is extremely slow and cpu-intensive, showing the error message described in this thread: Error while Storing folder 'INBOX'
I also see a modal dialog box with the error "Detected a corrupt mbox file or an invalid 'From' header." I'll attach that screen shot.
I also observed the duplicate messages mentioned earlier in this thread.
Are there any evolution utils to fix a corrupted mbox file? Losing a few messages would be ok but losing them all would be like having a lobotomy, and I'd like to avoid that.
Many thanks to all who contribute in big and little ways
I ran into this problem and I think I can tell you one way to re-produce it.
I logged in to my regular Ubuntu 8.10 box from another linux box (SuSE 10.3) using ssh -X. I ran evolution in remote XTerm mode for a couple of days (I was having issues with the video on the main box).
On the remote box, the shell I used to start the remote XWindow session reported some errors (maybe about a hundred) of two kinds:
(evolution:5533): camel-local- provider- WARNING **: Expected a From line here, didn't get it. SO recovering....
I got about 30 of those, and
(evolution:5533): camel-CRITICAL **: get_message_info: assertion `folder->summary != NULL' failed
I got about 90 of those in the screen rollback summary from the remote shell history.
Now, when I switched back to my Ubuntu HH box, evolution is extremely slow and cpu-intensive, showing the error message described in this thread: Error while Storing folder 'INBOX'
I also see a modal dialog box with the error "Detected a corrupt mbox file or an invalid 'From' header." I'll attach that screen shot.
I also observed the duplicate messages mentioned earlier in this thread.
Are there any evolution utils to fix a corrupted mbox file? Losing a few messages would be ok but losing them all would be like having a lobotomy, and I'd like to avoid that.
Many thanks to all who contribute in big and little ways
Dave