tobold.org

correct • elegant • free

△ comp.mail.* △

◅ Where are bounces supposed to go?

the Apparently-To: field ▻

Looking for doc on Content-Length

In article <1994Jul2.185659.29068@chemabs.uucp>, Larry W. Virden
<lvirden@cas.org> wrote:
>What RFC details Content-Length headers?

None.

The story so far as I know it is that someone at AT&T decided to throw
out the idiotic `traditional Unix' maildrop format (hooray!) only to
replace it with the idiotic `content-length-header' maildrop format.

It's only for local use, so it doesn't need an RFC: it should never
appear on a message in transmission.  If it's documented anywhere, it'll
be the man pages for the systems that use it.

Oh, the MMDF/PP maildrop format is idiotic, too.  Just in case you were
wondering :-).

Tim.
--
Tim Goodwin        | "Any time *anything* goes wrong on a
Public IP Exchange | PC, I immediately suspect a hardware
Cambridge, UK      | problem :-)." -- Chris Torek

Original headers:

From: tim@pipex.net (Tim Goodwin)
Newsgroups: comp.mail.headers
Subject: Re: Looking for doc on Content-Length
Date: 4 Jul 1994 12:52:13 +0100
Organization: PIPEX, 216 Science Park, Cambridge, England
Message-ID: <2v8t5d$8qt@sink.pipex.net>
References: <1994Jul2.185659.29068@chemabs.uucp>

△ comp.mail.* △

◅ Where are bounces supposed to go?

the Apparently-To: field ▻