; sysgw.txt
;
; This is the WaterGate help file
; This file is included by wtrgate.txt
;
; Contents: WtrConf System -> Gateway 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)


;---------------------------------------------------------------------------
; SysGW Select gateway AKA
;
#topic(SysGW Select gateway AKA)
#title(Gateway AKA selection)
Select the FTN system node number that you want to be the
gateway AKA.
#end


;=========================================================================
; SysGW Copy Headers Editor
;
#topic(SysGW Copy Headers Editor)
#title(Copy Headers)
Select the UUCP fields you want to keep message that are
gated from e-mail or news to netmail or echomail.

The selected fields can be copied to the beginning of a Fido
message as normal text, or as kludges that can be hidden
by the editor, so you can pop them up if you want to see them.

#subtopic(SysGW CopyHeaders Name)
#title(Header name)
Enter the name of the UUCP header line you want to search for.
These are always one word (no spaces) and WaterGate searches
for them #hl(with a space appended). This way the keyword
"From" won't match both "From" and "From:".

Some of the most common keywords have been filled in for you
already. You can change them to your own needs.

#subtopic(SysGW CopyHeaders WhereTo)
#title(Where to)
Select how the header line should be stored.

#hl("Not") disables this copy option. Otherwise, if set to #hl("Kludge")
the header is copied and stored as a kludge line. #hl("Body") copies
the header to the body of the message, before the actual message text.
#end


;===========================================================================
; Gateway Settings
;
#topic(System Gateway Settings)
#title(Gateway Settings)
This topic is releated to the fields in WtrConf under System
Configuration, Gateway Settings.

#subtopic(SysGW Gateway AKA)
#title(Gateway AKA)
Select which system node number to use for the gateway.

This address is mainly used when building domain addresses for
users without their own domain address (either filled in in the
user record or via a MAP-UUCP statement).

Your users can address the gateway on all your system node
numbers and not just the node number you set here!

#subtopic(SysGW Gateway user)
#title(Gateway user)
Your users write their netmails to one of your system node
numbers and to the user name you fill in here. WaterGate
then gates the netmail into an e-mail.

The actual destination address must be placed in the first
line of the message, as in the following example:

  From: John Doe          2:512/301
  To  : #hl(UUCP)              2:512/17
  Subj: About that new program...
  -----------------------------------------------------------
  TO: jake@fatman.network.nl

The default setting is "UUCP", but you can change it to
"Gateway" or whatever though.

Notice that it is also possible to put the e-mail address in
the TO field instead of on the first line of the body of the
netmail. You have to enable the "Allow TO" option for that.

#subtopic(SysGW AcceptTo)
#title(Accept To:)
Set this option to YES if you want WaterGate to scan if the TO:
field of a FidoNet message to the UUCP gateway contains a fully
qualified domain address.

This may not always be possible, because a domain address can be
longer than the maximum length of a FidoNet TO: field. When this
is the case, you can still use 'normal' way of putting the domain
address on the first line of a message.

The following are equivalent:

 From: Jaap Aap               2:280/803
 To  : jaap@aap.nl            2:280/802
 Subj: Leven zonder bananen

 From: Jaap Aap               2:280/803
 To  : UUCP                   2:280/802
 Subj: Leven zonder bananen
 --------------------------------------------
 TO: jaap@aap.nl

#subtopic(SysGW Kill gated netmail)
#title(Kill gated netmail)
If this option is set the Yes, all netmail that has been
gated to UUCP will be deleted afterwards. This
corresponds to setting the KillSent flag on a netmail.

If one of your points or downlinks forgets to set this
flag, your netmail area will fill up with these gated
messages.

If you use WaterGate in a point setup, you might want to
leave this setting to NO and move all sent message to an
other (history) area.

#subtopic(SysGW Allow headers)
#title(Allows headers)
When this options is set to YES, WaterGate will search the start
of the netmail message for header lines that can be copied into
the mail or news message.

You can for example put a "Reply-To: user@somewhere.com" at the
beginning of the netmail message. This header will then be copied
into the UUCP style message. Notice that #hl(if) you have a To:
header in the netmail, that it should be place before all other
headers!

You can normally leave this option set to YES, unless you
experience problems or you don't want your users to use this
option.

WaterGate stops search from headers at the first empty line or an
non-valid header. Headers have to have be of the format
"<word>: <text>".

#subtopic(SysGW Transport limitation)
#title(Transport Limitation)
If your RFC message transport mechanism cannot handle 8 bit
characters (above 127 and control characters below 32) then
keep this option at the default of 7-bit. Characters in the
just mentioned range are then encoded using quoted-printable.

Users able to to use 8 bit transport and users not willing or
not able to use quoted-printable encoding can set this option
to 8-bit.

Remember though that the receiving system or intermediate
systems might not be able to handle messages with 8-bit
characters and it is not known whether these messages are
translated to 7-bit at that point (small chance) or simply
deleted.

#subtopic(SysGW Quoted printable)
#title(Quoted printable)
WaterGate automatically uses the MIME option "quoted-printable" to
represent the otherwise illegal characters with the highest bit set
in a form that looks like this: =E7.

