Am Tue, Feb 24, 2026 at 01:16:45PM -0800 schrieb Mark Sapiro: > On 2/24/26 09:23, Laurens Kils-Hütten wrote: > > > > I've used the debian packages: > > > > apt install mailman3-full mailman3-web > > Then this may be a Debian issue and should be reported there in any case. > See <https://wiki.list.org/x/12812344>.
I will, once I convinced it's really a bug. Right now I'm thinking it's a misconfiguration on inn2's side. >From scrutinising the message headers this is what happens: mailman sends the message to the newsserver where it get's injected properly receiving an Injection-Information: header field. Then however this new message is sent back to mailman. Now there's a duplicate with identical message ID. Mailman then sends it back to inn2 which refuses to take it and the python nntp client throws an error, thus preventing an endless loop. Why inn2 even sends the message back to mailman I can't tell right now. These are the relevant snippets from my inn2 setup: # this is from /etc/news/news2mail.cf # no surprises, and it basically works. News from the grenzland.test # group is forwarded to the proper list address test-grenzland-club [email protected] # 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 # [email protected] list to the grenzland.test newsgroup, # AND don't send any messages back which have grenzland.club # in their Path header. This last bit seems to fail however, # and I fail to spot the error. I'll ask about this in the inn2 places I known of. Cheers, lkh -- Laurens Kils-Hütten https://lkh.sdf-eu.org _______________________________________________ Mailman-users mailing list -- [email protected] To unsubscribe send an email to [email protected] https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Archived at: https://lists.mailman3.org/archives/list/[email protected]/message/W4WTVI3MAV4WHYTAV7IBVWXP3OL25DKM/ This message sent to [email protected]
