On 6/25/23 11:04 AM, Ken Alker wrote:
I've just taken on the project so I'm new to all of this, and one thing I noticed that caught my eye, and has left me curious, is that for the first a couple of seconds starting just after midnight every night (just after log rotation) mailman.log would have many (dozens, or hundreds) of lines entered in it just like this one:
Jun 19 00:00:04 2023 (2266) 127.0.0.1 - - "GET /3.0/users/old-user@domain.tld HTTP/1.1" 404 58
where "old-user@domain.tld" is the email address of a user who either had unsubscribed or changed their email address (I don't know which, I just know they are no longer a member/subscriber to the list). Each successive entry in the log would have a different "old username" in it. I don't understand why these entries would be in the log and what they mean. Can someone shed some light on this for me? This is merely a question of curiosity, and not one of import. (Since migrating from 3.2.2 to 3.3.8 this behavior has stopped, be that GOOD or BAD.)
This is the Django hyperkitty sync_mailman job which is one of the django admin jobs run daily. It goes through the HyperKitty 'sender' database table and tries to find the Mailman core user id for each sender address to add/update its mailman_id field with core's user_id.
The 404s are addresses im HyperKitty's sender table for whih there is no corresponding Mailman user. There are multiple possible reasons for this.
If the behavior has stopped it's probably because the periodic Django jobs are not being run - this is bad.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan