9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "erik quanstrom" <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, "Russ Cox" <rsc@swtch.com>
Subject: Re: [9fans] [Fwd: road sign]
Date: Mon, 10 Oct 2005 21:34:51 -0500	[thread overview]
Message-ID: <20051011023451.570F41AB1BD@dexter-peak.quanstro.net> (raw)
In-Reply-To: <20051011015640.5EEA91AB1BD@dexter-peak.quanstro.net>

i'm not sure if this is quite right (does apple publish specs on this junk?),
but treating "multipart/appledouble" as "multipart/alt" and picking the
first sub document that is not of type "application/applefile" seems to
do the right thing. this Content-Type tree now:

Content-Type: multipart/mixed;
	boundary=------------000409010601080409080502
.00Content-Type: text/plain; charset=utf-8
.01Content-Type: message/rfc822;
	name="road sign"
.01.00Content-Type: multipart/mixed;
	boundary=Apple-Mail-3-273748659
.01.00.00Content-Type: text/plain; charset=utf-8
.01.00.01Content-Type: image/jpeg;
	name="IMG_3043.JPG"

"erik quanstrom" <quanstro@quanstro.net> writes

| 
| apple's mail program has sent some goofy mime headers. Note the
| "multipart/appledouble". this definately isn't part of the rfcs.
| 
| (the output included here is a little strange because it's the mimetypes /after/ charset
| conversion and de-transfer-encoding. output from a program that only i suffer from.
| subparts of "multipart/appledouble" don't appear because it's not recognized.)
| 
| ; ./mimedesc $m/1128992546.9661*
| Content-Type: multipart/mixed;
| 	boundary=------------000409010601080409080502
| .00Content-Type: text/plain; charset=utf-8
| .01Content-Type: message/rfc822;
| 	name="road sign"
| .01.00Content-Type: multipart/mixed;
| 	boundary=Apple-Mail-3-273748659
| .01.00.00Content-Type: text/plain; charset=utf-8
| .01.00.01Content-Type: multipart/appledouble;
| 	boundary=Apple-Mail-4-273748660
| 


  reply	other threads:[~2005-10-11  2:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-10  3:57 Ronald G Minnich
2005-10-10 19:52 ` Russ Cox
2005-10-11  1:56   ` erik quanstrom
2005-10-11  2:34     ` erik quanstrom [this message]
2005-10-11  2:49     ` Chris Collins
2005-10-11  3:05       ` Jeff Sickel
2005-10-11  5:52         ` David Leimbach
2005-10-11  7:11           ` Chris Collins
2005-10-11  8:05             ` leimy2k
2005-10-11  7:25           ` Uriel
2005-10-11 10:05             ` erik quanstrom
2005-10-13  2:09             ` Jeff Sickel

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=20051011023451.570F41AB1BD@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=rsc@swtch.com \
    /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).