Content-Transfer-Encoding header incorrectly kept for piped messages

When piping a base64-encoded message with pipe_decode set, mutt correctly decodes the message, but keeps the "Content-Transfer-Encoding: base64" header. This confuses downstream software, such as git-am that complains it can't decode the message properly.