Toolvox® x3, Administrator guide – Code Blue TOOLVOX X3 User Manual
Page 125
![background image](https://www.manualsdir.com/files/778590/content/doc125.png)
Code Blue
•
259 Hedcor Street
•
Holland, MI 49423 USA
•
800.205.7186
•
www.codeblue.com
GU-154-F
page 125 of 132
ToolVox® X3
Administrator Guide
Restrictions on client hostnames/addresses
This restriction applies to the client host name and/or address. By default, Postfix will allow
connections from any host, but you may add additional restrictions using the following: reject_
unknown_client, permit_mynetworks, check_client_access maptype:mapname, reject_maps_rbl,
maps_rbl_reject_code, permit, reject, warn_if_reject, reject_unauth_pipelining.
Restrictions on sends in HELO commands
This option specifies additional restrictions on information that can be sent by client in the HELO
and EHLO commands. This option correlates to the smtpd_helo_restrictions directive. By default
Postfix accepts anything, and the following restrictions may be added: reject_invalid_hostname,
permit_naked_ip_address, reject_unknown_hostname, reject_non_fqdn_hostname, check_
helo_access maptype:mapname, reject_maps_rbl, reject_unknown_client, check_client_access
maptype:mapname, permit, reject, warn_if_reject, reject_unauth_pipelining.
Restrictions on sender addresses
This option restricts what can be contained in the MAIL FROM command in a message. It may
be used to prevent specific email addresses from sending mail, reject clients without a resolvable
host name, etc. This option correlates to the smtpd_sender_restrictions directive and may contain
any of the following restrictions: permit_mynetworks:, reject_unknown_client, reject_maps_rbl,
reject_invalid_hostname, reject_unknown_hostname, reject_unknown_sender_domain, check_
sender_access maptype:mapname, check_client_access maptype:mapname, check_helo_access
maptype:mapname, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject, permit.
Restrictions on recipient addresses
This parameter places restrictions on the recipients that can be contained in the RCPT TO
command of a sent message. It can be used to dictate where email may be sent. This option
correlates to the smtpd_recipient_restrictions, and may contain any of the following restrictions:
permit_mynetworks, reject_unknown_client, reject_maps_rbl, reject_invalid_hostname,
reject_unknown_hostname, reject_unknown_sender_domain, check_relay_domains, permit_
auth_destination, reject_unauth_pipelining, permit_mx_backup, reject_unknown_recipient,
check_recipient_access, check_client_access, check_helo_access, check_sender_access, reject_
non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject, permit.
DNS domains for blacklist lookups
This option configures the optional blacklist DNS servers that will be used for all RBL checks that
have been specified in all access restrictions. It may contain any number of servers in a whitespace
separated list. These services can be used to help prevent spam, as discussed earlier in this
section, with the
Restrict ETRN command upon... parameter. This option configures the maps_
rbl_domains directive and is empty by default.
Restrict mail relaying
This option specifies which hosts, networks, domains, etc., Postfix will relay email for. This option
correlates to the relay_domains directive and defaults to $mydestination.
SMTP server response on access map violation, SMTP server response on RBL domains violation,
SMTP server response on forbidden relaying, SMTP server response on unknown client reject,