On 2/27/26 07:17, Ibiam Chihurumnaya via Mailman-users wrote:
Currently running Mailman 3.3.10 and I followed the instructions from https://docs.mailman3.org/en/latest/install/virtualenv.html# to install.
OK.
I get something else when I do it differently - how I've been doing it so far -.
mailman shell Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not.
from mailmanclient import Client from mailmanclient import Client client = Client('http://localhost:8001/3.1', '**', '**') sg = client.domains[0] sy = sg.get_lists()[-1] sy <List 'systems-logs@lists.sugarlabs.org'> sy.settings {'acceptable_aliases': [], ...
OK. You are using Mailman Client which is a bunch of Python bindings for Mailman core's REST API and which is intended for use by HyperKitty, Postorius and Django-Mailman3 to communicate with Mailman core via its REST API.
If you are using mailman shell you already have direct access to all
of Mailman core. Using Mailman Client is just adding overhead to things
you could do directly.
If you really want to use Mailman Client, rather than invoking mailman shell and all it brings that you don't use, you could just invoke your
venv's python, e.g.,
$ /opt/mailman/venv/bin/python
or if your venv is active, just
(venv) $ python
and then import Client and continue as above.
Yes, but like I've mentioned in another thread, I don't have access to the web UI because I can't get a confirmation link.
You can always confirm your address manually
UPDATE account_emailaddress SET verified = 't' where email = 'your_address';
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan