Gnus development mailing list
 help / color / mirror / Atom feed
From: Sten Drescher <stend@grendel.texas.net>
Subject: Re: (gnus-inews-domain-name); insertion of Sender:
Date: 19 Jan 1996 12:05:36 -0600	[thread overview]
Message-ID: <5568e82h73.fsf@galil.austnsc.tandem.com> (raw)
In-Reply-To: Per Abrahamsen's message of Fri, 19 Jan 1996 15:22:06 +0100

Per Abrahamsen <abraham@dina.kvl.dk> said:

>>>>>> "PP" == Per Persson <pp@pfawww.pp.se> writes:
PP> So using a half-hearted/intelligent authentication method which
PP> might return bogus values is better then letting the user make sure
PP> that the value returned is correct? Thanks for clearing things out
PP> for me.

PA> A value provided by the user is per definition wrong for the Sender:
PA> field.  The Sender: field is not expected to reflect the users mail
PA> address.  That would have been really stupid, as we already have the
PA> From: field for that.

	Incorrect.  It _must_ reflect the users mail address if it is
present:

rfc822> 4.1.  SYNTAX

[...]

rfc822> authentic   =   "From"       ":"   mailbox  ; Single author
rfc822>             / ( "Sender"     ":"   mailbox  ; Actual submittor
rfc822>                 "From"       ":" 1#mailbox) ; Multiple authors
rfc822>                                             ;  or not sender

[...]

rfc822> 4.4.2.  SENDER / RESENT-SENDER

rfc822> This field contains the authenticated identity of the AGENT
rfc822> (person, system or process) that sends the message.  It is
rfc822> intended for use when the sender is not the author of the mes-
rfc822> sage, or to indicate who among a group of authors actually sent
rfc822> the message.  If the contents of the "Sender" field would be
rfc822> completely redundant with the "From" field, then the "Sender"
rfc822> field need not be present and its use is discouraged (though
rfc822> still legal).  In particular, the "Sender" field MUST be present
rfc822> if it is NOT the same as the "From" Field.

-- 
#include <disclaimer.h>				/* Sten Drescher */
1973 Steelers    About Three Bricks Shy of a Load    1994 Steelers
1974 Steelers         And the Load Filled Up         1995 Steelers?
To get my PGP public key, send me email with your public key and
	Subject: PGP key exchange
Key fingerprint =  90 5F 1D FD A6 7C 84 5E  A9 D3 90 16 B2 44 C4 F3
Unsolicited email advertisements will be proofread for a US$100/page fee.


  reply	other threads:[~1996-01-19 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-18 11:49 Per Persson
1996-01-18 13:37 ` Per Abrahamsen
1996-01-18 15:36   ` Per Persson
1996-01-19  8:34     ` Per Abrahamsen
1996-01-19 10:14       ` Per Persson
1996-01-19 10:14         ` Per Abrahamsen
1996-01-19 13:29           ` Per Persson
1996-01-19 14:22             ` Per Abrahamsen
1996-01-19 18:05               ` Sten Drescher [this message]
1996-01-19 20:38                 ` Per Abrahamsen
1996-01-19 22:37                   ` Sten Drescher
1996-01-20  1:46                     ` Stainless Steel Rat
1996-01-20 11:08                       ` Sudish Joseph
1996-01-19 22:55                   ` Sten Drescher
1996-01-19 23:53                     ` Per Abrahamsen
1996-01-20  2:30                       ` Sten Drescher
1996-01-20  5:24                   ` Lars Magne Ingebrigtsen

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=5568e82h73.fsf@galil.austnsc.tandem.com \
    --to=stend@grendel.texas.net \
    --cc=dreschs@austnsc.tandem.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).