Re: How to convert maildir to mbox format
Your messages came through fine -- maybe it was just your own incoming
copy that was blocked or mangled by Mindspring?
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.
* 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'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.
--
-D. dgc@xxxxxxxxxxxx NSIT::ENSS
No money, no book. No book, no study. No study, no pass.
No pass, no graduate. No graduate, no job. No job, no money.
T h e U n i v e r s i t y o f C h i c a g o