From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: No Cc on wide reply
Date: Mon, 24 Jul 2000 12:46:16 -0400 [thread overview]
Message-ID: <00Jul24.124616edt.115274@gateway.intersys.com> (raw)
In-Reply-To: Simon Josefsson's message of "24 Jul 2000 11:22:23 +0200"
* Simon Josefsson <simon@josefsson.org> on Mon, 24 Jul 2000
| Reply-To is not used when I do "followup", but Mail-Copies-To is. (But
| I admit it's questionable if it should.)
Not questionble at all: you shouldn't.
You should be switching on the backend type, and only use Mail-Copies-To
when using a news backend. Admittedly mine is back-asswards, creating the
header by default and removing it for non-nntp backends:
(cond ((or (not (boundp 'gnus-select-method))
(not (equal (car gnus-select-method) 'nntp)))
(let* ((headers nil))
(setq headers (list "Mail-Copies-To"
"X-No-Archive"))
(message-narrow-to-headers)
(while headers
(message-remove-header (car headers))
(setq headers (cdr headers)))
)))
But that should give you an idea of what to switch on.
Or else posting styles could be used, probably.
| What would the mail headers look that achieve the same thing as my
| "Mail-Copies-To: never" in this mail look like?
Reply-To: [mailing-list-mailbox]
Which has its own plethora of problems, but there you have it.
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball may stick to certain types
Minion of Nathan - Nathan says Hi! \ of skin.
PGP Key: at a key server near you! \
next prev parent reply other threads:[~2000-07-24 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-22 4:11 Harry Putnam
2000-07-22 12:03 ` Kai Großjohann
2000-07-22 13:43 ` Harry Putnam
2000-07-22 14:02 ` Stainless Steel Rat
2000-07-23 9:43 ` Kai Großjohann
2000-07-23 15:17 ` Stainless Steel Rat
2000-07-24 9:22 ` Simon Josefsson
2000-07-24 16:46 ` Stainless Steel Rat [this message]
[not found] ` <vaf7la4ud2k.fsf@lucy.cs.uni-dortmund.de>
2000-07-30 14:30 ` Stainless Steel Rat
2000-07-24 15:05 ` Paul Jarc
2000-07-24 16:47 ` Stainless Steel Rat
2000-07-25 6:55 ` Kai Großjohann
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=00Jul24.124616edt.115274@gateway.intersys.com \
--to=ratinox@peorth.gweep.net \
/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).