Am Wed, Feb 25, 2026 at 08:30:47PM +0100 schrieb Thomas Hochstein:
Laurens Kils-Hütten wrote:
# this is in /etc/news/newsfeeds news2mail!:!*:Ac,Tc,Wn*:/usr/lib/news/bin/news2mail test-grenzland-club/grenzland.club:!*,grenzland.test:Ap,Tm:news2mail! # this last line should do two things: forward messages from the # test@grenzland.club list to the grenzland.test newsgroup,
No, it doesn't. newsfeeds specifies how incoming articles should be distributed to other programs and files on the server. It can't "forward" articles from a mailing list. That's what Mailman does (and has to do).
right, thanks for clarifying. I shouldn't have written "forward" and I mixed it up.
It will forward messages that are posted to grenzland.test to the news2mail feed and to the test@grenzland.club mailing list, so the other way around. And it will ...
# AND don't send any messages back which have grenzland.club
... or test-grenzland-club ...
I think the Ap flag should prevent this.
# in their Path header. This last bit seems to fail however, # and I fail to spot the error.
Does Mailman submit the message with a Path header containing "grenzland.club" or "test-grenzland-club"?
Looking at the Path headers it's the former. test-grenzland-club is just an arbitrary identifier used in the inn2 configuration.
I'm not sure mailman is even generating the Path header itself.
Does Mailman post the message (via NNRP / nnrpd) or feed it?
nnrpd
If the former, what Path element does your nnrpd add?
see below
Can you show the relevant entries from the news and news.notice logfiles and the Path header from a message from the mailing list to the newsgroup?
Path headers always look like this, whether I post a message as news or email:
Path: grenzland.club!.POSTED.localhost!not-for-mail
So the exclusion pattern should match on the first part.
This is what shows up in /var/log/news/news.notice: # I've added some comments ... # first mailman's nnrp client connects ... 2026-02-25T22:49:31.966611+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:32.006079+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:32.006427+01:00 grenzland innd: localhost:21 checkpoint seconds 1 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:32.006490+01:00 grenzland innd: localhost:21 closed seconds 1 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:32.015322+01:00 grenzland nnrpd[2990705]: localhost (127.0.0.1) connect - port 119 2026-02-25T22:49:32.059569+01:00 grenzland nnrpd[2990705]: SERVER perl filtering enabled 2026-02-25T22:49:32.059711+01:00 grenzland innd: localhost connected 21 2026-02-25T22:49:32.061392+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 1 refused 0 rejected 0 duplicate 0 accepted size 1338 duplicate size 0 rejected size 0 2026-02-25T22:49:32.061463+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 1 refused 0 rejected 0 duplicate 0 accepted size 1338 duplicate size 0 rejected size 0 # and posts successfully: 2026-02-25T22:49:32.061498+01:00 grenzland nnrpd[2990705]: localhost post ok <20260225214930.E77531412C1@grenzland.club> 2026-02-25T22:49:32.062568+01:00 grenzland nnrpd[2990705]: localhost posts received 1 rejected 0 2026-02-25T22:49:32.062771+01:00 grenzland nnrpd[2990705]: localhost times user 0.006 system 0.004 idle 0.000 elapsed 0.048 2026-02-25T22:49:32.062895+01:00 grenzland nnrpd[2990705]: localhost time 48 idle 43(6) nntpwrite 1(24) # with a notable delay I sea the same connection procedure 2026-02-25T22:49:33.070321+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:33.110111+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:33.111092+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.111186+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.124001+01:00 grenzland nnrpd[2990714]: localhost (127.0.0.1) connect - port 119 # but now it fails, presumably because an Injection-Info header field # has already been set. At the same time I see the error message given # in my original email in /var/log/mailman3/mailman.log 2026-02-25T22:49:33.165116+01:00 grenzland nnrpd[2990714]: localhost post failed Can't set system Injection-Info header field 2026-02-25T22:49:33.165765+01:00 grenzland nnrpd[2990714]: localhost posts received 0 rejected 1 2026-02-25T22:49:33.165832+01:00 grenzland nnrpd[2990714]: localhost times user 0.005 system 0.004 idle 0.000 elapsed 0.043 2026-02-25T22:49:33.165876+01:00 grenzland nnrpd[2990714]: localhost time 43 idle 42(6) nntpwrite 0(24) 2026-02-25T22:49:33.173419+01:00 grenzland innd: localhost connected 21 streaming allowed 2026-02-25T22:49:33.213944+01:00 grenzland innd: localhost:21 NCmode "MODE READER" received 2026-02-25T22:49:33.214300+01:00 grenzland innd: localhost:21 checkpoint seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.214368+01:00 grenzland innd: localhost:21 closed seconds 0 accepted 0 refused 0 rejected 0 duplicate 0 accepted size 0 duplicate size 0 rejected size 0 2026-02-25T22:49:33.221243+01:00 grenzland nnrpd[2990715]: localhost (127.0.0.1) connect - port 119 2026-02-25T22:49:33.261359+01:00 grenzland nnrpd[2990715]: localhost post failed Can't set system Injection-Info header field 2026-02-25T22:49:33.262391+01:00 grenzland nnrpd[2990715]: localhost posts received 0 rejected 1 2026-02-25T22:49:33.263326+01:00 grenzland nnrpd[2990715]: localhost times user 0.005 system 0.002 idle 0.000 elapsed 0.042 2026-02-25T22:49:33.263816+01:00 grenzland nnrpd[2990715]: localhost time 43 idle 41(6) nntpwrite 1(24)
(Or we can take that to news.software.nntp or de.comm.software.newsserver, whichever (language) you prefer.)
I don't have direct access to either group on this here machine. But news.software.nntp might actually be more on topic. Follow-up wherever you think is more apropriate.
Thanks in any case!
lkh
-thh
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/...
This message sent to lkh@grenzland.club
-- ~lkh (Laurens Kils-Hütten)