# This is a test version of the configuration file.
# Its format is:
#
# VarName	Value	Qualifier
#
# The currently used variables are marked as ***used by: <program>***
# The other variables are not used, you should not bother modifying them.

#
# Local port number for whoisd to bind to.

BINDPORT	43

#
# Generic help file

HELP	/export/db/doc/HELP

#
# What banner do we use when giving a reply to a whois query

REPLYBANNER % Rights restricted by copyright. See http://www.mydb.net/db/dbcopyright.html
REPLYBANNER %
REPLYBANNER % All rights reserved.
REPLYBANNER %

#
# All the details about each and every source we have in the database
#
# SOURCE SrcName DB-details	Mode	NRTM-details	UpdatePort	Options
# ***used by: rip, load***
#
# SrcName: the name of your source
#
# DB-details: MySQL_Host,MySQL_Port,MySQL_User,MySQL_Password,MySQL_Database
#
# Mode:
# 0 1 - nrtmc -+ dummy
# 6 7 - update standalone -+ dummy
# 2 3 - update server -+ dummy
#
# NRTM-details: NRTM_Server_Host,NRTM_Server_Port,LogFile,Delay,NRTM_Protocol_Version
# (can be ignored for a non-NRTM-client)
#
# UpdatePort: The port to which the server listens for updates by dbupdate
# (can be ignored for NRTM client)
#
# Options: CanUpd,DefLook
# (CanUpd: Can the source be updated? y : n)
# (DefLook: Is it a default database to do lookups in? 1->yes, 0->no)

# This should be used to load a database the first time (the Mode accepts dummies)
#SOURCE TEST sqlhost,3306,dbuser,dbpsw,TESTDB 7 dummy,0,dummy.mlog,120,14 43004 y,1

# This can be used for your own database
SOURCE TEST sqlhost,3306,dbuser,dbpsw,TESTDB 2 dummy,0,dummy.mlog,120,14 43004 y,1

# This can be used to mirror the RIPE Database (you must be an authorized
# site to do that! Write to <ripe-dbm@ripe.net> for details)
#SOURCE  RIPE sqlhost,3306,dbuser,dbpsw,RIPEDB 0 whois.ripe.net,43,ripe.mlog,120,1 0 n,1

#
# RIPADMIN
# Where is the RIPADMIN database
# RIPADMIN MySQL_Host,MySQL_Port,MySQL_User,MySQL_Password,MySQL_RIPADMIN_Database
#***used by: rip***
RIPADMIN sqlhost,3306,dbuser,dbpsw,RIPADMIN

#
# Run database sw in test mode?  
#***used by: dbupdate***
TESTMODE  0

#
# crypted password for overriding all security for updates
# 
# Example usage:
#
# object
# override: Reason_for_overriding_all_security Password
#***used by: dbupdate***
# [ This crypted password correspond to the word "password" ]

OVERRIDECRYPTEDPW   1F.5OTsRVjwLo


#
# help file for "whois help"

WHOISHELP	/export/db/doc/WHOIS-HELP

#
# help file for <auto-dbm> "HELP"

AUTODBMHELP             /export/db/doc/AUTO-DBM-HELP

#
# for each source a list of sources to look in for overlapping
# route objects

CROSSNOTIFYSOURCES	RIPE	RIPE

#
# User ID/name of the update process and whois server

UID dbase

#
# whoisd query log file

QRYLOG	/export/db/log/qry/qrylog
QRY2LOG /export/db/log/qry/qry2log

#
# Error log file (if something really goes wrong ...)

ERRLOG	/export/db/log/err/errlog

#
# logfile where an audit trail for deletes and other important
# database actions goes. Only one liners are syslogged. Maintainer
# should take care of rotating logs and the like.

AUDITLOG /export/db/log/audit/auditlog

#
# this is where all update requests will be logged

UPDLOG	/export/db/log/upd

#
# this is the file where all acknowledgements will be logged
#***used by: dbupdate***

ACKLOG	/export/db/log/acklog

#
# where to keep lock & PID files ?!?

LOCKDIR  /export/db/locks
                              
#
# This is where the whoisd pid goes once started

PIDFILE	whoisd.pid

#
# lockfile for stopping all updates via whois server
# dbupdate will still work

UPDATELOCK STOPUPDATES

#
# Keep connection open for at most KEEPOPEN seconds for 

KEEPOPEN 180

#
# List of maintainers which can create an inetnum object 
# with status ALLOCATED (one per line or space separated list
# or combination of the above)

ALLOCMNT MY-OWN-MNT

#
# TMPDIR is the tmp directory where various tools keep tmp files.
# 
# make sure that this directory is owned by the 'updating process'
# user and cannot be written by other users
#***used by: dbupdate***

TMPDIR	/export/db/tmp

##
## Site specific programs
## 

