@code{message-wide-reply-to-function}. It is used in the same way as
@code{message-reply-to-function} (@pxref{Reply}).
-@findex message-dont-reply-to-names
+@vindex 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.
+@vindex message-wide-reply-confirm-recipients
+If @code{message-wide-reply-confirm-recipients} is non-@code{nil} you
+will be asked to confirm that you want to reply to multiple
+recipients. The default is @code{nil}.
@node Followup
@section Followup
The @code{message-cancel-news} command cancels the article in the
current buffer.
+@vindex 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.}.
+
@node Superseding
@section Superseding
included as inline @sc{mime} RFC822 parts. If it's @code{nil}, forwarded
messages will just be copied inline to the new message, like previous,
non @sc{mime}-savvy versions of gnus would do.
+
+@item message-forward-before-signature
+@vindex message-forward-before-signature
+If non-@code{nil}, put forwarded message before signature, else after.
+
@end table
if the poster is already subscribed to the list.
@item
+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.
+
+@item
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
'(gnus-find-subscribed-addresses))
@end lisp
+@vindex message-subscribed-address-file
@item message-subscribed-address-file
You might be one organised human freak and have a list of addresses of
all subscribed mailing lists in a separate file! Then you can just
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 header. If there is one, the header is left alone.
-If not 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:
-
+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:
+
+@kindex C-c C-f C-a
+@findex message-gen-unsubscribed-mft
+@kindex C-c C-f C-m
+@findex message-goto-mail-followup-to
Hm. ``So'', you ask, ``what if I send an email to a list I am not
-subscribed to?'' Well, the kind folks at Gnus Towers are working on a
-database of all known mailing list addresses that can be used for this
-purpose. Till then, you could, like, insert a MFT header manually,
-with the help of @kbd{C-c C-f C-m} !!
+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
+@code{message-gen-unsubscribed-mft} 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.
@c @node Honoring an MFT post
@subsection Honoring an MFT post
@code{message-use-mail-followup-to}. This variable can be one of:
@table @code
-@item t
+@item use
Always honor MFTs. The To: and Cc: headers in your followup will be
- derived from the MFT header of the original post.
+ derived from the MFT header of the original post. This is the default.
@item nil
Always dishonor MFTs (just ignore the darned thing)
@item ask
-Gnus will prompt you for an action. This is the default.
+Gnus will prompt you for an action.
@end table
Digitally encrypt current message using @sc{pgp/mime}.
+@item C-c C-m C-n
+@kindex C-c C-m C-n
+@findex mml-unsecure-message
+Remove security related MML tags from message.
+
@end table
These commands do not immediately sign or encrypt the message, they
@item C-c C-e
@kindex C-c C-e
@findex message-elide-region
+@vindex 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
@code{message-elide-ellipsis}. The default value is to use an ellipsis
or @code{Newsgroups} header of the article you're replying to
(@code{message-insert-newsgroups}).
+@item C-c C-o
+@kindex C-c C-o
+@findex message-sort-headers
+@vindex message-header-format-alist
+Sort headers according to @code{message-header-format-alist}
+(@code{message-sort-headers}).
+
@item C-c M-r
@kindex C-c M-r
@findex message-rename-buffer
messages via MH. Set it to @code{nil} if your MH can handle these
headers.
+@item message-qmail-inject-program
+@vindex message-qmail-inject-program
+@cindex qmail
+Location of the qmail-inject program.
+
+@item message-qmail-inject-args
+@vindex 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")}.
+
+@item message-sendmail-f-is-evil
+@vindex message-sendmail-f-is-evil
+@cindex sendmail
+Non-@code{nil} means don't add @samp{-f username} to the sendmail
+command line. Doing so would be even more evil than leaving it out.
+
+@item message-mailer-swallows-blank-line
+@vindex message-mailer-swallows-blank-line
+Set this to non-@code{nil} 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.
+
@item message-send-mail-partially-limit
@vindex message-send-mail-partially-limit
The limitation of messages sent as message/partial.
@item Organization
@cindex organization
+@vindex message-user-organization
+@vindex message-user-organization-file
This optional header will be filled out depending on the
@code{message-user-organization} variable.
@code{message-user-organization-file} will be used if this variable is
@item Expires
@cindex Expires
+@vindex message-expires
This extremely optional header will be inserted according to the
@code{message-expires} variable. It is highly deprecated and shouldn't
be used unless you know what you're doing.
@item Distribution
@cindex Distribution
+@vindex message-distribution-function
This optional header is filled out according to the
@code{message-distribution-function} variable. It is a deprecated and
much misunderstood header.
@item Path
@cindex path
+@vindex 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
@vindex message-directory
Directory used by many mailey things. The default is @file{~/Mail/}.
+@item message-auto-save-directory
+@vindex message-auto-save-directory
+Directory where Message auto-saves buffers if Gnus isn't running. If
+@code{nil}, Message won't auto-save. The default is @file{~/Mail/drafts/}.
+
@item message-signature-setup-hook
@vindex message-signature-setup-hook
Hook run when initializing the message buffer. It is run after the
@vindex message-sent-hook
Hook run after sending messages.
+@item message-cancel-hook
+@vindex message-cancel-hook
+Hook run when cancelling news articles.
+
@item message-mode-syntax-table
@vindex message-mode-syntax-table
Syntax table used in message mode buffers.
+@item message-strip-special-text-properties
+@vindex 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.
+
@item message-send-method-alist
@vindex message-send-method-alist
an article\\nthat has been posted to %s as well.\\n\\n"}.
@item message-fcc-externalize-attachments
-@vindex message-gcc-externalize-attachments
+@vindex message-fcc-externalize-attachments
If @code{nil}, attach files as normal parts in Fcc copies; if it is
non-@code{nil}, attach local files as external parts.
+@item message-interactive
+@vindex message-interactive
+If non-@code{nil} wait for and display errors when sending a message;
+if @code{nil} let the mailer mail back a message to report errors.
+
@end table
projects / elisp / gnus.git- / blobdiff