Group Not Carried

Usenet has no central registry of groups that every server honours. Each operator decides which hierarchies to accept from peers and which to drop, so the set of groups available is a property of one server rather than of Usenet, and it varies widely between providers on the same day. A group command naming anything outside that set returns 411, which newsreaders render variously as no such group, group unavailable, or an unhelpfully generic subscription error.

Which groups get declined, and why

Text-only and budget feeds routinely omit binary hierarchies altogether, since carrying binaries is the dominant cost of running a news server and a text feed can be operated for a fraction of it. Beyond that, operators drop regional trees with no subscribers on their side, groups that have carried nothing but spam for years, groups removed by a control message the server chose to honour, and hierarchies whose administrators require an explicit peering arrangement before feeding them.

One case resolves without intervention: a genuinely new group has to propagate, and a server that has not yet seen the creation message will refuse it for a while. Everything else on the list is a standing configuration decision rather than a transient fault, so waiting accomplishes nothing.

Confirming it instead of assuming it

Adding a group by name in a newsreader creates a local subscription entry; it does not create a group, and the reader will happily display a name the server has never heard of. The authoritative check is the server's own list, retrieved with the LIST command or through whatever group-list refresh the newsreader offers, which reports what the server actually carries rather than what the client remembers. A misspelling anywhere in the hierarchy path produces exactly the same 411, so comparing the exact string against that list is worth doing before anyone is contacted about it.

Options once it is confirmed, and what it is not

Providers will frequently add a group on request when it is legitimately active, and asking costs nothing. Where the missing group belongs to a binary hierarchy on a text-only feed, the question is one of service tier rather than configuration, and no support request changes it. Where a group is carried by some providers and not others, a second source resolves it, which is a straightforward technical fact about how feeds differ rather than a recommendation to buy anything.

Two lookalikes are worth naming. A 430 means the server carries the group but does not hold the specific article requested, which is an entirely different situation involving retention or removal. An empty group is carried and reported with a zero article count rather than refused, so a reader seeing a group open successfully with nothing in it is not seeing this condition at all.