Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Cc: ding@gnus.org
Subject: Re: Disable generation of "Sender: " by default.
Date: 15 Dec 2000 05:19:07 -0800	[thread overview]
Message-ID: <m2d7etesac.fsf@gnus-5.8.8-cvs.now.playing> (raw)
In-Reply-To: Per Abrahamsen's message of "15 Dec 2000 13:35:30 +0100"

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Jesper Harder <harder@ifa.au.dk> writes:
> 
> > Or maybe disable it only for mail, which won't break anything.
> 
> Yep.  But as far as I can see, I don't get a "Sender: " in my mail,
> and I don't understand why.  'message-syntax-checks' is nil, and I'm
> posting from another machine than my mail address.  So I do not dare
> touch the code.

There have been long and bitter discussions about the `sender' line
here and on gnu.emacs.gnus  going back a year or two,  back then it
was generally presented as a `bad' thing to disable generation of
sender.

Respected posters advocated against hotly.  But apparently things have
changed in the way mail is processed since then and the sender line
doesn't play the same role it once did.

Not so long ago someone advocating: 
(setq message-syntax-checks '((sender . disabled))), openly would 
have been called to task...

What has changed for this attitude to have relaxed or disappeared?



  reply	other threads:[~2000-12-15 13:19 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 [this message]
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
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=m2d7etesac.fsf@gnus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.com \
    --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).