Odhiambo Washington writes:
Where XXXXX from the subject implies github|fedora|openid|gitlab, etc, I edited my settings.py and removed those references to socialaccount auth providers, except google:
It's clear enough:
Internal Server Error: /mailman3/accounts/gitlab/login/
DoesNotExist at /accounts/gitlab/login/
SocialApp matching query does not exist.Mailman is doing the right thing here: it assumes the remote user knows what they're doing, tries the auth provider, and discovers it doesn't exist, so it reports an error. Mailman is not responsible for the query; some third party is. You're dealing with the Internet -- we can't help you with what third parties do.
The one possible link to Mailman is that somehow mailman-web is offering social auth using those providers to users. When you log out of Postorius/ HyperKitty, then try to log back in, does the application offer login through any social auth other than Google? If so, that may be the problem, but I don't know how that can happen: the social auth offered is based on querying the providers installed by settings.py. And the person initiating the login would presumably be your user, who I would imagine would complain if they were trying to use social auth and it failed for them. Perhaps it's a user's browser cache.
If mailman-web doesn't offer social auth, it's something else. The reverse DNS lookup says it's coming from REMOTE_ADDR = '185.191.171.20' which is "20.bl.bot.semrush.com", where semrush is an SEO company. The "bot" part is suggestive of an automated attack, but who knows.
Steve