home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 14 Text
/
14-Text.zip
/
GATE131B.ZIP
/
gateways.lst
< prev
next >
Wrap
File List
|
1994-07-07
|
5KB
|
118 lines
$File: gateways.lst
$Revision Date: July 6, 1994
FidoNet <-> UUCP Approved Sites
(Authorized to use GUUCP flag in Fidonet Nodelist)
via Anonymous-FTP:
ftp.fidonet.org:/pub/fidonet/info/gateways.lst
via Gopher: gopher.fidonet.org
Corrections to:
Hostmaster
via Fidonet: Burt Juda at 1:1/31
via Internet: hostmaster@fidonet.fidonet.org
Following is a list of Gateways which have Passed the tests required
for gating mail in the FidoNet to Internet direction.
This does *NOT* necessarily mean that the return traffic will be routed
back thru these sites (that is governed by other things). Sites shown
with an asterisk (*) do NOT handle mail in the Internet -> FidoNet
direction.
All of these systems have passed the tests conducted by
the Hostmaster and genuinely are allowed to carry the GUUCP flag and
do allow gating of mail from ANY Node.
To use any other site other than those in this list, you should
check with the SysOp at the gateway node *before* attempting to send any
traffic to them for gating.
Note that this list includes ONLY those sites registered in the .fidonet.org
Domain. There are other sites which operate gateways which are NOT handled
by the .fidonet.org Domain-Name-Server. Those sites operate TOTALLY on
their own and are NOT sanctioned by the Hostmaster. If you have a problem
with such a site, please communicate DIRECTly with the SysOp of that site,
I do not want to hear of problems with sites which are not registered
in the DNS.
I do NOT want to hear about "additions or corrections" from THIRD parties,
only from the Gateway operators themselves.
Requirements for flying the GUUCP Flag
--------------------------------------
In order to be authorized to use the GUUCP flag in the FidoNet NODELIST,
a gateway site *must* pass ALL mail in the FidoNet -> Internet direction
thru the gateway *regardless* of origination (sites are allowed to use
whatever utilities at their disposal to block messages from Non-FidoNet
Zones if they desire) *AND* must be registered with the Hostmaster and
operate in the .fidonet.org domain. Sites may NOT display the GUUCP flag
if the traffic passing thru their gateway passes onto the Internet as part
of any other domain.
Burt Juda
Hostmaster, .fidonet.org
Sitename Node Location
======== ==== ========
nisc 1:1/31 Piscataway, NJ
afitamy 1:110/300
americon 1:373/26
baobab 1:109/151 Washington, DC
bdragon 1:333/401
beacon.dev.com 1:105/30
branch 1:369/11 Pompano Beach, FL
camphq 1:2606/533
cbr 3:620/262 Canberra ACT Aust.
csource 3:632/348 Doveton, VIC, Aust.
dawggon 1:105/6 Portland, OR
dehnbase 1:204/9
edgfrvr 1:300/8
emdisle 1:300/14
fidour 4:850/0
gisatl * 1:133/411 Atlanta, GA
jadpc2 1:202/723
kisbbs * 1:3624/6
mcws 1:102/851 Los Angeles, CA
mdf * 1:382/39 Austin, TX
mechanic 1:3603/330
nwark 1:391/1060 Fayetteville, AR
ocitor * 1:124/2206
okgate 1:147/3660
paranet 1:104/422
puddle 1:105/42 Portland, OR
rccons 1:129/220
rochgte 1:2613/333 Rochester, NY
shelter 1:125/5109
solitud 1:300/23
spuzz * 1:2606/534
therose 1:105/7 Portland, OR
tvk 1:249/128
urchin 1:106/88 Houston, YX
vkom 1:101/316
webfido 1:250/406
wsyd 1:325/2
wmeonlin 1:203/2 Sacramento, CA
zorro9 1:16/390
Sites which have recently *FAILED* the latest Testing
-----------------------------------------------------
Sitename Node
-------- ====
ccfcc 1:205/42 Test message never arrived
cmhgate 1:226/20 Test message never arrived
ehsnet 1:233/13 Test message never arrived
hnews 1:141/420 Test message never arrived
kennel 1:143/8 Test message never arrived
memco 1:139/610 Site is seeking a new MX-receiver
terrabit 1:282/341 Test message never arrived