FidoConfig Manual


Node: Top, Up: (dir)

fidoconfig

This document describes the use of fidoconfig to make fido work on your favorite platform.

This document applies to version 1.4 of fidoconfig.


Node: design goals, Next: , Previous: Top, Up: Top

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.


Node: config file, Next: , Previous: design goals, Up: Top

Config file

This chapter describes how a fidoconfig config-file is written, which keywords exist and where to put the file.


Node: Location, Next: , Previous: config file, Up: config file

Config file location

The fidoconfig library searches the config file on different locations:

linux:
/etc/fido/config
freebsd:
/usr/local/etc/fido/config
os2/win32/etc:
in the current directory

If you compile library with huskymak.cfg, the location will be overset with CFGDIR parameter.

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 using the autoareacreate feature of HPT / autofilecreate featute of HTick / etc..., the config file(s) must be writeable.


Node: Syntax, Next: , Previous: Location, Up: config file

Syntax

All symbols are not case-sensitive.

{<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 last line matching the situation is valid. Another words: second definition overwrites the previous one. If no match is found, a default value will be used.

"#" at the start of a line or <whiteSpace>#<whiteSpace> within the line starts a comment. The comment ends with the line. Comment char "#" can be overwritten by commentChar token.

If the first word in a line is an undefined keyword, program exits with error message.

Each keyword has to start a new line.

Keyword parameters:

<integer>
string including integer numbers, like: 1234567890
<string>
text string
<bool>
may be set to "1", "0", "yes", "no", "on", "off", and also without parameters (it means "on").
<addr>
address string like zone:net/node[.point][@domain]
example: 2:5000/117
<file>
file name. path can be omitted.
<path>
only path. trailing slash may be included or not.

Note! [<parameter>] means that it can be omitted.

FIDOCONFIG library can set up internal variables:

     set basedir=/home/user/fido/
     

[OS] variable is automatically set up for following operating systems:

UNIX
All unix-like OS: Linux, *BSD, BeOS, ...
OS/2

WIN

MSDOS

You can set something like:

     if [OS]==UNIX
     tearline `uptime`
     endif
     

Some programs can be compiled with module variable. It can be used to speed up config parsing:

     if [module]==htick
     include /etc/ftn/fileareas
     endif
     

And if HPT is running, fileareas aren't parsed because [module]==hpt.

There are following modules available:

hpt (Highly Portable Tosser)

htick (Husky Ticker)

hptutil

hpucode

Also external variables can be parsed:

     autoexec.bat:
     SET VAR=myvar
     
     fidoconfig:
     if [VAR]==myvar
     ...
     else
     ...
     endif
     
     ifdef UNIX
     MsgBaseDir  [home]/msgbase
     endif
     

You can use external programs output via `cmd`. It is available only for UNIX & OS/2+EMX:

     Name Power Station under `uname -mrs`
     

List of the additional commands:

set, if, if not, else, elseif, ifdef, ifndef, endif.

You can compare with a pattern by using =~ and !~ instead of == and !=:

     if [VAR] =~ *substr*
     ...
     endif
     if [VAR] !~ bla?bla*
     ...
     endif
     


Node: Keywords, Next: , Previous: Syntax, Up: config file

Common keywords for HUSKY-programs

These keywords may be used by several programs. More specific keywords you can find in the programs' individual documentations.


Node: version, Next: , Previous: Keywords, Up: Keywords

version

Syntax:
version <integer>.<integer>
Example:
version 1.4

Here you specify which version of fidoconfig your config belongs to. Currently this statement does nothing.

This statement cannot be repeated.


Node: name, Next: , Previous: version, Up: Keywords

name

Syntax:
name <string>
Example:
name Leetebrok BBS

Here you specify your system's name.

This statement cannot be repeated.


Node: location, Next: , Previous: name, Up: Keywords

location

Syntax:
location <string>
Example:
location Dusseldorf

You specify your location here.

This statement cannot be repeated.


Node: sysop, Next: , Previous: location, Up: Keywords

sysop

Syntax:
sysop <string>
Example:
sysop Matthias Tichy

You specify your name with this keyword.

This statement cannot be repeated.


Node: include, Next: , Previous: sysop, Up: Keywords

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 you the ability to have some survey about your config.

This statement can be repeated. But don't make recursive includes, e.g. 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.


Node: address, Next: , Previous: include, Up: Keywords

address

Syntax:
Address <addr>
Example:
Address 2:2433/1245

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. The first address statement is your main aka which will be used by tosser on different occasions, for example if zone number could not be taken from the @INTL Kludge in netmails.

This statement can be repeated. The domain name is not full supported throughout fidoconfig


Node: commentChar, Next: , Previous: address, Up: Keywords

commentChar

Syntax:
commentChar <char>
Example:
commentChar ;

This command specifies which symbol is used to mark rest of line as comment. Default is '#'

This statement can be repeated.


Node: outbound, Next: , Previous: commentChar, Up: Keywords

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 node's netnumber.
FFFF
The 4-digit hex-number of the node's nodenumber.
?
Here the flavour of the mails can be chosen. h-hold, c-crash, f-normal, d-direct, i-immediate.

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.


Node: inbound, Next: , Previous: outbound, Up: Keywords

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 is 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.


Node: tempDir, Next: , Previous: inbound, Up: Keywords

tempDir

Syntax:
tempDir <path>
Example:
tempDir /var/tmp

This command specifies the path where the temporary files of the fido-programs should be stored. This directory can be erased while booting. Good idea is to set it to a memory disk.

Default value is path specified by TEMP, TMP or TMPDIR enviroment variables (use TEMP first, if it not defined then use TMP, next use TMPDIR). If these enviroment variables are not defined: - win32 versions use %WINDIR%\TEMP (usually c:\windows\temp for Win9x/Me and c:\winnt\temp for Windows NT/2000/XP) - versions for unix-like OS'es use /tmp - other versions use c:\

This statement cannot be repeated.


Node: logfiledir, Next: , Previous: tempDir, Up: Keywords

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.

Some programs use logFileDir for persistent temporary/work files.


Node: syslogfacility, Next: , Previous: logfiledir, Up: Keywords

syslogfacility

Syntax:
syslogFacility <facility>
Example:
syslogFacility local0

Some Husky programs are able to write logs via syslogd instead of via log file. For those programs, this keyword defines which facility to use for writing to the syslog. Syslogd will use this facility name to decide which syslog logfile the log messages will go to. Common names that can be used include mail, news, uucp, local0. The exact values that can be used depend upon your operating system. Refer to the man page for syslog.conf or /usr/include/sys/syslog.h for more information.

Logging via syslogd is only supported on UNIX platforms, and currently only used by herp, but not by any other Husky program. If a Husky program logs via log file or via syslog or both depends on the program and not on your fidoconfig file. Consult the individual program's documentation.


Node: loglevels, Next: , Previous: syslogfacility, Up: Keywords

LogLevels

Syntax:
loglevels <string>
Example:
loglevels 1345789,A-F Q

This statement defines log levels list for writing messages into log file. Hiphen is a range char (A-F expands to ABCDEF). Only alpha & numeric log level characters are recognized, others are ignored.

In example we output to log messages with levels 3,4,5,7,8,9,A,B,C,D,E,F,Q.

The log levels are following:

1 - Program start, end;

2 - dupecheck

3 - linking messages

4 - scanning messages

5 - posting messages

6 - execute strings

7 - bundles, pkts, links, freqs, file routing, file attachs, msg packing

8 - areafix, relink, autocreate

9 - error messages (critical, usually exit on error)

0 - creation of file-flags

A - trivial error messages (print message and continue execution)

B - warnings & alerts

C - informational messages

D - statistics

E - summary

F - print program name & version

G - message send/sent

H - recoding operations & recoding tables read/write

I - Generate or check MSGID

J - Echomail phase

K - Filebox phase

L - Netmail phase

M - File create

N - File delete

O - operations with opened file (read, write, seek, ...)

P - Directory operations (create, delete, rename, ...)

Q - Email message parsing and construction

R - Truncate file

S - File send/sent

T - Test files (exist, permittions, etc.)

U - Functions calls (entering func & leaving it)

V - reserved

W - reserved

X - Filenames construction

Y - Link messagebase pass (some phase in hptlink & etc)

Z - debug messages: source lines (functions control points).

a-z - debug messages

Default value: 1234567890ABCDEF

This statement cannot be repeated.


Node: screenloglevels, Next: , Previous: loglevels, Up: Keywords

ScreenLogLevels

Syntax:
screenloglevels <string>
Example:
screenloglevels 2345789,A-C

Sets levels of log output to screen. See loglevels for details.

This statement cannot be repeated.


Node: seqdir, Next: , Previous: screenloglevels, Up: Keywords

seqdir

Syntax:
seqDir <path>
Example:
seqDir /var/spool/fido/seq

Sets path for current msgid sequence stamp.

By default environment variable SEQDIR is used.

This statement cannot be repeated.


Node: seqoutrun, Next: , Previous: seqdir, Up: Keywords

seqoutrun

Syntax:
seqOutrun <string>
Example:
seqOutrun 1m

Sets maximum outrun for msgid sequence from current time.

Use decimal number with optional suffix.

Suffixes are:

y - year (365 days)

m - month (31 days)

w - week (7 days)

d - day

h - hour

Set seconds without suffix.

By default environment variable SEQOUT is used, or 3y if it isn't set.

This statement cannot be repeated.


Node: pack, Next: , Previous: seqoutrun, Up: Keywords

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 archive, that means the file will be deleted from the harddisk. It only remains in the archive.

$a will be replaced by the archive file.

$f will be replaced by the file which should be packed into the archive.

This statement can be repeated.

See also hpt and htick documentation.

Note

On some OSes, if a program called can't be found (can't be run) result of pack command is undefined. (Example: DOS. Reason of this: command.com does not return error code if executable file was not found.) To prevent danger write full path name for packer program, please.


