[tz] Converting TZ DB files to pretty markup
Steffen Daode Nurpmeso
sdaoden at gmail.com
Tue Jan 29 12:14:12 UTC 2013
Marc Lehmann <schmorp at schmorp.de> wrote:
|On Mon, Jan 28, 2013 at 12:58:46PM +0100, Steffen Daode Nurpmeso \
|<sdaoden at gmail.com> wrote:
|> And yes, a good mailer converts 'From ' lines to quoted printable
|> encoding instead of using the '>From ' quoting because it doesn't
|> modify actual data content. :)
|Except ">From " encoding doesn't modify actual data content either, and
yes it does. yes it does. yes it does.
|even an average mailer needs to support both formats when reading mbox
|(See rfc4155 or http://qmail.org./man/man5/mbox.html for details)
I did have had a .. relationship with both of these, too.
I think NetBSD's Mail(1) is the outstanding neat and clean one in
respect to conformance to these standards, at least still and as
of *today*, and to the best of my knowledge.
'From_' quoting has a terribly long story beside that, as many do
know, and many false solutions imho have been used or are still in
use even today; let's just mention the rather famous thread from
Unfortunately POSIX and backward tools like Python's standard
library MBOX support go for a 'From_' quoting that can be dated
back to RFC 976 -- from February 1986!
The good thing about using quoted-printable encoding for 'From '
lines, instead of whatever MBOXO/MBOXRD etc. quoting, is, beside
being required for S/MIME (digest does not change since data
content is not modified, but only the transfer-encoding), that
even those backward-oriented and savage tools will work with
message content that is produced today, transparently.
| The choice of a Deliantra, the free code+content \
| -----==- _GNU_ http://www.deliantra.net
| ----==-- _ generation
| ---==---(_)__ __ ____ __ Marc Lehmann
| --==---/ / _ \/ // /\ \/ / schmorp at schmorp.de
| -=====/_/_//_/\_,_/ /_/\_\
More information about the tz