From: mblaze-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Problems with special characters using mencrypt and mmime
Date: Thu, 05 Sep 2019 14:02:57 +0200 [thread overview]
Message-ID: <20190905120257.QKK1rOFXOCg08zddI8IXr9NNIcul32POwzImSvVtZEc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-167@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
Closed issue by guillaumecherel on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/167
Description:
I've noticed that when I encrypt a message that contains special characters like à , é, send it to myself, and decrypt it, the characters don't display well anymore. Digging a bit, I see that when calling mmime on a message that contains such characters, they become unreadable (example below). How can I read them properly? Am I misunderstanding how mmime works?
The ultimate question is how can I read special characters properly when decoding an email that was encoded with mencrypt?
For example, with the following content in the file "msgtest":
```
To: bla@bla.com
Cc:
Bcc:
Subject:
From: bla@bla.com
Message-Id: <1YHLB0BBH7E5S.3KT9KOOFC0R67@bla.fr>
User-Agent: mblaze/0.5.1-13-g1ed8a0a-dirty (2019-09-05)
accents: à é
```
The mmime command gives:
```
guillaume@guillaume-portable ~/tmp> mmime < msgtest
To: bla@bla.com
Cc:
Bcc:
Subject:
From: bla@bla.com
Message-Id: <1YHLB0BBH7E5S.3KT9KOOFC0R67@bla.fr>
User-Agent: mblaze/0.5.1-13-g1ed8a0a-dirty (2019-09-05)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_462810cc62ddba987fdf34f3_=_"
This is a multipart message in MIME format.
------_=_462810cc62ddba987fdf34f3_=_
Content-Type: text/plain; charset=UTF-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
accents: =C3=A0 =C3=A9
------_=_462810cc62ddba987fdf34f3_=_--
```
Thanks
prev parent reply other threads:[~2019-09-05 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 10:30 [ISSUE] " mblaze-github
2019-09-05 10:43 ` mblaze-github
2019-09-05 10:58 ` mblaze-github
2019-09-05 10:58 ` mblaze-github
2019-09-05 12:02 ` mblaze-github
2019-09-05 12:02 ` mblaze-github [this message]
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=20190905120257.QKK1rOFXOCg08zddI8IXr9NNIcul32POwzImSvVtZEc@z \
--to=mblaze-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).