Quoted-printable also allows to use soft line breaks: an equal sign
at the end of a line to indicate that the paragraph or long line
continues on the next line. This powerful feature allows paragraphs
(as we have them in FidoNet) to be recovered by the recipient!!

If you want this, then set this option to "Always" (the default).

Otherwise set it to "If needed". WaterGate will then check the
message and decide whether quoted printable is really required. If
the body only contains ASCII, then you can do without. This will
also avoid encoded equal signs (=3D) and receivers without MIME
support (or not behind a gateway with MIME support, like WaterGate)
will be able to read and reply to the message without problems.

#subtopic(SysGW Line wrap)
#title(Line wrap)
When translating the body of a FidoNet message to RFC format,
this number is used to wrap too long lines.

The word that makes the line too long is "wrapped" to the
next line. If there is no word within reach, the line is
simply cut off at this position.

This number can be set between 50 and 99. The default setting is 72.

To avoid these broken down lines, check the option to use
MIME quoted-printable with soft line breaks above.

Another alternative is to set this option to zero. This will
disable the line wrapping, but results in long lines that can be
presented by the recipient's reader in a way that requires
horizontal scrolling.

#subtopic(SysGW Small addresses)
#title(Small addresses)
Since your gateway isn't going to move anywhere far, filling in the
entire Fido address each time a netmail message passes through the
gate from an unknown system is really unnecessary. Instead, using
the small addresses you send only the parts that differ from your
own system.

For example: 2:280/908 sends a message to the gateway at @2:280/802@,
these systems only differ in their node numbers. So WaterGate adds only
that information to its gateway domain:

    joe_user@f908.gateway.network.nl

Instead of creating:

    joe_user@f908.n280.z2.gateway.network.nl

When someone writes a reply to that message, the program will merge
the found 'f908' into its own address, thereby reconstructing the
original address. Of course, someone can still reply to a message
using the full fido munged address.

#subtopic(SysGW Name separator)
#title(Name separator)
The name separator is used when converting usernames from
FidoNet to UUCP, for example when using the default separator
the underscore, '_':

"Jaap Aap" is converted into "Jaap_Aap".

Another character often used by gateway programs is the dot,
'.'. But this character is often used by users on systems
that do not support multiple parts in a lastname, reconstructing
their name could go wrong because of this.

#subtopic(SysGW FSC35 Kludges)
#title(FSC35 Kludges)
If you want to reply to a netmail that is a gated UUCP e-mail
message, you need to know the correct address. If your editor
supports FSC-35 kludges, replying becomes very easy and almost
automatic.

   REPLYTO     2:280/802 UUCP
   REPLYADDR   jaap@aap.nl

#subtopic(SysGW FTN From)
#title(FTN From:)
If your editor does not support FSC-35, you need to have the
address written down in the message somewhere, so you can reply
to the message.

You can get the name of the sender in the From: field of the
netmail or echomail message. If this doesn't fit then it will be
put in the body of the message as well.

If you have selected the From: header line from the e-mail to
be written down in the body of the FidoNet message anyway, then
you can also choose to have the Full Name of the e-mail sender
to be put in the From: field of the fido message. You can also
select this if you are using FSC-35.

#subtopic(SysGW Copy headers)
#title(Copy headers)
When converting messages from UUCP format into Fido format, WaterGate
converts the information stored in the UUCP headers into a format
readable by Fido systems. Optionally, it also copies some of the UUCP
header lines to the beginning of the Fido message. Use this option
to select which fields you want to keep in a Fido message.

#subtopic(SysGW MessageID_to_MSGID)
#title(Message-ID to MSGID)
This option allows transparent gating of Message-ID headers
into FTN and back again. The contents of the Message-ID
header will be put in the MSGID kludge of the Fido message
and recovered when a reply is sent.

Some tossers cannot handle this irregular, but completely
legal format and might even crash. Use NO if you experience
problems or use INCLUDE if you want to be a completely
transparent gateway.

WaterGate follows the GateBau guidelines for this feature.

#subtopic(SysGW Organization to Origin)
#title(Organization to Origin)
With this option you can tell WaterGate to gate the
Organization: header from a news message into the
Origin line of the resulting echomail.

Since you can also use Copy Headers to copy the
Organization: line into the body of a gated message,
you can override that option for echomail here.

 #No#       - Do not gate Organization into Origin
 #Yes#      - Gate Organization into Origin
 #Override# - Gate and no Copy Header for Organization

You can edit language entry 105 to configure how the
Organization header is gated into the Origin.

#subtopic(SysGW Name separator 2)
#title(Name separator 2)
This is an additional character that replaces the space. It is only
used in the RFC->FTN direction as an additional character that
indicates a space.

For example, if the Name Separator is set to '_' and you set this
field to '.' then both characters, when found in an e-mail address,
are replaced with a space to form the Full Name.

If you don't want to use it then either put a space here, or set it
the same as the Name Separator.
#end


; end of file sysgw.txt

