Just an alternative POV:
t> Main problems [of leafnode]:
t> there is no database for the overview but a collection of directories
t> and symbolic links.
t> Then, first this is inefficient for providing fast overview, second it
t> eats a lot of inodes and your filesystem can easily be full.
Since it is targetted at small sites this is unlikely to be a
t> Expiration is slow and doesn't work well. I have been obliged to remove
t> dead links by hand.
Haven't had the problem, don't care how slow it ios as it runs at night.
t> Third security is next to nil. Better use tcpwrappers to restrict
Again, for the target `market' this doesn't seem to be an issue. No
one outside my network can see the machine it is on in any case. If I
had a network which had a legal address rather than being NATed, or
just one machine, my firewall wouild certainly not pass NNTP
connections from the outside world. Hence security on the server is a
t> In my opinion it is clear that the time spent configuring inn is
t> well spent. It then keeps going without any flaws.
This is probably true if you are running a site big enough to make INN
worthwhile in the first place, but for small organisations/individuals
leafnode's almost instant setup is likely to outweigh the limitations,
which in any case they likely won't hit.