Re: improve rmail's MIME handling

[Kenichi Handa <handa@m17n.org>]

In article <83r5e874ab.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> > Now the default value of rmail-enable-mime is t, and thus a MIME
> > message is properly decoded in RMAIL buffer automatically.

> Why is this a good idea, especially on the Emacs 23 branch, in the
> middle of a pretest?

I interpreted Stefan and Yidong's "go ahead" as so.

> Previously, Rmail would never do anything with
> attachments without my say-so, and thus was one of the safest MUAs on
> Earth.  Why change that now?

Rmail still does nothing non-safe thing with attachments.  It
just shows you something like this line (with proper buttons):

Attached image/jpeg file: temp.jpg (281kB) Display

instead of showing something like this raw base64 data:

Content-Type: image/jpeg
Content-Disposition: attachment; filename=temp.jpg
Content-Transfer-Encoding: base64

/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAMCAgMCAgMDAwMEAwMEBQgFBQQEBQoHBwYIDAoMDAsK
CwsNDhIQDQ4RDgsLEBYQERMUFRUVDA8XGBYUGBIUFRT/wAALCAO3AqgBAREA/8QAHwAAAQUBAQEB
AQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1Fh
....

And, a text content is of course decoded properly, but it
had been decoded anyway.  The difference is that, with the
new code, text contents in multipart (and encoded-words in
headers) are also decoded correctly.

> Of course, if other Rmail users think we should make it t by default,
> I can always customize it back, so if I'm the only one who cares,
> let's leave it at t.

I vote for `t', but of course I follow the opinion of the
majority.

---
Kenichi Handa
handa@m17n.org