Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
Subject: Re: Disable generation of "Sender: " by default.
Date: 17 Dec 2000 14:57:37 -0800	[thread overview]
Message-ID: <yllmtewt9a.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Stainless Steel Rat's message of "17 Dec 2000 11:31:11 -0500"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> RFC 1036: Sender exists as a crude authentication mechanism.  Sender is
> the authenticated (by software) local mailbox of the originator of the
> message when that mailbox differs from the one in the originator header.
> Ie, if I am on, say, skuld.gweep.net w/ login 'ratinox' and I post a
> news article with 'grumble@bogus.com' as my From header, then some
> program somewhere must generate 'Sender: ratinox@skuld.gweep.net'.

> They are not even vaguely close to each other.  My opinion is that RFC
> 1036's Sender is badly broken, because it utterly fails to accomplish
> its goal.  RFC 822's Sender does exactly what it is intended to do, no
> more, no less.

I'm fairly sure USEFOR drops the entire broken idea of a Sender header,
thankfully.

LISTSERV still responds to the Sender header rather than the From header,
checks the Sender header to see if you can post to a list, and if you try
to subscribe to a mailing list, subscribes the content of your Sender
header instead of your From address.  That's why I turned off Sender in my
Gnus settings; it's easier to do that than it is to try to argue with Eric
Thomas that his software is doing something really stupid.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  parent reply	other threads:[~2000-12-17 22:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-12 21:09 ms outlook replyers Nick Papadonis
2000-12-12 22:12 ` Kai Großjohann
2000-12-12 22:25   ` Stainless Steel Rat
2000-12-13  6:41   ` Justin Sheehy
2000-12-13  8:36   ` Disable generation of "Sender: " by default Per Abrahamsen
2000-12-13 14:05     ` Jesper Harder
2000-12-14 14:18       ` Per Abrahamsen
2000-12-14 17:58         ` Jesper Harder
2000-12-15 12:35           ` Per Abrahamsen
2000-12-15 13:19             ` Harry Putnam
2000-12-15 15:47               ` Alan Shutko
2000-12-15 14:27             ` Stainless Steel Rat
2000-12-17 12:29               ` Kai Großjohann
2000-12-17 16:31                 ` Stainless Steel Rat
2000-12-17 19:33                   ` Kai Großjohann
2000-12-17 22:57                   ` Russ Allbery [this message]
2000-12-18 11:16                     ` Per Abrahamsen
2000-12-18 23:44                       ` Russ Allbery
2000-12-20 10:48                   ` Toby Speight
2000-12-20 20:05                     ` Stainless Steel Rat
2000-12-14  8:05   ` ms outlook replyers Dirk Gomez
2000-12-14 13:33     ` Kai Großjohann
2000-12-14 15:03       ` Alan Shutko
2000-12-14 20:19         ` Nick Papadonis
2000-12-14 21:24           ` Kai Großjohann
2000-12-14 21:57             ` Stainless Steel Rat
2000-12-15  5:48             ` Nick Papadonis
2000-12-15  9:34               ` Kai Großjohann
2000-12-15 22:36                 ` Nick Papadonis
2000-12-15 22:57                   ` Kai Großjohann
2000-12-15 14:54           ` Paul Jarc
2000-12-13  2:11 ` Colin Walters
2000-12-13  5:07   ` Nick Papadonis
2000-12-13  4:47     ` Colin Walters
2000-12-13  8:49     ` Kai Großjohann
2000-12-13  5:24   ` Stainless Steel Rat
2000-12-13  6:16     ` Colin Walters
2000-12-13 16:06       ` 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=yllmtewt9a.fsf@windlord.stanford.edu \
    --to=rra@stanford.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).