Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Cc: ding@gnus.org
Subject: Re: Who sets Sender:?
Date: Tue, 21 May 2002 11:27:27 -0400	[thread overview]
Message-ID: <m3r8k5ldvu.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <02May21.105936edt.119176@gateway.intersystems.com> (Stainless Steel Rat's message of "Tue, 21 May 2002 11:04:32 -0400")

Stainless Steel Rat <ratinox@peorth.gweep.net> wrote:
> * prj@po.cwru.edu (Paul Jarc)  on Tue, 21 May 2002
> | It might also help if you quoted the part of RFC 2822 that makes you
> | think this is relevant.
>
> Because a mailbox is not necessarilly used by the person who uses the
> account.  It could be the vacation program invoked by the user's .forward
> file.
>
> Because a mailbox is not necessarilly a single person.  A mailbox may be
> shared by several people.
>
> Because a mailbox may not be a person at all.  It could be a program like
> Mailman sending out its monthly reminders to list subscribers.

I don't see how any of this is relevant.  I also don't see any quotes
from RFC 2822.  Do you think there are any specific parts of RFC 2822
that support your position?

> If RFC 2822 is interpreted such that a single user has a single identity
> with many mailboxes, then you need to start making exceptions for special
> cases and conditionalizing others.

Such as?

> | That fact that you can be indicated by two distinct mailboxes doesn't
> | change the fact that you can also be indicated by a single mailbox.
>
> If that statement were true, then by strictest reading of RFC 2822, mail
> that I send as samurairat@spamcop.net from ratinox@ccs.neu.edu should never
> have a Sender header.

Right.

> This is wrong.

I don't see why.  Anyone who's interested in the route the message was
sent by can look at the Received fields.

> Sender -is- unimportant for mail.  My opinion is that Sender should
> never be generated automatically for mail.

Agreed.

> | > Also, be aware that the Sender header must never be used for anything but
> | > human consumption.
>
> | What does this mean, exactly?  If I want to reply to a message and
> | send the response to the Sender address, should my MUA stop me?  Or
> | just not provide any easy way to do this?  Or just not make it the
> | default reply address?
>
> It means exactly that.

Exactly *which*?  Those are mutually exclusive, or were meant to be.
Should my MUA stop me from sending a response to the Sender address?
If it does not stop me, should it provide no easy way to do this?  If
it provides an easy way to do this, should it merely not use Sender by
default?

> The default reply address is the From field.  The default reply address can
> be changed by the originator by setting a Reply-To header.  Your MUA is
> very broken if it uses the Sender address over From or Reply-To.

I don't think any of that is in dispute.


paul



  reply	other threads:[~2002-05-21 15:27 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 [this message]
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
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=m3r8k5ldvu.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    --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).