Re: rfc1495 & mime-body-part

"Harald T. Alvestrand" <> Thu, 02 June 1994 07:54 UTC

Received: from by IETF.CNRI.Reston.VA.US id aa00381; 2 Jun 94 3:54 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00377; 2 Jun 94 3:54 EDT
Received: from by CNRI.Reston.VA.US id aa00863; 2 Jun 94 3:54 EDT
Received: from by with SMTP (PP) id <>; Thu, 2 Jun 1994 09:43:51 +0200
Received: from localhost by with SMTP (PP) id <>; Thu, 2 Jun 1994 09:43:23 +0200
To: Justin Ziegler <>
Subject: Re: rfc1495 & mime-body-part
In-reply-to: Your message of "Tue, 31 May 1994 14:13:41 +0200." <>
MIME-version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: Quoted-Printable
Date: Thu, 02 Jun 1994 09:43:18 +0200
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Harald T. Alvestrand" <>
Message-ID: <"survis.sur.104:">

this is a real headache.
I would dearly love to keep those headers, and it will
harm interoperability that they are lost, but
*where can I put them?????*

When I define the bodypart (like the mime-tunnel one), the
answer is simple: Create a parameter for them.

When there is only one bodypart in a message, the answer
is simple too: Put them in the RFC-822-Headers extension.

But when I have (for instance) multipart Text/Plain, which
gateways into multiple GeneralText parts, there
is *no place* where I can put them that I can see.
Any suggestion?

                   Harald T. Alvestrand