Ján Sáreník
Ján Sáreník
It seems the tests are broken anyway. When I run locally, I get: ``` $ ./tests/test-shell.sh ================================= Using /usr/bin/sh Testing ./despf Getting both-spf.spf-tools.eu.org Getting mx20.spf-tools.eu.org Getting a24.spf-tools.eu.org Getting a24.spf-tools.eu.org Getting...
> It seems the tests are broken anyway. > > When I run locally, I get: > > ``` > $ ./tests/test-shell.sh > ================================= > Using /usr/bin/sh > Testing ./despf...
The whole set of scripts was started because of the DNS 255 char requirement in SPF. I am wondering, maybe `mkblocks.sh` is already too far in the chain and does...
Oops, sorry, I misunderstood the question.
That's why there is the `-l` parameter. When it is set to length over 255, it will go beyond the limit... Normal setting is 257 (i.e. 255 + two bytes...
Aah, I see now. Thank you for explanation. I have not explored these options yet. Do you have any idea or a patch?
It's good, though if you want some more recognition, make a new branch and send this as a pull request. See what I have so far: https://github.com/spf-tools/spf-tools/tree/mkearey/255_characters
@mkearey As for me, spf-tools/spf-tools@5fcfbd9483be45a97c596c1dd9f2888e01d7a0d6 is ready to fly. Do you want to change anything? OK to merge?
@mkearey you can always fork and send a pull request. Try it. I want your name in git history.
> Just reading the code and not actually testing but, @jsarenik > > I think you meant : > > ` L) test -n "$OPTARG" && strlength=$OPTARG;;` > > right...