Description |
This article describes how to use the IP pool in several scenarios. |
Scope |
FortiMail v7.0 and v7.2. |
Solution |
IP pools are used to define a range of IP addresses that can be used as source or destination IPs.
IP pool can be used in 3 different locations and each of them has different behavior:
Delivery: the IP pool will be used as the originating IP when delivering emails to external, but it will NOT be used as the originating IP when delivering to the internal SMTP server.
Receiving: the IP pool will be used as the destination IP for the incoming traffic.
Both: Receiving & Delivery.
Note 1: the Delivery Access control policy has priority over the IP policy, so if the IP pool is applied in both access control & IP policy, only the one in the access control policy will be applied.
Note 2: when the email hits the delivery access control policy, the logs will show only the receiving access control in the policy ID. The matched Delivery access control policy will not be visible. In the policy ID only Receiving access control, IP policy: Recipient policy will be shown as following in the logs:
Note 3: After 7.4.0 Added ACL delivery ID to event logs.
Note 4: before v7.0.1 GA, the IP pool will be ignored when the sender and recipient are protected domain addresses. Starting from v7.0.1 GA, the IP pool will be used and a new CLI command was introduced to have more control on it:
config system mailserver
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.