Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Gnus generates an invalid To header
Date: Wed, 28 Nov 2007 22:42:59 +0100	[thread overview]
Message-ID: <v9fxyqkpwc.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87prxxw534.fsf@denkblock.local>

On Mon, Nov 26 2007, Elias Oltmanns wrote:

> Tassilo Horn <tassilo@member.fsf.org> wrote:
>> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>>> 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?  

In the end, yes.  (More specifically, I meant
`message-idna-to-ascii-rhs-1'.)

>> 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.
[...]
> Your concern is legitimate, but it is a feature request rather than
> a bug fix.  After all, the sender is ultimately responsible for
> setting a valid Reply-To header and, by failing to do so, positively
> asks for trouble.

ACK

> That said, it might still be worthwhile to implement the feature you are
> asking for.  I recollect two incidents where I tried to reply to emails
> only to find out that the Reply-To header was bogus.  However, there
> seem to be too many ways to screw the Reply-To header in a way that
> results in a syntactically correct but effectively bogus header.  If a
> user decides to use fully qualified email addresses only (after all,
> there is bbdb and auto completion), gnus can generally warn before
> shipping off messages to addresses without a domain part.  This is about
> all I can think of right now to tacle this issue and its probably not a
> good default setting.

I agree.  Such a feature could be provides via
`message-syntax-checks'.  But it should be disabled by default, I
think.  Hm, probably it is already there: See
`message-bogus-recipient-p', `message-bogus-address-regexp', ...

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2007-11-28 21:42 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
2007-11-26 12:42     ` Elias Oltmanns
2007-11-28 21:42       ` Reiner Steib [this message]
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=v9fxyqkpwc.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).