From pepper@reppep.com  Sun Jun 23 21:16:41 2002
Return-Path: <pepper@reppep.com>
Received: from guest.reppep.com (guest.reppep.com [64.81.19.110])
	by hub.freebsd.org (Postfix) with ESMTP id 5EBC937B401
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 23 Jun 2002 21:16:36 -0700 (PDT)
Received: by guest.reppep.com (Postfix, from userid 501)
	id B38E5A86A; Mon, 24 Jun 2002 00:16:39 -0400 (EDT)
Message-Id: <20020624041639.B38E5A86A@guest.reppep.com>
Date: Mon, 24 Jun 2002 00:16:39 -0400 (EDT)
From: Chris Pepper <pepper@rockefeller.edu>
Reply-To: Chris Pepper <pepper@rockefeller.edu>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Clarification for remote MX sendmail explanation (Handbook 18.5.3)
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         39757
>Category:       docs
>Synopsis:       Clarification for remote MX sendmail explanation (Handbook 18.5.3)
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    keramida
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jun 23 21:20:01 PDT 2002
>Closed-Date:    Sun Jul 14 22:17:46 PDT 2002
>Last-Modified:  Sun Jul 14 22:17:46 PDT 2002
>Originator:     Chris Pepper
>Release:        FreeBSD 4.6-STABLE i386
>Organization:
>Environment:
System: FreeBSD guest.reppep.com 4.6-STABLE FreeBSD 4.6-STABLE #0: Tue Jun 18 21:27:59 EDT 2002 pepper@guest.reppep.com:/usr/obj/usr/src/sys/GENERIC i386


	
>Description:
	In the Sendmail chapter of the Handbook, "18.5.3. How can I run a mail server on a dial-up PPP host?" provides an example of how to have an external host provide secondary MX service. Unfortunately, the hostnames were very confusing. I've tried to use more obvious names, but someone who actually uses sendmail should check my changes.
	
>How-To-Repeat:
	
>Fix:
	Patch provided, changing bigco.com to myco.com and smalliap.com to myisp.com, and adding some additional clarification.

--- chapter.sgml.diff begins here ---
Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v
retrieving revision 1.52
diff -u -r1.52 chapter.sgml
--- chapter.sgml	2002/06/11 23:50:46	1.52
+++ chapter.sgml	2002/06/24 04:12:24
@@ -803,33 +803,33 @@
 	<para>There are at least two ways to do this, an alternative
 	  being UUCP.</para>
       
-	<para>The key is to get a Internet site to provide secondary MX
+	<para>The key is to get an full-time Internet server to provide secondary MX
 	  service for your domain.  For example:</para>
 
-	<programlisting>bigco.com.            MX        10      bigco.com.
-                      MX        20      smalliap.com.</programlisting>
+	<programlisting>myco.com.            MX        10      myco.com.
+                      MX        20      myisp.com.</programlisting>
           
 	<para>Only one host should be specified as the final recipient
-	  (add <literal>Cw bigco.com</literal> in
-	  <filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">bigco.com</hostid>).</para>
+	  (add <literal>Cw myco.com</literal> in
+	  <filename>/etc/mail/sendmail.cf</filename> on <hostid role="domainname">myco.com</hostid>).</para>
           
 	<para>When the sending <command>sendmail</command> is trying to
-	  deliver the mail it will try to connect to you over the modem
+	  deliver the mail it will try to connect to you (<hostid role="domainname">myco.com</hostid>) over the modem
 	  link.  It will most likely time out because you are not online.
 	  <command>sendmail</command> will automatically deliver it to the
-	  secondary MX site, i.e. your Internet provider.  The secondary MX
-	  site will try every
-	  (<literal>sendmail_flags = -bd -q15m</literal> in
-	  <filename>/etc/rc.conf</filename>) 15 minutes to connect to
-	  your host to deliver the mail to the primary MX site.</para>
+	  secondary MX site, i.e. your Internet provider (<hostid role="domainname">myisp.com</hostid>).  The secondary MX
+	  site will then try every
+	  15 minutes (assuming they have <literal>sendmail_flags = -bd -q15m</literal> in
+	  <filename>/etc/rc.conf</filename> or the equivalent) to connect to
+	  your host and deliver the mail to the primary MX host (<hostid role="domainname">myco.com</hostid>).</para>
           
 	<para>You might want to use something like this as a login
 	  script.</para>
 
 	<programlisting>#!/bin/sh
-# Put me in /usr/local/bin/pppbigco
+# Put me in /usr/local/bin/pppmyisp
 ( sleep 60 ; /usr/sbin/sendmail -q ) &amp;
-/usr/sbin/ppp -direct pppbigco</programlisting>
+/usr/sbin/ppp -direct pppmyisp</programlisting>
 
 	<para>If you are going to create a separate login script for a
 	  user you could use <command>sendmail -qRbigco.com</command>
--- chapter.sgml.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: keramida 
State-Changed-When: Sun Jul 14 22:15:16 PDT 2002 
State-Changed-Why:  
I committed a slightly modified version of the patch.  The reference 
to -bd 15m was replaced by `will periodically try to' which is also 
true and doesn't depend on the exact queue timeout that the secondary 
MX might have.  Thanks for an excellent submission. 


Responsible-Changed-From-To: freebsd-doc->keramida 
Responsible-Changed-By: keramida 
Responsible-Changed-When: Sun Jul 14 22:15:16 PDT 2002 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=39757 
>Unformatted:
 	