Node: unpack, Next: , Previous: pack, Up: Keywords

Unpack

Syntax:
Unpack "<call>" <offset> <matchcode>
Example for DOS:
          Unpack  "c:\arc\pkunpak /r $a $p $f"                 0 1a
          Unpack  "c:\arc\pak e /wn $a $p"                    -2 fe
          Unpack  "c:\arc\lha e /m $a $p $f"                   2 2d6c68
          Unpack  "c:\arc\zoo e:O $a $p $f"                    0 5a4f4f
          Unpack  "c:\arc\jar e -y $a $p $f"                  14 1a4a61721b
          # *.rar
          Unpack  "c:\arc\unrar e -y -c- -o+ -inul $a $p $f"   0 52617221
          # rar-sfx/DOS
          Unpack  "c:\arc\unrar e -y -c- -o+ -inul $a $p $f"  28 52534658
          
          

Example for Linux:
          Unpack  "/usr/bin/zoo e:O $a $p $f"                    0 5a4f4f
          Unpack  "/usr/bin/arc eno $a $p'*.*' $f"               0 1a
          Unpack  "/usr/bin/unzip -joLqq $a -d $p $f"            0 504b0304
          Unpack  "cd $p && /usr/bin/unarj e $a $f>/dev/null"    0 60ea
          Unpack  "/usr/bin/unrar e -y -c- -o+ -inul $a $p $f"   0 52617221
          Unpack  "/usr/bin/unrar e -y -c- -o+ -inul $a $p $f"  28 52534658
          Unpack  "/usr/bin/jar e -y $a $p $f"                  14 1a4a61721b
          Unpack  "cd $p && /usr/bin/ha eyq -e $a $f"            0 4841
          

This statement sets the call of certain unpackers according to the id in the archive file

call is the command line call for the packer (enclosed into quotes!);

offset position of recognition string in packed file;

match code hexdump of the recognition string for packed file, ?? can be used as any byte;

$a will be replaced by the archive file to extract from archive;

$p will be replaced by the path to unpacked files (usually tempoutbound);

$f will be replaced by the description file name if any (used by htick, see 'FileDescName' token; possibly other husky programs).

     
     e.g.: unpack "unzip -joLqq $a -d $p $f" 0 504b0304
     
            files packed by zip can be recognized by
              504b0304(hex) at offset 0(integer)
            they can be unpacked by htick using command
            "unzip -joLqq <filename> -d <path> <descrption_filename>"
     
     

This statement can be repeated.

Also see hpt and htick documentation.

Note

On some OSes, if a program called can't be found (can't be run) result of unpack command is undefined. (Example: MS DOS. Reason of this: command.com does not return error code if executable file was not found.) To prevent danger write full path name for unpacker program, please.


Node: link, Next: , Previous: unpack, Up: Keywords

link

Syntax:
link <string>
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.


Node: linkdefaults, Next: , Previous: link, Up: Keywords

linkdefaults

Syntax:
linkdefaults [begin | end | destroy]
Example:
linkdefaults

This statement starts section of default definitions of links. All the following link-related statements change default configuration of link until a 'link' or 'linkdefaults end' or 'linkdefaults destroy' statement is found. All parameters collected in linkdefaults sections are copied to link configuration every time when 'link' statement is found in configuration file. Link-related statements after 'linkdefaults end' or 'linkdefaults destroy' or before first 'link' or 'linkdefaults' statement are treated as error. 'linkdefaults' statement without 'begin' or 'end' means 'linkdefaults begin' 'linkdefaults destroy' destroys all default definitions.

Be careful with Pause, Export, etc. ;-)

This statement can be repeated. New definitions overwrite old ones.


Node: aka, Next: , Previous: linkdefaults, Up: Keywords

aka

Syntax:
aka <addr>
Example:
aka 2:2433/1245

This statement sets the aka for the current link.

This statement can only be repeated for different links.


Node: ouraka, Next: , Previous: aka, Up: Keywords

ouraka

Syntax:
ouraka <addr>
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.


Node: password, Next: , Previous: ouraka, Up: Keywords

password

Syntax:
password [<string>]
Example:
password secret

This statement sets the default password for the link. If you do not change the other passwords, they are set to this password.

This statement can only be repeated for different links.


Node: pktpwd, Next: , Previous: password, Up: Keywords

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.


Node: ticpwd, Next: , Previous: pktpwd, Up: Keywords

ticpwd

Syntax:
ticpwd [<string>]
Example:
ticpwd geheim

This statement sets the ticker 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.


Node: areafixpwd, Next: , Previous: ticpwd, Up: Keywords

areafixpwd

Syntax:
areafixpwd [<string>]
Example:
areafixpwd geheim

This statement sets the areafix password for the actual link. An empty statement is allowed, but not recommended.

This statement can only be repeated for different links.


Node: filefixpwd, Next: , Previous: areafixpwd, Up: Keywords

filefixpwd

Syntax:
filefixpwd [<string>]
Example:
filefixpwd geheim

This statement sets the filefix password for the actual link. An empty statement is allowed, but not recommended.

This statement can only be repeated for different links.


Node: bbspwd, Next: , Previous: filefixpwd, Up: Keywords

bbspwd

Syntax:
bbspwd [<string>]
Example:
bbspwd geheim

This statement sets the bbs password for the actual link. An empty statement is allowed.

This statement can only be repeated for different links.


Node: sessionpwd, Next: , Previous: bbspwd, Up: Keywords

sessionpwd

Syntax:
sessionpwd [<string>]
Example:
sessionpwd geheim

This statement sets the session password for the actual link. An empty statement is allowed.

This statement can only be repeated for different links.


Node: handle, Next: , Previous: sessionpwd, Up: Keywords

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.


Node: packer, Next: , Previous: handle, Up: Keywords

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 or set packer none no mail will be packed. The pkts will be put in the outbound.

This statement can only be repeated for different links.


Node: badarea, Next: , Previous: packer, Up: Keywords

badarea

Syntax:
BadArea <name> <file> [-b <msgbase>] [Options]
Example:
BadArea badarea /var/spool/fido/msgb/bad -b Squish

This statement specifies the BadArea. Read HPT documentation for details.

This statement cannot be repeated.


Node: dupearea, Next: , Previous: badarea, Up: Keywords

dupearea

Syntax:
dupeArea <name> <file> [-b <msgbase>] [Options]
Example:
dupeArea dupeArea /var/spool/fido/msgb/dupes -b Squish

This statement specifies the DupeArea. Read HPT documentation for details.

This statement cannot be repeated.


Node: echoarea, Next: , Previous: dupearea, Up: Keywords

echoarea

Syntax:
EchoArea <name> <file> [-b <msgbase>] [Options] [linkAKAs] [linkOptions]
Example:
EchoArea linux.develop.ger /var/spool/fido/msgb/linux.develop.ger -b Squish -a 2:2433/1247 -g A -dupeCheck move -dupehistory 11 -d "Linux development" 2:2433/1245 -def

This statement specifies the echoarea. Read HPT documentation for details.

This statement can be repeated.


Node: netmailarea, Next: , Previous: echoarea, Up: Keywords

netmailarea

Syntax:
NetmailArea <name> <file> [-b <msgbase>] [Options]
Example:
NetmailArea netmail /var/spool/fido/msgb/netmail -b Squish

This statement specifies the NetMailArea. Read HPT documentation for details.

This statement can be repeated.


Node: localarea, Next: , Previous: netmailarea, Up: Keywords

localarea

Syntax:
LocalArea <name> <file> [-b <msgbase>] [Options]
Example:
LocalArea MyBBSarea /var/spool/fido/msgb/MyBBS -b Squish

This statement specifies the LocalArea: messages area in BBS. Read HPT documentation for details.


Node: filearea, Next: , Previous: localarea, Up: Keywords

filearea

Syntax:
FileArea <name> <fileareapath> <uplink> [options] [<downlinks>]
Example:
filearea Photoes /var/spool/fido/fileecho/Photoes 2:50/1 -d "Sysop photoes"

This statement specifies the FileArea: fileecho definition. Read HTick documentation for details.


Node: bbsarea, Previous: filearea, Up: Keywords

bbsarea

