# WHITELISTING (functional) #
#####################################################################
#
# whitelisting: default: on
#
# this enables whitelisting of ip/netblocks. this is needed
# if you want to allow any of the whitelisting features.
#
# 1=on 0=off
WHITELISTING=1
# whitelist null sender: default: off
#
# null senders are normally used for bounce messages. many
# viruses use null senders so its wise to leave this disabled.
#
# 1=on 0=off
WHITELISTNULL=0
# whitelist sender address/domain
#
# this allows you to do whitelisting based on envelope sender
# address or envelope sender domain. a number of people have
# been asking for this. please AVOID using this as spammers
# forge senders and domains a lot.
#
# 1=on 0=off
WHITELISTSENDER=1
#
# whitelist client dns name
#
# this allows you whitelist clients that have proper resolving
# records. for example, i could whitelist 'bulk.scd.yahoo.com'.
# so any connections from n6a.bulk.scd.yahoo.com or
# n6b.bulk.scd.yahoo.com would be whitelisted. this type of
# whitelisting gives far greater power when it comes to
# whitelisting ISPs or big companies which you know do not
# house spammers. please note. this table must NOT have more
# than 10 000 -> 15 000 entries.
#
# 1=on 0=off
WHITELISTDNSNAME=1
# automatic whitelisting default: off
#
# this allows whitelisting of remote networks who have sent
# more than AUTO_WHITELIST_NUMBER of authenticated triplets.
#
# 1=on 0=off
AUTO_WHITE_LISTING=1
# auto whitelist number: default: 500
#
# how many succesfull triplets does it require before a
# network is automatically whitelisted
#
AUTO_WHITELIST_NUMBER=10
Starting policyd: [ OK ]