March 2, 2026
7:03 p.m.
On 3/2/26 10:13, Washington Odhiambo via Mailman-users wrote:
I will have to check the mailman.log. What should I look for? Right now it looks so clean - without anything to worry about.
I'm assuming the list's active archivers includes hyperkitty and that messages are archived there and messages from the list contain an appropriate Archived-AT: header. Is all that correct?
Are there Exception in "hyperkitty" archiver messages in mailman.log,
or if you have set a path: in the [logging.archiver] section of
mailman.cfg, in that file?
You could try in mailman shell
$ mailman shell -l list.example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the list.example.com mailing list
>>> for archiver in IListArchiverSet(m).archivers:
... if archiver.system_archiver.name == 'hyperkitty':
... print(f'Enabled: {archiver.is_enabled}')
...
Enabled: True
>>>
and see if it prints Enabled: True.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan