as trusted | set |
as trusted
Use these commands to configure trusted MTA addresses. If there are any servers within your network that mail travels through before reaching the FortiMail unit, the addresses of these servers would be checked as part of the antispam scans. If spam mail cannot be introduced by these servers, you can exclude them from the antispam checks.
Antispam scanning methods that observe these trusted addresses include FortiGuard Antispam, DNSBL, SPF, and DKIM.
Private network addresses are never checked and do not need to be excluded using this command.
Syntax
set as trusted
set as trusted mta delete <ipv4_mask>
Keywords and variables | Description | Default |
|
|
|
Enter an IP address/mask to add to the FortiMail unit’s |
| |
<ipv4_mask> | list. Addresses on this list are the points past which no addresses will |
|
| be scanned for spam. For example, if a server is at the very edge of |
|
| your network and no servers inside your network will generate spam, |
|
| use the |
|
| edge of the network. Once done, the IP address of the specified |
|
| server, and all servers between it and the FortiMail unit will be ignored |
|
| for antispam scans. |
|
|
|
|
Enter an IP address/mask to delete from the antispam MTA list. |
| |
<ipv4_mask> |
|
|
mta add <ipv4_mask> | Enter an IP address/mask to add to the FortiMail unit’s MTA list. |
|
| Addresses on this list will be ignored by certain FortiMail antispam |
|
| scans. |
|
|
|
|
mta delete | Enter an IP address/mask to delete from the MTA list. |
|
<ipv4_mask> |
|
|
History
FortiMail v3.0 MR3 New.
Related topics
•set as profile modify fortishield
•set as profile modify dnsbl
•set ip_profile sendervalidation
| FortiMail™ Secure Messaging Platform Version 3.0 MR4 CLI Reference |
132 |