What's New
The following table summarizes the new features and enhancements in this release. For details, see the FortiMail Administration Guide.
|
Feature |
Description |
|---|---|
| Business Email Compromise(BEC) Enhancements |
Introduced BEC check and action in antispam profiles with BEC rules for cocktail scoring. |
|
Granular Actions for DMARC and DKIM Scan in AntiSpam Profile |
Individual actions can be configured for different DMARC and DKIM scan results. |
|
QR Code URL Scan |
Extract URLs from email body QR code images for FortiGuard and FortiSandbox scan, using the following CLI commands: config antispam settings set qr-code-url-scan-status {enable | disable} end |
|
Malformed HTML Tag Content Handling |
The following CLI command has been added to help handling malformed HTML tag contents for URL click protection: config system fortiguard url-protection set malformed-html-tag-content-action {remove | rewrite} end The default action is "remove" . |
|
Utilize ISDB in ACL |
Added Internet Service Database (ISDB) to the source type in ACL rules. |
|
FortiSandbox Cloud EMEA Option |
Added FortiSandbox Cloud EMEA region option. |
|
DMARC Action and Antispam Profile Action Combination |
FortiMail can now combine non-final actions set in the antispam profile with the actions set in the DMARC DNS record policy. If the antispam profile DMARC actions are non-final, such as "Tag subject" and "Notify", they are combined with the actions in the DMARC DNS record policy: None, Reject, or Quarantine. This happens when: config antispam settings set dmarc-failure-action use-profile-action-with-none (and the sender's DMARC record policy is 'p=none') Or set dmarc-failure-action use-policy-action end |
|
Quarantine Search Based on Release Status |
Added the release status (release or unreleased) as a quarantine search criteria. |
|
Journaled Email Scan |
Added option to scan incoming journaled email when creating a journaling source for archiving. |
|
AWS Snowball Support |
Support AWS Snowball for FortiMail KVM. |