mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #14] DKIM computed bodyhash fails when used with encryption #64
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#64
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @anonaddy on GitHub (Dec 20, 2019).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/14
Emails forwarded to custom domains (with sending verified) need to be signed by DKIM (selector dk1 or dk2).
This fails to pass DKIM checks when the email is also encrypted using GPG encryption.
DKIM checks fail due to the "Computed body hash is different from the expected one".
At the moment I've set it to not sign outgoing messages with DKIM for custom domains if they are also encrypted until I can find a solution.
@erik-h commented on GitHub (Feb 15, 2020):
@anonaddy Any updates on this issue? I'm loving forwarding using my custom domain, but it'd be great to be also able to enable GPG encryption again.
@anonaddy commented on GitHub (Feb 15, 2020):
@erik-h will look into this at the start of next week to see if I can find a solution. Thanks for reminding me.
@erik-h commented on GitHub (Feb 15, 2020):
@anonaddy Awesome, thanks for the response!
@willbrowningme commented on GitHub (Feb 18, 2020):
@erik-h This issue has now been fixed in the latest release.
It was solved by updating some LFs -
\nto CRLFs -\r\n.https://github.com/anonaddy/anonaddy/commit/3056f5aed4ffff8fd0f688869433fafdcea648ab#diff-bc5a3d7c8332409aed797d25d7cdd2da
@erik-h commented on GitHub (Feb 21, 2020):
@willbrowningme Ah I see, awesome, thanks again!