Syntax:
bbsarea <name> <bbsareapath>
Example:
BBSarea Incoming /var/spool/fido/BBS/incoming

This statement specifies the BBSArea: BBS file area definition. It's used for filelist building. Read HTick documentation for details.


Node: HPT, Next: , Previous: Keywords, Up: config file

Highly Portable Tosser keywords

This section contains keyword-list only. Read HPT Manual for more info.


     accessgrp
     address
     addtoseen
     advancedareafix
     advisorylock
     afterunpack
     aka
     allowemptypktpwd
     allowpktaddrdiffer
     arcmailsize
     arcnetmail
     areafix
     areafixecholimit
     areafixfrompkt
     areafixhelp
     areafixReportsAttr
     areafixkillrequests
     areafixmsgsize
     areafixnames
     areafixorigin
     areafixpwd
     areafixqueryreports
     areafixqueuefile
     areafixsplitstr
     areafixfromname
     areasfilenamecase
     areasmaxdupeage
     autoareacreate
     autoareacreatedefaults
     autoareacreatefile
     autoareacreateflag
     autoareacreatesubdirs
     autopassive
     autopause
     availlist
     badarea
     beforepack
     bundlenamestyle
     carbonaddr
     carbonandquit
     carboncopy
     carbondelete
     carbonexcludefwdfrom
     carbonextern
     carbonfrom
     carbonfromarea
     carbongroups
     carbonkeepsb
     carbonkludge
     carbonmove
     carbonout
     carbonreason
     carbonrule
     carbonsubj
     carbontext
     carbonto
     createareascase
     createfwdnonpass
     defarcmailsize
     denyfwdfile
     denyfwdmask
     denyfwdreqaccess
     denyuncondfwdreqaccess
     disabletid
     disablepid
     dupearea
     dupebasetype
     dupehistorydir
     echoarea
     echoareadefaults
     echomailflavour
     echotosslog
     excludepassthroughcarbon
     export
     filebox
     fileboxalways
     fileboxesdir
     forwardareapriority
     forwardpkts
     forwardrequestfile
     forwardrequestmask
     forwardrequests
     forwardrequesttimeout
     hptperlfile
     idlepassthrutimeout
     ignorecapword
     ignoreseen
     import
     importlog
     inbound
     include
     intab
     keeptrsfiles
     keeptrsmail
     killedrequesttimeout
     kludgeareanetmail
     level
     link
     linkbundlenamestyle
     linkdefaults
     linkfilebasedir
     linkgrp
     linkmsgbasedir
     linkwithimportlog
     localarea
     localinbound
     lockfile
     logechotoscreen
     mandatory
     mindiskfreespace
     msgbasedir
     name
     netarea
     netmailarea
     netmailextern
     netmailflag
     newarearefusefile
     noprocessbundles
     norules
     notvalidfilenamechars
     optgrp
     origin
     ouraka
     outbound
     outtab
     pack
     packaka
     packer
     packnetmailonscan
     password
     pause
     pktpwd
     pktsize
     processpkt
     protinbound
     publicgroup
     readonly
     reducedseenby
     remap
     remoterobotname
     reportto
     robotsarea
     route
     routefile
     routemail
     rulesdir
     separatebundles
     setconsoletitle
     statlog
     sysop
     tearline
     tempinbound
     tempoutbound
     tossingext
     unpack
     writeonly
     


Node: HTick, Next: , Previous: HPT, Up: config file

HTick (Husky Ticker) keywords

This section contains keyword-list only. Read HTick Manual for more info.


     AddDLC
     AnnAreaTag
     AnnAddrfrom
     AnnAddrto
     AnnExclude
     AnnFileOrigin
     AnnFileRFrom
     AnnFrom
     AnnInclude
     AnnMessFlags
     AnnOrigin
     AnnounceSpool
     AnnSubj
     AnnTo
     AutoFileCreateFlag
     BbsArea
     BusyFileDir
     ConvertLongNames
     ConvertShortNames
     DLCDigits
     ExecOnFile
     FileArea
     FileAreaBaseDir
     FileAreaCreatePerms
     FileDescPos
     FileAreaDefaults
     FileDescName
     FileEchoFlavour
     FileLDescString
     FileFixFromName
     FileFixHelp
     FileFixReportsAttr
     FileFixKillRequests
     FileFixNames
     MaxTicLineLength
     OriginInAnnounce (obsoleted)
     PassFileAreaDir
     RemoteFileRobotName
     SaveTic
     TicOutbound
     
      In Link section:
       AutoFileCreate
       AutoFileCreateDefaults
       AutoFileCreateFile
       AutoFileCreateSubdirs
       DelNotRecievedTIC
       FileFixEchoLimit
       FileFixFSC87Subset
       ForwardFilePriority
       ForwardFileRequestFile
       ForwardFileRequests
       NoTIC
       LinkFileBaseDir
       PackAka
       TickerPackToBox
     


Node: NLTools, Next: , Previous: HTick, Up: config file

NLTools keywords


Node: nodelistdir, Next: , Previous: NLTools, Up: NLTools

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 (see nodelist). Also, compiled nodelists like the FIDOUSER.LST will be stored here.

This statement cannot be repeated.


Node: fidouserlist, Next: , Previous: nodelistdir, Up: NLTools

fidoUserList

Syntax:
fidoUserList <filename>
Example:
fidoUserList fidouser.lst

If this keyword is present, the nodelist compiler (e.g. ulc) is instructed to build a user list file with the given filename in the nodelist directory (see nodelistdir). This is a simple text file with fixed line length that contains user names (nodes, points) and their corresponding node or pointnumbers. The file is sorted alphabetically by user name (case insensitive), so that it can be bsearched to implement a quick node numer lookup functinality. The fido user list file format is understood by msged, for example.


Node: nodelist, Next: , Previous: fidouserlist, Up: NLTools

nodelist

Syntax:
Nodelist <name>
Example:
Nodelist nodelist or Nodelist points24

This statement starts a new nodelist definition. All the following nodelist-related stamtements change the configuration of this nodelist until a new nodelist statement is found.

