FidoNews · Vol 14, No 7 · 17 February 1997
F I D O N E W S -- Volume 14, Number 7 17 February 1997
+----------------------------+-----------------------------------------+
| The newsletter of the | ISSN 1198-4589 Published by: |
| FidoNet community | "FidoNews" |
| _ | 1-904-409-7040 [1:1/23] |
| / \ | |
| /|oo \ | |
| (_| /_) | |
| _`@/_ \ _ | |
| | | \ \\ | Editor: |
| | (*) | \ )) | Christopher Baker 1:18/14 |
| |__U__| / \// | |
| _//|| _\ / | |
| (_/(_|(____/ | |
| (jm) | Newspapers should have no friends. |
| | -- JOSEPH PULITZER |
+----------------------------+-----------------------------------------+
| Submission address: FidoNews Editor 1:1/23 |
+----------------------------------------------------------------------+
| MORE addresses: |
| |
| submissions=> cbaker84@digital.net |
+----------------------------------------------------------------------+
| For information, copyrights, article submissions, |
| obtaining copies of FidoNews or the internet gateway FAQ |
| please refer to the end of this file. |
+----------------------------------------------------------------------+
IT'S PRESIDENTS' DAY IN THE U.S.A.
Table of Contents
1. EDITORIAL ................................................ 1
Echomail anniversary and other gripes .................... 1
2. GUEST EDITORIAL .......................................... 3
Another viewpoint about FidoNet .......................... 3
3. ARTICLES ................................................. 5
Common Sense for Fidonews ................................ 5
FTSC - Maybe this article should be .jok ................. 5
4. COLUMNS .................................................. 7
FIDONET IN EUROPE ........................................ 7
5. GETTING TECHNICAL ........................................ 8
FSC-0037 - AVATAR proposal ............................... 8
FSC-0038 - A Domain Proposal ............................. 12
FSC-0039 - A Type-2 Packet Extension Proposal ............ 13
6. COORDINATORS CORNER ...................................... 20
Nodelist-statistics as seen from Zone-2 for day 045 ...... 20
7. NET HUMOR ................................................ 21
Jeane Dixon didn't see it coming? ........................ 21
8. NOTICES .................................................. 24
Future History ........................................... 24
9. FIDONET SOFTWARE LISTING ................................. 26
Latest Greatest Software Versions ........................ 26
10. FIDONEWS PUBLIC-KEY ..................................... 33
FidoNews PGP public-key listing .......................... 33
11. FIDONET BY INTERNET ..................................... 34
And more!
FIDONEWS 14-07 Page 1 17 Feb 1997
=================================================================
EDITORIAL
=================================================================
As I write this Issue's editorial, it is the 11th anniversary of the
invention of Echomail by the now infamous Jeff Rush. Echomail is now
the reason why many people belong to FidoNet. What a concept!
More opinion on the size of FidoNet this week but differing views of
where the 'bloat' is. I guess it depends on whose ox is gored. [grin]
Below is the text of an exchange with a Z2 Sysop. I didn't have time
to get his permission to post his side but his name is removed for the
sake of discussion and only my quoted reply is included.
Date: 16 Feb 97 14:08:46
From: Christopher Baker on 1:18/14 Rights On! in Edgewater FL
To: Zone 2 Sysop
Subj: Re: FNews
______________________________________________________________________
> CB> but smaller IS better, right? [chuckle]
> I think you won't understand.
i think understanding is important. we all need to understand what is
going on here.
> It has nothing to do with smaller or bigger ...
good, because size is irrelevant unless FidoNews in archive gets too
big to fit on a floppy.
> Posting old (and almost uninteresting) Doc's (while not practicised)
> is pure nonsense.
practice makes perfect. the publishing is for historical and technical
purpose. the FTSC has lain dormant for years. the folks who went to
all the trouble of creating the various proposals and technical essays
contained in the FTSC docs never got much of an audience. the
publishing serves to illustrate where we came from and may stimulate
some action on some of these plans. it also acquaints people with the
underpinnings of the hobby many do not understand at any technical
level.
> And the Fidonet-Software-Listing ?
> Isn't there a FIDOSOFT conference where the listing may be posted ?
> In Germany there is FIDOSOFT.xxx where discussions are going on and
> a bigger list is posted frequently.
Echomail is not mandatory and not what FidoNet is or does. it's a nice
add-on that is useful for specific topics but it is not universal nor
available to everyone in toto. your reference to FIDOSOFT.xxx is a
good example of a local phenomenon that nobody outside your area knows
about. that's why FidoNews is an important conduit for such
FIDONEWS 14-07 Page 2 17 Feb 1997
information.
> I crashed this file month ago to Peter ... nothing happens.
did you get any mail back from him? perhaps, he has incorporated some
of the info into his listings or used it as a contact point for the
authors involved? i cannot answer for Peter.
he has taken on a monumental and thankless task in reorganizing and
winnowing this list. the software list is VERY important to FidoNet.
it is the ONLY centralized list of what is available for new Sysops
[or current Sysops looking for a change]. it won't always be the size
it is now. it is being actively maintained which means the dead wood
will be removed eventually. this is going to take time, however, and
FidoNews is not going to suffer for its size or content while that
process continues. it is important information and the only way to get
it to everyone [including the authors] at once is via FidoNews.
the point is that FidoNews is the only place [other than the Nodelist]
that is standard to all FidoNet Nodes. it is the appropriate place to
recount FidoNet history and to disseminate material peculiar to
FidoNet.
i hope this helps our mutual understanding. [grin]
thanks.
QOFM.
Chris
-30-
We have another Guest Editorial in response to Clay's of 1406. Keep
'em coming! I also see that Clay Tannacore HAS returned to the
Nodelist as of .045 on Friday. That's the spirit!
C.B.
-----------------------------------------------------------------
FIDONEWS 14-07 Page 3 17 Feb 1997
=================================================================
GUEST EDITORIAL
=================================================================
[This was slightly reformatted and edited for spelling and punctuation
and clarification of which Net is being referred to only.] Ed.
Hi Chris..
I don't suppose this will be in the proper format for a submission,
but I am ignorant of such things. Please do as you see fit. <grin>
I'm responding to a few pieces in the latest issue of Fidonews -
volume 6/97. Specifically, the article by Clay Tannacore about the
direction of Fidonet.
I found myself nodding my head in agreement with just about everything
Clay says in his article. I particularly found agreement in his
position #5, regarding the overuse of quoting in echomail. This has
long been a thorn in my side in every echo I read, or have read and
left. I have, on numerous occasions, taken it upon myself to attempt
to educate writers in the proper methods of quoting in echomail. Among
them, only quoting enough of the original message so others know your
point of reference. I've also campaigned against the geeks with the
multi-line, Internet style, high ascii "sigs" people have become so
fond of lately. As a SysOp myself, I'm aware of the costs involved in
moving echomail. I take it personally when people abuse our largesse
with this crap. Unfortunately, the response to most of my pleas has
been to "mind your own business - you ain't the Moderator!" Now you
would expect such from the elements who regard anonymous
communications as there personal playground to practice "Beavis and
Butt-Headisms", but when you get the same response from an echos
Moderator - saying "Leave the Moderating to the Moderator" - it's a
bit much. After all, had the Moderator been doing his job - such
conduct would not have been tolerated. The attitude seems to be "Fido
is dying, let them talk or they'll go to the Net." Well fine - let
them go if that's what Fido has degenerated into -I don't like paying
the freight for it!
Clay's point on the plethora of "Pay to Use" BBSes also struck a cord
here. I've run a board since 1992 - as a hobby. Shareware BBS software
(TriBBS 10/Pro, registered, thank you), bottomline all the way. I've
never charged for access to my board. Yes - I do offer subscriptions
for cash or donations of equipment in exchange for increased file
limits. Now, there are 2 schools of thought on Pay vs. Free boards.
The first is that people seeing a board charges for access will assume
it has to be pretty good or they wouldn't charge. Interesting! The
second is that, as Clay points out - we do this as a hobby, and
therefore shouldn't charge for access. I tend to see points of
agreement in each, since a few pay boards in my area are doing great,
while free boards like mine are suffering. Doubly interesting since on
"free previews" I've taken on these boards, neither the graphics work,
features, games, nor filebase are as extensive or good as mine. But
there ya go - different strokes. Clay's proposition that pay boards
are sometimes thinly disguised pirated software hangouts, i.e. "Elite"
FIDONEWS 14-07 Page 4 17 Feb 1997
boards, has an element of truth to it. That is certainly the case in
my areas anyway. I limit non-members on my board to specific but
generous download levels. Members are allowed practically unrestricted
downloads. That's it. All callers have full access to the 15 CDROMs I
carry, all message networks and echos, and all the games. I do know
of several boards running hacked software, with logon procedures like
speakeasys of the 20's - complete with "joe sent me" doorways and
phony menus. Pretty neat if you want to spend 3 hours online
downloading a copy of Win95 at 14400. Not me, thanks.
A final point is Clay's mention of the effects of the [Inter]Net on
local "hobby" bulletin boards. The [Inter]net has hurt me badly.
Calls have dropped significantly over the last year, for a number of
reasons. One of those is new computer owners/users don't need
additional communications software and the accompanying knowledge to
call the [Inter]Net - most PCs come with the software. They can
connect to the [Inter]Net and play. To call a BBS they have to locate
and install a comm program, find some local boards numbers, then plod
through setting up to connect properly with ANSI, etc. Not a lot of
fun for todays crop of "point and click or forget it" PC users. We
should indeed stress the FREE nature of our boards, and the usefulness
of Fidonet in messaging all over the world via a local call. I've
found myself making close friends I've yet to meet in countries the
world over, as well as states of this great country I've never
visited. That means something, and should be made note of. There has
to be a simpler method of interfacing local boards with beginners PCs.
How that could be accomplished I have not a clue - the more technical
aspects of these toys we play with escape me, and at this time of my
life (age 50), there is no hope of my learning. That I will leave up
to others more capable.
Fido[Net] has some problems, to be sure. None of them are
insurmountable, in my opinion. Surely the "in your face" mentality of
certain recent critics does nothing to enhance its prospects. Fidonet
after all is a mirror image of politics - many criticize, yet too few
offer solutions. Not surprising since criticism is easy. Finding
solutions takes work and some semblance of intelligence - both
characteristics lacking in the harbingers of doom.
Respectfully,
Bruce Emmott
SysOp, Aegis BBS
1:2619/121
Merrick, NY
-----------------------------------------------------------------
FIDONEWS 14-07 Page 5 17 Feb 1997
=================================================================
ARTICLES
=================================================================
Common Sense for Fidonews
by Lee Kindness, 2:259/7, lkindnes@csl.co.uk
Gary Gilmore was quite rash in a number of his comments a couple of
weeks back... However a couple of valid comments can be made regarding
Fidonews's size and content:
o Internet distribution sites - A simple link to a web page that
contains these address would suffice. It goes without saying that
everyone that is interested in these sites would have internet access,
and hence be able to access such a page.
o Zone, Region, Net Homepages - As above, a reference to a web page
would do.
o Jokes & ASCII 'pics' - Not the thing we should *promote* for
Fidonews inclusion. It's the type of thing anyone with an email
address gets bombarded with daily from friends and in the humour
echoes (PUNCH et al). So before you think about submitting these
jokes and pictures consider that you've got - it's more than likely
everyone else has too!
o Software listing - Monthly rather than weekly would be a better
frequency, and lets get rid of the old software section - a pile of
meaning less names and version numbers is of no use to anyone!
o PGP key - A pointless peace of INet poseur?
Lets cut down on all the static information...
And now onto the positive aspects... The posting of FTSC documents is
a great idea (i waiting to see how the RTF FSC is handled thou ;) and
Chris has done a great job in reviving Fidonews after Tees's death
grip.
--
_____ _ _ _____
( __ )(_)-coco-moko-cwewe-modete-escro-(_)( __ )
\/ (_)(_)-loko-noko-lkindnes@csl.co.uk-(_)(_) \/
-----------------------------------------------------------------
FTSC - Dead and Buried?
by Lee Kindness, 2:259/7, lkindness@csl.co.uk
Last year i submitted 3 FTS update proposals to the FTSC Chair Dave
Nugent. 5 months later, no reply.
Speaks volumes really... I wonder how many people remember the words
of Dave when he took over the position, pot calling the ke... I
FIDONEWS 14-07 Page 6 17 Feb 1997
really must dig them up and post them!
We need a solution, The 'new' FTSC-something leaded by R1EC seems
too elitist (All this FTSC_PUBLIC echo bollox, get into NET_DEV
where the developers are!)
A point to ponder...
--
_____ _ _ _____
( __ )(_)-coco-moko-cwewe-modete-escro-(_)( __ )
\/ (_)(_)-loko-noko-lkindnes@csl.co.uk-(_)(_) \/
-----------------------------------------------------------------
FIDONEWS 14-07 Page 7 17 Feb 1997
=================================================================
COLUMNS
=================================================================
Fidonet in Europe
-----------------
by Dave Meikle (2:259/24.105 , postmaster@rjambo.abel.co.uk)
Send info to europe@2:259/24.105 or europe@rjambo.abel.co.uk
Nothing much happening apart from THE Zone 2 Fidonet Home page @
http://www.z2.fidonet.org .
Dave
P.S. TO GET THE LATEST FIDONET IN EUROPE INFO SEND A FIDONET MESSAGE
TO infomail@2:259/24.105 with the subject line: Fido-in-europe .
-----------------------------------------------------------------
FIDONEWS 14-07 Page 8 17 Feb 1997
=================================================================
GETTING TECHNICAL
=================================================================
FSC-0037
Updates: FSC-0025
[This is part of the continuing series of FidoNet Standards and
proposals presented as FidoNet History. These docs have been
reformatted to 70 columns where required. As always, full text
versions are available via the sources listed in the Masthead info at
the end of each Issue.] Ed.
Pittsburgh, PA
1 May 1989
A V A T A R
Advanced Video Attribute Terminal Assembler and Recreator
George A. Stanislav
Fidonet 1:129/39.0
Information
This FSC is being distributed to members of the FidoNet
community in order to solicit their reactions to the
proposals contained in it. While the issues discussed may
not be directly relevant to FidoNet standards, they may
be interesting to implementers. Distribution of this
document is unlimited.
Revised on 25 November 1989
Definitions
Avatar, level 0 - The Avatar protocol as presented at Fidocon '88 and
described in AVATAR0.C, dated 23 August 1989, plus extensions
defined in this document.
AVT/0 - An abbreviation for Avatar, level 0, suggested by Joaquim
Homrighausen.
Current attribute - Video attribute defined by the last ^V^A, ^V^L,
^V^M or ^L AVT/0 command whichever happened last. In AVT/0, ^L
sets the value of current attribute to 3, ^V^L, ^V^M and ^V^A
to an explicit value. In addition, ^V^B turns blink on.
Extending AVT/0
It has become clear some of the Avatar commands originally reserved
for AVT/1 would be very useful in AVT/0. I was hesitant to add them
for one simple reason: Any addition on level 0 will break all existing
Avatar emulating software.
FIDONEWS 14-07 Page 9 17 Feb 1997
However, at present there are only three programs I know of that have
implemented Avatar emulation: My own TinyTerm, Joaquim Homrighausen's
FrontDoor and Jason Galanter's Jterm.
Both Joaquim and Jason have assured me they would put the new commands
in their programs, thus nothing will be broken. With that assurance in
mind, I feel confident no chaos will result from adding these new
commands.
New Commands (brief definitions)
<^V><^I> - Turn insert mode ON. It stays on until any other
AVT/0 command except <^Y> and <^V><^Y> is
encountered after which it is turned off;
<^V><^J><numlines><upper><left><lower><right> - scroll area
up;
<^V><^K><numlines><upper><left><lower><right> - scroll area
down;
<^V><^L><attr><lines><columns> - clear area, set attribute;
<^V><^M><attr><char><lines><columns> - initialize area, set
attribute;
<^V><^N> - delete character, scroll rest of line left;
<^V><^Y><numchars><char>[...]<count> - repeat pattern.
Detailed Description
Insert mode: Insert mode controls the way characters are printed on
the screen. Insert mode is always assumed OFF unless explicitly
set ON by the ^V^I command after which it stays on until another
AVT/0 command except for ^Y or ^V^Y is encountered. Then it reverses
back to off.
Whenever insert mode is OFF, characters are printed on the
screen like this:
1. Print character at current cursor position using current
attribute, overwriting whatever was previously displayed at
current cursor position;
2. Move cursor to next position, usually one character to the
right. At end of the line, move the cursor to next line
(possibly scrolling the display or current window if in
AVT/1).
Whenever insert mode is ON, characters are printed on the
screen as follows:
1. Starting at current cursor position and going all the way
to the second last character on current line, scroll the
text one character to the right;
FIDONEWS 14-07 Page 10 17 Feb 1997
2. Discard the character previously at the end of the line, do
NOT move it at the beginning of the next line;
3. Print character at current cursor position using current
attribute;
4. Move cursor to next position, precisely as in par. 2 of
insert mode off.
If ^Y or ^V^Y are encountered, the string of characters they compress
is first expanded, then treated as an ordinary stream of characters
printed according to the above rules.
Any other AVT/0 command turns insert mode back off. Please note that
in either case the cursor is moved to its next position in an
identical manner. The mere fact the cursor is moved to next line, or
even scrolls the screen a line up, does NOT turn insert mode off. Only
an AVT/0 except as mentioned above can change insert mode on or off.
If control characters are a part of the text stream, they are
interpreted indentically in insert mode on and off as follows:
Carriage return - move cursor at the beginning of the same
line;
Line feed - move cursor one line down (scroll screen
or window [in AVT/1] if necessary), do not
change cursor column;
Back space - move cursor one position to the left. Do
NOT overwrite the character at that
position. Do nothing if already at the
leftmost position;
Tab - move cursor to next tab position without
overwriting anything. Tab positions are
multiples of 8. Do nothing if already at
the rightmost position.
A space is treated as a character, not as a control character.
Scrolling an area (^V^J and ^V^K): The area defined by its upper,
left, lower and right coordinates is scrolled up <^V^J) or
down (^V^K) by <numlines> lines filling the gap with blank
spaces using current attribute. If the value of <numlines> is
zero or exceeds the actual number of lines within the scrolled
area, the area is filled with blanks using current attribute.
These two commands do NOT change the position of the cursor,
nor do they define the scrolled area as the default window.
The coordinates are relative to the upper left corner of the
screen (or current window in AVT/1). The coordinates of upper
left corner are 1,1. If a coordinate contains 0, it is to be
changed to 1.
FIDONEWS 14-07 Page 11 17 Feb 1997
Initializing an area (^V^M): This command contains several steps:
1. Set current attribute to <attr>;
2. Starting at current cursor position (inclusively), ending
at current cursor position plus number of <lines> and
<columns>, print <char> at all position inside the defined
area. Do not move the cursor. If the number of columns or
lines exceeds whatever is available to the right and below
current cursor position, truncate the dimensions to fit
within the limits of the screen (or current window in
AVT/1).
Clearing an area (^V^L): This is a shortcut version of the ^V^M
command.
The character to be used to initialize the area of the screen
is assumed to be a blank space. In other words, it sets
current attribute and clears an area of the screen starting at
current cursor position (which remains unchanged).
Please note that the usual 7-bit restriction applies to ^V^L That
means that the attribute byte should be anded with 7f hex before
applying. If blinking is desired, ^V^B should be used next.
On the other hand, requiring to ignore the high bit in ^V^M would make
it impossible to fill the area of the screen with a blinking pattern
(something I have seen used very creatively by Chris Gaal of PittNet).
Therefore, if bit 7 of attr is set in ^V^M, current attribute is set
to <attr> AND 7f hex and blink is turned on before filling the area
with a character.
Deleting a character (^V^N): Starting at the column one character to
the right of current cursor position all the way to end of the
line, scroll the text one character position to the left. This
effectively deletes the character at current cursor position.
Print a blank space using current attribute at the rightmost
end of the line to fill the gap. Do not change current cursor
position. If the cursor is at the end of the line, simply
overwrite the last character with a blank space using current
attribute.
Repeat pattern: This is an extension of the ^Y command which allows a
group of characters to form a repetititious pattern. <numchars>
determines the number of characters in the pattern, <count> the
number of times the pattern is to be printed out. The pattern
may contain AVT/0 codes.
For example, <^V><^Y><#3>ABC<#4> expands to "ABCABCABCABC".
Scrolling Philosophy
An important philosophical question has not been answered yet: When
scrolling the contents of an area (in the scrolling commands ^V^J and
^V^J, in insert mode ON and in deleting characters ^V^N) should only
the text be scrolled and the attribute of the scrolled areas remain
where they are or should the attributes move as well.
FIDONEWS 14-07 Page 12 17 Feb 1997
A case can be made for either approach. Obviously, the gaps created by
scrolling are filled with current attribute, therefore, it seems more
logical to scroll the attributes along with the text (else there would
be no need to fill the gaps). Thus we follow a consistent principle of
video attributes belonging to a character (be it a blank, a digit, or
a true character), not to a location. Whenever a character is scrolled
to a different location, it takes its attribute along.
-30-
-----------------------------------------------------------------
Document: FSC-0038
Version: 001
Date: 02/22/90
A Domain Proposal For Fidonet(r)
jim nutt
1:114/30@fidonet
Information:
This FSC suggests a proposed protocol for the FidoNet
community, and requests discussion and suggestions for
improvements. Distribution of this document is
unlimited.
A. Rationale
A recent proliferation of alternative networks based on Fidonet
technology has brought to light the difficulty of maintaining a fully
coupled addressing method for Fidonet. Additionally, Fidonet has
joined the Internet, revealing a need for a transparent scheme for
addressing messages across the networks. It is therefore proposed
that a system be established whereby geographical or political sub
units of the network can be broken off into an independent network
called a "domain". These networks will be fully independent, even to
the point of having duplicate net/node numbers or using a different
addressing scheme altogether. This will allow continued growth of
Fidonet without necessitating that the nodelist grow to an
unmanageable size (if it isn't already there). Among the advantages
of this type of system are reduced nodelist overhead, easier inter-
network communication and greater autonomy of alternative networks.
This document will only cover the definition of the necessary
addressing extensions to support domain based addressing. It will not
attempt to define standards for gating mail and conferences between
domains.
B. Description
It is proposed that domain addressing be implemented in a fashion
similar to the current ZONE extended addressing method. Domain names
will be case insensitive. The domain extended addressing line will be
comprised of a leading SOH (^A, 0x01) followed by the keyword
FIDONEWS 14-07 Page 13 17 Feb 1997
"DOMAIN", the destination domain of the message and then the full
address (zone:net/node.point) of the destination node in that domain,
followed by the source domain of the message and the full address of
the originating node. The line will be terminated by a <CR> (0x0d)
and an optional linefeed (0x0a), fields within the line will be
separated by one or more spaces or tabs. i.e.
^ADOMAIN dstdmn daddress srcdmn saddress
Where "dstdmn" is the name of the destination domain and "daddress" is
the address of the destination system in a format appropriate to the
destination domain. "srcdmn" and "saddress" are similar, except that
they express the origination address of the message in a format
appropriate to the originating domain. This allows a seamless gateway
to the Internet and other large system networks. The destination
address in the FTS-001 message header should be that of a gateway to
the destination domain.
C. Summary
Domains are independent networks that are fully decoupled from the
Fidonet nodelist. Message traffic is passed back and forth between
domains via domain gateways that can understand the DOMAIN extended
addressing line and act accordingly upon the message. The advantages
include reduced nodelist size and easier communication with other
networks.
-30-
-----------------------------------------------------------------
Document: FSC-0039
Version: 04
Date: 29-Sep-90
A Type-2 Packet Extension Proposal
Mark A. Howard 1:260/340@FidoNet
Status of this document:
------------------------
This FSC suggests a proposed protocol for the FidoNet(r) community,
and requests discussion and suggestions for improvements.
Distribution of this document is unlimited.
Fido and FidoNet are registered marks of Tom Jennings and Fido
Software. FTS-0001 is a copyrighted work of Randy Bush.
Introduction
------------
This document serves two major purposes. The first is an attempt to
define and document the Type-2 packet which is widely in use in
FidoNet today. Although FTS-0001 defines the structure of a Type-2
packet, the natural evolution of our network, mostly with regards to
FIDONEWS 14-07 Page 14 17 Feb 1997
addressing methodology, has made it necessary to utilize hitherto
unused portions of the header to insert Zone and Point information.
Also, it has become apparent that some of the existing fields are
not large enough to accomplish their original tasks.
The second is to propose a simple mechanism to allow FidoNet to
begin to utilize advanced mail packing techniques. It is quite
apparent that while Type-2 has served us faithfully for some time
now, the evolution of our network in terms of technical and physical
complexity has caused us to consider more efficient and functional
ways to pack mail.
It should be made clear that with the exception of the Capability
Word, Capability Word Validation Copy, ProductCode(hi), and
Revision(minor), which are proposed extensions to the Type-2 packet
header, this FSC is an attempt to correctly document existing
practices with regards to the insertion of zone and point info by at
least three mail processors in use today.
The Type-2 Header (Where's the Zone?)
-------------------------------------
Although FTS-0001 has recently been updated to reflect the use of
some of the areas in the packed message header for zone data, at
least two other methods for inserting the zone information have been
adopted, making it necessary to provide support for both formats in
all of the zone aware mail processors. The end result is more code,
and redundant information in the packet header.
This has presented a problem in logistics, as it is difficult to
consider the project of updating mail processors using one type to
use the other. As sufficient indentification is provided, in the
form of the product code, to determine the expected location of the
zone information, and because code already exists in most of the
mail processors to overcome this, this proposal does not attempt to
suggest that one method be used over the other, rather the intent is
to attempt to document the extensions in use, and the products
involved.
See the accompanying chart and cross-reference.
The Product Code
----------------
Based upon the current rate of requests for product codes from the
FTSC, it is probable that the Product Code byte will not be large
enough to accomodate all of the codes required. While it is not
reasonable to expect that all Type-2 processors will eventually
check the hi-order byte proposed here, it is likely that 'current'
mail processors will. This can be nothing but benefical, as it will
force users to upgrade their mail processors to a product which will
as a minimum, support Type-2 with Zone and Point extensions, and
quite possibly, processors that will utilize more advanced mail
packing techniques, making Type-2 extinct once and for all.
The Capability Word (How do we GET there from here?)
-----------------------------------------------------
Everybody would like to see more efficient and functional ways to
FIDONEWS 14-07 Page 15 17 Feb 1997
pack and exchange mail. Several Type-3 message bundle proposals
exist, but none really address a problem which must be solved first.
The problem is that since FidoNet is a hobbyist network, no demands
can be placed on any one sysop to upgrade or change their bundling
software. Because of this, it is necessary to consider strategies
which allow for the existence of Type-2 bundlers in the network
topology.
Considerable advantages can be realized, however, between systems
that consent to use advanced bundling techniques. One way to do
this is to simply send netmail to all of your connecting systems,
saying "Hey, I've got a Type-3 bundler now, how about you?" This
could become quite tiresome, and does not represent much of an
improvement on the current situation.
What would be desirable is a network that would 'upgrade itself'.
Given a situation where mail processors of various capabilities will
exist in a network topology, the goal is to provide a mechanism
whereby two links can determine and utilize the most efficient
bundling method to use, in a manner transparent to the sysop.
For instance, let's say that the FTSC releases the Type-7 All New
Singing and Dancing bundle format. Well, your current version of
SlingToss can only support Types 2, 3, and 5. One of your downlinks
gets a new version of MailMangle which can support Types 2, 3, 4,
and 7. Well, it is quite obvious that since you and he are
exchanging 4 megs of mail each night, and it's an overseas call,
that it would be in your interest to obtain a new version of
SlingToss which can support Type 7.
Note that this is *optional*. Because both processors can support
Type-3, they will continue to exchange Type-3 mail quite happily,
even though MailMangle is happily advertising the availability of
Type-7. Even your downlinks which are still using stone-age Type-2
processors will be fine, as SlingToss will always export Type-2
bundles when no higher capability can be determined.
So, after dashing off the check to the author, your new version of
SlingToss comes in the mail! You rush over to your system, and
install it. The next time SlingToss exports mail to the MailMangle
system, it says "Hey! I can now support Type 2, 3, 5, and 7! So,
whattya got?" This is no skin off MailMangle's nose, he's had Type-7
for quite a while, and he begins to export Type-7 bundles to
SlingToss. "It's about time.", he says.
Now, this scenario is made possible by implementing a 'Capability
Word' in the present and future packet headers. The Capability
Update mechanism depends on several assumptions:
1) Any Advanced Capability Bundler *MUST* be capable of receiving
and faithfully processing Type-2 bundles. Hopefully, the inbound
packets will be in the new format proposed by this document, but
then again, this is not an exact science. What this means is
that it is likely that some packets may arrive with the
Capability Word (CW) set to 0. In this case, Type-2 is assumed,
assuring compatibility. The only caveat is that it is
FIDONEWS 14-07 Page 16 17 Feb 1997
conceivable that some obscure mail processor uses the location
proposed for the CW for other arcane purposes. This | can
detected through the CWValidation Copy, which is byte-swapped and
| compared with the CW at that time. If a mismatch is found, a
CW of | type 0 is assumed, and a Type-2 bundling method is used.
2) An Advanced Capability Bundler, hereafter referred to as a Type-N
Bundler, must have a method to store and maintain the node-by-
node capability information. This can be done many ways, and in
fact several processors already have begun to maintain node
information outside of that found in AREAS.BBS, mostly to
implement pre-arranged alternate compression methods. In a text
configuration file, you might see the following:
; Address Comp Send LastCW ; Comments
Node 1:260/340 ZIP Auto 7 ; Auto detect & upgrade
Node 1:135/20 LZH 3 2,3,7 ; Always send Type-3
Node 1: ARC 2 0 ; Stone-Age processor
Node 1:135/4 --- Auto 7 ; Sent me netmail
Node 1: --- 0 0 ; Don't send CW
In this example, the fields are:
Address - downlink address. Note that this is not necessarily
relative to echomail, only, it is possible to append
information to the node database as netmail packets are
receieved from different addresses.
Comp - desired mail compression method.
Send - Auto - automatically determined maximum common packing
method to use. Automatically update to LastCW
when packing.
LastCW - Last CW received from remote system.
3) A Type-N Bundle will always advertise it's capabilities in the CW
regardless of the type being sent. As shown in the above
example, it allows Type-N processors to automatically track the
capability of your system. Again, in cases where a stone-age
processor is being used, this field will be ignored, and in the
unusual event that it is not ignored, and is somehow harmful to
the far system, the Type-N processor can be configured to send a
CW of 0.
The format of the Capability Word is designed to support up to 15
future bundle types, and is bit-mapped to facilitate the easy
determination of the maximum common level supported between two
nodes:
msb Capability Word lsb
Node Supports ------------FTSC Type Supported----------------
U 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2
FIDONEWS 14-07 Page 17 17 Feb 1997
2, 3, and 7 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 1
2, 3, and 5 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1
2 (this FSC) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Stone Age** 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
^
+--- Indicates UseNet RFC-822 capability
** - a mismatch in the CWValidation Copy also
produces a CW=0.
In this example, the Type-N bundler would first compare the remote
CW | and the byte-swapped remote CWValidation Copy, and check for a
mismatch. Prior to the compare, the MSB of the CW's are masked, as
this bit is reserved to indicate whether the mail processor is
capable of also accepting UseNet RFC-822 bundles. Following the MSB
mask, and bit comparison, if they do not match, a remote CW of 0 is
assumed. If they match, the Type-N processor would AND the local
and remote CW words, obtaining a CW expressing the Types which are
in common to both systems. The most significant Type will be used,
by default, but note that this assumes that new bundling Types will
be increasingly more efficient or in some way more beneficial.
Because this may not always be the case, there should be a method
provided, as illustrated above, to override the automatic upgrade
should this become the case.
The MSB of the CW is used to indicate whether the mail processor can
accept UseNet RFC-822 bundles or not. It is a separate indicator,
and not intended to be used as a part of the above comparison,
however can be used to also advertise RFC-822 capability to other
systems. Since RFC-822 is 'set in stone', there is no need to
assign more than one capability bit.
It might seem somewhat limiting to only consider the possibility of
15 different future bundling methods, but it is my opinion that the
careful use of a 'Sub-Type' byte in the packet header can allow for
the variations on a single theme, and that proposals for new formats
should be evaluated by the FTSC to determine whether sufficient
benefit can be realized in the implementation of the given format,
prior to assigning a new type code.
Mailers
-------
It is quite clear to me that should this concept take hold, that the
logical place to store node capability data is in the local nodelist
database, or an index-associated data file. As above, it is
necessary to generate Type-2 packets for whatever purpose, unless it
is known by prior association, that the far mailer can accept other
types of packets. It is also quite reasonable to assume that a
nodelist flag could be assigned to advertise the CW for a given
node, which the native mailer nodelist compiler could then
immediately determine the preferred bundling method for any given
node in FidoNet.
Another possibility would be to pass a capability advertisement in
the extensible portion of a handshake protocol, which may or may not
FIDONEWS 14-07 Page 18 17 Feb 1997
already exist in FidoNet.
The approach suggested previously in this document suggests the use
of a text configuration file, but it is quite obvious that many
benefits can be realized through the use of the nodelist, including
the use of additional flags to indicate the preferred compression
method, etc.
Summary
-------
This document has been created in an attempt to define a method to
allow the future expansion and enhancement of FidoNet technology
mail processors and mailers, and in a way that is the least
disruptive to existing mail operations. The intent is to provide
for an environment that is as open, and extensible as possible.
The mechanism described should allow many different types of
processors (FTSC-registered) to exist in the network at once, and to
provide an environment which is designed to operate at it's maximum
efficiency wherever possible or practical.
Revision 2 of this document was produced to implement suggestions
made primarily by Jan Vroonhof, who suggested the use of the CW
Validation Copy. Jan presented this idea in his FSC-0048, along
with other concepts relating to the correct indentification and
handling of zone and point addressing. This document sanctions the
improvements to the CW as recommended, but does not address or
support the other extensions recommended in FSC-0048.
Thanks
------
To Ward Christensen, creator of XModem and BYE.
Tom Jennings, who started this whole mess.
Joaquim Homrighausen, for lots of good ideas, and motivation.
Here's another Lamborghini to work on.
Wynn Wagner, Oliver McDonald, Roeland Meyer, Andrew Farmer,
Claude Warren, Jan Vroonhof, Bob Hartman, and Vince Perriello,
who all contributed in some way to the creation of this document,
mostly through their messages in NET_DEV.
Type-2 Packet Format (proposed, but currently in use)
-----------------------------------------------------
Field Ofs Siz Type Description Expected
value(s) ------- --- --- ---- -------------------------- -------
----------
OrgNode 0x0 2 Word Origination node address 0-65535
DstNode 2 2 Word Destination node address 1-65535
Year 4 2 Int Year packet generated 19??-2???
Month 6 2 Int Month " " 0-11 (0=Jan)
Day 8 2 Int Day " " 1-31
Hour A 2 Int Hour " " 0-23
Min C 2 Int Minute " " 0-59
Sec E 2 Int Second " " 0-59
FIDONEWS 14-07 Page 19 17 Feb 1997
Baud 10 2 Int Baud Rate (not in use) ????
PktVer 12 2 Int Packet Version Always 2
OrgNet 14 2 Word Origination net address 1-65535
DstNet 16 2 Word Destination net address 1-65535
PrdCodL 18 1 Byte FTSC Product Code (lo) 1-255
* PVMajor 19 1 Byte FTSC Product Rev (major) 1-255
Password 1A 8 Char Packet password A-Z,0-9
* QOrgZone 22 2 Int Orig Zone (ZMailQ,QMail) 1-65535
* QDstZone 24 2 Int Dest Zone (ZMailQ,QMail) 1-65535
Filler 26 2 Byte Spare Change ?
| * CapValid 28 2 Word CW Byte-Swapped Valid Copy BitField
* PrdCodH 2A 1 Byte FTSC Product Code (hi) 1-255
* PVMinor 2B 1 Byte FTSC Product Rev (minor) 1-255
* CapWord 2C 2 Word Capability Word BitField
* OrigZone 2E 2 Int Origination Zone 1-65535
* DestZone 30 2 Int Destination Zone 1-65535
* OrigPoint 32 2 Int Origination Point 1-65535
* DestPoint 34 2 Int Destination Point 1-65535
* ProdData 36 4 Long Product-specific data Whatever
PktTerm 3A 2 Word Packet terminator 0000
* - extensions to FTS-0001
Ofs, Siz are in hex, other values are decimal.
Zone/Point Aware Mail Processors (probably a partial list)
----------------------------------------------------------
Prod
Code Name - Uses QOrg/QDstZone Orig/DestZone Orig/DestPoint
---- ----------- ------------- ------------- --------------
0x0C FrontDoor Reads/Updates Yes Yes
0x1A DBridge ????? Yes Yes
0x45 XRS Reads/Updates Yes Yes
0x29 QMail Yes ????? Not point-aware
0x35 ZMailQ Yes ????? Not point-aware
0x3F TosScan Reads/Updates Yes Yes
-30-
-----------------------------------------------------------------
FIDONEWS 14-07 Page 20 17 Feb 1997
=================================================================
COORDINATORS CORNER
=================================================================
Nodelist-statistics as seen from Zone-2 for day 045
By Ward Dossche, 2:292/854
ZC/2
+----+------+------------+------------+------------+------------+--+
|Zone|Nl-017|Nodelist-024|Nodelist-031|Nodelist-038|Nodelist-045|%%|
+----+------+------------+------------+------------+------------+--+
| 1 | 10177|10063 -114 | 9877 -186 | 9729 -148 | 9527 -202 |34|
| 2 | 15936|15938 2 |16078 140 |16067 -11 |16074 7 |57|
| 3 | 865| 863 -2 | 863 0 | 863 0 | 846 -17 | 3|
| 4 | 553| 558 5 | 550 -8 | 549 -1 | 538 -11 | 2|
| 5 | 93| 93 0 | 87 -6 | 87 0 | 87 0 | 0|
| 6 | 1073| 1072 -1 | 1072 0 | 1072 0 | 1071 -1 | 4|
+----+------+------------+------------+------------+------------+--+
| 28697|28587 -110 |28527 -60 |28367 -160 |28143 -224 |
+------+------------+------------+------------+------------+
-----------------------------------------------------------------
FIDONEWS 14-07 Page 21 17 Feb 1997
=================================================================
NET HUMOR
=================================================================
To: cbaker84@digital.net
From: top5@lists.zdnet.com
Subject: TopFive -- 1/31/97 -- Things Overheard at Psychic Jeane
Dixon's Funeral
Errors-To: top5-errors@lists.zdnet.com
Date: Thu, 30 Jan 1997 18:38:53 MST
_____________________________________
_________| |________
\ | The Top Five List | /
\ | www.topfive.com | /
\ | | /
\ | Sponsored by Windows Sources | /
> | www.winsources.com | <
/ | | \
/ | January 31, 1997 | \
/ |_____________________________________| \
/___________) (__________\
The Top 16 Things Overheard at Psychic Jeane Dixon's Funeral
16> "Ms Warwick, please stop talking to the deceased."
15> "Now we'll NEVER know who's going to win the Oscars!"
14> "I'm thinking of a passage from John Chapter 3 between
1 and 20."
13> "You're next, you know."
12> "Quiet down, everyone! I can't hear a word Jeane's saying!"
11> "I'm going to miss the way she always knew the outcome of
each Matlock."
10> "The woman predicted Kennedy's assassination, for cryin' out
loud -- you'd think she'd have known how hideous she'd look
in that dress."
9> "I spoke with Jeane this morning. She wants me to have
her BMW."
8> "Wait, I'm seeing it -- yes! The number 8 entry on tomorrow's
Top Five List will be a self-referential psychic quote thing
by Alexander Clemens of San Francisco."
7> "I see a world plunged in darkness. What the--? Hey!
FIDONEWS 14-07 Page 22 17 Feb 1997
Somebody, get me outta this box!"
6> "She looks so supernatural."
5> "Since we all know what the eulogy's going to be, let's cut
right to the coffee and sweet rolls."
4> "I see a drunken reception in my near future."
3> "Light as a feather, stiff as a board... light as a feather,
stiff as a board..."
2> "Wait, I'm seeing... yes, I'm seeing... worms!"
and the Number 1 Thing Overheard at Psychic Jeane Dixon's Funeral...
1> "Who knew?"
[ This list copyright 1997 by Chris White and Ziff-Davis ]
[ *To forward or repost, please include this section.* ]
[ The Top Five List top5@walrus.com www.topfive.com ]
Selected from 79 submissions from 28 contributors.
Today's Top Five List authors are:
----------------------------------------------------------------
George Olson, Colorado Springs, CO -- 1 (10th #1)
Lev L. Spiro, Los Angeles, CA -- 2
Marianne Tatom, Austin, TX -- 3
Rob Winchell, Arlington, MA -- 4
David G. Scott, Kansas City, MO -- 5, 9
Ed Smith, Chattanooga, TN -- 6
Bruce Ansley, Baltimore, MD -- 7 (Hall of Famer)
Alexander Clemens, San Francisco, CA -- 8
Peg Warner, Derry, NH -- 10
Bill Muse, Seattle, WA -- 11
Jason Anderson, Birmingham, AL -- 12 (Rookie!)
Michael Wolf, Brookline, MA -- 13
Paul Seaburn, Houston, TX -- 14
David Hyatt, New York, NY -- 15
Mitch Patterson, Atlanta, GA -- 16
Chris White, New York, NY -- List owner/editor
----------------------------------------------------------------
Today's Runners Up list, "What's the Frequency, Kenneth?",
can be found at our website: www.topfive.com
================================================================
*** Windows Sources Spotlight ***
Adobe Systems Acrobat 3.0!
Acrobat 3.0 Goes Online
and Elsewhere -- get the story,
at www.winsources.com
FIDONEWS 14-07 Page 23 17 Feb 1997
================================================================
T H E T O P F I V E L I S T
To subscribe: Send mail to top5-on@lists.zdnet.com
To unsubscribe: Send mail to top5-off@lists.zdnet.com
For more information: Send mail to top5@walrus.com
with "INFO" in the *subject* line of the message.
To report a sighting of a Top Five List in other media:
Send mail to top5@walrus.com with "BINGO!" in the *subject*.
================================================================
Ruminations & Ponderances
One night I walked into the kitchen and found Grandma
getting ready to cut up Anna Chin-Williams' family.
"GRANDMA!" I cried, "You said we were having
*Paul Paternoster* tonight!!" She replied,
"No, the dog is having Paul Paternoster!"
Boy, did we ever laugh about that one.
(Thanks to Bill Muse)
One night while I was enjoying Grandma's dog a l*orange,
I mentioned that Paul Paternoster's family actually ate CHICKEN!
Grandma replied, "I guess for some people, nothing's sacred."
There wasn't much to laugh about that night.
(Thanks to Anna Chin-Williams)
THE END
================================================================
The Top Five List http://www.topfive.com
Sponsored by Windows Sources http://www.winsources.com
This delivery powered by Mercury Mail, Inc. http://www.merc.com
-----------------------------------------------------------------
FIDONEWS 14-07 Page 24 17 Feb 1997
=================================================================
NOTICES
=================================================================
Future History
29 Feb 1997
Nothing will happen on this day.
17 May 1997
Independence Day, Norway.
25 May 1997
Independence Day, Argentina.
6 Jun 1997
National Commemoration Day, Sweden.
11 Jun 1997
Independence Day, Russia.
1 Jul 1997
Canada Day - Happy Birthday Canada.
13 Oct 1997
Thanksgiving Day, Canada.
1 Dec 1997
World AIDS Day.
10 Dec 1997
Nobel Day, Sweden.
12 Jan 1998
HAL 9000 is one year old today.
22 May 1998
Expo '98 World Exposition in Lisbon (Portugal) opens.
1 Dec 1998
Fifteenth Anniversary of release of Fido version 1 by
Tom Jennings.
31 Dec 1999
Hogmanay, Scotland. The New Year that can't be missed.
1 Jan 2000
The 20th Century, C.E., is still taking place thru 31 Dec.
15 Sep 2000
Sydney (Australia) Summer Olympiad opens.
1 Jan 2001
This is the actual start of the new millennium, C.E.
-- If YOU have something which you would like to see in this
FIDONEWS 14-07 Page 25 17 Feb 1997
Future History, please send a note to the FidoNews Editor.
-----------------------------------------------------------------
FIDONEWS 14-07 Page 26 17 Feb 1997
=================================================================
FIDONET SOFTWARE LISTING
=================================================================
Latest Greatest Software Versions
by Peter E. Popovich, 1:363/264
I'm going out on a limb here, but I'm -fairly- sure that all of the
utilities listed in the old format for OS/2 aren't used any more. I
could easily be wrong, though. If I am, all you have to do to keep
a specific utility in the list is send me netmail by the 28th.
Fair warning: Macintosh, Amiga, and Atari sections are close behind.
Currently the old format takes up 45% of the list. I expect that to
drop to well under 40% by the 3 Mar 97 issue and to under 25% by 7
Apr 97.
Phased out this week: "Xenix/Unix 386 -- Other Utilities" Section
Phase-out highlights:
This week: "OS/2 Systems" Section
Deadline for info: 28 Feb 1997.
Last week: "Tandy Color Computer 3 (OS-9 Level II)" Section
Deadline for info: 21 Feb 1997.
-=- Snip -=-
Submission form for the Latest Greatest Software Versions column
OS Platform :
Software package name :
Version :
Function(s) - BBS, Mailer, Tosser, etc. :
Freeware / Shareware / Commercial? :
Author / Support staff contact name :
Author / Support staff contact node :
Magic name (at the above-listed node) :
Please include a sentence describing what the package does.
Please send updates and suggestions to: Peter Popovich, 1:363/264
-=- Snip -=-
MS-DOS:
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
Act-Up 4.6 G D Chris Gunn 1:15/55 ACT-UP
ALLFIX 4.40 T S Harald Harms 2:281/415 ALLFIX
Announcer 1.1 O S Peter Karlsson 2:206/221 ANNOUNCE
BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BDOS_260.ZIP
BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_DOS
FIDONEWS 14-07 Page 27 17 Feb 1997
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
CheckPnt 1.0 O G Michiel vd Vlist 2:500/9 CHECKPNT
FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FASTECHO
FastEcho/16 1.45a T S Tobias Burchhardt 2:2448/400 FE16
FidoBBS (tm) 12u B S Ray Brown 1:1/117 FILES
FrontDoor 2.12 M S JoHo 2:201/330 FD
FrontDoor 2.20c M C JoHo 2:201/330 FDINFO
GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO
GoldED 2.50 O S Len Morgan 1:203/730 GED
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
GoldNODE 2.50 O S Len Morgan 1:203/730 GEN
Imail 1.75 T S Michael McCabe 1:1/121 IMAIL
ImCrypt 1.04 O G Michiel vd Vlist 2:500/9 IMCRYPT
InfoMail 1.11 O F Damian Walker 2:2502/666 INFOMAIL
InfoMail/386 1.20 O F Damian Walker 2:2502/666 INFO386
InterEcho 1.19 T C Peter Stewart 1:369/35 IEDEMO
InterMail 2.29k M C Peter Stewart 1:369/35 IMDEMO
InterPCB 1.52 O S Peter Stewart 1:369/35 INTERPCB
IPNet 1.11 O S Michele Stewart 1:369/21 IPNET
JD's CBV 1.4 O S John Dailey 1:363/277 CBV
Jelly-Bean 1.01 T S Rowan Crowe 3:635/727 JELLY
Jelly-Bean/386 1.01 T S Rowan Crowe 3:635/727 JELLY386
JMail-Hudson 2.81 T S Jason Steck 1:285/424 JMAIL-H
JMail-Goldbase 2.81 T S Jason Steck 1:285/424 JMAIL-G
MakePl 1.9 N G Michiel vd Vlist 2:500/9 MAKEPL
Marena 1.1 beta O G Michiel vd Vlist 2:500/9 MARENA
Maximus 3.01 B P Tech 1:249/106 MAX
McMail 1.0 M S Michael McCabe 1:1/148 MCMAIL
MDNDP 1.18 N S Bill Doyle 1:388/7 MDNDP
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
Opus CBCS 1.73a B P Christopher Baker 1:374/14 OPUS
O/T-Track 2.63a O S Peter Hampf 2:241/1090 OT
PcMerge 2.7 N G Michiel vd Vlist 2:500/9 PCMERGE
PlatinumXpress 1.3 M C Gary Petersen 1:290/111 PX13TD.ZIP
QuickBBS 2.81 B S Ben Schollnick 1:2613/477 QUICKBBS
RAR 2.00 C S Ron Dwight 2:220/22 RAR
RemoteAccess 2.50 B S Mark Lewis 1:3634/12 RA
Silver Xpress
Door 5.4 O S Gary Petersen 1:290/111 FILES
Reader 4.4 O S Gary Petersen 1:290/111 SXR44.ZIP
Spitfire 3.51 B S Mike Weaver 1:3670/3 SPITFIRE
Squish 1.11 T P Tech 1:249/106 SQUISH
StealTag UK 1.c... O F Fred Schenk 2:284/412 STEAL_UK
StealTag NL 1.c... O F Fred Schenk 2:284/412 STEAL_NL
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL
Terminate 4.00 O S Bo Bendtsen 2:254/261 TERMINATE
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
TriBBS 10.0 B S Patrick Driscoll 1:372/19 TRIBBS
TriDog 10.0 M S Patrick Driscoll 1:372/19 TRIDOG
TriToss 10.0 T S Patrick Driscoll 1:372/19 TRITOSS
WaterGate 0.92 G S Robert Szarka 1:320/42 WTRGATE
WWIV 4.24a B S Craig Dooley 1:376/126 WWIV
WWIVTOSS 1.36 T S Craig Dooley 1:376/126 WWIVTOSS
xMail 2.00 T S Thorsten Franke 2:2448/53 XMAIL
XRobot 3.01 O S JoHo 2:201/330 XRDOS
FIDONEWS 14-07 Page 28 17 Feb 1997
OS/2:
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
ALLFIX/2 1.10 T S Harald Harms 2:281/415 AFIXOS2
BGFAX 1.60 O S B.J. Guillot 1:106/400 BGFAX
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BOS2_260.ZIP
BinkleyTerm-XE XR4 M F Thomas Waldmann 2:2474/400 BTXE_OS2
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
FastEcho 1.45a T S Tobias Burchhardt 2:2448/400 FE2
FleetStreet 1.19 O S Michael Hohner 2:2490/2520 FLEET
GIGO 07-14-96 G S Jason Fesler 1:1/141 INFO
GoldED 2.50 O S Len Morgan 1:203/730 GEO
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
GoldNODE 2.50 O S Len Morgan 1:203/730 GEN
ImCrypt 1.04 O G Michiel vd Vlist 2:500/9 IMCRYPT
Maximus 3.01 B P Tech 1:249/106 MAXP
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
PcMerge 2.3 N G Michiel vd Vlist 2:500/9 PCMERGE
RAR 2.00 C S Ron Dwight 2:220/22 RAR2
Squish 1.11 T P Tech 1:249/106 SQUISHP
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAIL2
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
XRobot 3.01 O S JoHo 2:201/330 XROS2
Windows (16-bit apps):
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL
FrontDoor APX 1.10 P S Mats Wallin 2:201/329 FDAPXW
Windows (32-bit apps):
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
BeeMail 1.0 M C Andrius Cepaitis 2:470/1 BEEMAIL
Binkley Docs 2.60 M F Bob Juge 1:1/102 BDOC_260.ZIP
BinkleyTerm 2.60 M F Bob Juge 1:1/102 BW32_260.ZIP
CFRoute 0.92 O G C. Fernandez Sanz 2:341/70 CFR
GoldED 2.50 O S Len Morgan 1:203/730 GEO
GoldED Docs 2.50 O S Len Morgan 1:203/730 GEM
Maximus 3.01 B P Tech 1:249/106 MAXN
Msged/NT 4.00 O G Andrew Clarke 3:635/728 MSGNT400.ZIP
PlatinumXpress 2.00 M C Gary Petersen 1:290/111 PXW-INFO
T-Mail 2.599I M S Ron Dwight 2:220/22 TMAILNT
WinFOSSIL/95 1.12 r4 F S Bryan Woodruff 1:343/294 WNFOSSIL.ZIP
WinFOSSIL/NT 1.0 beta F S Bryan Woodruff 1:343/294 NTFOSSIL.ZIP
Unix:
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
ifmail 2.9 M G Eugene Crosser 2:293/2219 IFMAIL
ifmail-tx ...tx7.9 M G Pablo Saratxaga 2:293/2219 IFMAILTX
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
Amiga:
FIDONEWS 14-07 Page 29 17 Feb 1997
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
CrashMail 1.23 T X Fredrik Bennison 2:205/324 CRASHMAIL
CrashTick 1.1 O F Fredrik Bennison 2:205/324 CRASHTICK
DLG Pro BBOS 1.15 B C Holly Sullivan 1:202/720 DLGDEMO
GMS 1.1.85 M S Mirko Viviani 2:331/213 GMS
Msged 4.00 O G Paul Edwards 3:711/934 MSGED
Tobruk 0.33 T G Paul Edwards 3:711/934 TOBRUK
Atari:
Program Name Version F C Contact Name Node Magic Name
----------------------------------------------------------------------
BinkleyTerm/ST 3.18pl1 M F Bill Scull 1:363/112 BINKLEY
Function: B-BBS, P-Point, M-Mailer, N-Nodelist, G-Gateway, T-Tosser,
C-Compression, F-Fossil, O-Other. Note: Multifunction will
be listed by the first match.
Cost: P-Free for personal use, F-Freeware, S-Shareware, C-Commercial,
X-Crippleware, D-Demoware, G-Free w/ Source
Old info from: 01/27/92
---------------------------------------------------------------------
MS-DOS Systems Other Utilities Other Utilities
-------------- Name Version Name Version
-------------------- --------------------
Network Mailers 2DAPoint 1.50* Netsex 2.00b
Name Version 4Dog/4DMatrix 1.18 OFFLINE 1.35
-------------------- ARCAsim 2.31 Oliver 1.0a
D'Bridge 1.30 ARCmail 3.00* OSIRIS CBIS 3.02
Dreamer 1.06 Areafix 1.20 PKInsert 7.10
Dutchie 2.90c ConfMail 4.00 PolyXarc 2.1a
Milqtoast 1.00 Crossnet 1.5 QM 1.00a
PreNM 1.48 DOMAIN 1.42 QSort 4.04
SEAdog 4.60 DEMM 1.06 RAD Plus 2.11
SEAmail 1.01 DGMM 1.06 Raid 1.00
TIMS 1.0(mod8) DOMAIN 1.42 RBBSMail 18.0
EEngine 0.32 ScanToss 1.28
Compression EMM 2.11* ScMail 1.00
Utilities EZPoint 2.1 ScEdit 1.12
Name Version FGroup 1.00 Sirius 1.0x
-------------------- FidoPCB 1.0s@ SLMail 2.15C
ARC 7.12 FNPGate 2.70 StarLink 1.01
ARJ 2.20 GateWorks 3.06e TagMail 2.41
LHA 2.13 GMail 2.05 TCOMMail 2.2
PAK 2.51 GMD 3.10 Telemail 1.5*
PKPak 3.61 GMM 1.21 TGroup 1.13
PKZip 1.10 GROUP 2.23 TIRES 3.11
GUS 1.40 TMail 1.21
NodeList Utilities Harvey's Robot 4.10 TosScan 1.00
Name Version HeadEdit 1.18 UFGATE 1.03
-------------------- HLIST 1.09 VPurge 4.09e
EditNL 4.00 ISIS 5.12@ WEdit 2.0@
FDND 1.10 Lola 1.01d WildMail 2.00
MakeNL 2.31 Mosaic 1.00b WMail 2.2
FIDONEWS 14-07 Page 30 17 Feb 1997
Parselst 1.33 MailBase 4.11a@ WNode 2.1
Prune 1.40 MSG 4.5* XRS 4.99
SysNL 3.14 MsgLnk 1.0c XST 2.3e
XlatList 2.90 MsgMstr 2.03a YUPPIE! 2.00
XlaxNode/Diff 2.53 MsgNum 4.16d ZmailH 1.25
MSGTOSS 1.3 ZSX 2.40
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OS/2 Systems
------------
Other Utilities Other Utilities
BBS Software Name Version Name Version
Name Version -------------------- --------------------
-------------------- ARC 7.12 oMMM 1.52
Kitten 1.01 ARC2 6.01 Omail 3.1
SimplexBBS 1.04.02+ ConfMail 4.00 Parselst 1.33
EchoStat 6.0 PKZip 1.02
Network Mailers EZPoint 2.1 PMSnoop 1.30
Name Version FGroup 1.00 PolyXOS2 2.1a
-------------------- GROUP 2.23 QSort 2.1
BinkleyTerm(S) 2.50 LH2 2.11 Raid 1.0
BinkleyTerm/2-MT MSG 4.2 Remapper 1.2
1.40.02 MsgLink 1.0c Tick 2.0
SEAmail 1.01 MsgNum 4.16d VPurge 4.09e
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
BBS Software Macintosh Other Software
Name Version --------- Name Version
-------------------- --------------------
FBBS 0.91 Network Mailers MacArd 0.04
Hermes 1.6.1 Name Version Mantissa 3.21
Mansion 7.15 -------------------- Mehitable 2.0
Precision Sys. 0.95b Copernicus 1.0 OriginatorII 2.0
Red Ryder Host 2.1 Tabby 2.2 PreStamp 3.2
Telefinder Host StuffIt Classic 1.6
2.12T10 Other Software SunDial 3.2
Name Version TExport 1.92
-------------------- TimeStamp 1.6
Point System ArcMac 1.3 TImport 1.92
Software AreaFix 1.6 Tset 1.3
Name Version Compact Pro 1.30 TSort 1.0
-------------------- EventMeister 1.0 UNZIP 1.02c
Copernicus 1.00 Export 3.21 Zenith 1.5
CounterPoint 1.09 Import 3.2 Zip Extract 0.10
MacWoof 1.1 LHARC 0.41
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Amiga Network Mailers Other Software
----- Name Version Name Version
-------------------- --------------------
BBS Software BinkleyTerm 1.00 Areafix 1.48
Name Version TrapDoor 1.80 AReceipt 1.5
-------------------- WelMat 0.44 ChameleonEdit 0.11
FIDONEWS 14-07 Page 31 17 Feb 1997
4D-BBS 1.65 ConfMail 1.12
Falcon CBCS 1.00 ElectricHerald 1.66
Starnet 1.0q@ Compression FFRS 1.0@
TransAmiga 1.07 Utilities FileMgr 2.08
XenoLink 1.0 Name Version Fozzle 1.0@
-------------------- Login 0.18
AmigArc 0.23 MessageFilter 1.52
NodeList Utilities booz 1.01 Message View 1.12
Name Version LHARC 1.30 oMMM 1.50
-------------------- LhA 1.10 PolyXAmy 2.02
ParseLst 1.66 LZ 1.92 RMB 1.30
Skyparse 2.30 PkAX 1.00 Roof 46.15
TrapList 1.40 UnZip 4.1 RoboWriter 1.02
Zippy (Unzip) 1.25 Rsh 4.07a
Zoo 2.01 Tick 0.75
TrapToss 1.20
|Contact: Maximilian Hantsch 2:310/6| Yuck! 2.02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
BBS Software Atari ST/TT
Name Version -----------
--------------------
FIDOdoor/ST 2.5.1 Network Mailers Other Utilities
FiFo 2.1v Name Version Name Version
LED ST 1.00 -------------------- --------------------
QuickBBS/ST 1.06* The Box 1.95* ApplyList 1.00@
Burep 1.1
Compression ComScan 1.04
Utilities NodeList Utilities ConfMail 4.10
Name Version Name Version Echoscan 1.10
-------------------- -------------------- FDrenum 2.5.2
ARC 6.02 ParseList 1.30 FastPack 1.20
LHARC 2.01i EchoFix 1.20 Import 1.14
PackConvert sTICK/Hatch 5.50 oMMM 1.40
STZip 1.1* Pack 1.00
UnJARST 2.00 Trenum 0.10
WhatArc 2.02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Tandy Color Computer 3 (OS-9 Level II) Other Utilities
-------------------------------------- Name Version
--------------------
BBS Software Compression Utility Ascan 1.2
Name Version Name Version AutoFRL 2.0
-------------------- -------------------- Bundle 2.2
RiBBS 2.02+ Ar 1.3 CKARC 1.1
DeArc 5.12 EchoCheck 1.01
OS9Arc 1.0 FReq 2.5a
UnZip 3.10 LookNode 2.00
UnLZH 3.0 ParseLST
PReq 2.2
RList 1.03
RTick 2.00
UnBundle 1.4
FIDONEWS 14-07 Page 32 17 Feb 1997
UnSeen 1.1
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Key to old info:
+ - Netmail Capable (Doesn't Require Additional Mailer Software)
* - Recently Updated Version
@ - New Addition
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Please send updates and suggestions to: Peter Popovich, 1:363/264
-----------------------------------------------------------------
FIDONEWS 14-07 Page 33 17 Feb 1997
=================================================================
FIDONEWS PUBLIC-KEY
=================================================================
[this must be copied out to a file starting at column 1 or
it won't process under PGP as a valid public-key]
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.2
Comment: Clear-signing is Electronic Digital Authenticity!
mQCNAzINVLcAAAEEAM5dZN6t6j5Yc0kl7qegVFfiBeVoteuhDg4ay8h43u38Q4kO
eJ9Mm7J89wXFb9vgouBVb4biIN6bTWCwcXTbGhBe5OIceLvluuxuEKsaIs/UwXNe
Ogx5azIPhRfC7MJDe41Z8tMEBuHY/NE88cuxQ8yXWO126IRttavu6L/U5BwRAAUR
tCRGaWRvTmV3cyBFZGl0b3IgPDE6MS8yM0BmaWRvbmV0Lm9yZz6JAJUDBRAyGwFS
JZMgw7eCKz0BAZl0A/9xrfhpsEOqGiPfjy2qd9dv6tvSVPPVFu+Wy1lGTHYtuTtg
FIN3fQ47AM3XzqHxWRWvp/xZYgR6sRICL7UFx94ShYBQc7CyqBBZKA0IvIWqXP/g
c4Br+gQJR6CLiQK7TUyjUbqNbs6QAxuNUi4xFQM+O2Gene5/iTjHFmmSDj2C9YkB
FQMFEDIOmHDTQ6/52IG1SQEBQ78H/Rz/mleIrtZwFIOhzy3JH4Z6FUTfZuM9nPcs
1ZLjZCPptHvY7wEYJWGr03lPPJ6tj1VBXwTrWJTf/hOLsoi00GKV8t1thjqGDo23
O91/bSQ+Vn0vBQ2vOEJys8ftxdoLJAyI5YLzHVT+RsMTQLIXVuPyrNcKs1vC2ql+
UDHpU1R+9cG9JUEHpGI6z0DPnQ74SKbQH3fiVBpHhYx4BmvcBC4gWQzKMkDWFiq3
8AssIZ7b9lWl3OBgQ4UM1OIDKoJyjRewIdKyl7zboKSt6Qu8LrcsXO3kb81YshOW
ZpSS3QDIqfZC4+EElnB15l4RcVwnPHBaQY0FxUr4Vl4UWM36jbuJAJUDBRAyDpgY
q+7ov9TkHBEBAQGoA/sFfN07IFQcir456tJfBfB9R5Z6e6UKmexaFhWOsLHqbCq6
3FGXDLeivNn6NTz81QeqLIHglTuM3NP1mu8sw215klAG8G3M1NA2xLw7Eqhspze2
raGvNeEwxl8e+PY9aZwBj4UWU+CmIm6QNiP0MtvR7QYDIKn5mZCDc3CLmr942IkB
FQMFEDIOh0O8AhTPqRipPQEB4EYH/1gkDmdHL6lbEkFuQLrylF+weBl0XQ+kv7ER
vWXYrvIrkppxtc4VAge6CXXEbOGJnvkFHgyNZzO9Q9O64QsmZvjip+4lhDLeNrdH
X9DizS4YKXxkSKr9Yltmn2/AlBCx6jwcDIfkqy/P1tNWcikxZZMd6KryK0Wsres9
Ik12OmVmJjQSxb5bS6Q8aYUbV3qwosGXTqy+BzYh/UYAX/XJIWa5kxFVSPKFSZ+5
toiSzANd9SpHPEogGvQDHJlJ23lmsMx/6uHsR1LTsQ8su8zIk92XyqePJTjlMx2j
D7KJWNR7Zzu4QHCXBkga5W8l2FfPk7D3+o7bXTLRuR1yTYGdNoiJAJUCBRAyDhwt
SlKLwP4OFW0BAdaMA/9rcWQlSq44K9JuJ7fZUgt9fwxGreTud9fC8DvlbUW79+CA
AHLTLLagcEF1OKsWzVBWcA2JEAp+TUTqktRN0oD8vnaw3uNJd1G5KK59hw0WR8x1
v4ivypbSjiq95Y3gBunb7WjpyiFRWDlm0PrKrWHtbWzjnpPIpetln1UuqsSfbokB
FQIFEDIOG9C3N61ZQ4Dr/QEBIzMH/1VxxztmBPBszbjZLDO8Svcax9Ng8IcWpcDy
WqHCAA2Hoe5VtMD0v6w31ZgVqTPIvCark2Y/aTR1GofiuN9NUqbVV534AgAYLzYk
DMT1swsPvqDTpOYgQl6PCGh6A5JGAbWJfKkX9XCUHJAAmiTsEVRNnjOgL+p6qjoh
EfIG8CGehghWSRKl5eGeDAtbXupZKNjFI1t2XV+ks0RFQ/RPuTH7pF7pk7WO6Cyg
+Dk2ZMgua0HRL1fXvHKb5Xzr3MVgsbAl5gP8ooIiD9MI/x5Irh3oo58VyoEZNBs/
Kz+drGFDPljcS6fdiVCFtYIzMrshY6YsfLi0aB8fwOvFtxgBqli0J0NocmlzdG9w
aGVyIEJha2VyIDwxOjE4LzE0QGZpZG9uZXQub3JnPrQoQ2hyaXN0b3BoZXIgQmFr
ZXIgPGNiYWtlcjg0QGRpZ2l0YWwubmV0Pg==
=61OQ
-----END PGP PUBLIC KEY BLOCK-----
File-request FNEWSKEY from 1:1/23 [1:18/14] or download it from the
Rights On! BBS at 1-904-409-7040 anytime except 0100-0130 ET and Zone
1 ZMH at 1200-9600+ HST/V32B. The FidoNews key is also available on
the FidoNews homepage listed in the Masthead information.
-----------------------------------------------------------------
FIDONEWS 14-07 Page 34 17 Feb 1997
=================================================================
FIDONET BY INTERNET
=================================================================
This is a list of all FidoNet-related sites reported to the Editor as
of this appearance.
============
FidoNet:
Homepage http://www.fidonet.org
FidoNews http://ddi.digital.net/~cbaker84/fidonews.html
HTML FNews http://www.geocities.com/Athens/6894/
WWW sources http://www.scms.rgu.ac.uk/students/cs_yr94/lk/fido.html
FTSC page http://www2.blaze.net.au/ftsc.html
Echomail http://www.portal.ca/~awalker/index.html
WebRing http://ddi.digital.net/~cbaker84/fnetring.html
============
Zone 1: http://www.z1.fidonet.org
Region 10:
http://www.psnw.com/~net205/region10.html
http://www.dharmanet.org/BDO/net125.html
Region 15:
http://www.smrtsys.com/region15/
Region 16:
http://www.tiac.net/users/satins/region16.htm
http://www.tiac.net/users/satins/net130.htm
Region 17:
http://www.portal.ca/~awalker/region17.htm
Region 18:
http://www.citicom.com/fido.html
Region 19:
http://ccove.n-link.com/
============
Zone 2: http://www.z2.fidonet.org
ZEC2 http://fidoftp.paralex.co.uk/zec.htm
Region 29: http://www.rtfm.be/fidonet/ (in French)
Region 36: http://www.geocities.com/SiliconValley/7207/
============
Zone 3: http://www.z3.fidonet.org
FIDONEWS 14-07 Page 35 17 Feb 1997
============
Zone 4: (not yet listed)
============
Zone 5: (not yet listed)
============
Zone 6: http://www.z6.fidonet.org
============
-----------------------------------------------------------------
FIDONEWS 14-07 Page 36 17 Feb 1997
=================================================================
FIDONEWS INFORMATION
=================================================================
------- FIDONEWS MASTHEAD AND CONTACT INFORMATION -------
Editor: Christopher Baker
Editors Emeritii: Tom Jennings, Thom Henderson, Dale Lovell,
Vince Perriello, Tim Pozar, Sylvia Maxwell,
Donald Tees
"FidoNews Editor"
FidoNet 1:1/23
BBS 1-904-409-7040, 300/1200/2400/14400/V.32bis/HST(ds)
more addresses:
Christopher Baker -- 1:18/14, cbaker84@digital.net
cbaker84@aol.com
cbaker84@msn.com
(Postal Service mailing address)
FidoNews Editor
P.O. Box 471
Edgewater, FL 32132-0471
U.S.A.
voice: 1-904-409-3040 [1400-2100 ET only, please]
[1800-0100 UTC/GMT]
------------------------------------------------------
FidoNews is published weekly by and for the members of the FIDONET
INTERNATIONAL AMATEUR ELECTRONIC MAIL system. It is a compilation
of individual articles contributed by their authors or their
authorized agents. The contribution of articles to this compilation
does not diminish the rights of the authors. OPINIONS EXPRESSED in
these articles ARE THOSE OF THE AUTHORS and not necessarily those of
FidoNews.
Authors retain copyright on individual works; otherwise FidoNews is
Copyright 1997 Christopher Baker. All rights reserved. Duplication
and/or distribution permitted for noncommercial purposes only. For
use in other circumstances, please contact the original authors, or
the Editor.
=*=*=*=*=*=*=*=*=
OBTAINING COPIES: The most recent issue of FidoNews in electronic
form may be obtained from the FidoNews Editor via manual download or
file-request, or from various sites in the FidoNet and Internet.
PRINTED COPIES may be obtained by sending SASE to the above postal
address. File-request FIDONEWS for the current Issue. File-request
FNEWS for the current month in one archive. Or file-request specific
back Issue filenames in distribution format [FNEWSEnn.ZIP] for a
FIDONEWS 14-07 Page 37 17 Feb 1997
particular Issue. Monthly Volumes are available as FNWSmmmy.ZIP
where mmm = three letter month [JAN - DEC] and y = last digit of the
current year [7], i.e., FNWSFEB7.ZIP for all the Issues from Feb 97.
Annual volumes are available as FNEWSn.ZIP where n = the Volume number
1 - 14 for 1984 - 1997, respectively. Annual Volume archives range in
size from 48K to 1.4M.
INTERNET USERS: FidoNews is available via:
http://www.fidonet.org/fidonews.htm
ftp://ftp.fidonet.org/pub/fidonet/fidonews/
ftp://ftp.aminet.org/pub/aminet/comm/fido/
*=*=*
You may obtain an email subscription to FidoNews by sending email to:
jbarchuk@worldnet.att.net
with a Subject line of: subscribe fnews-edist
and no message in the message body. To remove your name from the email
distribution use a Subject line of: unsubscribe fnews-edist with no
message to the same address above.
*=*=*
You can read the current FidoNews Issue in HTML format at:
http://www.geocities.com/Athens/6894/
STAR SOURCE for ALL Past Issues via FTP and file-request -
Available for FReq from 1:396/1 or by anonymous FTP from:
ftp://ftp.sstar.com/fidonet/fnews/
Each yearly archive also contains a listing of the Table-of-Contents
for that year's issues. The total set is currently about 11 Megs.
=*=*=*=
The current week's FidoNews and the FidoNews public-key are now also
available almost immediately after publication on the Editor's new
homepage on the World Wide Web at:
http://ddi.digital.net/~cbaker84/fidonews.html
There are also links there to jim barchuk's HTML FidoNews source and
to John Souvestre's FTP site for the archives. There is also an email
link for sending in an article as message text. Drop on over.
=*=*=*=*=*=*=*=*=
A PGP generated public-key is available for the FidoNews Editor from
FIDONEWS 14-07 Page 38 17 Feb 1997
1:1/23 [1:18/14] by file-request for FNEWSKEY or by download from
Rights On! BBS at 1-904-409-7040 as FIDONEWS.ASC in File Area 18. It
is also posted twice a month into the PKEY_DROP Echo available on the
Zone 1 Echomail Backbone.
*=*=*=*=*
SUBMISSIONS: You are encouraged to submit articles for publication in
FidoNews. Article submission requirements are contained in the file
ARTSPEC.DOC, available from the FidoNews Editor, or file-requestable
from 1:1/23 [1:18/14] as file "ARTSPEC.DOC". ALL Zone Coordinators
also have copies of ARTSPEC.DOC. Please read it.
"Fido", "FidoNet" and the dog-with-diskette are U.S. registered
trademarks of Tom Jennings, P.O. Box 410923, San Francisco, CA 94141,
and are used with permission.
"Disagreement is actually necessary,
or we'd all have to get in fights
or something to amuse ourselves
and create the requisite chaos."
-Tom Jennings
-30-
-----------------------------------------------------------------
Download original FidoNews · Volume 14 (1997) · ← Previous · Next →