From: Steven L Baur <steve@miranova.com>
Subject: Re: Checking `Reply-To'
Date: 22 Feb 1997 21:06:43 -0800 [thread overview]
Message-ID: <m2rai8861o.fsf@altair.xemacs.org> (raw)
In-Reply-To: Stainless Steel Rat's message of 22 Feb 1997 21:57:04 -0500
Stainless Steel Rat writes:
>>>>>> "Hrv" == Hrvoje Niksic <hniksic@srce.hr> writes:
Hrv> Regardless of GNKSA, I think Gnus should perform the same checks for
Hrv> `Reply-To' as it does for `From'. What do you think?
I felt the GNKSA/U review of RadicalNews was mean-spirited and the
reviewer had an axe to grind, but that's besides the point.
> I think this is a violation of RFC822, actually. It depends on just what
> kinds of checking Gnus performs. A common use of Reply-To (and one of the
> intents of RFC822) is to specify a gatewayed mailbox that will work when
> the conventional "user@domain" format will fail. Such addresses have
> potentially infinite chance to fail the tests for an Internet "user@domain"
> address because most are completely different, and many are technically
> illlegal.
Yup. Consider example A.2.4 from RFC822:
A.2.4. Committee activity, with one author
George is a member of a committee. He wishes to have any
replies to his message go to all committee members.
From: George Jones <Jones@Host.Net>
Sender: Jones@Host
Reply-To: The Committee: Jones@Host.Net,
Smith@Other.Org,
Doe@Somewhere-Else;
Note that if George had not included himself in the
August 13, 1982 - 37 - RFC #822
Standard for ARPA Internet Text Messages
enumeration of The Committee, he would not have gotten an
implicit reply; the presence of the "Reply-to" field SUPER-
SEDES the sending of a reply to the person named in the "From"
field.
Example A.2.6 has another example containing an address that would
otherwise be considered invalid.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be billed at $250/message.
next prev parent reply other threads:[~1997-02-23 5:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-22 2:47 Hrvoje Niksic
1997-02-23 2:57 ` Stainless Steel Rat
1997-02-23 5:06 ` Steven L Baur [this message]
1997-02-28 23:34 ` Lars Magne Ingebrigtsen
1997-03-01 6:11 ` Hrvoje Niksic
1997-03-09 15:38 ` Nathan O. Siemers
1997-03-09 17:01 ` Lars Magne Ingebrigtsen
1997-03-09 22:59 ` Stainless Steel Rat
1997-03-10 5:21 ` Lars Magne Ingebrigtsen
1997-03-10 23:38 ` Stainless Steel Rat
1997-03-11 2:35 ` François Pinard
1997-03-11 14:35 ` Per Abrahamsen
1997-03-11 17:01 ` Stainless Steel Rat
1997-03-11 17:45 ` Per Abrahamsen
1997-03-11 22:39 ` Stainless Steel Rat
1997-03-12 1:05 ` Sudish Joseph
1997-03-12 17:47 ` Stainless Steel Rat
1997-03-12 19:56 ` Sudish Joseph
1997-03-11 18:46 ` Sten Drescher
1997-03-11 22:53 ` Stainless Steel Rat
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=m2rai8861o.fsf@altair.xemacs.org \
--to=steve@miranova.com \
/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).