Now I'm confused, befuddled, intimidated and overwhelmed.
So let me ask two, I hope, simple questions.
Is it reasonably safe for me to put characters (octets) greater than 127 in the
body, excluding any attachments, of a message?
If so, what encodings is it reasonably safe for me to use for
I had Nmh stumble on a mime msg for the first time ever just now.
The workaround was to edit the C-T from file/pdf to application/pdf.
MUA was Apple Mail (2.1084). The PDF was inside a forwarded msg so
perhaps Mail.app isn't at fault.
Just fyi; I'm not looking for a cure.
steve
--
$
Steve wrote:
MUA was Apple Mail (2.1084). The PDF was inside a forwarded msg so
perhaps Mail.app isn't at fault.
I'd be really surprised if Apple Mail was at fault. But
someone is:
Content-Type: file/pdf;
file is not a registered Media Type according to IANA:
Content-Type: file/pdf;
file is not a registered Media Type according to IANA:
Yeah, that's completely mega-bozo. According to my reading of RFC 2046,
you're allowed to treat unknown _subtypes_ as application/octet-stream
(well, it depends), but it is mum on what's supposed to happen if
you
Content-Type: file/pdf;
file is not a registered Media Type according to IANA:
Yeah, that's completely mega-bozo. According to my reading of RFC 2046,
you're allowed to treat unknown _subtypes_ as application/octet-stream
(well, it depends), but it is mum on what's supposed to
Probably. I was able to view the enclosed PDF.
I have a request out for the orginal msg--to figure out the mega-bozo MUA, FYA.
As a follow-up ...
Like I said, RFC 2045-2046 are mum about what to do with an unknown top-level
Content-Type (as far as I can tell). But the precessors to those RFCs
