From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Default mail address
Date: 22 Jun 1997 19:18:20 +0200 [thread overview]
Message-ID: <kighgeqpndv.fsf@jagor.srce.hr> (raw)
In-Reply-To: Stainless Steel Rat's message of "22 Jun 1997 11:32:26 -0400"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> >>>>> "PA" == Per Abrahamsen <abraham@dina.kvl.dk> writes:
>
> PA> For News, Son-of-RFC 1036 compliance:
> [...]
> PA> Gnus should not create Sender for mail.
>
> Pardon me, Per, but what the hoek have you been smoking? Using
> Son-of-RFC 1036 as an argument for mail handling is absurd.
According to SoR1036, `Sender' *should* be generated. According to
RFC822, `Sender' should *not* be generated in the context in which
Gnus does it. From that Per correctly infers that Gnus should not
`Sender' create `Sender' for mail.
What is wrong with that?
Or, have I (or Per) misunderstood the relevant part of RFC822?
Admittedly, RFC1036 is much clearer on that point.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
"Silence!" cries Freydag. "I did not call thee in for a consultation!"
"They are my innards! I will not have them misread by a poseur!"
next prev parent reply other threads:[~1997-06-22 17:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-20 17:50 Ben Gertzfield
1997-06-20 19:19 ` Default mail address (duh, solved) Ben Gertzfield
1997-06-20 19:53 ` Default mail address Justin Sheehy
1997-06-20 23:39 ` Alan Shutko
1997-06-21 1:38 ` Justin Sheehy
1997-06-21 13:48 ` Johan Danielsson
1997-06-21 14:40 ` Per Abrahamsen
1997-06-21 14:52 ` Johan Danielsson
[not found] ` <wkafkislf9.fsf@peorth.gweep.net>
1997-06-22 17:18 ` Hrvoje Niksic [this message]
[not found] ` <wkiuz5wdrl.fsf@peorth.gweep.net>
1997-06-23 18:10 ` Johan Danielsson
1997-06-23 12:44 ` Per Abrahamsen
1997-06-21 2:00 ` Hrvoje Niksic
1997-06-21 9:01 ` Russ Allbery
1997-06-25 4:52 ` Roderick Schertler
1997-06-26 18:58 ` Steven L Baur
1997-06-23 9:40 ` Robert Bihlmeyer
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=kighgeqpndv.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).