9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@messagingdirect.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mime
Date: Thu, 23 Nov 2000 10:18:43 +0000	[thread overview]
Message-ID: <86d7fn4pmz.fsf@gollum.esys.ca> (raw)
In-Reply-To: <20001122204959.D4FE0199F5@mail.cse.psu.edu>

>>>>> "presotto" == presotto  <presotto@plan9.bell-labs.com> 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


  parent reply	other threads:[~2000-11-23 10:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 20:49 presotto
2000-11-22 21:26 ` Boyd Roberts
2000-11-23 10:18 ` Lyndon Nerenberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-23 12:21 rog
2000-11-23 19:49 ` Boyd Roberts
2000-11-22 21:13 presotto
2000-11-22 15:46 rog
2000-11-22 15:02 ` Boyd Roberts
2000-11-22 15:16   ` Nigel Roles
2000-11-22 23:28   ` Steve Kilbane
2000-11-22 22:37     ` Boyd Roberts
2000-11-22 15:07 ` Boyd Roberts
2000-11-22 15:19 forsyth
2000-11-22 15:23 ` Boyd Roberts
2000-11-22 20:30   ` Boyd Roberts
2000-11-22 13:12 rog
2000-11-22 14:21 ` Boyd Roberts
2000-11-21 19:37 presotto
2000-11-21 20:04 ` Boyd Roberts
2000-11-21 23:07   ` Steve Kilbane
2000-11-22 13:50     ` Boyd Roberts
2000-11-21 23:25 ` rob pike
2000-11-21 23:31   ` Boyd Roberts
2000-11-22 10:31     ` matt
2000-11-22 14:00       ` Boyd Roberts
2000-11-22 14:53   ` Boyd Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86d7fn4pmz.fsf@gollum.esys.ca \
    --to=lyndon@messagingdirect.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).