vm team mailing list archive
-
vm team
-
Mailing list archive
-
Message #00747
[Bug 490018] Re: vm: sends garbled non-ASCII in default setup
*** This bug is a duplicate of bug 430521 ***
https://bugs.launchpad.net/bugs/430521
VM 7.19 is just too old. Please use the latest version of VM available
on your system. Is it Debian? We really recommend the 8.1.x releases.
You can download them from the vm front page here on launchpad.
Cheers,
Uday Reddy
(VM development team)
--
vm: sends garbled non-ASCII in default setup
https://bugs.launchpad.net/bugs/490018
You received this bug notification because you are a member of VM
development team, which is the registrant for VM (defunct) (via bug
430521).
Status in VM (View Mail) for Emacs: New
Status in “vm” package in Debian: Confirmed
Bug description:
Hi,
[Please retain a CC to 508552-forwarded@xxxxxxxxxxxxxxx in order
for the Debian bug tracking system to retain a record of your
contribution]
This was reported by a Debian user.
In VM's default setup messages containing non-ASCII characters
are sent as "Content-Type: text/plain; charset=iso-2022-jp". They look
garbled in every MUA (Gnus, VM, Rmail, Icedove) I've tried. If an
iso-2022 encoding is used at all, at least "Content-Type: text/plain;
charset=iso-2022-7bit" should be used, which would make the messages
readable in Emacs-based MUAs.
Note that this applies to messages sent in VM under emacs22,
with emacs-snapshot the situation is even worse: all non-ASCII
characters silently disappear when the message is sent!
This can be worked around by setting
vm-mime-8bit-composition-charset to "utf-8" which makes VM send
messages as "Content-Type: text/plain; charset=utf-8", although the
docstring for vm-mime-8bit-composition-charset wrongly claims that this
variable has no effect.
manoj
References