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 (Julien ?LIE)
2. Re: Disabling XBATCH by default in innd (Julien ?LIE)
3. Re: Excluding Cancel-Lock for certain users (Julien ?LIE)
----------------------------------------------------------------------
Message: 1
Date: Thu, 7 Apr 2022 22:51:58 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: nnrpd: adding blacklistd support
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi all,
>> Adding it as --with-blacklist sounds like the right thing to do, yes.
>
> I've submitted a pull request for review at
> https://github.com/InterNetNews/inn/pull/234 for those interested.
Andreas' work is now merged upstream.
blacklistd (shipped with FreeBSD and NetBSD notably) is now natively
supported by nnrpd.
--
Julien ?LIE
??Le dieu, dont l'oracle est ? Delphes, ne parle pas, ne dissimule pas?:
il indique.?? (H?raclite d'?ph?se, fragment 93, traduction de Jean
Voilquin)
------------------------------
Message: 2
Date: Thu, 7 Apr 2022 22:56:19 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: Disabling XBATCH by default in innd
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi all,
>> It would become commented in incoming.conf:
>> #email: "[email protected]"
>
> Oh, that's a great idea that for some reason I didn't think of. I'm in
> favor of doing that.
Also done in CURRENT.
innupgrade will take care of the changes in incoming.conf:
- commenting the lines with removed "comment" or "email" parameters;
- renaming "nolist" and "noresendid" to "list" and "resendid" while
inverting the related boolean value.
Also, "noxbatch" has been renamed to "xbatch".
Everything is now clearer in incoming.conf.
--
Julien ?LIE
??Tant qu'il y a des marmites, il y a de l'espoir?!?? (Ast?rix)
------------------------------
Message: 3
Date: Thu, 7 Apr 2022 23:02:26 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: Excluding Cancel-Lock for certain users
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi all,
> As an identity is always assigned by readers.conf, all posts are
> considered to be sent by a known posting-account (the one appearing in
> Injection-Info).
> Yet, it causes a problem with Cancel-Lock because some identities may be
> shared between several persons.? Which means that any user with that
> identity can cancel any other post from another user with the same
> identity.
FYI, an "addcanlockuser" (defaulting to true) can now be added in access
blocks to deactive the generation of a user Cancel-Lock for access
blocks shared between several persons with the same assigned identity.
Example:
auth "example.com" {
hosts: "*.example.com"
auth: "ckpasswd -f <pathdb in inn.conf>/newsusers"
default: "anonymous"
}
access regular {
newsgroups: "*,!example.restricted.*"
addcanlockuser: false
}
access full {
users: "*,!anonymous"
newsgroups: *
}
Only an admin Cancel-Lock will be generated for anonymous users.
--
Julien ?LIE
??Tant qu'il y a des marmites, il y a de l'espoir?!?? (Ast?rix)
------------------------------
Subject: Digest Footer
_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers
------------------------------
End of inn-workers Digest, Vol 140, Issue 1
*******************************************
