Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Who sets Sender:?
Date: Wed, 22 May 2002 12:03:50 -0400	[thread overview]
Message-ID: <m3wutw88zn.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <02May22.114919edt.119312@gateway.intersystems.com> (Stainless Steel Rat's message of "Wed, 22 May 2002 11:54:12 -0400")

Stainless Steel Rat <ratinox@peorth.gweep.net> wrote:
> * prj@po.cwru.edu (Paul Jarc)  on Wed, 22 May 2002
> | >> In what cases should the MUA guess that Sender is needed?
...
> The MUA should attempt to deterine if a Sender header is needed for
> every message sent.

You're answering this question: "in what cases should the MUA guess
whether Sender is needed?"  That isn't the question I asked.

> | You didn't answer these questions, nor many others from previous
> | messages.
>
> Because the answers are obvious to anyone who bothers to think about them
> for more than half a second.

It isn't obvious to me what *your* answers are, or I wouldn't have
asked them.

> Failure to generate a Sender header when one is required results in
> a technically incorrect message.

Will that incorrectness ever cause problems?  A wrong guess in the
other direction can cause problems.  "Correct" isn't always the best
thing to be.

> When is a Sender header required?  When RFC 2822 says it is.
...
> When should Gnus not create a Sender header?  When one already
> exists or RFC 2822 says no.

Punting to RFC 2822 is pointless when the interpretation of RFC 2822
is itself in question.


paul



  reply	other threads:[~2002-05-22 16:03 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
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 [this message]
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=m3wutw88zn.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).