@cindex yanking
@cindex quoting
When you are replying to or following up an article, you normally want
-to quote the person you are answering. Inserting quoted text is done by
-@dfn{yanking}, and each quoted line you yank will have
+to quote the person you are answering. Inserting quoted text is done
+by @dfn{yanking}, and each quoted line you yank (except earlier
+quotes, see @code{message-yank-cited-prefix}) will have
@code{message-yank-prefix} prepended to it. The default is @samp{> }.
+@item message-yank-cited-prefix
+@vindex message-yank-cited-prefix
+@cindex yanking
+@cindex cited
+@cindex quoting
+The @code{message-yank-prefix} prefix is not used on already cited
+lines, instead the contents of this variable is used as yank prefix.
+The default is @samp{>}.
+
@item message-indentation-spaces
@vindex message-indentation-spaces
Number of spaces to indent yanked messages.
Using the MML language, Message is able to create digitally signed and
digitally encrypted messages. Message (or rather MML) currently support
PGP/MIME and S/MIME. Instructing MML to perform security operations on
-a MIME part is done using the @code{M-m s} key map for signing and the
-@code{M-m c} key map for encryption, as follows.
+a MIME part is done using the @code{C-c C-m s} key map for signing and the
+@code{C-c C-m c} key map for encryption, as follows.
@table @kbd
-@item M-m s s
-@kindex M-m s s
+@item C-c C-m s s
+@kindex C-c C-m s s
@findex mml-secure-sign-smime
Digitally sign current MIME part using S/MIME.
-@item M-m s p
-@kindex M-m s p
+@item C-c C-m s p
+@kindex C-c C-m s p
@findex mml-secure-sign-pgp
Digitally sign current MIME part using PGP/MIME.
-@item M-m c s
-@kindex M-m c s
+@item C-c C-m c s
+@kindex C-c C-m c s
@findex mml-secure-encrypt-smime
Digitally encrypt current MIME part using S/MIME.
-@item M-m c p
-@kindex M-m c p
+@item C-c C-m c p
+@kindex C-c C-m c p
@findex mml-secure-encrypt-pgpmime
Digitally encrypt current MIME part using PGP/MIME.
information is sent, you may want to have some way to ensure that your
mail is actually signed or encrypted. After invoking the above
sign/encrypt commands, it is possible to preview the raw article by
-using @code{C-u M-m P} (@code{mml-preview}). Then you can verify that
+using @code{C-u C-m P} (@code{mml-preview}). Then you can verify that
your long rant about what your ex-significant other or whomever actually
did with that funny looking person at that strange party the other
night, actually will be sent encrypted.
To be able to send encrypted mail, a personal certificate is not
required. Message (MML) need a certificate for the person to whom you
wish to communicate with though. You're asked for this when you type
-@code{M-m c s}. Currently there are two ways to retrieve this
+@code{C-c C-m c s}. Currently there are two ways to retrieve this
certificate, from a local file or from DNS. If you chose a local file,
it need to contain a X.509 certificate in PEM format. If you chose DNS,
you're asked for the domain name where the certificate is stored, the
@subsection Using PGP/MIME
-PGP/MIME require an external OpenPGP implementation, such as GNU Privacy
-Guard (@code{http://www.gnupg.org/}. It also require a Emacs interface
-to it, such as Mailcrypt (available from
+PGP/MIME requires an external OpenPGP implementation, such as GNU
+Privacy Guard (@code{http://www.gnupg.org/}). It also requires an Emacs
+interface to it, such as Mailcrypt (available from
@code{http://www.nb.net/~lbudney/linux/software/mailcrypt.html}) or
Florian Weimer's @code{gpg.el}.
@item message-generate-headers-first
@vindex message-generate-headers-first
-If non-@code{nil}, generate all headers before starting to compose the
-message.
+If non-@code{nil}, generate all required headers before starting to
+compose the message.
+
+The variables @code{message-required-mail-headers} and
+@code{message-required-news-headers} specify which headers are required.
+
+Note that some headers will be removed and re-generated before posting,
+because of the variable @code{message-deletable-headers} (see below).
@item message-from-style
@vindex message-from-style
@vindex message-required-mail-headers
@xref{News Headers}, for the syntax of this variable. It is
@code{(From Date Subject (optional . In-Reply-To) Message-ID Lines
-(optional . X-Mailer))} by default.
+(optional . User-Agent))} by default.
@item message-ignored-mail-headers
@vindex message-ignored-mail-headers
Regexp of headers to be removed before mailing. The default is
-@samp{^[GF]cc:\\|^Resent-Fcc:}.
+@samp{^[GF]cc:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:}.
@item message-default-mail-headers
@vindex message-default-mail-headers
this isn't a fully qualified domain name (FQDN), Message will use
@code{mail-host-address} as the FQDN of the machine.
-@item X-Newsreader
-@cindex X-Newsreader
+@item User-Agent
+@cindex User-Agent
This optional header will be filled out according to the
@code{message-newsreader} local variable.
-@item X-Mailer
-This optional header will be filled out according to the
-@code{message-mailer} local variable, unless there already is an
-@code{X-Newsreader} header present.
-
@item In-Reply-To
This optional header is filled out using the @code{Date} and @code{From}
header of the article being replied to.
@item message-ignored-news-headers
@vindex message-ignored-news-headers
Regexp of headers to be removed before posting. The default is@*
-@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:}.
+@samp{^NNTP-Posting-Host:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|^X-Draft-From:}.
@item message-default-news-headers
@vindex message-default-news-headers
projects / gnus / blobdiff