INN 2.7.0 feeding "local" newsgroup to peers

[Julien ÉLIE]

Hi Jesse,

> 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.

Your peers do not know that you carry a newsgroup named "local".

Besides what Kamil already said, I would just add:

>         :*,!*.bina*,!*.bain*,!*.dateien*,!*.pictures*,!junk/!local\

When "*" is used, pseudo-groups like control.cancel are explicitly 
marked to be transferred.  If you then exclude newsgroups, you should
also exclude control articles for these newsgroups.

:*,!*.bina*,!*.bain*,!*.dateien*,!*.pictures*,!junk,!control,!control.*

would be better.  This way, control articles for news.software.nntp will 
still be fed (as they follow the propagation of their Newsgroups header 
field), but control articles for alt.xxx.binary won't be fed (which is 
what you expect).
Otherwise, all the contents of the pseudo-groups is sent, whatever the 
Newsgroups header field is.


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

Better say "!control,!control.*" as a hierarchy named controller.* for 
instance would not be fed with that pattern.


>         !@*.biana*,!@*.biinaries*,!@*bina*,!@*.bineries*,!@*.binia*,\

Is the "!@" pattern really working?  ("@" would be enough, I'm not sure 
"!@" is valid)

-- 
Julien ÉLIE

« L'éternité, c'est long, surtout vers la fin. » (Woody Allen)