@bofh: what is group "!ka.*" for? why don't you want it?
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").
Hi!
I have a question about your peering configuration:
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?
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!" ?
Billy G.
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
On 22/05/2024 11:20, Billy G. (go-while) wrote:
Hi![cut]
I have a question about your peering configuration:
Your config almost looks like from bofh.team
but with many "!"
but missing it in "@*dateien*"?
Not need ! in front to @ (double negation).
for me looks like negating the poisoning pattern => allowing it?
don't know how inn handles "!@" pattern but i read it as "dont poison".
Billy G. (go-while) wrote:
for me looks like negating the poisoning pattern => allowing it?
don't know how inn handles "!@" pattern but i read it as "dont poison".
@ needs to be the first char to act as poison indicator elsewhere
it is just a regular char.
:*,!control*,!junk,!local.*,\
:*,!control*,!junk,!local.*,\
why do * first and then denials afterwards?
why not put entries with ! or @ first and put the single * to the end?
so i believe the order should not matter?
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 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.
found 1 active group "unidata.hds"
On 01.06.2024 um 14:08 Uhr Billy G. (go-while) wrote:
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?
why do some ppl filter out unidata.* ?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 00:12:19 |
Calls: | 7,466 |
Calls today: | 2 |
Files: | 12,691 |
Messages: | 5,627,862 |