; sysftn.txt
;
; This is the WaterGate help file
; This file is included by wtrgate.txt
;
; Contents: WtrConf System Config -> FTN
;

; quick reference:
;
; #topic(reference text)
; #subtopic(reference text)
; #end
; #title(text)
; Space at start of line or #linebreak
; Empty line or #break
; #link(reference)(text)
; #highlight(text) or #hl(text)

;===========================================================================
; System FTN Settings
;
#topic(System FTN Settings)
#title(FTN Settings)
This window contains all the FTN related settings. Some groups
of settings have been put together in a sub-window.

#subtopic(SysFTN Inbound)
#title(Inbound paths)
You can specify up to two directories where WaterGate will
look for arrived ("inbound") mail. These can be compressed
with most common archivers, or just plain .PKT files.

#subtopic(SysFTN Security)
#title(Inbound security)
Toggle this option to ON if you want WaterGate to check
passwords in arrived mail bundles (.PKT files). If set
to NO then no checking is done.

#subtopic(SysFTN Outbound)
#title(Outbound path)
Specify a directory where WaterGate will store its outgoing Fido mail-
bundles. WaterGate will refuse to operate if no directory is specified.

BinkleyTerm 2.50+ 5D outbound directories are fully supported
by WaterGate.

#subtopic(SysFTN Origin)
#title(System Origins)
An Origin line is added to every message exported from your local message
base that didn't have one already. They are also added to messages that
are converted from UUCP to FidoNet. You can assign a custom origin line
to every different message area, or choose one you have entered here.

If you enter: The Power of no imagination

WaterGate will export the following:

 * Origin: The Power of no imagination (2:512/17)

#subtopic(SysFTN Mailer type)
#title(Mailer type)
WaterGate currently supports #hl(Binkley), #hl(FrontDoor) and #hl(d'Bridge)
compatible mailers.

#hl(Binkley) uses an outbound directory tree with queue files
that decide the delivery flavour (normal, crash, etc.) and a list of
files to transport to that system.

#hl(FrontDoor) uses netmail messages from ARCmail with the destination
system in the To: field and the file to transport attached to the message.
The flags on the message decide the delivery flavour.
#linebreak
If you use a FrontDoor system then you are required to set the primary
netmail area type to *.MSG.

#hl(d'Bridge) uses a special queue path for outgoing files.

#subtopic(SysFTN DBridge queue)
#title(d'Bridge queue)
The #d'Bridge# queue path is used to store the general purpose
outbound queue files used by #d'Bridge# systems.

#subtopic(SysFTN Rescan files)
#title(Mailer and Editor rescan file)
The #Rescan flag files# are used to inform your mailer and editor
that new netmail messages were imported. By using the flag files
it is no longer required to scan the entire netmail area with
certain intervals.

WaterGate supports two different flag files: one for your mailer
and one for your editor. The first is set when a new file attach
was created and the other when a normal netmail message was created.

The #hl(Mailer rescan file) is usually one of the following:

 FrontDoor  FDRESCAN.NOW
 InterMail  IMRESCAN.NOW
 d'Bridge   DBRIDGE.RSN

The #hl(Editor rescan file) is FMRESCAN.NOW for FrontDoor's FM.EXE.
Other editors might look at the same flag file, or have their own.

#hl(Note:) You have to enter the complete path plus the filename.

#subtopic(SysFTN Maximum archive length)
#title(Maximum archive length)
Enter the maximum size for an outgoing ARCmail bundle for systems
not present under the User Definitions.

WaterGate checks the size of a bundle before it adds a .PKT file.
If it has reached or passed its limit, then a new ARCmail bundle
is started.

#subtopic(SysFTN ARCmail flag)
#title(ARCmail flag)
When your mailer has transmitted an archive, it can either
delete it completely or truncate the file to zero bytes.

Some tossers/mailers require the zero-length file when deciding
the next ARCmail extension to use. WaterGate administrates
this information internally and the mailer can thus delete
(kill) the file.

If you use WaterGate together with another tosser that
also creates archives, then keep this option at Truncate
(the default). Otherwise, set it to Kill and automatically
get rid of all those zero-byte archives in your outbound.

#subtopic(SysFTN ARCmail extensions)
#title(ARCmail extensions)
Select the range of archive file extensions that WaterGate will
accept for incoming Fido mail archives, and use when creating
outgoing mail archives.

 #hl(System      Range           Examples)
 ARCMAIL     0..9            *.WE0 .. *.WE9
 HEX         0..9 + A..F     *.WE0 .. *.WEF
 ALL         0..9 + A..Z     *.WE0 .. *.WEZ

Make sure your up and downlinks can accept the format you specify!