The name that you specify must match the base name (without extension and without pathname) of the raw, unpacked, nodelist file. The husky tools ulc and nlupdate math the file name case-insensitively, but other tools may need the exact spelling. The raw nodelist file is expected to reside in the nodelist directory (see nodelistdir).


Node: diffupdate, Next: , Previous: nodelist, Up: NLTools

diffupdate

Syntax:
DiffUpdate <path_and_basname>
Example:
DiffUpdate /var/spool/filebase/nodediff/nodediff

Here you can specify the base filename of nodelist difference files (nodediffs) that are used to keep the corresponding nodelist up to date. The argument to the DiffUpdate is the full file name with path of a difference file, without the file extension. For example, if you have a file area at /var/spool/filebase/24000, where your ticker places the updates for the German Pointlist, and those update files are called points24.a26, points24.a33, and so on, you would use

     DiffUpdate /var/spool/filebase/24000/points24
     

The Diffupdate keyword is used by nlupdate, for example. The nodelist updater will unpack the difference file (if it is archived, of course, unpacked diffs are also supported), apply the diff to the corresponding nodelist, and delete the temporary unpacked diff again.


Node: fullupdate, Next: , Previous: diffupdate, Up: NLTools

fullupdate

Syntax:
FullUpdate <path_and_basname>
Example:
FullUpdate /var/spool/filebase/nodelist/nodelist

This statement works like DiffUpdate (see diffupdate). The difference is that here you don't specify the location of a nodelist difference file, but the locations where complete nodelist files/archives can be found. Some othernets do not (regularly) distribute a nodediff file, but just hatch a new nodelist every few weeks. In this case, you need the FullUpdate statement.


Node: defaultzone, Next: , Previous: fullupdate, Up: NLTools

defaultzone

Syntax:
DefaultZone <zone>
Example:
DefaultZone 2

Some nodelist files do not start with a Zone entry. This is the case for the German Points24 list, for example, but could also happen for othernets that only have one zone. In this case, you can use the DefaultZone keyword to specify the default zone number for all nodes listed in this nodelist.


Node: nodelistformat, Previous: defaultzone, Up: NLTools

nodelistformat

Syntax:
Nodelistformat <format>
Example:
NodelistFormat standard or NodelistFormat Points24

Here you can specify the format of the unpacked nodelist. The default is standard; this is the normal Fidonet nodelist format. You can also specify points24, which is needed for the nodelist compiler to recognise a point list in the German points24 format as such, so that it can see the proper 5D point numbers instead of the fakenet numbers.


Node: EmailPkt, Next: , Previous: NLTools, Up: config file

EmailPkt keywords

Common tokens:


Node: sendMailCmd, Next: , Previous: EmailPkt, Up: EmailPkt

email

Syntax:
sendMailCmd string
Example:
sendMailCmd /usr/sbin/sendmail $a <$f

This keyword is used to define send mail command & its parameters. Macro '$a' specifies position of the recipient e-mail address; macro '$f' specifies position of name of file with message body. If '$f' is omitted then message body will be taken from stdin.

This statement can't be repeated.


Node: email, Next: , Previous: sendMailCmd, Up: EmailPkt

email

Syntax:
email <email-address>
Example:
email eddie@ironmaiden.com

This keyword is used to set the email-address for the link. This can be used to send pkts via email.

This statement can only be repeated for different links.


Node: emailFrom, Next: , Previous: email, Up: EmailPkt

emailFrom

Syntax:
emailFrom <email-address>
Example:
emailFrom fred@ironmaiden.com

This keyword is used to set the email-address used as sender address for outgoing emails to this link.

This statement can only be repeated for different links.


Node: emailSubj, Next: , Previous: emailFrom, Up: EmailPkt

emailSubj

Syntax:
emailSubj <subject>
Example:
emailSubj Fido over EMail message in UUE format

This keyword is used to set the subject for emails to and from this link. It may be ignored by some encodings (e.g. SEAT).

This statement can only be repeated for different links.


Node: emailEncoding, Previous: emailSubj, Up: EmailPkt

email

Syntax:
emailEncoding (MIME | SEAT | UUE)
Example:
emailEncoding MIME

This keyword is used to set the encoding for outgoing emails to this link.

This statement can only be repeated for different links.


Node: BSOpack, Next: , Previous: EmailPkt, Up: config file

BSOpack keywords

This section contains keyword-list only. Read BsoPack Manual for more info.


     maxunpackednetmail
     packnetmail
     


Node: herp, Next: , Previous: BSOpack, Up: config file

herp keywords

Herp is the Husky External file Request Processor. The following fidoconfig keywords are specific to herp. Some programs of herp, in particular herpidx, also use part of the htick configuration, i.E. filearea definitions.


Node: reqidxdir, Previous: herp, Up: herp

reqidxdir

Syntax:
reqidxDir <path>
Example:
reqidxDir /var/spool/fido/reqidx

This command specifies a subdirectory which will be used to store the request index generated by herpidx. This subdirectory should be writable for the herpidx process and at least readable for the user under which your mailer and herp will be run. herpidx will place various request index files here. The subdirectory should not be used for any other purposes. The index can become rather large, so plan for enough free disk space.


Node: Example, Previous: herp, Up: config file

