home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.mail.mime:54 comp.mail.mh:1446
- Newsgroups: comp.mail.mime,comp.mail.mh
- Path: sparky!uunet!spool.mu.edu!yale.edu!yale!gumby!destroyer!ncar!csn!boulder.parcplace.com!imp
- From: imp@boulder.parcplace.com (Warner Losh)
- Subject: MIME RFC nit????
- Message-ID: <Bzy63n.CAy@boulder.parcplace.com>
- Sender: news@boulder.parcplace.com
- Organization: ParcPlace Boulder
- Date: Mon, 28 Dec 1992 02:11:46 GMT
- Lines: 25
-
- mh 6.8 barfs on the following header:
-
- Content-Type: message/external-body; access-type=local-file;
- name=/x/ap1/imp/Mail/inbox/29
-
- but it does accept the following header:
-
- Content-Type: message/external-body; access-type=local-file;
- name="/x/ap1/imp/Mail/inbox/29"
-
- RFC1341 uses the following example (on page 40, ASCII version):
-
- Content-Type: message/external-body; access-type=local-file;
- name=/u/nsb/Me.gif
-
- It would seem to me that this example is in error, in light of the
- parameter definitions on page 7, listing "/" as a tspecial, thus in
- need of quoting.
-
- Is this nit old news? Does anybody care?
-
- Warner
- --
- Warner Losh imp@boulder.parcplace.COM ParcPlace Boulder
- I've almost finished my brute force solution to subtlety.
-