GNU bug report logs -
#1141
23.0.60; RMAIL: can't display base64 encoded message
Previous Next
Reported by: Xavier Maillard <xma <at> gnu.org>
Date: Sat, 11 Oct 2008 00:40:06 UTC
Severity: wishlist
Tags: moreinfo
Done: Xavier Maillard <xma <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Date: Sat, 11 Oct 2008 02:00:43 +0200
> From: Xavier Maillard <xma <at> gnu.org>
> Jabber-ID: xma01 <at> jabber.fr
> Cc:
>
> With latest emacs (CVS), several messages can't be displayed.
>
> Here is one the message I can't read directly:
>
> Date: Fri, 10 Oct 2008 13:29:09 +0200
> From: "CHARLIER Cyril" <ccharlier <at> lolica.org>
> To: "Xavier Maillard" <xma <at> gnu.org>
> Subject: Re: [lolica] Renouvelement loliwin.org ?
> Cc: lolica <at> lolica.org
> Content-Type: multipart/alternative;
> boundary="----=_Part_98966_28250470.1223638149537"
>
> ------=_Part_98966_28250470.1223638149537
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: base64
> Content-Disposition: inline
Thank you for your report.
This is not a bug, but a missing feature. Rmail never supported
multipart email messages. There's an effort to add this to Rmail in
the future, but for now, you will have to decode the base64-encoded
part manually, after typing `e' to make the message editable: mark the
encoded part, type "M-x base64-decode-region RET", then "C-c C-c", and
finally "M-x rmail-redecode-body RET utf-8 RET" to decode the text
into Emacs's internal character representation.
This bug report was last modified 15 years and 193 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.