[InterNetNews/inn] ac1c75: Keep user-supplied domain in readers.conf
Julien ÉLIE
noreply at github.com
Sun Feb 19 17:24:55 UTC 2023
Branch: refs/heads/main
Home: https://github.com/InterNetNews/inn
Commit: ac1c752091e0671a5aa3eb798024acd0af84fe37
https://github.com/InterNetNews/inn/commit/ac1c752091e0671a5aa3eb798024acd0af84fe37
Author: Julien ÉLIE <Julien-Elie at users.noreply.github.com>
Date: 2023-02-19 (Sun, 19 Feb 2023)
Changed paths:
M control/gencancel.c
M doc/FAQ
M doc/pod/inn.conf.pod
M doc/pod/libinn.pod
M doc/pod/news.pod
M doc/pod/readers.conf.pod
M frontends/inews.c
M lib/innconf.c
M lib/messageid.c
M nnrpd/commands.c
M nnrpd/nnrpd.h
M nnrpd/perm.c
M nnrpd/post.c
Log Message:
-----------
Keep user-supplied domain in readers.conf
Customizing the domain part of Message-IDs generated by nnrpd and the
server name indicated in Injection-Info header fields is now easier:
the domain parameter in the access blocks of readers.conf can be
directly used (without setting virtualhost as it was previously the
case).
An expicitly-set configuration option should override whatever is
discovered while probing around on the system. So we now use domain
unconditionally if it is set in readers.conf for forming message
identifiers and Injection-Info. But keep backwards-compatibility by
not using domain if only set in inn.conf (previous versions of INN only
use it if virtualhost is also set to true).
Document domain as a first-class configuration parameter for access
groups in readers.conf, saying that it changes the way Message-IDs and
Injection-Info are constructed.
Update wording in the FAQ and various documentation (inn.conf, libinn,
readers.conf, comments in C code).
close #243
More information about the inn-committers
mailing list