opendkim: improve too-much-header-data log and SMTP reply (issue #143)#344
Merged
thegushi merged 1 commit intoMay 25, 2026
Conversation
…teddomainproject#143) The bare "too much header data" log message gave no context about which message, which header, or what the limit was. Add the job ID, the offending header field name, and the configured limit. Also set a 552 5.3.4 SMTP reply so the sending MTA receives a descriptive error rather than the generic service-unavailable response. The OnSecurity action (default tempfail) still controls accept/reject behaviour. Fixes trusteddomainproject#143
Closed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
"too much header data"log message gave no context - no job ID, no header name, no size infoMaximumHeaderslimit to the log line552 5.3.4SMTP reply so the sending MTA receives a descriptive permanent error rather than a generic service-unavailable responseOnSecurityconfig still controls accept/reject/tempfail behavior; this just makes each outcome more informativeFixes #143
Credit to @andreasschulze for the original diagnosis and proposed approach.