<?xml version="1.0"?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN"
"http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="index" title="Text File" newcontext="true">
<p>
Received: with ECARTIS (v1.0.0; list gopher);
 Wed, 01 Aug 2007 11:25:03 -0500 (CDT)
Received: from static-71-170-11-156.dllstx.dsl-w.verizon.net ([71.170.11.156]
 helo=turquoise.pongonova.net)
	by glockenspiel.complete.org with esmtp
	(Exim 4.63)
	id 1IGH0O-0000YF-S9
	for gopher@complete.org; Wed, 01 Aug 2007 11:25:03 -0500
Received: by turquoise.pongonova.net (Postfix, from userid 1000)
	id C908D66B; Wed,  1 Aug 2007 10:27:58 -0500 (CDT)
Date: Wed, 1 Aug 2007 10:27:58 -0500
From: brian@pongonova.net
To: gopher@complete.org
Subject: [gopher] Re: Problem with SiMpLeMaChInEs
Message-ID: &lt;20070801152758.GA18712@pongonova.net&gt;
References: &lt;f705f7020707312020g4a663f25xe9f24544ef661d9f@mail.gmail.com&gt;
 &lt;618171.61504.qm@web35503.mail.mud.yahoo.com&gt;
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: &lt;618171.61504.qm@web35503.mail.mud.yahoo.com&gt;
User-Agent: Mutt/1.5.5.1i
X-Spam-Status: No (score 0.6): AWL=0.000, NO_REAL_NAME=0.55
X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Wed,
 01 Aug 2007 11:25:03 -0500
Content-Transfer-Encoding: 8bit
X-archive-position: 1681
X-ecartis-version: Ecartis v1.0.0
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
X-original-sender: brian@pongonova.net
Precedence: bulk
Reply-to: gopher@complete.org
List-help: &lt;mailto:ecartis@complete.org?Subject=help&gt;
List-unsubscribe: &lt;mailto:gopher-request@complete.org?Subject=unsubscribe&gt;
List-software: Ecartis version 1.0.0
List-Id: Gopher &lt;gopher.complete.org&gt;
X-List-ID: Gopher &lt;gopher.complete.org&gt;
List-subscribe: &lt;mailto:gopher-request@complete.org?Subject=subscribe&gt;
List-owner: &lt;mailto:jgoerzen@complete.org&gt;
List-post: &lt;mailto:gopher@complete.org&gt;
List-archive: &lt;http://www.complete.org/mailinglists/archives/&gt;
X-list: gopher
</p>
<p>It doesn&#x27;t appear that the authors of this RFC had it in mind that
gophers would *always* appear on port 70:
</p>
<p>    There is nothing to prevent secondary servers or services from running
    on otherwise named servers or ports other than 70, however these
    should be reachable via a primary server.
</p>
<p>Also, the word &quot;should&quot; doesn&#x27;t mandate compliance. It&#x27;s a
recommendation.
</p>
<p>  --Brian
</p>
<p>On Wed, Aug 01, 2007 at 09:08:42AM -0700, JumpJet Mailbox wrote:
&gt; This is the last I will say about Port 70.  It comes from the second paragraph of the Introduction, in the Gopher Protocol RFC1436:
&gt;
&gt;      Gopher servers should listen on port 70 (port 70 is assigned to Internet Gopher by IANA).
&gt;
</p>
<p></p>
<p></p>
</card>
</wml>
