Technical Tip: The debug level syntax has changed in v7.6.3

[vchauhan]

Description	This article describes that in v7.6.3, the debug level syntax has changed.
Scope	FortiMail v7.6.3.
Solution	In v7.6.2 and earlier: diagnose debug application authd 255 diagnose debug enable In v7.6.3 and later: diagnose debug application authd level 255 diagnose debug application authd enable If the old format is used, the system will return a parsing error: diagnose debug application authd 255 Parsing error at '255'. err=1 Command failed(-284). Error string: A correct usage example: diagnose debug application authd level 255 System Time: 2025-09-23 10:45:21 CEST (Uptime: 0d 0h 10m) debug level set to: 255(0xff) debug verbose-debug library-debug library-verbose-debug very-verbose-debug very-verbose-library-debug diagnose debug application authd enable System Time: 2025-09-23 10:45:28 CEST (Uptime: 0d 0h 10m) debug mask: 0x401ff authd debug enabled level : 255(0xff) ... duration: 30 minutes Related document: debug