• INN 2.x FAQ (3/3)

    From Russ Allbery@21:1/5 to All on Sat Nov 21 08:01:04 2020
    [continued from previous message]

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Dec 21 08:01:02 2020
    [continued from previous message]

    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Jan 21 08:01:03 2021
    [continued from previous message]

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun Feb 21 08:01:02 2021
    [continued from previous message]

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun Mar 21 07:01:03 2021
    [continued from previous message]

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Wed Apr 21 07:01:04 2021
    [continued from previous message]

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Fri May 21 07:01:04 2021
    [continued from previous message]

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Jun 21 07:01:04 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Wed Jul 21 07:01:02 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sat Aug 21 07:01:03 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Tue Sep 21 07:01:03 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Oct 21 07:01:04 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun Nov 21 08:01:02 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Tue Dec 21 08:01:02 2021
    [continued from previous message]

    individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header which is more widely used for that purpose. Accordingly, INN does
    not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header

    There is no built-in support for suppressing generation of the
    Injection-Info header. You can, however, remove it from inside a Perl
    posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header effective in the actual posted article. Instead of removing the
    header, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the
    virtualhost: and domain: parameters in readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Fri Jan 21 08:01:03 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Feb 21 08:01:02 2022
    [continued from previous message]

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Mar 21 07:01:04 2022
    [continued from previous message]

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Apr 21 07:01:03 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sat May 21 07:01:04 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Tue Jun 21 07:01:02 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    You can ask for an external feed in the news.admin.peering newsgroup.
    Several news administrators will certainly respond and gracefully provide
    you with a news feed. And why not keep subscribed to this newsgroup to
    help others find a news feed once you get yours?

    You then have to parameter the NNTP feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Jul 21 07:01:02 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun Aug 21 07:01:04 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Wed Sep 21 07:01:02 2022
    [continued from previous message]

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Fri Oct 21 07:01:03 2022
    [continued from previous message]

    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Nov 21 08:01:04 2022
    [continued from previous message]

    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Wed Dec 21 08:01:02 2022
    [continued from previous message]

    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sat Jan 21 08:01:03 2023
    [continued from previous message]

    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the virtualhost: and domain: parameters in
    readers.conf.

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Tue Feb 21 08:01:02 2023
    [continued from previous message]

    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Fri Apr 21 07:01:01 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun May 21 07:01:03 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Wed Jun 21 07:01:04 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Fri Jul 21 07:01:04 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Mon Aug 21 07:01:03 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Sep 21 07:01:03 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sat Oct 21 07:01:04 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From KP2 KP2@21:1/5 to Russ Allbery on Mon Nov 6 18:01:38 2023
    [continued from previous message]

    servers using the peer-to-peer portions of the NNTP protocol. However,
    with some additional software, it is also possible to use INN as, in essence, a local cache for a news server that you can use to read and post but which doesn't treat your server like a peer.

    This configuration is generally called a "suck" feed, because rather than having news fed directly to your server, you pull it down or "suck" it
    from another news server, and because possibly the first and one of the
    most widely used packages for doing this is named suck.

    The software to pull down articles from another server and to feed
    articles to another server using post rather than peer-to-peer commands
    does not come with INN (INN has a few utilities to do this on a small
    scale, but not really anything designed to handle a lot of groups or a lot of articles). You will need an external package to do this. The two most popular are suck and newsx; however, both sites appear to be unavailable
    as of thos writing. You may be able to find a package in your local distribution or package repository.

    Note that current versions of INN refer to articles internally using a storage API token, not a path name, which is not always what suck or newsx expects. Read the documentation carefully; you'll need to use a script or configuration that retrieves articles using the sm program that comes with INN rather than trying to open files directly.

    It's also worth noting that INN is a fairly complex package, and while
    many people are running it successfully using this sort of configuration
    and like having a full-fledged news server available to them, other people have found INN rather complicated and difficult to configure for a small, simple personal news cache. If your needs and goals are simple and the number of groups you're interested in is small, you may be better off with
    a smaller, lighter package such as LeafNode or NNTPcache.

    ------------------------------

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh` MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1> <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file for the proper operation of INN, so you can't remove the groups entirely. You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of users saying things that they didn't, runs the risk of corrupting messages by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN does not support this, or any other modification of the body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do this (as well as any other modifications and internal filtering that you want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost: for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand them off to nnrpd as appropriate. It is, however, becoming increasingly common to run innd and nnrpd on separate ports for a variety of reasons, such as wanting to handle connections to nnrpd with a smart network connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port 433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that port.

    Now, set port in inn.conf to the port you want to run innd on and add noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as any custom authentication programs or files you're using (like a password file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that they retain for a long time (like local hierarchies) and don't bother with all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration files.
    Good read.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Tue Nov 21 08:01:03 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Thu Dec 21 08:01:03 2023
    [continued from previous message]

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can
    possibly modify messages that arrive via a suck/rpost connection. It also
    adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN
    does not support this, or any other modification of the body of a message
    from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the man pages of these configuration
    files.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Russ Allbery@21:1/5 to All on Sun Jan 21 08:01:02 2024
    [continued from previous message]

    a smaller, lighter package such as LeafNode or NNTPcache.

    ------------------------------

    Subject: 6.8. Generate MRTG graphs for INN

    INN's CNFS storage system has direct support for producing information
    suitable for MRTG graphs on the usage of the CNFS cycbuffs. Running
    cnfsstat -m <cycbuf> will generate output suitable for MRTG, and running cnfsstat -p will generate sample MRTG configuration fragments for each
    cycbuff.

    To generate MRTG graphs of the usage of the buffindexed overview system,
    try the following configuration fragment:

    Target[overview-BUFF]: `/usr/local/etc/mrtg/overview.sh`
    MaxBytes[overview-BUFF]: 100
    Title[overview-BUFF]: BUFF1 Usage
    Options[overview-BUFF]: growright gauge
    YLegend[overview-BUFF]: Overview Buffers
    ShortLegend[overview-BUFF]: %
    PageTop[overview-BUFF]: <H1>Usage of Overview Buffers</H1>
    <BR><TT>overview</TT>

    where the overview.sh script is:

    #!/bin/sh
    echo "100"
    <pathbin in inn.conf>/inndf -o | awk '{print $1}'
    echo "0"
    echo "overview"

    This sample configuration is from Basil Kruglov. Note that you can
    instead use -n (for total count of articles); in that case, you'll want to remove the MaxBytes setting above or change it to be some sensible limit
    on the total number of articles you receive. You'll also want to change a
    few of the other labels in the MRTG configuration.

    I'm not aware of any packaged solutions for generating MRTG data from
    other things, such as incoming or outcoming news flows. If anyone has any pointers, let me know.

    ------------------------------

    Subject: 6.9. Hide the junk and control groups from users

    The junk, control, and control.cancel groups must exist in the active file
    for the proper operation of INN, so you can't remove the groups entirely.
    You can, however, hide them completely from users.

    To do this, edit readers.conf, and for each user access group where you
    want to hide the junk and control groups, add "!junk,!control,!control.*"
    to the newsgroups pattern. In other words, if you have a line like:

    newsgroups: *

    just change that to:

    newsgroups: *,!junk,!control,!control.*

    If you use read and post patterns instead, do the same for each of them individually. The groups will then no longer show up on the server for
    users to which that access group applies; it will be as if they do not
    exist.

    ------------------------------

    Subject: 6.10. Modify the body of posts made through my server

    You can't without either making code changes to INN or putting your own software in the path of incoming posts. This is intentional.

    Some sites like to try to append a standard signature to all posts through their service, generally as advertising. This creates the appearance of
    users saying things that they didn't, runs the risk of corrupting messages
    by appending text without regard to what's in the message, and can possibly modify messages that arrive via a suck/rpost or pullnews/rnews connection.
    It also adds advertising in an obnoxious location, rather than in the Organization header field which is more widely used for that purpose. Accordingly, INN does not support this, or any other modification of the
    body of a message from inside the news server.

    If you only want to do this for a private hierarchy, the easiest way to do
    this (as well as any other modifications and internal filtering that you
    want to perform) is to mark all of the groups as moderated and route all submissions through a script that makes whatever modifications you want
    and then posts the messages with an Approved header field.

    If you want to do this in order to advertise your service, please
    reconsider. You can add your advertisements to the headers, like many
    other news service providers.

    ------------------------------

    Subject: 6.11. Hide the Injection-Info header field

    There is no built-in support for suppressing generation of the
    Injection-Info header field. You can, however, remove it from inside
    a Perl posting filter. Try using a posting filter like this:

    sub filter_post {
    $modify_headers = 1;
    delete $hdr{'Injection-Info'};
    return '';
    }

    Note that you have to set $modify_headers to make changes to the article
    header field effective in the actual posted article. Instead of removing
    the header field, you can also alter it if you modify
    $hdr{'Injection-Info'}. If you only want to alter the host name used in Injection-Info, see the domain: parameter in readers.conf (and virtualhost:
    for INN 2.7.0 and earlier).

    ------------------------------

    Subject: 6.12. Run innd and nnrpd on separate ports

    Originally, innd was designed to handle all incoming connections and hand
    them off to nnrpd as appropriate. It is, however, becoming increasingly
    common to run innd and nnrpd on separate ports for a variety of reasons,
    such as wanting to handle connections to nnrpd with a smart network
    connection handling daemon like xinetd that can do things like rate
    limiting of connections. INN does support this configuration, but be
    warned that since you need to run nnrpd on port 119 for most reader
    clients to be able to find it, you'll need to tell all of your news peers
    to use a different port to feed you news.

    The recommended alternate port for innd transit-only connections is port
    433, which has been reserved for that purpose. If you want to use some low-numbered port (less than 1024) other than 119 or 433 for innd, you
    will need to build INN with the --with-innd-port option specifying that
    port.

    Now, set port in inn.conf to the port you want to run innd on and add
    noreader: true (so that innd will never attempt to hand connections off to nnrpd). Then, restart INN. It will now be listening on the new port.
    You should now set up nnrpd to run via xinetd, inetd, tcpserver, or
    some other similar network connection handling daemon on port 119. Make
    sure that nnrpd is run as the news user, not as root. You don't have to
    pass any arguments to nnrpd (unless you want to).

    ------------------------------

    Subject: 6.13. Back up and restore an INN installation

    (This entry is based on a post by Jeffrey M. Vinocur.)

    For a full backup, you need, at a minimum, to save all of the articles in $patharticles, the configuration files in $pathetc, and the active and newsgroup files in $pathdb. If you have any custom filters you've
    installed, or a cleanfeed.local file, you'll want to keep that, as well as
    any custom authentication programs or files you're using (like a password
    file for news accounts). You may also want to save HTML versions of the news.daily reports, if you've been generating them, and you may want to
    look at the first few lines of config.status in your original source tree
    so that you can be sure to use the same options to configure.

    Note that most people only back up those portions of the news spool that
    they retain for a long time (like local hierarchies) and don't bother with
    all the regular Usenet articles.

    It's considerably easier to back up and restore articles from tradspool
    than any other storage mechanism, and it's quite hard to back up and
    restore timecaf or CNFS. Remember that you can use different storage
    methods for different articles. I highly recommend saving the hierarchies
    you want to back up in tradspool and use the higher-performance storage mechanisms for news you don't care as much about.

    To restore a single newsgroup using tradspool and the tradindexed overview method, you can just restore the articles into the news spool and then
    rebuild overview for just that group with tdx-util -R.

    Otherwise, for more general restorations, compile INN on the new system
    with the same ./configure command if you've lost the installation, run
    make install, then put all the pieces back where they belong. Now, you
    have to run:

    makehistory -O

    to rebuild the history and overview databases. When that finishes, cd to
    the $pathdb directory and run:

    makedbz -s `wc -l < history` -o

    You should now be able to start the server and read and post news to it.

    ------------------------------

    Subject: 6.14. Find external feeds and set up peering

    One way to find peers is to ask for an external feed in the
    news.admin.peering newsgroup. Some news administrators read that group
    and may be willing to peer. It's common for news administrators to have different criteria for peering (specific hierarchies, geographic or
    network proximity, spam filtering, no binaries, binaries, specific network protocols; the variation is endless), so finding someone with matching
    goals may require some patience and possibly some configuration changes.
    And why not keep subscribed to this newsgroup to help others find a news
    feed once you get yours?

    You will then have to configure your new feed in incoming.conf, newsfeeds
    and innfeed.conf (assuming you'll use innfeed, the most common way to feed articles). Follow the examples in the manual pages of these configuration files.

    If you need importing old articles, you may want to use pullnews. See its manual page for more information about how to use it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)