Go to the previous, next section.
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 to ensure that mail and news copies of messages look sufficiently similar.
nil, generate all headers before starting to compose the message.
Fromheaders should look. There are four legal values:
anglesif that doesn't require quoting, and
parensif it does. If even
parensrequires quoting, use
*post-buf*buffer, edit the
Newsgroupsline, and ship it off again. By default, this variable makes sure that the old generated
Message-IDis 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.
(From Date Subject (optional . In-Reply-To) Message-ID Lines (optional . X-Mailer))by default.
message-send-mail-with-sendmail. If you prefer using MH instead, set this variable to
message-required-news-headers 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 legal:
message-make-fromfunction, which depends on the
message-user-organization-filewill be used if that variable is
mail-host-addressas the fully qualified domain name (FQDN) of the machine if that variable is define. If not, it will use
system-name, which doesn't report a FQDN on some machines -- notably Suns.
message-mailerlocal variable, unless there already is an
Fromheader of the article being replied.
message-expiresvariable. It is highly deprecated and shouldn't be used unless you know what you're doing.
message-distribution-functionvariable. It is a deprecated and much misunderstood header.
message-user-pathfurther controls how this
Pathheader is to look. If is is
nil, the the server name as the leaf node. If is is a string, use the string. If it is neither a string nor
nil, use the user name only. However, it is highly unlikely that you should need to fiddle with this variable at all.
In addition, you can enter conses into this list. The car of this cons
should be a symbol. This symbol's name is the name of the header, and
the 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
Mime-Version: 1.0, you should enter
(Mime-Version . "1.0")
into the list. If you want to insert a funny quote, you could enter
(X-Yow . yow) into the list. The function
yow will then be called without any arguments.
If the list contains a cons where the car of the cons is
optional, the cdr of this cons will only be inserted if it is
Other variables for customizing outgoing news articles:
nil, message will attempt to check the legality of the headers, as well as some other stuff, before posting. You can control the granularity of the check by adding or removing elements from this list. Legal elements are:
Senderheader if the
Fromheader looks odd.
Fromheader seems nice.
Approvedheader, which is something only moderators should include.
Followup-Toheaders are valid syntactially.
All these conditions are checked by default.
rmail-outputwhich saves in Unix mailbox format.
nil, no such courtesy message will be added.
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. It's name is changed and a certain number of old message buffers are kept alive.
nil, generate new buffers. The default is
t. 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
nil.) The function should return the new buffer name.
nil, no old message buffers will ever be killed.
(setq message-send-rename-function 'ignore)
nil, kill the buffer immediately on exit.
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.
The user may exit from the message buffer in various ways. The most
common is C-c C-c, which sends the message and exits. Other
possibilities are C-c C-s which just sends the message, C-c
C-d which postpones the message editing and buries the message buffer,
and C-c C-k which kills the message buffer. Each of these actions
have lists associated with them that contains actions to be executed:
Message provides a function to interface with these lists:
message-add-action. 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:
(message-add-action `(set-window-configuration ,(current-window-configuration)) 'exit 'postpone 'kill)
This restores the Gnus window configuration when the message buffer is killed, postponed or exited.
An action can be either a normal function; or a list where the
car is a function and the
cdr is the list of arguments; or
a form to be
Go to the previous, next section.