Path: utzoo!attcan!uunet!decwrl!hayes.ims.alaska.edu!accuvax.nwu.edu!nucsrl!telecom-request
From: hayes!tnixon@uunet.uu.net (Toby Nixon)
Newsgroups: comp.dcom.telecom
Subject: Re: Accessing Archives Through Mail
Message-ID: <13801@accuvax.nwu.edu>
Date: 18 Oct 90 13:39:59 GMT
Sender: news@accuvax.nwu.edu
Organization: Hayes Microcomputer Products, Norcross, GA
Lines: 28
Approved: Telecom@eecs.nwu.edu
X-Submissions-To: telecom@eecs.nwu.edu
X-Administrivia-To: telecom-request@eecs.nwu.edu
X-Telecom-Digest: Volume 10, Issue 745, Message 6 of 13


In article <13626@accuvax.nwu.edu>, cybrspc!roy@cs.umn.edu (Roy M.
Silvernail) writes:

> Toby, I wonder if you would be kind enough to ferret out an
> unambiguous path to pucc.princeton.edu from a major backbone? 

My requests from back with the "From:" field containing:

	From: uunet!pucc.PRINCETON.EDU!BITFTP1

To be honest, I don't know enough about the internet backbone to be
able to offer more than that.  Perhaps if you just used this address
instead of "bitftp@pucc.princeton.edu" it might work, since UUNET
apparently knows how to get there.


Toby Nixon, Principal Engineer   | Voice:   +1-404-449-8791  AT&T:  !tnixon
Hayes Microcomputer Products Inc.| Fax:     +1-404-447-0178  CIS: 70271,404
P.O. Box 105203                  | UUCP: uunet!hayes!tnixon  MCI:  267-0805
Atlanta, Georgia  30348  USA     | Internet:      hayes!tnixon@uunet.uu.net


[Moderator's Note: 'bitftp@pucc.princeton.edu' and 'bitftp@pucc.bitnet' 
are one and the same. Use whichever works best. As Toby points out,
you can route through uunet, but I suggest you avoid it when possible,
as those folks (uunet) get enough abuse as it is from fellow travelers
passing through on their nickle.  PAT]