; syslog.txt
;
; This is the WaterGate help file
; This file is included by wtrgate.txt
;
; Contents: WtrConf Sytstem -> Log settings
;

; 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 Global Log Settings
;
#topic(System Global Log Settings)
#title(Log file settings)
This topic covers the settings that can be made in WtrConf under
the System Configuration menu, Global Settings, Log file settings.

You can control how much and which details are written to the log file.

#subtopic(CFGGlobLog LogDebug)
#title(Debug)
If this option is set to YES, WaterGate will write
as much information to the logfile as possible. This
has the same effect as setting all the other options
to YES.

#subtopic(CFGGlobLog LogSpoolTossed)
#title(Tossing .X and .D files)
When this option is set to YES, WaterGate will log
the complete names of the .X and .D files it processes.

#subtopic(CFGGlobLog LogFidoExtract)
#title(Extracting Fido archives)
When this option is set to YES, WaterGate will write
a line to the logfile with the complete name of the
archive it is about to extract.

#subtopic(CFGGlobLog LogFidoTossed)
#title(Tossing Fido .PKT files)
When this option is set to YES, WaterGate will write
a line to the logfile with the complete name of the
.PKT file it is about to process.

#subtopic(CFGGlobLog LogTranslationFU)
#title(Address translation FTN->RFC)
If this option is set to YES, WaterGate will log all
the address translations. This are the mappings you
installed in ROUTE.TDB and the automatic translations
when a FidoNet messages originates from a system AKA
or a user with a domain address in his/her record.

#subtopic(CFGGlobLog LogCheckFilter)
#title(New newsgroup names check)
If this option is set to YES, WaterGate will write a
line to the logfile when a check is made for a new
newsgroup name. The logged line will tell you wether
the new newsgroup name was accepted or rejected and
which line of the filter file caused that. The line
number allows for easy debugging of your filter file.

#subtopic(CFGGlobLog LogXFix)
#title(Incomplete address fix)
If this option is set to YES, WaterGate will write a
line to the logfile whenever it encounters an incomplete
address in the .X file and has searched the .D file
header for the complete address.

#subtopic(CFGGlobLog LogCopyHeaders)
#title(Copied headers FTN->RFC)
Set this option to YES when you want to have log lines
for each header that was copied from a fido netmail or
echomail and placed in a UUCP mail or news.

#subtopic(CFGGlobLog LogIllegalHeaders)
#title(Illegal copy headers)
Set this option to YES when you want to have log lines
for each header that was found in a fido netmail or
echomail, but is not copied to the mail or news because
it is an system header line, like From:, To:, Message-ID:
etc.

#subtopic(CFGGlobLog LogAreaFix)
#title(Area/newsfix processing)
Set this option to YES when you want to have log lines
for each AreaFix or newsfix command that is executed.
You will see every statement that is processed and
every area that is connected or disconnected.

#subtopic(CFGGlobLog LogMapApply)
#title(Applied mapping statements)
Set this option to YES when you want to have log lines
for each System, MAP-UUCP and MAP-FIDO statement that
has been applied while translation addresses.

#subtopic(CFGGlobLog LogNetmailImport)
#title(Importing of netmail)
Set this option to YES when you want to have log lines
for each message that is imported into the netmail area.

#subtopic(CFGGlobLog LogRODeny)
#title(Read-only denied postings)
Set this option to YES when you want to have log lines
for each echomail or news message that was not allowed
because the user had access to area via a read-only
and not via a read-write group.

#subtopic(CFGGlobLog LogPktEachEcho)
#title(Each message from a .PKT)
Set this option to YES when you want to have log lines
for each echomail message that originates from a .PKT
file and is processed. WaterGate will write a single
line with the AREA name and the number of bytes the
message is big.

This enables you to see the contents of a .PKT file
while it is being processed.

#subtopic(CFGGlobLog LogUUCPOutbound)
#title(Created UUCP jobs)
Set this option to YES when you want to have log lines
for each UUCP job that is created by WaterGate. This
enables you to see that WaterGate is creating UUCP jobs
and with what filenames.

#subtopic(CFGGlobLog LogSMTPOutbound)
#title(Created SMTP jobs)
Set this option to YES when you want to have log lines
for each SMTP job that is created by WaterGate. This
enables you to see that WaterGate is creating SMTP jobs
and with what filenames.

#subtopic(CFGGlobLog LogExportedMsgs)
#title(Exported messages)
Set this option to YES when you want to have log lines
for each *.MSG netmail that is exported. It logs the
message filename and who the message is to.

#subtopic(CFGGlobLog LogErrNewsgroups)
#title(Article newsgroups)
When this option is set to YES, then WaterGate will log
all newsgroups in which an articles was cross-posted
when none of those newsgroups are valid or know for the
user/link delivering the message.

The listing of newsgroups can be helpful when debugging
but can be annoying and occupying space when the number
of newsgroups in which an article was cross-posted is
high.
#end


; end of file syslog.txt

