#205 RFC 2047 munged on send

[Bill Wohler]

If you receive a message with RFC 2047 encodings
(message attached) and reply, the RFC 2047 encoding
appears in the To and Comments header fields, rather
than the decoded characters. For example:

| To: asjo@koldfront.dk (Adam
=?iso-8859-1?Q?Sj=F8gren?=)

When this message is sent, the encoding is wrapped
within another RFC 2047 encoding, as follows:

| To: asjo@koldfront.dk (Adam
=?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FSj=3DF8gre?=
| =?us-ascii?Q?n=3F=3D?=)

I think there are two components to this problem.

1. Let's add a feature request to nmh/GNU mailutils so
that you see the decoded character in your reply and
the RFC 2047 encoding happens automatically in either
send or post. This is the user-friendly way to solve
this problem.

2. Because a user *can* perform RFC 2047 encodings in
his message, and we see that repl inserts them in the
header, mml-to-mime must be fixed to recognize RFC 2047
encodings that are already present and leave them
alone, rather than wrapping them in another RFC 2047
encoding as it does now.

[Bill Wohler]

Message with RFC 2047 encoding

[Mike Kupfer]

See also #486