On Wed, Dec 14, 2011 at 12:10:25PM +0200, Daniel Shahaf wrote: > Andreas' attachment declared itself as > Content-Type: text/x-patch; charset=us-ascii; name="german-fuzzy-0.diff" > but contained literal [ü»«] characters. > > Andreas, you should consider fixing that, so it's easier to process > your patches.
This could also be an interoperability problem between mutt and gmx. The charset is correct as far as the encoded base64 form is concerned. Should the charset= header apply to the encoded or the decoded form? Of course, always assuming ascii for the encoded form makes sense for base64. But what about other encodings? Not sure what RFCs say here.
