Quoting Mark Sapiro ([email protected]):

> On 11/29/24 7:48 AM, [email protected] wrote:
> >
> >So this points to an issue with the one list I assume? It's much, much
> >larger than the one with the subscription options working. Where do I
> >go next?


> I'm surprised nothing is logged in Mailman's error.log.

Nothing abnormal or related, just the expected 'no such list' listname
typos etc. So logging is working, just not logging anything
interesting for this issue.

> What happens if you run Mailman's
> 
> bin/config_list -o - LISTNAME
> 
> Does this throw an exception with a traceback? If not, how about
> 
> bin/config_list -i /dev/null LISTNAME

Both commands return as expected - the first the long list of config
values, and the second just returns after updating the timestamp on
the list files. I ran both commands against all current lists and a
couple of disused/test lists as well. All produced the same output.

Definitely a weird one. Really appreciate the help Mark.
------------------------------------------------------
Mailman-Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/[email protected]/
    https://mail.python.org/archives/list/[email protected]/
Member address: [email protected]

Reply via email to