🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.mail.mime
Article #146

Re: The reason for 76 characters limit of a MIME encoded header line?

#146
From: Hector Santos
Date: Mon, 28 Nov 2005 14:02
45 lines
2952 bytes
Your standard dumb online terminal was 80 characters wide. Punch cards
80/132,  JCL jobs, etc, all based around the original punch cards, etc.
Getting 132 characters was EXTRA effort for terminals and required special
graphic cards or "smart terminals"  plus you need glasses <g>

In short, for old school programmers, you had what you had, it was what it
was, everything "you type" or print when this stuff was invented, was done
in one nice row readable line that "fit"  the screen.

Most mail formats ever invented all were limited by the same inventions of
the time I/O limitations.

It carried on during the automation till today.

--
Hector Santos, Santronics Software, Inc.
http://www.santronics.com



"Masanori HATA" <hata@iname.com> wrote in message
news:dlehqb$laj$1@caraway.media.kyoto-u.ac.jp...
> Hello to all,
>
> I have a question about the number of characters that each of
> multiple-line header field that contains one or more 'encoded-words' is
> limited to 76 in RFC 2047 (section 2) (or in its former version 1522).
>
> Why is it 76 characters? Why isn't it 78 characters?
>
> In RFC 2822 (section 2.1.1) it is said that the number of characters in
> a line SHOULD be no more than 78 characters, excluding the CRLF.
>
> So the CRLF is excluded that each line of characters can be upto 80
> characters including the trailing CRLF.
>
> What is the reason for the decreasing two characters of the number of
> characters in a MIME encoded header line?
>
> Could anyone please give me suggestion? Any comment is appreciated.
>
> Regards,
>
> --
> Masanori HATA
Technical Details
Message-ID: <54Eif.37492$6y4.8538@bignews3.bellsouth.net>
Path: arc1-ca.pugleaf.net!g2news1.google.com!news3.google.com!news.glorb.com!bigfeed.bellsouth.net!bignumber.bellsouth.net!news.bellsouth.net!bignews3.bellsouth.net.POSTED!9a90cc71!not-for-mail
References: <dlehqb$laj$1@caraway.media.kyoto-u.ac.jp>

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!news.glorb.com!bigfeed.bellsouth.net!bignumber.bellsouth.net!news.bellsouth.net!bignews3.bellsouth.net.POSTED!9a90cc71!not-for-mail
From: "Hector Santos" <avs-tracker-address-comp.networks@isdg.net>
Newsgroups: comp.mail.mime,fj.mail
References: <dlehqb$laj$1@caraway.media.kyoto-u.ac.jp>
Subject: Re: The reason for 76 characters limit of a MIME encoded header line?
Lines: 46
MIME-Version: 1.0
Content-Type: text/plain;
 charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Message-ID: <54Eif.37492$6y4.8538@bignews3.bellsouth.net>
X-Complaints-To: abuse@bellsouth.net
X-Abuse-Info: Please forward a copy of all headers for proper handling
X-Trace: bhmkggakljkaanefdbdpiflmbcekedmfhojhikkbagflhcbojoekokoekhbbooiogeogkhologffoobpdnhfglpgkfechgkmljpcdgmjkimlaaoojpkbmbbogcdffjncknllgkpmbcapdllagghbjjfoaiemglci
NNTP-Posting-Date: Mon, 28 Nov 2005 09:00:33 EST
Organization: BellSouth Internet Group
Date: Mon, 28 Nov 2005 09:02:49 -0500