Charles Lindsey wrote:
Yes, I am coming round to the view that, in the few cases where a gateway
cannot determine the proper way to encode some header in RFC 2047, it
would be better to stick an "X-" in front of that header and then encode
it as unstructured. That gives the user the best chance of working out
what was originally intended, and little harm will ensue since it cannot
have been a header that was essential for the basic News or Email
protocols.
That still doesn't address backward compatibility, because that's not
what existing gateways do.