From: dugo@xs4all.nl (Jacob Goense)
Subject: [TUHS] make inn automatically accept new group control messages
Date: Wed, 19 Apr 2017 11:21:10 +0200 [thread overview]
Message-ID: <cff8d22be0208fae471cb86c2f9836ea@xs4all.nl> (raw)
In-Reply-To: <alpine.BSF.2.20.1704191508220.5445@aneurin.horsfall.org>
On 2017-04-19 07:10, Dave Horsfall wrote:
> On Wed, 19 Apr 2017, Warren Toomey wrote:
>
>> > Looks like INN isn't quite as trusting as CNews, so it doesn't
>> > automatically create a group when it receives a control message.
>> > Anyone know how to make it do that, or at least email me to notify of
>> > the new group?
>>
>> ctlinnd newgroup tuhs.tuhslist
>>
>> I think that's what I did on my Inn system.
>
> (Gadzooks; first time I've seen Newsgroups: for ages!)
>
> Isn't there a config file that says something like "this user can issue
> these ctl commands for these groups"?
I have not touched INN in ages either. I'm sure you need to be in
control.ctl to configure this. It will be a while until we see
control message abuse on this August network, so you could probably
put in something like newgroup:*:*:doit for now.
prev parent reply other threads:[~2017-04-19 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 22:34 John Floren
2017-04-19 11:02 ` Warren Toomey
2017-04-19 5:10 ` Dave Horsfall
2017-04-19 9:21 ` Jacob Goense [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cff8d22be0208fae471cb86c2f9836ea@xs4all.nl \
--to=dugo@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).