Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: "(ding)" <ding@gnus.org>
Subject: Re: Disable generation of "Sender: " by default.
Date: 17 Dec 2000 13:29:50 +0100	[thread overview]
Message-ID: <vaflmtfjkn5.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3n1dx4v58.fsf@peorth.gweep.net>

On 15 Dec 2000, Stainless Steel Rat wrote:

> News is different.  For news, the Sender header is generated when
> your From address does not match your local posting address.  RFC
> 1036 assumes that if you are posting from a particular host then you
> can receive mail at that host.  The assumption is invalid, but it is
> in the standard.

Hm.  The only difference I can find between the description in RFC 822
and the one in 1036:

* 1036 says that the Sender header should be verified by software at
  the submitting host.  822 says nothing about verification by
  software.

* 1036 talks about the `entity' submitting the message into the
  network, 822 talks about the `agent (person, system or process)'.

Gack.  I still feel that the intent of the Sender header is the same
in RFC 822 and 1036, but it's only a feeling.

I don't know what Son-of-1036 says, and there is another document for
this, I think, which I also don't know.  I wish that Usenet was better
standardized.  As it is, we have to play by ear which is not good.

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)



  reply	other threads:[~2000-12-17 12:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12 21:09 ms outlook replyers Nick Papadonis
2000-12-12 22:12 ` Kai Großjohann
2000-12-12 22:25   ` Stainless Steel Rat
2000-12-13  6:41   ` Justin Sheehy
2000-12-13  8:36   ` Disable generation of "Sender: " by default Per Abrahamsen
2000-12-13 14:05     ` Jesper Harder
2000-12-14 14:18       ` Per Abrahamsen
2000-12-14 17:58         ` Jesper Harder
2000-12-15 12:35           ` Per Abrahamsen
2000-12-15 13:19             ` Harry Putnam
2000-12-15 15:47               ` Alan Shutko
2000-12-15 14:27             ` Stainless Steel Rat
2000-12-17 12:29               ` Kai Großjohann [this message]
2000-12-17 16:31                 ` Stainless Steel Rat
2000-12-17 19:33                   ` Kai Großjohann
2000-12-17 22:57                   ` Russ Allbery
2000-12-18 11:16                     ` Per Abrahamsen
2000-12-18 23:44                       ` Russ Allbery
2000-12-20 10:48                   ` Toby Speight
2000-12-20 20:05                     ` Stainless Steel Rat
2000-12-14  8:05   ` ms outlook replyers Dirk Gomez
2000-12-14 13:33     ` Kai Großjohann
2000-12-14 15:03       ` Alan Shutko
2000-12-14 20:19         ` Nick Papadonis
2000-12-14 21:24           ` Kai Großjohann
2000-12-14 21:57             ` Stainless Steel Rat
2000-12-15  5:48             ` Nick Papadonis
2000-12-15  9:34               ` Kai Großjohann
2000-12-15 22:36                 ` Nick Papadonis
2000-12-15 22:57                   ` Kai Großjohann
2000-12-15 14:54           ` Paul Jarc
2000-12-13  2:11 ` Colin Walters
2000-12-13  5:07   ` Nick Papadonis
2000-12-13  4:47     ` Colin Walters
2000-12-13  8:49     ` Kai Großjohann
2000-12-13  5:24   ` Stainless Steel Rat
2000-12-13  6:16     ` Colin Walters
2000-12-13 16:06       ` 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=vaflmtfjkn5.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).