Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Reply in mailing lists
Date: 16 Dec 1999 12:46:30 +1100	[thread overview]
Message-ID: <t4i902virnt.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Per Abrahamsen's message of "Tue, 14 Dec 1999 09:47:04 +0100"

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

    Per> Brian May <bmay@csse.monash.edu.au> writes:
    >> I think the To field will prevent the news message from being
    >> posted (unless I am mistaken).

    Per> You are mistaken.

I am...? I will take your word for it ;-)

I assume then that if Gnus sees a "newsgroup" header, it will always
post it?

Similarly, if Gnus sees a "To", "Cc", or "Bcc" header, it
will always post it (independently of if it mails it or not).

    >> IMHO, "mail-copies-to" should override the setting for
    >> "to-address", but would it?

    Per> Try it.

Amazing, it worked! Assuming my test wasn't flawed... (I don't
think it was).

So now I can summarize for mailing lists (and I assume the same holds
for all newsgroups) that have the "to-address" set:

narrow reply
- reply only to author - this is obvious

wide reply
- reply to everyone specified in original message (this may/may not
include the mailing list).
- except if original mail contains "mail-copies-to: never"[1],
in which case the original author will not get a separate copy.
Not sure about other people.

followup
- same thing as "wide reply" for mailing lists where "to-address"
is not set. Otherwise...

- reply to "to-address" only.
- except if "mail-copies-to: always" was set, in which case a CC
is sent to the author.
- if you want to manually force replying to the original author,
then pushing C-c C-t (did I get that correct?) will add him/her
to the "to" field.


So, me thinks it is a pity that the wide reply wont always include
the address of the mailing list, but everything else seems
rather sane and straight forward.


Note:

[1] I can't remember if this is never or nobody. Please substitute for
correct value, and don't take my version as being up-to-date and
correct.

-- 
Brian May <bmay@csse.monash.edu.au>



  reply	other threads:[~1999-12-16  1:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-10 13:52 Jochen Lillich
1999-12-10 13:58 ` Per Abrahamsen
1999-12-13  0:37   ` Brian May
1999-12-13  9:02     ` Per Abrahamsen
1999-12-13 23:31       ` Brian May
1999-12-14  8:47         ` Per Abrahamsen
1999-12-16  1:46           ` Brian May [this message]
1999-12-21 20:18     ` Kai Großjohann
1999-12-22  6:33       ` Brian May
1999-12-22  8:43         ` Steinar Bang
1999-12-14 10:08   ` Jochen Lillich
1999-12-10 14:08 ` Shaun Lipscombe

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=t4i902virnt.fsf@silas-2.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).