Working sample config


     # sample fido config file
     
     
     version 0.14 # test for new stripComment
     Name hpt-HQ
     Location Paderborn, GER
     Sysop Matthias Tichy
     
     LogLevels 456789
     
     Address 2:2432/645
     Address 44:4932/110
     Address 21:499/976
     Address 49:199/976
     Address 54:490/976
     Address 64:199/976
     Address 530:199/976
     
     # This is taken from Serge Koghin's ParToss
     # Hope he wouldn't be angry for this
     # ATTENTION the commented lines are not tested by me (mtt)
     # and will mostly be only useful on dos-systems
     
     Unpack  "unzip  -j -Loqq $a -d $p" 0 504b0304
     Unpack "\path\pkzipc -ext -dir=none -over=all -nozip -silent $a $p $f" 0 504b0304
     #Unpack "pkunzip -njCL $a -d $p $f" 0 504b0304
     #Unpack "pkzip25 -ext -silent -over=all -nofix -nozip $a $p $f" 0 504b0304
     Pack  zip zip -9 -j -q $a $f
     
     Unpack  "arc eno $a $p'*.*'" 0 1a
     
     #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
     # Unpack  "cd $p && /usr/bin/unarj e $a > /dev/null" 0 60ea # for Linux
     #Pack  arj arj a -+ -e -y $a $f
     
     # *.rar
     Unpack  "unrar e -y -c- -inul $a $p $f"   0 52617221
     # rar-sfx/DOS
     Unpack "unrar e -y -c- -inul $a $p $f" 28 52534658
     #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/600
     ourAka 2:2432/645
     Password xxxxxxxxx
     EchoMailFlavour Crash
     AutoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     AutoFileCreate on
     forwardRequests on
     Packer zip
     
     Link Matthias Schniedermeyer
     Aka 44:4932/100
     ourAka 44:4932/110
     password xxxxxxxx
     EchoMailFlavour Crash
     AutoAreaCreate on
     AutoFileCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     Packer zip
     
     Link Carsten Ellermann
     Aka 2:2432/215
     ourAka 2:2432/645
     password xxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     autoFileCreate on
     
     Link Matthias Tichy
     Aka 2:2432/646
     ourAka 2:2432/645
     Password xxxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Tichy
     Aka 21:499/980
     ourAka 21:499/976
     Password xxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Tichy
     Aka 49:199/980
     ourAka 49:199/976
     Password xxxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Tichy
     Aka 54:490/980
     ourAka 54:490/976
     Password xxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Tichy
     Aka 64:199/980
     ourAka 64:199/976
     Password xxxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Tichy
     Aka 530:199/980
     ourAka 530:199/976
     Password xxxxxxxx
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     forwardPkts on
     
     Link Matthias Born
     Aka 2:240/6223
     ourAka 2:2432/645
     Password xxxxxxx
     EchoMailFlavour hold
     Packer zip
     
     Link Matthias Born
     Aka 44:4932/120
     ourAka 44:4932/110
     Password xxxxxxx
     EchoMailFlavour hold
     Packer zip
     
     Link Sascha Silbe
     Aka 2:2435/424
     ourAka 2:2432/645
     AutoFileCreate on
     Password xxxxxxxx
     
     Link Sascha Silbe
     Aka 54:490/963
     ourAka 54:490/976
     AutoFileCreate on
     Password xxxxxxxxx
     
     Link Alfred Cleve
     Aka 2:244/6260
     ourAka 2:2432/645
     password xxxxxxxxxxx
     packer zip
     EchoMailFlavour crash
     autoAreaCreate on
     AutoAreaCreateDefaults -p 14 -dupeCheck move -dupeHistory 11
     
     ; +++ FREEPNT-MARKE +++
     
     #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 hold noroute 2:2432/645.*
     route hold noroute 2:240/6223.*
     route crash noroute 2:2432/646
     route hold 44:4932/120 44:4932/120 44:4932/130
     Route crash 44:4932/100 44:*
     Route crash 49:199/980 49:*
     Route crash 54:490/980 54:*
     Route crash 530:199/980 530:*
     
     Route normal 2:2435/424 2:2435/*
     
     Route crash 2:2432/646 *
     
     Inbound		/home/mtt/fido/in/
     ProtInbound	/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
     FileAreaBaseDir /home/mtt/fido/files
     
     public		/home/mtt/fido/public
     # public		/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/fido/hpt/linux
     DupeHistoryDir	/home/mtt/fido/dupes
     NodelistDir	/home/mtt/fido/nodelist
     PassFileAreaDir     /home/mtt/fido/passFileDir
     magic		/home/mtt/fido/magic
     lockfile        /home/mtt/fido/lock
     
     areafixhelp     /home/mtt/fido/hpt/misc/areafix.hlp
     FileFixHelp     /home/mtt/fido/htick/misc/filefix.hlp
     
     AreafixReportsAttr loc pvt k/s npd dir
     FilefixReportsAttr loc pvt k/s npd dir
     
     NodeList nodelist
     DiffUpdate /home/mtt/fido/files/nodediff
     NodeList unionnet
     Nodelist geonode
     Nodelist linuxnet
     DiffUpdate /home/mtt/fido/files/lin44.node
     
     NetmailArea NetmailArea /home/mtt/fido/msgb/netmail -b msg
     # NetmailArea NetmailArea /home/mtt/fido/msgb/net -b  Squish
     BadArea     BadArea     /home/mtt/fido/msgb/bad -b Squish
     DupeArea    DupeArea    /home/mtt/fido/msgb/dupe -b Squish
     
     EchoArea 2432.points      /home/mtt/fido/msgb/2432/points       -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea 2432.Talk        /home/mtt/fido/msgb/2432/talk         -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea C_ECHO.ger       /home/mtt/fido/msgb/c_echo_g          -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea C_PLUSPLUS.ger   /home/mtt/fido/msgb/c_plpl_g          -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea binkley          /home/mtt/fido/msgb/binkley           -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea Binkley.ger      /home/mtt/fido/msgb/binkley_g         -a 2:2432/645  -b  Squish -p 14 2:2432/600
     EchoArea hardrock.ger     /home/mtt/fido/msgb/hardrock_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea   linux.ger        /home/mtt/fido/msgb/linux/ger           -a 2:2432/645  -b Squish -p 14 -dupecheck move -dupeHistory 11  2:2432/646
     echoArea linux.develop.ger /home/mtt/fido/msgb/linux/develop_g   -a 2:2432/645 -b Squish  -dupeCheck move -dupeHistory 11  2:2432/646
     EchoArea os2.base.ger     /home/mtt/fido/msgb/os2/base_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.beta.ger     /home/mtt/fido/msgb/os2/beta_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2bbs.ger       /home/mtt/fido/msgb/os2/bbs_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.debate.ger   /home/mtt/fido/msgb/os2/debate_g      -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.install.ger  /home/mtt/fido/msgb/os2/install_g     -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea Os2.wps.ger      /home/mtt/fido/msgb/os2/wps_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea Os2.prog.ger     /home/mtt/fido/msgb/os2/prog_g        -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea Os2.lan.ger      /home/mtt/fido/msgb/os2/lan_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.hw.ger       /home/mtt/fido/msgb/os2/hw_g          -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.online.ger   /home/mtt/fido/msgb/os2/online_g      -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea os2.tec.ger      /home/mtt/fido/msgb/os2/tec_g         -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea OWL.Newfiles     /home/mtt/fido/msgb/owl/newfiles      -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea owl.announce     /home/mtt/fido/msgb/owl/announce      -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea owl.flea         /home/mtt/fido/msgb/owl/flea          -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea owlserver.news   /home/mtt/fido/msgb/owl/snews         -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea Paderborn.Flohmarkt  /home/mtt/fido/msgb/pader/floh    -a 2:2432/645  -b Squish -p 14 2:2432/600
     EchoArea Tolkien.ger      /home/mtt/fido/msgb/tolkien_g         -a 2:2432/645  -b Squish -dupeCheck move -p 14 2:2432/600
     EchoArea Schweden.ger     /home/mtt/fido/msgb/schweden_g        -a 2:2432/645  -b Squish -tinySB -p 14 2:2432/600
     
     LocalArea carbonArea       /home/mtt/fido/msgb/carbonArea  -b Squish
     
     CarbonTo Matthias Tichy
     CarbonCopy carbonArea
     
     EchoArea paderborn.mailbox /home/mtt/fido/msgb/paderborn.mailbox -a 2:2432/645 -b  Squish -dupeCheck move -dupeHistory 11 -p 14 2:2432/600
     EchoArea owl.allfix /home/mtt/fido/msgb/owl.allfix -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea fidosoft.winpoint.ger /home/mtt/fido/msgb/fidosoft.winpoint.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea net_dev.ger /home/mtt/fido/msgb/net_dev.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea net_dev /home/mtt/fido/msgb/net_dev -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea fidosoft.ger /home/mtt/fido/msgb/fidosoft.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea linux.bbs /home/mtt/fido/msgb/linux.bbs -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.software /home/mtt/fido/msgb/linux.software -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.setup /home/mtt/fido/msgb/linux.setup -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.reg /home/mtt/fido/msgb/linux.reg -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea linux.netzwerk /home/mtt/fido/msgb/linux.netzwerk -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.announce /home/mtt/fido/msgb/linux.announce -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.hardware /home/mtt/fido/msgb/linux.hardware -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea darkness.info /home/mtt/fido/msgb/darkness.info -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  2:2432/600
     EchoArea linux.coord /home/mtt/fido/msgb/linux.coord -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea 2432.nodes.info /home/mtt/fido/msgb/2432.nodes.info -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea linux.office /home/mtt/fido/msgb/linux.office -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea linux.develop /home/mtt/fido/msgb/linux.develop -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  44:4932/100
     EchoArea linux.x /home/mtt/fido/msgb/linux.x -a 44:4932/110 -b  Squish -p 14 -dupeCheck move -dupeHistory 11  44:4932/100
     EchoArea 2432.nodes /home/mtt/fido/msgb/2432.nodes -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea fido2000.ger /home/mtt/fido/msgb/fido2000.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea java.ger /home/mtt/fido/msgb/java.ger -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea ftsc_public /home/mtt/fido/msgb/ftsc_public -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/646
     EchoArea BINKLEY.DEVELOP /home/mtt/fido/msgb/binkley.develop -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/215
     
     FileArea binkley.dev /home/mtt/fido/files/binkley.dev -a 2:2432/645  -d "Binkleyterm Development: Source Diffs, Misc, stuff" 2:2432/215
     FileArea btxebos2 /home/mtt/fido/files/btxebos2 -a 2:2432/645  -d "Binkleyterm Development: Beta Binaries for OS/2" 2:2432/215
     FileArea btxebsrc /home/mtt/fido/files/btxebsrc -a 2:2432/645  -d "Binkleyterm Development: Beta Source" 2:2432/215
     FileArea btxebw32 /home/mtt/fido/files/btxebw32 -a 2:2432/645  -d "Binkleyterm Development: Beta Binaries for Win32" 2:2432/215
     EchoArea golded.ger /home/mtt/fido/msgb/golded.ger -b Squish -a 2:2432/645 -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea fidosoft.husky /home/mtt/fido/msgb/fidosoft.husky -b Squish -a 2:2432/645 -dupeCheck move -dupeHistory 11 2:2432/646 2:240/6223
     EchoArea darkness.points /home/mtt/fido/msgb/darkness.points -a 2:2432/645 -b  Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea linux.fido.ger /home/mtt/fido/msgb/linux.fido.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/646
     EchoArea FUSSBALL.GER /home/mtt/fido/msgb/fussball.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea PGP.GER /home/mtt/fido/msgb/pgp.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea HARDWARE.SCSI.GER /home/mtt/fido/msgb/hardware.scsi.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea TV.GER /home/mtt/fido/msgb/tv.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea CDWRITER.GER /home/mtt/fido/msgb/cdwriter.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea FASTECHO.GER /home/mtt/fido/msgb/fastecho.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea URTEILE.GER /home/mtt/fido/msgb/urteile.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea PRO_WRESTLING /home/mtt/fido/msgb/pro_wrestling -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea SPORT.EISHOCKEY.GER /home/mtt/fido/msgb/sport.eishockey.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea RAETSEL.GER /home/mtt/fido/msgb/raetsel.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea WRESTLING.GER /home/mtt/fido/msgb/wrestling.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea JAZZ.GER /home/mtt/fido/msgb/jazz.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea TV.SITCOM.GER /home/mtt/fido/msgb/tv.sitcom.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea FAEKAL.GER /home/mtt/fido/msgb/faekal.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea STEUER.GER /home/mtt/fido/msgb/steuer.ger -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/600
     EchoArea LINUX.TALK /home/mtt/fido/msgb/linux.talk -a 44:4932/110 -b Squish -p 14 -dupeCheck move -dupeHistory 11 44:4932/100
     EchoArea LINUX /home/mtt/fido/msgb/linux -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/646 2:240/6223
     EchoArea FTN.BACKBONE.INFO /home/mtt/fido/msgb/ftn.backbone.info -a 2:2432/645 -b Squish -p 14 -dupeCheck move -dupeHistory 11 2:2432/646
     FileArea 24000 /home/mtt/fido/files/24000 -a 2:2432/645  2:2432/600
     FileArea NODEDIFF /home/mtt/fido/files/nodediff -a 2:2432/645  2:2432/600
     FileArea LIN44.NODE /home/mtt/fido/files/lin44.node -a 44:4932/110  44:4932/100
     FileArea LIN44.POINT /home/mtt/fido/files/lin44.point -a 44:4932/110  44:4932/100
     EchoArea GN.ALLGEMEIN /home/mtt/fido/msgb/gn.allgemein -a 54:490/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 54:490/980
     EchoArea GN.ANNOUNCE /home/mtt/fido/msgb/gn.announce -a 54:490/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 54:490/980
     EchoArea SN.GEW.IGMEDIEN.ALLG /home/mtt/fido/msgb/sn.gew.igmedien.allg -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.RECHT.ARB.URTEILE /home/mtt/fido/msgb/sn.recht.arb.urteile -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.RECHT.SOZ.DISKUSSION /home/mtt/fido/msgb/sn.recht.soz.diskussion -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.RECHT.ARB.DISKUSSION /home/mtt/fido/msgb/sn.recht.arb.diskussion -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.BETR.BR+PR /home/mtt/fido/msgb/sn.betr.br+pr -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.BETR.VEREINBARUNGEN /home/mtt/fido/msgb/sn.betr.vereinbarungen -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea GN.CLUBS /home/mtt/fido/msgb/gn.clubs -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.KOO.VORSTELLUNG /home/mtt/fido/msgb/sn.koo.vorstellung -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.ALLGEMEIN /home/mtt/fido/msgb/sn.gew.allgemein -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.AKTUELL.TERMINE /home/mtt/fido/msgb/sn.aktuell.termine -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.KOO.TEST /home/mtt/fido/msgb/sn.koo.test -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.GHK /home/mtt/fido/msgb/sn.gew.ghk -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.AKTUELL.AKTIONEN /home/mtt/fido/msgb/sn.aktuell.aktionen -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.BETR.BILDUNG /home/mtt/fido/msgb/sn.betr.bildung -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.INTERNATIONAL /home/mtt/fido/msgb/sn.gew.international -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.KOO.DISKUSSION /home/mtt/fido/msgb/sn.koo.diskussion -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.HBV /home/mtt/fido/msgb/sn.gew.hbv -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.IGMETALL /home/mtt/fido/msgb/sn.gew.igmetall -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.JUGEND /home/mtt/fido/msgb/sn.gew.jugend -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea GN.CBM /home/mtt/fido/msgb/gn.cbm -a 54:490/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 54:490/980
     EchoArea SN.KOO.WICHTIG /home/mtt/fido/msgb/sn.koo.wichtig -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.KOO.ANTRAEGE /home/mtt/fido/msgb/sn.koo.antraege -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.THESEN /home/mtt/fido/msgb/sn.gew.thesen -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.OETV /home/mtt/fido/msgb/sn.gew.oetv -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.FRAUEN /home/mtt/fido/msgb/sn.frauen -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.GEW.HBS /home/mtt/fido/msgb/sn.gew.hbs -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.ARB+SOZ.ALLGEMEIN /home/mtt/fido/msgb/sn.arb+soz.allgemein -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.AKTUELL.VORSCHAU /home/mtt/fido/msgb/sn.aktuell.vorschau -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.ARB+SOZ.ERWERBSLOS /home/mtt/fido/msgb/sn.arb+soz.erwerbslos -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.ARB+SOZ.DISKUSSION /home/mtt/fido/msgb/sn.arb+soz.diskussion -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.BETR.ARBSCHU+UMWELT /home/mtt/fido/msgb/sn.betr.arbschu+umwelt -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea SN.BETR.ARBEIT+TECHNIK /home/mtt/fido/msgb/sn.betr.arbeit+technik -a 49:199/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 49:199/980
     EchoArea GN.SYSOPS /home/mtt/fido/msgb/gn.sysops -a 54:490/976 -b Squish -p 14 -dupeCheck move -dupeHistory 11 54:490/980
     


Node: converting, Next: , Previous: config file, Up: Top

Converting fidoconfig to golded, msged and aquaed

Since original GoldEd by Odin Sorensen does not support fidoconfig at all and msged and aquaed only in beta versions, we have developed three programs that convert your fidoconfig to these proprietary config file formats.

  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
              


Node: tparser, Next: , Previous: converting, Up: Top

Testing the config

You should run tparser EVERYTIME you have changed the config. If tparser found error in config please correct your config file and try again.

Syntax:
tparser [-h|--help] [-Dvar=value] [-E] [-P] [/path/to/config/file]
Example:
          tparser -Dmodule=hpt | less
          

tparser (like any fidoconfig program) will display error messages if you have made an error in the config. It also may be display some warnings about your config settings. It will grumble on every Keyword it does not know. It will stop after the first error (not warning) to give you the ability to change your config.

Options

-Dvar=value
Set the config variable var to value.
-E
Dumps config into stdout (all config variables expanded).
-h
--help
Display usage information.
-P
Try to create non-existing directories.


Node: contact, Previous: tparser, Up: Top

Contacting the author

You can reach me at

     mtt@tichy.de
     2:2432/645
     

and in the fido echoarea

     linux.develop.ger
     fidosoft.husky
     

Max Levenkov:

     sackett@mail.ru
     ru.husky (russian)
     ru.echoprocessors (russian)
     fidosoft.husky (english)
     

The actual fidoconfig library and other fido software will be on <http://husky.sourceforge.net>.