diff options
| author | Leszek Cimała <ernierasta@zori.cz> | 2019-12-06 15:28:34 +0100 |
|---|---|---|
| committer | Drew DeVault <sir@cmpwn.com> | 2019-12-07 14:30:20 -0500 |
| commit | 30aa77c1c975e7fa25e202add14971d4077cc9e1 (patch) | |
| tree | b607c00361f967f76f884a2835f96ec9f3c2c244 /commands/next-tab.go | |
| parent | 0a1a75aed17e56c32cb0283e1b9f1978bd52fd7f (diff) | |
use correct headers for message part
Hello guys,
on the hunt for bugs related to wrong encoding. This patch is fixing
reply to non-utf8 messages.
We were using global message headers instead of part specific. In
practice header were often something like:
multipart; boundry=...
where there should be:
text/plain; charset=...
Fixed also missing SubType.
Have great weekend!
Leszek
Diffstat (limited to 'commands/next-tab.go')
0 files changed, 0 insertions, 0 deletions