| Tuxedo 2007-06-16, 7:12 am |
| Dr.Ruud wrote:
> Tuxedo schreef:
>
>
> I assume that you want to find out at which message the problem starts
> and at which line in the mbox file that is, and start fixing from there.
Yes. If I only knew. I tried to split it up, delete sections and so on,
only to find the problem appearing in many sections, but not knowing
exactly where. The file is just too big to locate the error manually.
>
> Be careful not to introduce extra problemes with the move of the mbox
> file from the Windows to the Linux system (maybe you should do a
> dos2unix on the file, and then maybe you shouldn't, formail will DWIM).
>
> You can use formail together with procmail to convert from mbox to
> maildir format (the one file per message in new/ cur/ tmp/ structure)
> like this:
>
> formail -defYz \
> -s procmail -m VERBOSE=yes DEFAULT="test_maildir/" /dev/null <
> crappy.mbx
>
> (the "test_maildir/" will be created in the user's $HOME, include
> MAILDIR="/some/path" to redirect)
>
> The "-defYz" just lists all interesting options for this case, change at
> will, see man formail.
>
> From the maildir structure you should be able to find out at which
> message the split up breaks.
>
Many thanks for all the tips, especially about formail. However, in this
particular case, I will leave the problematic mbox to rest, because it is
my ambition not to deal with anything from the Windows user space. In
realising it is probably a 99% Mozilla bug, my solution became to simply
transfer the file to a good old BSD mail server and let the file owner
access it's content via Neomail - an exceptional PERL program which handles
mbox pop-mail via a no-frills web interface. I just tested that and the
full mbox was read, as fine as it was in MUTT or another native *nix mailer.
Sooner or later Mozilla developers will likely fix the bug, whatever it is.
|