#
# PGPCMD
#
# PGPV and PGPK are the full pathnames of your PGP5.0i executables
#
# comment these out if you don't want to support PGP authentication

PGPV /usr/local/bin/pgpv
PGPK /usr/local/bin/pgpk

#
# PGPPATH is the directory where PGP process stores server's public key
# ring and where it might read the configuration file pgp.cfg (which is not
# needed for normal operations)

PGPPATH /export/db/.pgp

#
# MAILCMD is the command into which a composed e-mail is given as standard
# input, to be send as mail. The message piped into this command has ALL
# the necessary mail header to process the mail:
# From:
# To:
# Subject:
# The mail command should take the recipients from the actual message.
# Using sendmail it will be executed as: /usr/lib/sendmail -t < "messagefile"
# (default: /usr/lib/sendmail -t)
#
# NOTE:
# -fregistry-dbm makes registry-dbm the trusted user that will appear on the
# envelope. Bounces will go to this address. If you do not specify
# this, sendmail will send bounces straight back to the automatic
# mailbox, where it will bounce again, and again, ....
# User has to be a trusted user, T<name> in sendmail.cf.
#***used by: dbupdate***

MAILCMD /var/qmail/bin/qmail-inject -fmy-dbm

#
# NROFNAMES
#
# minimal number of components that a name should consist of

NROFNAMES 2

##
## EMAIL addresses
##

# 
# DEFMAIL is the mailbox used when no mail notifications or acknowledgements
# both as to and from address in various places.

DEFMAIL	my-dbm@mydb.net

#
# HUMAILBOX is a human looked at mailbox, used for forwarding
# special objects. IT MUST NOT BE THE AUTOMATIC MAILBOX!!!!
# It can be used in mail messages as explained in MAILTXT below.
#***used by: dbupdate***

HUMAILBOX	my-dbm@mydb.net

#
# AUTOBOX is the mailbox used for automatic updates
#         it is only used in informational messages to users
#         the software doesn't send mail to this address.

AUTOBOX		auto-dbm@mydb.net

#
# DUPLICATEPERSONCHECK
# enable create/modify check for person with the same name/contact data 
# and different nic handles
# when not defined check is disabled. 
# when defined warning is generated if person with the same name found
# when defined as 'strict' and contact data are also the same then 
# creation/modification is refused, when nonstrict only warning is generated

DUPLICATEPERSONCHECK nostrict

#
# What to display if no match was found

NOMATCH % No entries found for the selected source(s).

#### Various Cross Notification Texts
#### used in the outgoing messages
#### 
#### there are two type of messages
####   1. to the originator prefixed with CN_
####   2. to the others prefixed with CNO_
####
#### there are two sets of text for each type of message
####   1. when the updated object was an addition postfixed with _ADD
####   2. when the updated object was a  deletion postfixed with _DEL
####

### Messages to the ORIGINATOR of the update

## CN_SUBJECT
# 
# The complete 'To:' line for the outgoing message. 
# Lines are concatenated together. Make sure you indent following lines
# with white space (see RFC822)
#

CN_SUBJECT_ADD Subject: MyDB RR: Addition of overlapping routes
CN_SUBJECT_DEL Subject: MyDB RR: Removal  of overlapping routes

### CN_EXPLAIN
#
# Something like "Your update to the following object..."
# used at start of message and followed by the updated route object
#

CN_EXPLAIN_ADD The addition of your route object ... 
CN_EXPLAIN_DEL The deletion of your route object ... 

### CN_OVERLAPS
#
# Something like "It overlaps with your routes.."
# used after the updated object and before the list of overlapping routes
#

CN_OVERLAP_ADD created new overlaps with the following routes ...
CN_OVERLAP_DEL removed the overlaps with the following routes ...

## CNO_SUBJECT
# 
# The complete 'To:' line for the outgoing message. 
# Lines are concatenated together. Make sure you indent following lines
# with white space (see RFC822)
#

CNO_SUBJECT_ADD Subject: MyDB RR: Addition of overlapping routes
CNO_SUBJECT_DEL Subject: MyDB RR: Removal  of overlapping routes

### CNO_EXPLAIN
#
# Something like "Your update to the following object..."
# used at start of message and followed by the updated route object
#

CNO_EXPLAIN_ADD The addition of the route object ... 
CNO_EXPLAIN_DEL The deletion of the route object ... 

### CNO_OVERLAPS

# Something like "It overlaps with your routes.."
# used after the updated object and before the list of overlapping routes
#

CNO_OVERLAP_ADD created new overlaps with your following routes ...
CNO_OVERLAP_DEL removed the overlaps with your following routes ...

