After speaking with the package maintainer about this and doing a little more experimentation, it became clear that this is really caused by a bug in the pine mbox format. mb2md expects message content lines in mbox files which begin with the word From to have been converted to >From:
>From blahblahblah goes to >From blahblahblah when located in the message body rather than the header. There was some version of pine which didn't do this, leading to the current problem. Particularly since RFC 822 gives a lot of leeway with regard to what header fields are required, there's no deterministic way to solve this problem in every case. Consequently it makes most sense to leave mb2md as is and edit the content of mbox which have this problem by hand. On the one hand this isn't practical when converting lots of mbox files, but it's also fairly rare to find a line beginning with From. In any case, this is what I did with my incorrectly formatted mbox files. Note in passing that using mb2md -c probably won't save you from this problem, since mbox files with incorrectly encoded From content lines probably won't include a Content-Length header, either. Sorry for the false bug alarm. Someone should mark this bug as invalid. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771893 Title: Incorrectly identifies message body lines starting with the word From as the beginning of a new message -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
