Commit ee2916c6 authored by Paul Eggert's avatar Paul Eggert

Use “Cc” for email copies, as per RFC 5322.

Also fix similar problems with Bcc, Fcc, In-Reply-To,
and similar email headers.  See thread starting at:
https://lists.gnu.org/r/emacs-devel/2018-05/msg00463.html
parent a32412b8
...@@ -8,7 +8,7 @@ This is 95% of all you will ever need to know. ...@@ -8,7 +8,7 @@ This is 95% of all you will ever need to know.
** How do I report a bug? ** How do I report a bug?
Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org. Use M-x report-emacs-bug, or send mail to bug-gnu-emacs@gnu.org.
If you want to Cc someone, use an "X-Debbugs-CC" header (or If you want to Cc someone, use an "X-Debbugs-Cc" header (or
pseudo-header, see below) instead. pseudo-header, see below) instead.
** How do I comment on a bug? ** How do I comment on a bug?
...@@ -53,7 +53,7 @@ i) Your report will be assigned a number and generate an automatic reply. ...@@ -53,7 +53,7 @@ i) Your report will be assigned a number and generate an automatic reply.
ii) Optionally, you can set some database parameters when you first ii) Optionally, you can set some database parameters when you first
report a bug (see "Setting bug parameters" below). report a bug (see "Setting bug parameters" below).
iii) If you want to CC: someone, use X-Debbugs-CC: (note this only iii) If you want to Cc someone, use X-Debbugs-Cc: (note this only
applies to _new_ reports, not followups). applies to _new_ reports, not followups).
Once your report is filed and assigned a number, it is sent out to the Once your report is filed and assigned a number, it is sent out to the
...@@ -64,8 +64,8 @@ quiet@debbugs.gnu.org. ...@@ -64,8 +64,8 @@ quiet@debbugs.gnu.org.
** How do I reply to an existing bug report? ** How do I reply to an existing bug report?
Reply to 123@debbugs.gnu.org, replacing 123 with the number Reply to 123@debbugs.gnu.org, replacing 123 with the number
of the bug you are interested in. NB this only sends mail to the of the bug you are interested in. NB this only sends mail to the
bug-list, it does NOT send a CC to the original bug submitter. bug-list, it does NOT send a Cc to the original bug submitter.
So you need to explicitly CC him/her (and anyone else you like). So you need to explicitly Cc him/her (and anyone else you like).
(This works the same way as all the Emacs mailing lists. We generally (This works the same way as all the Emacs mailing lists. We generally
don't assume anyone who posts to a list is subscribed to it, so we don't assume anyone who posts to a list is subscribed to it, so we
cc everyone on replies.) cc everyone on replies.)
...@@ -95,23 +95,23 @@ normal bug reporting.) ...@@ -95,23 +95,23 @@ normal bug reporting.)
** When reporting a new bug, to send a Cc to another address ** When reporting a new bug, to send a Cc to another address
(e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header. (e.g. bug-cc-mode@gnu.org), do NOT just use a Cc: header.
Instead, use "X-Debbugs-CC:". This ensures the Cc address(es) will get a Instead, use "X-Debbugs-Cc:". This ensures the Cc address(es) will get a
mail with the bug report number in. If you do not do this, each reply mail with the bug report number in. If you do not do this, each reply
in the subsequent discussion might end up creating a new bug. in the subsequent discussion might end up creating a new bug.
This is annoying. (So annoying that a form of message-id tracking has This is annoying. (So annoying that a form of message-id tracking has
been implemented to hopefully stop this happening, but it is still been implemented to hopefully stop this happening, but it is still
better to use X-Debbugs-CC.) better to use X-Debbugs-Cc.)
If you want to send copies to more than one address, add them If you want to send copies to more than one address, add them
comma-separated in only one X-Debbugs-CC line. comma-separated in only one X-Debbugs-Cc line.
Like any X-Debbugs- header, this one can also be specified in the Like any X-Debbugs- header, this one can also be specified in the
pseudo-header (see below), if your mail client does not let you add pseudo-header (see below), if your mail client does not let you add
"X-" headers. "X-" headers.
If a new report contains X-Debbugs-CC in the input, this is If a new report contains X-Debbugs-Cc in the input, this is
converted to a real Cc header in the output. (See Bug#1780,5384) converted to a real Cc header in the output. (See Bug#1780,5384)
It is also merged into the Resent-CC header (see below). It is also merged into the Resent-Cc header (see below).
** How does Debbugs send out mails? ** How does Debbugs send out mails?
...@@ -120,15 +120,15 @@ header is unchanged. In new reports only (at present), the To: ...@@ -120,15 +120,15 @@ header is unchanged. In new reports only (at present), the To:
address is altered as follows. Any "bug-gnu-emacs", address is altered as follows. Any "bug-gnu-emacs",
"emacs-pretest-bug", or "submit@debbugs" address is replaced by "emacs-pretest-bug", or "submit@debbugs" address is replaced by
123@debbugs in the mail that gets sent out. (This also applies to any 123@debbugs in the mail that gets sent out. (This also applies to any
Cc: header, though you should be using X-Debbugs-CC instead in new Cc: header, though you should be using X-Debbugs-Cc instead in new
reports). The original header is stored as X-Debbugs-Original-To, if reports). The original header is stored as X-Debbugs-Original-To, if
it was changed. Any X-Debbugs-CC is merged into the Cc. it was changed. Any X-Debbugs-Cc is merged into the Cc.
Mails arriving at the bug list have the following Resent-* headers: Mails arriving at the bug list have the following Resent-* headers:
Resent-From: person who submitted the bug Resent-From: person who submitted the bug
Resent-To: owner@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org
Resent-CC: maintainer email address, plus any X-Debbugs-CC: entries Resent-Cc: maintainer email address, plus any X-Debbugs-Cc: entries
The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases. The "maintainer email address" is "bug-gnu-emacs@gnu.org" in most cases.
...@@ -239,7 +239,7 @@ The control server ignores anything after the last line above. So you ...@@ -239,7 +239,7 @@ The control server ignores anything after the last line above. So you
can place control commands at the beginning of a reply to a bug can place control commands at the beginning of a reply to a bug
report, and Bcc: the control server (note the commands have no effect report, and Bcc: the control server (note the commands have no effect
if you just send them to the bug-report number). Bcc: is better than Cc: if you just send them to the bug-report number). Bcc: is better than Cc:
in case people use Reply-to-All in response. in case people use Reply-To-All in response.
Some useful control commands: Some useful control commands:
......
...@@ -4398,7 +4398,7 @@ ...@@ -4398,7 +4398,7 @@
mail-header-separator. mail-header-separator.
(Mail Headers): Put info about initialization and changing in one place (Mail Headers): Put info about initialization and changing in one place
at the start. Update FCC section for mbox Rmail. Clarify From at the start. Update FCC section for mbox Rmail. Clarify From
section, mention mail-setup-with-from. Clarify Reply-to section. section, mention mail-setup-with-from. Clarify Reply-To section.
Add Mail-followup-to and mail-mailing-lists. Clarify References Add Mail-followup-to and mail-mailing-lists. Clarify References
section. section.
(Mail Aliases): Update example, make less contentious. (Mail Aliases): Update example, make less contentious.
......
...@@ -753,24 +753,24 @@ Try sending a bounced message a second time (@code{rmail-retry-failure}). ...@@ -753,24 +753,24 @@ Try sending a bounced message a second time (@code{rmail-retry-failure}).
to the message you are reading. To do this, type @kbd{r} to the message you are reading. To do this, type @kbd{r}
(@code{rmail-reply}). This displays a mail composition buffer in (@code{rmail-reply}). This displays a mail composition buffer in
another window, much like @kbd{C-x 4 m}, but preinitializes the another window, much like @kbd{C-x 4 m}, but preinitializes the
@samp{Subject}, @samp{To}, @samp{CC}, @samp{In-reply-to} and @samp{Subject}, @samp{To}, @samp{Cc}, @samp{In-Reply-To} and
@samp{References} header fields based on the message you are replying @samp{References} header fields based on the message you are replying
to. The @samp{To} field starts out as the address of the person who to. The @samp{To} field starts out as the address of the person who
sent the message you received, and the @samp{CC} field starts out with sent the message you received, and the @samp{Cc} field starts out with
all the other recipients of that message. all the other recipients of that message.
@vindex mail-dont-reply-to-names @vindex mail-dont-reply-to-names
You can exclude certain recipients from being included automatically You can exclude certain recipients from being included automatically
in replies, using the variable @code{mail-dont-reply-to-names}. Its in replies, using the variable @code{mail-dont-reply-to-names}. Its
value should be a regular expression; any recipients that match are value should be a regular expression; any recipients that match are
excluded from the @samp{CC} field. They are also excluded from the excluded from the @samp{Cc} field. They are also excluded from the
@samp{To} field, unless this would leave the field empty. If this @samp{To} field, unless this would leave the field empty. If this
variable is @code{nil}, then the first time you compose a reply it is variable is @code{nil}, then the first time you compose a reply it is
initialized to a default value that matches your own address. initialized to a default value that matches your own address.
To reply only to the sender of the original message, enter To reply only to the sender of the original message, enter
the reply command with a numeric argument: @kbd{C-u r} or @kbd{1 r}. the reply command with a numeric argument: @kbd{C-u r} or @kbd{1 r}.
This omits the @samp{CC} field completely for a particular reply. This omits the @samp{Cc} field completely for a particular reply.
Once the mail composition buffer has been initialized, editing and Once the mail composition buffer has been initialized, editing and
sending the mail goes as usual (@pxref{Sending Mail}). You can edit sending the mail goes as usual (@pxref{Sending Mail}). You can edit
...@@ -939,8 +939,8 @@ commas. ...@@ -939,8 +939,8 @@ commas.
@kbd{C-M-r @var{rcpts} @key{RET}} (@code{rmail-summary-by-recipients}) @kbd{C-M-r @var{rcpts} @key{RET}} (@code{rmail-summary-by-recipients})
makes a partial summary mentioning only the messages that have one or makes a partial summary mentioning only the messages that have one or
more recipients matching the regular expression @var{rcpts}. This is matched more recipients matching the regular expression @var{rcpts}. This is matched
against the @samp{To}, @samp{From}, and @samp{CC} headers (supply a prefix against the @samp{To}, @samp{From}, and @samp{Cc} headers (supply a prefix
argument to exclude the @samp{CC} header). argument to exclude the @samp{Cc} header).
@kindex C-M-t @r{(Rmail)} @kindex C-M-t @r{(Rmail)}
@findex rmail-summary-by-topic @findex rmail-summary-by-topic
......
...@@ -170,14 +170,14 @@ writes in Babyl format. If an Rmail buffer is visiting the file, ...@@ -170,14 +170,14 @@ writes in Babyl format. If an Rmail buffer is visiting the file,
Emacs updates it accordingly. To specify more than one file, use Emacs updates it accordingly. To specify more than one file, use
several @samp{Fcc} fields, with one file name in each field. several @samp{Fcc} fields, with one file name in each field.
@item Reply-to @item Reply-To
An address to which replies should be sent, instead of @samp{From}. An address to which replies should be sent, instead of @samp{From}.
This is used if, for some reason, your @samp{From} address cannot This is used if, for some reason, your @samp{From} address cannot
receive replies. receive replies.
@item Mail-reply-to @item Mail-Reply-To
This field takes precedence over @samp{Reply-to}. It is used because This field takes precedence over @samp{Reply-To}. It is used because
some mailing lists set the @samp{Reply-to} field for their own some mailing lists set the @samp{Reply-To} field for their own
purposes (a somewhat controversial practice). purposes (a somewhat controversial practice).
@item Mail-Followup-To @item Mail-Followup-To
...@@ -186,14 +186,14 @@ messages. This is typically used when you reply to a message from a ...@@ -186,14 +186,14 @@ messages. This is typically used when you reply to a message from a
mailing list that you are subscribed to, and want replies to go to the mailing list that you are subscribed to, and want replies to go to the
list without sending an extra copy to you. list without sending an extra copy to you.
@item In-reply-to @item In-Reply-To
An identifier for the message you are replying to. Most mail readers An identifier for the message you are replying to. Most mail readers
use this information to group related messages together. Normally, use this information to group related messages together. Normally,
this header is filled in automatically when you reply to a message in this header is filled in automatically when you reply to a message in
any mail program built into Emacs. any mail program built into Emacs.
@item References @item References
Identifiers for previous related messages. Like @samp{In-reply-to}, Identifiers for previous related messages. Like @samp{In-Reply-To},
this is normally filled in automatically for you. this is normally filled in automatically for you.
@end table @end table
...@@ -220,12 +220,12 @@ To: foo@@example.net, this@@example.net, ...@@ -220,12 +220,12 @@ To: foo@@example.net, this@@example.net,
You can direct Emacs to insert certain default headers into the mail You can direct Emacs to insert certain default headers into the mail
buffer by setting the variable @code{mail-default-headers} to a buffer by setting the variable @code{mail-default-headers} to a
string. Then @kbd{C-x m} inserts this string into the message string. Then @kbd{C-x m} inserts this string into the message
headers. For example, here is how to add a @samp{Reply-to} and headers. For example, here is how to add a @samp{Reply-To} and
@samp{Fcc} header to each message: @samp{Fcc} header to each message:
@smallexample @smallexample
(setq mail-default-headers (setq mail-default-headers
"Reply-to: foo@@example.com\nFcc: ~/Mail/sent") "Reply-To: foo@@example.com\nFcc: ~/Mail/sent")
@end smallexample @end smallexample
@noindent @noindent
...@@ -293,7 +293,7 @@ alias definitions and include commands. ...@@ -293,7 +293,7 @@ alias definitions and include commands.
Mail aliases expand as abbrevs---that is to say, as soon as you type Mail aliases expand as abbrevs---that is to say, as soon as you type
a word-separator character after an alias (@pxref{Abbrevs}). This a word-separator character after an alias (@pxref{Abbrevs}). This
expansion takes place only within the @samp{To}, @samp{From}, expansion takes place only within the @samp{To}, @samp{From},
@samp{Cc}, @samp{Bcc}, and @samp{Reply-to} header fields (plus their @samp{Cc}, @samp{Bcc}, and @samp{Reply-To} header fields (plus their
@samp{Resent-} variants); it does not take place in other header @samp{Resent-} variants); it does not take place in other header
fields, such as @samp{Subject}. fields, such as @samp{Subject}.
...@@ -422,7 +422,7 @@ Move to the @samp{Cc} header (@code{message-goto-cc}). ...@@ -422,7 +422,7 @@ Move to the @samp{Cc} header (@code{message-goto-cc}).
@item C-c C-f C-b @item C-c C-f C-b
Move to the @samp{Bcc} header (@code{message-goto-bcc}). Move to the @samp{Bcc} header (@code{message-goto-bcc}).
@item C-c C-f C-r @item C-c C-f C-r
Move to the @samp{Reply-to} header (@code{message-goto-reply-to}). Move to the @samp{Reply-To} header (@code{message-goto-reply-to}).
@item C-c C-f C-f @item C-c C-f C-f
Move to the @samp{Mail-Followup-To} header field Move to the @samp{Mail-Followup-To} header field
(@code{message-goto-followup-to}). (@code{message-goto-followup-to}).
......
...@@ -4463,11 +4463,11 @@ appropriate regexp. ...@@ -4463,11 +4463,11 @@ appropriate regexp.
@cindex Automatic filing of outgoing mail @cindex Automatic filing of outgoing mail
@cindex Mail, saving outgoing automatically @cindex Mail, saving outgoing automatically
You can either mail yourself a copy by including a @samp{BCC} header in the You can either mail yourself a copy by including a @samp{Bcc} header in the
mail message, or store a copy of the message directly to a file by mail message, or store a copy of the message directly to a file by
including an @samp{FCC} header. including an @samp{Fcc} header.
If you use standard mail, you can automatically create a @samp{BCC} to If you use standard mail, you can automatically create a @samp{Bcc} to
yourself by putting yourself by putting
@lisp @lisp
...@@ -4475,7 +4475,7 @@ yourself by putting ...@@ -4475,7 +4475,7 @@ yourself by putting
@end lisp @end lisp
@noindent @noindent
in your @file{.emacs} file. You can automatically include an @samp{FCC} in your @file{.emacs} file. You can automatically include an @samp{Fcc}
field by putting something like the following in your @file{.emacs} field by putting something like the following in your @file{.emacs}
file: file:
...@@ -4485,7 +4485,7 @@ file: ...@@ -4485,7 +4485,7 @@ file:
The output file will be in Unix mail format. The output file will be in Unix mail format.
If you use @code{mh-e}, add an @samp{FCC} or @samp{BCC} field to your If you use @code{mh-e}, add an @samp{Fcc} or @samp{Bcc} field to your
components file. components file.
It does not work to put @samp{set record filename} in the @file{.mailrc} It does not work to put @samp{set record filename} in the @file{.mailrc}
...@@ -4562,8 +4562,8 @@ these systems, you should configure @code{movemail} to use @code{flock}. ...@@ -4562,8 +4562,8 @@ these systems, you should configure @code{movemail} to use @code{flock}.
@c isaacson@@seas.upenn.edu @c isaacson@@seas.upenn.edu
Ron Isaacson says: When you hit Ron Isaacson says: When you hit
@kbd{r} to reply in Rmail, by default it CCs all of the original @kbd{r} to reply in Rmail, by default it Ccs all of the original
recipients (everyone on the original @samp{To} and @samp{CC} recipients (everyone on the original @samp{To} and @samp{Cc}
lists). With a prefix argument (i.e., typing @kbd{C-u} before @kbd{r}), lists). With a prefix argument (i.e., typing @kbd{C-u} before @kbd{r}),
it replies only to the sender. However, going through the whole it replies only to the sender. However, going through the whole
@kbd{C-u} business every time you want to reply is a pain. This is the @kbd{C-u} business every time you want to reply is a pain. This is the
......
...@@ -708,7 +708,7 @@ RFC822 date when the part was read (@code{Content-Disposition}). ...@@ -708,7 +708,7 @@ RFC822 date when the part was read (@code{Content-Disposition}).
@item recipients @item recipients
Who to encrypt/sign the part to. This field is used to override any Who to encrypt/sign the part to. This field is used to override any
auto-detection based on the To/CC headers. auto-detection based on the To/Cc headers.
@item sender @item sender
Identity used to sign the part. This field is used to override the Identity used to sign the part. This field is used to override the
......
...@@ -1161,13 +1161,13 @@ from using them): ...@@ -1161,13 +1161,13 @@ from using them):
@example @example
(setq nnmail-split-methods (setq nnmail-split-methods
'(("duplicates" "^Gnus-Warning:.*duplicate") '(("duplicates" "^Gnus-Warning:.*duplicate")
("XEmacs-NT" "^\\(To:\\|CC:\\).*localpart@@xemacs.invalid.*") ("XEmacs-NT" "^\\(To:\\|Cc:\\).*localpart@@xemacs.invalid.*")
("Gnus-Tut" "^\\(To:\\|CC:\\).*localpart@@socha.invalid.*") ("Gnus-Tut" "^\\(To:\\|Cc:\\).*localpart@@socha.invalid.*")
("tcsh" "^\\(To:\\|CC:\\).*localpart@@mx.gw.invalid.*") ("tcsh" "^\\(To:\\|Cc:\\).*localpart@@mx.gw.invalid.*")
("BAfH" "^\\(To:\\|CC:\\).*localpart@@.*uni-muenchen.invalid.*") ("BAfH" "^\\(To:\\|Cc:\\).*localpart@@.*uni-muenchen.invalid.*")
("Hamster-src" "^\\(CC:\\|To:\\).*hamster-sourcen@@yahoogroups.\\(de\\|com\\).*") ("Hamster-src" "^\\(Cc:\\|To:\\).*hamster-sourcen@@yahoogroups.\\(de\\|com\\).*")
("Tagesschau" "^From: tagesschau <localpart@@www.tagesschau.invalid>$") ("Tagesschau" "^From: tagesschau <localpart@@www.tagesschau.invalid>$")
("Replies" "^\\(CC:\\|To:\\).*localpart@@Frank-Schmitt.invalid.*") ("Replies" "^\\(Cc:\\|To:\\).*localpart@@Frank-Schmitt.invalid.*")
("EK" "^From:.*\\(localpart@@privateprovider.invalid\\|localpart@@workplace.invalid\\).*") ("EK" "^From:.*\\(localpart@@privateprovider.invalid\\|localpart@@workplace.invalid\\).*")
("Spam" "^Content-Type:.*\\(ks_c_5601-1987\\|EUC-KR\\|big5\\|iso-2022-jp\\).*") ("Spam" "^Content-Type:.*\\(ks_c_5601-1987\\|EUC-KR\\|big5\\|iso-2022-jp\\).*")
("Spam" "^Subject:.*\\(This really work\\|XINGA\\|ADV:\\|XXX\\|adult\\|sex\\).*") ("Spam" "^Subject:.*\\(This really work\\|XINGA\\|ADV:\\|XXX\\|adult\\|sex\\).*")
...@@ -1177,10 +1177,10 @@ from using them): ...@@ -1177,10 +1177,10 @@ from using them):
("Spam" "^From:.*\\(verizon\.net\\|prontomail\.com\\|money\\|ConsumerDirect\\).*") ("Spam" "^From:.*\\(verizon\.net\\|prontomail\.com\\|money\\|ConsumerDirect\\).*")
("Spam" "^Delivered-To: GMX delivery to spamtrap@@gmx.invalid$") ("Spam" "^Delivered-To: GMX delivery to spamtrap@@gmx.invalid$")
("Spam" "^Received: from link2buy.com") ("Spam" "^Received: from link2buy.com")
("Spam" "^CC: .*azzrael@@t-online.invalid") ("Spam" "^Cc: .*azzrael@@t-online.invalid")
("Spam" "^X-Mailer-Version: 1.50 BETA") ("Spam" "^X-Mailer-Version: 1.50 BETA")
("Uni" "^\\(CC:\\|To:\\).*localpart@@uni-koblenz.invalid.*") ("Uni" "^\\(Cc:\\|To:\\).*localpart@@uni-koblenz.invalid.*")
("Inbox" "^\\(CC:\\|To:\\).*\\(my\ name\\|address@@one.invalid\\|address@@two.invalid\\)") ("Inbox" "^\\(Cc:\\|To:\\).*\\(my\ name\\|address@@one.invalid\\|address@@two.invalid\\)")
("Spam" ""))) ("Spam" "")))
@end example @end example
@noindent @noindent
......
...@@ -5592,7 +5592,7 @@ command uses the process/prefix convention. ...@@ -5592,7 +5592,7 @@ command uses the process/prefix convention.
Mail a wide reply to the author of the current article Mail a wide reply to the author of the current article
(@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that (@code{gnus-summary-wide-reply}). A @dfn{wide reply} is a reply that
goes out to all people listed in the @code{To}, @code{From} (or goes out to all people listed in the @code{To}, @code{From} (or
@code{Reply-to}) and @code{Cc} headers. If @code{Mail-Followup-To} is @code{Reply-To}) and @code{Cc} headers. If @code{Mail-Followup-To} is
present, that's used instead. present, that's used instead.
@item S W @item S W
...@@ -5616,7 +5616,7 @@ message to the mailing list, and include the original message ...@@ -5616,7 +5616,7 @@ message to the mailing list, and include the original message
Mail a very wide reply to the author of the current article Mail a very wide reply to the author of the current article
(@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply (@code{gnus-summary-wide-reply}). A @dfn{very wide reply} is a reply
that goes out to all people listed in the @code{To}, @code{From} (or that goes out to all people listed in the @code{To}, @code{From} (or
@code{Reply-to}) and @code{Cc} headers in all the process/prefixed @code{Reply-To}) and @code{Cc} headers in all the process/prefixed
articles. This command uses the process/prefix convention. articles. This command uses the process/prefix convention.
@item S V @item S V
...@@ -174,7 +174,7 @@ inserted into the head of the outgoing mail. ...@@ -174,7 +174,7 @@ inserted into the head of the outgoing mail.
The @code{message-wide-reply} pops up a message buffer that's a wide The @code{message-wide-reply} pops up a message buffer that's a wide
reply to the message in the current buffer. A @dfn{wide reply} is a reply to the message in the current buffer. A @dfn{wide reply} is a
reply that goes out to all people listed in the @code{To}, @code{From} reply that goes out to all people listed in the @code{To}, @code{From}
(or @code{Reply-to}) and @code{Cc} headers. (or @code{Reply-To}) and @code{Cc} headers.
@vindex message-wide-reply-to-function @vindex message-wide-reply-to-function
Message uses the normal methods to determine where wide replies are to go, Message uses the normal methods to determine where wide replies are to go,
...@@ -2056,7 +2056,7 @@ Check whether the @code{Newsgroups} header exists and is not empty. ...@@ -2056,7 +2056,7 @@ Check whether the @code{Newsgroups} header exists and is not empty.
@item quoting-style @item quoting-style
Check whether text follows last quoted portion. Check whether text follows last quoted portion.
@item repeated-newsgroups @item repeated-newsgroups
Check whether the @code{Newsgroups} and @code{Followup-to} headers Check whether the @code{Newsgroups} and @code{Followup-To} headers
contains repeated group names. contains repeated group names.
@item reply-to @item reply-to
Check whether the @code{Reply-To} header looks ok. Check whether the @code{Reply-To} header looks ok.
...@@ -2069,7 +2069,7 @@ Check for the existence of version and sendsys commands. ...@@ -2069,7 +2069,7 @@ Check for the existence of version and sendsys commands.
@item shoot @item shoot
Check whether the domain part of the @code{Message-ID} header looks ok. Check whether the domain part of the @code{Message-ID} header looks ok.
@item shorten-followup-to @item shorten-followup-to
Check whether to add a @code{Followup-to} header to shorten the number Check whether to add a @code{Followup-To} header to shorten the number
of groups to post to. of groups to post to.
@item signature @item signature
Check the length of the signature. Check the length of the signature.
...@@ -2080,7 +2080,7 @@ Check whether the @code{Subject} header exists and is not empty. ...@@ -2080,7 +2080,7 @@ Check whether the @code{Subject} header exists and is not empty.
@item subject-cmsg @item subject-cmsg
Check the subject for commands. Check the subject for commands.
@item valid-newsgroups @item valid-newsgroups
Check whether the @code{Newsgroups} and @code{Followup-to} headers Check whether the @code{Newsgroups} and @code{Followup-To} headers
are valid syntactically. are valid syntactically.
@end table @end table
......
...@@ -847,9 +847,9 @@ sending the original message, like this: ...@@ -847,9 +847,9 @@ sending the original message, like this:
To: To:
cc: cc:
Subject: Re: Test Subject: Re: Test
In-reply-to: <31054.1142621351@@stop.mail-abuse.org> In-Reply-To: <31054.1142621351@@stop.mail-abuse.org>
References: <31054.1142621351@@stop.mail-abuse.org> References: <31054.1142621351@@stop.mail-abuse.org>
Comments: In-reply-to Bill Wohler <wohler@@stop.mail-abuse.org> Comments: In-Reply-To Bill Wohler <wohler@@stop.mail-abuse.org>
message dated "Fri, 17 Mar 2006 10:49:11 -0800." message dated "Fri, 17 Mar 2006 10:49:11 -0800."
X-Mailer: MH-E 8.1; nmh 1.1; GNU Emacs 23.1 X-Mailer: MH-E 8.1; nmh 1.1; GNU Emacs 23.1
-------- --------
......
...@@ -201,10 +201,10 @@ is carried over to the expansion that replaces it. ...@@ -201,10 +201,10 @@ is carried over to the expansion that replaces it.
has the syntax of an ordinary punctuation character. As a result, has the syntax of an ordinary punctuation character. As a result,
\[...\] and such like are considered to balance each other. \[...\] and such like are considered to balance each other.
* Mail-mode automatic Reply-to field. * Mail-mode automatic Reply-To field.
If the variable `mail-default-reply-to' is non-`nil', then each time If the variable `mail-default-reply-to' is non-`nil', then each time
you start to compose a message, a Reply-to field is inserted with you start to compose a message, a Reply-To field is inserted with
its contents taken from the value of `mail-default-reply-to'. its contents taken from the value of `mail-default-reply-to'.
* Where is your .emacs file? * Where is your .emacs file?
......
...@@ -438,7 +438,7 @@ The other accent characters, not needed for the chosen language, ...@@ -438,7 +438,7 @@ The other accent characters, not needed for the chosen language,
remain normal. remain normal.
** Posting articles and sending mail now has M-TAB completion on various ** Posting articles and sending mail now has M-TAB completion on various
header fields (Newsgroups, To, CC, ...). header fields (Newsgroups, To, Cc, ...).
Completion in the Newsgroups header depends on the list of groups Completion in the Newsgroups header depends on the list of groups
known to your news reader. Completion in the Followup-To header known to your news reader. Completion in the Followup-To header
...@@ -2087,7 +2087,7 @@ arguments are ARGS. ...@@ -2087,7 +2087,7 @@ arguments are ARGS.
for mail-default-reply-to. for mail-default-reply-to.
** When you send a message in Emacs, if you specify an Rmail file with ** When you send a message in Emacs, if you specify an Rmail file with
the FCC: header field, Emacs converts the message to Rmail format the Fcc: header field, Emacs converts the message to Rmail format
before writing it. Thus, the file never contains anything but Rmail before writing it. Thus, the file never contains anything but Rmail
format messages. format messages.
......
...@@ -986,7 +986,7 @@ be prompted for confirmation ...@@ -986,7 +986,7 @@ be prompted for confirmation
**** can generate a MESSAGE-ID: line and a DATE: line; the date can be **** can generate a MESSAGE-ID: line and a DATE: line; the date can be
the time the message was written or the time it is being sent; this the time the message was written or the time it is being sent; this
can make FCC copies more closely resemble copies that recipients get can make Fcc copies more closely resemble copies that recipients get
**** you can specify an arbitrary function for actually transmitting **** you can specify an arbitrary function for actually transmitting
the message; included in feedmail are interfaces for /bin/[r]mail, the message; included in feedmail are interfaces for /bin/[r]mail,
......
...@@ -289,7 +289,7 @@ \section{Čtení a posílání pošty} ...@@ -289,7 +289,7 @@ \section{Čtení a posílání pošty}
\key{C-x m} nová zpráva \key{C-x m} nová zpráva
\key{C-c C-c} pošli zprávu a přepni do jiného bufferu \key{C-c C-c} pošli zprávu a přepni do jiného bufferu
\key{C-c C-f C-c} přesuň se na hlavičku `CC' a pokud neexistuje, tak ji \key{C-c C-f C-c} přesuň se na hlavičku `Cc' a pokud neexistuje, tak ji
vytvoř vytvoř
\section{Různé} \section{Různé}
......
...@@ -287,7 +287,7 @@ \section{Lecture et envoi de courrier} ...@@ -287,7 +287,7 @@ \section{Lecture et envoi de courrier}
\key{C-x m} d\'ebute la composition d'un message \key{C-x m} d\'ebute la composition d'un message
\key{C-c C-c} envoie le message et bascule dans un autre tampon \key{C-c C-c} envoie le message et bascule dans un autre tampon
\key{C-c C-f C-c} va \`a l'ent\^ete `CC', en cr\'ee un s'il n'existe pas \key{C-c C-f C-c} va \`a l'ent\^ete `Cc', en cr\'ee un s'il n'existe pas
\section{Divers} \section{Divers}
......
...@@ -292,7 +292,7 @@ \section{Čítanie a posielanie pošty} ...@@ -292,7 +292,7 @@ \section{Čítanie a posielanie pošty}
\key{C-x m} nová správa \key{C-x m} nová správa
\key{C-c C-c} pošli správu a prepni sa do iného bufferu \key{C-c C-c} pošli správu a prepni sa do iného bufferu
\key{C-c C-f C-c} presuň sa na hlavičku `CC', a ak neexistuje, tak ju \key{C-c C-f C-c} presuň sa na hlavičku `Cc', a ak neexistuje, tak ju
vytvor vytvor
\section{Rôzne} \section{Rôzne}
......
...@@ -278,7 +278,7 @@ \section{Reading and Sending Mail} ...@@ -278,7 +278,7 @@ \section{Reading and Sending Mail}
\key{C-x m} begin composing a message \key{C-x m} begin composing a message
\key{C-c C-c} send the message and switch to another buffer \key{C-c C-c} send the message and switch to another buffer
\key{C-c C-f C-c} move to the `CC' header field, creating one \key{C-c C-f C-c} move to the `Cc' header field, creating one
if there is none if there is none
\section{Miscellaneous} \section{Miscellaneous}
......
...@@ -1229,7 +1229,7 @@ ...@@ -1229,7 +1229,7 @@
1987-05-13 Richard M. Stallman (rms@prep) 1987-05-13 Richard M. Stallman (rms@prep)
* sendmail.el (mail-setup): New parameter mail-default-reply-to: * sendmail.el (mail-setup): New parameter mail-default-reply-to:
if non-nil, insert it as a Reply-to field.