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

Change /myco.com/example.com/ since the latter is reserved exactly for

Browse source 
this type of thing, instead of rolling our own example domainnames as
in rev 1.53 of this file.

Suggested by:	ceri
This commit is contained in:
Giorgos Keramidas 2002-08-25 00:54:57 +00:00
parent d682d8e008
commit 659d6a9e7b
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=14006
1 changed files with 9 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -804,22 +804,23 @@ to /etc/mail/sendmail.cf.</programlisting>
UUCP.</para> UUCP.</para>
<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:</para> services for your domain. For example, if your company's domain is
<hostid>example.com</hostid>:</para>
<programlisting>myco.com. MX 10 myco.com. <programlisting>example.com. MX 10 example.com.
MX 20 myisp.com.</programlisting> MX 20 myisp.com.</programlisting>
<para>Only one host should be specified as the final recipient <para>Only one host should be specified as the final recipient
(add <literal>Cw myco.com</literal> in (add <literal>Cw example.com</literal> in
<filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">myco.com</hostid>).</para> <filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">example.com</hostid>).</para>
<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">myco.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 <application>Sendmail</application> will automatically deliver it to the
secondary MX site, i.e. your Internet provider (<hostid role="domainname">myisp.com</hostid>). The secondary MX secondary MX site, i.e. your Internet provider (<hostid role="domainname">myisp.com</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">myco.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>
@ -830,9 +831,9 @@ to /etc/mail/sendmail.cf.</programlisting>
/usr/sbin/ppp -direct pppmyisp</programlisting> /usr/sbin/ppp -direct pppmyisp</programlisting>
<para>If you are going to create a separate login script for a <para>If you are going to create a separate login script for a
user you could use <command>sendmail -qRmyco.com</command> user you could use <command>sendmail -qRexample.com</command>
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 myco.com 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>