Gnus development mailing list
 help / color / mirror / Atom feed
From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Who sets Sender:?
Date: Tue, 21 May 2002 15:46:16 -0400	[thread overview]
Message-ID: <02May21.154121edt.119281@gateway.intersystems.com> (raw)
In-Reply-To: <m3u1p1ibc4.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Tue, 21 May 2002 14:50:45 -0400")

* prj@po.cwru.edu (Paul Jarc)  on Tue, 21 May 2002
| > 2. RFC 2822 requires a Sender header be generated when the identities of
| >    the originator and sender differ.

| By "generated", do you mean automatically?  I would disagree with
| that.  Even if not, this is only a matter of SHOULD, not MUST, so I
| wouldn't say "required".

In some circumstances the Sender MUST appear, such as when the From field
contains more than one mailbox.  In others it says that the header SHOULD
appear.  It does not say who MUST or SHOULD generate the header.  It is
presumed that the MUA will do so if the user does not, just as the MUA
fills in the From header as necessary.

| > I choose to use a definition of "identity" that meets the criteria given by
| > both RFC 2822 and

| Which criteria are those, specifically?

That it identify the agent who hits the button that initiates the process
of connecting to the the MTA or news server and handing off the message,
and that an attempt has been made at getting the address correct if the
user has not done so himself.

[...]
| You give me the impression that that goal is worth more to you than
| using a reasonable reading of RFC 2822.  If you care about that goal,
| that's fine, but I don't see anything in RFC 2822 to back you; you can
| promote that sort of configuration without claiming that RFC 2822
| demands it.

Correct me if I am mistaken, but it seems to me that you read RFC 2822 as a
Gnus user.  You see a small problem with Gnus and you fix it.  There is
nothing wrong with that, but...

I read RFC 2822 as a systems administrator, and I have to make RFC 2822 --
the format of a mail message -- work with all of the other protocols
necesssary to get your message delivered.  Where you see a small problem, I
see a symptom of a greater problem, one that affects all users on a
network.  Your solution is to configure the client.  That is not a good
solution for systems administrators who may have to deal with hundreds or
thousands of users.  We want to fix the problem once and be done with it.
My solution is to configure the network and mail gateway to function
correctly for everyone who uses them.  What you see as my goal is the
solution to your problem.

-- 
Rat <ratinox@peorth.gweep.net>    \ Caution: Happy Fun Ball may suddenly
Minion of Nathan - Nathan says Hi! \ accelerate to dangerous speeds.
PGP Key: at a key server near you!  \ 
       That and five bucks will get you a small coffee at Starbucks.




  parent reply	other threads:[~2002-05-21 19:46 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-20 20:19 Norman Walsh
2002-05-20 21:24 ` Stainless Steel Rat
2002-05-21 13:43   ` Norman Walsh
2002-05-21 14:25     ` Stainless Steel Rat
2002-05-21 14:38       ` Paul Jarc
2002-05-24 22:55     ` Steinar Bang
2002-05-26 13:48     ` Barry Fishman
2002-05-26 14:33       ` Harry Putnam
2002-05-26 17:17         ` Barry Fishman
2002-05-20 22:12 ` Matt Armstrong
2002-05-21  1:58   ` Stainless Steel Rat
2002-05-21 14:14     ` Paul Jarc
2002-05-21 15:04       ` Stainless Steel Rat
2002-05-21 15:27         ` Paul Jarc
2002-05-21 16:27           ` Stainless Steel Rat
2002-05-21 16:56             ` Paul Jarc
2002-05-21 18:33               ` Stainless Steel Rat
2002-05-21 18:50                 ` Paul Jarc
2002-05-21 19:04                   ` Matt Armstrong
     [not found]                     ` <84g00lma45.fsf@rjk.greenend.org.uk>
2002-05-21 22:07                       ` Paul Jarc
2002-05-22 12:05                         ` Richard Kettlewell
2002-05-21 19:46                   ` Stainless Steel Rat [this message]
2002-05-21 20:13                     ` Paul Jarc
2002-05-21 21:16                       ` Stainless Steel Rat
2002-05-21 21:51                         ` Paul Jarc
2002-05-22  0:02                           ` Stainless Steel Rat
2002-05-22 15:23                             ` Paul Jarc
2002-05-22 15:54                               ` Stainless Steel Rat
2002-05-22 16:03                                 ` Paul Jarc
2002-05-22 17:04                                   ` Stainless Steel Rat
2002-05-22 17:25                                     ` Paul Jarc
2002-05-22 17:56                                       ` Stainless Steel Rat
2002-05-22 17:38                                     ` Bjørn Mork
2002-05-22 18:04                                       ` Stainless Steel Rat
2002-05-21 17:52     ` Matt Armstrong
2002-05-21 18:48       ` 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=02May21.154121edt.119281@gateway.intersystems.com \
    --to=ratinox@peorth.gweep.net \
    /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).