-
Notifications
You must be signed in to change notification settings - Fork 418
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Include support for exists element in SPF. #356
Conversation
What's the best way to test these changes? |
Awesome to hear that somebody is using this kinda fringe feature! I had to dig into the spec on this one. exists is a part of spf I was hoping wasn't widely used. Apparently I was wrong. Apparently So my question is: are there any situations where a macro will expand to cause multiple lookups, or will it always be one? Reading the spec I suspect not, but my eyes kinda glazed over after a while. If that is the case, I have no reason not to include this. Thank you! |
With regards to testing, the tests in that package are not very robust. You could probably add an exists clause to the test here I'd love to hear ideas if you have a good way to test all of this better. But I wouldn't block this for that. |
Thanks for the fast response. My hope is that the SPF support simplifies the management of our SPF records in the long run. From my reading of the RFC, I can't see a situation where the expansion would cause multiple lookups. Section 5.7 says
In terms of testing, we could include an entry using |
The change looks good. Please add an "exists:" example to dnscontrol/pkg/spflib/parse_test.go then we'll merge the PR. |
Forgot to let you know that I have added the example into the tests. |
* Include support for "exists" element in SPF. * Add exists: SPF entry to test support
Hi,
Related to issues #355, I suspect it would only take a simple change of the handling for the
exists:
element to work, however I could be very wrong (and totally happy for you to tell me so).