From: "Bjørn Mork" <bmork@dod.no>
Subject: Re: Who sets Sender:?
Date: Wed, 22 May 2002 19:38:40 +0200 [thread overview]
Message-ID: <hvsn4khylb.fsf@rasputin.ws.nextra.no> (raw)
In-Reply-To: <02May22.125928edt.119302@gateway.intersystems.com>
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> * prj@po.cwru.edu (Paul Jarc) on Wed, 22 May 2002
> | You're answering this question: "in what cases should the MUA guess
> | whether Sender is needed?" That isn't the question I asked.
>
> I answered -that- question in one of my earliest posts: if the From field
> is not user@host.domain. That was right before I pointed out that this is
> a religious debate.
And the reason for this being a religious debate is such strong
beliefs for no apparent reason. There is nothing other than a
religiously confused mind that can make "originator", "author" or
"transmitter" become "user@host.domain".
If I were to state my beliefs, I would say that the intented meaning
of this section is that a Sender never should be added as long as the
_person_ writing the message and the _person_ entering the message
into the mail transport are the same:
If the originator of the message can be indicated
by a single mailbox and the author and transmitter are identical, the
"Sender:" field SHOULD NOT be used. Otherwise, both fields SHOULD
appear.
Which would make the current Gnus default a violation of RFC2822.
> [...]
> | Will that incorrectness ever cause problems?
>
> Potentially, yes. Received headers will tell you the route a message has
> taken, but it will not necessarilly tell you anything about the humans
> involved.
Which is a problem for whom/what?
> | A wrong guess in the other direction can cause problems. "Correct" isn't
> | always the best thing to be.
>
> A wrong guess in the other direction will not cause problems unless someone
> violates RFC 2822 and misuses Sender.
Which I hope everybody can agree is a real problem today. Buggy MUAs
use the Sender for replies, and buggy mailing list software refuse
messages unless the Sender is subscribed.
One can either be a religious fanatic, or try to adapt as much as
possible within the _actual_ RFC requirements.
Bjørn
--
I mean, most Nicaraguan people have computers .
next prev parent reply other threads:[~2002-05-22 17:38 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
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 [this message]
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=hvsn4khylb.fsf@rasputin.ws.nextra.no \
--to=bmork@dod.no \
/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).