gtic is a GNU software. It has NO WARRANTY and may contain a buffer
overflows and other bugs. Running gtic from root may crash your system.
Due to some security reasons gtic should NOT be run by root or be suid to
root. To make gtic execution more secure commit the following steps:

1) Make a new group for running gtic and related binaries (i.e.: gtic)
   or use the existing one. Separated group for gtic is required because
   gtic also works as an area manager and is usually called from /etc/aliases
   by sendmail or other mailer daemon. sendmail doesn't run "aliased"
   programs as root, usually it runs programs as "bin" or "mail" user.
# groupadd gtic

2) If you don't have a separate user for your ftn-like software (i.e.: fido),
   add a new user to /etc/passwd with disabled password and
homedir=shell=/dev/null.
   Run gtic as this user from crontab etc.
# adduser fido -d /dev/null -g uucp -G gtic -M -r -s /dev/null

3) Add "bin" or "mail" (depending on your system) user to gtic's group to
   enable sendmail gtic execution from aliases file, add your username to
   permit yourself to execute gtic (some debugging purposes, hatching etc).
   (i.e.: gtic:x:513:bin,sysop)
# vi /etc/groups

4) Edit CONFIG and Makefile files to adjust some variables.
   Steps 1-3 of this INSTALL file should be performed manually
   and steps 5-7 can be automatized by `make install`.
   Type `make clean; make all; make install`.
>  Run "make install" as root user.

4) Change owner and group of the gtic binary to fido.gtic relatively:
# chown fido.gtic /usr/local/gtic/gtic

5) Make gtic binary suid to the "fido" for it to handle inbound,
   outbound, config and filebase directories and disallow the
   world access to the gtic binary:
# chmod 4110 /usr/local/gtic/gtic

6) Change owner and group of the gtic config files to fido.gtic
   relatively (directory /etc/gtic must be available for writing for "fido"
   user or "gtic" group):
# chown -R fido.gtic /etc/gtic

7) Fix permissions for the config files in $(CONFIGDIR) so that
   areas/config/areagroups files could be public accessible, but users
   file cointaining passwords being inaccessible to the world:
# chmod 664 /etc/gtic*
# chmod 600 /etc/gtic/users

8) If you want gtic to reply to the areafix querries it can be called by MTA.
   To enable it put the following lines in /etc/aliases
allfix:  filefix
filefix: "|/usr/local/gtic -m"
    and reindex aliases database
# newaliases