#subtopic(SysFTN Default archiver)
#title(Default archiver)
The default Fido compression program is used when creating a new
Fido user record, and when the program needs to compress a message
for an unknown node, for example when sending a crash netmail.
#end



;===========================================================================
; AreaFix Settings Editor
;
#topic(System Areafix Settings)
#title(Areafix Settings)
This window contains all the AreaFix related settings.

#subtopic(SysFTN AreaFix name)
#title(AreaFix name)
This system accepts AreaFix requests (from FidoNet style users) via this
username on one of this systems' AKAs. The name is case-insensitive.

#subtopic(SysFTN Kill after Areafix)
#title(Kill after AreaFix)
When set to Yes, this options helps you clean up your netmail
area.

When a point send a message to AreaFix via FrontDoor, the message
ends up in you primary netmail area and stays there unless it
has a Kill/Sent flag on it.

This option tells WaterGate to force this Kill/Sent flag on all
messages addressed to AreaFix at one of your system AKAs.

#subtopic(SysFTN Rescan Msgs Limit)
#title(Rescan messages limit)
This field defines how many message may be rescanned from an area
at once. If the user requests to rescan more messages, then this
setting will limit that. This is to limit the amount of data that
must be sent to the requesting user.

A value of zero means no limit. The maximum value that can be set
here is 65535 messages.

#subtopic(SysFTN Rescan Days Limit)
#title(Rescan days limit)
This field defines from how many days messages may be rescanned from
an area. If the user requests to rescan older messages, then this
setting will limit that. This is to limit the amount of data that
must be sent to your downlink.

A value of zero means no limit. The maximum value that can be set
here is 255 days.
#end

;===========================================================================
; System Node Number Editor
;
#topic(System Node Number Editor)
#title(System node number editor)
This help topic belongs to the window where you can edit a system node
number.

#subtopic(SysAkaEdit Node number)
#title(Node number)
An FTN address consists of at most 5 parts:

      zone:net/node.point@domain

Valid combinations are:              Examples:

      zone:net/node                   2:512/17
      zone:net/node@domain            2:512/17@fidonet.org
      zone:net/node.point@domain      2:512/17.6@fidonet.org

#subtopic(SysAkaEdit Point net)
#title(Point net)
For compatibility with older FidoNet Technology programs that don't
understand points, you can optionally specify a fakenet. For example
if you are 2:512/17, and specify 1017 as your fakenet, mail from 2:1017/6
is internally converted into 2:512/17.6

Please contact your network coordinator for information on your network's
policy on fakenet numbers.
#end

;---------------------------------------------------------------------------
; SysFTN System node numbers
;
#topic(SysFTN System node numbers)
#title(System Node Numbers)
A FidoNet address consists of at most 5 parts :

      zone:net/node.point@domain

Valid combinations are:              Examples:

      zone:net/node.point@domain      2:512/17.6@fidonet.org
      zone:net/node@domain            2:512/17@fidonet.org
      zone:net/node                   2:512/17

For compatibility with older FidoNet Technology programs that don't
understand points, you can optionally specify a fakenet. For example
if you are 2:512/17, and specify 1017 as your fakenet, mail from 2:1017/6
is internally converted into 2:512/17.6

Please contact your network coordinator for information on your network's
policy on fakenet numbers.
#end


;---------------------------------------------------------------------------
; SysFTN System node numbers usage
;
#topic(SysFTN System node numbers usage)
#title(System node numbers usage)
This window shows where the system node numbers are used.

The Export AKA used in each of the user definitions is checked.
The Origin AKA and SEEN-BYs for each area definition are checked.
The groups in which these area definitions can be found are
reported instead of a list of the found areas.

Note that the ROUTE.TDB file is not checked. In addition, if the
export AKA is set to Automatic, the system node number can still
be used but WtrConf cannot detect this.
#end


;===========================================================================
; System FTN  Archivers
;
#topic(System FTN Archivers)
#title(FTN Archive Programs)
This topic is related to the Archivers Configuration in WtrConf
under System Configuration, FTN Settings.

#subtopic(SysFTN Archivers)
#title(Archivers)
When a fido mail bundle is received it is usually compressed.
WaterGate is capable of recognizing the ARC,ARJ,PAK,ZIP,LZH,ZOO
and RAR archive formats.

Specify the compression and decompression program and its
command line options you want to use for each format.

If you need a special compression program, then define it
under OP1 and select that archiver in the user record.

#subtopic(SysFTN Unpacking with GUS)
#title(Unpacking with GUS)
When WaterGate is unable to determine the archive format for a mail
bundle, it checks whether there is #hl(General Unpack Shell) defined.
If there is, it lets the GUS try to unpack the archive.
#end

; end of file sysftn.txt

