-
Notifications
You must be signed in to change notification settings - Fork 60
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
DKIM broken by "Sign Clean Messages" optiion #544
Comments
That issues can be solved easily by doing **Sign Clean Messages = yes **
|
@rubeldonarman your issue seems different. |
@alexskynet would you please assist for the following issues Body Hash Did Not Verify [DKIM Signature Body Hash] |
@rubeldonarman does it work ok if sendig a new email using any client (p.e. Thunderbird)? |
without MS , DKIM is working perfectly , with MS Body Hash Did Not Verify With MS : Without MS : |
@rubeldonarman may I suggest you to use this test result instead of headers only test? |
Signing of a message will always alter the body and cause the downstream system DKIM to fail. This is the point of DKIM, to see if a message has been altered in transit. The downstream systems should rely on the upstream system to do the DKIM verification prior to the addition of the signature and not do their own DKIM verification from this system. |
I like to add I have Mailscanner v5 with DKMI enabled and a signature on inline.sig.html and don't have any issues with DKMI.. must be a problem on the config.. (I like to clarify that, now I having problems with my email, because the version of exim4 on Debian 10 is more strict on the size.) |
Having a valid DKIM signature from the original sender and then adding additional mail content like MailScanners signature are mutually exclusive by design. The MailScanner signature modifies the content of the mail (which is exactly what DKIM should prevent) and as such the original DKIM signature will no longer be valid. The only way to add the MailScanner signature to a mail and for the endclient to still be able to validate the DKIM signature of the original sender would be to add the original mail as an attachment (which doesn't contain the MailScanner signature) to the mail that where the MS signature was added. But the receiver then has to open the original mail in the attachment manually if he wants to validate that DKIM signature. Same is also valid if MailScanner is configured to disarm links etc. |
I am agree, another way is don't put a signature, (I use a Mailscanner without signature) and put the signature using altermime for example. |
I like to add for the final solution is avoid signatures on mailscanner and put the LOPD or some avisory on the mail using exim.. I can share some details.. and leave mailscanner to avoid modify the mail.. |
This should be mentionend in docs
If you are using DKIM then you have to set the "Sign Clean Messages" option to off.
If not DKIN will be broken and the message is marked by clients as "altered"
The text was updated successfully, but these errors were encountered: