INTERNET-DRAFT Charles H. Lindsey
Usenet Format Working Group University of Manchester
July 2001
6.8. Mail-Copies-To
Previous Up Next
6.8. Mail-Copies-To
The Mail-Copies-To header indicates whether or not the poster wishes
to have followups to an article emailed in addition to being posted
to Netnews and, if so, establishes the address to which they should
be sent.
The content syntax makes use of syntax defined in [RFC 2822], but
subject to the revised definition of local-part given in section 5.2.
Mail-Copies-To-content = copy-addr / "nobody" / "poster"
copy-addr = mailbox
The keyword "nobody" indicates that the poster does not wish copies
of any followup postings to be emailed. This indication is widely
seen as a very strong wish, and is to be taken as the default when
this header is absent.
The keyword "poster" indicates that the poster wishes a copy of any
followup postings to be emailed to him.
Otherwise, this header contains a copy-addr to which the poster
wishes a copy of any followup postings to be sent.
NOTE: Some existing practice uses the keyword "never" in place
of "nobody" and "always" in place of "poster". These usages are
deprecated, but followup agents MAY observe them.
The automatic actions of a followup agent in the various cases
(subject to manual override by the user) are as follows:
nobody (or when the header is absent)
The followup agent SHOULD NOT, by default, email such a copy and
Ought, especially when there is an explicit "nobody", to issue a
warning and ask for confirmation if the user attempts to do so.
poster
The followup agent Ought, by default, to email a copy, which MUST
then be sent to the address in the Reply-To header, and in the
absence of that to the address(es) in the From header.
copy-addr
The followup agent Ought, by default, to email a copy, which MUST
then be sent to the copy-addr.
NOTE: This header is only relevant when posting followups to
Netnews articles, and is to be ignored when sending pure email
replies to the poster, which are handled as prescribed under the
Reply-To header (6.1). Whether or not this header will also
find similar usage for replies to messages sent to mailing lists
falls outside the scope of this standard.
When emailing a copy, the followup agent SHOULD also include a
"Posted-And-Mailed: yes" header (6.9).
NOTE: In addition to the Posted-And-Mailed header, some followup
agents also include within the body a mention that the article
is both posted and mailed, for the benefit of reading agents
that do not normally show that header.
Previous Up Next
Previous draft (04): 6.8. Mail-Copies-To
Diffs to previous draft
--- {draft-04} Wed Jul 11 21:55:34 2001
+++ {draft-05} Wed Jul 11 21:55:34 2001
@@ -4,22 +4,21 @@
to Netnews and, if so, establishes the address to which they should
be sent.
- The content syntax makes use of syntax defined in [MESSFOR], but
+ The content syntax makes use of syntax defined in [RFC 2822], but
subject to the revised definition of local-part given in section 5.2.
Mail-Copies-To-content = copy-addr / "nobody" / "poster"
copy-addr = mailbox
- The keyword "nobody" indicates that the author does not wish copies
+ The keyword "nobody" indicates that the poster does not wish copies
of any followup postings to be emailed. This indication is widely
seen as a very strong wish, and is to be taken as the default when
this header is absent.
-
- The keyword "poster" indicates that the author wishes a copy of any
+ The keyword "poster" indicates that the poster wishes a copy of any
followup postings to be emailed to him.
- Otherwise, this header contains a copy-addr to which the author
+ Otherwise, this header contains a copy-addr to which the poster
wishes a copy of any followup postings to be sent.
NOTE: Some existing practice uses the keyword "never" in place
@@ -45,7 +44,7 @@
NOTE: This header is only relevant when posting followups to
Netnews articles, and is to be ignored when sending pure email
- replies to the author, which are handled as prescribed under the
+ replies to the poster, which are handled as prescribed under the
Reply-To header (6.1). Whether or not this header will also
find similar usage for replies to messages sent to mailing lists
falls outside the scope of this standard.