On Tue, Aug 12, 2025 at 4:39 AM Philip Homburg <pch-ietf-8@xxxxxxxxxxxxxx> wrote:
> However, two useful details have been exchanged that at least
> clarify some possibilities:
>
> 1. It appears my IPv6 address for my new server instance has been
> swept up into a spamhaus PBL entry. This wasn't the case during
> initial setup and prior rounds of triage, but it'll certainly cause
> issues now.
>
> 2. It appears the provider I'm attempting to use, Hostinger, has
> made it onto sufficient other hidden black lists that the address
> ranges are problematic.
>
> So, the issues are not configuration, they're collateral damage,
> and there's diddly squat I'll be able to do about the issue aside
> from "move somewhere more reputable".
>
> Unfortunately, good luck finding "somewhere more reputable".
Long term, we have plenty of IPv6 addresses. So in theory you can get your
own IPv6 prefix (or together with some friends) have it routed and use that.
No you cannot. Or rather you can as a special case but an internet with 8 billion prefixes under independent control routing over the core is outside the parameters systems are built for. It's not just Spamhaus that is designed with assumptions of how many independent IP allocations it needs to route.
The assumption that large-ish chunks of IP space route in similar fashion is part of what keeps the system working.
If you want to have personal IPv6 space, you certainly can but it has to be non-routable, at least as far as the Internet is concerned. Private addresses are for routing over VPNs...
The solution to this problem is to change the email system to one that doesn't require ad-hoc hackery like the Spamhaus block list. And building such a system is actually quite easy: every user has an identity bound to a public key, every message is signed, only authorized messages are delivered. Could give you a spec and working code for that in three months, easy,
The hard part, the only hard part is changing the email system. How do we get from where we are to where we want to be?
