On 12/1/20 5:31 PM, Brian Carpenter wrote:
On 12/1/20 8:22 PM, Mark Sapiro wrote:
Those come from the HyperKitty sync_mailman job which is run by hyperkitty_import if you don't specify --no-sync-mailman, but is also one of the Django daily jobs.
Ok but those number are the same for thousands of entries and apparently are being logged for weeks. That can't be good. How does one fix this?
The sync_mailman job does two things. The first thing it does is for all lists known to HyperKitty, it gets the list attributes "display_name", "description", "subject_prefix", "archive_policy", "created_at" and "list_id" from Mailman core and updates the list properties in Hyperkitty.
Then it gets every message sender known to Hyperkitty for which HK's sender.mailman_id is null, and, 1000 senders at a time, it tries to get and set the core user_id for the address to the sender's mailman_id.
What happens when you import old archives, you archive a lot of posts with senders that are no longer list members and are not known to core, and every time sync_mailman runs, it tries again to get those core user_ids.
You definitely want the first part to run to pick up changes like a change in archive_policy or a change in subject_prefix (to be able to strip it from Subject: headers.
The second step could also find a newly registered core user, but is less important. Whether it is bad is a matter of opinion. At worst, it is a waste of some processing time, and at best it will pick up new users if there are any. "Fixing" it requires modification of the sync_with_mailman function in hyperkitty/libs/mailman.py.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan