How does mutt decode and display base64 parts of a message?
My xterm running mutt, and also ThunderBird, shows garbage like this:
...
#
# Regards,
# NormanN?????r??y隊Z)z{.????ۚ?맲??r??z?^?ˬz??N?(?֜??^?
ޭ隊Z)z{.????ۚ??0???????Ǩ
#
...
The input looks like this:
# Content-Transfer-Encoding: base64
# Content-Type: text/plain; charset="utf-8"
# X-MIME-Notice: attachments may have been removed from this message
# MIME-Version: 1.0
#
# SGVsbG8sDQoNCmkgbm90aWNlZCBpbiBTTEVTIDEyLjEgdGhhdCB4bCBkb2VzIG5vdCBoYXZlIGEg
# 4oCeeGwgbmV34oCcIGNvbW1hbmQgYW55IG1vcmUuIEkgd2FzIGhlYXZpbHkgdXNpbmcg4oCeeG0g
# bmV34oCcIHdpdGggcGxhaW4gdGV4dCBjb25maWdzLg0K4oCedmlyc2ggZGVmaW5l4oCcIG9ubHkg
# d29ya3Mgd2l0aCB4bWwgZmlsZXMuDQoNCklzIHRoZXJlIGFueSB3YXkgdG8gYWRkIGEgZG9tYWlu
# IGFuZCBub3Qgc3RhcnQgaXQgZnJvbSBhIHBsYWluIHRleHQgY29uZmlnPw0KDQpSZWdhcmRzLA0K
# Tm9ybWFu
# --
# To unsubscribe, e-mail: opensuse-virtual+unsubscr...@opensuse.org
I wonder why both TB and mutt fail to display properly. I think similar
failures happen in the gmail webUI.
Looks like something forgets to properly truncate a buffer.
Olaf
