owner 307819 m...@debian.org thanks Assigning the bug to the package maintainer, I suspect that there is a decision to be made.
Quick summary so it can be taken faster: 1) Klaus is reporting that mutt doesn't honor the body charset while sending a mail signed inline with pgp/gnupg, infact there is code in pgp.c to check if the send_charset is different from us-ascii, in that case it will be set to utf-8. This code is still there (checked the latest testing version 1.5.18-4). 2) mutt was not doing this before version 1.5.6, the user is proposing a patch to fix this, other people are maintaining a separate fork of 'japanese mutt' which includes a similar patch: http://www.emaillab.org/mutt/download159.html 3) the submitter claims that the upstream refused the change, the original bug (267015) was reported to both the upstream (mutt-dev@) and the maintainer of the 'similar' patch, unfortunately there was no responde (see bug correspondence). The real question is, do the maintainer(s) want(s) to support a behavior which the upstream doesn't support? Please note that this bug seems to impact only a particular set of mail reader, 'decent mailreaders' should be able to handle the different content-lenght (see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267015#35 for details) So the bug is reproducible against the latest version, it was forwarded upstream and the change was refused, does the current package maintainer want to maintain this patch? Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
