From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: Lyndon Nerenberg Message-ID: <86d7fn4pmz.fsf@gollum.esys.ca> Content-Type: text/plain Content-Transfer-Encoding: 7bit References: <20001122204959.D4FE0199F5@mail.cse.psu.edu> Subject: Re: [9fans] mime Date: Thu, 23 Nov 2000 10:18:43 +0000 Topicbox-Message-UUID: 3039ce28-eac9-11e9-9e20-41e7f4b1d025 >>>>> "presotto" == presotto writes: presotto> However, I'm still perplexed as to what to put in the presotto> header of a multipart message. Does the transfer presotto> encoding specified there pertain to the whole message or presotto> just to the presotto> nyah nyah, if you only had a MIME mailer you wouldn't presotto> see this presotto> message that starts every multipart message? If the message contains a C-T-E header in the 822 headers, it applies to the _entire_ message body (i.e. everything after the CRLFCRLF 822 header/body separator). If any of the mime body parts contain a C-T-E header the 822 headers should *not* contain a C-T-E header. Instead, each mime body part should have an explicit C-T-E header (or an implicit "C-T-E: 7bit" indicated by the absence of a C-T-E header on a particular body part). As for the "nyah nyah" blob at the beginning of a mime multipart, consider that that text will only be displayed by non-mime-aware software, therefore it only makes sense to include only US-ASCII characters in that text. You could also argue that in a multipart message the "nyah nyah" part isn't really a mime body part (since you can't reference it via mime), and therefore falls outside the mime domain. If it's not mime, it is by definition 7bit content. If you really want a definitive "ruling" on this you should talk to Ned Freed. --lyndon