generated from haraka/haraka-plugin-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Release v1.3.0 #9
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
Merged
Merged
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
Pull Request Test Coverage Report for Build 16061014205Details
💛 - Coveralls |
3 tasks
msimerson
added a commit
to haraka/Haraka
that referenced
this pull request
Jul 6, 2025
- Pairs with haraka/message-stream#9 - (tests are broken until the message-stream PR is merged) - fixes haraka/haraka-plugin-dkim#17
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.
While looking into haraka/haraka-plugin-dkim#17, I came across this perverse logic:
Therefore, the default behavior of message-stream is to set
dot_stuffing=false
and remove stuffed dots only whendot_stuffing=false
. This is not intuitive, so I looked at all cases where we handle dot stuffing across Haraka. The closest I got to a good explanation was in the Outbound.md doc:That actually starts to make sense. The variable dot_stuffing isn't a request, it's an indicator. The disconnect is that the naming isn't aligned. Elsewhere in Haraka it was improved to
dot_stuffed
. This PR updates message-stream by renaming dot_stuffing to dot_stuffed and changes the default value from false to true. Our default assumes any content being piped is dot-stuffed and we should remove the dot. The caller can pass{ dot_stuffed: false }
to override.