os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Add right role attribute to hostid tags

Browse source 
- Add various tags
- Avoid capitalization of the name "sendmail"
- Some punctuation fixes
- s/admin/administrator and don't/do not
- use of man entity when needed
This commit is contained in:
Marc Fonvieille 2002-10-08 18:53:51 +00:00
parent 783ac287d9
commit e5978b0d32
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14563
1 changed files with 20 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
en_US.ISO8859-1/books/handbook/mail/chapter.sgml
View file

@ -355,8 +355,8 @@ okay.cyberspammer.com OK
rejects mail from a specific host on the Internet, rejects mail from a specific host on the Internet,
<hostid>another.source.of.spam</hostid>. The next entry accepts <hostid>another.source.of.spam</hostid>. The next entry accepts
mail connections from a host mail connections from a host
<hostid>okay.cyberspammer.com</hostid>, which is more exact than <hostid role="fqdn">okay.cyberspammer.com</hostid>, which is more exact than
the <hostid>cyberspammer.com</hostid> line above. More specific the <hostid role="domainname">cyberspammer.com</hostid> line above. More specific
matches override less exact matches. The last entry allows matches override less exact matches. The last entry allows
relaying of electronic mail from hosts with an IP address that relaying of electronic mail from hosts with an IP address that
begins with <hostid>128.32</hostid>. These hosts would be able begins with <hostid>128.32</hostid>. These hosts would be able
@ -395,7 +395,7 @@ procmail: "|/usr/local/bin/procmail"</programlisting>
list. Mail to the mailbox <username>ftp-bugs</username> is list. Mail to the mailbox <username>ftp-bugs</username> is
expanded to the three local mailboxes <username>joe</username>, expanded to the three local mailboxes <username>joe</username>,
<username>eric</username>, and <username>paul</username>. Note <username>eric</username>, and <username>paul</username>. Note
that a remote mailbox could be specified as user@example.com. The that a remote mailbox could be specified as <literal>user@example.com</literal>. The
next example shows writing mail to a file, in this case next example shows writing mail to a file, in this case
<filename>/dev/null</filename>. The last example shows sending <filename>/dev/null</filename>. The last example shows sending
mail to a program, in this case the mail message is written to the mail to a program, in this case the mail message is written to the
@ -414,7 +414,7 @@ procmail: "|/usr/local/bin/procmail"</programlisting>
<application>sendmail</application> is to be receiving mail for. <application>sendmail</application> is to be receiving mail for.
For example, if this mail server was to accept mail for the For example, if this mail server was to accept mail for the
domain <hostid role="domainname">example.com</hostid> and the host domain <hostid role="domainname">example.com</hostid> and the host
<hostid>mail.example.com</hostid>, its <hostid role="fqdn">mail.example.com</hostid>, its
<filename>local-host-names</filename> might look something like <filename>local-host-names</filename> might look something like
this:</para> this:</para>
@ -467,15 +467,15 @@ postmaster@example.com postmaster@noc.example.net
</example> </example>
<para>In the above example, we have a mapping for a domain <para>In the above example, we have a mapping for a domain
<hostid>example.com</hostid>. This file is processed in a <hostid role="domainname">example.com</hostid>. This file is processed in a
first match order down the file. The first item maps first match order down the file. The first item maps
root@example.com to the local mailbox root. The next entry maps <literal>root@example.com</literal> to the local mailbox <username>root</username>. The next entry maps
postmaster@example.com to the mailbox postmaster on the host <literal>postmaster@example.com</literal> to the mailbox <username>postmaster</username> on the host
noc.example.net. Finally, if nothing from example.com has <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 matched so far, it will match the last mapping, which matches
every other mail message addressed to someone at every other mail message addressed to someone at
<hostid>example.com</hostid>. <hostid role="domainname">example.com</hostid>.
This will be mapped to the local mail box joe.</para> This will be mapped to the local mailbox <username>joe</username>.</para>
</sect2> </sect2>
</sect1> </sect1>
@ -653,13 +653,13 @@ postmaster@example.com postmaster@noc.example.net
<title>Replacing <application>sendmail</application> as <title>Replacing <application>sendmail</application> as
the system's default mailer</title> the system's default mailer</title>
<para><application>Sendmail</application> is so ubiquitous <para>The program <application>sendmail</application> is so ubiquitous
as standard software on Unix systems that some software as standard software on Unix systems that some software
just assumes it is already installed and configured. just assumes it is already installed and configured.
For this reason, many alternative MTA's provide their own compatible For this reason, many alternative MTA's provide their own compatible
implementations of the <application>sendmail</application> implementations of the <application>sendmail</application>
command-line interface; this facilitates using them as command-line interface; this facilitates using them as
<quote>drop-in</quote> replacements for sendmail.</para> <quote>drop-in</quote> replacements for <application>sendmail</application>.</para>
<para>Therefore, if you are using an alternative mailer, <para>Therefore, if you are using an alternative mailer,
you will need to make sure that software trying to execute you will need to make sure that software trying to execute
@ -820,8 +820,8 @@ to /etc/mail/sendmail.cf.</programlisting>
<para>Another way is to get a full-time Internet server to provide secondary MX <para>Another way is to get a full-time Internet server to provide secondary MX
services for your domain. For example, if your company's domain is services for your domain. For example, if your company's domain is
<hostid>example.com</hostid> and your Internet service provider has <hostid role="domainname">example.com</hostid> and your Internet service provider has
set <hostid>example.net</hostid> up to provide secondary MX services set <hostid role="domainname">example.net</hostid> up to provide secondary MX services
to your domain:</para> to your domain:</para>
<programlisting>example.com. MX 10 example.com. <programlisting>example.com. MX 10 example.com.
@ -834,13 +834,13 @@ to /etc/mail/sendmail.cf.</programlisting>
<para>When the sending <command>sendmail</command> is trying to <para>When the sending <command>sendmail</command> is trying to
deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem
link. It will most likely time out because you are not online. link. It will most likely time out because you are not online.
<application>Sendmail</application> will automatically deliver it to the The program <application>sendmail</application> will automatically deliver it to the
secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX
site will then periodically try to connect to site will then periodically try to connect to
your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para> your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para>
<para>You might want to use something like this as a login <para>You might want to use something like this as a login
script.</para> script:</para>
<programlisting>#!/bin/sh <programlisting>#!/bin/sh
# Put me in /usr/local/bin/pppmyisp # Put me in /usr/local/bin/pppmyisp
@ -852,7 +852,7 @@ to /etc/mail/sendmail.cf.</programlisting>
instead in the script above. This will force all mail in your instead in the script above. This will force all mail in your
queue for <hostid role="domainname">example.com</hostid> to be processed immediately.</para> queue for <hostid role="domainname">example.com</hostid> to be processed immediately.</para>
<para>A further refinement of the situation is as follows.</para> <para>A further refinement of the situation is as follows:</para>
<para>Message stolen from the &a.isp;.</para> <para>Message stolen from the &a.isp;.</para>
@ -916,7 +916,7 @@ the DNS for <quote>customer.com</quote>.</programlisting>
<para>After creating or editing this file you must restart <para>After creating or editing this file you must restart
<application>sendmail</application>. This works great if <application>sendmail</application>. This works great if
you are a server admin and don't wish to send mail you are a server administrator and do not wish to send mail
locally, or would like to use a point and click locally, or would like to use a point and click
client/system on another machine or even another ISP. It client/system on another machine or even another ISP. It
is also very useful if you only have one or two email is also very useful if you only have one or two email
@ -1063,7 +1063,7 @@ freefall MX 20 who.cdrom.com</programlisting>
<indexterm><primary>DNS</primary></indexterm> <indexterm><primary>DNS</primary></indexterm>
<para>To make life easiest, a user account with the same <para>To make life easiest, a user account with the same
<emphasis>username</emphasis> should exist on both machines. Use <emphasis>username</emphasis> should exist on both machines. Use
<command>adduser</command> to do this.</para> &man.adduser.8; to do this.</para>
<para>The mailhost you will be using must be the designated mail <para>The mailhost you will be using must be the designated mail
exchanger for each workstation on the network. This is done in exchanger for each workstation on the network. This is done in
@ -1082,7 +1082,7 @@ freefall MX 20 who.cdrom.com</programlisting>
<para>If you are doing virtual email hosting, the following <para>If you are doing virtual email hosting, the following
information will come in handy. For this example, we information will come in handy. For this example, we
will assume you have a customer with their own domain, in this will assume you have a customer with his own domain, in this
case <hostid role="domainname">customer1.org</hostid>, and you want case <hostid role="domainname">customer1.org</hostid>, and you want
all the mail for <hostid role="domainname">customer1.org</hostid> all the mail for <hostid role="domainname">customer1.org</hostid>
sent to your mailhost, <hostid sent to your mailhost, <hostid