The precedence of a mail message determines its position among other
messages in the queue when the queue is processed. Precedence, as a header line,
also defines whether or not a bounced message should be returned
to the sender. Precedences are not hard-coded into
Instead, they need to be declared in the configuration file.
The typical declarations, and the ones we will use, look like this:
These lines use the
(precedence) configuration command.
Like all configuration
must begin the line. It is followed
by a name, an equal sign, and a value. The general form
looks like this:
There are only five possibilities for
that are legal:
This mail message needs to be processed before any others. This
precedence is effective only when the message is being delivered
from the queue.
Unless otherwise declared with a
the message is
The message originated as part of a mailing list. It should be
deferred until other more important mail has been processed
from the queue.
The message is a broadcast, like a mailing list but less important.
If the message can't be delivered, the message body is discarded
from the bounced mail.
Absolutely worthless mail. Test messages and mail from some
programs fall into this category. Like
, the message
body is discarded from the bounced mail.
assigned to each
is somewhat arbitrary.
The ones that we use are common. As you gain familiarity with the
queue and mailing lists, you may want to adjust these values.
In general, the higher the number, the higher the precedence.
By convention, formal first-class mail has a precedence of zero, with
positive numbers used
mail and negative numbers
used for various kinds of bulk mail.
configuration command only tells
to assign to a given
has no other effect. The values are used only when a mail
message is processed that has a
line in it. The inclusion of
is left to MUAs.
To illustrate, imagine that a user on your machine is managing
a mailing list. The software that is used to create each message
for the list arranges to include a
that looks like this:
The mailing-list message is given to
on the local
machine. The local
in the message and extracts the field of that header, the
It then compares
to each of the
parts of its
configuration lines. It finds a match
with the line:
Because it finds a match, it uses the
configuration command as the initial precedence of the mail message.
If there is no match (or if the original message lacks
header), the initial precedence of the
mail message defaults to zero.
configuration commands to
file. Traditionally, they are placed after the header
H?D?Date: $a # Add if F=D
H?M?Message-Id: <$t.$i@$j> # Add if F=M