Well if it wasn't by design then how do you explain this reply from your
support team. quote:
"I've got feedback from engineering on this.
The current behavior is by design, the action for DMARC check failure is
driven by the action next to the DMARC check (action-dmarc) no matter
the DMARC policy (p=) setting."
Which then continued with:
"Thank you for the feedback. I agree that it would be nice to respect
the "none" or give more control over what action should be done in which
case.
But as per update from engineering the current FortiMail behavior is by
design and there is no current plan to change the behavior."
Anyway I am glad that it will be fixed.
Regards
Petr
Dne 25.11.2016 v 10:36 Carl Windsor via dmarc-discuss napsal(a):
Hi DMARC Group, I am the Product Manager @ Fortinet for FortiMail and can
confirm that this was not by design but a bug. As of 5.3 interim build 625 we
respect the p=none directive and this will be rolled in to the next patch
release (5.3.8).
Carl Windsor
_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
