How to setup a news server

4 min read

This tutorial shows the initial setup and basic configuration of INN 2.6.0 on FreeBSD 11.0.

It’s all about usenet—which is probably dying, but I read alot in the internet and found not much information about building your own news server so I decided to write down my findings and my experience.

We will have a look at the setup and the initial configuration to have a news server up and running.


We are going to install InterNetNews 2.6.0 on FreeBSD 11.0. You should have basic knowledge about FreeBSD and its ports. You may also benefit from a routined workflow when compiling ports.

Installation of INN

On the terminal head over to /usr/ports/news/inn and configure the port. make config will help us with that. You can also configure all dependencies at one, use make config-recursive instead. After that, install the port with make install clean.

To start or stop the server as service within FreeBSD you should add the following line to /etc/rc.conf.


This will also start the server after boot.


The basic configuration is pretty simple. You find many information in the manpages of inn.conf, ctlinnd, readers.conf, active, newsgroups and moderators.


INN installs within /usr/local/news/. Configuration files reside in /usr/local/news/etc/.

We will make basic settings or changes in inn.conf.

organization:    "A very local News Site"


This files defines the access rights on the news server. My readers.conf looks like this:

# auth block

auth "default" {
  auth: "/usr/local/news/bin/auth/passwd/ckpasswd -f /usr/local/news/etc/.passwds"
  default: "<FAIL>"

auth "localhost" {
    hosts: "localhost,, ::1, stdin"
    default: "<localhost>"

# access block

access "users" {
  users: "*,!<FAIL>,!admin@*"
  newsgroups: "*,!control,!control.*,!junk"
  #nnrpdauthsender: true
  access: RP

access "fail" {
  users: "<FAIL>@*"
  newsgroups: ","

access "admin" {
  users: "admin@*"
  newsgroups: "*"
  access: RPA
  perlfilter: false

access "localhost" {
    users: "<localhost>"
    newsgroups: "*"
    access: RPIANL

A client that connects on the local interface gets all rights RPIANL—for detailed information about rights and its descriptions have a look at the manpage of readers.conf. Look at ACCESS GROUP PARAMETERS.

With this configuration any client can see the newsgroups and The latter is also writable to post a question for an admin. All other newsgroups are hidden.

A useraccount on the newsserver can see the dominicreich.* hierarchy. He can also post in there.


To save our articles forever, we add this line into expire.ctl:



To allow control messages for newgroup and rmgroup add this to control.ctl*:doit*:doit

Watch out! There is no verification yet implemented. A fake message from would add or delete groups. If you plan to use your newsserver on a production environment you should probably think about a good implementation of any kind of user verification.

If you don’t need these control messages, use the default value all:*:*:drop and delete the rest.


I addes this line:


The file’s syntax is described in the header of the file itself. Usually there is %s in the local part of the mail address.

Group management

Groups are managed with the tool ctlinnd. Let’s add a test group to our configuration.

# ctlinnd newgroup dominicreich.test y

And a deletion would look like this:

# ctlinnd rmgroup dominicreich.test

Files in /usr/local/news/db


The active file contains the managed newsgroups. ctlinnd make changes in this file.

A fresh file looks like this:

control 0000000000 0000000001 n
control.cancel 0000000000 0000000001 n
control.checkgroups 0000000000 0000000001 n
control.newgroup 0000000000 0000000001 n
control.rmgroup 0000000000 0000000001 n
junk 0000000000 0000000001 n


The newsgroups’ descriptions are held in this file.

A fresh file:

control             Various control messages (no posting).
control.cancel      Cancel messages (no posting).
control.checkgroups Hierarchy check control messages (no posting).
control.newgroup    Newsgroup creation control messages (no posting).
control.rmgroup     Newsgroup removal control messages (no posting).
junk                Unfiled articles (no posting).

Add users to your configuration

I created my userfile manually—with openssl. You can also use the tool htpasswd (which usually gets installed with the Apache webserver). When using htpasswd make sure to use crypt for password encryption.

$ openssl passwd -crypt
Verifying - Password:

It’s output is saved together with a username in your specified password file. I chose /usr/local/news/etc/.passwds—look in readers.conf where I specified this file.


Restart INN

To save changes you want to restart the newserver.

# service innd restart
Stopping innd: .
Starting innd.
Scheduled start of /usr/local/news/bin/innwatch.

More configuration

You can hide the host that injected the message with those lines in inn.conf.

addinjectiondate:            true
addinjectionpostingaccount:  false
addinjectionpostinghost:     false

That removes the hostname and the ip address of the sender. With addinjectionpostingaccount the users accountname (specified in readers.conf) gets added to Injection-Info.

Let’s have a look on some examples.

All information in Injection-Info header line

From: User <>
Newsgroups: dominicreich.test
Subject: Re: testpost for the testgroup
Injection-Date: Mon, 3 Apr 2017 20:16:38 +0000 (UTC)
Injection-Info:; posting-account=""; posting-host="";
        logging-data="58264"; mail-complaints-to=""

Only the user account in Injection-Info header line

From: User <>
Newsgroups: dominicreich.test
Subject: Re: testpost for the testgroup
Injection-Date: Mon, 3 Apr 2017 20:15:48 +0000 (UTC)
Injection-Info:; posting-account="";
        logging-data="57952"; mail-complaints-to=""

All info removed—but with additional Sender header

From: User <>
Newsgroups: dominicreich.test
Subject: Re: testpost for the testgroup
Injection-Date: Mon, 3 Apr 2017 18:15:07 +0000 (UTC)
        logging-data="54917"; mail-complaints-to=""

For this you also have to uncomment the commented line in the readers.conf users access block. Uncomment nnrpdauthsender: true and the sender header gets added.


This is a basic configuration. I do not own a newserver nor did I ever owned one. I have read a lot of information when I initially wrote this tutorial (which was back in 2017). You should definitly read more about this topic when you want to set your own server up.

Hints, suggestions or critic can be sent to me per mail or comments. Thank you!

Enjoyed this content?

Help keep it free by sending a donation or purchasing something from my Amazon Wish List. You can also subscribe to various site feeds to get notified of new posts or follow me on social media.

Leave a comment

Explore more:


↑ back to top