I ran into this issue on our FortiMail and wanted to let you know:
We found a mail going out of the FML that should have been quarantined due to failing DMARC check.
However the mail went through to the user even without any filtering. The log only states the failing DMARC check but no action and no further checks/filters while there is more checks/filters in the recipient policy and also the antispam profile in the policy does specify the action to quarantine it upon failing DMARC check.
I opened a ticket with TAC on this and they sent me to the right path:
The reason is a new option which was introduced in 7.4.0 first. Since 7.4.0 there is a dmarc generic action option in security=>options=>antispam. Per factory default this is set to not perform any action.
This leads to the FML still detecting a failed DMARC check but ignore any specified action. However due to the failing DMARC check it still skips the rest of the checks/filters and lets the mail out completely unfiltered!
This option was never mentioned in 7.4.0s release notes as a new option and even the admin guide only describes it at where it is in the menue (under security=>Preferences) but has no further references to it.
Unfortunately it renders your DMARC Check rather useless and creates a security risk because mails go out unfiltered.
So I recommend anyone to check their FortiMail and reset that option to perform the specified action!
I am still on this with TAC also.
Cheers
Sebastian
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
Thanks for sharing, sw2090.
Do you confirm this behavior is the same with 7.4.5 (highest patch)? Or does it affect only 7.4.0?
If I understand well the default DMARC config cancels all checks and delivers the mail, right? So this is obviously a bug, because all other checks should be applied even if DMARC or any other check fails. However I can't find such bug in the release notes of any 7.5.x version.
yes I confirm that!
It was introduced with 7.4.0 I guess since the admin guide of the last 7.2 does not mention it at all.
I would predict it also exists in 7.6 but since we are on 7.4 I cannot confirm this.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
and yes you understand that correctly. However I am not sure if that is a bug. If there is an action to perform which is to defer or quarantine the mail then the cancellation of anything further would probably be correct. However it should not if there is no action being performed. I think the bug is that it does ignore the action in first case so nothing is done but onprocessing the mail it still "sees" the action in the profile and thinks the mail went to quarantine so it doesn't need further checks/filtering right now.
I've anyways asked TAC about this but they didn't yet reply.
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
Hi sw
Any update from TAC? Curious to know.
User | Count |
---|---|
2647 | |
1405 | |
810 | |
690 | |
455 |
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 2025 Fortinet, Inc. All Rights Reserved.