Fix postfix_warning pattern, solves #84 #85
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
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.
The
POSTFIX_WARNINGpattern did not match any lines that start with a postfix queue id, which resulted in an attempt of thePOSTFIX_KEYVALUEpattern to handle the line.Because of the typical whitespace before a url in the warning message, and the
=character in the query parameters, this made the key-value parser create apostfix_http://example.org/something.html?arg(or similar) fieldname, which is illegal syntax.Solved by fixing the
POSTFIX_WARNINGpattern to pickup the lines correctly.