Send inn-workers mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."
Today's Topics:
1. Re: nnrpd: adding blacklistd support (Andreas Kempe)
2. INN 2.7.0 feeding "local" newsgroup to peers (Jesse Rehmer)
3. Re: INN 2.7.0 feeding "local" newsgroup to peers (Kamil Jo?ca)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Mar 2022 17:00:57 +0200
From: Andreas Kempe <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: nnrpd: adding blacklistd support
Message-ID: <YkMfKU+/[email protected]>
Content-Type: text/plain; charset=iso-8859-1
On Mon, Mar 28, 2022 at 10:52:12PM +0200, Andreas Kempe wrote:
> On Mon, Mar 28, 2022 at 04:21:31PM +0000, Julien ?LIE wrote:
> > Hi Andreas,
> >
> > > Adding it as --with-blacklistd sounds like the right thing to do, yes.
> > >
> > >> I'll have a look.? As I do not run FreeBSD myself, it would
> > >> be great if you could somehow test it.
> > >
> > > When you say that you will have a look, does that mean that you want
> > > to rework the patch yourself?
> > >
> > > I'm willing (and was expecting) to open a pull request on GitHub and
> > > do testing as well as any required rewriting per your review.
> >
> > Oh, that's kind of you. It will save me time to do other work for INN
> > for the next major release.
> > Of course I don't mind your working on a pull request.
> > As we did not have GitHub until last year, I was accustomed to
> > reworking myself patches sent to our mailing-lists.
> >
>
> Happy to help! When I want a feature, I'm not adverse to putting in
> some work to get it.
>
> > The idea would be to create a new m4/blacklistd.m4 file (based for
> > instance on m4/canlock.m4), add related glue in configure.ac and
> > Makefile.global.in, and surround the new code in nnrpd with
> > #if defined(HAVE_BLACKLISTD) instructions.
> >
> > There is an entry in MANIFEST to add too.
> >
> > Maybe a note about blacklistd in doc/pod/nnrpd.pod? (or any other
> > file you think more appropriate)
> > And mention --with-blacklistd in doc/pod/install.pod.
> >
> > As GitHub continuous integration is run on Ubuntu, it cannot be
> > tested (so there is nothing to change in the ci directory I think).
> >
> >
>
> Your suggestions sound good. I'll open a pull request on Github for
> review when I have made the changes.
>
I've submitted a pull request for review at
https://github.com/InterNetNews/inn/pull/234 for those interested.
> > Many thanks to you. It is greatly appreciated!
> >
> > --
> > Julien ?LIE
>
Cordially,
Andreas Kempe
------------------------------
Message: 2
Date: Wed, 30 Mar 2022 03:49:07 -0500
From: Jesse Rehmer <[email protected]>
To: [email protected]
Subject: INN 2.7.0 feeding "local" newsgroup to peers
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Greetings,
I'm noticing odd behavior with a new INN 2.7.0 setup. When I post to
the "local" newsgroup on my server it is being sent to many peers I
would not expect. I'm using newsfeeds configurations given to me by
peers and there are a mix of styles. So I'm not sure if almost all of
my peers are providing an improper newsfeeds config, or if something has
changed.
Examples of newsfeeds configurations where "local" was fed to peers:
:*,!*.bina*,!*.bain*,!*.dateien*,!*.pictures*,!junk/!local\
:Ajfp,C20,G12,U5,<32768,Tm\
:innfeed!
:*,@*.bina*,@*.bain*,@*.dateien*,@*.pictures*/!local\
:Afjp,Tm:innfeed!
:*,!unidata.*,@*.bina*,@*.bain*,@*.dateien*,@*.pictures*/!local\
:Ajp,Tm,<65536:innfeed!
:*,!junk/!local,\
:Ajp,Tm,<512000:innfeed!
:*,!control*,!junk,!local.*,\
[email protected]*,@alt.dvd*,!@*pedophil.*,@*dateien*,!@*.bain*,\
!@*.biana*,!@*.biinaries*,!@*bina*,!@*.bineries*,!@*.binia*,\
!@*.binries*,!@*.cd.image*,!@*.files.images*,!@*.mp3*,\
:Afjp,Tm,<262144:innfeed!
The only example out of several peers with a local exclusion that did
*not* feed the article to the peer:
:!*,uk.*,cam.*,ed.*,alt.*,\
gnu.*,demon.*,eternal-september.*,argonet.*,24hoursupport.*,\
comp.*,news.*,soc.*,humanities.*,sci.*,talk.*,rec.*,misc.*,\
at.*,aus.*,be.*,ch.*,cz.*,de.*,dk.*,ee.*,es.*,esp.*,\
fr.*,grk.*,ie.*,hun.*,is.*,it.*,italia.*,malta.*,nl.*,\
nz.*,pl.*,pt.*,se.*,sfnet.*,sk.*,us.*,\
@*.bain*,@*.binar*,@*.mp3*,@*.pictures*,@*.biana*,@*.biinaries*,\
@*.dateien*,@*.binaer,@*.warez*,@alt.bin*,@unidata.*\
/!local\
:<65536,Afjp,Tm,Wmn:innfeed!
Header from an article that was fed to peers:
Path:
usenet.blueworldhosting.com!.POSTED.023-084-030-207.res.spectrum.com!not-for-mail
From: Jesse Rehmer <[email protected]>
Newsgroups: local
Subject: t
Date: Wed, 30 Mar 2022 03:22:02 -0500
Organization: BlueWorld Hosting USENET
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 30 Mar 2022 08:22:02 -0000 (UTC)
Injection-Info: bwh01.blueworldhosting.com; posting-account="<*>";
posting-host="023-084-030-207.res.spectrum.com:23.84.30.207";
logging-data="80954"; mail-complaints-to="[email protected]"
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
Gecko/20100101 Thunderbird/91.7.0
Cancel-Lock: sha1:00ax9nzaxJCmPVz2Yl638deRdhM=
sha256:NHsaIBg+szcH4ETKON90eInITjACXQK6oejqBHl6Aw0=
sha1:mNuGRo8Ve9svhl490cs6KYVlyuQ=
sha256:L3wJ8+JMYmKKysLdkWf+1V3L4cpvR21Jd9cvUAJQ/eY=
Content-Language: en-US
Xref: usenet.blueworldhosting.com local:1
Regards,
Jesse Rehmer
------------------------------
Message: 3
Date: Wed, 30 Mar 2022 11:39:18 +0200
From: Kamil Jo?ca <[email protected]>
To: [email protected]
Subject: Re: INN 2.7.0 feeding "local" newsgroup to peers
Message-ID: <[email protected]>
Content-Type: text/plain
Jesse Rehmer <[email protected]> writes:
> Greetings,
>
> I'm noticing odd behavior with a new INN 2.7.0 setup. When I post to
Why do you think it is odd?
One general remark: the "/!local" part of of line is taken into account
against "Distribution:" header, not 'Newsgroup:" header.
So if you have no distribution header in you example - it should be
irrelevant (Correct me if I am wrong)
> the "local" newsgroup on my server it is being sent to many peers I
> would not expect. I'm using newsfeeds configurations given to me by
> peers and there are a mix of styles. So I'm not sure if almost all of
> my peers are providing an improper newsfeeds config, or if something
> has changed.
>
> Examples of newsfeeds configurations where "local" was fed to peers:
>
> :*,!*.bina*,!*.bain*,!*.dateien*,!*.pictures*,!junk/!local\
> :Ajfp,C20,G12,U5,<32768,Tm\
> :innfeed!
this config will aaccept newsgroup named "local" (because of first "*")
>
> :*,@*.bina*,@*.bain*,@*.dateien*,@*.pictures*/!local\
> :Afjp,Tm:innfeed!
similary first "*" accept local
>
> :*,!unidata.*,@*.bina*,@*.bain*,@*.dateien*,@*.pictures*/!local\
> :Ajp,Tm,<65536:innfeed!
>
> :*,!junk/!local,\
> :Ajp,Tm,<512000:innfeed!
also first "*"
>
> :*,!control*,!junk,!local.*,\
> [email protected]*,@alt.dvd*,!@*pedophil.*,@*dateien*,!@*.bain*,\
> !@*.biana*,!@*.biinaries*,!@*bina*,!@*.bineries*,!@*.binia*,\
> !@*.binries*,!@*.cd.image*,!@*.files.images*,!@*.mp3*,\
> :Afjp,Tm,<262144:innfeed!
>
also first '*", here '!local.*" excludes subgroups of local
(ie. local.a,local.b) but no "local" itself.
>
> The only example out of several peers with a local exclusion that did
> *not* feed the article to the peer:
>
> :!*,uk.*,cam.*,ed.*,alt.*,\
> gnu.*,demon.*,eternal-september.*,argonet.*,24hoursupport.*,\
> comp.*,news.*,soc.*,humanities.*,sci.*,talk.*,rec.*,misc.*,\
> at.*,aus.*,be.*,ch.*,cz.*,de.*,dk.*,ee.*,es.*,esp.*,\
> fr.*,grk.*,ie.*,hun.*,is.*,it.*,italia.*,malta.*,nl.*,\
> nz.*,pl.*,pt.*,se.*,sfnet.*,sk.*,us.*,\
> @*.bain*,@*.binar*,@*.mp3*,@*.pictures*,@*.biana*,@*.biinaries*,\
> @*.dateien*,@*.binaer,@*.warez*,@alt.bin*,@unidata.*\
> /!local\
> :<65536,Afjp,Tm,Wmn:innfeed!
here you exclude everything (!*) and then enable explictly some groups
and no "local" group.
>
> Header from an article that was fed to peers:
>
> Path:
> usenet.blueworldhosting.com!.POSTED.023-084-030-207.res.spectrum.com!not-for-mail
> From: Jesse Rehmer <[email protected]>
> Newsgroups: local
> Subject: t
> Date: Wed, 30 Mar 2022 03:22:02 -0500
> Organization: BlueWorld Hosting USENET
> Message-ID: <[email protected]>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8; format=flowed
> Content-Transfer-Encoding: 7bit
> Injection-Date: Wed, 30 Mar 2022 08:22:02 -0000 (UTC)
> Injection-Info: bwh01.blueworldhosting.com; posting-account="<*>";
> posting-host="023-084-030-207.res.spectrum.com:23.84.30.207";
> logging-data="80954"; mail-complaints-to="[email protected]"
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
> Gecko/20100101 Thunderbird/91.7.0
> Cancel-Lock: sha1:00ax9nzaxJCmPVz2Yl638deRdhM=
> sha256:NHsaIBg+szcH4ETKON90eInITjACXQK6oejqBHl6Aw0=
> sha1:mNuGRo8Ve9svhl490cs6KYVlyuQ=
> sha256:L3wJ8+JMYmKKysLdkWf+1V3L4cpvR21Jd9cvUAJQ/eY=
> Content-Language: en-US
> Xref: usenet.blueworldhosting.com local:1
>
> Regards,
>
> Jesse Rehmer
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 139, Issue 6
*******************************************
