Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Gnus generates an invalid To header
Date: Mon, 26 Nov 2007 12:25:10 +0100	[thread overview]
Message-ID: <873autb65l.fsf@member.fsf.org> (raw)
In-Reply-To: <v9d4tzeqx4.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 24 Nov 2007 14:03:51 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

Hi Reiner,

>> 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?

With "the same header" you mean the complete bogus Reply-To header?  I
don't think that would be good, because then it would possibly be sent
to a local user.  And sending to a wrong recipient is much worse than
not sending at all.

Bye,
Tassilo



  reply	other threads:[~2007-11-26 11:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 11:47 Tassilo Horn
2007-11-24 13:03 ` Reiner Steib
2007-11-26 11:25   ` Tassilo Horn [this message]
2007-11-26 12:42     ` Elias Oltmanns
2007-11-28 21:42       ` Reiner Steib
2007-12-01 11:56       ` Avoid calling idna-to-ascii on ASCII domain names (was: Gnus generates an invalid To header) Reiner Steib

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=873autb65l.fsf@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).