Re: No "Content-Type:"

[Michael Welsh Duggan <md5i@cs.cmu.edu>]

Shigeki Uno <shigeki@mediawars.ne.jp> writes:

> I asked you about *Content-Transfer-Encoding* topic the other day
> and No problems occured about Encoding MIME e-mails after that.
> (Thanks, Yamaoka-san.)
> 
> *But* I said that some e-mails causes *unintelligible sequence of
> characters* and these e-mails are encoded by Quoted-Printable.  I
> looked into them carefully today again and found that I made an
> error in reports. :-(
>   
> Following example is e-mail's headers which causes *unintelligible
> sequence of characters*(This is one of them).

[...]

> I found *Content-Type: text/plain; charaset="iso-2022-JP"* line
> doesn't exist. And others which cause *unintelligible sequence of
> characters* also doesn't have *Content-Type* line.
> 
> I can read it with _MEW_(Message in the Emacs World) without any
> problems but, on the other hand, certainly can't read it with
> (P)Gnus :-(.  SIGH.

I also have had problems with malformed messages before.  Often I can
fix them by using washing functions.  For example, if I received a
quoted-printable iso-2022-jp article with a missing Content-Type
header, I would run the following washing functions:

`W q'  <- This should take care of quoted-printable
`C-u W M c iso-2022-jp RET' <- This should take care of the encoding

-- 
Michael Duggan
(md5i@cs.cmu.edu)