IPs Authorized to Relay
You can specify which IP addresses are authorized to relay mail through GreenArrow Engine, along with default values for mail received from those IP addresses within the configuration files described in this document. Alternatively, SMTP AUTH, or username/password based authentication can be used to authorize users to relay messages.
Configuration File Locations
The default IP authorization configuration file location for the SMTP, SMTP2 and SMTP3 services is
If you’d like to create a separate IP authorization configuration file for the SMTP2 service, complete the steps below. These steps are optional:
Create a new configuration file in
cp -a /var/hvmail/control/smtp.tcp /var/hvmail/control/smtp2.tcp
Make any desired changes to the new file, then apply them by running:
TCPRULES_INHERITvariable in the
/var/hvmail/control/smtp2file equal to
Restart the SMTP2 service:
svc -t /service/hvmail-qmail-smtpd2
A separate configuration file can also be created for the SMTP3 service by following the steps above, replacing
To authorize an IP address to relay, add a line to
To allow a class A, B, or C block of IP addresses to relay:
1.:allow,RELAYCLIENT="" 1.2.:allow,RELAYCLIENT="" 1.2.3.:allow,RELAYCLIENT=""
To authorize a range of IP addresses to relay (in this example,
To authorize a range of blocks of IP addresses (in this example,
1.2.5.x) to relay:
Setting Default Values
In addition to setting the
RELAYCLIENT variable, which authorizes IP addresses as relay clients, you can set additional variables such as:
Specify the Mail Class (which uses SimpleMH):
Specify the ListID, SendID and MtaID:
Don’t insert the
Received header that would normally be inserted into a message.
The full definition of this file format is here: http://cr.yp.to/ucspi-tcp/tcprules.html
After updating the
/var/hvmail/control/smtp.tcp file, run the following command to apply the changes:
After running this command, the new data will be used for all new incoming connections. No services need to be restarted.