inn2 peering configs questions - hispagatos wrong?

[Billy G. (go-while)]

Hi!

I have a question about your peering configuration:

Is this correct usage "!@..." ?

I thought to deny groups with wildcards only @ is needed?
without "!" in front?

newsfeeds:
news.hispagatos.org/news.hispagatos.org\
:*,!control*,!junk,!local.*,\
!@alt.bin*,@alt.dvd*,!@*pedophil.*,@*dateien*,!@*.bain*,\
!@*.biana*,!@*.biinaries*,!@*bina*,!@*.bineries*,!@*.binia*,\
!@*.binries*,!@*.cd.image*,!@*.files.images*,!@*.mp3*,\
!@*music.bin*,!@*.pictures*,!@*porno.images*,!@*warez*,!@unidata.*,\
:Ap,Tm,<262144:innfeed!


Doc says in
https://www.eyrie.org/~eagle/software/inn/docs-2.7/newsfeeds.html

....It is a uwildmat pattern supporting poison (@) wildcards; ...
... If a newsgroup matches an @ pattern in pattern, then not only is it
not added to the subscription list, but any articles crossposted to that
newsgroup also will not be sent to that site even if other newsgroups to
which it was crossposted are in that site's subscription list. This is
called a poison pattern (because matching groups are "poisoned").



Your config almost looks like from bofh.team
but with many "!"
but missing it in "@*dateien*"?

better use this one from bofh.team?
@bofh: what is group "!ka.*" for? why don't you want it?
first line "@unidata.*",\ could be removed?
as it exists twice near the end?

$asnNOBINARY=\
!control*,!junk,!local*,@unidata.*,\
!ka.*,\
@alt.bin*,\
@alt.dvdnordic.*,\
@alt.*pedophil.*,\
@*.bain*,\
@*.biana*,\
@*.biinaries*,\
@*bina*,\
@*.bineries*,\
@*.binia*,\
@*.binries*,\
@*.cd.image*,\
@*.files.images*,\
@*.mp3*,\
@*music.bin*,\
@*.pictures*,\
@*porno.images*,\
@unidata.*,\
@*.warez*

newsfeed.bofh.team/newsfeed.bofh.team\
:*,$asnNOBINARY/!local\
:Af,Ap,Tm:innfeed!




if you tell your peers they should have cleanfeed
the newsfeed should have ":Af,Ap,Tm:innfeed!" ?

FLAG VALUES
https://www.eyrie.org/~eagle/software/inn/docs-2.7/newsfeeds.html#S3

A checks
An article will only be sent to this site if it meets the requirements
specified in checks, which should be chosen from the following set.
checks can be multiple letters if appropriate. Note that this flag is
not effective on funnel targets; it has to be used on every funnel entry
(for instance, Af is not effective on the innfeed! funnel target and
therefore has to be specified on every funnelled news site).

f
Don't send articles rejected by filters. This is only useful when
dontrejectfiltered is set to true in inn.conf. With that variable set,
this lets one accept all articles but not propagate filtered ones to
some sites.

p
Only check the exclusions against the Path header field of articles;
don't check the site name. This is useful if your site names aren't the
same as the path identities in Path header fields added by those remote
sites, or for program feeds where the site name is arbitrary and
unrelated to the Path header field body.


Looking for peers (in near future) to feed to my archive.
Configuring a front/transit server at the moment, since a while.
Will contact you (all) when it's done.

Billy G.

[Urs Janßen]

Post by Billy G. (go-while)
@bofh: what is group "!ka.*" for? why don't you want it?

ka.* should only be passed along from the core sites, not from any
other system, see <http://www.karlsruhe.org/peering.txt> (German).

[rek2 hispagatos]

Post by Billy G. (go-while)
Hi!
without "!" in front?
news.hispagatos.org/news.hispagatos.org\
:*,!control*,!junk,!local.*,\
:Ap,Tm,<262144:innfeed!
Doc says in
https://www.eyrie.org/~eagle/software/inn/docs-2.7/newsfeeds.html
not added to the subscription list, but any articles crossposted to that
newsgroup also will not be sent to that site even if other newsgroups to
which it was crossposted are in that site's subscription list. This is
called a poison pattern (because matching groups are "poisoned").

Hello I am a INN noob, been running the server and some newsgroups for
like now 1 year give or take and have asked many other admins I peer
with if that config was correct and they all said yes.
if is not please say something, I will be happy to change it.
In short we do not want porn/binaries/warez etc

PS: If I remember well I got that config from Eternal September (that is
one of our peers)

ReK2

[Billy G. (go-while)]

Post by rek2 hispagatos
Hello I am a INN noob, been running the server and some newsgroups for
like now 1 year give or take and have asked many other admins I peer
with if that config was correct and they all said yes.
if is not please say something, I will be happy to change it.
In short we do not want porn/binaries/warez etc
PS: If I remember well I got that config from Eternal September (that is
one of our peers)
ReK2

I'm noob too =) that's why i'm asking

[Ivo Gandolfo]

Post by Billy G. (go-while)
Hi!

[cut]

Post by Billy G. (go-while)
Your config almost looks like from bofh.team
but with many "!"
better use this one from bofh.team?
@bofh: what is group "!ka.*" for? why don't you want it?

It's a private hy. If u want it ask the sync server to do so. Long time
ago one my peer (Albasani, now death) send this to me (wrong config I
suppose). I just set my config as well to avoid problem.
Yeah, my bad. Thanks for the info. U can safe remove these.

Post by Billy G. (go-while)
as it exists twice near the end?
newsfeed.bofh.team/newsfeed.bofh.team\
        :*,$asnNOBINARY/!local\
        :Af,Ap,Tm:innfeed!
