From: NAGY Andras <nagya@inf.elte.hu>
Subject: Re: mail-{followup,copies}-to on this list
Date: 14 Feb 2001 23:48:10 +0100 [thread overview]
Message-ID: <dzcwvasankl.fsf@pandora.inf.elte.hu> (raw)
In-Reply-To: <vafhf1wyl6w.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> > If the header is not present the agent SHOULD NOT set the message
> > to be both posted and mailed.
> >
> > Please correct me if I interpret this wrong, or stop sending me
> > personal followups.
>
> This message is not posted, only mailed. So technically, this is
> okay.
In the context of a mailing list, `post' means mail to the list, and
`mail' means private mail, semantically, regardless the actual
technical transport.
> Also, following your interpretation would mean that the MCT/MFT
> proposal would change what happens to a message which does NOT contain
> these headers. But surely, in the interest of backward compatibility,
> the proposal for a new header should specify that the old behavior is
> used in case the header is not present.
I think most people except public responses (followups) to the mailing
list. This is also the case when they do not set a MCT/MFT header.
(Perhaps because they don't know about it.)
The common practice on all the mailing lists I know is to send
followups to the list by default. (This is also what broken list
servers suggest when adding an In-Reply-To header pointing to the
list.)
So, sending a private followup by default is not what most users
except, therefore this interpretation breaks backward compatibility.
> Is it so difficult for you to include the MCT/MFT headers?
Of course not (just looking for some mixture of posting styles and
group parameters).
Andras
next prev parent reply other threads:[~2001-02-14 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 20:44 NAGY Andras
2001-02-14 21:36 ` ShengHuo ZHU
2001-02-14 21:51 ` Paul Jarc
2001-02-14 22:05 ` Kai Großjohann
2001-02-14 22:48 ` NAGY Andras [this message]
2001-02-15 13:14 ` Per Abrahamsen
2001-02-15 13:56 ` NAGY Andras
2001-02-15 14:13 ` Per Abrahamsen
2001-02-15 18:37 ` Jake Colman
2001-02-15 19:03 ` Per Abrahamsen
2001-02-15 13:53 ` David S. Goldberg
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=dzcwvasankl.fsf@pandora.inf.elte.hu \
--to=nagya@inf.elte.hu \
/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).