OmitHeadersDB directive, for a per-recipient list of headers to not s… #173
Conversation
This file contains 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
…ign. The directive specify a tab-separated file with two columns: recipient (as user@domain or just domain) and comma-separated list of headers to not use in signature. For instance, to cope with a miling list that adds a tag in the subject: [email protected] Subject
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this pull request
Apr 22, 2023
list of headers to not use in signature. The file format is: [email protected] header1,header2,header3 domain.tld header4,header5 From upstream trusteddomainproject/OpenDKIM#173
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this pull request
Jul 30, 2024
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.
…ign.
The directive specify a tab-separated file with two columns: recipient (as user@domain or just domain) and comma-separated list of headers to not use in signature.
For instance, to cope with a miling list that adds a tag in the subject: [email protected] Subject