home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Elysian Archive
/
AmigaElysianArchive.iso
/
comm
/
rr20eval.lha
/
docs
/
RadaReader.Man
next >
Wrap
Text File
|
1993-01-24
|
81KB
|
2,882 lines
Page 1 RadaReader V2.0, The Manual Page 1
RRRR AAA DDDD AAA RRRR EEEEE AAA DDDD EEEEE RRRR
R R A A D D A A R R E A A D D E R R
RRRR AAAAA D D AAAAA RRRR EEE AAAAA D D EEE RRRR
R R A A D D A A R R E A A D D E R R
R R A A DDDD A A R R EEEEE A A DDDD EEEEE R R
RadaReader V2.0.
The Powerful Amiga Mail Processor.
By Jesper Jensen.
Copyright © 1991,1992, Jesper Jensen.
All right reserved.
FidoNet: 2:230/417.0
AmyNet: 39:141/117.0
BadNet: 92:910/106.0
InterNet: Radagast@iluvatar.bbs.bad.se
2.0 Jesper Jensen, DK 2.0
Page 2 RadaReader V2.0, The Manual Page 2
1. Introduction
A new update. New features. That is, reading a long and boring
manual again :-). This manual is intended to be used by newcomers to
the RadaReader system. Old users might just want to browse through
this manual for new stuff, as it is not neccassary for them to read
about, how the RadaReader system works.
As RadaReader has been heavily advanced, much new stuff is
introduced, so this manual will concentrate more on the new stuff,
than the old. If you find something missing, you might want to try
the manual for RadaReader V1.2, as this one explains fidonet and
other things, nice to know, in depth. Furthermore, I'd recommend to
the new user of FidoNet (or other nets) to get hold of 'FidoNet.Man',
which is distributed with the TrapLand productions (TrapDoor,
TrapList aso.).
For your convenience there is a table of contents last in this
manual, but I advise you to read the entire manual anyway.
2.0 Jesper Jensen, DK 2.0
Page 3 RadaReader V2.0, The Manual Page 3
2. Getting started
RadaReader requires a few things, before being able to run. This
chapter is devoted to explaining these things.
2.1. Requirements
First of all, RadaReader will only run under KS 2.0. So you'll
have to have the 2.0 ROM. Furthermore, RadaReader uses the
ReqTools.library by Nico Francois. You'll also have to assign 'MAIL:'
to your mail directory, as RadaReader uses this in it's processing.
In the software department also : you need copies of the
standard workbench commands Copy and Delete to be in your command
search path ('C:').
2.2. Keyfile
The keyfile, is a little file, that unlocks certain errors in
RadaReader. This file is obtained by registrating RadaReader. This
can be done at the support sites or directly to the author (chapter
13).
2.0 Jesper Jensen, DK 2.0
Page 4 RadaReader V2.0, The Manual Page 4
3. The mail processor's job
The first thing to do, when setting up a mail system, is to
define, what it should be capable of.
3.1. Mail Processing
FidoNet is a large chain of independant systems, which then
distribute mail to one another. In order to do this without problems,
certain steps have to be watched. These include the standards for
exchanging mail. The mail processor is the tool, that watches these
standards, and enables the sysop to exchange mail correctly.
3.2. Node vs. Point
As of this version, RadaReader is capable of both running a node
system as well as a point system. The point system is an easy system
to maintain. Being a point is like being an 'extended' user of a
BBS/Mail System. A point picks up and delivers mail in sessions with
the socalled boss, that is a node. The point, normally, has no
contact with other nodes than the point's boss. Therefore, a point
system does not need to distribute the mail further, a point is a
dead-end in the FidoNet technology.
A node, on the other hand, may have 'downlinks', which should be
feeded with mail, and not just one. Therefore it is crucial for the
node system to know, which links already have a message. Such
information must be stored, and then, in term, processed further.
This information is defined in FTS-4 for those interested.
Information such as SEEN-BY lines and PATH kludges must be stored.
More about, how RadaReader does this later.
3.3. The Mail Editor (Reader)
In order for the node/point to add new messages, some editting
functions must be present. RadaReader is a system containing Tosser
(Importer), Scanner (Exporter) and Editor. Thus RadaReader is
responsible for all mail flow within the system.
The editor enables the sysop to write new messages, reply to old
messages and/or edit existing messages. These (new) messages will
then be exported along with all other mail.
2.0 Jesper Jensen, DK 2.0
Page 5 RadaReader V2.0, The Manual Page 5
4. Configuring RadaReader
Configuring RadaReader is quite a task, if you have not used it
before. RadaReader needs a main configuration file, in which almost
everything about your system is stated.
4.1. Keywords
The configuration of RadaReader is done by creating a normal
ASCII file, containing 'keywords'. These keywords must be used in a
special way, and do all have a special meaning to RadaReader. This
entire chapter is devoted to explaining the keywords of the
RadaReader configuration.
4.1.1. ADDRESS <Number>
ADDRESS enables you to operate echoes in multinet setups.
ADDRESS defines, which of your addresses should be applied to this
particular echo. Therefore it is part of the AREA-ENDAREA structure.
The argument for ADDRESS is a number from 0 - 10. 0 meaning the NODE,
and 1 - 10 is the number of your AKA to use.
Example : ADDRESS 5
Default : ADDRESS 0
4.1.2. AKA <FQFA> <Fakenet> [Domain]
This is part of your global configuration. The AKA keyword makes
RadaReader aware of additional addresses in the system. Fx. the NODE
address could be the FidoNet address of the system, while AKA could
specify AmigaNet, BadNet, VirNet or whatever. It is used in the same
manner as NODE.
Ypu can specify up to 10 additional addresses via the AKA
keyword.
Example : AKA 39:141/117.0 14117 amiganet.ftn
Default : N/A
4.1.3. ARC <Command>
ARC specifies, which archiving method should be used by
default.
Example : ARC UnZip
Default : ARC LHA A
4.1.4. ARCPATH <Directory>
2.0 Jesper Jensen, DK 2.0
Page 6 RadaReader V2.0, The Manual Page 6
When the need arises for storing messages, one can use the
'Archive Message' option from within the editor. RadaReader will then
store the message with some information in the directory given by
'ARCPATH', as Archived_Msgs_Of_***, where '***' is the month.
Example : ARCPATH Mail:Archived/
Default : ARCPATH Mail:Text/
4.1.5. AREA
AREA marks the beginning of an area definition. It _has_ to be
followed by an ENDAREA keyword, for RadaReader to be aware of the new
areas presence.
Example : AREA
Default : N/A
4.1.6. AREAFIXCOMMAND "Command"
The command within the quotation marks will be executed every
time a user has had contact with AreaFix. Nice for updating your text
configuration.
Example : "RRUnInstall >Mail:RadaReader.cfg"
Default : Do nothing
4.1.7. AREAFIXLOG <Path>
As RadaReader can now operate in a node environment, and thus
handle incoming areafix requests, there has to be a log. In this log,
information is saved, concerning AreaFix.
Example : AREAFIXLOG Logs:AreaFix.log
Default : AREAFIXLOG Mail:AreaFix.log
4.1.8. BADDIR <Directory>
Determines which directory should hold the bad messages
imported.
Example : BADDIR Mail:Bad/
Default : BADDIR Mail:Bad_Msgs/
4.1.9. BAKDIR <Directory>
Defines a backup directory, in which RadaReader will store all
incoming mail. Actually, it will do a clone copy, so you can still
2.0 Jesper Jensen, DK 2.0
Page 7 RadaReader V2.0, The Manual Page 7
see the information, that fx. TrapDoor attaches to the files. If you
do not specify any BAKDIR, RadaReader will not make backups.
Example : BAKDIR Mail:Backup/
Default : No backups
4.1.10. COLOR <Where> <Which> <R,G,B>
RadaReader uses three different color sets, when running, one
for the Editor, one for the Browser and one for Requesters. With
COLOR, you can define the palettes. 'Where' should be 'EDITOR',
'BROWSER' or 'REQUESTER', value is stated like this : 'R,G,B', where
R, G and B are numbers between 0 and 15.
Example : COLOR EDITOR 1 15,15,15
Default : Standard OS 2.0 color set
4.1.11. DEFHEADER "String"
DEFHEADER is as reply header for those areas (AREA-ENDAREA),
which do not have a HEADER statement attached to them. You can use
embedded percent commands in these header, and they go like this :
%f ..... First name of sender.
%n ..... Whole name of sender.
%F ..... First name of receiver.
%N ..... Whole name of receiver.
%s ..... The subject.
%d ..... Date (Not with SEADog format currently).
%t ..... Time (do.).
%a ..... Address of sender.
'\r' represents newline.
DEFHEADER, DEFLOGO, DEFORIGIN, HEADER, LOGO, ORIGIN,
FWDTEMPLATE, DESCRIPTION and NAME has to be inside quotation marks.
Example : DEFHEADER "%d, %n (%s) wrote :\r"
Default : N/A
4.1.12. DEFLOGO "String"
DEFLOGO works the same way as DEFHEADER, exept that it is
appended as the last of the message, both in a write and reply. The
embedded percent commands stated above are not recognized by
DEFLOGO/LOGO, but '\r' is.
Example : DEFLOGO "See ya'\rJesper"
2.0 Jesper Jensen, DK 2.0
Page 8 RadaReader V2.0, The Manual Page 8
Default : N/A
4.1.13. DEFMAXMSGS <Number>
DEFMAXMSGS tells RadaReader, how many messages by default should
be left in an area after maintenance.
Example : DEFMAXMSGS 20
Default : DEFMAXMSGS 30
4.1.14. DEFORIGIN "String"
Got the routine by now ? :-). This is of course the default
origin, if no origin has been stated for the area.
Example : DEFORIGIN "Iluvatar BBS, 2200 - 0630, +45-42-730817"
Default : N/A
4.1.15. DESCRIPTION "String"
DESCRIPTION defines a logical name for a conference to be used
in context with AreaFix. Instead of just showing the TAG of the
conference, RadaReader's AreaFix will show the TAG and the
DESCRIPTION definitions for the area.
Example : DESCRIPTION "Yet another amiga area"
Default : N/A
4.1.16. EDITOR <Command>
This keyword defines how your text editor should be run.
RadaReader uses a temporary file for messages being editted. This
file is inserted into the command by a tilde ('~'). The temporary
filename is made up of WORKDIR and 'RR.TEMP', and thus WORKDIR MUST
be defined before EDITOR.
Example : Ed ~ -sticky
Default : N/A
4.1.17. ENDAREA
Marks the end of an area. When RRInstall detects an 'ENDAREA',
it will first check, if anything is wrong, then insert default value,
and last write it and make room for a new one. Thus, it's _very_
important, that the ENDAREA keyword is not forgotten.
Example : ENDAREA
2.0 Jesper Jensen, DK 2.0
Page 9 RadaReader V2.0, The Manual Page 9
Default : N/A
4.1.18. ENDLINK
Marks the end of a link. Same rules applies here as for
ENDAREA.
Example : ENDLINK
Default : N/A
4.1.19. EXPORTCOMMAND "Command"
This command is executed everytime you've exported.
Example : TrapPoll +d
Default : Do nothing
4.1.20. EXPORTTO <FQFA>
For each link receiving a certain conference, you'll have to
include the EXPORTTO keyword. If the EXPORTTO keyword is to be used,
the address has to be defined as a link too (see 4.1.31), otherwise
RRInstall will moan ! :-).
Example : EXPORTTO 2:230/417.0
Default : N/A
4.1.21. EXTERNAL <MenuText> <MenuCommand>
In RadaReader, you have an external menu. it is the rightmost of
the menus, and it contains utilities of your choice. With this you
can access external commands easy and painless (without use of 'x').
Of course it also accepts some templates. These are :
%a : Current area number
%n : Current message number
%z : Zone
%N : Net
%o : Node
%p : point
%f : FakeNet
%A : Full address (FQFA)
%i : Inbound dir
%O : Outbound dir
%P : Current Area Path
%t : Current Area Tag
%s : Name of Sysop, like this : "Jesper Jensen"
2.0 Jesper Jensen, DK 2.0
Page 10 RadaReader V2.0, The Manual Page 10
As you see in the syntax, EXTERNAL takes two arguments. The
first is the name of the menu item, and the second is the command to
execute (with templates).
Example : EXTERNAL AutoReply MAIL:Tools/AutoReply %P %n %A %f %s
Default : N/A
4.1.22. FLAGS <Binary Number>
Flags are used to control users' access to conferences. Fx. you
could set a certain flag for sysop conferences, and then, when a user
requests an availability list the sysop conferences will not be
shown, unless the user has the same flag set in his/her link
definition. FLAGS can hold up to 16 flags, and they are defined like
a binary number. See LINKFLAGS.
FLAGS is stated within an AREA-ENDAREA structure, and controls
thus the availability of an area.
Example : FLAGS 0000010110011110
Default : FLAGS 0000000000000000
4.1.23. FONT <Font> [SIZE <Number>]
Of course you can't be a point, without having tremendous
trouble with your font, whereever you may live :-). Therefore you can
use one of the point-fonts, which can be found on various BBS's. The
'SIZE' keyword is optional, and if omitted, assumed to be 8.
Example : FONT IBM.font
Default : FONT Topaz.font SIZE 8
4.1.24. FORCEINTL
With the FORCEINTL keyword, you can create a better basis for
netmails getting through to thier destination. FORCEINTL means to
tell RadaReader to always include the INTL kludge in a netmail.
Example : FORCEINTL
Default : Only insert INTL, when out-of-zone netmail
4.1.25. FWDTEMPLATE "String"
When forwarding, FWDTEMPLATE will be inserted at the top of the
message. Normally it will show a little info about, which area it
was forwarded from and to, and who did it, original sender aso.
The templates for this are :
2.0 Jesper Jensen, DK 2.0
Page 11 RadaReader V2.0, The Manual Page 11
%% : '%'
%a : Address of original sender
%n : Destination area NAME
%t : Destination area TAG
%N : Source area NAME
%T : Source area TAG
%o : Original sender
%O : Original receiver
%s : Original subject
%d : Original date/time
Otherwise the same rules apply here as for HEADER's and LOGO's.
Example : FWDTEMPLATE " * Forwarded from %T : \r\r"
Default : N/A
4.1.26. HEADER "String"
HEADER is the same as DEFHEADER, exept for the fact, that HEADER
is defined inside the AREA-ENDAREA structure, and hence, it is only
valid for that particular area.
Again : Same rules apply as for DEFHEADER.
Example : HEADER "Hi %f, you wrote :\r\r"
Default : DEFHEADER
4.1.27. HIDEKLUDGE
Instructs RadaReader to hide the kludge.
Example : HIDEKLUDGE
Default : Show kludges
4.1.28. IMPORTONLYKNOWN
If running a node system, it's pretty important (in order to not
being annoying :-)) to make sure, that only echomail from known links
are imported and exported. This is done by IMPORTONLYKNOWN, that will
mark messages from addresses, not defined as LINKs, as ILLEGALs, and
thus put them in your bad messages directory.
Example : IMPORTONLYKNOWN
Default : Import from everybody
4.1.29. INDIR <Directory>
2.0 Jesper Jensen, DK 2.0
Page 12 RadaReader V2.0, The Manual Page 12
Defines your directory for incoming mail packets/bundles.
Example : INDIR IN:
Default : INDIR Mail:Inbound/
4.1.30. INTERLACE
Instructs RadaReader to open an interlaced screen. This does not
yet work properly !.
Example : INTERLACE
Default : Standard workbench-sized screen
4.1.31. KILLDUPES
Tells RadaReader not to import dupes to bad, but to just neglect
them. RadaReader will, however, make an entry in the log!
Example : KILLDUPES
Default : Import dupes to BAD_MSGS.
4.1.32. LINK
Marks the beginning of a LINK definition, that is, a system,
with which the system exchanges mail. All keywords starting with
LINK* must be inside LINK-ENDLINK in order to have any effect.
Example : LINK
Default : N/A
4.1.33. LINKACCOUNTING
Tells RadaReader to count the mail flowing through the system
for this particular link. RadaReader will count :
Exported Echomail
Imported Echomail
Routed NetMail to link.
Routed NetMail from link.
If you use LINKACCOUNTING, the global switch ACCOUTING must be
present in your configuration. ACCOUNTING sets the possibility of
accounting, and RadaReader will not check, if a link has
LINKACCOUNTING set, if ACCOUNTING is not set. This is done to save
time.
Example : LINKACCOUNTING
2.0 Jesper Jensen, DK 2.0
Page 13 RadaReader V2.0, The Manual Page 13
Default : No accounting
4.1.34. LINKADDRESS <FQFA>
Defines the LINK's address.
Example : LINKADDRESS 2:230/417.0
Default : N/A
4.1.35. LINKARC <Command>
Defines the archiving method used, when archiving mail to this
link.
Example : LINKARC LhA A
Default : N/A
4.1.36. LINKFLAGS <Binary Number>
Same as FLAGS. LINKFLAGS and FLAGS are and'ed by AreaFix to see,
if a certain echo is available to a link requesting it.
Example : LINKFLAGS 0101010101010101
Default : LINKFLAGS 0000000000000000
4.1.37. LINKFLOW <Type>
Determines the type of flowfiles to be used in context with this
LINK. Three types are available: NORMAL, HOLD and CRASH.
Example : LINKFLOW NORMAL
Default : N/A
4.1.38. LINKMAIL2D
Isn't used.
4.1.39. LINKPASSWORD <Password>
Defines the password this link uses in his/her sessions with
AreaFix. The password must be present in the subject line of the
message, and must be the first word in this line. If RadaReader
detects a password mismatch, it'll make a note about it in the
areafix log.
Example : LINKPASSWORD Secret
Default : N/A
2.0 Jesper Jensen, DK 2.0
Page 14 RadaReader V2.0, The Manual Page 14
4.1.40. LINKRADAREADER
Tells RadaReader, that the receiving/sending LINK is using
RadaReader as his/her mail processor. RadaReader will then add some
information about the size of the body for faster importing.
Example : LINKRADAREADER
Default : Don't add info mentioned above
4.1.41. LOGFILE <Path>
Path to your logfile.
Example : LOGFILE LOGS:RadaReader.log
Default : LOGFILE Mail:RadaReader.log
4.1.42. LOGO "String"
Same as DEFLOGO, only this one is area-specific.
Example : LOGO "Bye now, Jesper\r"
Default : DEFLOGO
4.1.43. MAIL4D
Tells RadaReader to show 4D info in editor.
Example : MAIL4D
Default : Dunno, really. Include it !
4.1.44. MAXMSGS <Number>
Number of messages, that should be left in an area after
maintenance. This one must be inside an AREA-ENDAREA structure to
have effect.
Example : MAXMSGS 5
Default : DEFMAXMSGS
4.1.45. MSGBUFFER <Number>
Maximum size of message bodies. Can be anynumber, you'd like.
The size is given in bytes.
Example : MSGBUFFER 50000
2.0 Jesper Jensen, DK 2.0
Page 15 RadaReader V2.0, The Manual Page 15
Default : MSGBUFFER 32768 (32 kb)
4.1.46. NAME "String"
A logical name for the area, which will be shown in title bar,
and when shifting between areas.
Example : NAME "NetMail"
Default : N/A (TAG)
4.1.47. NOACTIONWINDOW
Set this, if you do not wish to see information in the action
window at import, export and maintenance.
Example : NOACTIONWINDOW
Default : Use window
4.1.48. NOCHECKDUPES
Tells RadaReader not to check for dupes. RadaReader uses MSGID
kludges for dupe checking, which has made it to a standard thanks to
Jim Nutt's great proposal.
Example : NOCHECKDUPES
Default : Don't check
4.1.49. NODE <FQFA> <Fakenet> [Domain]
Defines your main address. Normally, this would be your FidoNet
address. This is the most important keyword in the configuration of
RadaReader, so remember to include it ! :-)
Example : NODE 2:230/417.0 10417 fidonet.org
Default : N/A (moaning from RRInstall)
4.1.50. NODELIST <Directory>
This one defines the directory, in which a TrapList style
compiled nodelist resides. Thus, in order to use a nodelist, you must
have it compiled with TrapList.
Example : NODELIST NodeList:
Default : N/A
4.1.51. NOSYSTEMLISTS
2.0 Jesper Jensen, DK 2.0
Page 16 RadaReader V2.0, The Manual Page 16
Tells RadaReader's AreaFix not to create system lists if
requested.
Example : NOSYSTEMLISTS
Default : Create them if requested
4.1.52. ORIGIN "String"
Defines an ORIGIN for an area. Must be inside AREA-ENDAREA
structure.
Example : ORIGIN "Iluvatar BBS, home of the divine"
Default : DEFORIGIN
4.1.53. OUTDIR <Directory>
Your outbound directory.
Example : OUTDIR OUT:
Default : OUTDIR Mail:Outbound/
4.1.54. PATH <Directory>
Path to the directory, in which RadaReader establishes an area.
Remember, that all paths HAVE to be terminated with either '/' or
':'.
This one, too, must be inside the AREA-ENDAREA structure.
Example : PATH Mail:NetMail/
Default : PATH Mail:<TAG>/
4.1.55. POLLCMD <Command>
Command used for polling.
Example : POLLCMD BBS:bin/TrapDoor Call 2:230/204734354365
Default : N/A
4.1.56. QUALCHAR <Character>
States the character, RadaReader should put in front of
filenames in flow files. If you use TrapDoor, the most appropriate
character would be '-', as this deletes the packet after sending
them, but, anyway, consult your mailer manual.
Example : QUALCHAR -
2.0 Jesper Jensen, DK 2.0
Page 17 RadaReader V2.0, The Manual Page 17
Default : QUALCHAR \0
4.1.57. ROUTE <For> <To>
Instructs RadaReader on, how to route netmail. The wildcard '*'
is allowed. It's a good idea to have *:*/*.* defined as a fallback
address.
Example : ROUTE 39:*/*.* 39:141/117.0
Default : N/A
4.1.58. ROUTEONIMPORT
Tells RadaReader to route inbound netmails, not destined for
this system, at import.
Example : ROUTEONIMPORT
Default : Route netmails when exporting
4.1.59. SIG <Number> "Name"
Defines a SIG (Special Interest Group). This means, that you can
divide the areas into smaller subdivisions, like nets or your
preferences. The Number of the SIG is used with SIGNUMBER. Remember
not to have a SIG with the number zero. RadaReader uses this
internally to see, if any SIGs are available.
Example : SIG 1 "FidoNet conferences"
Default : N/A
4.1.60. SIGNUMBER <Number>
Tells RadaReader, which SIG a certain area belongs to. This one
is stated inside the AREA-ENDAREA structure.
Note: if you run SIGs, and do not state a SIGNUMBER for some
area, it is not included in any sigs ! :-) :-(
Example : SIGNUMBER 1
Default : See above
4.1.61. SPECIAL <Number>
If you have areas in which you may not write, you can use
SPECIAL to prevent you from doing so. SPECIAL 1 means read/write and
SPECIAL 2 means read only.
2.0 Jesper Jensen, DK 2.0
Page 18 RadaReader V2.0, The Manual Page 18
Example : SPECIAL 1
Default : N/A (moaning from RRInstall)
4.1.62. SYSOP <Name>
Your name.
Example : SYSOP Jesper Jensen
Default : N/A (Moaning from RRInstall)
4.1.63. TAG <Netname>
Defines the TAG (netname) for a certain area. It must be stated
for each area (yes, you are right : inside the AREA-ENDAREA
structure). Note, that the tag for your netmail area HAS to be
NETMAIL and for bad messages area : BAD_MSGS.
Example : TAG AMIGA
Default : N/A (moaning)
4.1.64. TRAPDOORV1.7+
If you run TrapDoor V1.7+, RadaReader will use the 4D filenames,
if you define this switch,
Example : TRAPDOORV1.7+
Default : 2D filenames
4.1.65. TYPE <Type-character>
Defines, what kind of an area is being defined. Valid characters
are : 'E' (=EchoMail), 'M' (=NetMail) and 'B' (=Bad Messages).
This one MUST be there, and must be inside the unevitable
AREA-ENDAREA structure.
Example : TYPE E
Default : ... <moaning> ...
4.1.66. WORKDIR <Directory>
A directory for temporary files, created by RadaReader.
Example : WORKDIR ram:
Default : WORKDIR t:
2.0 Jesper Jensen, DK 2.0
Page 19 RadaReader V2.0, The Manual Page 19
4.1.67. UNARC <Command>
Command for unarchiving mail bundles.
Example : UNARC AX X
Default : UNARC LhA X
4.1.66. UTCDIFF <Number>
The difference (in minutes) between localtime and Universal Time
Coordination.
Example : UTCDIFF -60
Default : UTCDIFF 0
2.0 Jesper Jensen, DK 2.0
Page 20 RadaReader V2.0, The Manual Page 20
5. Files created by RadaReader
When exporting your messages, RadaReader will create different
files in your outbound directory (defined with OUTDIR, see 4.1.51).
An explanation of the filenames of the these files is given in this
paragraph.
Furthermore, a little something is written about the files
created by RRInstall and at runtime.
5.1. Outbound Directory
5.1.1. Mail packets.
Mail packets usually have extension '.PKT'. These files contain
the messages in a packed format, lying right behind eachother. These
files are made, when RadaReader scans your areas. The filename itself
is actually a datestamp.
When making Crash and Hold mail these packets are named
otherwise :
Crash:
TrapDoorV1.7+ mode :
<Zone>.<Net>.<Node>.<Point>.(CUT|DUT).
<Zone>.<Net>.<Node>.<Point>.(CLO|DLO).
'Normal' Mode :
<netdiff><nodediff>.CUT.
<netdiff><nodediff>.CLO
netdiff is the difference between the originating and
destination net numbers, and nodediff is ditto for node
numbers.
Hold:
TrapDoorV1.7+ mode :
<Zone>.<Net>.<Node>.<Point>.HUT.
<Zone>.<Net>.<Node>.<Point>.HLO.
'Normal' mode :
<netdiff><nodediff>.HUT.
<netdiff><nodediff>.HLO.
BTW: Normal is embraced by 's, because the most common mailer
being used today is TrapDoor V1.8(3).
2.0 Jesper Jensen, DK 2.0
Page 21 RadaReader V2.0, The Manual Page 21
5.1.2. Compressed mail bundles.
Compressed mail bundles are files archive with the command given
with ARC in your configuration. These files include one or more mail
packets.
The compressed mail bundles will have an extension of '.DDN',
where DD is a day-of-the-week sign (MO, TU, WE etc.), and N is the
number of bundle that day, ranging from 0 to 9.
Compressed mail bundles are made, when RadaReader is through
with scanning your areas, and archives the mail packets.
The naming of compressed mail bundles is :
TrapDoor V1.7+ mode :
<Zone>.<Net>.<Node>.<Point>.DDN
'Normal' mode :
<netdiff><nodediff>.DDN.
5.1.3. Flow files.
In order to make the mailer aware of, which files should be sent
to whom, RadaReader makes socalled flow files
These files will have extension .FLO, .CLO, .HLO or .DLO. The
'FLO' extension is made for normal outbound mail, which is probably
the most common in a point system. The 'CLO' is made with crash mail,
the 'HLO' with hold mail, and the 'DLO' with direct mail (see the
chapter on crashing messages).
The flow files will contain the filenames of all the files to be
sent in a session with the node pointed out by the filename. That is,
if you fx. have a normal mail packet, where one of the messages has a
file attached to it, RadaReader will, on export, include this file in
the flow file with its' FULL path.
5.1.4. File Requests.
Most systems in the nodelist support some type of file
requesting (FReq'ing). This means, that you can call the system as a
normal mail session, and then obtain files (download) from the
systems file libraries. This is a very convenient way to transfer
files, as the BBS, which may also be at the system being called, is
not at all used. Furthermore, the EMSI/DirectZap protocols of
handshaking and file transfers are highly efficient.
2.0 Jesper Jensen, DK 2.0
Page 22 RadaReader V2.0, The Manual Page 22
When you request a file, RadaReader will create a file in your
outbound directory, which has the following format :
TrapDoor V1.7+ :
<Zone>.<Net>.<Node>.<Point>.REQ.
'Normal' mode :
<netdiff><nodediff>.REQ.
The .REQ files contain the filenames of the files you wish to
request. A common way to use file requests is by use of the socalled
magic names. These are pseudos for the actual file(s). Fx. most
BBS's/Nodes support these two MAGIC names : FILES and NEWFILES. FILES
will give you a file list of the BBS/Node system, and NEWFILES will
give you a list of the newest uploads (normally not more than 30 days
old). The most convenient way to use filerequests, is to first FREQ
FILES, then use it to freq more files from the file libraries. If you
want to know more about file requesting possibilities on a system,
feel free to ask the sysop.
Though file requesting at other systems than one's boss is
considered 'Annoying behaviour' in policy, most sysops don't mind.
But, make sure, ask the sysop before you request files at 'his
place'.
5.2. Configuration
As stated above, the configuration of RadaReader consists in
parsing an ASCII textfile with RRInstall, which then makes the
appropriate data files. These are :
5.2.1. RadaReader.Prefs
In which all the main information is stored. This is the
'backbone' of RadaReader. Paths to runtime directories are defined in
here, as well as editor, workdir, switches aso.
5.2.2. RadaReader.Areas
Defines the Areas. This file is open, while RadaReader is
running. Therefore, you cannot parse any configuration, while
RadaReader is running. Because the areas are gathered in this file,
there actually is no limit to the number of areas, but Import cannot
go higher than 512. Thus the limit, anyway !
This limit will probably be raised in later versions. See the
chapter on 'What the future might bring' to know why!
5.2.3. RadaReader.Links
2.0 Jesper Jensen, DK 2.0
Page 23 RadaReader V2.0, The Manual Page 23
Defines the Links, as stated in your configuration. The same as
for RadaReader.Areas applies here. No actual limit, but Import
doesn't go higher than 512 links, neither does Export BTW. If you
think, this is too little, then please say so ! :-).
5.2.4. RadaReader.Route
Contains the route statements. Wow : no limits here. It's for
real.
5.2.5. RadaReader.Sigs
Contains your Special Interest Groups (SIGs).
5.2.6. Mail:RadaReader.Data
Small datafile used at runtime. Just one bitmapped byte pr.
area. Thus, you can always check, how many areas, RRInstall
recognized by the size of this file.
5.3. Mail:RadaReader.Acc
If accounting is set, this file will be made during runtime. It
contains the information, which can be printed by WriteAcc.
2.0 Jesper Jensen, DK 2.0
Page 24 RadaReader V2.0, The Manual Page 24
6. AreaFix
AreaFix is a utility built in to RadaReader, that enables links
to (dis)connect areas without bothering the sysop of the system. This
is done by sending a message to 'AreaFix'. RadaReader will detect
this inbound message at import, and create a reply right away.
6.1. Invoking AreaFix
As explained the 'To' field of the message must be 'AreaFix'.
But, in order for AreaFix to accept the message, two things have to
be made. First of all, the sending system must be defined as a link
at the destination system. Second, the password for AreaFix must
match. This password is defined in 'LINKPASSWORD', see 4.1.38. If the
passwords do not match, RadaReader will not process the message.
Messages for AreaFix are terminated by '---'.
6.2. Options
With AreaFix it is not only possible to connect/disconnect
areas. A link can also obtain additional information. Information,
such as which areas the link is connected to, and which choices, the
link has, regarding areas. These options are preceeded with a '-'.
Here is a list of the options RadaReader is aware of :
-L : Create a list of available areas. RadaReader will _only_ create
a list, that the link, with that address, can connect itself to. So,
if fx. a link is a point/downlink in more nets, the conferences of
these nets are not included. RadaReader uses the tagname along with
the DESCRIPTION of the echo, see 4.1.15.
-Q : Creates a list of areas, to which the Link is connected. The
same rules as for '-L' applies here.
-A : Creates a list of systems connected to the system. Will display
the address, archiving method, the mail capabilities etc.
6.2. (Dis)Connecting areas
When a downlink wants to add an area to his/her exportlist, it
is done by writing the tagname of that area. To disconnect the area,
the tagname must be preceeded by a dash '-'.
6.3. Using AreaFix
When a link has done an 'AreaFix', the datafiles (RadaReader.*)
are updated to meet the new conditions. But your configuration is not
updated. Therefore, RRUnInstall was made. This tool enables you to
do a 'write active profile', meaning, that RRUnInstall will print out
the current configuration. Yes, the configuration is printed out,
which means, that in order to create a file with the current
2.0 Jesper Jensen, DK 2.0
Page 25 RadaReader V2.0, The Manual Page 25
configuration, you'll have to redirect the output.
Furthermore, AreaFix keeps a log, in which any activation of
AreaFix is logged. This log is made by specifying the AREAFIXLOG
keyword (4.1.7).
2.0 Jesper Jensen, DK 2.0
Page 26 RadaReader V2.0, The Manual Page 26
7. RadaReader's Editor
7.1. Menus
RadaReader uses both menus and the keyboard for your input. That
is, you can access every command in RadaReader via either a menu or a
press on the keyboard.
The following is an explanation of the commands in RadaReader.
7.1.1. About.
This will give you a little information requester about
RadaReader with information on the author and how to register
RadaReader.
Menu: 'Radagast'.
Key Equivalent: 'a'.
7.1.2. Archive message.
This command is used, when you want to store a message, so that
a deletion of the message wont affect you. The message is stored in a
file in the directory stated with the ARCPATH keyword. The format of
the file is : Archived_Msgs_Of_XXX, where 'XXX' is a three character
month qualifier.
Menu: 'Special'.
Key Equivalent: 'm'.
7.1.3. Edit Message.
This allows you to edit a message, previously written (by you or
any other. No point in editting other's messages anyway). It uses the
same procedures as 'Write Message' and 'Reply',
Menu: 'Messages'.
Key Equivalent: 'e'.
7.1.4. Execute External.
Will pop up a requester, prompting you for the command it should
execute. This is just like executing the command from the shell.
Menu: 'Special'.
Key Equivalent: 'x'.
7.1.5. Export.
2.0 Jesper Jensen, DK 2.0
Page 27 RadaReader V2.0, The Manual Page 27
This is the same as running RadaReader with argument 'X'. It
scans all of your areas, and exports any messages, needing it.
Menu: 'Special'.
Key Equivalent: 'f'.
7.1.6. File Attach.
With this command file attaching is possible. RadaReader will
create a FLO file for the address, you state, and insert any files,
you wish to attach in it.
Menu: 'Options'.
Key Equivalent: 'A'.
7.1.7. File Request.
Will create a #?.REQ file in your outbound directory, if it is
not already there, and append the filename, which you enter via yet
another requester.
Menu: 'Options'.
Key Equivalent: 'R'.
7.1.8. Forward Message.
Will forward the CURRENT message into another area given via a
requester.
Menu: 'Options'.
Key Equivalent: 'o'.
7.1.9. HWM all area.
Sets the LastRead pointer to the number of messages for all
areas. Useful for seeing from where RadaReader imports next time.
Menu: 'Special'.
Key Equivalent: 'G'.
7.1.10. Import.
The same as running RadaReader with argument 'I'. Will scan the
inbound directory, and import any bundles/packets matching the
filepatterns stated in chapter 5. (that is, the <netdiff><nodediff>
way!).
2.0 Jesper Jensen, DK 2.0
Page 28 RadaReader V2.0, The Manual Page 28
Menu: 'Options'.
Key Equivalent: 'F'.
7.1.11. Jump to Message.
Jumps to the message number entered.
Menu: 'Special'.
Key Equivalent: 'j'.
7.1.12. Maintenance All Areas.
Maintenance means deleting of messages, if there is too many of
them, according to your configuration. The MAXMSGS decide, if
maintenance should delete any messages, and will do so, if it finds
too many in the area.
Menu: 'Options'.
Key Equivalent: 'O'.
7.1.13. Maintenance Current Area.
Will do a maintenance check on the current area only.
Menu: 'Options'.
Key Equivalent: 'L'.
7.1.14. Matrix Reply.
This command replies the current message, but puts the reply in
the netmail area.
Menu: 'Messages'.
Key Equivalent: 'g'.
7.1.15. Memory Info.
Gives you some information on the memory left in your system.
Menu: 'Radagast'.
Key Equivalent: 'M'.
7.1.16. Message Browser.
Invokes RadaReader's message browser.
2.0 Jesper Jensen, DK 2.0
Page 29 RadaReader V2.0, The Manual Page 29
Menu: 'Special'.
Key Equivalent: 'b'.
7.1.17. New Area.
Will pop up a requester, in which you can click your way to a
new area.
Menu: 'Special'.
Key Equivalent: 'N'.
7.1.18. New Mail.
Jumps to the next area with new mail. A bit ackward, when using
SIGs :-).
Menu: 'Messages'.
Key Equivalent: 'i'.
7.1.19. New Mail Area.
Jumps to the next area with new mail for the sysop.
Menu: 'Messages'.
Key Equivalent: 'I'.
7.1.20. New SIG.
This is the command to use, when you wish to change the current
SIG.
Menu: 'Special'.
Key Equivalent: 'n'.
7.1.21. Next Subjectassociated.
Will cause RadaReader to search for the next message in the
current area, which has the same subject field as the current
message.
Menu: 'Messages'.
Key Equivalent: 'z'.
7.1.22. Next To Sysop.
2.0 Jesper Jensen, DK 2.0
Page 30 RadaReader V2.0, The Manual Page 30
Causes RadaReader to search for the next message for the sysop
in the current area. If it could not be found, RadaReader will do a
visual blink.
Menu: 'Messages'.
Key Equivalent: 's'.
7.1.23. Poll Normal.
If this key/menu is chosen, RadaReader will use the POLLCMD in
your configuration to do a poll to your boss.
Menu: 'Options'.
Key Equivalent: 'p'.
7.1.24. Poll with Import.
Same as the above, exept RadaReader will automatically switch to
the import routines, when the mailer is through.
Menu: 'Options'.
Key Equivalent: 'l'.
7.1.25. Print Message.
Copies the current message to the printer. Does the same as
'Archive Message', exept that it is for the printer, not to a file.
Menu: 'Special'.
Key Equivalent: 'P'.
7.1.26. Quit.
Quits RadaReader.
Menu: 'Radagast'.
Key Equivalent: 'Amiga/Q'.
7.1.27. Reply.
Causes RadaReader to launch the editor, given with EDITOR in
your configuration. RadaReader first produces a file, which contain
the quoting from the current message.
Reply uses the HEADER/DEFHEADER keywords. That is, if the
current AREA has a HEADER, RadaReader will use this. If not,
RadaReader will use DEFHEADER. If this is not there either, no header
2.0 Jesper Jensen, DK 2.0
Page 31 RadaReader V2.0, The Manual Page 31
will be produced.
Menu: 'Messages'.
Key Equivalent: 'r'.
7.1.28. Search For Reply.
Causes RadaReader to search for a reply. That is, test the
following message for : '<SUBJECT>' or 'Re:<SUBJECT>'.
Menu: 'Messages'.
Key Equivalent: 'u'.
7.1.29. Set Address.
In this item (with subitems) you can set the address used for
netmail. It works globally, that is : you can chage it in all
areas.
Menu: 'Special'.
Key Equivalent: None.
7.1.30. Set Colors.
Pops up a palette requester, in which you can determine the
values to put in your configuration.
Menu: 'Messages'.
Key Equivalent: 'S'.
7.1.31. Toggle Flags.
Every message has an attributes field to it. This is a 16 bit
field, in which each bit (exept one), has a special meaning. By using
'Toggle Flags', you can alter the state of these bits.
Some of these bits are used, when you instruct RadaReader to
export. Some of them only have meaning in netmail areas. The same
information can be stated by ways of LINK definitions.
BTW: the 'Sent' flag toggling is only useful with netmail. In
echomail, the sent-flag is not the only thing checked before
exporting. In netmail, you also have to edit the message, or else
RadaReader doesn't know, that the area has unexported mail !
Menu: 'Options'.
Key Equivalent: 't'.
2.0 Jesper Jensen, DK 2.0
Page 32 RadaReader V2.0, The Manual Page 32
7.1.32. Write Message.
This is the command, you should use, when writing a new
message.
Menu: 'Messages'.
Key Equivalent: 'w'.
7.2. The Screen.
The screen in RadaReader is divided into two windows, the upper
has information, obtained in the message's header, and the window
below shows the message text (body).
The top window has 5 lines : FROM, TO, SUBJECT, CREATION DATE,
IMPORT DATE. If you're in a netmail area, FROM and TO lines will also
have the addresses of the destination and origination. The CREATION
TIME line also has the FLAGS entry. This is a string of x characters,
which specifies, if a certain flag is set. Here is an explanation of,
what the flags mean :
P : Private.
C : Crash.
R : Received.
S : Sent.
A : File Attached.
I : In transit (of no use in a point system).
K : Killsent.
L : Local.
H : Hold for pickup.
R : File Request.
7.3. Cursor keys
You use the cursor keys to move back and forth in the messages,
and to scroll the text up and down.
The cursor keys are used like this :
Left : Next message
Right : Previous message
Up : One line up
Down : One line down
ALT-Left : Next area (not in use, if you use SIGs)
ALT-Right : Previous area (not in use, if you use SIGs)
ALT-Up : 10 lines up
ALT-Down : 10 lines down
CTRL-Left : Next SIG (only if using SIGs)
CTRL-Right : Previous SIG (only if using SIGs)
2.0 Jesper Jensen, DK 2.0
Page 33 RadaReader V2.0, The Manual Page 33
7.4. The Action Window
The action window pops up at Import, Export and Maintenance, and
ONLY if you have not set the 'NOACTIONWINDOW' switch in your
configuration. It gives you some information on, what RadaReader is
doing at a given time.
When RadaReader is through with it's action, you must click on
the close-window gadget.
7.4. The Message Browser
The message browser in RadaReader has been subject to a major
revision since version 1.2. Now it has a neat 2.0 look, and is a bit
more efficient and usable.
With the message browser, you can mark messages. Marking message
and then quitting the browser (the 'OK' gadget) will make RadaReader
show you the message you marked. Just press the right cursor key for
the next marked message. The message will be shown in the same
manner, as you marked them. That is, if you fx. marked #3, then #45
and then #27, RadaReader will show the messages in the same order.
The message browser is your only mean of deleting messages. Just
mark the message, you'd like to delete, and then press the 'Delete
Marked Messages' gadget.
Furthermore, you can select more messages to be printed or
archived with the browser. Just mark them out, and press the
appropriate gadget.
2.0 Jesper Jensen, DK 2.0
Page 34 RadaReader V2.0, The Manual Page 34
8. RadaReader in action
This chapter is devoted to explaining some of the capabilities
RadaReader has.
8.1. Routing
Routing is a term used in conjunction with netmail. It means
'sending netmail along to it's destination'. Routing was invented, so
that a sender of a netmail didn't have to call directly to the
receiver in order to send a netmail. Instead the sender sends the
netmail to the uplink, which then routes it on to another uplink,
which then routes it on ... aso.
RadaReader can be instructed to route the netmails at import.
This is useful for privacy. This way the sysop will never know, that
a netmail passed his/her system (exept if he/she look in the log, of
course).
RadaReader will always include the right address in the via
kludge. The UTCDIFF is also used for this via kludge, as this must
state when and where a netmail was processed (routed).
8.2. Accounting
Accounting was introduced due to a beta-testers need for
accounting the netmail flow through his system. Setting accounting
will count the bytes exported and imported for netmail and echomail.
Note, that the 'NetMail In' value of the accouting is flow-through
netmail only. That is, netmail sent to the sysop of the system will
NOT reflect in the accounting.
8.3. MultiNet support
RadaReader handles multinet and multiboss environments. This is
accomplished by the AKA and ADDRESS keywords, which defines other
addresses, than the NODE address, which would usually be the fidonet
address.
8.4. Logfiles
RadaReader keeps two logfiles: one for RadaReader, and one for
AreaFix. These are both configurable, regarding paths. A typical
entry in a log would look like :
Q DD-MMM-YY HH:MM:SS ACTION
where Q is a qualifier :
| : Plain information
= : RadaReader/AreaFix started doing something
- : RadaReader/AreaFix ended something
2.0 Jesper Jensen, DK 2.0
Page 35 RadaReader V2.0, The Manual Page 35
+ : Number of message might not be the same
! : SysOp relevant information
? : RadaReader/AreaFix encountered an error
8.5. Duplicate Messages
If the 'NOCHECKDUPES' switch is not set, RadaReader will create
a dupe table for each area. Currently these tables can't go over 200
messages :-(. The way RadaReader checks for dupes is by calculating
CRC-32 values for some information in the headers.
2.0 Jesper Jensen, DK 2.0
Page 36 RadaReader V2.0, The Manual Page 36
9. Running dormantly (TellRR)
RadaReader has the option of running dormantly. That is : if
RadaReader is run with argument 'DORMANT', it will not open it's
screen, but wait for a port to message'd. This is particularly
useful, when running a node, and ie. using the AFTERSESSION keyword
of TrapDoor.
In order to communicate with RadaReader, when running dormantly,
you must use TellRR. This program sends a message to RadaReader's
message port, and waits for it to be replied. Currently TellRR
recognizes these commands :
EDITOR: Brings up the editor. When quitting, RadaReader will ask, if
you want to go back to running dormant.
EXPORT: Causes RadaReader to scan areas.
IMPORT: Causes RadaReader to toss incoming mail.
MAINT: Causes RadaReader to do a maintenance (on all areas).
POLL: Makes RadaReader poll, using POLLCMD.
Not tested yet.
SETPRI: To set RadaReader's priority. The VALUE argument must hold
the new priority.
QUIT: Removes RadaReader.
2.0 Jesper Jensen, DK 2.0
Page 37 RadaReader V2.0, The Manual Page 37
10. RR(Un)Install
RRInstall and RRUnInstall are used in context with the
configuration. RRInstall parses your configuration file, and creates
the neccassary data files. Neccassary in order to run RadaReader.
RRUnInstall does the reverse. It PRINTS OUT the configuration, as
is. It is using normal printf() to print out, thus you must use
redirection, if you'd wan't RadaReader to write to a file.
RRUnInstall is particularly useful as 'AREAFIXCOMMAND', as your
text configuration immediately will reflect any changes.
See chapter 4 on how to create the configuration file.
2.0 Jesper Jensen, DK 2.0
Page 38 RadaReader V2.0, The Manual Page 38
11. Limitations
Number of Areas: 512
Number of Msgs/Area: unlimited (2^32)
Number of Msgs (Browser): unlimited (2^32)
Maximum Size/Msg: anything. Adjustable.
Number of Links: 512
Number of Links connected to area: 512
Number of ROUTE statements: unlimited
2.0 Jesper Jensen, DK 2.0
Page 39 RadaReader V2.0, The Manual Page 39
12. Politics
A little chapter on RadaReader's distribution and alike.
12.1. Shareware
RadaReader is made available to you under the concept of
shareware. This implies, that you should evaluate RadaReader for a
month, and then, if you decide to keep on using it, register it.
12.2. Distribution
RadaReader is distributed via SAN, and future versions can also
be obtained from there.
You may copy the program as much as you'd like, as long as no
costs, other than that of disks or alike, are charged.
12.3. You may
Use this software to use by a single person and on a single
computer.
Make verbatim copies of the original distribution archive, as
long as no files are omitted/added/changed.
Distribute the archive, if NO fee is charged.
Upload it to BBS's, please do if you like it :-).
12.4. You may not
Alter the software or any files accompaning the archive.
Re-code the software, including, but not limited to,
deassembling or decompilation
Grant other licenses of the software
Rent RadaReader or following files to others.
12.5. Disclaimer
THE AUTHOR (JESPER JENSEN) CAN UNDER NO CIRCUMSTANCES BE HELD
RESPONSIBLE FOR ANY FAILURES INCLUDING, BUT NOT LIMITED TO, HARDWARE
FAILURES OR LOSS OF DATA. YOU ARE USING THIS SOFTWARE ENTIRELY AT
YOUR OWN RISK.
NEITHER CAN THE AUTHOR BE HELD RESPONSIBLE FOR ANY FAILURES,
INVOKED BY MISUSE OF THE PROGRAM, OR PARTS OF THE PROGRAM, NOT
COVERED BY THIS MANUAL.
2.0 Jesper Jensen, DK 2.0
Page 40 RadaReader V2.0, The Manual Page 40
13. Miscellaneous
This chapter gives you some information about various stuff.
13.1. Support Centers
The RadaReader Project has some support centers attached to it.
At these centers, you can always pick up the newest version of
RadaReader, and maybe some utilities, that will come along.
You can register RadaReader at these sites. Please use the
register form in this archive. Or else your registration will go
unattended.
The support centers are :
Author
Danish/European RadaReader Support Site
Iluvatar BBS.
Jesper Jensen.
2:230/417.0, FidoNet.
39:141/117.0, AmyNet.
92:910/106.0, BadNet.
Radagast@iluvatar.bbs.bad.se, InterNet.
Modem: v32b, v42b.
2200-0630, Phone : +45-42-730817.
Europe
European RadaReader Support Site
Syntax Amiga BBS.
Franz Eckert.
2:230/612.0, FidoNet.
39:140/104.0, AmyNet.
92:910/0.0, BadNet.
Franz_Eckert@syntax.bbs.bad.se, InterNet.
Modem: v32b, v42b, HST.
24h, Phone : +45-66-146211.
Australia
Australian RadaReader Support Site
The Ice Cave.
Dave Freeman.
3:640/535.0, FidoNet.
41:400/533.0, AmyNet.
Modem: v32.
24h, Phone : +61-70-31-4186.
Any questions concerning the installation of RadaReader should
be directed to one of these sites, or preferably to Peter Simonsen,
2.0 Jesper Jensen, DK 2.0
Page 41 RadaReader V2.0, The Manual Page 41
2:230/419.2, 39:141/116.2.
13.2. What the future might bring
This is a little list of planned future enhancements :
* Raid, Hatch and Tick built into RadaReader.
* Expansion of the dormant mode facilities.
* Guided User Interface installation program.
* Random origins.
* your suggestions ? :-)
13.3. Acknowledgements
First of all, a giant thank you to the betatesters :
Peter Simonsen, Franz Eckert, Dave Freeman, Klaus Seistrup,
Cristopher A. Lee, Carsten Lausen and Hans Majlinder.
Thank you all!
And thanks to BadNet-Denmark for the patience.
The following names are either trademarks or the efforts of
the person and/or company listed:
* Amiga, AmigaDOS, CLI and WorkBench by Commodore-Amiga, Inc.
* AreaFix (for MS-DOS) by Greg Dawson
* CarbonCopy and AX by Klaus Seistrup
* Chameleon Editor by Jurgen Hermann
* Fido and FidoNet are trademarks of Tom Jennings, Fido Software
* Foozle by Peer Hasselmeyer
* Four dimensional addressing and FSC-0039 by Mark A. Howard
* FServ by Mark Cassidy
* FTS-0001 by Randy Bush
* Global Conference Control and GCChost by Davide Massarenti
* LhA by Stefan Boberg
* MSGID/REPLY kludges and FSC-0041/FTS-9 by Jim Nutt
* NicePoll and Gertrud by Adam Sjoegren
* PID kludge and FSC-0046 by Joaquim Homrighausen
* PointManager by Mario Pacchiarotti
* ReqTools.library and ToolsDaemon by Nice Francois
* TransAmiga BBS by Timothy Aston
* TrapDoor by Maximilian Hantsch and Martin Laubach
* TrapList and traplist.library by Martin Laubach and Maximilian Hantsch
* Welmat by Michael C. Richardson and Russel McOrmond
Thank you :
2.0 Jesper Jensen, DK 2.0
Page 42 RadaReader V2.0, The Manual Page 42
* Thomas Agatz for being my uplink :-)
* Bjarke Oerbeck for being my sysop!
* Mark Cassidy for suggestions
* Klaus Seistrup for suggestions and other
* Sune Trudslev for patience
* Klaus Ellegaard for patience
* Kurt Noe for feedback
* Jimmy Ljungberg for feedback
* Eric Krieger for feedback
* Roger Nordin for help on FSC-39
* Peter Simonsen for sticking to RadaReader through the hard times :-)
13.4. Echo and File Requesting
An echo with tagname RADAREADER is available from the support
sites. So just contact one of them to get connected, or,
alternatively, if you are a point, ask your boss to get it.
Furthermore, RadaReader is available for file requesting at the
support sites under these magic names :
RADAREADER, the full archive
RREXE, only the RadaReader executable
RRINSTALL, RRinstall only
RRUNINSTALL, RRUnInstall only
TELLRR, TellRR only
RRMANUAL, only the manual
WRITEACC, WriteAcc only
2.0 Jesper Jensen, DK 2.0
Page 43 RadaReader V2.0, The Manual Page 43
14. Known bugs
When RadaReader is running dormant, and the editor is 'up',
RadaReader will hang after it has been invoked by TellRR, fx. if you
try to do a 'New Area'.
This is not a known bug, but a 'might-be' bug. If RadaReader
encounters extremely bad packets, I sincerely don't know, if it will
just skip the bad messages, and import the rest. It looks that way
right now, but one never can be sure ! :-(
A beta tester experienced strange problems, when forwarding
several very large messages. After forwarding 7-8 times, it's
pointers in that area was wrong.
Interlace is not yet working properly.
2.0 Jesper Jensen, DK 2.0
Page 44 RadaReader V2.0, The Manual Page 44
15. IMPORTANT!
Should you experience strange problems in your use of
RadaReader, then CHECK YOUR CONFIGURATION. A file, describing the
structures is in this archive (RadaReader.Tech.Ref).
If that doesn't work, then check it again :).
2.0 Jesper Jensen, DK 2.0
Page 45 RadaReader V2.0, The Manual Page 45
1. Introduction................................................. 2
2. Getting started.............................................. 3
2.1. Requirements............................................ 3
2.2. Keyfile................................................. 3
3. The mail processor's job..................................... 4
3.1. Mail Processing......................................... 4
3.2. Node vs. Point.......................................... 4
3.3. The Mail Editor (Reader)................................ 4
4. Configuring RadaReader....................................... 5
4.1. Keywords................................................ 5
4.1.1. ADDRESS <Number>................................... 5
4.1.2. AKA <FQFA> <Fakenet> [Domain]...................... 5
4.1.3. ARC <Command>...................................... 5
4.1.4. ARCPATH <Directory>................................ 5
4.1.5. AREA............................................... 6
4.1.6. AREAFIXCOMMAND "Command"........................... 6
4.1.7. AREAFIXLOG <Path>.................................. 6
4.1.8. BADDIR <Directory>................................. 6
4.1.9. BAKDIR <Directory>................................. 6
4.1.10. COLOR <Where> <Which> <R,G,B>..................... 7
4.1.11. DEFHEADER "String"................................ 7
4.1.12. DEFLOGO "String".................................. 7
4.1.13. DEFMAXMSGS <Number>............................... 8
4.1.14. DEFORIGIN "String"................................ 8
4.1.15. DESCRIPTION "String".............................. 8
4.1.16. EDITOR <Command>.................................. 8
4.1.17. ENDAREA........................................... 8
4.1.18. ENDLINK........................................... 9
4.1.19. EXPORTCOMMAND "Command"........................... 9
4.1.20. EXPORTTO <FQFA>................................... 9
4.1.21. EXTERNAL <MenuText> <MenuCommand>................. 9
4.1.22. FLAGS <Binary Number>............................. 10
4.1.23. FONT <Font> [SIZE <Number>]....................... 10
4.1.24. FORCEINTL......................................... 10
4.1.25. FWDTEMPLATE "String".............................. 10
4.1.26. HEADER "String"................................... 11
4.1.27. HIDEKLUDGE........................................ 11
4.1.28. IMPORTONLYKNOWN................................... 11
4.1.29. INDIR <Directory>................................. 11
4.1.30. INTERLACE......................................... 12
4.1.31. KILLDUPES......................................... 12
4.1.32. LINK.............................................. 12
4.1.33. LINKACCOUNTING.................................... 12
4.1.34. LINKADDRESS <FQFA>................................ 13
4.1.35. LINKARC <Command>................................. 13
4.1.36. LINKFLAGS <Binary Number>......................... 13
4.1.37. LINKFLOW <Type>................................... 13
4.1.38. LINKMAIL2D........................................ 13
4.1.39. LINKPASSWORD <Password>........................... 13
4.1.40. LINKRADAREADER.................................... 14
4.1.41. LOGFILE <Path>.................................... 14
4.1.42. LOGO "String"..................................... 14
2.0 Jesper Jensen, DK 2.0
Page 46 RadaReader V2.0, The Manual Page 46
4.1.43. MAIL4D............................................ 14
4.1.44. MAXMSGS <Number>.................................. 14
4.1.45. MSGBUFFER <Number>................................ 14
4.1.46. NAME "String"..................................... 15
4.1.47. NOACTIONWINDOW.................................... 15
4.1.48. NOCHECKDUPES...................................... 15
4.1.49. NODE <FQFA> <Fakenet> [Domain].................... 15
4.1.50. NODELIST <Directory>.............................. 15
4.1.51. NOSYSTEMLISTS..................................... 15
4.1.52. ORIGIN "String"................................... 16
4.1.53. OUTDIR <Directory>................................ 16
4.1.54. PATH <Directory>.................................. 16
4.1.55. POLLCMD <Command>................................. 16
4.1.56. QUALCHAR <Character>.............................. 16
4.1.57. ROUTE <For> <To>.................................. 17
4.1.58. ROUTEONIMPORT..................................... 17
4.1.59. SIG <Number> "Name"............................... 17
4.1.60. SIGNUMBER <Number>................................ 17
4.1.61. SPECIAL <Number>.................................. 17
4.1.62. SYSOP <Name>...................................... 18
4.1.63. TAG <Netname>..................................... 18
4.1.64. TRAPDOORV1.7+..................................... 18
4.1.65. TYPE <Type-character>............................. 18
4.1.66. WORKDIR <Directory>............................... 18
4.1.67. UNARC <Command>................................... 18
4.1.68. UTCDIFF <Number>.................................. 19
5. Files created by RadaReader.................................. 20
5.1. Outbound directory...................................... 20
5.1.1. Mail packets....................................... 20
5.1.2. Compressed mail bundles............................ 21
5.1.3. Flow files......................................... 21
5.1.4. File Requests...................................... 21
5.2. Configuration........................................... 22
5.2.1. RadaReader.Prefs................................... 22
5.2.2. RadaReader.Areas................................... 22
5.2.3. RadaReader.Links................................... 22
5.2.4. RadaReader.Route................................... 23
5.2.5. RadaReader.Sigs.................................... 23
5.2.4. Mail:RadaReader.Data............................... 23
5.3. Mail:RadaReader.Acc..................................... 23
6. AreaFix...................................................... 24
6.1. Invoking AreaFix........................................ 24
6.2. Options................................................. 24
6.2. (Dis)Connecting areas................................... 24
6.3. Using AreaFix........................................... 24
7. RadaReader's Editor.......................................... 26
7.1. Menus................................................... 26
7.1.1. About.............................................. 26
7.1.2. Archive Message.................................... 26
7.1.3. Edit Message....................................... 26
7.1.4. Execute External................................... 26
7.1.5. Export............................................. 26
2.0 Jesper Jensen, DK 2.0
Page 47 RadaReader V2.0, The Manual Page 47
7.1.6. File Attach........................................ 27
7.1.7. File Request....................................... 27
7.1.8. Forward Message.................................... 27
7.1.9. HWM all areas...................................... 27
7.1.10. Import............................................ 27
7.1.11. Jump to Message................................... 28
7.1.12. Maintenance All Areas............................. 28
7.1.13. Maintenance Current Areas......................... 28
7.1.14. Matrix Reply...................................... 28
7.1.15. Memory Info....................................... 28
7.1.16. Message Browser................................... 28
7.1.17. New Area.......................................... 29
7.1.18. New Mail.......................................... 29
7.1.19. New Mail Area..................................... 29
7.1.20. New SIG........................................... 29
7.1.21. Next Subjectassociated............................ 29
7.1.22. Next To Sysop..................................... 29
7.1.23. Poll Normal....................................... 30
7.1.24. Poll with Import.................................. 30
7.1.25. Print Message..................................... 30
7.1.26. Quit.............................................. 30
7.1.27. Reply............................................. 30
7.1.28. Search For Reply.................................. 31
7.1.29. Set Address....................................... 31
7.1.30. Set Colors........................................ 31
7.1.31. Toggle Flags...................................... 31
7.1.32. Write Message..................................... 32
7.2. The Screen.............................................. 32
7.3. Cursor keys............................................. 32
7.4. The Action Window....................................... 33
7.5. The Message Browser..................................... 33
8. RadaReader in action......................................... 34
8.1. Routing................................................. 34
8.2. Accounting.............................................. 34
8.3. MultiNet support........................................ 34
8.4. Logfiles................................................ 34
8.5. Duplicate messages...................................... 35
9. Running dormantly (TellRR)................................... 36
10. RR(Un)Install............................................... 37
11. Limitations................................................. 38
12. Politics.................................................... 39
12.1. Shareware.............................................. 39
12.2. Distribution........................................... 39
12.3. You may................................................ 39
12.4. You may not............................................ 39
12.5. Disclaimer............................................. 39
13. Miscellaneous............................................... 40
13.1. Support Centers........................................ 40
13.2. What the future might bring............................ 41
13.3. Acknowledgements....................................... 41
13.4. Echo and File Requesting............................... 42
14. Known bugs.................................................. 43
2.0 Jesper Jensen, DK 2.0
Page 48 RadaReader V2.0, The Manual Page 48
15. IMPORTANT!.................................................. 44
2.0 Jesper Jensen, DK 2.0
