[Users] Mbox import has failed.

[Adrian]

Well, to sort-of answer my own question, I never found out what was
wrong. But as the source was many old mbox files from different sources
including some old Eudora Mail ones with nonstandard features, I
decided to try another way,

I split up each mbox file into individual mails in its own directory
and named each file with a serial number to simulate MH folders.  I
haven't done the final one yet, but I find that you can create an empty
local folder in Claws, dump numbered files into it and Claws is happy to
create its metadata files.  The order of numbering doesn't matter, the
mails can be in random order as they get sorted by the criteria you
choose, and can have some gaps in the numbers.

Just reporting this here, obviously not the right place, but might be
of interest.

Adrian

On Sat, 14 Nov 2020 14:27:38 +0000
Adrian <adrian at aeolian.org.uk> wrote:

> I found some more non-text characters and removed them.  And ran
> unix2dos to correct the line endings.
> 
> The new version gives the same error, but like the first time, after a
> few seconds the stats show that some messages were imported.  6491
> this time, an improvement, but there are 16469 messages in the mbox
> file.
> 
> To clarify my original question, is there a log or a verbose mode I
> can turn on to give some insight about what Claws mail is failing on?
> ~/.claws/claws.log says nothing about the import and filtering.log
> just shows the new messages being filtered.
> 
> Adrian
> 
> On Sat, 14 Nov 2020 13:36:01 +0000
> Adrian <adrian at aeolian.org.uk> wrote:
> 
> > Sorry.  What I mean is I get an Error box with the subject line,
> > i.e. "Mbox import has failed".
> > 
> > After the first time I later found that 5001 mails had imported.
> > The .mbx file is pretty large.  I then found the point in the file
> > where import stopped.  No obvious problems around there, but I
> > created a file starting from a few mails later and tried to import
> > that - with the same failure.  This time no mails imported at all.
> > 
> > Using a text editor on the mbx file reports invalid characters, so I
> > piped it through strings -w.  Same error.
> > 
> > I found that some of the message delimiters, i.e. "From ???@???...."
> > were concatenated onto the last line of the previous message so I 
> > 
> > I'm now chopping the file into smaller files.  I'll start with just
> > one mail or two, process of elimination.
> > 
> > ....aaah.  My line separators are \n and they should be \r\n.  I'll
> > repair, retry and repost if that was the reason - which I suspect it
> > is.
> > 
> > Thanks
> > 
> > Adrian
> > 
> > On Fri, 13 Nov 2020 21:04:49 +0000
> > Adrian <adrian at aeolian.org.uk> wrote: 
> >   
> > > And I get this error.    
> > 
> > What error did you get?
> > 
> > with regards
> > 
> > Paul
> > 
> > Begin forwarded message:
> > 
> > Date: Fri, 13 Nov 2020 21:04:49 +0000
> > From: Adrian <adrian at aeolian.org.uk>
> > To: users at lists.claws-mail.org
> > Subject: Mbox import has failed.
> > 
> > 
> > I'm trying to import an mbox file (you guessed?)
> > 
> > And I get this error.
> > 
> > Now, I don't exactly blame Claws Mail for that.  To be honest, I've
> > faked up the mbox file by concatenating select individual mails from
> > other mbox files, and may have got something wrong.  The mails are
> > not in date order, for one thing.
> > 
> > But I really would like an idea of what Claws itself thinks is
> > wrong!
> > 
> > Any ideas?
> > 
> > Adrian