Well just so you know, I reported this bug to FortiNet almost a year
ago 2015-12-09. That was when FortiMail got the DMARC
implementation(firmware 5.3.0). Since that time we contacted their
support, which gave us the answer I posted. So we tried to change it by
contacting local Fortinet's representative but all he could do was
create a new feature request.
The problem is, when Fortinet's engineering says it's by desing and not
a bug there is nothing you can do to change that or maybe I just didn't
have the right contacts high enough :). Anyway I am glad they will fix it.
Regards
Petr
Dne 28.11.2016 v 10:59 Roland Turner via dmarc-discuss napsal(a):
Petr,
Do you also kick small dogs? I'd suggest that a 2-week turnaround on
a bug that's non-critical for Fortinet's customers is pretty
impressive.
On the meaning of "by design", there are of course multiple designs
(intentions) present. Surely you're familiar with the tree-swing
project management cartoon? You know this happens all the time in
real engineering organisations, right?
http://www.tamingdata.com/wp-content/uploads/2010/07/tree-swing-project-management-large.png
- Roland
_______________________________________________
dmarc-discuss mailing list
dmarc-discuss@dmarc.org
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)
