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

Article View: comp.mail.mime

Article #145

#145

From: Masanori HATA
Date: Wed, 16 Nov 2005 07:35

27 lines
2448 bytes

Thank you Mark, I could see the point.

Mark Crispin wrote:
> I remember when this was discussed nearly 15 years ago.  There was 
> testimony that certain email gateways could not be trusted not to break 
> lines with a larger limit, and that limiting the lines to 76 octets was 
> the only way to be sure that would not happen.  Line breaking by an 
> email gateway would be disasterous if it happened to an encoded-word.  I 
> don't remember the details, but I'm sure that the working group 
> discussion archives are available someplace.
> 
> RFC 2822 was produced 10 years after MIME's decision was made.  The 78 
> character recommendation in RFC 2822 is to avoid line break behavior on 
> 24x80 type displays, as opposed to worrying about email gateways that do 
> line breaking.

The 76 characters limit in RFC 2047 is come from quite a separate reason 
from that of 78 characters limit in RFC 2822...

So I thought these two numbers have a certain relation with each other 
that there should be the reason for the subtraction of number. --Perhaps 
the precondition was wrong.

Regards,

-- 
Masanori HATA

Technical Details

Message-ID: <dlenf6$qfi$1@caraway.media.kyoto-u.ac.jp>

Path:

arc1-ca.pugleaf.net!g2news1.google.com!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.moat.net!mmcatv.co.jp!newsfeed.media.kyoto-u.ac.jp!news.media.kyoto-u.ac.jp!not-for-mail

References: <dlehqb$laj$1@caraway.media.kyoto-u.ac.jp> <Pine.OSX.4.64.0511152234250.533@pangtzu.panda.com>

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!news4.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.moat.net!mmcatv.co.jp!newsfeed.media.kyoto-u.ac.jp!news.media.kyoto-u.ac.jp!not-for-mail
From: Masanori HATA <hata@iname.com>
Newsgroups: comp.mail.mime,fj.mail
Subject: Re: The reason for 76 characters limit of a MIME encoded header 
  line?
Date: Wed, 16 Nov 2005 16:35:01 +0900
Organization: Individual
Lines: 27
Sender: hata@iname.com
Message-ID: <dlenf6$qfi$1@caraway.media.kyoto-u.ac.jp>
References: <dlehqb$laj$1@caraway.media.kyoto-u.ac.jp> <Pine.OSX.4.64.0511152234250.533@pangtzu.panda.com>
NNTP-Posting-Host: pl1528.nas924.soka.nttpc.ne.jp
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Trace: caraway.media.kyoto-u.ac.jp 1132126503 27122 219.102.121.248 (16 Nov 2005 07:35:03 GMT)
X-Complaints-To: news@news.media.kyoto-u.ac.jp
NNTP-Posting-Date: Wed, 16 Nov 2005 07:35:03 +0000 (UTC)
User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923)
X-Accept-Language: ja, en-us, en
In-Reply-To: <Pine.OSX.4.64.0511152234250.533@pangtzu.panda.com>

Reply to Parent Message