home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
hpt2_028.zip
/
FidoConf.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1999-06-16
|
62KB
|
1,799 lines
ΓòÉΓòÉΓòÉ 1. Title page ΓòÉΓòÉΓòÉ
FidoConfig Manual
a way to make your unix fido-capable
Matthias Tichy
Copyright (C) 1998-99 Matthias Tichy
ΓòÉΓòÉΓòÉ 2. Top node: "fidoconfig" ΓòÉΓòÉΓòÉ
This document describes the use of fidoconfig to make fido work on your unix
workstation.
This document applies to version 0.8 of fidoconfig.
design goals what we want to achieve
config file how does it look like
tparser testing your config
converting Converting fidoconfig to golded and
msged
contact contacting the author
ΓòÉΓòÉΓòÉ 3. Design goals ΓòÉΓòÉΓòÉ
The design goal of fidoconfig was to provide one config-file for several
different fido software packages like editor, tosser etc. An additional aim was
to have one library (fidoconfig) which can be used by all programs. The
advantage is you only have to edit one config-file, so changing your system is
much easier than with common software packages. Also bugs can only creep in one
library and not in thousands over thousands libraries. The config definition
can be used in all operating systems. Also the library should be quite
portable.
ΓòÉΓòÉΓòÉ 4. Config file ΓòÉΓòÉΓòÉ
This chapter describes how a fidoconfig config-file is written, which keywords
exist and where to put the file.
Location Where to put the config file
Syntax Syntax
Keywords Keyword reference
Example Here is a sample configfile which
works for me
ΓòÉΓòÉΓòÉ 4.1. Configfile location ΓòÉΓòÉΓòÉ
The fidoconfig library searches the config file on different locations:
linux:
/etc/fido/config
freebsd:
/usr/local/fido/config
os2/win32/dos:
c:\fido\config
Additionally you can set an enviroment variable called FIDOCONFIG which points
to the file:
set FIDOCONFIG=e:\bbs\fidoconfig\config
FIDOCONFIG=~/fidoconfig/config
export FIDOCONFIG
The config file(s) must be readable. If you plan to use the autoareacreate
feature the config file must be writeable.
ΓòÉΓòÉΓòÉ 4.2. Syntax ΓòÉΓòÉΓòÉ
The configfile must be readable to fidoconfig. If you plan to use the
autoareacreate feature the writing process must have write-access to the
configfile.
All symbols are *not* case-sensitiv.
{<whiteSpace>} at the start of the line will be ignored.
All keywords are evaluated as occurring, the first matching keyword found is
valid. If there are more then one keywords of the same type allowed, the first
line matching the situation is valid. If no match is found, a default-value
will be used.
"\" is used as escape-sequence. "\" has to be written as "\\".
non-printable characters can be expressed as \<hexValue>
"#" at the start of a line or <whiteSpace>#<whiteSpace> within the line starts
a comment. The comment ends with the line.
If the first word in a line is an undefined keyword, the line will be ignored.
Each keyword has to start a new line.
Currently not supported:
"\" at end of line means that "\" and the following new-line- character(s) will
be ignored. (concatenating lines)
ΓòÉΓòÉΓòÉ 4.3. Keywords ΓòÉΓòÉΓòÉ
All statements are case-*insensitive*. A line which starts with a # is a
comment and will be ignored.
version version of fidoconfig
name your Systems Name
location your location
sysop your Name
include include other files
address your system address
Path and file definition:
outbound outbound path
tempoutbound temporary outbound path
inbound inbound path
protinbound protected inbound
listinbound listed inbound
localinbound local inbound
tempinbound temporary inbound path
msgbasedir base directory of areas
intab file for recoding incoming msgs
outtab file for recoding outgoing msgs
importlog file which contains the names of the
areas tossed in
echotosslog file which contains the names of the
areas messaged entered
linkWithImportLog determines if only the areas which are
in importLog should be linked
public path for requestable files
logfiledir path for log files
dupehistorydir path for dupe files
nodelistdir path for nodelists
magic path for magic-file requests
lockfile file which lock hpt session
link definition:
link adding a link to your config
aka links adress
ouraka our aka for link
password links session and default password
pktpwd pktpassword for this link
ticpwd ticcer password for this link
areafixpwd areafix password for this link
filefixpwd filefix password for this link
bbspwd bbs password for this link (online
user)
handle nickname or handle for link
tossgrp tosser groups which link belongs to
ticgrp ticcer groups which link belongs to
bbsgrp online groups which link belongs to
accessgrp groups for echomail access
optgrp groups for export/import/mandatory
export rules for echomail export
import rules for echomail import
mandatory rules for echoarea access
level definition of link access level
autoareacreate right to auto create areas on your
system
autoareacreatedefaults set defaults to autocreated echoareas
packer default packer for link
echomailflavour flavour for outgoing echomail
autoCreateFile file where autoCreated Areas by this
links are going
forwardRequests allow forward requests to this link
forwardRequestFile file for forwardRequest,
AvialableAreas & descriptions
forwardPkts shall we forward inbound packets for
this node?
pause don't export mail for this link
area definition:
netmailarea definition of netmailarea
badarea definition of badarea
dupearea definition of dupearea
echoarea definition of echoarea
localarea definition of localarea
rights
PublicGroup this is a list of groups for public
echo acess
GroupAutoAreaCreate right to autoareaCreate for a group
AutoCreateDefaults default area options for autocreated
areas
GroupDefaults default area options for
GroupAutoAreaCreated areas
packer
pack definition for packer
unpack definition for unpacker
routing
route routing of netmails
routeFile routing of netmails with file attached
routeMail routing of netmails without file
attached
carbon copy
carbonTo make carbonCopy using to-field of msg
carbonFrom make carbonCopy using from-field of
msg
carbonKludge make carbonCopy using kludge lines of
msg
carbonArea specify the area where the carbon
copies go into
areafix
areafixFromPkt process areafix requests on the fly
areafixKillReports set kill/sent flag to areafix reports
ReportTo set area or netmail for areafix
reports
misc:
logEchoToScreen set output to screen log information
Remap remap mail to other address
SeparateBundles move echomail for each link to his own
directory
ΓòÉΓòÉΓòÉ 4.3.1. version ΓòÉΓòÉΓòÉ
Syntax:
version <integer>.<integer>
Example:
version 0.13
Here you specify to which version of fidoconfig your config belong. Currently
this statement does nothing.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.2. name ΓòÉΓòÉΓòÉ
Syntax:
name <text>
Example:
name Leetebrok BBS
Here you specify your Systems name.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.3. location ΓòÉΓòÉΓòÉ
Syntax:
location <text>
Example:
location Dusseldorf
You specify your Location here.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.4. sysop ΓòÉΓòÉΓòÉ
Syntax:
sysop <text>
Example:
sysop Matthias Tichy
You specify your name with this keyword.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.5. include ΓòÉΓòÉΓòÉ
Syntax:
include <file>
Example:
include /etc/fido/areas
You can include other files into your config file. For example if you would
like to have different config parts, you can include a file and (via cron job
or manually) change the content of this file without changing the rest of the
config. Additionally you can split your config in different parts. So you can
have your fileareas definition in another file than your msgareas definition.
This gives your the ability to have some survey about your config.
This statement can be repeated. But dont make recursive includes. eg include a
file which includes another which includes the first. Although this will be
detected and fixed many times, there is a chance that it will not be detected
one time.
ΓòÉΓòÉΓòÉ 4.3.6. address ΓòÉΓòÉΓòÉ
Syntax:
Address <aka> [Line [unsignedInteger]1* ]
Example:
Address 2:2433/1245 Line 1 4 5
This command specifies which akas your system has. This statement is full 5d
compatible, which means you can have also addresses like
2:2433/1245.1@fidonet.org. If the Line options is empty this aka is displayed
on all lines. In the above example this aka is displayed on line 1, 4 and 5.
The first address statement is your main aka which will be used by tossers on
different occasions, for example if zone number could not be taken from the
@INTL Kludge in netmails.
This statement can be repeated.
*The Line option is not supported* *The domain name is not full supported
throughout fidoconfig*
ΓòÉΓòÉΓòÉ 4.3.7. outbound ΓòÉΓòÉΓòÉ
Syntax:
outbound <path>
Example:
outbound /var/spool/fido/out
This command specifies your outbound path. This outbound path is
binkley-style. A binkley style outbound consists of a base path and
subdirectories. Each subdirectory represents a place for all the files for one
zone. The base path is the zone path for your base zone.
Example:
/var/spool/fido/out
This directory contains the files for your base zone.
/var/spool/fido/out.003
This directory contains the files for zone 3.
/var/spool/fido/out.00A
This directory contains the files for zone 10.
The zone directory contains the flow-files for each node. A Flow-file of a
node has the name NNNNFFFF.?lo
NNNN
The 4-digit hex-number of the nodes netnumber.
FFFF
The 4-digit hex-number of the nodes nodenumber.
?
Here the flavour of the mails can be chosen. *h*old, *c*rash,
*f*normal.
For points there is a subdirectory with nodes flowfilename with suffix.pnt. In
this subdirectory the flowfiles have the names PPPPPPPP ( 8-digit point number
in hex).
For a deeper background on a binkley-style outbound see the binkley-term
documentation and source code.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.8. tempoutbound ΓòÉΓòÉΓòÉ
Syntax:
tempoutbound <path>
Example:
outbound /var/spool/fido/out.tmp
This command specifies your temporaryoutbound path. It is used for outgoing
packets.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.9. inbound ΓòÉΓòÉΓòÉ
Syntax:
inbound <path>
Example:
inbound /var/spool/fido/in
This command specifies where your inbound files are stored. This directory is
the base directory which means if you have a connection which ist not
protected and the other system is not listed. The files go in here. Only
netmails are tossed from this inbound.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.10. protinbound ΓòÉΓòÉΓòÉ
Syntax:
protinbound <path>
Example:
protinbound /var/spool/fido/in.sec
This command specifies where files should be stored which were received during
a password-protected session. All types of mail are tossed from this path. But
passwords are checked before.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.11. listinbound ΓòÉΓòÉΓòÉ
Syntax:
listinbound <path>
Example:
listinbound /var/spool/fido/in.lst
This command specifies where the files should be stored which were received
during a non-password-protected session from a listed system. Only netmails
are tossed from this path.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.12. localinbound ΓòÉΓòÉΓòÉ
Syntax:
localinbound <path>
Example:
localinbound /var/spool/fido/in.loc
This command specifies the path, from which all types of netmail and echomail
are tossed *without* any password checking. You can put pktΓöñs here which were
created by a file tosser etc. So created by a you or a programm on your own
system.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.13. tempinbound ΓòÉΓòÉΓòÉ
Syntax:
tempinbound <path>
Example:
tempinbound /var/spool/fido/in.tmp
This command specifies a path which is used while tossing. The incoming
packets are unpacked there.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.14. msgBaseDir ΓòÉΓòÉΓòÉ
Syntax:
msgBaseDir <path>
Example:
msgBaseDir /var/spool/fido/msgb
This command specifies the path where autoareacreated msgBases are stored. For
example: If an area called LINUX.GER was autoareacreated and the msgBaseDir is
/var/spool/fido/msgb the resulting msgBaseName is
/var/spool/fido/msgb/linux.ger.sqd
If you specify the msgbasedir as PASSTHROUGH, the areas are created as
passthrough areas.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.15. intab ΓòÉΓòÉΓòÉ
Syntax:
intab <file>
Example:
intab /var/spool/fido/recode/outaltkoi8
This statement specifies the file which should be used to recode the
characters of the incoming messages from transport to internal charset. It is
useful in russia. If you do not use this statement no recoding will be done.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.16. outtab ΓòÉΓòÉΓòÉ
Syntax:
outtab <file>
Example:
outtab /var/spool/fido/recode/outkoi8alt
This statement specifies the file which should be used to recode the
characters of the outgoing messages from internal to transport charset. It is
useful in russia. If you do not use this statement no recoding will be done.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.17. importlog ΓòÉΓòÉΓòÉ
Syntax:
importlog <file>
Example:
importlog /var/spool/fido/import.log
This statement specifies the file which a tosser fills with the names of the
areas where echomails has been tossed in.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.18. echotosslog ΓòÉΓòÉΓòÉ
Syntax:
echotosslog <file>
Example:
echotosslog /var/spool/fido/echotoss.log
This statement specifies the file which is filled by a message editor with the
names of the areas where new echomails have been entered. A tosser will only
scan those areas which leads to a great speed-up. After scanning the tosser
will remove the file.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.19. linkWithImportLog ΓòÉΓòÉΓòÉ
Syntax:
linkWithImportLog <yers|no|kill>
Example:
linkWithImportLog yes
This statement specifies if the importlog-file should be used to determine
which echomail areas need to be linked.
yes
importlog-file will be read. areas which are in importlog, will be
linked. the importlog-file will not be erased.
kill
like yes, but the importlog-file will be killed after using it.
no
DEFAULT. all areas will be linked.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.20. public ΓòÉΓòÉΓòÉ
Syntax:
public <path>
Example:
public /var/spool/fido/public
This command specifies the path where files which are requested are searched
for. The files are searched in this directory and in all subdirectories.
This command can be repeated.
ΓòÉΓòÉΓòÉ 4.3.21. logFileDir ΓòÉΓòÉΓòÉ
Syntax:
logFileDir <path>
Example:
logFileDir /var/spool/log/fido
This command specifies the path where the log-files of the fido-programs
should be stored.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.22. dupeHistoryDir ΓòÉΓòÉΓòÉ
Syntax:
dupeHistoryDir <path>
Example:
dupeHistoryDir /var/spool/fido/dupes
This command specifies the path where the dupe history files are stored. The
format and the names of the dupe-files are not standardized.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.23. nodelistDir ΓòÉΓòÉΓòÉ
Syntax:
nodelistDir <path>
Example:
nodelistDir /var/spool/fido/nodelist
This command specifies the path where the actual nodelists are or should be
written to. This path contains the raw nodelist as well as the compiled ones.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.24. magic ΓòÉΓòÉΓòÉ
Syntax:
magic <path>
Example:
magic /var/spool/fido/magic
Directory with executables to satisfy "magic" file requests if requested a
file present in this directory, it will be executed and stdout sent to the
remote system. If the file is not executable, it is read line by line and the
lines are processed as if they were received file requests (recusively).
Execution of commands may compromize security! You are warned.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.25. lockfile ΓòÉΓòÉΓòÉ
Syntax:
lockfile <file>
Example:
lockfile /var/lock/hpt
another session of hpt will be terminated if found lockfile
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.26. link ΓòÉΓòÉΓòÉ
Syntax:
link <name>
Example:
link Matthias Tichy
This statement starts a new Link-definition. All the following link-related
statements change the configuration of this link until a new link statement is
found. The name is the name of this link.
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.27. aka ΓòÉΓòÉΓòÉ
Syntax:
aka <aka>
Example:
aka 2:2433/1245
This statement sets the aka for the current link.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.28. ouraka ΓòÉΓòÉΓòÉ
Syntax:
ouraka <aka>
Example:
ouraka 2:2433/1247
This statement sets the aka which is used with this link.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.29. password ΓòÉΓòÉΓòÉ
Syntax:
password <string>
Example:
password secret
This statement sets the session and the default password for the link. If you
do not change the other passwords, they are set to this password. Only
passwords with maximal 8 characters are valid because of limitations of other
software packages.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.30. pktpwd ΓòÉΓòÉΓòÉ
Syntax:
pktpwd [<string>]
Example:
pktpwd geheim
This statement sets the pktpassword for the actual link. Only passwords with
maximal 8 characters are valid because of limitations of other software
packages. An empty statement is allowed.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.31. ticpwd ΓòÉΓòÉΓòÉ
Syntax:
ticpwd [<string>]
Example:
ticpwd geheim
This statement sets the ticcer password for the actual link. Only passwords
with maximal 8 characters are valid because of limitations of other software
packages. An empty statement is allowed.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.32. areafixpwd ΓòÉΓòÉΓòÉ
Syntax:
areafixpwd [<string>]
Example:
areafixpwd geheim
This statement sets the areafix password for the actual link. Only passwords
with maximal 8 characters are valid because of limitations of other software
packages. An empty statement is allowed.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.33. filefixpwd ΓòÉΓòÉΓòÉ
Syntax:
filefixpwd [<string>]
Example:
filefixpwd geheim
This statement sets the filefix password for the actual link. Only passwords
with maximal 8 characters are valid because of limitations of other software
packages. An empty statement is allowed.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.34. bbspwd ΓòÉΓòÉΓòÉ
Syntax:
bbspwd [<string>]
Example:
bbspwd geheim
This statement sets the bbs password for the actual link. Only passwords with
maximal 8 characters are valid because of limitations of other software
packages. An empty statement is allowed.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.35. handle ΓòÉΓòÉΓòÉ
Syntax:
handle <name>
Example:
handle eddie
This statements gives a link a nickname. This statement is supposed for bbs
systems.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.36. tossgrp ΓòÉΓòÉΓòÉ
Syntax:
tossgrp {<group>}
Example:
tossgrp fido
This statement connects a link to several echomails groups.
This statement can only be repeated for different links.
*This statement is currently not supported.*
ΓòÉΓòÉΓòÉ 4.3.37. ticgrp ΓòÉΓòÉΓòÉ
Syntax:
ticgrp {<group>}
Example:
ticgrp gfd
This statement connects a link to several fileecho groups.
This statement can only be repeated for different links.
*This statement is currently not supported.*
ΓòÉΓòÉΓòÉ 4.3.38. bbsgrp ΓòÉΓòÉΓòÉ
Syntax:
bbsgrp {<group>}
Example:
bbsgrp pay1
This statement connects a link to several bbs groups.
This statement can only be repeated for different links.
*This statement is currently not supported.*
ΓòÉΓòÉΓòÉ 4.3.39. accessgrp ΓòÉΓòÉΓòÉ
Syntax:
accessgrp {<group>}
Example:
accessgrp pay1
This statement connects a link to several echomail groups. See also
"publicgroup".
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.40. optgrp ΓòÉΓòÉΓòÉ
Syntax:
optgrp {<group>}
Example:
optgrp py
Export, Import & Mandatory restrictions uses "optgrp" areas instead of
"accessgrp".
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.41. export ΓòÉΓòÉΓòÉ
Syntax:
export (on|off)
Example:
export off
By default "export on".
if "export" is off, mail for groups defined in "optgrp" not tossed to link and
if "optgrp" not defined, then no mail tossed to link at all.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.42. import ΓòÉΓòÉΓòÉ
Syntax:
import (on|off)
Example:
import off
By default "import on".
Same as "export", but this is for mail *from* link.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.43. mandatory ΓòÉΓòÉΓòÉ
Syntax:
mandatory (on|off)
Example:
mandatory on
By default "mandatory off".
This statament do not allow the link to subscribe/unsubscribe areas
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.44. level ΓòÉΓòÉΓòÉ
Syntax:
level {<integer>}
Example:
level 200
Access level. Used in echoareas to control read/write access. By default
"level 0".
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.45. autoareacreate ΓòÉΓòÉΓòÉ
Syntax:
autoareacreate (on|off)
Example:
autoareacreate on
This statement gives a link the permission to create areas on your system just
by sending msgs in them. The echoarea is created using the AutoCreateDef
contents:
EchoArea <areaName> <msgBaseDir><areaName> -a <mypktaka> Squish <linkAka> <autoCreateDef>
This statement can only be repeated for different links.
*This statement is only a temporal solution for autoareacreating. It will be
replaced by the group scheme, which is about to be implemented.*
ΓòÉΓòÉΓòÉ 4.3.46. autoareacreatedefaults ΓòÉΓòÉΓòÉ
Syntax:
autoareacreatedefaults [<string>]
Example:
autoareacreatedefaults -$m 200 -dupecheck move
Set defaults to autocreated echoareas.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.47. packer ΓòÉΓòÉΓòÉ
Syntax:
packer <packer>
Example:
packer zip
This statement sets the packer for the link. You can use the packer which you
has set up using the pack statement. If you omit this statement no mail will
be packed. The pktΓöñs will be put in the outbound.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.48. echomailflavour ΓòÉΓòÉΓòÉ
Syntax:
echoMailFlavour <hold|normal|crash|direct|immediate>
Example:
echoMailFlavour hold
This statement sets the flavour which outgoing echomails for this link get.
For example set echomailFlavour for points to hold and for uplink crash.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.49. autoCreateFile ΓòÉΓòÉΓòÉ
Syntax:
autoCreateFile <fileName>
Example:
autoCreateFile /etc/fido/areas.matthias
This statement defines where autocreated areas by this link are going to. If
you omit this statement the default configuration file will be used. The
tosser must have the rights to create and change the file.
*You must include the specified file for yourself into fidoconfig, so these
autocreated areas are found in subsequent tosser-runs.*
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.50. forwardRequests ΓòÉΓòÉΓòÉ
Syntax:
forwardRequests (on|off)
Example:
forwardRequests on
By default "forwardRequests off". "on" allow forward requests to this link
from other links.
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.51. forwardRequestFile ΓòÉΓòÉΓòÉ
Syntax:
forwardRequestFile <fileName>
Example:
forwardRequestFile /etc/fido/fidonet.na
file for forward requests (also for available areas and descriptions) if not
defined then forward requests unconditional
This statement can only be repeated for different links.
ΓòÉΓòÉΓòÉ 4.3.52. forwardPkts ΓòÉΓòÉΓòÉ
Syntax:
forwardPkts <no|secure|yes>
Example:
forwardPkts yes
If we receive a PKT file that is not addressed to our system, but to this link
of us, this flag controls if the PKT file should be binary forwarded to this
link. The default behaviour is not to forward the pkt file, but to remain it
to <filename>.ntu and leave it in the inbound. If you specify <yes>, the file
will instead be forwarded to the destination link (i.E. put into his arcmail
bundle). If you specify <secure>, the file will only be forwarded if we have
received it in the secure inbound. You should specify secure if the
destination link does not check packet passwords.
PKT forwarding can be useful for tunneling purposes, for instance. Another
example is if you are running two nodes, one IP node at your company and one
PSTN node at your home. If you want to show both node numbers at both mailers,
the tossers at each node must forward PKT files that are addressed to the
other node, because they themselves cannot process it (each tosser has a
different node number, because the systems operate on distinct outbound
structures and distinct message base areas).
ΓòÉΓòÉΓòÉ 4.3.53. pause ΓòÉΓòÉΓòÉ
Syntax:
pause
Example:
pause
Stop export echomail for this link.
ΓòÉΓòÉΓòÉ 4.3.54. netmailarea ΓòÉΓòÉΓòÉ
Syntax:
NetmailArea <name> <file> [<msgbase>] {Option}
Example:
NetmailArea netmail /var/spool/fido/msgb/netmail Squish
This statement specifies the netmailarea. See echoarea, for details on Option.
Like all areas Netmailareas are *.msg bases per default.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.55. badarea ΓòÉΓòÉΓòÉ
Syntax:
badArea <name> <file> [<msgbase>] {Option}
Example:
BadArea badarea /var/spool/fido/msgb/bad Squish
This statement specifies the badarea. Messages which have no area on your
system go to the badArea. See echoarea, for details on Option. Like all areas
Badareas are *.msg bases per default.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.56. dupeArea ΓòÉΓòÉΓòÉ
Syntax:
dupeArea <name> <file> [<msgbase>] {Option}
Example:
dupeArea dupeArea /var/spool/fido/msgb/dupes Squish
This statement specifies the dupeArea. Messages which area dupes e.g. come to
your system the second time, will be put in the dupearea. See echoarea, for
details on Option. Like all areas Dupeareas are *.msg bases per default.
This statement cannot be repeated.
ΓòÉΓòÉΓòÉ 4.3.57. echoArea ΓòÉΓòÉΓòÉ
Syntax:
EchoArea <name> <file> [<msgbase>] {Option} {linkAka} {linkOption}
Example:
EchoArea linux.develop.ger /var/spool/fido/msgb/linux.develop.ger
Squish -a 2:2433/1247 -dupeCheck move -dupehistory 11 -d "Linux
development" 2:2433/1245
This statement specifies the echoareas.
name:
area-tag
file:
filename(s) for this area without extension; should be the area-tag
(as far as possible) if file == Passthrough then [<msgBase>] is
skipped and msgarea is set as an passthrough area
msgbase:
*.msg is standard. Write Squish for an Squish-msgbase
LinkAKA:
aka's of up- and down links
Options:
-lr <integer>
required level for read access (see also "level" in link options)
-lw <integer>
required level for write access
-mandatory
forbid to subscibe/unsubscribe from this echo
<linkAka> -r
this link is read only
<linkAka> -w
this link is write only
<linkAka> -mn
this link is mandatory subscribed you may also set: "<aka> -r -mn"
or "<aka> -w -r" and so on...
-p <integer>
purge after n days,
-$m <integer>
leave max n messages after purge in area
-a <aka>
aka to use
-keepsb
keep seen-by's
-tinysb
keep only seen-by's of links listed in {link}
-manual
disallow remote changes (only manual connect/disconnect)
-dosfile
file name of area is in dos style (8+3)
-h
hide area
-d <"Description for the area between double quote (like this)">
describe area
-nopause
%PAUSE has no effect to this area
-ccoff
disables carbonCopies for this area
-DupeCheck off|move|del
toss in dupes, move dupes to dupeArea or delete dupes.
-DupeHistory <unsignedInteger>
size of dupecheck history file in days
LinkOption:
-imp
import only for redundant echomail-supply
-def
default-uplink for redundant echomail-supply
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.58. localArea ΓòÉΓòÉΓòÉ
Syntax:
localArea <name> <file> [<msgbase>] {Option}
Example:
localArea linux.develop.ger /var/spool/fido/msgb/linux.develop.ger
Squish -a 2:2433/1247 -dupeCheck move -dupehistory 11 -d "Linux
development"
This statement creates an localArea. The only difference between a localArea
and a echoArea is that a localArea has no links and is not scanned for new
mails.
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.59. PublicGroup ΓòÉΓòÉΓòÉ
Syntax:
PublicGroup {<groups>}
Example:
PublicGroup abcde12
Tis is a list of groups for public echo acess.
ΓòÉΓòÉΓòÉ 4.3.60. GroupAutoAreaCreate ΓòÉΓòÉΓòÉ
Syntax:
GroupAutoAreaCreate on|off {<groups>}
Example:
GroupAutoAreaCreate on fidonet fido.de
You can here define for all the members of a group, if they area allowed to
autoCreate areas on your system. If no group is given, this is default for all
groups.
*This statement is currently not supported.*
ΓòÉΓòÉΓòÉ 4.3.61. AutoCreateDefaults ΓòÉΓòÉΓòÉ
Syntax:
AutoCreateDefaults <string>
Example:
AutoCreateDefaults -$m 200 -dupeCheck move -dosfile -d "Autocreated
area"
Area options defaults for autoCreated Areas.
*This will be replaced by the more flexible group definition.*
ΓòÉΓòÉΓòÉ 4.3.62. GroupDefaults ΓòÉΓòÉΓòÉ
Syntax:
GroupDefaults <groups> <path> [<msgbas>] {<option>} {<linkAka>
{linkoption}}
Example:
GroupDefaults fidonet /var/spool/fido/msgb Squish -$m 200 -dupeCheck
move -dupeHistory 14 -d "Autocreated Area"
This statement sets the default for auto created Areas according to the group
of the creater.
*This is currently not supported*
ΓòÉΓòÉΓòÉ 4.3.63. Pack ΓòÉΓòÉΓòÉ
Syntax:
Pack zip|tgz|rar|arc|arj|..... <call>
Example:
Pack zip zip -9 -g -q $a $f
This statement sets the command line call for the packer. The file will be
moved into the archiv, that means the file will be deleted on the harddisk. It
only remains in the archiv.
$a will be replaced by the archiv file
$f will be replaced by the file which should be packed into the archiv
ΓòÉΓòÉΓòÉ 4.3.64. Unpack ΓòÉΓòÉΓòÉ
Syntax:
Unpack "<Call>" <offset> <matchcode>
Example:
Unpack "unzip -joLqq $a -d $p" 0 504b0304
This statement sets the call of certain unpackers according to a id in the
archiv file
call: see pack
offset: position of recognition string in packed file.
offset ::= <hexValue>
match code: recognition string for packed file, ?? can be used as don't care
$p will be replaced by the temp inbound path
e.g.: unpack "unzip -joLqq $a -d $p" 0 504b0304
files packed by zip can be recognized by
504b0304(hex) at offset 0(hex)
they can be unpacked by "unzip -joLqq <filename> -d <path>"
ΓòÉΓòÉΓòÉ 4.3.65. route ΓòÉΓòÉΓòÉ
Syntax:
route <flavour> [enc|noenc] <target> {<linkWW>}
Example:
route crash 2:2433/1245 2:2433/* 2:2432/*
This statement defines a route.
*flavour:*
1. hold
2. normal
3. crash
4. direct
5. immediate
enc: means encrypted msgs
noenc: means unencrypted msgs
*target:*
1. <aka>
2. host
3. hub
4. boss
5. no-route
linkWW is a dos pattern with ? and *.
Route statements are parsed in descending order: Pseudo-code:
1) actual = first statement
2) if linkWWW = msg-destination using pattern matching
2a) take this routing and return
2b) else actual = next statement
3) jump to 2)
if no route statement found whose pattern matchs witch the aka, then the mail
is left alone.
ΓòÉΓòÉΓòÉ 4.3.66. routeFile ΓòÉΓòÉΓòÉ
Syntax:
route <flavour> [enc|noenc] <target> {<linkWW>}
Example:
route crash 2:2433/1245 2:2433/* 2:2432/*
This statement is the same as the route statement, but considers only msgs
with an file attached.
ΓòÉΓòÉΓòÉ 4.3.67. routeMail ΓòÉΓòÉΓòÉ
Syntax:
route <flavour> [enc|noenc] <target> {<linkWW>}
Example:
route crash 2:2433/1245 2:2433/* 2:2432/*
This statement is the same as the route statement, but considers only msgs
without file attached.
ΓòÉΓòÉΓòÉ 4.3.68. carbonTo ΓòÉΓòÉΓòÉ
Syntax:
carbonTo <name>
Example:
carbonTo Max Levenkov
If an echomail is tossed whose to-field is the same as <name>, the echomail is
copied to the area specified by the carbonArea keyword. The names must be an
exact match.
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.69. carbonFrom ΓòÉΓòÉΓòÉ
Syntax:
carbonFrom <name>
Example:
carbonFrom Matthias Tichy
If an echomail is tossed whose from-field is the same as <name>, the echomail
is copied to the area specified by the carbonArea keyword. The names must be
an exact match.
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.70. carbonKludge ΓòÉΓòÉΓòÉ
Syntax:
carbonKludge <kludge-substring>
Example:
carbonKludge MSGID: 2:5000/117.
If an echomail is tossed which has a kludge line which includes the <kludge-
string> as a substring, he echomail is copied to the area specified by the
arbonArea keyword.
This statement can be repeated.
ΓòÉΓòÉΓòÉ 4.3.71. carbonArea ΓòÉΓòÉΓòÉ
Syntax:
carbonArea <area-tag>
Example:
carbonArea written.from.points
This statement sets the area for the previous carbon{To|From|Kludge}
statement. If this statement is ommitted. The carbon Copy goes to the badArea.
This statement can be repeated for each different carbon{To|From|Kludge}
statement.
ΓòÉΓòÉΓòÉ 4.3.72. areafixFromPkt ΓòÉΓòÉΓòÉ
Syntax:
areafixFromPkt
Example:
areafixFromPkt
Process areafix requests on the fly. Check "areafix", "areamgr" & "hpt"
keywords in toUserName field.
ΓòÉΓòÉΓòÉ 4.3.73. areafixKillReports ΓòÉΓòÉΓòÉ
Syntax:
areafixKillReports
Example:
areafixKillReports
Set kill/sent flag to areafix reports.
ΓòÉΓòÉΓòÉ 4.3.74. ReportTo ΓòÉΓòÉΓòÉ
Syntax:
ReportTo <name>
Example:
ReportTo netmail
Set area or netmail for areafix reports.
ΓòÉΓòÉΓòÉ 4.3.75. logEchoToScreen ΓòÉΓòÉΓòÉ
Syntax:
logEchoToScreen
Example:
logEchoToScreen
Set output to screen log messages.
ΓòÉΓòÉΓòÉ 4.3.76. Remap ΓòÉΓòÉΓòÉ
Syntax:
Remap <toUserName>,<toAka>,<newAka>
Example:
Remap Max Levenkov,2:5000/117,2:5000/117.1
Remap mail to other address.
ΓòÉΓòÉΓòÉ 4.3.77. SeparateBundles ΓòÉΓòÉΓòÉ
Syntax:
SeparateBundles
Example:
SeparateBundles
This statament move echomail for all links to his own directory.
ΓòÉΓòÉΓòÉ 4.4. Working sample config ΓòÉΓòÉΓòÉ
# sample fido config file
version 0.14 # test for new stripComment
Name LeeteBrok BBS III
Location Paderborn, GER
Sysop Matthias Tichy
Address 2:2433/1247 #
Address 2:2433/1245.1
Address 2:2432/601.29
Address 2:2432/605.14
Address 44:4932/100.14
# This is taken from Serge Koghin's ParToss
# Hope he wouldn't be angry for this
# ATTENTION the commeneed lines are not tested by me (mtt)
# and will mostly only useful on dos-systems
Unpack "unzip -j -Loqq $a -d $p" 0 504b0304
Pack zip zip -9 -j -q $a $f
#Unpack "pkunpak /r $a $p" 0 1a
#Pack arc pkpak -oct a $a $f
#Unpack "pak e /wn $a $p" -2 fe
#Pack pak pak a $a $f
#Unpack "lha e /m $a $p" 2 2d6c68
#Pack lha lha a /o /m $a $f
#Unpack "zoo e:O $a $p" 0 5a4f4f
#Pack zoo zoo a: $a $f
#Unpack "arj e -+ -y $a $p" 0 60ea
#Pack arj arj a -+ -e -y $a $f
Unpack "unrar e -y $a $p > /dev/null" 0 52617221
#Pack rar rar a -std -ep $a $f
#Unpack "jar e -y $a $p" 14 1a4a61721b
#Pack jar jar a -y $a $f
#Unpack "ha eyq $a" 0 4841
#Pack ha ha a21eq $a $f
# include /etc/fido/areas
Link Matthias Schniedermeyer
Aka 2:2432/605
ourAka 2:2432/605.14
Password hghprt
EchoMailFlavour Crash
AutoAreaCreate on
AutoCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
Packer zip
Link Matthias Schniedermeyer
Aka 2:2432/600
ourAka 2:2432/605.14
Password hghprt
EchoMailFlavour Crash
AutoAreaCreate on
AutoCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
Packer zip
Link Matthias Schniedermeyer
Aka 44:4932/100
ourAka 44:4932/100.14
password hghprt
EchoMailFlavour Crash
AutoAreaCreate on
AutoCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
Packer zip
Link Matthias Tichy
Aka 2:2433/1245
# OurAka 2:2433/1247
ourAka 2:2433/1245.1
# Password Test
Password
forwardPkts On
autoAreaCreate on
AutoCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
Link edde
AKA 2:2433/1245.100
OurAka 2:2433/1247
AutoAreaCreate on
AutoCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
AutoCreateFile /etc/fido/autocreated.edde
password xxx
forwardPkts Secure
#route crash 2:2433/1245 *
#route hold 2:2433/1247.100 2:2433/1247.100
#route Crash 2:2433/1245 2:2433/*
#route hold noroute 2:2433/1245.*
#route crash host 2:2433/*
#route crash enc no-route *
Route crash 44:4932/100 44:*
Route crash 2:2432/605 *
Inbound n /home/mtt/fido/in/
ProtInbound n/home/mtt/fido/in.sec
LocalInbound /home/mtt/fido/in.loc
Outbound /home/mtt/fido/out/
tempOutbound /home/mtt/fido/out.tmp
tempInbound /home/mtt/fido/in.tmp
#MsgBaseDir Passthrough
MsgBaseDir /home/mtt/fido/msgb
public b t/home/mtt/fido/public
# public t t/home/mtt/fido/public2
# intab /home/mtt/fido/recode/outaltkoi8
# outtab /home/mtt/fido/recode/outkoi8alt
echotosslog /home/mtt/fido/echotoss.log
importlog /home/mtt/fido/import.log
logFileDir /home/mtt/hpt/linux
DupeHistoryDir p/home/mtt/fido/dupes
NodelistDir i/home/mtt/fido/nodelist
magic i t/home/mtt/fido/magic
areafixhelp /home/mtt/hpt/misc/areafix.hlp
NetmailArea NetmailArea /home/mtt/fido/msgb/netmail msg
# NetmailArea NetmailArea /home/mtt/fido/msgb/net Squish
BadArea BadArea /home/mtt/fido/msgb/bad squish
DupeArea DupeArea /home/mtt/fido/msgb/dupe squish
EchoArea 2432.points /home/mtt/fido/msgb/2432/points -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea 2432.Talk /home/mtt/fido/msgb/2432/talk -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea C_ECHO.ger /home/mtt/fido/msgb/c_echo_g -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea C_PLUSPLUS.ger /home/mtt/fido/msgb/c_plpl_g -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea binkley /home/mtt/fido/msgb/binkley -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea Binkley.ger /home/mtt/fido/msgb/binkley_g -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea Dolphin.Points /home/mtt/fido/msgb/dolphin/point -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea Dolphin.announce /home/mtt/fido/msgb/dolphin/announce -a 2:2432/605.14 Squish -p 14 2:2432/600
EchoArea hardrock.ger /home/mtt/fido/msgb/hardrock_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea linux.ger /home/mtt/fido/msgb/linux/ger -a 2:2432/605.14 squish -p 14 -dupecheck move -dupeHistory 11 2:2432/600
echoArea linux.develop.ger /home/mtt/fido/msgb/linux/develop_g -a 2:2432/605.14 squish -dupeCheck move -dupeHistory 11 2:2432/600
#echoarea linux.ger /home/mtt/fido/msgb/linux/ger -a 2:2433/1247 squish 2:2433/1245 2:2433/1200
# echoarea linux.develop.ger /home/mtt/fido/msgb/linux/develop_g -a 2:2433/1247 squish 2:2433/1245 2:2423/605 2:2433/1245.100
EchoArea os2.base.ger /home/mtt/fido/msgb/os2/base_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.beta.ger /home/mtt/fido/msgb/os2/beta_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2bbs.ger /home/mtt/fido/msgb/os2/bbs_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.debate.ger /home/mtt/fido/msgb/os2/debate_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.install.ger /home/mtt/fido/msgb/os2/install_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea Os2.wps.ger /home/mtt/fido/msgb/os2/wps_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea Os2.prog.ger /home/mtt/fido/msgb/os2/prog_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea Os2.lan.ger /home/mtt/fido/msgb/os2/lan_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.hw.ger /home/mtt/fido/msgb/os2/hw_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.online.ger /home/mtt/fido/msgb/os2/online_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea os2.tec.ger /home/mtt/fido/msgb/os2/tec_g -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea OWL.Newfiles /home/mtt/fido/msgb/owl/newfiles -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea owl.announce /home/mtt/fido/msgb/owl/announce -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea owl.flea /home/mtt/fido/msgb/owl/flea -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea owlserver.news /home/mtt/fido/msgb/owl/snews -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea Paderborn.Flohmarkt /home/mtt/fido/msgb/pader/floh -a 2:2432/605.14 squish -p 14 2:2432/600
EchoArea Tolkien.ger /home/mtt/fido/msgb/tolkien_g -a 2:2432/605.14 squish -dupeCheck move -p 14 2:2432/600
EchoArea Schweden.ger /home/mtt/fido/msgb/schweden_g -a 2:2432/605.14 squish -tinySB -p 14 2:2432/600
LocalArea carbonArea /home/mtt/fido/msgb/carbonArea squish
CarbonTo Matthias Tichy
CarbonArea carbonArea
EchoArea paderborn.mailbox /home/mtt/fido/msgb/paderborn.mailbox -a 2:2432/605.14 Squish -dupeCheck move -dupeHistory 11 -p 14 2:2432/600
EchoArea owl.allfix /home/mtt/fido/msgb/owl.allfix -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fidosoft.winpoint.ger /home/mtt/fido/msgb/fidosoft.winpoint.ger -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea net_dev.ger /home/mtt/fido/msgb/net_dev.ger -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea net_dev /home/mtt/fido/msgb/net_dev -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fidosoft.ger /home/mtt/fido/msgb/fidosoft.ger -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.bbs /home/mtt/fido/msgb/linux.bbs -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.software /home/mtt/fido/msgb/linux.software -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.setup /home/mtt/fido/msgb/linux.setup -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.reg /home/mtt/fido/msgb/linux.reg -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.netzwerk /home/mtt/fido/msgb/linux.netzwerk -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.announce /home/mtt/fido/msgb/linux.announce -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.hardware /home/mtt/fido/msgb/linux.hardware -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea darkness.info /home/mtt/fido/msgb/darkness.info -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.coord /home/mtt/fido/msgb/linux.coord -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea 2432.nodes.info /home/mtt/fido/msgb/2432.nodes.info -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea linux.office /home/mtt/fido/msgb/linux.office -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.develop /home/mtt/fido/msgb/linux.develop -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea linux.x /home/mtt/fido/msgb/linux.x -a 44:4932/100.14 Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
EchoArea 2432.nodes /home/mtt/fido/msgb/2432.nodes -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea fido2000.ger /home/mtt/fido/msgb/fido2000.ger -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea java.ger /home/mtt/fido/msgb/java.ger -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
EchoArea ftsc_public /home/mtt/fido/msgb/ftsc_public -a 2:2432/605.14 Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
ΓòÉΓòÉΓòÉ 5. Converting fidoconfig to golded, msged and aquaed ΓòÉΓòÉΓòÉ
Since goldEd not support fidoconfig, and msged and aquaed only in beta
versions, we have developed two programs which converts your fidoconfig to the
proprietary config file format.
1. fconf2golded fconf2golded <goldedConfigFileName> [<default.cfg>]
fconf2golded ~/golded/golded.cfg ~/golded/goldDefaults.cfg
2. fconf2msged fconf2msged <msgedConfigFileName>
fconf2msged ~/msged.areas
3. fconf2aquaed fconf2aquaed <aquaedConfigFileName> [<default.cfg>] (if you
specify default.cfg there will be a include <default.cfg> generated in
your config file)
fconf2aquaed ~/aquaed/aquaed.cfg
ΓòÉΓòÉΓòÉ 6. Testing the config ΓòÉΓòÉΓòÉ
You should run tparser everytime you have changed the config. If tparser
crashes please correct your config file and send your config or the line which
causes the crash.
./tparser | less
tparser (like any fidoconfig program) will display error messages if you have
made an error in the config. It will grumble on every Keyword it does not know.
It will stop after the first error to give you the ability to change your
config.
ΓòÉΓòÉΓòÉ 7. Contacting the author ΓòÉΓòÉΓòÉ
You can reach me at
2:2432/605.14
2:2433/1245
and in the fido echoarea
linux.develop.ger
The actual fidoconfig library and other fido software will be on www.tichy.de.