public inbox for dbl@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: dbl@lists.ipfire.org
Subject: Re: postcodeloterij.nl in Gambling category
Date: Mon, 16 Mar 2026 10:26:09 +0000	[thread overview]
Message-ID: <F024AB15-8775-43A6-AB66-442DFCC40C4B@ipfire.org> (raw)
In-Reply-To: <f06d2e6f-0ea9-407b-b418-e714311df7d0@ipfire.org>

Hello Adolf,

Thanks for raising this. There seems to be a problem here indeed.

> On 13 Mar 2026, at 17:49, Adolf Belka <adolf.belka@ipfire.org> wrote:
> 
> Hi All,
> 
> postcodeloterij.nl is in 5 of the lists in the gambling category but I was finding that it was not being blocked.
> 
> I checked and found that the domains file in the URL Filter blacklists directory did not have the postcodeloterij.nl domain in it. That obviously is why it was not being blocked.

Correct. Since you reported the domain as missing and Stefan accepted the report, I cannot reproduce the problem any more unfortunately.

> I have reported in in the reporting system but am also reporting it here as it is not that the lists have it and shouldn't or the lists haven't got it and should, it is that the lists have it but it seems to get filtered out when the domains list is created.
> 
> In the How to use section there are links to https://dbl.ipfire.org/lists/gambling/domains.txt and this has no entries for postcodeloterij.nl in it.
> 
> It looks like somehow in the creation of the gambling domains.txt file the postcodeloterij.nl entries are not included for some reason.

This is fixed now.

I analysed my algorithm that is actually pulling all domains from the lists and removing anything we don’t want to export. This seems to be working well.

The problem itself seems to be in the dead checker. I have found a couple of more domains that seem to have been removed from the list because the checker assumes that they are dead which they are not. I manually ran the checker again on the affected domains and of course they came back just fine :)

So I am not sure where to go from here. Generally it is a good idea to remove completely dead domains, but what is it worth if this is not 100% accurate.

We could still run the dead check to have a feeling about what our upstream sources are giving us and simply always export everything. That way, we are always on the safe side. The downside is that the lists would at least double in size which means more bandwidth and more memory usage for no reason.

-Michael

> Regards,
> 
> Adolf.
> 
> 



      reply	other threads:[~2026-03-16 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 17:49 Adolf Belka
2026-03-16 10:26 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F024AB15-8775-43A6-AB66-442DFCC40C4B@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=adolf.belka@ipfire.org \
    --cc=dbl@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox