-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat!: DKIM verifier with https fallback #35
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
Open
j-g00da
wants to merge
2
commits into
main
Choose a base branch
from
j-g00da/dkim-verify
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Few notes:
|
link2xt
reviewed
Feb 5, 2026
1150907 to
da063fd
Compare
36a0f0e to
41237b3
Compare
Collaborator
Author
|
TODO:
|
Collaborator
Author
|
Also:
|
41237b3 to
7482b51
Compare
This implements a DKIM verification as well as a strict DKIM signature alignment check with domain in `From` header address. Additionally, provides a fallback mechanism that retrieves TXT record over HTTPS from a location: `<domain>/.well-known/_domainkey/<selector>` if DNS lookup fails, expecting a plain text RDATA. Caches the retrieved RDATA using in-memory LRU. BREAKING CHANGE: incoming messages now require DKIM signatures aligned to domain of the `From` header address. Signed-off-by: Jagoda Ślązak <jslazak@jslazak.com>
Signed-off-by: Jagoda Ślązak <jslazak@jslazak.com>
7482b51 to
fa57846
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This implements a DKIM verification as well as a strict
DKIM signature alignment check with domain in
Fromheader address.
Additionally, provides a fallback mechanism that retrieves
TXT record over HTTPS from a location:
<domain>/.well-known/_domainkey/<selector>if DNS lookup fails, expecting a plain text RDATA.
Caches the retrieved RDATA using in-memory LRU.
BREAKING CHANGE: incoming messages now require DKIM signatures
aligned to domain of the
Fromheader address.Signed-off-by: Jagoda Ślązak jslazak@jslazak.com