Fix dmarc reject #260
Merged
Fix dmarc reject #260
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
added 4 commits
May 2, 2016 15:31
We cannot reject at this stage, which is only there to alter headers. Fix #258
Followup of #258: we cannot reject a connection during data_post_headers. So add a new hook in data_post to do the real rejection
It's probably possible to have one valid email after an invalid one using the same connection (even if not common)
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.
Add the dmarc_reject note in the transaction instead of the connection. Even if uncommon, it's probably possible to have one invalid and one valid email in a single connection