Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include attachments that were failed to be scanned in the scheduled scan report #13

Closed
Enygma2002 opened this issue Nov 15, 2018 · 1 comment

Comments

@Enygma2002
Copy link
Contributor

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.

@Enygma2002 Enygma2002 added this to the 1.2 milestone Nov 15, 2018
@Enygma2002 Enygma2002 self-assigned this Nov 15, 2018
Enygma2002 added a commit that referenced this issue Nov 21, 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.
Enygma2002 added a commit that referenced this issue Nov 21, 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)
@Enygma2002
Copy link
Contributor Author

Enygma2002 commented Nov 21, 2018

  • Report with no errors and no infections:
    antivirus-job-email-report-noerrors
  • Report with errors:
    antivirus-job-email-report-errors
  • Report with infections
    antivirus-job-email-report-infections
  • Report with errors and infections
    (no screenshot available)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant