Article View: comp.mail.mime
Article #147Re: The reason for 76 characters limit of a MIME encoded header line?
From: Mark Crispin
Date: Mon, 28 Nov 2005 17:57
Date: Mon, 28 Nov 2005 17:57
35 lines
2915 bytes
2915 bytes
Although the ongoing use of 24x80 windows is certainly due to the memories
of "old school programmers", the recommended limitations of lines to fit
within 80 characters has an older cause.
In the "small-i internet" (when networks with different protocols were
interconnected for email) of two decades ago, it was impossible to
transmit mail reliably across non-TCP/non-SMTP networks unless it fit
within an 80 character line. Punch card image was a particularly
important concept in some of these.
Today, the "small-i internet" is more of a memory in the minds of
oldtimers; but it never has been certified as dead, extinct, vanished.
Thus, there is a reluctance to relax the limit, and thus risk breaking
some vestigal piece of "small-i internet"; especially as such may be in
some pathetic little Third World twarf that doesn't have much of a chance
of getting real Internet ("large-I Internet") before the sun novas.
Quite a few email technology rules are in place to benefit some ancient
facility that, for one reason or other, can't be updated.
As a practical matter, it really doesn't matter what the line lengths are.
Flowed text and quoted-word continuation rules exist so that users should
neither know, nor particularly care, how the bits are represented. The
only people who should care are programmers who write email clients.
In typography, most text has considerably narrower margins than 80
characters to enhance readability. Typewriters typically have their
margins set at 65. Books (excluding geek technical books) have narrower
margins.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
Technical Details
Message-ID:
<Pine.OSX.4.64.0511280941280.562@pangtzu.panda.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!newshub.sdsu.edu!logbridge.uoregon.edu!arclight.uoregon.edu!news.u.washington.edu!pangtzu.panda.com!mrcReferences:
<dlehqb$laj$1@caraway.media.kyoto-u.ac.jp> <54Eif.37492$6y4.8538@bignews3.bellsouth.net>Show Full Headers
Complete Article Headers
X-Google-Thread: 10381e,da93d06d911be531 X-Google-Thread: 106028,da93d06d911be531 X-Google-Attributes: gid10381e,gid106028,public X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!newshub.sdsu.edu!logbridge.uoregon.edu!arclight.uoregon.edu!news.u.washington.edu!pangtzu.panda.com!mrc From: Mark Crispin <mrc@CAC.Washington.EDU> Newsgroups: comp.mail.mime,fj.mail Subject: Re: The reason for 76 characters limit of a MIME encoded header line? Date: Mon, 28 Nov 2005 09:57:24 -0800 Organization: University of Washington Lines: 35 Sender: mrc@pangtzu.panda.com Message-ID: <Pine.OSX.4.64.0511280941280.562@pangtzu.panda.com> References: <dlehqb$laj$1@caraway.media.kyoto-u.ac.jp> <54Eif.37492$6y4.8538@bignews3.bellsouth.net> NNTP-Posting-Host: pangtzu.panda.com Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Trace: gnus01.u.washington.edu 1133200662 20368 206.124.149.117 (28 Nov 2005 17:57:42 GMT) X-Complaints-To: help@cac.washington.edu NNTP-Posting-Date: Mon, 28 Nov 2005 17:57:42 +0000 (UTC) In-Reply-To: <54Eif.37492$6y4.8538@bignews3.bellsouth.net>