Github messages for mblaze
 help / Atom feed
* [ISSUE] Problems with special characters using mencrypt and mmime
@ 2019-09-05 10:30 mblaze-github
  2019-09-05 10:43 ` mblaze-github
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 10:30 UTC (permalink / raw)
  To: ml

[-- 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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problems with special characters using mencrypt and mmime
  2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime mblaze-github
@ 2019-09-05 10:43 ` mblaze-github
  2019-09-05 10:58 ` mblaze-github
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 10:43 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/167#issuecomment-528306728

Comment:
The mail client should decode it, the rfc for mails only allows ascii.

```
$ echo "\n\naccents: à é" | mmime | mshow /dev/stdin

--- 1: multipart/mixed size=259 ---
--- --- 2: text/plain size=16 ---

accents: à é
```

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problems with special characters using mencrypt and mmime
  2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime mblaze-github
  2019-09-05 10:43 ` mblaze-github
@ 2019-09-05 10:58 ` mblaze-github
  2019-09-05 10:58 ` mblaze-github
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 10:58 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/167#issuecomment-528311095

Comment:
When the mail is encrypted and you want to use `mshow` to read it you need to add the `mpgp` filter to `~/.mblaze/filter`: `multipart/encrypted: mgpg`.

```
$ mshow /tmp/test.gpg
From: mail@duncano.de

--- 1: multipart/encrypted size=2086 filter="mgpg" ---
--- --- 2: multipart/mixed size=720 ---
--- --- --- 3: text/plain size=15 ---
accents: à é
```

I think all other clients will work this way, decrypt the message and then decode the mime parts again.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problems with special characters using mencrypt and mmime
  2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime 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 ` [ISSUE] [CLOSED] " mblaze-github
  2019-09-05 12:02 ` mblaze-github
  4 siblings, 0 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 10:58 UTC (permalink / raw)
  To: ml

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

New comment by Duncaen on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/167#issuecomment-528311095

Comment:
When the mail is encrypted and you want to use `mshow` to read it you need to add the `mgpg` filter to `~/.mblaze/filter`: `multipart/encrypted: mgpg`.

```
$ mshow /tmp/test.gpg
From: mail@duncano.de

--- 1: multipart/encrypted size=2086 filter="mgpg" ---
--- --- 2: multipart/mixed size=720 ---
--- --- --- 3: text/plain size=15 ---
accents: à é
```

I think all other clients will work this way, decrypt the message and then decode the mime parts again.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [ISSUE] [CLOSED] Problems with special characters using mencrypt and mmime
  2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime mblaze-github
                   ` (2 preceding siblings ...)
  2019-09-05 10:58 ` mblaze-github
@ 2019-09-05 12:02 ` " mblaze-github
  2019-09-05 12:02 ` mblaze-github
  4 siblings, 0 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 12:02 UTC (permalink / raw)
  To: ml

[-- 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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Problems with special characters using mencrypt and mmime
  2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime mblaze-github
                   ` (3 preceding siblings ...)
  2019-09-05 12:02 ` [ISSUE] [CLOSED] " mblaze-github
@ 2019-09-05 12:02 ` mblaze-github
  4 siblings, 0 replies; 6+ messages in thread
From: mblaze-github @ 2019-09-05 12:02 UTC (permalink / raw)
  To: ml

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

New comment by guillaumecherel on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/167#issuecomment-528331008

Comment:
Great, thanks for the explanation!

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, back to index

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-05 10:30 [ISSUE] Problems with special characters using mencrypt and mmime 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 ` [ISSUE] [CLOSED] " mblaze-github
2019-09-05 12:02 ` mblaze-github

Github messages for mblaze

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

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


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