Closed GoogleCodeExporter closed 8 years ago
It's hard to say want went wrong... Would it be possible to try this with the
git version? That should give a little bit more information.
Original comment by digg...@gmail.com
on 21 Dec 2013 at 6:02
Thank you for the reply. I did compile and install the git version. The output
showed three invalid messages. I checked the messages and they were indeed
invalid, with a missing header and beginning part way through a message. So I
deleted them again and did a rebuild, which worked with no problems. So it
looks like the github version gracefully ignored the bad messages and works
perfectly. Whether this was the cause of the fail in the original I am not
sure, but as the github version is working perhaps we can close this bug. Thank
you for your help.
$ mu index --rebuild
indexing messages under /home/neil/Maildir [/home/neil/.mu/xapian]
/ processing mail; processed: 56550; updated/new: 56550, cleaned-up: 0
mu: message seems invalid, ignoring
(/home/neil/Maildir/sent/cur/1386281836.000037.mbox:2,S)
| processing mail; processed: 57075; updated/new: 57074, cleaned-up: 0
mu: message seems invalid, ignoring
(/home/neil/Maildir/sent/cur/1386281836.000610.mbox:2,S)
| processing mail; processed: 57375; updated/new: 57373, cleaned-up: 0
mu: message seems invalid, ignoring
(/home/neil/Maildir/sent/cur/1386281836.000905.mbox:2,)
- processing mail; processed: 57825; updated/new: 57822, cleaned-up: 0
cleaning up messages [/home/neil/.mu/xapian]
- processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 57867 msg/s
\ processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 271 second(s), ~ 213 msg/s
And after deleting the invalid messages
$ mu index --rebuild
indexing messages under /home/neil/Maildir [/home/neil/.mu/xapian]
- processing mail; processed: 57825; updated/new: 57825, cleaned-up: 0
cleaning up messages [/home/neil/.mu/xapian]
- processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 1 second(s), ~ 57867 msg/s
\ processing mail; processed: 57867; updated/new: 0, cleaned-up: 0
elapsed: 273 second(s), ~ 211 msg/s
Original comment by prof.nei...@gmail.com
on 27 Dec 2013 at 11:31
Okay, thanks for verifying this! I'll close this issue.
Original comment by digg...@gmail.com
on 29 Dec 2013 at 3:50
Original issue reported on code.google.com by
prof.nei...@gmail.com
on 19 Dec 2013 at 12:49