From: Eli Zaretskii <eliz@gnu.org>
To: Xavier Maillard <xma@gnu.org>, 1141@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org, bug-gnu-emacs@gnu.org
Subject: bug#1141: 23.0.60; RMAIL: can't display base64 encoded message
Date: Sat, 11 Oct 2008 09:32:46 +0200 [thread overview]
Message-ID: <uej2nio2p.fsf@gnu.org> (raw)
In-Reply-To: <200810110000.m9B00h44001297@zogzog.maillard.mobi>
> Date: Sat, 11 Oct 2008 02:00:43 +0200
> From: Xavier Maillard <xma@gnu.org>
> Jabber-ID: xma01@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@lolica.org>
> To: "Xavier Maillard" <xma@gnu.org>
> Subject: Re: [lolica] Renouvelement loliwin.org ?
> Cc: lolica@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.
next prev parent reply other threads:[~2008-10-11 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 0:00 bug#1141: 23.0.60; RMAIL: can't display base64 encoded message Xavier Maillard
2008-10-11 7:32 ` Eli Zaretskii [this message]
2008-10-14 6:25 ` Xavier Maillard
2010-01-15 2:21 ` Glenn Morris
2010-01-15 23:03 ` Xavier Maillard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uej2nio2p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=1141@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=xma@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.