As pointed by Kun Niu <[EMAIL PROTECTED]>, I finally get that one working. Although the patch is provided for mutt-1.5.10, it also works for mutt-1.5.16. See http://learn.tsinghua.edu.cn:8080/2002315162/muttpatched.html
That webpage is written in Chinese. So I summarize it in the following: First you need download a patch for mutt, which is at http://www.emaillab.org/mutt/download1510.html. Then apply the patch. Finally you can set whether or not to send RFC 2047 encoded mail by setting the parameter "create_rfc2047_parameters" to yes or no. I also set some send-hook for convience: send-hook "\.ac\.cn" "set create_rfc2047_parameters=yes" send-hook "\.gmail\.com" "set create_rfc2047_parameters=yes" You can set your own hook like these. On Tue, Dec 02, 2008 at 10:38:50AM +0800, Shaochun Wang wrote: > Hi all: > > > I know RFC 2047 encoding MIME is explicitly prohibited by the > standard. But unfortunately, a lot of my correspondents use the email > client which only decoded RFC 2047 encoded attachment, not RFC 2231, > including gmail. > > So my question is that is there some way to let mutt sent RFC 2047 > encoding attachment? > -- Shaochun Wang <[EMAIL PROTECTED]> Jabber: [EMAIL PROTECTED]
