INN FAQ Cookbook example of an outgoing NNTP feed:

INN FAQ Part 4

NOTE: The maintainers of the INN FAQ stopped publishing in December 1997.
An important update to this topic is provided by Mib Software in the Usenet RKT for Subscribers.

Subject: (4.14) Cookbook example of an outgoing NNTP feed:
This example involves a machine named oddball.mentorg.com, that has an alias of oddball.sjc.mentorg.com, which should receive all posts (but control & junk should never be passed on) and not certain distributions. Add the following line to newsfeeds: oddball.mentorg.com/oddball.sjc.mentorg.com:,!control,!junk/!local,!warren:Tf,Wnm: Have the user "news" run the following via cron: 3,23,43 * * * * /usr/lib/news/bin/nntpsend >/dev/null 2>&1 (this only needs to be added once. nntpsend refers to a file called nntpsend.ctl to find out what to do). Add the following to nntpsend.ctl: oddball.mentorg.com:oddball.mentorg.com:: Done! If you experience errors in the form "480 Transfer permission denied", then your remote site should double check its hosts.nntp file. Entries in hosts.nntp normally look like <host>:[<pass>[:<groups>]], where pass and groups can be omitted. Now if the remote has an entry like the following: \|host.do.main: \| ^^^ note space instead of return then it expects you to send a password. If you don't, you get the above error. In this case, the remote should check its hosts.nntp, remove trailing spaces and do a ctlinnd reload hosts.nntp afterwards. See also INN FAQ #4.7 Another version for the "480 Transfer permission denied" problem is that the your host does not appear in the remotes hosts.nntp, but is matched by an entry in their nnrp.access. When you then send a "ihave'' command, the remote gives you that error. ------------------------------ [Source: INN FAQ Part 4 Archive-name: usenet/software/inn-faq/part4] [Last Changed: $Date: 1997/08/26 01:26:21 $ $Revision: 2.19 $] [Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]

Subject: (4.14) Cookbook example of an outgoing NNTP feed:

This example involves a machine named oddball.mentorg.com, that has an
alias of oddball.sjc.mentorg.com, which should receive all posts (but
control & junk should never be passed on) and not certain
distributions. Add the following line to newsfeeds:

oddball.mentorg.com/oddball.sjc.mentorg.com:*,!control*,!junk/!local,!warren:Tf,Wnm:

Have the user "news" run the following via cron:

3,23,43 * * * *  /usr/lib/news/bin/nntpsend >/dev/null 2>&1

(this only needs to be added once. nntpsend refers to a file
called nntpsend.ctl to find out what to do).

Add the following to nntpsend.ctl:

oddball.mentorg.com:oddball.mentorg.com::

Done!

If you experience errors in the form "480 Transfer permission denied",
then your remote site should double check its hosts.nntp file.
Entries in hosts.nntp normally look like

<host>:[<pass>[:<groups>]], where pass and groups can be omitted.
Now if the remote has an entry like the following:

|host.do.main: |
             ^^^  note space instead of return

then it expects you to send a password. If you don't, you get the
above error. In this case, the remote should check its hosts.nntp,
remove trailing spaces and do a ctlinnd reload hosts.nntp afterwards.
See also INN FAQ #4.7

Another version for the "480 Transfer permission denied" problem is
that the your host does not appear in the remotes hosts.nntp, but
is matched by an entry in their nnrp.access. When you then send a
"ihave'' command, the remote gives you that error.

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

[Source: INN FAQ Part 4 Archive-name: usenet/software/inn-faq/part4]
[Last Changed: $Date: 1997/08/26 01:26:21 $ $Revision: 2.19 $]
[Copyright: 1997 Heiko Rupp, portions by Tom Limoncelli, Rich Salz, et al.]