-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tuesday, December 2 at 10:38 AM, quoth Shaochun Wang:
> 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,
Nope. According to the man page: "mutt will unconditionally use the
encoding specified in RFC2231" ... for *sending*. I.e. mutt can *read*
incorrect messages, but cannot *send* incorrect messages.
> including gmail.
Yikes!
> So my question is that is there some way to let mutt sent RFC 2047
> encoding attachment?
Not at the moment. You may want to make the request to mutt-dev
~Kyle
- --
Most truths are so naked that people feel sorry for them and cover
them up, at least a little bit.
-- Edward R. Murrow
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkk0oakACgkQBkIOoMqOI17/JwCfSkFROD+nC8mzAEN8jz8qWXN/
fAEAoPUFnGJ6GzTh2QjxlPNogEZFv3MA
=mDU/
-----END PGP SIGNATURE-----
