Re: Gnus generates an invalid To header

[Reiner Steib <reinersteib+gmane@imap.cc>]

On Sat, Nov 24 2007, Tassilo Horn wrote:

> Reply-To: "kontakt@tieraerztliche-klinik.com" <Tierklinik Kaiserberg Duisburg>
> From: <kontakt@tieraerztliche-klinik.com>
>
> When I want to reply to it (R or r) Gnus generates the following To
> header:
>
> To: "kontakt@/usr/bin/idn: tld_check_4z: missing inputtieraerztliche-klinik.com" <Tierklinik Kaiserberg Duisburg>

This looks like the output of the IDNA program (/usr/bin/idn).  I
don't have IDNA installed, so I get (disabling it does the same [1]):

,----
| To: "kontakt@tieraerztliche-klinik.com" <Tierklinik Kaiserberg Duisburg>
`----

This is exactly the bogus Reply-To the sender requested.

By edebugging `message-idna-to-ascii-rhs-1', I found that it calls
(idna-to-ascii rhs) with `rhs' = "" because the right hand side of
"tierklinikkaiserbergduisburg" is the empty string.  Maybe message
should just return the same header instead if calling `idna-to-ascii'
if `rhs' is empty?

Throwing an error would not be correct, because "To: foo" is valid
(local user / domain added by the MTA).

> I'm not too familiar with the specs, but I guess it's not Gnus' but the
> senders' fault, e.g. it has to be
>
> Reply-To: "Tierklinik Kaiserberg Duisburg" <kontakt@tieraerztliche-klinik.com>

Yes.  "kontakt@tieraerztliche-klinik.com" is a comment.

Bye, Reiner.

[1]
,----[ M-x apropos-variable RET idna RET ]
| gnus-use-idna
|   Variable: Whether IDNA decoding of headers is used when viewing messages.
| message-use-idna
|   Variable: Whether to encode non-ASCII in domain names into ASCII according to IDNA.
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/