On 19.07.25 04:35, Anonymous wrote:
I am trying out INN2. I suppose I should begin by explaining exactly what I want to do.
I need to configure INN so that:
A. by default nothing is synced unless I manually add a newsgroup to the configuration,
B. so that by adding a newsgroup to the configuration, that newsgroup will be synced with all peers,
C. and finally so that only the entry of a newsgroup name into the configuration will result in syncronization, rather than entire hierarchies.
If I add alt.nobody to the configuration then the group alt.nobody will be synced with all the configured peers, and not the alt.* hierarchy. If I later add the group alt.everybody to the configuration then both groups will be synced with all peers. If I remove a group name from the configuration then that group will no longer syncronize with any peers.
How can I do this in a way that does not require updating the configuration for each individual peer, so that the list of groups will automatically be the same for all peers?
Usually you get told from your peer what you send them.
And you tell your peers what you want.
Means you set their configuration what they want on your side.
If a peer requests a change you just set it regardless
if you carry the group at the moment or not.
inn can run in modes / has flags that accept articles without
even having an active file populated and distribution is done via one of those :Ap,Tm,< flags. Aj accept Junk, etc.
read manualpages for newsfeeds.
The newsfeeds file configures what innd does with incoming accepted articles.
The file /etc/news/newsfeeds specifies how incoming articles
should be distributed to other programs and files on the server.
^ this "to other programs" is distribution via innfeed to other peers
example: If we want to peer together
i'd give you the config lines that i want for your newsfeeds file.
so you will send only articles to me that match (or not) the variables
in /etc/news/newsfeeds and you tell the other peer what you want them to
put in their newsfeeds so that you won't receive groups you don't want.
example from
https://newsdeef.eu/etc/news/newsfeeds
$NEWSDEEFDEFAULT=\
!control,!control.*,\
!junk,!junk.*,\
!local,!local.*,\
!ka.*,!gmane.*,!gwene.*
$NEWSDEEFNOBINARY=\
@a.b.*,@ab.alt.*,@ab.mom,@alt.b.*,@alt.*sex*,\
@dk.b.*,@*alt-bin*,@*alt.bin*,\
@*alt.dvd*,@*alt.hdtv*,@*dvdnordic*,\
@*nairies*,@*naries*,@*.bain*,@*.banar*,@*.banir*,\
@*.biana*,@*.bianr*,@*.biin*,@*.binar*,@*.binai*,\
@*.binaer*,@*.bineri*,@*.biniar*,@*.binira*,\
@*.binrie*,@*.biya*,@*.boneles*,@*cd.image*,\
@*dateien*,@*files.images*,@*music.bin*,\
@*nzb*,@*mp3*,@*ictures*,@*iktures*,\
@*erotic*,@*porno*,@*pedo*,@*paedo*,@*xxx*,@*warez*,@unidata.*
# LAV
srv.newsdeef.eu\
:*,$NEWSDEEFDEFAULT,$NEWSDEEFNOBINARY/!local\
:Ap,Tm,<262144:innfeed!
# LUX
srl.newsdeef.eu\
:*,$NEWSDEEFDEFAULT,$NEWSDEEFNOBINARY/!local\
:Ap,Tm,<262144:innfeed!
# YGG **
#ygg-lux.newsdeef.eu/lux-feed1.newsdeef.eu\
# :*,$NEWSDEEFDEFAULT,$NEWSDEEFNOBINARY/!local\
# :Ap,Tm,<262144:innfeed!
The incoming.conf file configures from which remote peers innd accepts NNTP feeds.
/etc/news/incoming.conf
# LAV
peer srv.newsdeef.eu {
hostname: srv.newsdeef.eu
max-connections: 5
}
# LUX
peer srl.newsdeef.eu {
hostname: srl.newsdeef.eu
max-connections: 5
}
# YGG **
#peer ygg-lux.newsdeef.eu {
# hostname: ygg-lux.newsdeef.eu
# max-connections: 5
#}
The innfeed.conf file configures to which remote peers innfeed sends NNTP feeds.
/etc/news/innfeed.conf
# LAV
peer srv.newsdeef.eu {
ip-name: srv.newsdeef.eu
#force-ipv4: true
port-number: 433
max-connections: 5
}
# LUX
peer srl.newsdeef.eu {
ip-name: srl.newsdeef.eu
#force-ipv4: true
port-number: 433
max-connections: 5
}
# YGG **
#peer ygg-lux.newsdeef.eu {
# ip-name: ygg-lux.newsdeef.eu
# port-number: 433
# max-connections: 5
#}
-- .......Billy G. (go-while)