Technical Tip: How to bypass a feature from AntiSpam, AntiVirus, or Content profile for a specific user or group

[ovoda]

Description	This article describes how to bypass a feature for a recipient (or sender) or a group of recipients (or senders).
Scope	FortiMail v7.4.5, v7.6.2.
Solution	In some cases, it is necessary to bypass a feature from AntiSpam, AntiVirus, or Content profile. As an example will be bypassed SPF check for sender safe@example.com. The same way can be used to bypass any feature in any profile. It is also possible to specify if the bypass will be used for a sender or a recipient, or a group of senders or recipients. Consider using the default Recipient policy with an enabled SPF check. This policy matches all senders and recipients: Follow these steps to bypass the SPF check for sender safe@example.com: Clone the AntiSpam profile: In the Cloned AntiSpam profile, disable the SPF: Clone the Recipient policy: In the cloned Recipient policy, specify the Sender Pattern and set the AntiSpam profile created in step 2: By default, the cloned policy will be created above the currently existing policy, so the policy can be triggered. If necessary, move the new Recipient policy to the top of the list to ensure it will be matched:                                                                   As a result, for the sender safe@example.com will be used AntiSpam profile AS_Inbound_NoSPF. The AntiVirus and Content profile will remain the same as for the default Recipient policy.