Re: Another problem with rfc2047 encoding

[thomas_mail@daphne.gnuu.de (Thomas Hühn)]

Also sprach Lars Magne Ingebrigtsen <larsi@gnus.org>:

>> From: Ralf =?ISO-8859-1?Q?D=F6blitz?= <=?iso-8859-1?q?d=F6blitz?=@doeblitz.net>
>
> [...]
>
>> Message-ID: <b7k9a0$he6$3@msgids.netzverwaltung.net>
>>
>> ...the localpart seems to be interpreted, though it shouldn't.
>
> But that's not a Gnus message, is it?

Yes, what I mean is: If I want to reply, Gnus tries to send a mail to
<döblitz@doeblitz.net>.

OK, you could see it as the user's problem, but a warning would be nice.
And perhaps just don't "decode" the localpart. That way the user has a
chance that the "undecoded" localpart exists at the receiving mail
server. At least he sees that there is something strange going on. If
you're used to umlaute you don't catch them at first glance in the mail
address.

BTW, Ralf seems to interpret the RfC that way, that mail should be sent
to <=?iso-8859-1?q?d=F6blitz?=@doeblitz.net>, literally. I'm no expert
in terms of the RfC, so I'm not sure, whether that "must not" really
means, that no such string of characters may appear in the localpart, or
whether it means, that this string must not be interpreted as an encoded
word, thus being legal.

Thomas