-
Notifications
You must be signed in to change notification settings - Fork 149
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
Added HEADER_CHECKS configuration option #15
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
thanks for lovely work. Seems to be OK, but few minor finishing touches would be nice.
Can you please check and revert?
Thank you,
B
header_checks
Outdated
/^Received:.*with ESMTPSA/ IGNORE | ||
/^Received:.*with ESMTPS/ IGNORE | ||
/^Received:.*with SMTP/ IGNORE | ||
/^Received:/ IGNORE |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you just make sure that the lines are aligned?
### `HEADER_CHECKS` | ||
|
||
Each message header line is compared against a pre-configured list of patterns. When a match is found the corresponding action is executed. Set to a non-empty string (usually "1" or "yes") enable. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll need additional description here -- e.g. instructions on how to add the file. This is not apparent from documentation.
Thank you for your review. Can you please check again? |
Thank you, I'll merge this into the main branch but I'll most likely move the |
Hi, after consideration I've renamed your variable to |
Makes sense. |
Description
I added the HEADER_CHECKS 1 option with a sample configuration.
Each message header line is compared against a pre-configured list of patterns. When a match is found the corresponding action is executed.
Type of change
How Has This Been Tested?
I have tested this version of the docker image in a flask application and checked if the headers where ignored or replaced.