if you tell your peers they should have cleanfeed
the newsfeed should have ":Af,Ap,Tm:innfeed!" ?

yes. Or you can use innfeed delayed for more security.

Post by Billy G. (go-while)
Billy G.

Sincerely

[Billy G. (go-while)]

Post by Billy G. (go-while)
Hi!

[cut]

Post by Billy G. (go-while)
Your config almost looks like from bofh.team
but with many "!"

for me looks like negating the poisoning pattern => allowing it?
don't know how inn handles "!@" pattern but i read it as "dont poison".


thank you Ivo!

[Urs Janßen]

Post by Billy G. (go-while)
for me looks like negating the poisoning pattern => allowing it?

@ needs to be the first char to act as poison indicator elsewhere
it is just a regular char.

[Billy G. (go-while)]

Post by Urs Janßen

Post by Billy G. (go-while)
for me looks like negating the poisoning pattern => allowing it?

@ needs to be the first char to act as poison indicator elsewhere
it is just a regular char.

good to know thank you!

[Julien ÉLIE]

Hi Billy,

    :*,!control*,!junk,!local.*,\

In addition to what has already been rightly said in this thread, I
would recommend "!control,!control.*" instead of "!control*" because it
otherwise excludes possible hierarchies like a controllers.* one.

[Billy G. (go-while)]

Post by Julien ÉLIE
Hi Billy,

     :*,!control*,!junk,!local.*,\

In addition to what has already been rightly said in this thread, I
would recommend "!control,!control.*" instead of "!control*" because it
otherwise excludes possible hierarchies like a controllers.* one.

great!

another question i have is the order.

why do * first and then denials afterwards?

why not put entries with ! or @ first and put the single * to the end?

...
...

while i'm asking myself i jumped into the source and found this:

https://github.com/InterNetNews/inn/blob/0ff2d3ae0912cf2098d20aaecc900bb5b9e472b2/innd/newsfeeds.c#L363

/*
** Modify "subbed" according to the patterns in "patlist."
*/
static void
SITEsetlist(char **patlist, char *subbed, char *poison, bool *poisonEntry)


looks like cfg gets read at once and sets some bits somewhere else.
so i believe the order should not matter?

Thank you

[Julien ÉLIE]

Hi Billy,

Post by Billy G. (go-while)

     :*,!control*,!junk,!local.*,\

why do * first and then denials afterwards?

Because the last matching pattern for a newsgroup determines whether it
matches.
Example: local.test matches "*" and "!local.*" in the above line. The
last one applies.

Post by Billy G. (go-while)
so i believe the order should not matter?

The order matters. You can give it a try :)

[Billy G. (go-while)]

Post by Julien ÉLIE
Hi Billy,

     :*,!control*,!junk,!local.*,\

In addition to what has already been rightly said in this thread, I
would recommend "!control,!control.*" instead of "!control*" because it
otherwise excludes possible hierarchies like a controllers.* one.

Hi all!

why do some ppl filter out unidata.* ?
found 1 active group "unidata.hds"

it is saturday and i grepped latest newsgroups from providers
this filters more (or most of) binary groups
without false positives or did not see one

hit me if i'm wrong!

print filtered newsgroups:
***@shell:~$ egrep
"^a\.b\.|^alt\.bin|^alt\.biya|^alt\.dvdnordic|^bina|\.(bain|banar|banir|biana|bianr|biin|bina|bine|bini|binr|boneles|cd\.image|dateien|files\.images|porno)|mp3|music\.bin|[px]i[ck]tures|warez"
active.file | sort | less

inverted output (accepted newsgroups)
***@shell:~$ egrep -v ....

# /etc/news/newsfeeds

$DEFAULT=\
!control,!control.*,\
!junk,!junk.*,\
!local,!local.*,\
!ka.*

$NOBINARY=\
@a.b.*,\
@alt.bin*,\
@alt.biya*,\
@alt.dvdnordic*,\
@bina*,\
@*.bain*,\
@*.banar*,\
@*.banir*,\
@*.biana*,\
@*.bianr*,\
@*.biin*,\
@*.bina*,\
@*.bine*,\
@*.bini*,\
@*.binr*,\
@*.boneles*,\
@*.cd.image*,\
@*.dateien.*,\
@*.files.images*,\
@*mp3*,\
@*music.bin*,\
@*.pictures*,\
@*.piktures*,\
@*.xiktures*,\
@*.porno*,\
@*warez*


#sub.domain.net/sub.domain.net\
# :*,$DEFAULT,$NOBINARY/!local\
# :Af,Aj,Ap,Tm,<262144:innfeed!

[Marco Moock]

Post by Billy G. (go-while)
found 1 active group "unidata.hds"

I couldn't find a control file for it.
Which servers do carry that group, are public archives available?

[Billy G. (go-while)]

Post by Marco Moock

Post by Billy G. (go-while)
found 1 active group "unidata.hds"

I couldn't find a control file for it.
Which servers do carry that group, are public archives available?

found on some paid provider but is empty

[Urs Janßen]

Post by Billy G. (go-while)
why do some ppl filter out unidata.* ?

it did contain binaries (atmospheric data)

[Schlomo Goldberg]

Post by Billy G. (go-while)

Post by Julien ÉLIE
Hi Billy,

     :*,!control*,!junk,!local.*,\

In addition to what has already been rightly said in this thread, I
would recommend "!control,!control.*" instead of "!control*" because
it otherwise excludes possible hierarchies like a controllers.* one.

Hi all!
why do some ppl filter out unidata.* ?

It used to be some project where universities used Usenet to propagate
weather data. You can still find traces of it if you google
"unidata". Apparently it was *a lot* of data for the time, and most
people didn't want it.