- On 4/20/25 02:26, Mark Sapiro wrote:
This appears to be a bug in mailbox.mbox. To work around it, try this:
[...]
Thanks, that works!
Those headers are added by the rfc_2369 handler based on the archivers configured for the list. They will never point to the prototype archiver or the message in the prototype archive.
Normally they will point to HyperKitty and to the archived message in HyperKitty. This is the case even for messages in the prototype archiver as those messages are just the message as delivered to the list members absent any personalization.
Yes, it iterates through all archivers and gets the permalink and archiver's URL, adding it to the message if the data is non-empty.
Note that the generation of these headers by the rfc_2369 handler depends on this script being run in an installation that has hyperkitty and mailman-hyperkitty installed and the hyperkitty archiver enabled for the list.
There is one other thing that caught me off-guard: I had the Hyperkitty archiver enabled, of course, but the service was not running (I essentially turned off everything, including the cron jobs, for the migration, to make sure that no new data is coming in).
In order for mailman to query the required data, it has to communicate with the archivers (like Hyperkitty) and that in turn means that the archiver must be running.
After starting Hyperkitty, the headers magically gained proper values!
Thank you very much for your help.
Mihai