; sysrfc.txt
;
; This is the WaterGate help file
; This file is included by wtrgate.txt
;
; Contents: WtrConf System -> RFC Settings help
;

; 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)

;---------------------------------------------------------------------------
; SysRFC System domains
;
#topic(SysRFC System domains)
#title(System domain addresses)
Specify up to 6 domain names for your system, usually you should have
one domain address and some aka addresses.

Examples:
  powerline.network.nl
  powerline.station.network.nl

The first system domain is your primary system domain address and is
used by WaterGate to create automatic outbound address, for example
by the gateway.

Otherwise, all your users and WaterGate-internal systems can be reached
on all the domain addresses. WaterGate automatically chooses the
best matching domain address when responding to an external request.
For example, if you have two domain addresses netone.com and nettwo.com
and WaterGate sends a response to user@nettwo.com or user@sub.nettwo.com
then it will automatically use the nettwo.com domain instead of the
other domain.
#end


;---------------------------------------------------------------------------
; SysRFC UUCP Compression Programs
;
#topic(SysRFC UUCP Compression Programs)
#title(UUCP news bundle compression programs)
Specify the program you want to use to (de)compress UUCP news
bundles including the command-line options.
#end


;===========================================================================
; UUCP Settings Editor
;
#topic(SysRFC UUCP Settings Editor)
#title(UUCP Settings Editor)
This topic is related to the fields that can be changed in WtrConf
under System Configuration, RFC Settings, UUCP Settings.

#subtopic(SysRFCUUCP Spool directory)
#title(Spool directory)
The base directory for all your communications with other UUCP
compatible systems. For example, if your base directory is
@C:\BBS\SPOOL@, mail for the system PwrDial will be put in the
directory @C:\BBS\SPOOL\PWRDIAL@

#subtopic(SysRFCUUCP SpoolMode)
#title(Spool mode)
Select the type of spool directory you want to use: the good old
UUCP more or the alternative UUPC mode.

The setting must match the mode your UUCP mailer uses. If set
wrong, WtrGate cannot process received jobs and your mailer
cannot transmit the jobs created by WaterGate.

If your mailer uses UUCP mode, your spool directory contains
one sub-directory for each UUCP system you communicate with.
Received jobs will have the extensions .X and .D and outgoing
jobs will have the extensions .CMD, .XQT and .DAT.

If your mailer uses UUPC mode you will find additional sub-directories
named "X" and "D" under each UUCP system directory.

#subtopic(SysRFCUUCP UUCP name)
#title(UUCP name)
The UUCP name of your system, this name identifies your system
when messages are send using @bang path@ routing, and for
identifying spool-files.

Example:  Your systems UUCP name is PwrDial, and a message is
          send to @PwrDial!Jaap@, WaterGate will recognize
          its own address and imports the message for user Jaap.

#subtopic(SysRFCUUCP World registered)
#title(Word registered)
Toggle this option to ON if your system UUCP name is registered unique
over the entire world. Not that this is almost never used anymore
nowadays!! Only domain addresses are registered these days.

When this option is ON, your UUCPname is used in addresses instead of
your first system domain address.

Examples:  UUCPname="sun", first system domain address="sun.nluug.nl"

World registered UUCP name:
  From sun!ET.TUDelft.NL!M.vdLaan  Sun Nov 28 ....

Not world registered UUCP name:
  From sun.nluug.nl!ET.TUDelft.NL!M.vdLaan  Sun Nov 28 ....

#subtopic(SysRFCUUCP Maximum DAT length)
#title(Maximum .DAT file length)
If you want to set a maximum size for outgoing UUCP *.DAT bundles,
then set it here. WaterGate will close the bundle and create a new
one when the limit is reached.
If you don't want to use a limit, then set this value to 0.
The minimum value for this setting is 10000 bytes.

#subtopic(SysRFCUUCP Maximum rmail length)
#title(Maxmimum rmail line length)
This option specifies the maximum length of the so called
'rmail' line for outbound UUCP jobs.

If the length of that line passes the limit set here after
having added a recipient address, then WaterGate will close
the .XQT file and start a new one.

The valid limit for this option is based on the capabilities
of your ISP. Some ISPs can handle an unlimited number of
e-mail addresses while others allow only one address.

Set this option to 0 to force WaterGate to put only one e-mail
address on this line.

#subtopic(SysRFCUUCP Force no bitmask)
#title(UUCP filenames / Force No Bitmask)
If your ISP has problems processing the UUCP jobs created by
WaterGate, then try with this option set to #hl(No Bitmask).
WtrGate will use an alternative way to name the UUCP jobs.

An indication of the problems is that you can transfer the
jobs to your ISP, but they are not processed because the .D
file cannot be found by your ISP's software.
#end


;---------------------------------------------------------------------------
; SysRFC SmartHost PickList
;
#topic(SysRFC SmartHost PickList)
#title(Smart Host selection)
This lists shows the defined SMTP mailer Link Definitions and
UUCP style User Definitions. You can pick one to select it as
your Smart Host.
#end


;===========================================================================
; RFC Settings Editor
;
#topic(SysRFC RFC Settings Editor)
#title(RFC Settings Editor)
This topic is related to the fields that can be set in WtrConf under
System Configuration, RFC Settings.

#subtopic(SysRFC Organization)
#title(Organization)
Use this option to give a short description of your system, this
line is put in every message that originates from your system and
that is sent to UUCP.

