## DEPRECATION NOTICE

See [haraka-plugin-access](https://github.com/haraka/haraka-plugin-access)
for upgrade instructions.

# connect.rdns_access

This plugin will evaluate the remote IP address and the remote rDNS hostname
against a set of white and black lists. The lists are applied in the following
way:

connect.rdns_access.whitelist (pass)
connect.rdns_access.whitelist_regex (pass)
connect.rdns_access.blacklist (block)
connect.rdns_access.blacklist_regex (block)

## Configuration connect.rdns_access.ini

General configuration file for this plugin.

- connect.rdns_access.general.deny_msg

  Text to send the user on reject (text).

## Configuration connect.rdns_access.whitelist

The whitelist is mostly to counter blacklist entries that match more than
what one would want. This file should be used for a specific IP address
or rDNS hostnames, one per line, that should bypass blacklist checks.
NOTE: We heavily suggest tailoring blacklist entries to be as accurate as
possible and never using whitelists. Nevertheless, if you need whitelists,
here they are.

## Configuration connect.rdns_access.whitelist_regex

Does the same thing as the whitelist file, but each line is a regex.
Each line is also anchored for you, meaning '^' + regex + '$' is added for
you. If you need to get around this restriction, you may use a '.\*' at
either the start or the end of your regex. This should help prevent people
from writing overly permissive rules on accident.

## Configuration connect.rdns_access.blacklist

This file should be used for a specific IP address or rDNS hostnames, one
per line, that should fail on connect.

## Configuration connect.rdns_access.blacklist_regex

Does the same thing as the blacklist file, but each line is a regex.
Each line is also anchored for you, meaning '^' + regex + '$' is added for
you. If you need to get around this restriction, you may use a '.\*' at
either the start or the end of your regex. This should help prevent people
from writing overly permissive rules on accident.