Github messages for mblaze
 help / color / Atom feed
From: mblaze-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Problems with special characters using mencrypt and mmime
Date: Thu, 05 Sep 2019 12:30:50 +0200
Message-ID: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-167@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]

New 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

             reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-05 10:30 mblaze-github [this message]
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 ` [ISSUE] [CLOSED] " mblaze-github

Reply instructions:

You may reply publically 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=gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-167@inbox.vuxu.org \
    --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

Github messages for mblaze

Archives are clonable: git clone --mirror http://inbox.vuxu.org/mblaze-github

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.github.mblaze


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git