CDP nodes who want to add extended support the the Fido-Package deluxe, can
setup four more optional request magics in addition to the standard
CDP requirements: BOXLIST, NETZLIST, NODETEXT and PNT0002.
With BOXLIST a file box.lst is expected, with NETZLIST a netz.lst - both have
the same structure as the Fido area list (area name, at least one space,
description). In box.lst you can put those areas, which are only available
at your system for the systems directly connected with you and for your points,
so these are the (local) box areas. And in netz.lst are the areas that are
available in your network.

Example how it looks at Henning Schroeer (2457/265):

===== cut begin: box.lst =====
ccc.chat        DAS CHATecho schlechthin.
ccc.bs          Rund ums Programmieren, Betriebssysteme, etc.
ccc.postings    Hier kommen alle interessanten Mails hin.
ccc.linking     In diesem Echo werden wichtige Sachen gepostet. Mandatory.
ccc.flea        Wer was verkaufen will schreibts hier rein.
ccc.english     English speaking area for chats and questions
ccc.schule_uni  Alles rund um das Studium und Schule (Hausaufgaben, Lehrinhalte..)
CDPOINT         Diskussionen um Michael Haase's Fido-Paket deluxe.
===== cut end =====

===== cut begin: netz.lst =====
2457.net       Das Netz-Echo des Suedwestfalen-Netzes
2457.markt     An- und Verkauf im Netz
2457.announce  Frisch eingetroffene Files
2457.bs        Alles zu Betriebssystemen (Windows, Linux, OS/2, ..)
F.GER.TALK.2448.AND.2457  Netzuebergreifendes Echo zum 2448er
===== cut end =====

American/International areas can be packed as BACKBONE.NA (format like the
other lists) additionally in the ECHO0002.ZIP.
It should also work if you put box.lst and netz.lst also into ECHO0002.ZIP
(with the ECHO0002.LST containing the main mail areas), but that is not the
normal behaviour.

Note: In the ECHO0002.LST do not belong areas that are already included in
the BACKBONE.NA (American areas)!

NODETEXT expects nodehtm.zip - there can be one or more files in the zip file,
but no sub-directories. There you can put infos for the point about yourself
and your system or about whatever you like. It is displayed when the point
clicks on "Info, ..." in the main menu and then "Node-Info". The index file is
node.htm - so this is the one file that at least must be in the zip file.
Additionally other htm, html or jpg files can be included and linked. But not
too complex html files, it's just a simple html viewer I implemented for the
Fido-Package deluxe (FPD).

PNT0002 is the pointlist in Z2 format, that is because this is the only format
that is available world-wirde. Other formats are mostly only known in one or
some regions. Unfortunately the Z2 pointlist keeper is not very reliabel.

PNT0002 expects PNT0002.ZIP. In that zip R24PNT.??? is the expected list. And
the file echo R24PNT_D is connected with the diff files. The POINTS24 format
that is common in R24 must not be included in that zip file, it doesn't work.
Pointlists became very uncommon in Fidonet, it's rarely supported. And because
most nodes don't have a Z2 pointlist, the FPD requests it at one German system
that I know that it has these. But only the German points are included, so it's
probably not of much use for you.

At the moment (and for the future either) there seems no good solution for a
pointlist that works for everyone. The node might tell the point how to get the
pointlist (and maybe connects him to the appropriate file echo) and tells him
what to change in the config files (that is fastlst.cfg).


Membership cancellation of a point:
-----------------------------------
During the point's cancellation process all areas will be unsubscribed and a
file PPPPZZZZ.DEL will be sent to the node, in which the PPPP stands for
the point number that is cancelled in hex format filled up with leading zeros
(e.g. 000A for point 10). And ZZZZ is the zone in hex, filled up with leading
zeros (e.g. 0002 for zone 2). So, the complete file name would be 000A0002.DEL
for this example.
The content of this file are the following keywords (each followed by the
appropriate data):
POINTNUMBER=
NODENUMBER=
PASSWORD=
AREAFIXPW=
TICKERPW=
PKTPW=

When the CDP node finds such a file in his secured inbound, then he can - after
checking the passwords in that file - delete this point (manually or automatedly).

--
Info from: 07-JUN-2002