[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Af allows you to compose and send mail as well as read it. There are several different commands to send mail, each of which sends mail in a slightly different way.
Af composes messages in three stages. First you are prompted for any details needed for the message, such as the addresses to send it to. Then af starts an editor, so that you can edit the message. Finally, you are prompted for what to do with the message (its disposition).
8.1 Commands for Sending Mail The different commands to send mail. 8.2 Initial Details for Composing Mail The details af may ask for when sending mail. 8.3 Editing the Mail Message Details of editing your mail message. 8.4 Options After Editing the Message Your options after editing the message. 8.5 Composing MIME Mail. How to compose MIME messages. 8.6 Variables Related to Composing Mail Variables which affect composing messages. 8.7 Defining and Using Mail Aliases Convenient abbreviations for addresses.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are seven commands for sending mail in af. These commands are all similar in use, but conceptually different.
send-mail
). A numeric argument makes af
compose a MIME message. Alternatively, you can attach files or
compositions to the message later.
send-file
). You will
not normally edit the text of the message. A numeric argument makes af
prompt for the MIME Content-Type of the message to compose. If af
detects that the file name indicates some content type other than plain
text then it will default the Content-Type and prompt for the
information anyway.
reply-to-message
). This lets you
compose and send mail to whoever the current message is from.
group-reply-to-message
).
This lets you compose and send mail to whoever the message is from, and
all the addresses listed in the `To:' header. Copies are sent to
the addresses listed in the `Cc:' header.
forward-message
).
forward-message-as-attachment
). A numeric argument makes af
include the full headers of the message to attach. This is often useful
when sending reports of unsolicited commercial email to the sender's
postmaster.
forward-region-as-digest
). This is useful for
forwarding several messages to someone in a convenient format.
forward-tagset-as-digest
). This is useful for
forwarding several messages to someone in a convenient format.
bounce-message
).
You will not normally edit the text of the message.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Depending on how you are sending mail, and how you have configured af,
you will be prompted for several things when you begin composing a mail
message. Normally af will only prompt for `To:' and
`Subject:', and possibly `Content-Type:',
`Content-Disposition:', and `Content-Description:' if you give
send-file
an argument, but here are all the possible questions:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When you first edit a message you will normally see either a blank file, or the textual body parts of the original message with each line prefixed with `> '. You can then use your editor as usual to compose the text of the message. When you save the message, your `.signature' file will be appended to the message, separated by a line containing `-- '.
When you edit a message for the second time (or if you have configured af to do so), the headers of the message are inserted into the file you edit, separated by a blank line, and your signature will be visible at the end of the file. You can edit the headers with your editor, and af will process the changes when you exit the editor; reporting any problems to typeout. You can create headers by adding them into the header section of the file, or delete them by deleting them from the file.
You should be very careful when editing a message's headers. If you accidentally insert a blank line before the headers, then af will not find them when you exit the editor, and will therefore think that you have deleted them all. This can normally be fixed by editing the file again, and removing the offending text from the start of the file.
If a message is a multipart MIME message, then instead of using an editor to edit the message, the various body parts of the message will be displayed in compose mode. There you can add or delete body parts, or edit existing ones. See section 8.5.4 Non-Text Messages, for more details.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
When you finish editing a message and exit the editor, af will display a summary of the message's headers and prompt you with
Send, Edit, Attachments, Check spelling, List or Forget? |
It is a very good idea to check the headers that af displays, to make sure that you are sending the message to the people you think you are, that the subject is appropriate, and so on. Your options at this point are:
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Normally, electronic mail is composed in the `us-ascii' character set, which doesn't contain any accented or international characters. Af allows you to compose MIME messages in character sets other than `us-ascii', and to encode these messages so that they are not damaged in transit.
8.5.1 Internationalised Mail How to send internationalised mail. 8.5.2 Encoding Mail How to control encoding of messages. 8.5.3 International Headers Including international text in headers. 8.5.4 Non-Text Messages How to send non-text mail messages.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The default `us-ascii' character set contains only the characters used in American English. If you want to include international characters such as accents, Hebrew, Cyrillic or so on, you will need to make af compose messages in another character set, for example the `iso-8859-1' character set that covers Western European languages, or the `iso-8859-8' character set for Hebrew text.
The `Content-Type:' header defines how the message is to be treated. For text messages it is usually set to `text/plain; charset=us-ascii'. If you change the value to `text/plain; charset=iso-8859-1', then the message should be interpreted as containing characters in the `iso-8859-1' character set.
The default-charset
variable controls which character set you
compose mail messages in by default. For example, to compose messages
in the `iso-8859-1' character set, you would set the
default-charset
variable to `iso-8859-1'. Once you have
done this, any messages you compose will be marked as containing
characters from that character set. You can override this default by
editing the message headers.
The person who installed af at your site may have already configured it to compose messages in the correct character set. In this case you don't need to do anything to make af handle internationalised messages correctly.
Even if you compose messages in an international character set by default, af will still mark them as `us-ascii' if they don't contain any international characters. So you should rarely, if ever, need to change the character set of a message yourself.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Unfortunately, the international mail network is often unable to handle messages including international characters properly. To avoid this, af allows you to encode the message, converting any international characters into special sequences of ascii characters. Unfortunately, this means that the message will not be properly readable if the recipient doesn't have a MIME-capable mail reader. Alternatively, you can choose not to encode your message, and risk it being damaged in transit. Which choice is better is entirely dependent on your local situation.
The default-text-encoding
variable controls how international
messages should be encoded. The possible values are:
The person who installed af at your site may have already configured it to encode internationalised messages in the best way. In this case you don't need to do anything to make af encode internationalised messages correctly.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Af handles international characters in headers by encoding them in a special form, to avoid damage in transit. This is done automatically whenever af encounters an international character in a header.
Sometimes you will encounter comments like `(**iso-8859-8**)' in a
header containing international characters. If you are viewing the
header, this means that the header contains international characters in
a character set that isn't listed in the viewable-charsets
variable, and is a warning that af can't correctly display the
characters, what you see is a "best effort".
If you are editing the header, then such a comment means that the character set is not the one you are composing the message in. In this case the af will preserve the character set by assuming that any international characters after the comment contain characters in the specified character set. You can change this by adding another comment, such as `(**iso-8859-1**)' to force the character set back to your preference.
If you often need to type international characters into mail, the
command minibuffer-set-iso-keys
may be useful. This command
sets the allow-meta-bindings
variable (see section 21.6.1 Keymaps), and
then binds all the meta characters found in the `iso-8859-*'
character sets to insert themselves when typed in the minibuffer.
This is often useful when composing headers in languages other than
English.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are two ways to compose non-text messages with af. You can use
the send-file
command, and af will ask you for the content
type, disposition, and description if it recognises that the name of
the file indicates that it isn't textual (see section 21.1 Mime Configuration).
Or you can use an argument to send-file to force af to ask you for the
content type, disposition, and description, but that requires you to
know the correct content-type. Af will encode the message with the
`base64' encoding if required.
The second way is to supply an argument to the send-mail
command, or select the Attachments
option from the menu
presented after editing the text of a message. In either case you
will enter compose mode, where you can attach files or other
newly-created data to the message.
Compose mode looks very much like Mail mode, except that each line displays one body part of the message. Each body part can be of any type. The commands for moving around the screen, and viewing and deleting messages that you use in mail mode all work the same way in compose mode.
You can use two commands to add a body part in compose mode. One is
a or M-a (attach-file
). This prompts for a file
name, a Content-Type (which may be defaulted from the file name), and
a Content-Description, a textual description of the new body part.
The contents of the file are encoded if required, and then used to
create a new body part, which is inserted into the compose buffer
before point.
The second command is c or M-c (compose-body-part
).
This prompts for a Content-Type, Disposition, and Description, and then
uses an external program to create the body-part. The system needs to
be properly configured to create MIME mail, or af won't be able to
find out which program to use, and will give an error message, unless
the Content-Type is textual, in which case it will use an editor to
create the content.
In a similar way you can use e or M-e
(edit-body-part
) to edit the contents of a body part. Again, if
the system is not configured to do this then af will give an error
message for body part's that aren't textual.
You can edit the description of a body part using d or M-d
(edit-description
). You will be presented with the description
of the body part in the minibuffer for editing.
You can also edit the top-level headers of the composition using
h or M-h (edit-headers
). This presents the headers
of the message in an editor, just as when creating a non-MIME
message. Any text other than headers in the file will be discarded,
and a warning given.
When you've finished attaching files or composing body parts, then use
C-M-c or q (save-composition-and-exit
). This will
exit compose mode, creating a new message from the body parts. You will
be prompted for the disposition of the message, just as for any other
message you've edited.
If you want to abandon your changes in compose mode, then use
C-M-x (abandon-composition-and-exit
). You will be asked
if you really want to lose all your changes, and if you confirm, then
compose mode will exit, ignoring all your changes.
If you entered compose mode by supplying an argument to the
send-mail
command, then the entire command will be aborted.
Otherwise you will be prompted for the disposition of the message
normally.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
There are a number of configuration variables related to composing and sending mail. Here is a summary of each variable and its effects:
addresses-to-ignore
ask-bcc
true
, then af will prompt for addresses to send blind
copies to whenever you send mail. Default is false
.
ask-cc
true
, then af will prompt for addresses to send copies
to whenever you send mail. Default is false
.
auto-fold-headers
false
, then af will not automagically fold long header
lines onto several lines. Default is true
.
compose-line-format
header-line-format
defines the format of header
lines in mail mode. Defaults to %a %t %k %S
.
copy-on-reply
false
, af will never quote the text of the original
message in the initial text of a reply. If set to true
af will
always quote the original message. If set to ask
then you will
be asked each time you reply to a message. Defaults to ask
.
copy-preface
copy-prefix
edit-initial-headers
true
, headers will be placed into the file to edit the
first time you edit a message. When set to accept
, headers will
not be displayed for editing, but any valid headers typed at the
start of the message will be accepted. Defaults to false
.
edit-initial-signature
true
, any signature will be placed into the editor
the first time you edit a message. Defaults to false
.
edit-reply-address
true
, allows editing of the destination address when
replying to mail. It is intended for use by people at sites with
inadequate mail configurations. Defaults to false
.
editor
VISUAL
or EDITOR
environment variable.
forward-subject
headers-to-copy
multiple-reply-warning
true
, then af will prompt for confirmation if you try
to reply to a message that you have already replied to. Defaults to
false
.
organization
ORGANIZATION
environment variable.
outbound-folder
outbound-threshold
outbound-folder
. Af will prompt for
confirmation that a message longer than this limit is to be saved. If
set to 0 then all outbound messages will be saved regardless of length.
Default is 100 lines.
preserve-cc-in-group-reply
true
, any Cc:
header on a message is duplicated
in an outgoing group-reply to that message, so that recipients of a
carbon-copy will also receive the reply. Default is true
.
real-name
NAME
environment variable, or your details stored in
the file `/etc/passwd'.
reply-address
signature-file
signature-separator
spell-checker
ispell
is
installed on your system, or unset otherwise.
[ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Af will let you set mail aliases. These are short mnemonic names which stand for mail addresses or groups of mail addresses. Like many other mail programs, af expands aliases when they occur in the `To:', `From:', `Cc:', `Bcc:', and `Reply-to:' headers.
The easiest way to define a mail alias within af is with C-x C-a
(set-alias
). Af will prompt for the alias and then the real name
and the full address of the alias, defaulted from the From: header of
the current message. If the alias already exists, af will prompt for
confirmation that you want to change the alias. (2)
C-x C-a sets the alias internally; but it also writes the alias to the file `.afalias' in your home directory. This file is read whenever af starts up, so your aliases will be available next time you run af. You can also edit your `.afalias' file directly; each line should either be blank, be a comment beginning with `;', or look like:
alias:Real Name:addresses |
alias is the name of the alias; Real Name is the real name of the person or group the alias represents, and addresses stands for one or more mail addresses for alias to expand into. Separate multiple addresses with spaces or (preferably) commas. You can make an address list span more than one line by starting the second and subsequent lines with a space or tab, in the same way as mail headers are split over several lines of text.
For instance, to make afbug
stand for
af-bug@csv.warwick.ac.uk
put in these lines:
; Set up the af-bug mailing list as an alias afbug:Af Bug Mailing List:af-bug@csv.warwick.ac.uk |
Af expands aliases as soon as you finish editing the mail file, so you can check that the alias expanded properly by looking at the list of headers that af shows you when it prompts for the disposition of the mail.
[ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |