After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 535584 - “Corrupted” mbox, deleting *.ev-summary does not help: Expected a From line here, didn't get it. SO recovering....
“Corrupted” mbox, deleting *.ev-summary does not help: Expected a From line h...
Status: RESOLVED DUPLICATE of bug 533122
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Urgent blocker
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-05-29 20:59 UTC by Paul Menzel
Modified: 2008-06-12 21:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Paul Menzel 2008-05-29 20:59:24 UTC 
Please describe the problem:
My inbox has about 8000 messages, where around 300 are unread. Some does ago it was displaying ”Saving Inbox” in a tab, but the percentage was not increasing and stopped at a certain value. On the terminal the output was

(evolution:7391): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering.... [the numer was different].

I than did

evolution --force-shutdown

and started again, but it was the same. After some more tries, it worked but I head a lot of duplicated messages. I remembered this from the past and deleted the *.ev-summary file, but then starting evolution it stopped while displaying 6 or 20 or some different unread messages. After doing restarting evolution a few times it then showed all messages, but mostly the unread ones where shown twice and the message on the console was still there. The bug was formerly known as—I think—Bug 213072 – [Fixed in 2.22] Error "Summary and folder mismatch" [1].

[1] http://bugzilla.gnome.org/show_bug.cgi?id=213072

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Looking at the mbox file everything is ok and loading it with

$ mutt -f .evolution/mail/local/Inbox

and mutt does not complain.

1. So does evolution have a problem with big mbox files?

2. And is there a way to let evolution display in what line of the mbox file it has a problem? Or is this the number in

(evolution:7391): camel-local-provider-WARNING **: Expected a From line here, didn't get it. SO recovering....

3. Is there an option in Evolution to check an mbox file?


Thanks a lot,

Paul
Comment 1 Paul Menzel 2008-06-06 06:34:54 UTC 
Dear developers,


here is a small update on this issue.

Yesterday X (openchrome) or the kernel froze and I had to reset the computer. On reset filesystems were recovered from the journal—home is ext3 (rw, relatime) on an LUKS-encrypted raid1 LVM device.

Starting evolution afterwards, I did not get any “corrupted mbox” messages and my Inbox (which by the way just has around 4400 messages) was “good” again. Just the tags, if I replied to or forwarded a message, are lost.

But now I can work efficiently again, without having evolution taking all the processing power trying to save the Inbox every 15(?) minutes.

So I have no clue what was wrong. But I think it would be a great idea, to let evolution output the line of the mbox where it thinks the from-line is wrong or missing.


Thanks a lot,

Paul
Comment 2 André Klapper 2008-06-12 21:44:47 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 533122 ***