Re: bad rfc2047 encoding

[Simon Josefsson]

Dave Love <d.love@dl.ac.uk> writes:

> However, clearly the result for the typical form of address used in
> the microshaft world is bogus:
>
> (with-temp-buffer
>   (insert "To: \"Großjohann, K (Kai)\" <Kai.Grossjohann@CS.Uni-Dortmund.DE>
> ")
>   (rfc2047-encode-message-header)
>   (buffer-string))
>   => "To: 
> \"=?iso-8859-1?q?Gro=DFjohann,_K_(Kai)\"_<Kai.Grossjohann@CS.Uni-Dort?=
>  =?iso-8859-1?q?mund.DE>?=
> "
>
> Sorry, I don't have time to grovel the RFCs.  Is one simply not
> allowed to use such addresses?  If so, Gnus should warn rather than
> completely mangling it.

I can't reproduce this, I get the output below which seems fine.

"To: \"=?iso-8859-1?q?Gro=DFjohann?=, K (Kai)\"
  <Kai.Grossjohann@CS.Uni-Dortmund.DE>
 "

This is with EMACS_21_1_RC.  The output you get seems invalid to me.

>> I agree.  (I'm reading the gnus bugs list from quimby.gnus.org, which
>> removes To/Cc so when I reply it only goes to the author and
>> bugs@gnus.org.)
>
> That seems unfortunate.  People reporting bugs will potentially miss
> discussion.

It appears I was wrong, quimby.gnus.org does not alter headers, at
least the last few messages CC bug-gnu-emacs properly, but the
original submission did not.