Bug#878378: muttprint: ugly output in multipart/alternative with text/html and with "Subject: =?utf-8?Q?..."; not suitable for modern email

2017-10-15 Thread Rene Engelhard
On Sun, Oct 15, 2017 at 06:13:09PM +0200, Joost van Baal-Ilić wrote: > Indeed, you are right (and I was wrong). muttprint properly deals with both > > "Subject: =?utf-8?Q?blah blah?=" and rightfully skips html alternatives in > > multipart/alternative messages. mutt or the mailer does. >

Bug#878378: muttprint: ugly output in multipart/alternative with text/html and with "Subject: =?utf-8?Q?..."; not suitable for modern email

2017-10-15 Thread Joost van Baal-Ilić
Hi Rene, Thanks for your prompt feedback! Op Fri, Oct 13, 2017 at 03:51:10PM +0200 schreef Rene Engelhard: > On Fri, Oct 13, 2017 at 11:30:08AM +0200, Joost van Baal-Ilić wrote: > > I feel these days, muttprint is getting a bit stale. It is not suitable > > Yeah, true. > > > to use with modern

Bug#878378: muttprint: ugly output in multipart/alternative with text/html and with "Subject: =?utf-8?Q?..."; not suitable for modern email

2017-10-13 Thread Rene Engelhard
On Fri, Oct 13, 2017 at 11:30:08AM +0200, Joost van Baal-Ilić wrote: > I feel these days, muttprint is getting a bit stale. It is not suitable Yeah, true. > to use with modern email: But this is not an argument. What is "modern email"? Bogusly formatted mail? Broken E-Mail from not proper encod

Bug#878378: muttprint: ugly output in multipart/alternative with text/html and with "Subject: =?utf-8?Q?..."; not suitable for modern email

2017-10-13 Thread Joost van Baal-Ilić
Package: muttprint Version: 0.73-7 Severity: normal Dear Rene Engelhard, First of all, thanks for taking care of muttprint in Debian for over 15 years! I saved a raw multipart/alternative (both text/plain and text/html) email message in /tmp/mail.msg; ran muttprint -p - -f - mail.ps and ran e