Received: with ECARTIS (v1.0.0; list gopher);
 Sun, 23 Dec 2007 17:40:05 -0600 (CST)
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 1J6aQN-0008Qn-Kr
	for gopher@complete.org; Sun, 23 Dec 2007 17:40:05 -0600
Received: by turquoise.pongonova.net (Postfix, from userid 1000)
	id 74540726; Sun, 23 Dec 2007 17:40:49 -0600 (CST)
Date: Sun, 23 Dec 2007 17:40:49 -0600
From: brian@pongonova.net
To: gopher@complete.org
Subject: [gopher] Final dot required on server request?
Message-ID: <20071223234049.GA10710@pongonova.net>
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
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 Sun,
 23 Dec 2007 17:40:05 -0600
Content-Transfer-Encoding: 8bit
X-archive-position: 1763
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: <mailto:ecartis@complete.org?Subject=help>
List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: Gopher <gopher.complete.org>
X-List-ID: Gopher <gopher.complete.org>
List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe>
List-owner: <mailto:jgoerzen@complete.org>
List-post: <mailto:gopher@complete.org>
List-archive: <http://www.complete.org/mailinglists/archives/>
X-list: gopher

I noticed that PyGopherd does not appear to send a final "." character
prior to terminating the connection, but Bucktooth does.  A quick read
of the RFC leads me to believe the "." is to be expected.  Has this
been deprecated?  It's not a big deal, just need to know how to write
a bit of code to either expect or not expect the dot.

  --Brian