Example:  Stargate IV, gate to Proxima IV
Result:   Organization: Stargate IV, gate to Proxima IV

#subtopic(SysRFC Smarthost)
#title(Smarthost)
Mail messages destined for a system not directly known to us are
sent through the smarthost. This system must be a direct neighbour
of your own system, and is probably the system you get your
UUCP/Newsfeed from. If a message cannot be processed and it
came from your smarthost it is bounced to the sender.

There must be an user in WaterGate's userbase that has a matching
UUCP name.

Press #HL(Enter) to select a possible smart-host system based on
the User Definitions and Link Definitions.

#subtopic(SysRFC Time zone)
#title(Time zone)
Select the timezone string to add to date fields for newly created
UUCP messages. If no string is specified WaterGate defaults to 'GMT'

 Example:    GMT
 Result:     Tue, 26 Oct 1993 22:40:11 GMT

RFC 1036 states that the timezone be in the following:

 "UT" / "GMT" / ("+"/"-") hh mm [ space "(" zone-name ")" ]

Where the text between [ and ] is optional and "space" is a space,
the other spaces are just for readability.

 Examples:   GMT
             +0100 (GMT)

The reason we mention this is because some hosts trash your message
if it contains an invalid time-zone indication! So you're warned!

#subtopic(SysRFC Undeliverable mail)
#title(Undeliverable mail)
A mail is undeliverable when it is addressed to a non-existent
sub-domain of your system. This option lets you decide what
WaterGate does with those mails.

When set to BOUNCE, WaterGate will send all undeliverable mail
back to its sender with a piece of information added that the mail
could not be delivered.

If set to NETMAIL, these messages will be written to the netmail
area and the sender of the mail will not be informed. This allows
you to look at these mails and handle them later. We suggest you
use this option.

When set to DELETE, all undeliverable mails are simply discarded with
you nor the original poster being informed.
#subtopic(SysRFC Bounce small)
#title(Bounce small)
Set this option to YES if want WaterGate to bounce only the
first approximate 20 lines of the message, instead of the
entire message, which might be an 100kb uu-encoded file.

When set to NO, the entire message is bounced.

This setting applies to both undeliverable mail, bounce filters
and manually defined BOUNCE and BOUNCEFROM statements in the
ROUTE.TDB file.

#subtopic(SysRFC Cross post limit)
#title(Cross post limit)
This value tells WaterGate in how many newsgroups an #news#
article is allowed to be cross posted. If it is cross-posted
in more newsgroups then WaterGate will ignore it.

Notice that this is a global setting affecting all news
articles arriving at the system. It is intended to kill so
called "spam" messages, which are often cross-posted in 25
or so newsgroups. A setting of 20 will kill most of these spam
messages.

A setting of 1 does not allow any cross-posted articles at all.
Setting it very high (max 255) simple allows all articles.

#subtopic(SysRFC Newsfix name)
#title(Newsfix name)
Enter the name under which WtrGate will accept newsfix requests
from your users.

If you enter "newsfix" and one of your system domain addresses
is wline.se, then your users will be able to reach the newsfix
built into WtrGate by mailing newsfix@wline.se.

;Newsfix forwarding
;UUCP settings
#subtopic(SysRFC SMTP forward)
#title(SMTP forward)
This fields only applies to systems using SMTP for outgoing
mail to their ISP.

Instead of telling your SMTP mailer to deliver mail to the
final destination machine, you can tell it to deliver it
to the mail machine at your ISP, so that machine does the
delivery to the final machine.

This is controlled by the SMTP jobs that WaterGate creates.
You have to enter the name of the mail machine of your ISP
here, for example: #mail.isp.com#

This can save you a lot of time, because you don't have to
deal with the delays of the Internet. Instead, you let the
mail machine of your ISP do this.

#subtopic(SysRFC Address completion)
#title(Address completion)
This option is only important when you receive messages with incomplete
recipient e-mail address information in the envelope file. Where
"incomplete" means that the e-mail address does not contain a domain
part (the part after the @@).
For UUCP the incomplete address is in the "rmail" line in the inbound
.X file. For SMTP this is the second (and following) line(s) in the
inbound .WRK file.

Some ISP delivering this #mess# to you are simply not configured properly,
while others have it as a policy that you are not allowed to have
sub-domains and all users therefor must be local on your system, which
doesn't require a domain part to address.

@WaterGate's solution@ is to either simply add the first configured
system domain address or to scan the headers of the message for the
rest of the information.
The first option is the most safe, but doesn't support sub-domains.
The second option can find the complete address, but doesn't have to
(the address doesn't even have to be in the headers!). It can also
trigger on a wrong address, although there are loads of preventions
to make sure this doesn't happen.

#subtopic(SysRFC Backbone)
#title(Backbone)
If a message in a moderated newsgroups is received by WaterGate
without an @Approved@ header, denoting it was sent by the
moderator, it is then translated into a mail message to the moderator.
If no moderator is defined for the area, it is send to the @BackBone@
system. This is usually not the same as your @Smarthost@ !

If you don't know a valid @Backbone@ site, don't change this option,
or better: don't specify an area as moderated at all. Let another
site upstream take care of it.

#subtopic(SysRFC RFCBadPath)
#title(RFC bad path)
This is the RFC equivalent of the FTN "BAD" area. A message in RFC
format that for some reason cannot be delivered or processed further
will be written to a file in this directory.

You can press F3 to use the File Manager to select the path.
#end


; end of file sysrfc.txt

