<<< Date Index >>>     <<< Thread Index >>>

Re: Bug#222191: patch-1.4.1.tt.compat.1 for mutt fixes this bug



On Sun, Feb 01, 2004 at 07:17:06PM +0100,
 Thomas Roessler wrote:

> Even though I don't really like the assumed_charset feature, I'm
> somewhat tempted to adding it to mutt; I'd welcome comments on that.

I need this function as long as old mailers and broken mailers exist.

> Generating RFC2047-encoded MIME parameters with mutt is, however, a
> standards violation that is *not* going to make it into the code.
> RFC2231 is the standard for this.  Mutt implements that standard.

I agree with you. What you say is very right.
But it is also clear that there are those who need this function
because there are mailers which cannot parse RFC2231 parameters.
I want you to take that into consideration.
In addition, mutt generates both an RFC2231 parameter and an RFC2047 
parameter when $create_rfc2047_parameters is set. 
And, standard mailers disregard the RFC2047 parameter and parse the 
RFC2231 parameter. Practically, I think that any problem does not arise.

-- 
TAKIZAWA Takashi
http://www.emaillab.org/mutt/