pozar@kumr.lns.com (Tim Pozar) (05/15/91)
Volume 8, Number 19 13 May 1991
+---------------------------------------------------------------+
| _ |
| / \ |
| /|oo \ |
| - FidoNews - (_| /_) |
| _`@/_ \ _ |
| FidoNet (r) | | \ \\ |
| International BBS Network | (*) | \ )) |
| Newsletter ______ |__U__| / \// |
| / FIDO \ _//|| _\ / |
| (________) (_/(_|(____/ |
| (jm) |
+---------------------------------------------------------------+
Editor in Chief: Vince Perriello
Editors Emeritii: Thom Henderson, Dale Lovell
Chief Procrastinator Emeritus: Tom Jennings
Copyright 1991, Fido Software. All rights reserved. Duplication
and/or distribution permitted for noncommercial purposes only.
For use in other circumstances, please contact Fido Software.
FidoNews is published weekly by and for the Members of the
FidoNet (r) International Amateur Electronic Mail System. It is
a compilation of individual articles contributed by their authors
or authorized agents of the authors. The contribution of articles
to this compilation does not diminish the rights of the authors.
You are encouraged to submit articles for publication in
FidoNews. Article submission standards are contained in the file
ARTSPEC.DOC, available from node 1:1/1. 1:1/1 is a Continuous
Mail system, available for network mail 24 hours a day.
Fido and FidoNet are registered trademarks of Tom Jennings of
Fido Software, Box 77731, San Francisco CA 94107, USA and are
used with permission.
Opinions expressed in FidoNews articles are those of the authors
and are not necessarily those of the Editor or of Fido Software.
Most articles are unsolicited. Our policy is to publish every
responsible submission received.
Table of Contents
1. EDITORIAL ................................................ 1
From the Editor's Chair .................................. 1
2. ARTICLES ................................................. 2
Gateway Complaint Decision ............................... 2
Sending mail through networks ............................ 4
3. COLUMNS .................................................. 8
Talk Me Through It, Honey ................................ 8
4. LATEST VERSIONS .......................................... 11
Latest Software Versions ................................. 11
5. NOTICES .................................................. 16
A_THEIST Echo now available .............................. 16
And more!
FidoNews 8-19 Page 1 13 May 1991
=================================================================
EDITORIAL
=================================================================
Hi there. How have you been this week?
Things have been interesting around here of late. Some of the
events of the past few weeks seem to merit additional comment,
in my opinion.
First and most important of all, I just built a big disk file
with all the changes I had to make to the Current Versions list.
I then proceeded to type the wrong command and wrote all over
the file. If your change isn't there, please send it again.
Next, I'd like to say that about 70% of the Zone 1 Coordinators
should resign. If you would like to know which ones I am
referring to, take the Worldpol roll-call, and delete the ones
who voted (regardless of their choice). The remaining NC's have
failed in their mission to represent their net to the rest of
their Zone and FidoNet at large, and as such need replacement.
Now I have a more serious question -- has anyone within FidoNet
carried out any careful experiments to test the veracity of the
assertions against Prodigy? We've come just short of sliming
them, now it would be nice for us to put our vaunted computer
literacy on the line and check it out ourselves!
Thanks for being there. Have a great week.
Vince
-----------------------------------------------------------------
FidoNews 8-19 Page 2 13 May 1991
=================================================================
ARTICLES
=================================================================
Gateway Complaint Decision
Matt Whelan, 3:3/1000
International Coordinator
It is now some time since I received a Policy Complaint/Appeal
from Bob Moravsik, following rejections from RC13 and ZC1. My
apologies to all for the delay in publishing the result.
The complaint was lengthy and detailed, so I'll provide my
'instant summary' rather than list it all here.
In essence, Bob complained that a directive from his then-NC,
Glen Johnson, contradicted the FidoNet<tm> Gateway Document
adopted by me last year.
The NC directive, to his hub coordinators, insisted they pass on
all mail for their nodes, regardless of origin. It also insisted
they should accept calls from any system, whether or not it was
a FidoNet node.
Bob complained this forced the Hub Coords to act as Gateway
systems under FidoNet policy. Thus they would be required to
provide outbound gating facilities as well, despite the technical
complications this involved.
The decision at all levels was made more difficult by the
complaint's somewhat unclear intent: was it a protest at the NC's
imposition of a policy at all, or at the content of the policy?
The complaint was rejected at the RC and ZC levels. My feelings
were that these decisions were mostly based on the first premise,
and in that light were entirely correct.
I believe an NC _is_ entitled to set a policy for HCs, as they
are the NC's "deputies" and should run their portion of the net
the way the NC would. However, if the content of the NC/Hub policy
is contrary to (or more restrictive than, or different to, or . . .)
FidoNet policy, then the enforcement of such NC/Hub policy could
result in valid FidoNet policy complaints.
Thus the Moravsik/Johnson decision finally came down to the
content of the NC/Hub policy, and whether it really did directly
contravene the provisions of the Gateway Document.
The following is my 'ruling' on that aspect, as communicated
directly to Bob Moravsik and Z1C George Peace a month or so ago.
At that time it was also presented to the Zone Coordinators'
Council for comment/objection (there has been very little of
either), as I considered it an important "policy interpretation"
issue.
FidoNews 8-19 Page 3 13 May 1991
I welcome any comments on the issue, either here or in netmail
to me at 3:712/627 or 3:3/1000.
-Matt
-----------------------------------------------------------------
I believe Bob Moravsik's complaint/appeal against Glen Johnson's
Hub Coordinators' policy to be technically correct and valid.
However, I reject it at this time.
When I adopted the Gateway document I noted it was not intended
to hinder communications, and that I would allow time for its
implementation. Given that there was no working software to
facilitate 'correct' communication at the time the policy was
adopted, I am prepared to wait for a reasonable time to allow
such systems to be developed.
The fact there is evidence of serious efforts to develop a
standard, and the software, makes me comfortable with this
decision.
In the meantime, I accept each NC's individual right to choose
whether (or not) to accept calls/mail from non-FidoNet nodes
under the Gateway document's 'local experimentation' provisions.
I believe once such a call has been accepted, any mail correctly
addressed to a node in that local net must reach its intended
recipient.
I do not consider such operation a 'Gateway' service _at this
time_. Thus there is no obligation on anyone in FidoNet to
route return/outbound mail from FidoNet nodes to OtherNet
addresses. Systems routing inbound mail are advised to run one
of the several Netmail 'bouncers' which are capable of placing a
warning in the inbound message. This warning would point out the
origin system is unknown, and replies should not be routed back
via the inbound system(s).
Please note this an intentional and temporary relaxation of
existing policy and, as such, will not always be acceptable.
As the software for correct inter-network communication develops,
the full intent of the Gateway document will be enforced to
ensure people switch to this much-needed, and beneficial,
new technology.
-----------------------------------------------------------------
FidoNews 8-19 Page 4 13 May 1991
Roberto Zanasi
Fido 2:332/504.2
Sending mail through networks
Beggining with fidonews809 (Volume 8, n. 9, 4 march 1991), a
little announce appeared at the bottom of the fidonews issue: its
title is "Remember Campers!!!", and it explains "how to send mail
from an Internet site or a smart UUCP site TO a user that calls a
Fido-Net system"
Here I would like to give a more complete explanation of how to
send mail from one network to another. Well, someone else has
already done all the work, and I am only trying to give a
contribution to their efforts. The following is the complete
Inter-Network Mail Guide (Copyright 1990 by John J. Chew), a
document which explains methods of sending mail from a network to
another (when possible, of course). So, let's begin...
[P.S. I hope that I am not violating the Copyright Notice, since
the Inter-Network Mail Guide is distributed for non commercial
purposes, and the file is distributed intact. I have only
reformatted it (except only two lines, which are not
reformattable), in order to fit the margins specifications
written in fnewsart.doc.]
+++cut here (beginning of internetwork guide)+++
Inter-Network Mail Guide - Copyright 1990 by John J. Chew
$Header: netmail,v 1.12 90/07/06 20:38:28 john Exp $
For those of you who were wondering what happened to the June
1990 issue, there wasn't one, because of a lack of important
changes to the data, and because I've been busy with other
things. Even worse (:-), there will not be an August 1990 issue
as I will be temporarily between net addresses as I take a nice
long holiday between jobs on different continents. If you have
information to add or requests for subscriptions, send them as
usual to me at <poslfit@gpu.UTCS.UToronto.CA> and they should
catch up to me with some delay wherever I end up. I'm off to
enjoy my summer now, bye! -- John
COPYRIGHT NOTICE
This document is Copyright 1990 by John J. Chew. All rights
reserved. Permission for non-commercial distribution is hereby
granted, provided that this file is distributed intact, including
this copyright notice and the version information above.
Permission for commercial distribution can be obtained by
contacting the author as described below.
FidoNews 8-19 Page 5 13 May 1991
INTRODUCTION
This file documents methods of sending mail from one network to
another. It represents the aggregate knowledge of the readers of
comp.mail.misc and many contributors elsewhere. If you know of
any corrections or additions to this file, please read the file
format documentation below and then mail to me: John J. Chew
<poslfit@gpu.utcs.utoronto.ca>. If you do not have access to
electronic mail (which makes me wonder about the nature of your
interest in the subject, but there does seem to be a small such
population out there) you can call me during the month of July at
+1 416 979 7166 between 11:00 and 24:00 EDT (UTC-4h) and most
likely talk to my answering machine (:-).
DISTRIBUTION
(news) This list is posted monthly to Usenet newsgroups
comp.mail.misc and news.newusers.questions.
(mail) I maintain a growing list of subscribers who receive each
monthly issue by electronic mail, and recommend this to anyone
planning to redistribute the list on a regular basis.
(FTP) Internet users can fetch this guide by anonymous FTP as
~ftp/pub/docs/ internetwork-mail-guide on Ra.MsState.Edu
(130.18.80.10 or 130.18.96.37) [Courtesy of Frank W. Peters]
(Listserv) Bitnet users can fetch this guide from the Listserv at
UNMVM. Send mail to LISTSERV@UNMVM with blank subject and body
consisting of the line "GET NETWORK GUIDE". [Courtesy of Art
St. George]
HOW TO USE THIS GUIDE
Each entry in this file describes how to get from one network to
another. To keep this file at a reasonable size, methods that can
be generated by transitivity (A->B and B->C gives A->B->C) are
omitted. Entries are sorted first by source network and then by
destination network. This is what a typical entry looks like:
#F mynet
#T yournet
#R youraddress
#C contact address if any
#I send to "youraddress@thegateway"
For parsing purposes, entries are separated by at least one blank
line, and each line of an entry begins with a `#' followed by a
letter. Lines beginning with `# ' are comments and need not be
parsed. Lines which do not start with a `#' at all should be
ignored as they are probably mail or news headers.
#F (from) and #T (to) lines specify source and destination
networks. If you're sending me information about a new network,
please give me a brief description of the network so that I can
add it to the list below. The abbreviated network names used in
#F and #T lines should consist only of the characters a-z, 0-9
and `-' unless someone can make a very convincing case for their
favourite pi character.
FidoNews 8-19 Page 6 13 May 1991
These are the currently known networks with abbreviated names:
applelink AppleLink (Apple Computer, Inc.'s in-house
network)
bitnet international academic network
bix Byte Information eXchange: Byte magazine's
commercial BBS
bmug Berkeley Macintosh Users Group
compuserve commercial time-sharing service
connect Connect Professional Information Network
(commercial)
easynet Easynet (DEC's in-house mail system)
envoy Envoy-100 (Canadian commercial mail service)
fax Facsimile document transmission
fidonet PC-based BBS network
geonet GeoNet Mailbox Systems (commercial)
internet the Internet
mci MCI's commercial electronic mail service
mfenet Magnetic Fusion Energy Network
nasamail NASA internal electronic mail
peacenet non-profit mail service
sinet Schlumberger Information NETwork
span Space Physics Analysis Network (includes HEPnet)
sprintmail Sprint's commercial mail service (formerly
Telemail)
thenet Texas Higher Education Network
#R (recipient) gives an example of an address on the destination
network, to make it clear in subsequent lines what text requires
subsitution.
#C (contact) gives an address for inquiries concerning the
gateway, expressed as an address reachable from the source (#F)
network. Presumably, if you can't get the gateway to work at all,
then knowing an unreachable address on another network will not
be of great help.
#I (instructions) lines, of which there may be several, give
verbal instructions to a user of the source network to let them
send mail to a user on the destination network. Text that needs
to be typed will appear in double quotes, with C-style escapes if
necessary.
#F applelink
#T internet
#R user@domain
#I send to "user@domain@internet#"
#I domain can be be of the form "site.bitnet", address must be
#I <35 characters
#F bitnet
#T internet
#R user@domain
#I Methods for sending mail from Bitnet to the Internet vary
#I depending on what mail software is running at the Bitnet site
#I in question. In the best case, users should simply be able to
FidoNews 8-19 Page 7 13 May 1991
#I send mail to "user@domain". If this doesn't work, try
#I "user%domain@gateway" where "gateway" is a regional
#I Bitnet-Internet gateway site. Finally, if neither of these
#I works, you may have to try hand-coding an SMTP envelope for
#I your mail. If you have questions concerning this rather terse
#I note, please try contacting your local postmaster or system
#I administrator first before you send me mail -- John Chew
#I <poslfit@gpu.utcs.utoronto.ca>
#F compuserve
#T fax
#R +1 415 555 1212
#I send to "FAX 14155551212" (only to U.S.A.)
#F compuserve
#T internet
#R user@domain
#I send to ">INTERNET:user@domain"
#F compuserve
#T mci
#R 123-4567
#I send to ">MCIMAIL:123-4567"
#F connect
#T internet
#R user@domain
#I send to CONNECT id "DASNET"
#I first line of message: "\"user@domain\"@DASNET"
#F easynet
#T bitnet
#R user@site
#C DECWRL::ADMIN
#I from VMS use NMAIL to send to
#I "nm%DECWRL::\"user@site.bitnet\""
#I from Ultrix
#I send to "user@site.bitnet" or if that fails
#I (via IP) send to "\"user%site.bitnet\"@decwrl.
-----------------------------------------------------------------
FidoNews 8-19 Page 8 13 May 1991
=================================================================
COLUMNS
=================================================================
Henry Clark
1:124/6120
Interactive Video II --
Late one night, I was watching taped episodes of Pee Wee and
his video phone rings. Pee Wee gets into the booth, pulls down
the tropical paradise background matte, puts on an outrageous
hat and picks up the tin can ear piece. Onto his screen comes
a guy in a couch trying to order pizza. Wrong number...
A two by two meter HDTV screen hangs flush against the wall in
my home-office. I call up my PC vid-message program and begin
scanning through the video segments available in the echo
areas. As I hit the reply key, the camera record light comes
on and I make an obscene hand gesture to emphasize my point.
The next day I am banned from Fidonet for being excessively
annoying...
As I wake up somewhat disoriented, I decide to finish this
tyrade against the phone companies.
Last time I tried to outline the technical aspects of digital
video transmission. This week I'll tell you about some of the
methods and applications for interactive video.
Chuckin' from the Cheap Seats --
First let me thank Alan Gilbertson who runs the CSFSO Telecom
BBS down in Clearwater Florida for his insightful critique of
the previous article. The biggest mistake I made was to imply
that the current limits of transmission technology are not
going to be overcome any time soon.
Specifically, the current limit of 2.5 Gigabits per second is
not chiseled in stone. I have reports of 25,000 Gigabits per
seconds digital and Alan clearly pointed out the increases
available through multiplexing. I will continue to speak of
'full motion' video using 'no-loss' compression techniques
because that is the quality that I believe general usage will
require. It should be obvious that the bits per second
required to achieve this will drop over time.
Players Dept. --
FidoNews 8-19 Page 9 13 May 1991
Analog systems, like Orchard Communications, Wallingford CT, are
by far the least expensive. Orchard modulates an FM or AM
signal onto fiber using a laser. I believe that at the end
points of a network, cost may justify the use of analog
transmission. As with coaxial cable systems, every video
channel is available at every site ( scrambled or not ), and
this raises privacy issues. I tend to lean to the digital
format anyway.
Dedicated systems, like Grass Valley Group, Grass Valley
California, use DS3 digital switching systems. The network
controller is a Sun workstation, with various remote dial in
capabilities. GVG markets several device control stations, for
panning cameras or muting and they are by far the largest
Interactive Video products company. Their switching system has
some unique video manipulation features, but can't be used for
other TelCo functions, like bundling voice channels.
Cross connect systems, like Rockwell, Tellabs, Digital Switch
and AT&T build, are DS3 or DS1 digital switching systems used
by TelCos for trunk routing control. These cross connects have
point-to-point and point-to-multiple broadcast capabilities
which make them suitable for Interactive Video and
Conferencing. They are also owned and operated by the TelCos,
which allows for cost allocations favorable to the video
network users. PC based applications control the cross
connects, including remote dial in. The general goal is to use
the DS3 capacity of the local TelCos ( local exchange carriers
) and the Long Distance companies ( inter exchange carriers )
in a demand driven ( customer controlled ) network.
The costs for digital fiber transmission are staggering. 20
miles of working fiber could run you a cool million bucks. 45
Megabit Video Codecs are 5000 bucks per channel. A cross
connect will set you back 100 k. Not to mention the cameras,
monitors and control software and training to operate it all.
Who can afford it ?
We're In the Money Dept. --
Schools systems with government and TelCo backing. Courts and
law enforcement who spend millions transporting prisoners.
Libraries with duplication of information. Hospitals whose
insurance rates ( and need for quality staff ) have
skyrocketed.
What do all these have in common ? They are all tax payer
funded. They are also all suitable for the kind of tariff
'abatement' required to get the price down to a reasonable
level. You see, a lot of the price is the built in rates the
transport companies have to charge. The emphasis on transport
is based on the high cost of laying fiber. This brings up the
whole regulatory environment argument that has been raging
since the Bell breakup. Outside the US, especially in the
government owned TelCos of Europe, the situation is similar
FidoNews 8-19 Page 10 13 May 1991
because the prices are also artificially set.
There is going to come a time when literally everyone is fed up
with the communications system in the US, and then we'll start
to see big changes. Fidonews at 11, channel 1-800....
-----------------------------------------------------------------
FidoNews 8-19 Page 11 13 May 1991
=================================================================
LATEST VERSIONS
=================================================================
Latest Software Versions
MS-DOS Systems
--------------
Bulletin Board Software
Name Version Name Version Name Version
DMG 2.93 Phoenix 1.3 TAG 2.5g
Fido 12t+ QuickBBS 2.66 TBBS 2.1
GSBBS 3.02 RBBS 17.3B TComm/TCommNet 3.4
Lynx 1.30 RBBSmail 17.3B Telegard 2.5
Kitten 2.16 RemoteAccess 1.00* TPBoard 6.1
Maximus 1.02 SLBBS 1.77A Wildcat! 2.55
Opus 1.14+ Socrates 1.10 WWIV 4.12
PCBoard 14.5 SuperBBS 1.10 XBBS 1.17
Network Node List Other
Mailers Version Utilities Version Utilities Version
BinkleyTerm 2.40 EditNL 4.00 ARC 7.0
D'Bridge 1.30 MakeNL 2.31 ARCAsim 2.30
Dutchie 2.90C ParseList 1.30 ARCmail 2.07
FrontDoor 1.99c Prune 1.40 ConfMail 4.00
PRENM 1.47 SysNL 3.14 Crossnet v1.5
SEAdog 4.60* XlatList 2.90 DOMAIN 1.42
TIMS 1.0(Mod8) XlaxDiff 2.40* EMM 2.02
XlaxNode 2.40* 4Dog/4DMatrix 1.18
Gmail 2.05
GROUP 2.16
GUS 1.30
HeadEdit 1.18
IMAIL 1.10
InterPCB 1.31
LHARC 2.10
MSG 4.1
MSGED 2.06
MSGTOSS 1.3
Oliver 1.0a
PK[UN]ZIP 1.20
QM 1.0
QSORT 4.03
ScanToss 1.28
Sirius 1.0x
SLMAIL 1.36
StarLink 1.01
TagMail 2.41
FidoNews 8-19 Page 12 13 May 1991
TCOMMail 2.2
Telemail 1.27
TMail 1.15
TPBNetEd 3.2
TosScan 1.00
UFGATE 1.03
XRS 4.10*
XST 2.3e
ZmailH 1.14
OS/2 Systems
------------
Bulletin Board Software Network Mailers Other Utilities
Name Version Name Version Name Version
Maximus-CBCS 1.02 BinkleyTerm 2.40 Parselst 1.32
ConfMail 4.00
EchoStat 6.0
oMMM 1.52
Omail 3.1
MsgEd 2.06
MsgLink 1.0C
MsgNum 4.14
LH2 0.50
PK[UN]ZIP 1.02
ARC2 6.00
PolyXARC 2.00
Qsort 2.1
Raid 1.0
Remapper 1.2
Tick 2.0
VPurge 2.07
Xenix/Unix
----------
BBS Software Mailers Other Utilities
Name Version Name Version Name Version
BinkleyTerm 2.30b Unzip 3.10
ARC 5.21
ParseLst 1.30b
ConfMail 3.31b
Ommm 1.40b
Msged 1.99b
Zoo 2.01
C-Lharc 1.00
FidoNews 8-19 Page 13 13 May 1991
Omail 1.00b
Apple II
----------
Bulletin Board Software Network Mailers Other Utilities
Name Version Name Version Name Version
GBBS Pro 2.1 Fruity Dog 2.0* ShrinkIt 3.23
DDBBS + 7.4* ShrinkIt GS 1.04
deARC2e 2.1
ProSel 8.69*
Apple CP/M
----------
Bulletin Board Software Network Mailers Other Utilities
Name Version Name Version Name Version
Daisy v2j Daisy Mailer 0.38 Nodecomp 0.37
MsgUtil 2.5
PackUser v4
Filer v2-D
UNARC.COM 1.20
Macintosh
---------
Bulletin Board Software Network Mailers Other Utilities
Name Version Name Version Name Version
Red Ryder Host 2.1 Tabby 2.2 MacArc 0.04
Mansion 7.15 Copernicus 1.0 ArcMac 1.3
WWIV (Mac) 3.0 LHArc 0.41
Hermes 1.5 StuffIt Classic 1.6
FBBS 0.91 Compact Pro 1.30
Precision Systems 0.95b* TImport 1.92
TeleFinder Host 2.12T10 TExport 1.92
Timestamp 1.6
Tset 1.3
Import 3.2
Export 3.21
Point System Software Sundial 3.2
PreStamp 3.2
Name Version OriginatorII 2.0
FidoNews 8-19 Page 14 13 May 1991
AreaFix 1.6
Copernicus 1.0 Mantissa 3.21
CounterPoint 1.09 Zenith 1.5
Eventmeister 1.0
TSort 1.0
Mehitable 2.0
UNZIP 1.02c
Zip Extract 0.10
Amiga
-----
Bulletin Board Software Network Mailers Other Utilities
Name Version Name Version Name Version
Falcon CBBS 0.45 BinkleyTerm 1.00 AmigArc 0.23
Paragon 2.082+ TrapDoor 1.50 AReceipt 1.5
TransAmiga 1.07 WelMat 0.44 booz 1.01
ConfMail 1.12
ChameleonEdit 0.10
ElectricHerald1.66
Lharc 1.30
Login 0.18
MessageFilter 1.52
oMMM 1.49b
ParseLst 1.64
PkAX 1.00
PolyxAmy 2.02
RMB 1.30
Roof 44.03
RoboWriter 1.02
Rsh 4.06
Skyparse 2.30
Tick 0.75
TrapList 1.12
UNZIP 1.31
Yuck! 1.61
Zippy (Unzip) 1.25
Zoo 2.01
Atari ST/TT
-----------
Bulletin Board Network Node List
Software Version Mailer Version Utilities Version
FIDOdoor/ST 2.2.3* BinkleyTerm 2.40l ParseList 1.30
QuickBBS/ST 1.02 The BOX 1.20 Xlist 1.12
Pandora BBS 2.41c EchoFix 1.20
GS Point 0.61 sTICK/Hatch 5.50*
LED ST 1.00
MSGED 1.96S
FidoNews 8-19 Page 15 13 May 1991
Archiver Msg Format Other
Utilities Version Converters Version Utilities Version
LHARC 0.60 TB2BINK 1.00 ConfMail 4.03
LHARC2 3.18* BINK2TB 1.00 ComScan 1.02
ARC 6.02 FiFo 2.1m* Import 1.14
PKUNZIP 1.10 OMMM 1.40
Pack 1.00
FastPack 1.20
FDrenum 2.2.7*
Trenum 0.10
Archimedes
----------
BBS Software Mailers Utilities
Name Version Name Version Name Version
ARCbbs 1.44 BinkleyTerm 2.03 Unzip 2.1TH
ARC 1.03
!Spark 2.00d
ParseLst 1.30
BatchPacker 1.00
+ Netmail capable (does not require additional mailer software)
* Recently changed
Utility authors: Please help keep this list up to date by
reporting new versions to 1:1/1. It is not our intent to list
all utilities here, only those which verge on necessity.
-----------------------------------------------------------------
FidoNews 8-19 Page 16 13 May 1991
=================================================================
NOTICES
=================================================================
Christopher Baker
Rights On! 1:374/14
A_THEIST Echo Available
A_theism means free of religion in the way a_political means
free of politics or a_sexual means free of sex
characteristics or drives.
With that in mind and ever cognizant of the continued
pressure of religion to intrude itself into our government
and its operations, the A_THEIST Echo is provided to inform
and alarm and hopefully wake up the sleeping and too long
silent majority to the peril on our doorstep.
It is, at present, a non-backbone Echo Hosted and Moderated
by Rights On! [1:374/14] and Christopher Baker [card
carrying member of American Atheists, Inc.]. Initial links
will be provided from this system to any and all who request
same.
The Echo is open to anyone who can discuss, without
proselytizing, the extreme desirability of maintaining the
absolute separation of State and church in this country as
provided for in our Constitution.
A sample of the first few messages and the statement of
purpose of the Echo is available as A_THEIST.ZIP from this
system anytime except 0100-0130 and 0500-0800 ET [USR HST
ds online] if you wish to get an idea of whether to commit
disk space to the Echo.
I hope you will join us or ask your Sysop to request a link
via Netmail to 1:374/14.
TTFN.
Chris
-----------------------------------------------------------------
The Interrupt Stack
15 Aug 1991
FidoNews 8-19 Page 17 13 May 1991
5th annual Z1 Fido Convention - FidoCon '91 "A New Beginning"
Sheraton Denver West August 15 through August 18 1991.
8 Sep 1991
25th anniversary of first airing of Star Trek on NBC!
7 Oct 1991
Area code 415 fragments. Alameda and Contra Costa Counties
will begin using area code 510. This includes Oakland,
Concord, Berkeley and Hayward. San Francisco, San Mateo,
Marin, parts of Santa Clara County, and the San Francisco Bay
Islands will retain area code 415.
1 Nov 1991
Area code 301 will split. Area code 410 will consist of the
northeastern part of Maryland, as well as the eastern shore.
This will include Baltimore and the surrounding area. Area 301
will include southern and western parts of the state,
including the areas around Washington DC. Area 410 phones will
answer to calls to area 301 until November, 1992.
1 Feb 1992
Area code 213 fragments. Western, coastal, southern and
eastern portions of Los Angeles County will begin using area
code 310. This includes Los Angeles International Airport,
West Los Angeles, San Pedro and Whittier. Downtown Los
Angeles and surrounding communities (such as Hollywood and
Montebello) will retain area code 213.
1 Dec 1993
Tenth anniversary of Fido Version 1 release.
5 Jun 1997
David Dodell's 40th Birthday
If you have something which you would like to see on this
calendar, please send a message to FidoNet node 1:1/1.
-----------------------------------------------------------------
ANEWS Mail Hauler Needed
By Randy Edwards
1:141/552.0
For those of you that don't know what ANEWS is, ANEWS is an
acronym for "Alternative NEWS" and is a backbone echo in the
FidoNet. ANEWS is made up of various "alternative" news and
points of view -- opinions and news not normally found in our
corporate-controlled mass media.
FidoNews 8-19 Page 18 13 May 1991
I'm the moderator of ANEWS and have been more or less shocked
at it's success. ANEWS has existed for well over a year and has
grown in size, scope and traffic. The echo is truly
international in scope.
However, due to an upcoming move of mine across the country,
the ANEWS echo in need of someone to 'haul' mail for ANEWS.
Specifically, the ANEWS mail hauler would have to poll a 2400
bps non-nodelisted FidoNet-compatible system in New York City
and drop the news off at a FidoNet link so that the ANEWS
traffic can go out over the FidoNet echomail backbone to the
rest of the world.
If I could find a node IN New York City that is local to the
718-448-xxxx telephone echange to move this mail, it'd mean
local calls for the 'mail hauler'. If anyone is willing to be
a 'mail hauler' for the ANEWS echo (regardless of where you are)
please contact me, Randy Edwards, at FidoNet 1:141/552.0.
-----------------------------------------------------------------
---
Remember Campers!!!
To send mail from an Internet site or smart UUCP Site TO a user
that calls a Fido-Net system.
You need to know the name of the person and node number of the
Fido-Net system that the person uses.
The address of a FidoNode looks like this: 1:105/302.0. Usually
the 1: and .0 are left off, but they are there by default. (In
Europe it is 2: and in the Pacific Basin it is 3:.) That
address can be translated as "Zone 1, Net 105, FidoNode 302,
Point 0." or p0.f302.n105.z1. Add the FidoNet domain of
.fidonet.org to the end of that, chop off the p0 (it is again,
a default) and you have f302.n105.z1.fidonet.org - the "Fully
Qualified Domain Name" of a FidoNode. Another example is
1:105/4.3 which would be written as p3.f4.n105.z1.fidonet.org
(since there is a point number other than 0, we have to specify
it). Note also that we are only using zone 1. This will also
work for zones 2 and 3, just use z2 or z3 as appropriate.
FidoNet uses full names of the callers. Multi-part name folks
(eg. First Last, ie. "Dale Weber") will have a period '.'
seperating their names. So, lets say you wanted to send mail
to Dale Weber at 1:105/55.0, you would address your letter to:
Dale.Weber@f55.n105.z1.fidonet.org.
**********************************************************************
Submissions to comp.org.fidonet should be addressed to
pozar@toad.com
**********************************************************************
--
pozar@lns.com Fido: 1:125/555 PaBell: 415-788-3904
USNail: KKSF-FM / 77 Maiden Lane / San Francisco CA 94108