#
# The MAILTXT is the text that comes right after the headers in an email ack
# send by "dbupdate" when processing an email update (-M flag).
# In this text you can use the following variables that will be expanded
# to the real values in the ack:
#
# general purpose variables:
#
# $AUTOBOX      
# $HUMAILBOX
# $DATE
# $TIME
#
# E-mail variables:
#
# $FROM         = "From:"
# $CC           = "Cc:" 
# $SUBJECT      = "Subject:"                   
# $MDATE        = "Date:"
# $MSGID        = "Msg-Id:"
#
# networkupdate variables:
# 
# $FROMHOST     = from which host did the update come

MAILTXT Your e-mail:
MAILTXT
MAILTXT Your real e-mail:
MAILTXT
MAILTXT >   From:    $FROM
MAILTXT >   Cc:      $CC
MAILTXT >   Subject: $SUBJECT
MAILTXT >   Date:    $MDATE
MAILTXT >   Msg-Id:  $MSGID
MAILTXT
MAILTXT has been processed by the automatic update procedure at the MyDB NCC.
MAILTXT Diagnostic output follows:
MAILTXT
MAILTXT ------------------------------------------------------------------------

#
# MHEADER The complete mailheader for the ack mail, you can include any
# mail header field, EXCEPT for the "To:" and "Cc:" field which is added 
# inside the ack sending program. Again you can use the 4 variables as 
# specified in MAILTXT

MHEADER From: My Database Management <$HUMAILBOX>
FAILURETXT From: My Database Management <$HUMAILBOX>
SUCCESSTXT Subject: SUCCEEDED: $SUBJECT
HELPHEADER Help file requested so body of message ignored.

#
# ACKERR is the message that will be displayed when errors or warnings were
# found in an update.

ACKERR Objects that just generated a WARNING have been updated as shown.

#
# ACKOK is message displayed when no error/warnings were found in an update

ACKOK No errors were found in your database update.  Congratulations.

#
# Signature on the acknowledgement

ACKSIG MyDB Database Maintenance Department (Automatic Section)

#
# NOTITXT Notification text used in notification messages.
# Same variables as in MAILTXT can be used here.
#***used by: dbupdate***

NOTITXT This is to notify you that some object(s) in the MyDB database
NOTIMAILTXT The update causing these changes had the following mail headers:
NOTINETWORKTXT The update causing these changes came from the following host:

#
# NHEADER The Header used for notification messages

NHEADER From: MyDB Database Notifications <$HUMAILBOX>

#
# FWHEADER The header for forwarding updates that failed because of
# maintainer autorisation failures.

FWHEADER From: MyDB Database Maintainer Forwarding <$HUMAILBOX>

#
# FWTEXT The text send out to maintainers to inform them that someone
# tried to change objects for which they are maintainers, but failed
# the authorisation
#***used by: dbupdate***

FWTXT  This is to notify you that some objects in which you are mentioned as
FWMAILTXT  The mail message causing these failures had the following mail headers:
FWNETWORKTXT  The update causing these failures came from the following host:

#
# Maintainer objects are handles special and cannot be created auto
# automatically. They are forwarded to $HUMAILBOX or whatever you
# want to specify. The ERROR sent back to the sender, will contain
# $HUMAILBOX as the mailbox it was sent to. This one can take variable
# substitution like MAILTXT.

MTFWHEADER From: MyDB Database Maintainer Creation <$HUMAILBOX>
MTFWTXT A maintainer object is requested by:

#
# Text printed in response to queries coming from blocked hosts

DENYACCESSTXT              * A C C E S S    D E N I E D *

#
# text printed when displaing result of referred query

REFERRALTXT The object shown below is NOT in the MyDB database.

#
# text printed when referred query failed

REFERRALERRORTXT Referred query to host $REFERHOST at port $REFERPORT

#
# text printed when referral loop detected

REFERRALLOOPERRORTXT Referral loop detected when querying 

#
# text printed when referral timed out

REFERRALTIMEOUTTXT Referred query to host $REFERHOST at port $REFERPORT

#
# text printed when answer from remote server got truncated

REFERRALTRUNCTXT Result TRUNCATED. Answer length exceeded limit.

#
# text printed to mark end of referred query response

REFERRALENDTXT %%% End of referred query result

#
# value of referral timeout in seconds

REFERRALTIMEOUT 10

#
# limit for number of lines in referred query result

REFERRALMAXLINES 2000

#
# COPYRIGHT message that goes on top of every newly generated, or cleaned
# database, will be output with "#" before each line.

RIGHTS Copyright (c)1992/1993/1994/1995/1996/1997/1998/1999 by MyDB NCC 

#
# the list of valid country names MyDB database specific, used
# for syntax checking.
#***used by: dbupdate ***
COUNTRY NL
COUNTRY EU
COUNTRY IT
COUNTRY IE
COUNTRY RU
COUNTRY TR
COUNTRY PL
COUNTRY IE 
