[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to message.texi
|
From: |
Glenn Morris |
|
Subject: |
[Emacs-diffs] Changes to message.texi |
|
Date: |
Thu, 06 Sep 2007 04:38:27 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Glenn Morris <gm> 07/09/06 04:38:27
Index: message.texi
===================================================================
RCS file: message.texi
diff -N message.texi
--- message.texi 27 Aug 2007 04:00:18 -0000 1.45
+++ /dev/null 1 Jan 1970 00:00:00 -0000
@@ -1,2362 +0,0 @@
-\input texinfo @c -*-texinfo-*-
-
address@hidden ../info/message
address@hidden Message Manual
address@hidden fn cp
address@hidden vr cp
address@hidden pg cp
address@hidden
-This file documents Message, the Emacs message composition mode.
-
-Copyright @copyright{} 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
-2004, 2005, 2006, 2007 Free Software Foundation, Inc.
-
address@hidden
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, with the Front-Cover texts being ``A GNU
-Manual'', and with the Back-Cover Texts as in (a) below. A copy of the
-license is included in the section entitled ``GNU Free Documentation
-License'' in the Emacs manual.
-
-(a) The FSF's Back-Cover Text is: ``You have freedom to copy and modify
-this GNU Manual, like GNU software. Copies published by the Free
-Software Foundation raise funds for GNU development.''
-
-This document is part of a collection distributed under the GNU Free
-Documentation License. If you want to distribute this document
-separately from the collection, you can do so by adding a copy of the
-license to the document, as described in section 6 of the license.
address@hidden quotation
address@hidden copying
-
address@hidden Emacs
address@hidden
-* Message: (message). Mail and news composition mode that goes with Gnus.
address@hidden direntry
address@hidden
address@hidden
address@hidden iftex
address@hidden odd
-
address@hidden
address@hidden Message Manual
-
address@hidden by Lars Magne Ingebrigtsen
address@hidden
-
address@hidden 0pt plus 1filll
address@hidden
address@hidden titlepage
address@hidden
-
address@hidden Top
address@hidden Message
-
-All message composition from Gnus (both mail and news) takes place in
-Message mode buffers.
-
address@hidden
-* Interface:: Setting up message buffers.
-* Commands:: Commands you can execute in message mode buffers.
-* Variables:: Customizing the message buffers.
-* Compatibility:: Making Message backwards compatible.
-* Appendices:: More technical things.
-* GNU Free Documentation License:: The license for this documentation.
-* Index:: Variable, function and concept index.
-* Key Index:: List of Message mode keys.
address@hidden menu
-
address@hidden Adjust ../Makefile.in if you change the following lines:
-Message is distributed with Gnus. The Gnus distribution
address@hidden
-corresponding to this manual is Gnus v5.11.
-
-
address@hidden Interface
address@hidden Interface
-
-When a program (or a person) wants to respond to a message -- reply,
-follow up, forward, cancel -- the program (or person) should just put
-point in the buffer where the message is and call the required command.
address@hidden will then pop up a new @code{message} mode buffer with
-appropriate headers filled out, and the user can edit the message before
-sending it.
-
address@hidden
-* New Mail Message:: Editing a brand new mail message.
-* New News Message:: Editing a brand new news message.
-* Reply:: Replying via mail.
-* Wide Reply:: Responding to all people via mail.
-* Followup:: Following up via news.
-* Canceling News:: Canceling a news article.
-* Superseding:: Superseding a message.
-* Forwarding:: Forwarding a message via news or mail.
-* Resending:: Resending a mail message.
-* Bouncing:: Bouncing a mail message.
-* Mailing Lists:: Send mail to mailing lists.
address@hidden menu
-
-You can customize the Message Mode tool bar, see @kbd{M-x
-customize-apropos RET message-tool-bar}. This feature is only available
-in Emacs.
-
address@hidden New Mail Message
address@hidden New Mail Message
-
address@hidden message-mail
-The @code{message-mail} command pops up a new message buffer.
-
-Two optional parameters are accepted: The first will be used as the
address@hidden header and the second as the @code{Subject} header. If these
-are @code{nil}, those two headers will be empty.
-
-
address@hidden New News Message
address@hidden New News Message
-
address@hidden message-news
-The @code{message-news} command pops up a new message buffer.
-
-This function accepts two optional parameters. The first will be used
-as the @code{Newsgroups} header and the second as the @code{Subject}
-header. If these are @code{nil}, those two headers will be empty.
-
-
address@hidden Reply
address@hidden Reply
-
address@hidden message-reply
-The @code{message-reply} function pops up a message buffer that's a
-reply to the message in the current buffer.
-
address@hidden message-reply-to-function
-Message uses the normal methods to determine where replies are to go
-(@pxref{Responses}), but you can change the behavior to suit your needs
-by fiddling with the @code{message-reply-to-function} variable.
-
-If you want the replies to go to the @code{Sender} instead of the
address@hidden, you could do something like this:
-
address@hidden
-(setq message-reply-to-function
- (lambda ()
- (cond ((equal (mail-fetch-field "from") "somebody")
- (list (cons 'To (mail-fetch-field "sender"))))
- (t
- nil))))
address@hidden lisp
-
-This function will be called narrowed to the head of the article that is
-being replied to.
-
-As you can see, this function should return a list. In this case, it
-returns @code{((To . "Whom"))} if it has an opinion as to what the To
-header should be. If it does not, it should just return @code{nil}, and
-the normal methods for determining the To header will be used.
-
-Each list element should be a cons, where the @sc{car} should be the
-name of a header (e.g. @code{Cc}) and the @sc{cdr} should be the header
-value (e.g. @samp{larsi@@ifi.uio.no}). All these headers will be
-inserted into the head of the outgoing mail.
-
-
address@hidden Wide Reply
address@hidden Wide Reply
-
address@hidden message-wide-reply
-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 that goes out to all people listed in the @code{To}, @code{From}
-(or @code{Reply-to}) and @code{Cc} headers.
-
address@hidden message-wide-reply-to-function
-Message uses the normal methods to determine where wide replies are to go,
-but you can change the behavior to suit your needs by fiddling with the
address@hidden It is used in the same way as
address@hidden (@pxref{Reply}).
-
address@hidden message-dont-reply-to-names
-Addresses that match the @code{message-dont-reply-to-names} regular
-expression will be removed from the @code{Cc} header.
-
address@hidden message-wide-reply-confirm-recipients
-If @code{message-wide-reply-confirm-recipients} is address@hidden you
-will be asked to confirm that you want to reply to multiple
-recipients. The default is @code{nil}.
-
address@hidden Followup
address@hidden Followup
-
address@hidden message-followup
-The @code{message-followup} command pops up a message buffer that's a
-followup to the message in the current buffer.
-
address@hidden message-followup-to-function
-Message uses the normal methods to determine where followups are to go,
-but you can change the behavior to suit your needs by fiddling with the
address@hidden It is used in the same way as
address@hidden (@pxref{Reply}).
-
address@hidden message-use-followup-to
-The @code{message-use-followup-to} variable says what to do about
address@hidden headers. If it is @code{use}, always use the value.
-If it is @code{ask} (which is the default), ask whether to use the
-value. If it is @code{t}, use the value unless it is @samp{poster}. If
-it is @code{nil}, don't use the value.
-
-
address@hidden Canceling News
address@hidden Canceling News
-
address@hidden message-cancel-news
-The @code{message-cancel-news} command cancels the article in the
-current buffer.
-
address@hidden message-cancel-message
-The value of @code{message-cancel-message} is inserted in the body of
-the cancel message. The default is @samp{I am canceling my own
-article.}.
-
address@hidden Cancel Locks
address@hidden message-insert-canlock
address@hidden canlock
-When Message posts news messages, it inserts @code{Cancel-Lock}
-headers by default. This is a cryptographic header that ensures that
-only you can cancel your own messages, which is nice. The downside
-is that if you lose your @file{.emacs} file (which is where Gnus
-stores the secret cancel lock password (which is generated
-automatically the first time you use this feature)), you won't be
-able to cancel your message. If you want to manage a password yourself,
-you can put something like the following in your @file{~/.gnus.el} file:
-
address@hidden
-(setq canlock-password "geheimnis"
- canlock-password-for-verify canlock-password)
address@hidden lisp
-
-Whether to insert the header or not is controlled by the
address@hidden variable.
-
-Not many news servers respect the @code{Cancel-Lock} header yet, but
-this is expected to change in the future.
-
-
address@hidden Superseding
address@hidden Superseding
-
address@hidden message-supersede
-The @code{message-supersede} command pops up a message buffer that will
-supersede the message in the current buffer.
-
address@hidden message-ignored-supersedes-headers
-Headers matching the @code{message-ignored-supersedes-headers} are
-removed before popping up the new message buffer. The default address@hidden
address@hidden:\\|^Date\\|^NNTP-Posting-Host:\\|^Xref:\\|^Lines:\\|@*
-^Received:\\|^X-From-Line:\\|^X-Trace:\\|^X-Complaints-To:\\|@*
-Return-Path:\\|^Supersedes:\\|^NNTP-Posting-Date:\\|^X-Trace:\\|@*
-^X-Complaints-To:\\|^Cancel-Lock:\\|^Cancel-Key:\\|^X-Hashcash:\\|@*
-^X-Payment:}.
-
-
-
address@hidden Forwarding
address@hidden Forwarding
-
address@hidden message-forward
-The @code{message-forward} command pops up a message buffer to forward
-the message in the current buffer. If given a prefix, forward using
-news.
-
address@hidden @code
address@hidden message-forward-ignored-headers
address@hidden message-forward-ignored-headers
-All headers that match this regexp will be deleted when forwarding a message.
-
address@hidden message-make-forward-subject-function
address@hidden message-make-forward-subject-function
-A list of functions that are called to generate a subject header for
-forwarded messages. The subject generated by the previous function is
-passed into each successive function.
-
-The provided functions are:
-
address@hidden @code
address@hidden message-forward-subject-author-subject
address@hidden message-forward-subject-author-subject
-Source of article (author or newsgroup), in brackets followed by the
-subject.
-
address@hidden message-forward-subject-fwd
-Subject of article with @samp{Fwd:} prepended to it.
address@hidden table
-
address@hidden message-wash-forwarded-subjects
address@hidden message-wash-forwarded-subjects
-If this variable is @code{t}, the subjects of forwarded messages have
-the evidence of previous forwards (such as @samp{Fwd:}, @samp{Re:},
address@hidden(fwd)}) removed before the new subject is
-constructed. The default value is @code{nil}.
-
address@hidden message-forward-as-mime
address@hidden message-forward-as-mime
-If this variable is @code{t} (the default), forwarded messages are
-included as inline @acronym{MIME} RFC822 parts. If it's @code{nil}, forwarded
-messages will just be copied inline to the new message, like previous,
-non @acronym{MIME}-savvy versions of Gnus would do.
-
address@hidden message-forward-before-signature
address@hidden message-forward-before-signature
-If address@hidden, put forwarded message before signature, else after.
-
address@hidden table
-
-
address@hidden Resending
address@hidden Resending
-
address@hidden message-resend
-The @code{message-resend} command will prompt the user for an address
-and resend the message in the current buffer to that address.
-
address@hidden message-ignored-resent-headers
-Headers that match the @code{message-ignored-resent-headers} regexp will
-be removed before sending the message.
-
-
address@hidden Bouncing
address@hidden Bouncing
-
address@hidden message-bounce
-The @code{message-bounce} command will, if the current buffer contains a
-bounced mail message, pop up a message buffer stripped of the bounce
-information. A @dfn{bounced message} is typically a mail you've sent
-out that has been returned by some @code{mailer-daemon} as
-undeliverable.
-
address@hidden message-ignored-bounced-headers
-Headers that match the @code{message-ignored-bounced-headers} regexp
-will be removed before popping up the buffer. The default is
address@hidden(Received\\|Return-Path\\|Delivered-To\\):}.
-
-
address@hidden Mailing Lists
address@hidden Mailing Lists
-
address@hidden Mail-Followup-To
-Sometimes while posting to mailing lists, the poster needs to direct
-followups to the post to specific places. The Mail-Followup-To (MFT)
-was created to enable just this. Three example scenarios where this is
-useful:
-
address@hidden @bullet
address@hidden
-A mailing list poster can use MFT to express that responses should be
-sent to just the list, and not the poster as well. This will happen
-if the poster is already subscribed to the list.
-
address@hidden
-A mailing list poster can use MFT to express that responses should be
-sent to the list and the poster as well. This will happen if the poster
-is not subscribed to the list.
-
address@hidden
-If a message is posted to several mailing lists, MFT may also be used
-to direct the following discussion to one list only, because
-discussions that are spread over several lists tend to be fragmented
-and very difficult to follow.
-
address@hidden itemize
-
-Gnus honors the MFT header in other's messages (i.e. while following
-up to someone else's post) and also provides support for generating
-sensible MFT headers for outgoing messages as well.
-
address@hidden @menu
address@hidden * Honoring an MFT post:: What to do when one already
exists
address@hidden * Composing with a MFT header:: Creating one from scratch.
address@hidden @end menu
-
address@hidden @node Composing with a MFT header
address@hidden Composing a correct MFT header automagically
-
-The first step in getting Gnus to automagically generate a MFT header
-in posts you make is to give Gnus a list of the mailing lists
-addresses you are subscribed to. You can do this in more than one
-way. The following variables would come in handy.
-
address@hidden @code
-
address@hidden message-subscribed-addresses
address@hidden message-subscribed-addresses
-This should be a list of addresses the user is subscribed to. Its
-default value is @code{nil}. Example:
address@hidden
-(setq message-subscribed-addresses
- '("ding@@gnus.org" "bing@@noose.org"))
address@hidden lisp
-
address@hidden message-subscribed-regexps
address@hidden message-subscribed-regexps
-This should be a list of regexps denoting the addresses of mailing
-lists subscribed to. Default value is @code{nil}. Example: If you
-want to achieve the same result as above:
address@hidden
-(setq message-subscribed-regexps
- '("\\(ding@@gnus\\)\\|\\(bing@@noose\\)\\.org")
address@hidden lisp
-
address@hidden message-subscribed-address-functions
address@hidden message-subscribed-address-functions
-This can be a list of functions to be called (one at a time!!) to
-determine the value of MFT headers. It is advisable that these
-functions not take any arguments. Default value is @code{nil}.
-
-There is a pre-defined function in Gnus that is a good candidate for
-this variable. @code{gnus-find-subscribed-addresses} is a function
-that returns a list of addresses corresponding to the groups that have
-the @code{subscribed} (@pxref{Group Parameters, ,Group Parameters,
-gnus, The Gnus Manual}) group parameter set to a address@hidden value.
-This is how you would do it.
-
address@hidden
-(setq message-subscribed-address-functions
- '(gnus-find-subscribed-addresses))
address@hidden lisp
-
address@hidden message-subscribed-address-file
address@hidden message-subscribed-address-file
-You might be one organized human freak and have a list of addresses of
-all subscribed mailing lists in a separate file! Then you can just
-set this variable to the name of the file and life would be good.
-
address@hidden table
-
-You can use one or more of the above variables. All their values are
-``added'' in some way that works :-)
-
-Now you are all set. Just start composing a message as you normally do.
-And just send it; as always. Just before the message is sent out, Gnus'
-MFT generation thingy kicks in and checks if the message already has a
-MFT field. If there is one, it is left alone. (Except if it's empty -
-in that case, the field is removed and is not replaced with an
-automatically generated one. This lets you disable MFT generation on a
-per-message basis.) If there is none, then the list of recipient
-addresses (in the To: and Cc: headers) is checked to see if one of them
-is a list address you are subscribed to. If none of them is a list
-address, then no MFT is generated; otherwise, a MFT is added to the
-other headers and set to the value of all addresses in To: and Cc:
-
address@hidden C-c C-f C-a
address@hidden message-generate-unsubscribed-mail-followup-to
address@hidden C-c C-f C-m
address@hidden message-goto-mail-followup-to
-Hm. ``So'', you ask, ``what if I send an email to a list I am not
-subscribed to? I want my MFT to say that I want an extra copy.'' (This
-is supposed to be interpreted by others the same way as if there were no
-MFT, but you can use an explicit MFT to override someone else's
-to-address group parameter.) The function
address@hidden might come in
-handy. It is bound to @kbd{C-c C-f C-a} by default. In any case, you
-can insert a MFT of your own choice; @kbd{C-c C-f C-m}
-(@code{message-goto-mail-followup-to}) will help you get started.
-
address@hidden @node Honoring an MFT post
address@hidden Honoring an MFT post
-
address@hidden message-use-mail-followup-to
-When you followup to a post on a mailing list, and the post has a MFT
-header, Gnus' action will depend on the value of the variable
address@hidden This variable can be one of:
-
address@hidden @code
address@hidden use
- Always honor MFTs. The To: and Cc: headers in your followup will be
- derived from the MFT header of the original post. This is the default.
-
address@hidden nil
- Always dishonor MFTs (just ignore the darned thing)
-
address@hidden ask
-Gnus will prompt you for an action.
-
address@hidden table
-
-It is considered good netiquette to honor MFT, as it is assumed the
-fellow who posted a message knows where the followups need to go
-better than you do.
-
address@hidden Commands
address@hidden Commands
-
address@hidden
-* Buffer Entry:: Commands after entering a Message buffer.
-* Header Commands:: Commands for moving headers or changing headers.
-* Movement:: Moving around in message buffers.
-* Insertion:: Inserting things into message buffers.
-* MIME:: @acronym{MIME} considerations.
-* IDNA:: address@hidden domain name considerations.
-* Security:: Signing and encrypting messages.
-* Various Commands:: Various things.
-* Sending:: Actually sending the message.
-* Mail Aliases:: How to use mail aliases.
-* Spelling:: Having Emacs check your spelling.
address@hidden menu
-
-
address@hidden Buffer Entry
address@hidden Buffer Entry
address@hidden undo
address@hidden C-_
-
-You most often end up in a Message buffer when responding to some other
-message of some sort. Message does lots of handling of quoted text, and
-may remove signatures, reformat the text, or the like---depending on
-which used settings you're using. Message usually gets things right,
-but sometimes it stumbles. To help the user unwind these stumblings,
-Message sets the undo boundary before each major automatic action it
-takes. If you press the undo key (usually located at @kbd{C-_}) a few
-times, you will get back the un-edited message you're responding to.
-
-
address@hidden Header Commands
address@hidden Header Commands
-
address@hidden Commands for moving to headers
-
-These following commands move to the header in question. If it doesn't
-exist, it will be inserted.
-
address@hidden @kbd
-
address@hidden C-c ?
address@hidden C-c ?
address@hidden describe-mode
-Describe the message mode.
-
address@hidden C-c C-f C-t
address@hidden C-c C-f C-t
address@hidden message-goto-to
-Go to the @code{To} header (@code{message-goto-to}).
-
address@hidden C-c C-f C-o
address@hidden C-c C-f C-o
address@hidden message-goto-from
-Go to the @code{From} header (@code{message-goto-from}). (The ``o''
-in the key binding is for Originator.)
-
address@hidden C-c C-f C-b
address@hidden C-c C-f C-b
address@hidden message-goto-bcc
-Go to the @code{Bcc} header (@code{message-goto-bcc}).
-
address@hidden C-c C-f C-f
address@hidden C-c C-f C-f
address@hidden message-goto-fcc
-Go to the @code{Fcc} header (@code{message-goto-fcc}).
-
address@hidden C-c C-f C-c
address@hidden C-c C-f C-c
address@hidden message-goto-cc
-Go to the @code{Cc} header (@code{message-goto-cc}).
-
address@hidden C-c C-f C-s
address@hidden C-c C-f C-s
address@hidden message-goto-subject
-Go to the @code{Subject} header (@code{message-goto-subject}).
-
address@hidden C-c C-f C-r
address@hidden C-c C-f C-r
address@hidden message-goto-reply-to
-Go to the @code{Reply-To} header (@code{message-goto-reply-to}).
-
address@hidden C-c C-f C-n
address@hidden C-c C-f C-n
address@hidden message-goto-newsgroups
-Go to the @code{Newsgroups} header (@code{message-goto-newsgroups}).
-
address@hidden C-c C-f C-d
address@hidden C-c C-f C-d
address@hidden message-goto-distribution
-Go to the @code{Distribution} header (@code{message-goto-distribution}).
-
address@hidden C-c C-f C-o
address@hidden C-c C-f C-o
address@hidden message-goto-followup-to
-Go to the @code{Followup-To} header (@code{message-goto-followup-to}).
-
address@hidden C-c C-f C-k
address@hidden C-c C-f C-k
address@hidden message-goto-keywords
-Go to the @code{Keywords} header (@code{message-goto-keywords}).
-
address@hidden C-c C-f C-u
address@hidden C-c C-f C-u
address@hidden message-goto-summary
-Go to the @code{Summary} header (@code{message-goto-summary}).
-
address@hidden C-c C-f C-i
address@hidden C-c C-f C-i
address@hidden message-insert-or-toggle-importance
-This inserts the @samp{Importance:} header with a value of
address@hidden This header is used to signal the importance of the
-message to the receiver. If the header is already present in the
-buffer, it cycles between the three valid values according to RFC
-1376: @samp{low}, @samp{normal} and @samp{high}.
-
address@hidden C-c C-f C-a
address@hidden C-c C-f C-a
address@hidden message-generate-unsubscribed-mail-followup-to
-Insert a reasonable @samp{Mail-Followup-To:} header
-(@pxref{Mailing Lists}) in a post to an
-unsubscribed list. When making original posts to a mailing list you are
-not subscribed to, you have to type in a @samp{Mail-Followup-To:} header
-by hand. The contents, usually, are the addresses of the list and your
-own address. This function inserts such a header automatically. It
-fetches the contents of the @samp{To:} header in the current mail
-buffer, and appends the current @code{user-mail-address}.
-
-If the optional argument @code{include-cc} is address@hidden, the
-addresses in the @samp{Cc:} header are also put into the
address@hidden:} header.
-
address@hidden table
-
address@hidden Commands to change headers
-
address@hidden @kbd
-
address@hidden C-c C-o
address@hidden C-c C-o
address@hidden message-sort-headers
address@hidden message-header-format-alist
-Sort headers according to @code{message-header-format-alist}
-(@code{message-sort-headers}).
-
address@hidden C-c C-t
address@hidden C-c C-t
address@hidden message-insert-to
-Insert a @code{To} header that contains the @code{Reply-To} or
address@hidden header of the message you're following up
-(@code{message-insert-to}).
-
address@hidden C-c C-n
address@hidden C-c C-n
address@hidden message-insert-newsgroups
-Insert a @code{Newsgroups} header that reflects the @code{Followup-To}
-or @code{Newsgroups} header of the article you're replying to
-(@code{message-insert-newsgroups}).
-
address@hidden C-c C-l
address@hidden C-c C-l
address@hidden message-to-list-only
-Send a message to the list only. Remove all addresses but the list
-address from @code{To:} and @code{Cc:} headers.
-
address@hidden C-c M-n
address@hidden C-c M-n
address@hidden message-insert-disposition-notification-to
-Insert a request for a disposition
-notification. (@code{message-insert-disposition-notification-to}).
-This means that if the recipient support RFC 2298 she might send you a
-notification that she received the message.
-
address@hidden M-x message-insert-importance-high
address@hidden M-x message-insert-importance-high
address@hidden message-insert-importance-high
address@hidden Importance
-Insert an @samp{Importance} header with a value of @samp{high},
-deleting headers if necessary.
-
address@hidden M-x message-insert-importance-low
address@hidden M-x message-insert-importance-low
address@hidden message-insert-importance-low
address@hidden Importance
-Insert an @samp{Importance} header with a value of @samp{low}, deleting
-headers if necessary.
-
address@hidden C-c C-f s
address@hidden C-c C-f s
address@hidden message-change-subject
address@hidden Subject
-Change the current @samp{Subject} header. Ask for new @samp{Subject}
-header and append @samp{(was: <Old Subject>)}. The old subject can be
-stripped on replying, see @code{message-subject-trailing-was-query}
-(@pxref{Message Headers}).
-
address@hidden C-c C-f x
address@hidden C-c C-f x
address@hidden message-cross-post-followup-to
address@hidden message-cross-post-default
address@hidden message-cross-post-note-function
address@hidden X-Post
address@hidden cross-post
-Set up the @samp{FollowUp-To} header with a target newsgroup for a
-cross-post, add that target newsgroup to the @samp{Newsgroups} header if
-it is not a member of @samp{Newsgroups}, and insert a note in the body.
-If @code{message-cross-post-default} is @code{nil} or if this command is
-called with a prefix-argument, only the @samp{FollowUp-To} header will
-be set but the target newsgroup will not be added to the
address@hidden header. The function to insert a note is controlled
-by the @code{message-cross-post-note-function} variable.
-
address@hidden C-c C-f t
address@hidden C-c C-f t
address@hidden message-reduce-to-to-cc
-Replace contents of @samp{To} header with contents of @samp{Cc} or
address@hidden header. (Iff @samp{Cc} header is not present, @samp{Bcc}
-header will be used instead.)
-
address@hidden C-c C-f w
address@hidden C-c C-f w
address@hidden message-insert-wide-reply
-Insert @samp{To} and @samp{Cc} headers as if you were doing a wide
-reply even if the message was not made for a wide reply first.
-
address@hidden C-c C-f a
address@hidden C-c C-f a
address@hidden message-add-archive-header
address@hidden message-archive-header
address@hidden message-archive-note
address@hidden X-No-Archive
-Insert @samp{X-No-Archive: Yes} in the header and a note in the body.
-The header and the note can be customized using
address@hidden and @code{message-archive-note}. When
-called with a prefix argument, ask for a text to insert. If you don't
-want the note in the body, set @code{message-archive-note} to
address@hidden
-
address@hidden table
-
-
address@hidden Movement
address@hidden Movement
-
address@hidden @kbd
address@hidden C-c C-b
address@hidden C-c C-b
address@hidden message-goto-body
-Move to the beginning of the body of the message
-(@code{message-goto-body}).
-
address@hidden C-c C-i
address@hidden C-c C-i
address@hidden message-goto-signature
-Move to the signature of the message (@code{message-goto-signature}).
-
address@hidden C-a
address@hidden C-a
address@hidden message-beginning-of-line
address@hidden message-beginning-of-line
-If at beginning of header value, go to beginning of line, else go to
-beginning of header value. (The header value comes after the header
-name and the colon.) This behavior can be disabled by toggling
-the variable @code{message-beginning-of-line}.
-
address@hidden table
-
-
address@hidden Insertion
address@hidden Insertion
-
address@hidden @kbd
-
address@hidden C-c C-y
address@hidden C-c C-y
address@hidden message-yank-original
-Yank the message that's being replied to into the message buffer
-(@code{message-yank-original}).
-
address@hidden C-c C-M-y
address@hidden C-c C-M-y
address@hidden message-yank-buffer
-Prompt for a buffer name and yank the contents of that buffer into the
-message buffer (@code{message-yank-buffer}).
-
address@hidden C-c C-q
address@hidden C-c C-q
address@hidden message-fill-yanked-message
-Fill the yanked message (@code{message-fill-yanked-message}). Warning:
-Can severely mess up the yanked text if its quoting conventions are
-strange. You'll quickly get a feel for when it's safe, though. Anyway,
-just remember that @kbd{C-x u} (@code{undo}) is available and you'll be
-all right.
-
address@hidden C-c C-w
address@hidden C-c C-w
address@hidden message-insert-signature
-Insert a signature at the end of the buffer
-(@code{message-insert-signature}).
-
address@hidden C-c M-h
address@hidden C-c M-h
address@hidden message-insert-headers
-Insert the message headers (@code{message-insert-headers}).
-
address@hidden C-c M-m
address@hidden C-c M-m
address@hidden message-mark-inserted-region
-Mark some region in the current article with enclosing tags.
-See @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
-
address@hidden C-c M-f
address@hidden C-c M-f
address@hidden message-mark-insert-file
-Insert a file in the current article with enclosing tags.
-See @code{message-mark-insert-begin} and @code{message-mark-insert-end}.
-
address@hidden table
-
-
address@hidden MIME
address@hidden MIME
address@hidden MML
address@hidden MIME
address@hidden multipart
address@hidden attachment
-
-Message is a @acronym{MIME}-compliant posting agent. The user generally
-doesn't have to do anything to make the @acronym{MIME} happen---Message will
-automatically add the @code{Content-Type} and
address@hidden headers.
-
address@hidden mml-attach-file
address@hidden C-c C-a
-The most typical thing users want to use the multipart things in
address@hidden for is to add ``attachments'' to mail they send out.
-This can be done with the @kbd{C-c C-a} command (@kbd{M-x mml-attach-file}),
-which will prompt for a file name and a @acronym{MIME} type.
-
address@hidden mml-dnd-protocol-alist
address@hidden mml-dnd-attach-options
-If your Emacs supports drag and drop, you can also drop the file in the
-Message buffer. The variable @code{mml-dnd-protocol-alist} specifies
-what kind of action is done when you drop a file into the Message
-buffer. The variable @code{mml-dnd-attach-options} controls which
address@hidden options you want to specify when dropping a file. If it
-is a list, valid members are @code{type}, @code{description} and
address@hidden @code{disposition} implies @code{type}. If it is
address@hidden, don't ask for options. If it is @code{t}, ask the user
-whether or not to specify options.
-
-You can also create arbitrarily complex multiparts using the @acronym{MML}
-language (@pxref{Composing, , Composing, emacs-mime, The Emacs MIME
-Manual}).
-
address@hidden IDNA
address@hidden IDNA
address@hidden IDNA
address@hidden internationalized domain names
address@hidden non-ascii domain names
-
-Message is a @acronym{IDNA}-compliant posting agent. The user
-generally doesn't have to do anything to make the @acronym{IDNA}
-happen---Message will encode address@hidden domain names in @code{From},
address@hidden, and @code{Cc} headers automatically.
-
-Until @acronym{IDNA} becomes more well known, Message queries you
-whether @acronym{IDNA} encoding of the domain name really should
-occur. Some users might not be aware that domain names can contain
address@hidden now, so this gives them a safety net if they accidently
-typed a address@hidden domain name.
-
address@hidden message-use-idna
-The @code{message-use-idna} variable control whether @acronym{IDNA} is
-used. If the variable is @code{nil} no @acronym{IDNA} encoding will
-ever happen, if it is set to the symbol @code{ask} the user will be
-queried, and if set to @code{t} (which is the default if @acronym{IDNA}
-is fully available) @acronym{IDNA} encoding happens automatically.
-
address@hidden message-idna-to-ascii-rhs
-If you want to experiment with the @acronym{IDNA} encoding, you can
-invoke @kbd{M-x message-idna-to-ascii-rhs RET} in the message buffer
-to have the address@hidden domain names encoded while you edit
-the message.
-
-Note that you must have @uref{http://www.gnu.org/software/libidn/, GNU
-Libidn} installed in order to use this functionality.
-
address@hidden Security
address@hidden Security
address@hidden Security
address@hidden S/MIME
address@hidden PGP
address@hidden PGP/MIME
address@hidden sign
address@hidden encrypt
address@hidden secure
-
-Using the @acronym{MML} language, Message is able to create digitally
-signed and digitally encrypted messages. Message (or rather
address@hidden) currently support @acronym{PGP} (RFC 1991),
address@hidden/MIME} (RFC 2015/3156) and @acronym{S/MIME}.
-
address@hidden
-* Signing and encryption:: Signing and encrypting commands.
-* Using S/MIME:: Using S/MIME
-* Using PGP/MIME:: Using PGP/MIME
-* PGP Compatibility:: Compatibility with older implementations
address@hidden menu
-
address@hidden Signing and encryption
address@hidden Signing and encrypting commands
-
-Instructing @acronym{MML} to perform security operations on a
address@hidden part is done using the @kbd{C-c C-m s} key map for
-signing and the @kbd{C-c C-m c} key map for encryption, as follows.
address@hidden @kbd
-
address@hidden C-c C-m s s
address@hidden C-c C-m s s
address@hidden mml-secure-message-sign-smime
-
-Digitally sign current message using @acronym{S/MIME}.
-
address@hidden C-c C-m s o
address@hidden C-c C-m s o
address@hidden mml-secure-message-sign-pgp
-
-Digitally sign current message using @acronym{PGP}.
-
address@hidden C-c C-m s p
address@hidden C-c C-m s p
address@hidden mml-secure-message-sign-pgpmime
-
-Digitally sign current message using @acronym{PGP/MIME}.
-
address@hidden C-c C-m c s
address@hidden C-c C-m c s
address@hidden mml-secure-message-encrypt-smime
-
-Digitally encrypt current message using @acronym{S/MIME}.
-
address@hidden C-c C-m c o
address@hidden C-c C-m c o
address@hidden mml-secure-message-encrypt-pgp
-
-Digitally encrypt current message using @acronym{PGP}.
-
address@hidden C-c C-m c p
address@hidden C-c C-m c p
address@hidden mml-secure-message-encrypt-pgpmime
-
-Digitally encrypt current message using @acronym{PGP/MIME}.
-
address@hidden C-c C-m C-n
address@hidden C-c C-m C-n
address@hidden mml-unsecure-message
-Remove security related @acronym{MML} tags from message.
-
address@hidden table
-
-These commands do not immediately sign or encrypt the message, they
-merely insert the proper @acronym{MML} secure tag to instruct the
address@hidden engine to perform that operation when the message is
-actually sent. They may perform other operations too, such as locating
-and retrieving a @acronym{S/MIME} certificate of the person you wish to
-send encrypted mail to. When the mml parsing engine converts your
address@hidden into a properly encoded @acronym{MIME} message, the secure
-tag will be replaced with either a part or a multipart tag. If your
-message contains other mml parts, a multipart tag will be used; if no
-other parts are present in your message a single part tag will be used.
-This way, message mode will do the Right Thing (TM) with
-signed/encrypted multipart messages.
-
-Since signing and especially encryption often is used when sensitive
-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 @kbd{C-u C-c RET 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.
-
address@hidden Neither @acronym{PGP/MIME} nor @acronym{S/MIME} encrypt/signs
-RFC822 headers. They only operate on the @acronym{MIME} object. Keep this
-in mind before sending mail with a sensitive Subject line.
-
-By default, when encrypting a message, Gnus will use the
-``signencrypt'' mode, which means the message is both signed and
-encrypted. If you would like to disable this for a particular
-message, give the @code{mml-secure-message-encrypt-*} command a prefix
-argument, e.g., @kbd{C-u C-c C-m c p}.
-
-Actually using the security commands above is not very difficult. At
-least not compared with making sure all involved programs talk with each
-other properly. Thus, we now describe what external libraries or
-programs are required to make things work, and some small general hints.
-
address@hidden Using S/MIME
address@hidden Using S/MIME
-
address@hidden This section assume you have a basic familiarity with
-modern cryptography, @acronym{S/MIME}, various PKCS standards, OpenSSL and
-so on.
-
-The @acronym{S/MIME} support in Message (and @acronym{MML}) require
-OpenSSL. OpenSSL performs the actual @acronym{S/MIME} sign/encrypt
-operations. OpenSSL can be found at @uref{http://www.openssl.org/}.
-OpenSSL 0.9.6 and later should work. Version 0.9.5a cannot extract mail
-addresses from certificates, and it insert a spurious CR character into
address@hidden separators so you may wish to avoid it if you would like
-to avoid being regarded as someone who send strange mail. (Although by
-sending @acronym{S/MIME} messages you've probably already lost that
-contest.)
-
-To be able to send encrypted mail, a personal certificate is not
-required. Message (@acronym{MML}) need a certificate for the person to whom
you
-wish to communicate with though. You're asked for this when you type
address@hidden 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 @acronym{PEM} format.
-If you chose DNS, you're asked for the domain name where the
-certificate is stored, the default is a good guess. To my belief,
-Message (@acronym{MML}) is the first mail agent in the world to support
-retrieving @acronym{S/MIME} certificates from DNS, so you're not
-likely to find very many certificates out there. At least there
-should be one, stored at the domain @code{simon.josefsson.org}. LDAP
-is a more popular method of distributing certificates, support for it
-is planned. (Meanwhile, you can use @code{ldapsearch} from the
-command line to retrieve a certificate into a file and use it.)
-
-As for signing messages, OpenSSL can't perform signing operations
-without some kind of configuration. Especially, you need to tell it
-where your private key and your certificate is stored. @acronym{MML}
-uses an Emacs interface to OpenSSL, aptly named @code{smime.el}, and it
-contain a @code{custom} group used for this configuration. So, try
address@hidden customize-group RET smime RET} and look around.
-
-Currently there is no support for talking to a CA (or RA) to create
-your own certificate. None is planned either. You need to do this
-manually with OpenSSL or using some other program. I used Netscape
-and got a free @acronym{S/MIME} certificate from one of the big CA's on the
-net. Netscape is able to export your private key and certificate in
-PKCS #12 format. Use OpenSSL to convert this into a plain X.509
-certificate in PEM format as follows.
-
address@hidden
-$ openssl pkcs12 -in ns.p12 -clcerts -nodes > key+cert.pem
address@hidden example
-
-The @file{key+cert.pem} file should be pointed to from the
address@hidden variable. You should now be able to send signed mail.
-
address@hidden Your private key is now stored unencrypted in the file,
-so take care in handling it. Storing encrypted keys on the disk are
-supported, and Gnus will ask you for a passphrase before invoking
-OpenSSL. Read the OpenSSL documentation for how to achieve this. If
-you use unencrypted keys (e.g., if they are on a secure storage, or if
-you are on a secure single user machine) simply press @code{RET} at
-the passphrase prompt.
-
address@hidden Using PGP/MIME
address@hidden Using PGP/MIME
-
address@hidden/MIME} requires an external OpenPGP implementation, such
-as @uref{http://www.gnupg.org/, GNU Privacy Guard}. Pre-OpenPGP
-implementations such as PGP 2.x and PGP 5.x are also supported. One
-Emacs interface to the PGP implementations, PGG (@pxref{Top, ,PGG,
-pgg, PGG Manual}), is included, but Mailcrypt and Florian Weimer's
address@hidden are also supported. @xref{PGP Compatibility}.
-
address@hidden gpg-agent
-Message internally calls GnuPG (the @command{gpg} command) to perform
-data encryption, and in certain cases (decrypting or signing for
-example), @command{gpg} requires user's passphrase. Currently the
-recommended way to supply your passphrase to @command{gpg} is to use the
address@hidden program.
-
-To use @command{gpg-agent} in Emacs, you need to run the following
-command from the shell before starting Emacs.
-
address@hidden
-eval `gpg-agent --daemon`
address@hidden example
-
-This will invoke @command{gpg-agent} and set the environment variable
address@hidden to allow @command{gpg} to communicate with it.
-It might be good idea to put this command in your @file{.xsession} or
address@hidden @xref{Invoking GPG-AGENT, , , gnupg, Using the
-GNU Privacy Guard}.
-
-Once your @command{gpg-agent} is set up, it will ask you for a
-passphrase as needed for @command{gpg}. Under the X Window System,
-you will see a new passphrase input dialog appear. The dialog is
-provided by PIN Entry (the @command{pinentry} command), and as of
-version 0.7.2, @command{pinentry} cannot cooperate with Emacs on a
-single tty. So, if you are using a text console, you may need to put
-a passphrase into gpg-agent's cache beforehand. The following command
-does the trick.
-
address@hidden
-gpg --use-agent --sign < /dev/null > /dev/null
address@hidden example
-
-The Lisp variable @code{pgg-gpg-use-agent} controls whether to use
address@hidden See also @xref{Caching passphrase, , , pgg, The
-PGG Manual}.
-
-
address@hidden PGP Compatibility
address@hidden Compatibility with older implementations
-
address@hidden gpg-temp-directory
-Note, if you are using the @code{gpg.el} you must make sure that the
-directory specified by @code{gpg-temp-directory} have permissions
-0700.
-
-Creating your own key is described in detail in the documentation of
-your PGP implementation, so we refer to it.
-
-If you have imported your old PGP 2.x key into GnuPG, and want to send
-signed and encrypted messages to your fellow PGP 2.x users, you'll
-discover that the receiver cannot understand what you send. One
-solution is to use PGP 2.x instead (i.e., if you use @code{pgg}, set
address@hidden to @code{pgp}). If you do want to use
-GnuPG, you can use a compatibility script called @code{gpg-2comp}
-available from
address@hidden://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/}. You
-could also convince your fellow PGP 2.x users to convert to GnuPG.
address@hidden mml-signencrypt-style-alist
-As a final workaround, you can make the sign and encryption work in
-two steps; separately sign, then encrypt a message. If you would like
-to change this behavior you can customize the
address@hidden variable. For example:
-
address@hidden
-(setq mml-signencrypt-style-alist '(("smime" separate)
- ("pgp" separate)
- ("pgpauto" separate)
- ("pgpmime" separate)))
address@hidden lisp
-
-This causes to sign and encrypt in two passes, thus generating a
-message that can be understood by PGP version 2.
-
-(Refer to @uref{http://www.gnupg.org/gph/en/pgp2x.html} for more
-information about the problem.)
-
address@hidden Various Commands
address@hidden Various Commands
-
address@hidden @kbd
-
address@hidden C-c C-r
address@hidden C-c C-r
address@hidden message-caesar-buffer-body
-Caesar rotate (aka. rot13) the current message
-(@code{message-caesar-buffer-body}). If narrowing is in effect, just
-rotate the visible portion of the buffer. A numerical prefix says how
-many places to rotate the text. The default is 13.
-
address@hidden C-c C-e
address@hidden C-c C-e
address@hidden message-elide-region
address@hidden message-elide-ellipsis
-Elide the text between point and mark (@code{message-elide-region}).
-The text is killed and replaced with the contents of the variable
address@hidden The default value is to use an ellipsis
-(@samp{[...]}).
-
address@hidden C-c C-z
address@hidden C-c C-z
address@hidden message-kill-to-signature
-Kill all the text up to the signature, or if that's missing, up to the
-end of the message (@code{message-kill-to-signature}).
-
address@hidden C-c C-v
address@hidden C-c C-v
address@hidden message-delete-not-region
-Delete all text in the body of the message that is outside the region
-(@code{message-delete-not-region}).
-
address@hidden M-RET
address@hidden M-RET
address@hidden message-newline-and-reformat
-Insert four newlines, and then reformat if inside quoted text.
-
-Here's an example:
-
address@hidden
-> This is some quoted text. And here's more quoted text.
address@hidden example
-
-If point is before @samp{And} and you press @kbd{M-RET}, you'll get:
-
address@hidden
-> This is some quoted text.
-
-*
-
-> And here's more quoted text.
address@hidden example
-
address@hidden says where point will be placed.
-
address@hidden C-c M-r
address@hidden C-c M-r
address@hidden message-rename-buffer
-Rename the buffer (@code{message-rename-buffer}). If given a prefix,
-prompt for a new buffer name.
-
address@hidden TAB
address@hidden TAB
address@hidden message-tab
address@hidden message-tab-body-function
-If @code{message-tab-body-function} is address@hidden, execute the
-function it specifies. Otherwise use the function bound to @kbd{TAB} in
address@hidden or @code{global-map}.
-
address@hidden table
-
-
address@hidden Sending
address@hidden Sending
-
address@hidden @kbd
address@hidden C-c C-c
address@hidden C-c C-c
address@hidden message-send-and-exit
-Send the message and bury the current buffer
-(@code{message-send-and-exit}).
-
address@hidden C-c C-s
address@hidden C-c C-s
address@hidden message-send
-Send the message (@code{message-send}).
-
address@hidden C-c C-d
address@hidden C-c C-d
address@hidden message-dont-send
-Bury the message buffer and exit (@code{message-dont-send}).
-
address@hidden C-c C-k
address@hidden C-c C-k
address@hidden message-kill-buffer
-Kill the message buffer and exit (@code{message-kill-buffer}).
-
address@hidden table
-
-
-
address@hidden Mail Aliases
address@hidden Mail Aliases
address@hidden mail aliases
address@hidden aliases
-
address@hidden message-mail-alias-type
-The @code{message-mail-alias-type} variable controls what type of mail
-alias expansion to use. Currently only one form is supported---Message
-uses @code{mailabbrev} to handle mail aliases. If this variable is
address@hidden, no mail alias expansion will be performed.
-
address@hidden works by parsing the @file{/etc/mailrc} and
address@hidden/.mailrc} files. These files look like:
-
address@hidden
-alias lmi "Lars Magne Ingebrigtsen <larsi@@ifi.uio.no>"
-alias ding "ding@@ifi.uio.no (ding mailing list)"
address@hidden example
-
-After adding lines like this to your @file{~/.mailrc} file, you should
-be able to just write @samp{lmi} in the @code{To} or @code{Cc} (and so
-on) headers and press @kbd{SPC} to expand the alias.
-
-No expansion will be performed upon sending of the message---all
-expansions have to be done explicitly.
-
-
address@hidden Spelling
address@hidden Spelling
address@hidden spelling
address@hidden ispell-message
-
-There are two popular ways to have Emacs spell-check your messages:
address@hidden and @code{flyspell}. @code{ispell} is the older and
-probably more popular package. You typically first write the message,
-and then run the entire thing through @code{ispell} and fix all the
-typos. To have this happen automatically when you send a message, put
-something like the following in your @file{.emacs} file:
-
address@hidden
-(add-hook 'message-send-hook 'ispell-message)
address@hidden lisp
-
address@hidden ispell-message-dictionary-alist
-If you're in the habit of writing in different languages, this can be
-controlled by the @code{ispell-message-dictionary-alist} variable:
-
address@hidden
-(setq ispell-message-dictionary-alist
- '(("^Newsgroups:.*\\bde\\." . "deutsch8")
- (".*" . "default")))
address@hidden lisp
-
address@hidden depends on having the external @samp{ispell} command
-installed.
-
-The other popular method is using @code{flyspell}. This package checks
-your spelling while you're writing, and marks any mis-spelled words in
-various ways.
-
-To use @code{flyspell}, put something like the following in your
address@hidden file:
-
address@hidden
-(defun my-message-setup-routine ()
- (flyspell-mode 1))
-(add-hook 'message-setup-hook 'my-message-setup-routine)
address@hidden lisp
-
address@hidden depends on having the external @samp{ispell} command
-installed.
-
-
address@hidden Variables
address@hidden Variables
-
address@hidden
-* Message Headers:: General message header stuff.
-* Mail Headers:: Customizing mail headers.
-* Mail Variables:: Other mail variables.
-* News Headers:: Customizing news headers.
-* News Variables:: Other news variables.
-* Insertion Variables:: Customizing how things are inserted.
-* Various Message Variables:: Other message variables.
-* Sending Variables:: Variables for sending.
-* Message Buffers:: How Message names its buffers.
-* Message Actions:: Actions to be performed when exiting.
address@hidden menu
-
-
address@hidden Message Headers
address@hidden Message Headers
-
-Message is quite aggressive on the message generation front. It has to
-be -- it's a combined news and mail agent. To be able to send combined
-messages, it has to generate all headers itself (instead of letting the
-mail/news system do it) to ensure that mail and news copies of messages
-look sufficiently similar.
-
address@hidden @code
-
address@hidden message-generate-headers-first
address@hidden message-generate-headers-first
-If @code{t}, generate all required headers before starting to
-compose the message. This can also be a list of headers to generate:
-
address@hidden
-(setq message-generate-headers-first
- '(References))
address@hidden lisp
-
address@hidden message-required-headers
-The variables @code{message-required-headers},
address@hidden and
address@hidden 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).
-
address@hidden message-draft-headers
address@hidden message-draft-headers
-When running Message from Gnus, the message buffers are associated
-with a draft group. @code{message-draft-headers} says which headers
-should be generated when a draft is written to the draft group.
-
address@hidden message-from-style
address@hidden message-from-style
-Specifies how @code{From} headers should look. There are four valid
-values:
-
address@hidden @code
address@hidden nil
-Just the address -- @samp{king@@grassland.com}.
-
address@hidden parens
address@hidden@@grassland.com (Elvis Parsley)}.
-
address@hidden angles
address@hidden Parsley <king@@grassland.com>}.
-
address@hidden default
-Look like @code{angles} if that doesn't require quoting, and
address@hidden if it does. If even @code{parens} requires quoting, use
address@hidden anyway.
-
address@hidden table
-
address@hidden message-deletable-headers
address@hidden message-deletable-headers
-Headers in this list that were previously generated by Message will be
-deleted before posting. Let's say you post an article. Then you decide
-to post it again to some other group, you naughty boy, so you jump back
-to the @code{*post-buf*} buffer, edit the @code{Newsgroups} line, and
-ship it off again. By default, this variable makes sure that the old
-generated @code{Message-ID} is deleted, and a new one generated. If
-this isn't done, the entire empire would probably crumble, anarchy would
-prevail, and cats would start walking on two legs and rule the world.
-Allegedly.
-
address@hidden message-default-headers
address@hidden message-default-headers
-This string is inserted at the end of the headers in all message
-buffers.
-
address@hidden message-subject-re-regexp
address@hidden message-subject-re-regexp
address@hidden Aw
address@hidden Sv
address@hidden Re
-Responses to messages have subjects that start with @samp{Re: }. This
-is @emph{not} an abbreviation of the English word ``response'', but is
-Latin, and means ``in response to''. Some illiterate nincompoops have
-failed to grasp this fact, and have ``internationalized'' their software
-to use abominations like @samp{Aw: } (``antwort'') or @samp{Sv: }
-(``svar'') instead, which is meaningless and evil. However, you may
-have to deal with users that use these evil tools, in which case you may
-set this variable to a regexp that matches these prefixes. Myself, I
-just throw away non-compliant mail.
-
-Here's an example of a value to deal with these headers when
-responding to a message:
-
address@hidden
-(setq message-subject-re-regexp
- (concat
- "^[ \t]*"
- "\\("
- "\\("
- "[Aa][Nn][Tt][Ww]\\.?\\|" ; antw
- "[Aa][Ww]\\|" ; aw
- "[Ff][Ww][Dd]?\\|" ; fwd
- "[Oo][Dd][Pp]\\|" ; odp
- "[Rr][Ee]\\|" ; re
- "[Rr][\311\351][Ff]\\.?\\|" ; ref
- "[Ss][Vv]" ; sv
- "\\)"
- "\\(\\[[0-9]*\\]\\)"
- "*:[ \t]*"
- "\\)"
- "*[ \t]*"
- ))
address@hidden lisp
-
address@hidden message-subject-trailing-was-query
address@hidden message-subject-trailing-was-query
address@hidden message-subject-trailing-was-ask-regexp
address@hidden message-subject-trailing-was-regexp
-Controls what to do with trailing @samp{(was: <old subject>)} in subject
-lines. If @code{nil}, leave the subject unchanged. If it is the symbol
address@hidden, query the user what to do. In this case, the subject is
-matched against @code{message-subject-trailing-was-ask-regexp}. If
address@hidden is @code{t}, always strip the
-trailing old subject. In this case,
address@hidden is used.
-
address@hidden message-alternative-emails
address@hidden message-alternative-emails
-Regexp matching alternative email addresses. The first address in the
-To, Cc or From headers of the original article matching this variable is
-used as the From field of outgoing messages, replacing the default From
-value.
-
-For example, if you have two secondary email addresses john@@home.net
-and john.doe@@work.com and want to use them in the From field when
-composing a reply to a message addressed to one of them, you could set
-this variable like this:
-
address@hidden
-(setq message-alternative-emails
- (regexp-opt '("john@@home.net" "john.doe@@work.com")))
address@hidden lisp
-
-This variable has precedence over posting styles and anything that runs
-off @code{message-setup-hook}.
-
address@hidden message-allow-no-recipients
address@hidden message-allow-no-recipients
-Specifies what to do when there are no recipients other than
address@hidden or @code{Fcc}. If it is @code{always}, the posting is
-allowed. If it is @code{never}, the posting is not allowed. If it is
address@hidden (the default), you are prompted.
-
address@hidden message-hidden-headers
address@hidden message-hidden-headers
-A regexp, a list of regexps, or a list where the first element is
address@hidden and the rest are regexps. It says which headers to keep
-hidden when composing a message.
-
address@hidden
-(setq message-hidden-headers
- '(not "From" "Subject" "To" "Cc" "Newsgroups"))
address@hidden lisp
-
address@hidden message-header-synonyms
address@hidden message-header-synonyms
-A list of lists of header synonyms. E.g., if this list contains a
-member list with elements @code{Cc} and @code{To}, then
address@hidden will not insert a @code{To}
-header when the message is already @code{Cc}ed to the recipient.
-
address@hidden table
-
-
address@hidden Mail Headers
address@hidden Mail Headers
-
address@hidden @code
address@hidden message-required-mail-headers
address@hidden message-required-mail-headers
address@hidden Headers}, for the syntax of this variable. It is
address@hidden(From Subject Date (optional . In-Reply-To) Message-ID
-(optional . User-Agent))} by default.
-
address@hidden message-ignored-mail-headers
address@hidden message-ignored-mail-headers
-Regexp of headers to be removed before mailing. The default address@hidden
address@hidden:\\|^Resent-Fcc:\\|^Xref:\\|^X-Draft-From:\\|@*
-^X-Gnus-Agent-Meta-Information:}.
-
address@hidden message-default-mail-headers
address@hidden message-default-mail-headers
-This string is inserted at the end of the headers in all message
-buffers that are initialized as mail.
-
address@hidden table
-
-
address@hidden Mail Variables
address@hidden Mail Variables
-
address@hidden @code
address@hidden message-send-mail-function
address@hidden message-send-mail-function
address@hidden message-send-mail-with-sendmail
address@hidden message-send-mail-with-mh
address@hidden message-send-mail-with-qmail
address@hidden message-smtpmail-send-it
address@hidden smtpmail-send-it
address@hidden feedmail-send-it
-Function used to send the current buffer as mail. The default is
address@hidden Other valid values include
address@hidden, @code{message-send-mail-with-qmail},
address@hidden, @code{smtpmail-send-it} and
address@hidden
-
address@hidden message-mh-deletable-headers
address@hidden message-mh-deletable-headers
-Most versions of MH doesn't like being fed messages that contain the
-headers in this variable. If this variable is address@hidden (which is
-the default), these headers will be removed before mailing when sending
-messages via MH. Set it to @code{nil} if your MH can handle these
-headers.
-
address@hidden message-qmail-inject-program
address@hidden message-qmail-inject-program
address@hidden qmail
-Location of the qmail-inject program.
-
address@hidden message-qmail-inject-args
address@hidden message-qmail-inject-args
-Arguments passed to qmail-inject programs.
-This should be a list of strings, one string for each argument. It
-may also be a function.
-
-For e.g., if you wish to set the envelope sender address so that bounces
-go to the right place or to deal with listserv's usage of that address, you
-might set this variable to @code{'("-f" "you@@some.where")}.
-
address@hidden message-sendmail-f-is-evil
address@hidden message-sendmail-f-is-evil
address@hidden sendmail
address@hidden means don't add @samp{-f username} to the sendmail
-command line. Doing so would be even more evil than leaving it out.
-
address@hidden message-sendmail-envelope-from
address@hidden message-sendmail-envelope-from
-When @code{message-sendmail-f-is-evil} is @code{nil}, this specifies
-the address to use in the @acronym{SMTP} envelope. If it is
address@hidden, use @code{user-mail-address}. If it is the symbol
address@hidden, use the @samp{From} header of the message.
-
address@hidden message-mailer-swallows-blank-line
address@hidden message-mailer-swallows-blank-line
-Set this to address@hidden if the system's mailer runs the header and
-body together. (This problem exists on SunOS 4 when sendmail is run
-in remote mode.) The value should be an expression to test whether
-the problem will actually occur.
-
address@hidden message-send-mail-partially-limit
address@hidden message-send-mail-partially-limit
address@hidden split large message
-The limitation of messages sent as message/partial. The lower bound
-of message size in characters, beyond which the message should be sent
-in several parts. If it is @code{nil}, the size is unlimited.
-
address@hidden table
-
-
address@hidden News Headers
address@hidden News Headers
-
address@hidden message-required-news-headers
address@hidden a list of header symbols. These
-headers will either be automatically generated, or, if that's
-impossible, they will be prompted for. The following symbols are valid:
-
address@hidden @code
-
address@hidden From
address@hidden From
address@hidden user-full-name
address@hidden user-mail-address
-This required header will be filled out with the result of the
address@hidden function, which depends on the
address@hidden, @code{user-full-name},
address@hidden variables.
-
address@hidden Subject
address@hidden Subject
-This required header will be prompted for if not present already.
-
address@hidden Newsgroups
address@hidden Newsgroups
-This required header says which newsgroups the article is to be posted
-to. If it isn't present already, it will be prompted for.
-
address@hidden Organization
address@hidden organization
address@hidden message-user-organization
address@hidden message-user-organization-file
-This optional header will be filled out depending on the
address@hidden variable.
address@hidden will be used if this variable is
address@hidden This variable can also be a string (in which case this string
-will be used), or it can be a function (which will be called with no
-parameters and should return a string to be used).
-
address@hidden Lines
address@hidden Lines
-This optional header will be computed by Message.
-
address@hidden Message-ID
address@hidden Message-ID
address@hidden message-user-fqdn
address@hidden mail-host-address
address@hidden user-mail-address
address@hidden system-name
address@hidden Sun
address@hidden i-did-not-set--mail-host-address--so-tickle-me
-This required header will be generated by Message. A unique ID will be
-created based on the date, time, user name (for the local part) and the
-domain part. For the domain part, message will look (in this order) at
address@hidden, @code{system-name}, @code{mail-host-address}
-and @code{message-user-mail-address} (i.e. @code{user-mail-address})
-until a probably valid fully qualified domain name (FQDN) was found.
-
address@hidden User-Agent
address@hidden User-Agent
-This optional header will be filled out according to the
address@hidden local variable.
-
address@hidden In-Reply-To
-This optional header is filled out using the @code{Date} and @code{From}
-header of the article being replied to.
-
address@hidden Expires
address@hidden Expires
address@hidden message-expires
-This extremely optional header will be inserted according to the
address@hidden variable. It is highly deprecated and shouldn't
-be used unless you know what you're doing.
-
address@hidden Distribution
address@hidden Distribution
address@hidden message-distribution-function
-This optional header is filled out according to the
address@hidden variable. It is a deprecated and
-much misunderstood header.
-
address@hidden Path
address@hidden path
address@hidden message-user-path
-This extremely optional header should probably never be used.
-However, some @emph{very} old servers require that this header is
-present. @code{message-user-path} further controls how this
address@hidden header is to look. If it is @code{nil}, use the server name
-as the leaf node. If it is a string, use the string. If it is neither
-a string nor @code{nil}, use the user name only. However, it is highly
-unlikely that you should need to fiddle with this variable at all.
address@hidden table
-
address@hidden yow
address@hidden Mime-Version
-In addition, you can enter conses into this list. The @sc{car} of this cons
-should be a symbol. This symbol's name is the name of the header, and
-the @sc{cdr} can either be a string to be entered verbatim as the value of
-this header, or it can be a function to be called. This function should
-return a string to be inserted. For instance, if you want to insert
address@hidden: 1.0}, you should enter @code{(Mime-Version . "1.0")}
-into the list. If you want to insert a funny quote, you could enter
-something like @code{(X-Yow . yow)} into the list. The function
address@hidden will then be called without any arguments.
-
-If the list contains a cons where the @sc{car} of the cons is
address@hidden, the @sc{cdr} of this cons will only be inserted if it is
address@hidden
-
-If you want to delete an entry from this list, the following Lisp
-snippet might be useful. Adjust accordingly if you want to remove
-another element.
-
address@hidden
-(setq message-required-news-headers
- (delq 'Message-ID message-required-news-headers))
address@hidden lisp
-
-Other variables for customizing outgoing news articles:
-
address@hidden @code
-
address@hidden message-syntax-checks
address@hidden message-syntax-checks
-Controls what syntax checks should not be performed on outgoing posts.
-To disable checking of long signatures, for instance, add
-
address@hidden
-(signature . disabled)
address@hidden lisp
-
-to this list.
-
-Valid checks are:
-
address@hidden @code
address@hidden approved
address@hidden approved
-Check whether the article has an @code{Approved} header, which is
-something only moderators should include.
address@hidden continuation-headers
-Check whether there are continuation header lines that don't begin with
-whitespace.
address@hidden control-chars
-Check for invalid characters.
address@hidden empty
-Check whether the article is empty.
address@hidden existing-newsgroups
-Check whether the newsgroups mentioned in the @code{Newsgroups} and
address@hidden headers exist.
address@hidden from
-Check whether the @code{From} header seems nice.
address@hidden illegible-text
-Check whether there is any non-printable character in the body.
address@hidden invisible-text
-Check whether there is any invisible text in the buffer.
address@hidden long-header-lines
-Check for too long header lines.
address@hidden long-lines
address@hidden long lines
-Check for too long lines in the body.
address@hidden message-id
-Check whether the @code{Message-ID} looks syntactically ok.
address@hidden multiple-headers
-Check for the existence of multiple equal headers.
address@hidden new-text
-Check whether there is any new text in the messages.
address@hidden newsgroups
-Check whether the @code{Newsgroups} header exists and is not empty.
address@hidden quoting-style
-Check whether text follows last quoted portion.
address@hidden repeated-newsgroups
-Check whether the @code{Newsgroups} and @code{Followup-to} headers
-contains repeated group names.
address@hidden reply-to
-Check whether the @code{Reply-To} header looks ok.
address@hidden sender
address@hidden Sender
-Insert a new @code{Sender} header if the @code{From} header looks odd.
address@hidden sendsys
address@hidden sendsys
-Check for the existence of version and sendsys commands.
address@hidden shoot
-Check whether the domain part of the @code{Message-ID} header looks ok.
address@hidden shorten-followup-to
-Check whether to add a @code{Followup-to} header to shorten the number
-of groups to post to.
address@hidden signature
-Check the length of the signature.
address@hidden size
-Check for excessive size.
address@hidden subject
-Check whether the @code{Subject} header exists and is not empty.
address@hidden subject-cmsg
-Check the subject for commands.
address@hidden valid-newsgroups
-Check whether the @code{Newsgroups} and @code{Followup-to} headers
-are valid syntactically.
address@hidden table
-
-All these conditions are checked by default, except for @code{sender}
-for which the check is disabled by default if
address@hidden is address@hidden (@pxref{Canceling News}).
-
address@hidden message-ignored-news-headers
address@hidden message-ignored-news-headers
-Regexp of headers to be removed before posting. The default address@hidden
address@hidden:\\|^Xref:\\|^[BGF]cc:\\|^Resent-Fcc:\\|@*
-^X-Draft-From:\\|^X-Gnus-Agent-Meta-Information:}.
-
address@hidden message-default-news-headers
address@hidden message-default-news-headers
-This string is inserted at the end of the headers in all message
-buffers that are initialized as news.
-
address@hidden table
-
-
address@hidden News Variables
address@hidden News Variables
-
address@hidden @code
address@hidden message-send-news-function
address@hidden message-send-news-function
-Function used to send the current buffer as news. The default is
address@hidden
-
address@hidden message-post-method
address@hidden message-post-method
-Gnusish @dfn{select method} (see the Gnus manual for details) used for
-posting a prepared news message.
-
address@hidden table
-
-
address@hidden Insertion Variables
address@hidden Insertion Variables
-
address@hidden @code
address@hidden message-ignored-cited-headers
address@hidden message-ignored-cited-headers
-All headers that match this regexp will be removed from yanked
-messages. The default is @samp{.}, which means that all headers will be
-removed.
-
address@hidden message-cite-prefix-regexp
address@hidden message-cite-prefix-regexp
-Regexp matching the longest possible citation prefix on a line.
-
address@hidden message-citation-line-function
address@hidden message-citation-line-function
address@hidden attribution line
-Function called to insert the citation line. The default is
address@hidden, which will lead to citation lines
-that look like:
-
address@hidden
-Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
address@hidden example
-
-Point will be at the beginning of the body of the message when this
-function is called.
-
-Note that Gnus provides a feature where clicking on `writes:' hides the
-cited text. If you change the citation line too much, readers of your
-messages will have to adjust their Gnus, too. See the variable
address@hidden @xref{Article Highlighting, ,
-Article Highlighting, gnus, The Gnus Manual}, for details.
-
address@hidden message-yank-prefix
address@hidden message-yank-prefix
address@hidden yanking
address@hidden 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 line you yank will have
address@hidden prepended to it (except for quoted and
-empty lines which uses @code{message-yank-cited-prefix}). The default
-is @samp{> }.
-
address@hidden message-yank-cited-prefix
address@hidden message-yank-cited-prefix
address@hidden yanking
address@hidden cited
address@hidden quoting
-When yanking text from an article which contains no text or already
-cited text, each line will be prefixed with the contents of this
-variable. The default is @samp{>}. See also
address@hidden
-
address@hidden message-indentation-spaces
address@hidden message-indentation-spaces
-Number of spaces to indent yanked messages.
-
address@hidden message-cite-function
address@hidden message-cite-function
address@hidden message-cite-original
address@hidden sc-cite-original
address@hidden message-cite-original-without-signature
address@hidden Supercite
-Function for citing an original message. The default is
address@hidden, which simply inserts the original message
-and prepends @samp{> } to each line.
address@hidden does the same, but elides
-the signature. You can also set it to @code{sc-cite-original} to use
-Supercite.
-
address@hidden message-indent-citation-function
address@hidden message-indent-citation-function
-Function for modifying a citation just inserted in the mail buffer.
-This can also be a list of functions. Each function can find the
-citation between @code{(point)} and @code{(mark t)}. And each function
-should leave point and mark around the citation text as modified.
-
address@hidden message-mark-insert-begin
address@hidden message-mark-insert-begin
-String to mark the beginning of some inserted text.
-
address@hidden message-mark-insert-end
address@hidden message-mark-insert-end
-String to mark the end of some inserted text.
-
address@hidden message-signature
address@hidden message-signature
-String to be inserted at the end of the message buffer. If @code{t}
-(which is the default), the @code{message-signature-file} file will be
-inserted instead. If a function, the result from the function will be
-used instead. If a form, the result from the form will be used instead.
-If this variable is @code{nil}, no signature will be inserted at all.
-
address@hidden message-signature-file
address@hidden message-signature-file
-File containing the signature to be inserted at the end of the buffer.
-The default is @file{~/.signature}.
-
address@hidden message-signature-insert-empty-line
address@hidden message-signature-insert-empty-line
-If @code{t} (the default value) an empty line is inserted before the
-signature separator.
-
address@hidden table
-
-Note that RFC1036bis says that a signature should be preceded by the three
-characters @samp{-- } on a line by themselves. This is to make it
-easier for the recipient to automatically recognize and process the
-signature. So don't remove those characters, even though you might feel
-that they ruin your beautiful design, like, totally.
-
-Also note that no signature should be more than four lines long.
-Including @acronym{ASCII} graphics is an efficient way to get
-everybody to believe that you are silly and have nothing important to
-say.
-
-
address@hidden Various Message Variables
address@hidden Various Message Variables
-
address@hidden @code
address@hidden message-default-charset
address@hidden message-default-charset
address@hidden charset
-Symbol naming a @acronym{MIME} charset. address@hidden characters
-in messages are assumed to be encoded using this charset. The default
-is @code{iso-8859-1} on address@hidden Emacsen; otherwise @code{nil},
-which means ask the user. (This variable is used only on address@hidden
-Emacsen.) @xref{Charset Translation, , Charset Translation, emacs-mime,
-Emacs MIME Manual}, for details on the @address@hidden
-translation process.
-
address@hidden message-signature-separator
address@hidden message-signature-separator
-Regexp matching the signature separator. It is @samp{^-- *$} by
-default.
-
address@hidden mail-header-separator
address@hidden mail-header-separator
-String used to separate the headers from the body. It is @samp{--text
-follows this line--} by default.
-
address@hidden message-directory
address@hidden message-directory
-Directory used by many mailey things. The default is @file{~/Mail/}.
-All other mail file variables are derived from @code{message-directory}.
-
address@hidden message-auto-save-directory
address@hidden message-auto-save-directory
-Directory where Message auto-saves buffers if Gnus isn't running. If
address@hidden, Message won't auto-save. The default is @file{~/Mail/drafts/}.
-
address@hidden message-signature-setup-hook
address@hidden message-signature-setup-hook
-Hook run when initializing the message buffer. It is run after the
-headers have been inserted but before the signature has been inserted.
-
address@hidden message-setup-hook
address@hidden message-setup-hook
-Hook run as the last thing when the message buffer has been initialized,
-but before yanked text is inserted.
-
address@hidden message-header-setup-hook
address@hidden message-header-setup-hook
-Hook called narrowed to the headers after initializing the headers.
-
-For instance, if you're running Gnus and wish to insert a
address@hidden header in all your news articles and all messages
-you send to mailing lists, you could do something like the following:
-
address@hidden
-(defun my-message-header-setup-hook ()
- (let ((group (or gnus-newsgroup-name "")))
- (when (or (message-fetch-field "newsgroups")
- (gnus-group-find-parameter group 'to-address)
- (gnus-group-find-parameter group 'to-list))
- (insert "Mail-Copies-To: never\n"))))
-
-(add-hook 'message-header-setup-hook
- 'my-message-header-setup-hook)
address@hidden lisp
-
address@hidden message-send-hook
address@hidden message-send-hook
-Hook run before sending messages.
-
-If you want to add certain headers before sending, you can use the
address@hidden function in this hook. For instance:
address@hidden message-add-header
-
address@hidden
-(add-hook 'message-send-hook 'my-message-add-content)
-(defun my-message-add-content ()
- (message-add-header "X-In-No-Sense: Nonsense")
- (message-add-header "X-Whatever: no"))
address@hidden lisp
-
-This function won't add the header if the header is already present.
-
address@hidden message-send-mail-hook
address@hidden message-send-mail-hook
-Hook run before sending mail messages. This hook is run very late --
-just before the message is actually sent as mail.
-
address@hidden message-send-news-hook
address@hidden message-send-news-hook
-Hook run before sending news messages. This hook is run very late --
-just before the message is actually sent as news.
-
address@hidden message-sent-hook
address@hidden message-sent-hook
-Hook run after sending messages.
-
address@hidden message-cancel-hook
address@hidden message-cancel-hook
-Hook run when canceling news articles.
-
address@hidden message-mode-syntax-table
address@hidden message-mode-syntax-table
-Syntax table used in message mode buffers.
-
address@hidden message-strip-special-text-properties
address@hidden message-strip-special-text-properties
-Emacs has a number of special text properties which can break message
-composing in various ways. If this option is set, message will strip
-these properties from the message composition buffer. However, some
-packages requires these properties to be present in order to work. If
-you use one of these packages, turn this option off, and hope the
-message composition doesn't break too bad.
-
address@hidden message-send-method-alist
address@hidden message-send-method-alist
address@hidden message-mail-p
address@hidden message-news-p
address@hidden message-send-via-mail
address@hidden message-send-via-news
-Alist of ways to send outgoing messages. Each element has the form:
-
address@hidden
-(@var{type} @var{predicate} @var{function})
address@hidden lisp
-
address@hidden @var
address@hidden type
-A symbol that names the method.
-
address@hidden predicate
-A function called without any parameters to determine whether the
-message is a message of type @var{type}. The function will be called in
-the buffer where the message is.
-
address@hidden function
-A function to be called if @var{predicate} returns address@hidden
address@hidden is called with one parameter -- the prefix.
address@hidden table
-
-The default is:
-
address@hidden
-((news message-news-p message-send-via-news)
- (mail message-mail-p message-send-via-mail))
address@hidden lisp
-
-The @code{message-news-p} function returns address@hidden if the message
-looks like news, and the @code{message-send-via-news} function sends the
-message according to the @code{message-send-news-function} variable
-(@pxref{News Variables}). The @code{message-mail-p} function returns
address@hidden if the message looks like mail, and the
address@hidden function sends the message according to the
address@hidden variable (@pxref{Mail Variables}).
-
-All the elements in this alist will be tried in order, so a message
-containing both a valid @samp{Newsgroups} header and a valid @samp{To}
-header, for example, will be sent as news, and then as mail.
address@hidden table
-
-
-
address@hidden Sending Variables
address@hidden Sending Variables
-
address@hidden @code
-
address@hidden message-fcc-handler-function
address@hidden message-fcc-handler-function
-A function called to save outgoing articles. This function will be
-called with the name of the file to store the article in. The default
-function is @code{message-output} which saves in Unix mailbox format.
-
address@hidden message-courtesy-message
address@hidden message-courtesy-message
-When sending combined messages, this string is inserted at the start of
-the mailed copy. If the string contains the format spec @samp{%s}, the
-newsgroups the article has been posted to will be inserted there. If
-this variable is @code{nil}, no such courtesy message will be added.
-The default value is @samp{"The following message is a courtesy copy of
-an article\\nthat has been posted to %s as well.\\n\\n"}.
-
address@hidden message-fcc-externalize-attachments
address@hidden message-fcc-externalize-attachments
-If @code{nil}, attach files as normal parts in Fcc copies; if it is
address@hidden, attach local files as external parts.
-
address@hidden message-interactive
address@hidden message-interactive
-If address@hidden wait for and display errors when sending a message;
-if @code{nil} let the mailer mail back a message to report errors.
-
address@hidden table
-
-
address@hidden Message Buffers
address@hidden Message Buffers
-
-Message will generate new buffers with unique buffer names when you
-request a message buffer. When you send the message, the buffer isn't
-normally killed off. Its name is changed and a certain number of old
-message buffers are kept alive.
-
address@hidden @code
address@hidden message-generate-new-buffers
address@hidden message-generate-new-buffers
-Controls whether to create a new message buffer to compose a message.
-Valid values include:
-
address@hidden @code
address@hidden nil
-Generate the buffer name in the Message way (e.g., *mail*, *news*, *mail
-to whom*, *news on group*, etc.) and continue editing in the existing
-buffer of that name. If there is no such buffer, it will be newly
-created.
-
address@hidden unique
address@hidden t
-Create the new buffer with the name generated in the Message way. This
-is the default.
-
address@hidden unsent
-Similar to @code{unique} but the buffer name begins with "*unsent ".
-
address@hidden standard
-Similar to @code{nil} but the buffer name is simpler like *mail
-message*.
address@hidden table
address@hidden @var
address@hidden function
-If this is a function, call that function with three parameters: The
-type, the To address and the group name (any of these may be
address@hidden). The function should return the new buffer name.
address@hidden table
-
-The default value is @code{unique}.
-
address@hidden message-max-buffers
address@hidden message-max-buffers
-This variable says how many old message buffers to keep. If there are
-more message buffers than this, the oldest buffer will be killed. The
-default is 10. If this variable is @code{nil}, no old message buffers
-will ever be killed.
-
address@hidden message-send-rename-function
address@hidden message-send-rename-function
-After sending a message, the buffer is renamed from, for instance,
address@hidden to Lars*} to @samp{*sent reply to Lars*}. If you don't
-like this, set this variable to a function that renames the buffer in a
-manner you like. If you don't want to rename the buffer at all, you can
-say:
-
address@hidden
-(setq message-send-rename-function 'ignore)
address@hidden lisp
-
address@hidden message-kill-buffer-on-exit
address@hidden message-kill-buffer-on-exit
-If address@hidden, kill the buffer immediately on exit.
-
address@hidden table
-
-
address@hidden Message Actions
address@hidden Message Actions
-
-When Message is being used from a news/mail reader, the reader is likely
-to want to perform some task after the message has been sent. Perhaps
-return to the previous window configuration or mark an article as
-replied.
-
address@hidden message-kill-actions
address@hidden message-postpone-actions
address@hidden message-exit-actions
address@hidden message-send-actions
-The user may exit from the message buffer in various ways. The most
-common is @kbd{C-c C-c}, which sends the message and exits. Other
-possibilities are @kbd{C-c C-s} which just sends the message, @kbd{C-c
-C-d} which postpones the message editing and buries the message buffer,
-and @kbd{C-c C-k} which kills the message buffer. Each of these actions
-have lists associated with them that contains actions to be executed:
address@hidden, @code{message-exit-actions},
address@hidden, and @code{message-kill-actions}.
-
-Message provides a function to interface with these lists:
address@hidden The first parameter is the action to be
-added, and the rest of the arguments are which lists to add this action
-to. Here's an example from Gnus:
-
address@hidden
- (message-add-action
- `(set-window-configuration ,(current-window-configuration))
- 'exit 'postpone 'kill)
address@hidden lisp
-
-This restores the Gnus window configuration when the message buffer is
-killed, postponed or exited.
-
-An @dfn{action} can be either: a normal function, or a list where the
address@hidden is a function and the @sc{cdr} is the list of arguments, or
-a form to be @code{eval}ed.
-
-
address@hidden Compatibility
address@hidden Compatibility
address@hidden compatibility
-
-Message uses virtually only its own variables---older @code{mail-}
-variables aren't consulted. To force Message to take those variables
-into account, you can put the following in your @file{.emacs} file:
-
address@hidden
-(require 'messcompat)
address@hidden lisp
-
-This will initialize many Message variables from the values in the
-corresponding mail variables.
-
-
address@hidden Appendices
address@hidden Appendices
-
address@hidden
-* Responses:: Standard rules for determining where responses go.
address@hidden menu
-
-
address@hidden Responses
address@hidden Responses
-
-To determine where a message is to go, the following algorithm is used
-by default.
-
address@hidden @dfn
address@hidden reply
-A @dfn{reply} is when you want to respond @emph{just} to the person who
-sent the message via mail. There will only be one recipient. To
-determine who the recipient will be, the following headers are
-consulted, in turn:
-
address@hidden @code
address@hidden Reply-To
-
address@hidden From
address@hidden table
-
-
address@hidden wide reply
-A @dfn{wide reply} is a mail response that includes @emph{all} entities
-mentioned in the message you are responded to. All mailboxes from the
-following headers will be concatenated to form the outgoing
address@hidden/@code{Cc} headers:
-
address@hidden @code
address@hidden From
-(unless there's a @code{Reply-To}, in which case that is used instead).
-
address@hidden Cc
-
address@hidden To
address@hidden table
-
-If a @code{Mail-Copies-To} header is present, it will also be included
-in the list of mailboxes. If this header is @samp{never}, that means
-that the @code{From} (or @code{Reply-To}) mailbox will be suppressed.
-
-
address@hidden followup
-A @dfn{followup} is a response sent via news. The following headers
-(listed in order of precedence) determine where the response is to be
-sent:
-
address@hidden @code
-
address@hidden Followup-To
-
address@hidden Newsgroups
-
address@hidden table
-
-If a @code{Mail-Copies-To} header is present, it will be used as the
-basis of the new @code{Cc} header, except if this header is
address@hidden
-
address@hidden table
-
-
address@hidden GNU Free Documentation License
address@hidden GNU Free Documentation License
address@hidden doclicense.texi
-
address@hidden Index
address@hidden Index
address@hidden cp
-
address@hidden Key Index
address@hidden Key Index
address@hidden ky
-
address@hidden
address@hidden
address@hidden
-
address@hidden End:
-
address@hidden
- arch-tag: 16ab76af-a281-4e34-aed6-5624569f7601
address@hidden ignore
- [Emacs-diffs] Changes to message.texi,
Glenn Morris <=