Re: How to convert maildir to mbox format
On Sun, 20 Jun 2004 17:10:34 -0500, David Champion wrote:
>
>Your messages came through fine -- maybe it was just your own incoming
>copy that was blocked or mangled by Mindspring?
Glad it came through. Probably only my incoming blocked as you say.
>Anyway, I'm referring here to your first message, because it has
>more complete content for the mbox message. Your resend uses a
>message/rfc822 attachment, so it lacks the V7 From_ line. Since that's
>what we're looking at, I went with the other one. :) The first copy
>you sent included the full, literal mbox message, base64-encoded as an
>octet-stream.
What I did was load the entire mbox file into an editor.
I selected the first message in its entirety, pasted it to a file and attached
it to the first message to you.
Second message to you I simply edited formail.msg and ga20xs0.msg and removed
only the body of the message.
>* On 2004.06.20, in <E1Bc2nv-0007QO-00@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
>* "Larry Alkoff" <labradley@xxxxxxxxxxxxxx> wrote:
>>
>> I looked at the original .msg files and compared them to the created
>> mbox file. It seems that _every_ message in the file was created by
>> formail with that "funny" From line. None of the original messages
>> seem to have anything like that so I'm wondering if and why formail
>> created the data and where it came from.
>
>I think you'll see it if you look at the message with full headers.
>(Press "h" to toggle "header weeding".)
I'm not looking at the message in Mutt but using less or an editor on the mbox
file.
>
>> I've attached one of the original messages (ga20xs0.msg) and cut out
>> the same message from the mbox file (formail_msg).
>
>The header in Maildir and MH folders that's analogous to the V7 ("mbox")
>"From " line is Return-Path:. Here's the Return-Path: from your maildir
>message copy:
>
>> Return-Path: trxmanager-return-515-38565871@xxxxxxxxxxx
>
>And here are the Return-Path: and From_ from the V7 copy you attached:
>
>> From trxmanager-return-515-38565871@xxxxxxxxxxx Sat Jun 19 08:55:02 2004
>> Return-Path: <trxmanager-return-515-38565871@xxxxxxxxxxx>
>
>
>I think formail will construct a From_ line from the From: header, if
>Return-Path: is missing, but since Return-Path: represents the envelope
>sender, and so does From_, that's the ideal.
I think I understand now.
The first part of the From header is literally the contents of Return-Path:
That is what I would expect and didn't look closely enough at Return-Path:.
It looks like formail did its job very nicely and now I have a method of easily
converting all the .msg files
in a directory to mbox format. This gives me the mbox option.
This is another subject and if we start discussing this I'll change the subject.
That's what you get for being so helpful - more questions <g>
I'm still stuck on how to organize the 250+ subdirectories of files into a
structure Mut will be happy with.
A lot of those subdirs are rarely used, like trxmanager/save for messages I
want to save but hardly ever need to see.
When I simply copy them over from Windows and make them maildirs by adding new,
cur and tmp, I can read the messages in
each folder if I can get to them but Mutt doesn't easily navigate to them.
Usually I have to specify the full path which is a PITA.
Does Mutt have a way to selectively hide mail directories that clutter up the
folder view?
Alternatively is there a way for Mutt to hide entire sections of the folder
view?
Most graphical MUA have a little plus sign you can click on to expand and see
the tree it represents.
I don't think Mutt can do that but Sylpheed can. However, Sylpheed uses MH
format which I don't like.
Larry Alkoff N2LA - Austin TX