svn commit: r41450 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail
Dru Lavigne
dru at FreeBSD.org
Wed Apr 17 20:20:08 UTC 2013
Author: dru
Date: Wed Apr 17 20:20:07 2013
New Revision: 41450
URL: http://svnweb.freebsd.org/changeset/doc/41450
Log:
White space fix only. Translators can ignore.
Approved by: hrs (mentor)
Modified:
projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml
Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml
==============================================================================
--- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:17:38 2013 (r41449)
+++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:20:07 2013 (r41450)
@@ -54,8 +54,8 @@
</listitem>
<listitem>
- <para>The difference between remote and
- local mailboxes.</para>
+ <para>The difference between remote and local
+ mailboxes.</para>
</listitem>
<listitem>
@@ -108,20 +108,18 @@
<itemizedlist>
<listitem>
- <para>Properly set up a network
- connection (<xref
-linkend="advanced-networking"/>).</para>
+ <para>Properly set up a network connection (<xref
+ linkend="advanced-networking"/>).</para>
</listitem>
<listitem>
- <para>Properly set up the <acronym>DNS</acronym>
- information for a mail host (<xref
-linkend="network-servers"/>).</para>
+ <para>Properly set up the <acronym>DNS</acronym> information
+ for a mail host (<xref linkend="network-servers"/>).</para>
</listitem>
<listitem>
- <para>Know how to install additional
- third-party software (<xref linkend="ports"/>).</para>
+ <para>Know how to install additional third-party software
+ (<xref linkend="ports"/>).</para>
</listitem>
</itemizedlist>
</sect1>
@@ -136,7 +134,7 @@ linkend="network-servers"/>).</para>
<para>There are five major parts involved in an email exchange:
<link linkend="mail-mua">the Mail User Agent
<acronym>MUA></acronym></link>, <link linkend="mail-mta">the
- Mail Transfer Agent<acronym>MTA</acronym></link>, <link
+ Mail Transfer Agent<acronym>MTA</acronym></link>, <link
linkend="mail-dns"><acronym>DNS</acronym></link>, <link
linkend="mail-receive">a remote or local mailbox</link>, and
<link linkend="mail-host">the mail host</link>.</para>
@@ -179,11 +177,9 @@ linkend="network-servers"/>).</para>
<secondary><application>Exim</application></secondary>
</indexterm>
- <para>&os; ships with
-<application>Sendmail</application> as the default
- <acronym>MTA</acronym>, but it also supports numerous other
-mail server daemons,
- including:</para>
+ <para>&os; ships with <application>Sendmail</application> as the
+ default <acronym>MTA</acronym>, but it also supports numerous
+ other mail server daemons, including:</para>
<itemizedlist>
<listitem>
@@ -199,15 +195,13 @@ mail server daemons,
</listitem>
</itemizedlist>
- <para>The <acronym>MTA</acronym> usually has two
-functions. It is
- responsible for receiving incoming mail as well as delivering
- outgoing mail. It is <emphasis>not</emphasis> responsible
- for the collection of mail using protocols such as
+ <para>The <acronym>MTA</acronym> usually has two functions. It
+ is responsible for receiving incoming mail as well as
+ delivering outgoing mail. It is <emphasis>not</emphasis>
+ responsible for the collection of mail using protocols such as
<acronym>POP</acronym> or <acronym>IMAP</acronym>, nor does it
-allow connecting to local
- <filename>mbox</filename> or Maildir mailboxes. An additional
-<link
+ allow connecting to local <filename>mbox</filename> or Maildir
+ mailboxes. An additional <link
linkend="mail-receive">daemon</link> may be required for
these functions.</para>
@@ -215,10 +209,10 @@ allow connecting to local
<para>Older versions of <application>Sendmail</application>
contain serious security issues which may result in an
attacker gaining local or remote access to the system.
- Run a current version to &os; to avoid
- these problems. Optionally, install an alternative
- <acronym>MTA</acronym> from the <link linkend="ports">&os;
- Ports Collection</link>.</para>
+ Run a current version to &os; to avoid these problems.
+ Optionally, install an alternative <acronym>MTA</acronym>
+ from the <link linkend="ports">&os; Ports
+ Collection</link>.</para>
</warning>
</sect2>
@@ -226,14 +220,13 @@ allow connecting to local
<title>Email and DNS</title>
<para>The Domain Name System (<acronym>DNS</acronym>) and its
-daemon
- <command>named</command> play a large role in the delivery
- of email. In order to deliver mail from one site to another,
- the <acronym>MTA</acronym> will look up the remote site in
-<acronym>DNS</acronym>
- to determine which host will receive mail for the
- destination. This process also occurs when mail is sent from
- a remote host to the <acronym>MTA</acronym>.</para>
+ daemon <command>named</command> play a large role in the
+ delivery of email. In order to deliver mail from one site to
+ another, the <acronym>MTA</acronym> will look up the remote
+ site in <acronym>DNS</acronym> to determine which host will
+ receive mail for the destination. This process also occurs
+ when mail is sent from a remote host to the
+ <acronym>MTA</acronym>.</para>
<indexterm>
<primary>MX record</primary>
@@ -243,17 +236,16 @@ daemon
hostnames to IP addresses, as well as for storing information
specific to mail delivery, known as Mail eXchanger
<acronym>MX</acronym> records. The <acronym>MX</acronym>
-record specifies which host, or hosts, will receive
- mail for a particular domain. If there is no
-<acronym>MX</acronym> record
- for the hostname or domain, the mail will be delivered
+ record specifies which host, or hosts, will receive mail for a
+ particular domain. If there is no <acronym>MX</acronym>
+ record for the hostname or domain, the mail will be delivered
directly to the host, provided there is an
-<literal>A</literal> record pointing
- the hostname to the IP address.</para>
+ <literal>A</literal> record pointing the hostname to the IP
+ address.</para>
<para>To view the <acronym>MX</acronym> records for a domain,
-specify the type of record using
- &man.host.1;, as seen in the example below:</para>
+ specify the type of record using &man.host.1;, as seen in the
+ example below:</para>
<screen>&prompt.user; <userinput>host -t mx FreeBSD.org</userinput>
FreeBSD.org mail is handled by 10 mx1.FreeBSD.org</screen>
@@ -270,14 +262,13 @@ FreeBSD.org mail is handled by 10 mx1.Fr
<para>Receiving mail for a domain is done by the mail host.
It will collect all mail sent to the domain and store it
either in the default <filename>mbox</filename> or the
-alternative Maildir format, depending on the
- configuration. Once mail has been stored, it may either be
- read locally using a
- <acronym>MUA</acronym>, or remotely accessed and
- collected using protocols such as <acronym>POP</acronym> or
+ alternative Maildir format, depending on the configuration.
+ Once mail has been stored, it may either be read locally using
+ a <acronym>MUA</acronym>, or remotely accessed and collected
+ using protocols such as <acronym>POP</acronym> or
<acronym>IMAP</acronym>. In order to read mail locally,
- a <acronym>POP</acronym> or <acronym>IMAP</acronym>
- server does not need to be installed.</para>
+ a <acronym>POP</acronym> or <acronym>IMAP</acronym> server
+ does not need to be installed.</para>
<sect3 id="pop-and-imap">
<title>Accessing Remote Mailboxes Using <acronym>POP</acronym>
@@ -286,14 +277,12 @@ alternative Maildir format, depending on
<indexterm><primary>POP</primary></indexterm>
<indexterm><primary>IMAP</primary></indexterm>
<para>To access mailboxes remotely, access to a
-<acronym>POP</acronym> or
- <acronym>IMAP</acronym> server is required. These protocols
-allow users
- to connect to their mailboxes from remote locations. Though
-both <acronym>POP</acronym> and
- <acronym>IMAP</acronym> allow users to remotely access
- mailboxes, <acronym>IMAP</acronym> offers many advantages,
- including:</para>
+ <acronym>POP</acronym> or <acronym>IMAP</acronym> server is
+ required. These protocols allow users to connect to their
+ mailboxes from remote locations. Though both
+ <acronym>POP</acronym> and <acronym>IMAP</acronym> allow
+ users to remotely access mailboxes, <acronym>IMAP</acronym>
+ offers many advantages, including:</para>
<itemizedlist>
<listitem>
@@ -324,9 +313,8 @@ both <acronym>POP</acronym> and
<procedure>
<step>
<para>Use the Ports Collection to install an
-<acronym>IMAP</acronym> or
- <acronym>POP</acronym> server. The following
-<acronym>POP</acronym> and
+ <acronym>IMAP</acronym> or <acronym>POP</acronym>
+ server. The following <acronym>POP</acronym> and
<acronym>IMAP</acronym> servers are well known:</para>
<itemizedlist>
@@ -360,12 +348,12 @@ both <acronym>POP</acronym> and
<step>
<para>Where required, use the startup script that came
- with the application to load the
- <acronym>POP</acronym> or <acronym>IMAP</acronym>
- server. Those programs will also provide a variable
- which can be added to <filename>/etc/rc.conf</filename>
- to automate the startup of the application's daemon
- whenever the system boots.</para>
+ with the application to load the <acronym>POP</acronym>
+ or <acronym>IMAP</acronym> server. Those programs will
+ also provide a variable which can be added to
+ <filename>/etc/rc.conf</filename> to automate the
+ startup of the application's daemon whenever the system
+ boots.</para>
</step>
</procedure>
@@ -373,12 +361,10 @@ both <acronym>POP</acronym> and
<para>It should be noted that both <acronym>POP</acronym>
and <acronym>IMAP</acronym> transmit information,
including username and password credentials, in
-clear-text.
- To secure the transmission
- of information across these protocols, consider
-tunneling sessions over
-&man.ssh.1; (<xref linkend="security-ssh-tunneling"/>) or using
-SSL (<xref linkend="openssl"/>).</para>
+ clear-text. To secure the transmission of information
+ across these protocols, consider tunneling sessions over
+ &man.ssh.1; (<xref linkend="security-ssh-tunneling"/>) or
+ using SSL (<xref linkend="openssl"/>).</link>.</para>
</warning>
</sect3>
@@ -388,7 +374,7 @@ SSL (<xref linkend="openssl"/>).</para>
<para>Mailboxes may be accessed locally by directly using an
<acronym>MUA</acronym> on the server on which the mailbox
resides. This can be done using a built-in application
-such as &man.mail.1; or by installing a
+ such as &man.mail.1; or by installing a
<acronym>MUA</acronym> from the Ports Collection..</para>
</sect3>
</sect2>
@@ -398,9 +384,8 @@ such as &man.mail.1; or by installing a
<indexterm><primary>mail host</primary></indexterm>
- <para>The mail host is a server that is
- responsible for delivering and receiving mail for a host,
- or a network.</para>
+ <para>The mail host is a server that is responsible for
+ delivering and receiving mail for a host, or a network.</para>
</sect2>
</sect1>
@@ -422,12 +407,12 @@ such as &man.mail.1; or by installing a
<para>&man.sendmail.8; is the default <acronym>MTA</acronym>
which is installed with &os;.
-<application>Sendmail</application>
- accepts mail from <acronym>MUA</acronym>s and
- delivers it to the appropriate mailer as defined by its
- configuration file. <application>Sendmail</application> can
- also accept network connections and deliver mail to local
- mailboxes or to another program.</para>
+ <application>Sendmail</application> accepts mail from
+ <acronym>MUA</acronym>s and delivers it to the appropriate
+ mailer as defined by its configuration file.
+ <application>Sendmail</application> can also accept network
+ connections and deliver mail to local mailboxes or to another
+ program.</para>
<para><application>Sendmail</application> uses the following
configuration files. This section describes these files in more
@@ -521,9 +506,8 @@ such as &man.mail.1; or by installing a
passed to <application>Sendmail</application>'s error
handling routine with a given mailer error. Hosts that
are listed as <option>OK</option>, which is the default
-option,
- are allowed to send mail to this host as long as the mail's
- final destination is the local machine. Hosts that are
+ option, are allowed to send mail to this host as long as the
+ mail's final destination is the local machine. Hosts that are
listed as <option>REJECT</option> are rejected for all mail
connections. Hosts that are listed as <option>RELAY</option>
are allowed to send mail for any
@@ -540,37 +524,37 @@ okay.cyberspammer.com OK
128.32 RELAY</programlisting>
</example>
- <para>This example shows five entries. Mail senders that
- match the left side of the table are affected by the
- action on the right side of the table. The first two examples
- give an error code to <application>Sendmail</application>'s
- error handling routine. The message is sent to the remote
- host when a mail matches the left side of the table.
- The third entry rejects mail from a specific host on the
- Internet, <hostid>another.source.of.spam</hostid>. The fourth
- entry accepts mail connections from <hostid
+ <para>This example shows five entries. Mail senders that match
+ the left side of the table are affected by the action on the
+ right side of the table. The first two examples give an error
+ code to <application>Sendmail</application>'s error handling
+ routine. The message is sent to the remote host when a mail
+ matches the left side of the table. The third entry rejects
+ mail from a specific host on the Internet,
+ <hostid>another.source.of.spam</hostid>. The fourth entry
+ accepts mail connections from <hostid
role="fqdn">okay.cyberspammer.com</hostid>, which is
more specific than the <hostid
role="domainname">cyberspammer.com</hostid> line above.
More specific matches override less exact matches. The last
- entry allows relaying of email from hosts with an
- IP address that begins with <hostid>128.32</hostid>. These
- hosts can send mail through this mail server
- that is destined for other mail servers.</para>
+ entry allows relaying of email from hosts with an IP address
+ that begins with <hostid>128.32</hostid>. These hosts can
+ send mail through this mail server that is destined for other
+ mail servers.</para>
<para>Whenever this file is updated, run
<command>make</command> in <filename
-class="directory">/etc/mail/</filename>
- to update the database.</para>
+ class="directory">/etc/mail/</filename> to update the
+ database.</para>
</sect2>
<sect2>
<title><filename>/etc/mail/aliases</filename></title>
- <para>This database contains a list of virtual mailboxes
- that are expanded to other user(s), files, programs, or other
+ <para>This database contains a list of virtual mailboxes that
+ are expanded to other user(s), files, programs, or other
aliases. Here are a few examples to illustrate the
-file format:</para>
+ file format:</para>
<example>
<title>Mail Aliases</title>
@@ -581,20 +565,18 @@ bit.bucket: /dev/null
procmail: "|/usr/local/bin/procmail"</programlisting>
</example>
- <para>The mailbox name on the left
- side of the colon is expanded to the target(s) on the right.
- The first entry expands the mailbox
- <username>root</username> to the mailbox
+ <para>The mailbox name on the left side of the colon is expanded
+ to the target(s) on the right. The first entry expands the
+ mailbox <username>root</username> to the mailbox
<username>localuser</username>, which is then looked up again
in the <filename>aliases</filename> database. If no match is
-found, the
- message is delivered to
+ found, the message is delivered to
<username>localuser</username>. The second entry shows a
mail list. Mail to the mailbox <username>ftp-bugs</username>
is expanded to the three local mailboxes
<username>joe</username>, <username>eric</username>, and
- <username>paul</username>. A remote mailbox could
- be specified as <email>user at example.com</email>. The third
+ <username>paul</username>. A remote mailbox could be
+ specified as <email>user at example.com</email>. The third
entry shows how to write mail to a file, in this case
<filename>/dev/null</filename>. The last entry demonstrates
how to send mail to a program,
@@ -603,8 +585,8 @@ found, the
<para>Whenever this file is updated, run
<command>make</command> in <filename
-class="directory">/etc/mail/</filename>
- to update the database.</para>
+ class="directory">/etc/mail/</filename> to update the
+ database.</para>
</sect2>
<sect2>
<title><filename>/etc/mail/local-host-names</filename></title>
@@ -612,11 +594,10 @@ class="directory">/etc/mail/</filename>
<para>This is a list of hostnames &man.sendmail.8; is to accept
as the local host name. Place any domains or hosts that
<application>Sendmail</application> will receive mail
- for. For example, to configure a mail server to accept
-mail for
- the domain <hostid role="domainname">example.com</hostid> and
- the host <hostid role="fqdn">mail.example.com</hostid>, add
-these entries to
+ for. For example, to configure a mail server to accept mail
+ for the domain <hostid role="domainname">example.com</hostid>
+ and the host <hostid role="fqdn">mail.example.com</hostid>,
+ add these entries to
<filename>local-host-names</filename>:</para>
<programlisting>example.com
@@ -630,15 +611,13 @@ mail.example.com</programlisting>
<sect2>
<title><filename>/etc/mail/sendmail.cf</filename></title>
- <para>This is the master
-configuration file for <application>Sendmail</application>. It
-controls the overall
+ <para>This is the master configuration file for
+ <application>Sendmail</application>. It controls the overall
behavior of <application>Sendmail</application>, including
everything from rewriting email addresses to printing rejection
messages to remote mail servers. Accordingly, this
-configuration file is quite complex. Fortunately, this
- file rarely needs to be changed for standard mail
- servers.</para>
+ configuration file is quite complex. Fortunately, this file
+ rarely needs to be changed for standard mail servers.</para>
<para>The master <application>Sendmail</application> configuration
file can be built from &man.m4.1; macros that define the
@@ -670,18 +649,17 @@ postmaster at example.com postmast
<para>The above example contains a mapping for the domain
<hostid role="domainname">example.com</hostid>. This file
- is processed in a first match order. The first
- item maps <email>root at example.com</email> to the local mailbox
+ is processed in a first match order. The first item maps
+ <email>root at example.com</email> to the local mailbox
<username>root</username>. The second entry maps
<email>postmaster at example.com</email> to the mailbox
- <username>postmaster</username> on the host
- <hostid role="fqdn">noc.example.net</hostid>. Finally, if
+ <username>postmaster</username> on the host <hostid
+ role="fqdn">noc.example.net</hostid>. Finally, if
nothing from <hostid role="domainname">example.com</hostid>
has matched so far, it will match the last mapping, which
matches every other mail message addressed to someone at
<hostid role="domainname">example.com</hostid> to the local
-mailbox
- <username>joe</username>.</para>
+ mailbox <username>joe</username>.</para>
</sect2>
</sect1>
@@ -711,56 +689,47 @@ mailbox
<secondary>change mta</secondary>
</indexterm>
- <para>&os; comes with
- <application>Sendmail</application> already installed as the
- <acronym>MTA</acronym> which is
- in charge of outgoing and incoming mail.</para>
-
- <para>However, the system
- administrator can change the system's <acronym>MTA</acronym>.
-The
- reasons for doing so range from wanting to try out
-another <acronym>MTA</acronym> to
- needing a specific feature or package which relies on another
- <acronym>MTA</acronym>. Whatever the reason,
-&os; makes it
+ <para>&os; comes with <application>Sendmail</application> already
+ installed as the <acronym>MTA</acronym> which is in charge of
+ outgoing and incoming mail.</para>
+
+ <para>However, the system administrator can change the system's
+ <acronym>MTA</acronym>. The reasons for doing so range from
+ wanting to try out another <acronym>MTA</acronym> to needing a
+ specific feature or package which relies on another
+ <acronym>MTA</acronym>. Whatever the reason, &os; makes it
easy to make the change.</para>
<sect2>
<title>Install a New <acronym>MTA</acronym></title>
<para>A wide choice of <acronym>MTA</acronym>s is available
-from the <literal>mail</literal> category of the
- <link linkend="ports">&os; Ports Collection</link>.</para>
+ from the <literal>mail</literal> category of the <link
+ linkend="ports">&os; Ports Collection</link>.</para>
- <para>Once a new <acronym>MTA</acronym> is installed,
-configure the
- new software and decide if it really fulfills your needs
+ <para>Once a new <acronym>MTA</acronym> is installed, configure
+ the new software and decide if it really fulfills your needs
before replacing <application>Sendmail</application>.</para>
<para>Refer to the new chosen <acronym>MTA</acronym>'s
-documentation for
- information on how to configure the software.</para>
+ documentation for information on how to configure the
+ software.</para>
</sect2>
<sect2 id="mail-disable-sendmail">
<title>Disable <application>Sendmail</application></title>
<warning>
- <para>If <application>Sendmail</application>'s
- outgoing mail service is disabled, it is important that it
-is replaced
+ <para>If <application>Sendmail</application>'s outgoing mail
+ service is disabled, it is important that it is replaced
with an alternative mail delivery system. Otherwise, system
-functions such as
- &man.periodic.8; will be unable to deliver their results
- by email. Many parts of
- the system expect a functional
- <acronym>MTA</acronym>. If
- applications continue to use
- <application>Sendmail</application>'s binaries to try to
- send email they are disabled, mail could go
- into an inactive <application>Sendmail</application> queue,
- and never be delivered.</para>
+ functions such as &man.periodic.8; will be unable to deliver
+ their results by email. Many parts of the system expect a
+ functional <acronym>MTA</acronym>. If applications continue
+ to use <application>Sendmail</application>'s binaries to try
+ to send email they are disabled, mail could go into an
+ inactive <application>Sendmail</application> queue, and
+ never be delivered.</para>
</warning>
<para>In order to completely disable
@@ -773,9 +742,8 @@ sendmail_submit_enable="NO"
sendmail_outbound_enable="NO"
sendmail_msp_queue_enable="NO"</programlisting>
- <para>To only disable
- <application>Sendmail</application>'s incoming mail service,
- set</para>
+ <para>To only disable <application>Sendmail</application>'s
+ incoming mail service, set</para>
<programlisting>sendmail_enable="NO"</programlisting>
@@ -788,9 +756,8 @@ sendmail_msp_queue_enable="NO"</programl
<title>Running the New <acronym>MTA</acronym> on Boot</title>
<para>The new <acronym>MTA</acronym> can be started during
-boot by adding a
- configuration line to <filename>/etc/rc.conf</filename>.
- This example enables the
+ boot by adding a configuration line to
+ <filename>/etc/rc.conf</filename>. This example enables the
Postfix <acronym>MTA</acronym>:</para>
<screen>&prompt.root; echo
@@ -798,35 +765,33 @@ boot by adding a
>> /etc/rc.conf</screen>
<para>The specified <acronym>MTA</acronym> will now be
-automatically started during
- boot.</para>
+ automatically started during boot.</para>
</sect2>
<sect2>
<title>Replacing <application>Sendmail</application> as
the System's Default Mailer</title>
- <para><application>Sendmail</application> is so
- ubiquitous as standard software on &unix; systems that some
- software assumes it is already installed and configured.
- For this reason, many alternative <acronym>MTA</acronym>s
-provide their own
+ <para><application>Sendmail</application> is so ubiquitous as
+ standard software on &unix; systems that some software assumes
+ it is already installed and configured. For this reason, many
+ alternative <acronym>MTA</acronym>s provide their own
compatible implementations of the
<application>Sendmail</application> command-line interface in
-order to
- facilitate using them as <quote>drop-in</quote>
+ order to facilitate using them as <quote>drop-in</quote>
replacements for <application>Sendmail</application>.</para>
<para>When using an alternative <acronym>MTA</acronym>,
- make sure that software trying to execute
- standard <application>Sendmail</application> binaries, such as
+ make sure that software trying to execute standard
+ <application>Sendmail</application> binaries, such as
<filename>/usr/bin/sendmail</filename>, actually execute
- the chosen mailer instead. Fortunately, &os; provides
- a system called &man.mailwrapper.8; for this purpose.</para>
+ the chosen mailer instead. Fortunately, &os; provides a
+ system called &man.mailwrapper.8; for this purpose.</para>
<para>When <application>Sendmail</application> is operating
as installed,
-<filename>/etc/mail/mailer.conf</filename> will look like this:</para>
+ <filename>/etc/mail/mailer.conf</filename> will look like
+ this:</para>
<programlisting>sendmail /usr/libexec/sendmail/sendmail
send-mail /usr/libexec/sendmail/sendmail
@@ -835,19 +800,17 @@ newaliases /usr/libexec/sendmail/sendmai
hoststat /usr/libexec/sendmail/sendmail
purgestat /usr/libexec/sendmail/sendmail</programlisting>
- <para>When any of the commands listed on the left
- are run,
+ <para>When any of the commands listed on the left are run,
the system actually executes the associated command shown on
the right instead. This system makes it easy to change what
-binaries
- are executed when these default
+ binaries are executed when these default
<filename>Sendmail</filename> functions are invoked.</para>
<para>As an example, to run
<filename>/usr/local/supermailer/bin/sendmail-compat</filename>
instead of <application>Sendmail</application>, specify the
paths to the installed applications in
-<filename>/etc/mail/mailer.conf</filename>:</para>
+ <filename>/etc/mail/mailer.conf</filename>:</para>
<programlisting>sendmail /usr/local/supermailer/bin/sendmail-compat
send-mail /usr/local/supermailer/bin/sendmail-compat
@@ -862,13 +825,11 @@ purgestat /usr/local/supermailer/bin/pur
<title>Finishing</title>
<para>Once everything is configured, either kill the
-unneeded
- <application>sendmail</application> processes and start
-the processes belonging to the
- new software, or reboot. Rebooting provides the
-opportunity to ensure that the system is correctly configured to start
-the new <acronym>MTA</acronym> automatically
- on boot.</para>
+ unneeded <application>sendmail</application> processes and
+ start the processes belonging to the new software, or
+ reboot. Rebooting provides the opportunity to ensure that
+ the system is correctly configured to start the new
+ <acronym>MTA</acronym> automatically on boot.</para>
</sect2>
</sect1>
@@ -889,13 +850,12 @@ the new <acronym>MTA</acronym> automatic
</question>
<answer>
- <para>The host may actually be
- in a different domain. For example, in order for a
-host in
- <hostid role="fqdn">foo.bar.edu</hostid>
- to reach a host called <hostid>mumble</hostid> in the
- <hostid role="domainname">bar.edu</hostid> domain,
- refer to it by the Fully-Qualified Domain Name
+ <para>The host may actually be in a different domain.
+ For example, in order for a host in <hostid
+ role="fqdn">foo.bar.edu</hostid> to reach a host
+ called <hostid>mumble</hostid> in the <hostid
+ role="domainname">bar.edu</hostid> domain, refer to
+ it by the Fully-Qualified Domain Name
<acronym>FQDN</acronym>, <hostid
role="fqdn">mumble.bar.edu</hostid>, instead of just
<hostid>mumble</hostid>.</para>
@@ -904,23 +864,21 @@ host in
<para>This is because the version of
<application>BIND</application> which ships with
&os; no longer provides default abbreviations
- for non-FQDNs other than the local
- domain. An unqualified host such as
+ for non-FQDNs other than the local domain. An
+ unqualified host such as
<hostid>mumble</hostid> must either be found as
<hostid role="fqdn">mumble.foo.bar.edu</hostid>,
- or it will be searched for in the root
- domain.</para>
+ or it will be searched for in the root domain.</para>
<para>In older versions of
<application>BIND</application>,
the search continued across <hostid
role="domainname">mumble.bar.edu</hostid>, and
<hostid role="domainname">mumble.edu</hostid>. RFC
-1535 details why this is considered bad
- practice or even a security hole.</para>
+ 1535 details why this is considered bad practice or
+ even a security hole.</para>
- <para>As a good workaround, place the
- line:</para>
+ <para>As a good workaround, place the line:</para>
<programlisting>search foo.bar.edu bar.edu</programlisting>
@@ -942,11 +900,9 @@ host in
</question>
<answer>
- <para>This is answered in the
- <ulink
+ <para>This is answered in the <ulink
url="http://www.sendmail.org/faq/">Sendmail
- FAQ</ulink> as follows. This FAQ is
-recommended reading
+ FAQ</ulink> as follows. This FAQ is recommended reading
when <quote>tweaking</quote> the mail setup.</para>
<programlisting>I'm getting these error messages:
@@ -975,46 +931,41 @@ to /etc/mail/sendmail.cf.</programlistin
<answer>
<para>Connect to a &os; mail gateway on the LAN. The PPP
-connection is non-dedicated.</para>
+ connection is non-dedicated.</para>
<indexterm>
<primary>MX record</primary>
</indexterm>
<para>One way to do this is to get a full-time Internet server
-to
- provide secondary <acronym>MX</acronym> services for the
-domain. In this example,
- the domain is <hostid
+ to provide secondary <acronym>MX</acronym> services for the
+ domain. In this example, the domain is <hostid
role="domainname">example.com</hostid> and the ISP has
-configured <hostid
+ configured <hostid
role="domainname">example.net</hostid> to provide
secondary <acronym>MX</acronym> services to the
-domain:</para>
+ domain:</para>
<programlisting>example.com. MX 10 example.com.
MX 20 example.net.</programlisting>
<para>Only one host should be specified as the final
-recipient. For <application>Sendmail</application>,
- add <literal>Cw example.com</literal> in
+ recipient. For <application>Sendmail</application>, add
+ <literal>Cw example.com</literal> in
<filename>/etc/mail/sendmail.cf</filename> on
<hostid role="domainname">example.com</hostid>.</para>
<para>When the sending <acronym>MTA</acronym> attempts
to deliver mail, it will try to connect to the system,
-<hostid
- role="domainname">example.com</hostid>, over the PPP
+ <hostid role="domainname">example.com</hostid>, over the PPP
link. This will time out if the destination is offline.
- The <acronym>MTA</acronym>
- will automatically deliver it to the secondary
-<acronym>MX</acronym> site at the Internet Service
- Provider (<acronym>ISP</acronym>), <hostid
+ The <acronym>MTA</acronym> will automatically deliver it to
+ the secondary <acronym>MX</acronym> site at the Internet
+ Service Provider (<acronym>ISP</acronym>), <hostid
role="domainname">example.net</hostid>. The secondary
- <acronym>MX</acronym> site will periodically try to
-connect to
- the primary <acronym>MX</acronym> host,
- <hostid role="domainname">example.com</hostid>.</para>
+ <acronym>MX</acronym> site will periodically try to connect
+ to the primary <acronym>MX</acronym> host, <hostid
+ role="domainname">example.com</hostid>.</para>
<para>Use something like this as a login
script:</para>
@@ -1024,10 +975,9 @@ connect to
( sleep 60 ; /usr/sbin/sendmail -q ) &
/usr/sbin/ppp -direct pppmyisp</programlisting>
- <para>When creating a separate login script for
- users, instead use <command>sendmail
- -qRexample.com</command> in the script above.
- This will force all mail in the queue for <hostid
+ <para>When creating a separate login script for users, instead
+ use <command>sendmail -qRexample.com</command> in the script
+ above. This will force all mail in the queue for <hostid
role="domainname">example.com</hostid> to be processed
immediately.</para>
@@ -1075,31 +1025,28 @@ the DNS for <quote>customer.com</quote>.
<para>In a default &os; installation,
<application>Sendmail</application> is configured to only
send mail from the host it is running on. For example,
- if a <acronym>POP</acronym> server is available,
- users will be able to check mail from remote locations but
-they will not be able
- to send outgoing emails from outside locations.
- Typically, a few moments after the attempt, an email will
- be sent from <literal>MAILER-DAEMON</literal>
+ if a <acronym>POP</acronym> server is available, users
+ will be able to check mail from remote locations but they
+ will not be able to send outgoing emails from outside
+ locations. Typically, a few moments after the attempt, an
+ email will be sent from <literal>MAILER-DAEMON</literal>
with a <errorname>5.7 Relaying Denied</errorname>.</para>
- <para>The most
- straightforward solution is to add the ISP's FQDN to
- <filename>/etc/mail/relay-domains</filename>, as
-seen in this example:</para>
+ <para>The most straightforward solution is to add the ISP's
+ FQDN to <filename>/etc/mail/relay-domains</filename>, as
+ seen in this example:</para>
<screen>&prompt.root; <userinput>echo "your.isp.example.com" > /etc/mail/relay-domains</userinput></screen>
<para>After creating or editing this file, restart
<application>Sendmail</application>. This works great if
- the server administrator does not wish to send
- mail locally, would like to use a <acronym>MUA</acronym>
-on a
+ the server administrator does not wish to send mail
+ locally, would like to use a <acronym>MUA</acronym> on a
remote machine, or would like to use another
- <acronym>ISP</acronym> for remote connections. It
- is also useful when there is only one or two email
- accounts. If there are a large number of addresses,
- add them one per line:</para>
+ <acronym>ISP</acronym> for remote connections. It is also
+ useful when there is only one or two email accounts. If
+ there are a large number of addresses, add them one per
+ line:</para>
<programlisting>your.isp.example.com
other.isp.example.net
@@ -1107,11 +1054,10 @@ users-isp.example.org
www.example.org</programlisting>
<para>Now any mail sent through the system by any host in
- this list, provided the user has an account on the
- system, will succeed. This allows
- users to send mail from the system remotely without
- opening the system up to relaying SPAM from the
- Internet.</para>
+ this list, provided the user has an account on the system,
+ will succeed. This allows users to send mail from the
+ system remotely without opening the system up to relaying
+ SPAM from the Internet.</para>
</answer>
</qandaentry>
@@ -1121,9 +1067,8 @@ www.example.org</programlisting>
<sect1 id="mail-advanced">
<title>Advanced Topics</title>
- <para>This section covers more involved topics such as
- mail configuration and setting up mail for an entire
- domain.</para>
+ <para>This section covers more involved topics such as mail
+ configuration and setting up mail for an entire domain.</para>
<sect2 id="mail-config">
<title>Basic Configuration</title>
@@ -1133,13 +1078,11 @@ www.example.org</programlisting>
<secondary>configuration</secondary>
</indexterm>
- <para>Out of the box, one can send email to
- external hosts as long as
- <filename>/etc/resolv.conf</filename> is configured or the
-network has access to a configured
+ <para>Out of the box, one can send email to external hosts as
+ long as <filename>/etc/resolv.conf</filename> is configured or
+ the network has access to a configured
<acronym>DNS</acronym> server. If order to have mail
- delivered to the <acronym>MTA</acronym> on the &os;
-host,
+ delivered to the <acronym>MTA</acronym> on the &os; host,
do one of the following:</para>
<itemizedlist>
@@ -1155,27 +1098,24 @@ host,
</itemizedlist>
<indexterm><primary>SMTP</primary></indexterm>
- <para>In order
- to have mail delivered directly to a host, it must have
- a permanent static IP address, not a dynamic IP address. If
-the system is behind a
- firewall, it must be configured to allow SMTP traffic.
- To receive mail directly at a host, one of these two
-must be configured:</para>
+ <para>In order to have mail delivered directly to a host, it
+ must have a permanent static IP address, not a dynamic IP
+ address. If the system is behind a firewall, it must be
+ configured to allow SMTP traffic. To receive mail directly at
+ a host, one of these two must be configured:</para>
<itemizedlist>
<indexterm><primary>MX record</primary></indexterm>
<listitem>
<para>Make sure that the lowest-numbered
-<acronym>MX</acronym> record in
+ <acronym>MX</acronym> record in
<acronym>DNS</acronym> points to the host's static IP
-address.</para>
+ address.</para>
</listitem>
<listitem>
<para>Make sure there is no <acronym>MX</acronym> entry in
-the <acronym>DNS</acronym> for the
- host.</para>
+ the <acronym>DNS</acronym> for the host.</para>
</listitem>
</itemizedlist>
@@ -1189,8 +1129,8 @@ example.FreeBSD.org
&prompt.root; <userinput>host example.FreeBSD.org</userinput>
example.FreeBSD.org has address 204.216.27.XX</screen>
- <para>In this example, mail sent directly to
- <email role="nolink">yourlogin at example.FreeBSD.org</email>
+ <para>In this example, mail sent directly to <email
+ role="nolink">yourlogin at example.FreeBSD.org</email>
should work without problems, assuming
<application>Sendmail</application> is running correctly on
<hostid role="fqdn">example.FreeBSD.org</hostid>.</para>
@@ -1206,14 +1146,12 @@ example.FreeBSD.org mail is handled (pri
collected on <hostid>hub</hostid> under the same username
instead of being sent directly to your host.</para>
- <para>The above information is handled by
-the <acronym>DNS</acronym> server.
- The <acronym>DNS</acronym> record that carries mail routing
-information is the
- <acronym>MX</acronym> entry.
- If no <acronym>MX</acronym> record exists, mail will be
-delivered directly to
- the host by way of its IP address.</para>
+ <para>The above information is handled by the
+ <acronym>DNS</acronym> server. The <acronym>DNS</acronym>
+ record that carries mail routing information is the
+ <acronym>MX</acronym> entry. If no <acronym>MX</acronym>
+ record exists, mail will be delivered directly to the host by
+ way of its IP address.</para>
<para>The <acronym>MX</acronym> entry for <hostid
role="fqdn">freefall.FreeBSD.org</hostid> at one time looked
@@ -1226,35 +1164,30 @@ freefall MX 20 who.cdrom.com</programli
<para><hostid>freefall</hostid> had many <acronym>MX</acronym>
entries. The lowest <acronym>MX</acronym> number is the host
-that receives mail
- directly, if available. If it is not accessible for some
- reason, the next lower-numbered host will accept messages
-temporarily, and pass it along when a lower-numbered host becomes
-available.</para>
+ that receives mail directly, if available. If it is not
+ accessible for some reason, the next lower-numbered host will
+ accept messages temporarily, and pass it along when a
+ lower-numbered host becomes available.</para>
<para>Alternate <acronym>MX</acronym> sites should have separate
-Internet
- connections in order to be most useful. Your
- <acronym>ISP</acronym> can provide
- this service.</para>
+ Internet connections in order to be most useful. Your
+ <acronym>ISP</acronym> can provide this service.</para>
</sect2>
<sect2 id="mail-domain">
<title>Mail for a Domain</title>
<para>When configuring a <acronym>MTA</acronym> for a network,
-any mail sent to hosts in its
- domain should be diverted to the
+ any mail sent to hosts in its domain should be diverted to the
<acronym>MTA</acronym> so that users can receive their mail on
-the master
- mail server.</para>
+ the master mail server.</para>
<indexterm><primary>DNS</primary></indexterm>
<para>To make life easiest, a user account with the same
<emphasis>username</emphasis> should exist on both the
<acronym>MTA</acronym> and the system with the
- <acronym>MUA</acronym>.
- Use &man.adduser.8; to create the user accounts.</para>
+ <acronym>MUA</acronym>. Use &man.adduser.8; to create the
+ user accounts.</para>
<para>The <acronym>MTA</acronym> must be the designated mail
exchanger for each workstation on the network. This is done
@@ -1266,8 +1199,7 @@ the master
<para>This will redirect mail for the workstation to the
<acronym>MTA</acronym> no matter where the A record points.
-The mail is
- sent to the <acronym>MX</acronym> host.</para>
+ The mail is sent to the <acronym>MX</acronym> host.</para>
<para>This must be configured on a <acronym>DNS</acronym>
server. If the network does not run its own
@@ -1276,30 +1208,25 @@ The mail is
provider.</para>
<para>he following is an example of virtual email hosting.
-Consider a customer with the domain
- <hostid role="domainname">customer1.org</hostid>, where
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-projects
mailing list