Log the contents of the failed mail and attachment(s).

[wgresshoff]

❤️ Thank you for your contribution!

Description

When the retry mechanism finally fails the contents of the mail and the attachments will be logged so admins get informed.

Checklist

Ticks in all boxes and 🟢 on all GitHub actions status checks are required to merge:

• I'm aware of the code of conduct.
• I've created logical separate commits and followed the commit message format.
• I've added relevant test cases.
• I've added relevant documentation.
• I've marked translation strings.
• I've identified the copyright holder(s) and updated copyright headers for touched files (>15 lines contributions).
• I've NOT included third-party code (copy/pasted source code or new dependencies).
  • If you have added third-party code (copy/pasted or new dependencies), please reach out to an architect.

Frontend

• I've followed the CSS/JS and React guidelines.
• I've followed the web accessibility guidelines.
• I've followed the user interface guidelines.

Reminder

By using GitHub, you have already agreed to the GitHub’s Terms of Service including that:

1. You license your contribution under the same terms as the current repository’s license.
2. You agree that you have the right to license your contribution under the current repository’s license.

[Samk13]

Logging attachment data, the full message body, and recipients might expose sensitive information, don't you think?
Would it be better to e.g. redact the body and only log the number of attachments instead?

[wgresshoff]

We have a very special use case here in Münster so this is done under just some special circumstances:

• the retries have come to an end
• the log is at debug level and has to be switched to this by configuration

We only send mails when data is archived and a certificate for the funders is needed (which is in the attachment) about it. And made sure there is no sensible information included.