mailman3 supports using a whoosh (default, pure Python) backend for full text search or a supposedly faster/better xapian backend
See https://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.html#xapian and https://docs.mailman3.org/en/latest/config-web.html#enable-full-text-search-required
The xapian-haystack package in Buster is broken, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956653
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| mailman3: Use xapian for fulltext search | operations/puppet | production | +9 -1 |
Mentioned in SAL (#wikimedia-operations) [2021-04-02T21:28:15Z] <legoktm> imported python-xapian-haystack 2.1.0-6~wmf1 on apt1001 (T278717)
Change 676675 had a related patch set uploaded (by Legoktm; author: Legoktm):
[operations/puppet@production] mailman3: Use xapian for fulltext search
Change 676675 merged by Legoktm:
[operations/puppet@production] mailman3: Use xapian for fulltext search
More discussion ongoing at T278609: Import several public mailing lists archives from mailman2 to lists-next to measure database size, but it's enabled for now. I'm also going to see if we can get python-xapian-haystack fixed via buster-updates...