automatically when you send the message. Others, such as the recipient
names, must be specified by you in order to send the message properly.
- Mail mode provides a few commands to help you edit some header fields,
-and some are preinitialized in the buffer automatically at times. You can
-insert and edit header fields using ordinary editing commands.
+ In the mail buffer, you can insert and edit header fields using
+ordinary editing commands. Mail mode provides a commands to help you
+edit some header fields, and some are preinitialized in the buffer
+automatically when appropriate.
The line in the buffer that says
message actually sent. The text used for the delimiter line is controlled
by the variable @code{mail-header-separator}.
-Here is an example of what the headers and text in the mail buffer
+ Here is an example of what the headers and text in the mail buffer
might look like.
@example
continuation lines: one or more lines starting with whitespace,
following the starting line of the field, are considered part of the
field. Here's an example of a @samp{To} field with a continuation
-line:@refill
+line:
@example
@group
using it. This is the usual way to send the message.
In a file-visiting buffer, sending the message does not clear the
-modified flag, because only saving the file should do that. As a
-result, you don't get a warning if you try to send the same message
-twice.
+modified flag, because only saving the file should do that. Also, you
+don't get a warning if you try to send the same message twice.
@c This is indexed in mule.texi, node "Recognize Coding".
@c @vindex sendmail-coding-system