On Tue, Dec 06, 2022 at 02:35:44PM +0100, Wolfgang Breyha wrote:
> Hi!
>
> I'm using SA 4 trunk and tried the urinsrhsbl. Not sure if this is a bug or
> abuse on my side.
>
> I already have two RBLs... one
> uribl.example.at
> and one
> uriblfull.example.at
>
> The first does not use "tflags notrim", the second does.
>
> Now I added a lookup for uribl.example.at like
> urinsrhssub __URIBL_ZID_16 uribl.example.at. A 16
> body __URIBL_ZID_16 eval:check_uridnsbl('__URIBL_ZID_16')
> tflags __URIBL_ZID_16 net domains_only
> But if I check the debug output I see checks for the FQDN of all three NS
> RRs instead of one lookup for the trimmed NS domain.
>
> According to the man page of URIBLDNS this should only happen if
> urifullnsrhssub is used?
>
> Why are there two variants urinsrhssub/urifullnsrhssub? And what happens if
> "tflags notrim" is used with them?
>
> Is it even valid to use urinsrhssub on a RBL where urirhssub is used as
> well? I felt quite comfortable to do so since it was the easiest way to add
> support for NS listings with an existing uribl.
I would just create a bug, preferably with tested examples of all variants.
:-) Most than likely there has been some oversights with legacy code and
notrim addition, *nsrhs* isn't even used in stock rules.
