[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Request Deprecation of mts.conf's mmdelim1 and mmdelim

From: Jon Fairbairn
Subject: Re: [Nmh-workers] Request Deprecation of mts.conf's mmdelim1 and mmdelim2.
Date: Wed, 24 May 2017 09:50:29 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Robert Elz <address@hidden> writes:

>     Date:        Tue, 23 May 2017 09:35:52 +0100
>     From:        Jon Fairbairn <address@hidden>
>     Message-ID:  <address@hidden>
>   | One of the first things I learnt was that
>   | using in-band data as a separator is a bad idea,
> Like most generalizations, that is sometimes true, but sometimes not.
>   | so mmdf was obviously a more sensible format than mbox.
> Which doesn't follow at all, as MMDF is also using in-band data as
> a separator, just a different one.

Back when I made the decision it was out of band.

> I never really used MMDF format, so I am not sure of its details, but
> as I understand it, the only real issue with mbox format is that the
> conversion isn't invertible, that is, in that format, a line that used
> to start "From" is stored as ">From" (which exact lines that happens to
> depends upon implementation to some extent, but that doesn't matter),
> whereas an input like that started ">From" is also stored as ">From".
> When it comes time to extract the message, there's no way to invert that
> addition of the '>' as there's no way to determine whether the '>' was
> one that was added for this purpose or not.

Exactly, but if SOH*4 is now in band, it looks like I now have
to redesign my archive scripts.

Jón Fairbairn                                 address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]