-
Notifications
You must be signed in to change notification settings - Fork 5
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
Jcbf/fix reply code #34
Conversation
Codecov Report
@@ Coverage Diff @@
## master #34 +/- ##
==========================================
- Coverage 81.18% 78.61% -2.57%
==========================================
Files 1 1
Lines 473 491 +18
Branches 161 166 +5
==========================================
+ Hits 384 386 +2
- Misses 89 105 +16
Continue to review full report at Codecov.
|
Looking good, I understand what the SoftFail feature does now. Perhaps SoftFail is not the best name to choose in relation to this feature, as an SPF SoftFail is defined as Accept Message and Tag as domain is transitioning as indicated by the presence of the ~all tag in the domains SPF record. I understand it is there now as it is, so difficult to change, so perhaps some words in the documentation or config file to explain that by setting SoftFail to on in the config will result in the SPF Failed mails being rejected with a temporary fail status, where the correct response to this from the sending MTA is to defer and try delivery again later. I've just done a quick scan of the code for other such issues and I have a possible bug, so hang fire on the merge. I'll post more shortly. |
Lines 796 to 805 in ba30aa5
Here's another one. In this case we are in a TEMPERROR situation, we set the correct 4.x.x/4xx temp failure codes, but then SMFIS_REJECT instead of TEMPFAILing. That's the only one i could spot. |
1 similar comment
I'm pushing this changes to a new release. |
Many thanks. Graham |
Fix issues identified in #33 by @gwharton.