We're also sending out e-mails with EXIM 4.71 from a PHP program. DKIM can be allowed and will be working properly, unless when delivering a specific kind of mails, which benefits indkim=neutral (body hash did not verify).
The DKIM signature includes a hash over the body of the mail. This hash is created from the source code of the body as seen by the signing server. Any changes to the body during transport will thus invalidate the signature. Dkim body hash not verified. This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. On May 8, 2019 at 09:36 UTC. Microsoft Office 365. Needs Answer. Next: outlook. Get answers from your peers along with.
The kind of e-mail which falters contains a message joined via a HTML form on the site, and some other mails delivered from this application are great. I have got happen to be suspecting blended collection endings to be the culprit, but haven't become able to enhance the scenario by normalizing range endings.
Is definitely EXIM carrying out some washing after it creates the DKIM hash?
Any ideas?
Oscar
OscarOscar
1 Response
This has been very unusual, but the adhering to appears to be true:
This does not work, ending in DKIM body hash fail
But this works as it should
Not the area before the last LF.
OscarOscar