You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, scan errors are reported only to the server logs and, if the admins don't check them, they might not notice that some attachments failed to be scanned and could allow potentially infected files to remain undetected.
Similarly to how we include failed deletions in the report (when an infection is found but failed to be deleted), so should we include failed scans, in a dedicated section of the report.
The text was updated successfully, but these errors were encountered:
…can report #13
* Refactored the report's format
* Removed the plaintext report email's version to limit duplication. HTML support is to be expected in 2018.
…can report #13
* Refactored the report's format
* Removed the plaintext report email's version to limit duplication. HTML support is to be expected in 2018.
(cherry picked from commit 9fc07f0)
Currently, scan errors are reported only to the server logs and, if the admins don't check them, they might not notice that some attachments failed to be scanned and could allow potentially infected files to remain undetected.
Similarly to how we include failed deletions in the report (when an infection is found but failed to be deleted), so should we include failed scans, in a dedicated section of the report.
The text was updated successfully, but these errors were encountered: