content type: text/html -- but not mime

content type: text/html -- but not mime

[Alex Schroeder]

[-- Attachment #1: Type: text/plain, Size: 173 bytes --]

I cannot get Gnus to render as HTML the mails (usually spam) sent
without MIME headers.  When I edit the mail in Gnus, however, the mail
starts with the following magic:

  

[-- Attachment #2: Type: text/html, Size: 337 bytes --]

Re: content type: text/html -- but not mime

[Jinhyok Heo]

>>>>> "AS" == Alex Schroeder <alex@emacswiki.org> writes:

    AS> I cannot get Gnus to render as HTML the mails (usually spam) sent
    AS> without MIME headers.  When I edit the mail in Gnus, however, the mail
    AS> starts with the following magic:

    AS> [...]

Just try to hit "W h"(Washing html) on you Summary buffer. It'll try
to render any mail as html. It has been quite useful for me to read a
email without MIME headers.

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk

Re: content type: text/html -- but not mime

[Alex Schroeder]

Jinhyok Heo <novembre+dated+1037510504.19e28d@ournature.org> writes:

> Just try to hit "W h"(Washing html) on you Summary buffer. It'll try
> to render any mail as html. It has been quite useful for me to read a
> email without MIME headers.

Thanks, that was what I needed.

Alex.

Re: content type: text/html -- but not mime

[Matt Armstrong]

Alex Schroeder <alex@emacswiki.org> writes:

> Jinhyok Heo <novembre+dated+1037510504.19e28d@ournature.org> writes:
>
>> Just try to hit "W h"(Washing html) on you Summary buffer. It'll try
>> to render any mail as html. It has been quite useful for me to read a
>> email without MIME headers.
>
> Thanks, that was what I needed.

Procmail users can also do this to add a MIME-Version header whenever
there is a text/html content type without it.  Assuming MIME-Version
1.0 when there is a Content-Type: header is not the way the RFCs work,
but it is the way the world works.

:0fw
* ^Content-Type: text/html
* ! ^MIME-Version:
| formail -a 'MIME-Version: 1.0'