On 12/14/22 01:45, Stephen J. Turnbull wrote:
Alex A.J. writes:
line 1132, in identify_record raise exc.UnknownHashError("hash could not be identified") passlib.exc.UnknownHashError: hash could not be identified Dec 13 17:01:41 2022 (2677611) SHUNTING: 1670931101.6040337+d5806b00b2b9d03f25db396639f66f3a26516178
This looks like maybe you have the wrong password?
Maybe Mark or Abhilash has a more concrete suggestion, I've never used the Approved header with Mailman 3.
I don't have more time to look at this now, but I think it's a bug. This patch ``` --- a/src/mailman/rules/approved.py +++ b/src/mailman/rules/approved.py @@ -140,6 +140,7 @@ class Approved: mpw = mlist.moderator_password else: mpw = mlist.moderator_password.decode('utf-8') + mpw = config.password_context.encrypt(mpw) is_valid, new_hash = config.password_context.verify(password, mpw) if is_valid and new_hash: # Hash algorithm migration. ``` may fix it. -- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan