Mailprotector's Allow list only accepts valid domains and email addresses. To allow or whitelist an IP address or IP range, a Message Rule must be created.
Creating the Message Rule
Single IP Address
A Message Rule can be added to a domain, user, or reseller level to apply to all domains under management in the Mailprotector Console. Navigate to the appropriate location for applying the rule. In this article, the rule will be applied to the mpdemo.net domain.
From the desired location in the Console, go to Filtering and scroll down to the Message rules section.
Enter a name for the rule and click on the Create button.
|Message rule creation opens the Criteria settings first. Scroll down to the Source IP section.|
Type in a single IP address and press Enter. The IP address will become a blue criteria item.
NOTE: You may add additional IP addresses to the field if you have more than one to be allowed.
|Scroll back to the top of the page and click on Actions.|
|Find the Never hold the message for review (inbound only) option and enable the action.|
|Scroll to the top of the page and click the back arrow to view the list of Message rules.|
Find the rule you created in the rules list and enable it by clicking the switch icon.
NOTE: New rules are not enabled by default.
IP Range or CIDR Notation
Message Rules do not natively support IP ranges or CIDR (classless inter-domain routing) notation. A range of IP addresses must be added as individual IP addresses, or a CIDR notation can be converted to a regular expression.
A regular expression can be built quickly using the CIDR to RegEx builder.
As an example, adding 192.168.200.11/28 to the regular expression builder would provide the following result:
Follow the same steps for creating the Message Rule as above for a single IP address. However, add the regular expression built by the tool when adding the Source IP data. Begin and end the regular expression with a forward slash (/).
The criteria would look like the image below:
BEST PRACTICE: The Source IP criteria can contain individual IP addresses and regular expression IP ranges in the same rule. It is easier to manage an IP list in one rule than making a separate rule for each IP or range. The criteria would appear as below: