-
-
Notifications
You must be signed in to change notification settings - Fork 444
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
Bug: DKIM Failure for Emails with Content-Type: text/html #2165
Comments
I've got similar issue. My mail go to spam most of the time (DMARC set to quarantine wrong DKIM). Probably due to encoding issue. I use OpenDkim or RSPAMD and let know SL to not doing it:
It could be great to have that part working without the need of external tools. Or if it's not possible, then explain for self-hosting how to setup it using an external tools. |
Thanks for sharing your solution! It would be beneficial if this could work without relying on external tools. I will work on this this weekend. Thank You. I really appreciate it |
@celogeek do you have any links to follow the installation? I set it up, but it's not signing outgoing emails for some reason. |
For 1 domain, this one is pretty ok: https://wiki.debian.org/opendkim |
Thank you appreciate your help |
i'm still getting dkim fail
|
I was able to fix it. Using the reference above. Wish simplelogin would provide a fix |
Amazing! Thanks for this now all three SPF, DMARC and DKIM is working after some troubleshooting :) |
Description:
Emails sent with
Content-Type: text/html
are failing DKIM checks, resulting in a "dkim=fail (body hash mismatch)" error. However, when emails are sent withContent-Type: text/plain
, they pass DKIM checks without any issues.Steps to Reproduce:
Expected Behavior:
Emails sent with
Content-Type: text/html
should pass DKIM checks just like emails sent withContent-Type: text/plain.
Actual Behavior:
Emails with
Content-Type: text/html
fail DKIM checks with the error "dkim=fail (body hash mismatch)", whereas emails with Content-Type: text/plain pass DKIM checks.The text was updated successfully, but these errors were encountered: