Due to an oversight, one of the header filters has potentially modified
the message body, leading to broken cryptographic signatures.
Switch to the Message-Id instead of the Content-Type header, which is
usually only present in the global header.
Signed-off-by: Moritz Poldrack <git@moritz.sh>
Co-Authored-by: Georg Lauterbach <44545919+georglauterbach@users.noreply.github.com>
Reported-by: Cole Young <cole@young.sh>
Fixes: 009237cc ("chore: Prevent Microsoft MUAs from sending reactions (#4120)")
* feat: add support for MTA-STS for outgoing mails
* Hook-up mta-sts-daemon into basic process handling test
* fix: Call python script directly
The python3 shebang will run it, which will now meet the expectations of the process testing via pgrep. fail2ban has the same approach.
---------
Co-authored-by: Brennan Kinney <5098581+polarathene@users.noreply.github.com>
This was missed during original review.
On a linux host, processes running within a container have been visible via commands like `pgrep`. This is does not appear to be the case with WSL2 + Docker Desktop (Windows), resulting in test failure.
The command should have been run from within the container regardless.