[Pkg-mailman-hackers] Bug#968244: mailman3-web: Crash with: /usr/share/mailman3-web/manage.py runjobs daily

[Athanasius]

Package: mailman3-web
Version: 0+20180916-8
Severity: normal

Dear Maintainer,

After installing mailman3 I used migrated old Mailman 2.1 lists in using
'import21' and then their archives using 'python manage.py
hyperkitty_import -l ...'.

All seems to have gone OK, but the daily mailman3-web job in
/etc/cron.d/mailman3-web:

@daily             www-data     [ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.daily /usr/share/mailman3-web/manage.py runjobs daily

is throwing errors:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django_extensions/management/commands/runjobs.py", line 36, in runjobs
    job().execute()
  File "/usr/lib/python3/dist-packages/hyperkitty/jobs/sync_mailman.py", line 35, in execute
    sync_with_mailman()
  File "/usr/lib/python3/dist-packages/hyperkitty/lib/mailman.py", line 145, in sync_with_mailman
    sender.set_mailman_id()
  File "/usr/lib/python3/dist-packages/hyperkitty/models/sender.py", line 54, in set_mailman_id
    mm_user = client.get_user(self.address)
  File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 322, in get_user
    return User(self._connection, content['self_link'], content)
KeyError: 'self_link'
ERROR OCCURED IN DAILY JOB: sync_mailman (APP: hyperkitty)
START TRACEBACK:
END TRACEBACK

Adding a little debug output:

Address: #.pleasegivegenerously at hotmail.com
Response: {'date': 'Tue, 11 Aug 2020 14:35:42 GMT', 'server': 'WSGIServer/0.2 CPython/3.7.3', 'content-length': '712742', 'content-type': 'application/json; charset=UTF-8', 'status': '200', 'content-location': 'http://river-nat:8001/3.0/users/#.pleasegivegenerously@hotmail.com'}

And the 'content' at that point is *huge* (693KiB), indeed without a
'self_link' key at its top level, although it contains an 'entries'
array in which each member has a 'self_link' key.

This appears to be code to sync up hyperkitty's idea of senders with
actual members of the list, so is probably relatively harmless, but I
don't know if *subsequent* more important code is being prevented from
running.

-- System Information:
Debian Release: 10.5
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.138-fysh-kvmguest (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mailman3-web depends on:
ii  dbconfig-sqlite3           2.0.11+deb10u1
ii  debconf [debconf-2.0]      1.5.71
ii  lsb-base                   10.2019051400
ii  node-less                  1.6.3~dfsg-3
ii  python3                    3.7.3-1
ii  python3-django-hyperkitty  1.2.2-1
ii  python3-django-postorius   1.2.4-1
ii  python3-psycopg2           2.7.7-1
ii  python3-whoosh             2.7.4+git6-g9134ad92-4
ii  sassc                      3.5.0-1
ii  ucf                        3.0038+nmu1
ii  uwsgi                      2.0.18-1
ii  uwsgi-plugin-python3       2.0.18-1

Versions of packages mailman3-web recommends:
pn  libapache2-mod-proxy-uwsgi | nginx  <none>

Versions of packages mailman3-web suggests:
ii  mariadb-server-10.3 [virtual-mysql-server]  1:10.3.23-0+deb10u1

-- debconf information:
  mailman3-web/upgrade-error: abort
  mailman3-web/superuser-name: admin
  mailman3-web/pgsql/authmethod-user: password
  mailman3-web/restart-webserver: true
  mailman3-web/nginx-choice:
  mailman3-web/missing-db-package-error: abort
  mailman3-web/mysql/method: Unix socket
  mailman3-web/configure-webserver: none
  mailman3-web/dbconfig-upgrade: true
  mailman3-web/install-error: abort
  mailman3-web/pgsql/admin-user: postgres
  mailman3-web/dbconfig-remove: true
  mailman3-web/pgsql/changeconf: false
  mailman3-web/upgrade-backup: true
  mailman3-web/db/dbname: mailman3web
  mailman3-web/internal/skip-preseed: false
  mailman3-web/purge: false
  mailman3-web/remote/port:
  mailman3-web/superuser-mail: root at localhost
  mailman3-web/db/app-user: mailman3web at localhost
* mailman3-web/dbconfig-install: false
  mailman3-web/remove-error: abort
  mailman3-web/pgsql/manualconf:
  mailman3-web/pgsql/method: TCP/IP
  mailman3-web/remote/host: localhost
  mailman3-web/emailname: fysh.org
  mailman3-web/mysql/admin-user:
  mailman3-web/remote/newhost:
  mailman3-web/dbconfig-reinstall: false
  mailman3-web/passwords-do-not-match:
  mailman3-web/db/basepath: /var/lib/mailman3/web
  mailman3-web/pgsql/authmethod-admin: ident
  mailman3-web/internal/reconfiguring: false
  mailman3-web/pgsql/no-empty-passwords:
  mailman3-web/database-type: