Search results for "Postorius" - Mailman-users

Re: Mailman 3 installation from latest Debian packages

by Mark Sapiro

On 2/12/21 4:49 AM, Matthew Blissett wrote: > Hi, > > I've installed mailman3-full 3.3.3-1 from Debian bullseye (Debian testing). > > The dropdown controls on the UI for Postorius (e.g. "Subscription > requests", "Mass operations" and the username button to log out) and the > similar controls on Hyperkitty (e.g. "Threads by month") do not work. > You can see the latter at > http://newlistszm.gbif.org/mailman3/hyperkitty/list/test@newlistszm.gbif.or… Everything works as expected at <https://lists.mailman3.org/mailman3/> and <https://mail.python.org/mailman3> which are installed from source. > Could this be a problem with the Debian packaging, or perhaps my > configuration -- which is very close to the defaults (i.e. Mailman and > Apache configuration generated by dpkg). I can't speak to the Debian package possibility, but it might possibly be related to the way your browser handles the javascript. I don't know anything in configuration that would cause this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: Configure administrative users via command line?

by Mark Sapiro

On 7/18/23 11:38, kjohnson(a)eclypse.org wrote: > > How can I configure administrative users via command line? I need to process a moderation request. I have root access on the server. A pointer to the appropriate documentation would be more than welcome. Thank you to anyone who can provide help. I'm not sure what you want. If you are an owner or moderator of a list or a superuser, you can handle moderation requests via Postorius. If you are a list owner or a superuser, you can manage owners and moderators via Postorius. You can add superusers via the command line django admin `createsuperuser` command. It might be good if the command line `mailman addmembers` and `mailman delmembers` commands accepted a `role`, but they don't. You can manage owners and moderators via the REST API which you can access via curl. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. You can also do this via `mailman shell`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: List description as sender

by Mark Sapiro

On 09/14/2018 05:35 AM, Henrik Rasmussen wrote: > When receiving a mail from Mailman 3, the From: User name is the description of the list, like From: Long desription of the list for all members of certain project <project(a)lists.example.com>. > > Starting to get old, I recall something about a discussion we once had on http://mail.python.org/pipermail/mailman-users/, but I don't recall the reason for this and I can't find the discussion, so it might be something I dreamed. Specifically what messages are you talking about? The only case I see offhand where the From: is as you describe is in posts from an anonymous list. In any case, the list description is described in Postorius as "This description is used when the mailing list is listed with other mailing lists, or in headers, and so forth. It should be as succinct as you can get it, while still identifying what the list is." I.e., it shouldn't be a long description. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years

Re: urls.py location on venv install

by Torsten

Am 2026-08-10 15:13, schrieb Stephen J. Turnbull: > Torsten writes: > > > >> I have just nearly finished the migration of Mailman 3 from > > >> Debian packages to venv and mailman (master and runner) is up > > >> and running and uwsgi is also up and running. > > It looks like you are trying to use the configuration files from > Debian with minimal or no changes. > > If I were you I would > > 1. rsync -av /etc/mailman3 /tmp/ # if you don't have rsync, "cp -r" > 2. purge (not just uninstall) all the Debian mailman packages > this should delete a lot of the stuff you just copied to /tmp > 3. copy the configuration from Mailman's virtualenv install > instructions into /etc/mailman3 > 4. diff -r /etc/mailman3 /tmp/mailman3 > 5. make only essential changes you see in that diff (eg, > /opt/mailman/mm/var/web to /var/lib/mailman3/web), and see if > things work better > 6. if things still don't work, make more adjustments. > > Steve Yes, that was my intention. But now I started from scratch, following the documentation about Virtualenv installation at mailman3.org and also created the config files with the defaults shown there (with a few adjustments to match my installation). Now, I have everything running as user mailman (had user list before for mailman-core and www-data for mailman-web). And the tracebacks have changed: mailman throws this one: 2026-08-10 16:11:20 [FALCON] [ERROR] GET /3.1/lists?advertised=true&count=0&page=1 => Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.13/site-packages/falcon/app.py", line 476, in __call__ process_resource(req, resp, resource, params) ~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailman/rest/wsgiapp.py", line 65, in process_resource raise HTTPUnauthorized( ~~~~~~~~~~~~~~~~^ '401 Unauthorized', ^^^^^^^^^^^^^^^^^^^ 'REST API authorization failed', ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ challenges=[realm]) ^^^^^^^^^^^^^^^^^^^ TypeError: HTTPUnauthorized.__init__() takes 1 positional argument but 3 positional arguments (and 1 keyword-only argument) were given [10/Aug/2026:16:11:20 +0200] "GET /3.1/lists?advertised=true&count=0&page=1 HTTP/1.1" 500 38 "-" "GNU Mailman REST client v3.3.5" and mailman-web this one: ERROR 2026-08-10 14:11:20,011 1557501 postorius Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.13/site-packages/postorius/views/list.py", line 1141, in list_index lists = paginate( _get_list_page, ...<2 lines>... paginator_class=MailmanPaginator, ) File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate objects = paginator.page(page_num) File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 46, in page number = self.validate_number(number) File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/paginator.py", line 53, in validate_number if number > self.num_pages: ^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) ~~~~~~~~~^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/core/paginator.py", line 99, in num_pages if self.count == 0 and not self.allow_empty_first_page: ^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django/utils/functional.py", line 57, in __get__ res = instance.__dict__[self.name] = self.func(instance) ~~~~~~~~~^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/django_mailman3/lib/paginator.py", line 56, in count return self.function(count=0, page=1).total_size ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/postorius/views/list.py", line 1137, in _get_list_page return client.get_list_page( ~~~~~~~~~~~~~~~~~~~~^ advertised=advertised, mail_host=mail_host, count=count, page=page ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/client.py", line 211, in get_list_page return Page(self._connection, url, MailingList, count, page) File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/page.py", line 37, in __init__ self._create_page() ~~~~~~~~~~~~~~~~~^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page response, content = self._connection.call(self._build_url()) ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/venv/lib/python3.13/site-packages/mailmanclient/restbase/connection.py", line 160, in call raise HTTPError(params.get('url'), response.status_code, error_msg, response, None) urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} ERROR 2026-08-10 14:11:20,041 1557501 django.request Internal Server Error: /mailman3/lists/ ERROR 2026-08-10 14:11:20,041 1557501 django.request Internal Server Error: /mailman3/lists/ I have taken the old database from the Debian configuration and moved it to /opt/mailman... where it should belong (I hope).

1 month, 2 weeks

Upgrade

by Mark Sapiro

On 5/22/19 2:07 PM, David Krantz wrote: > Hi all, > > I am running a relatively old version of mailman 3, namely 3.2.0a1 > from late september 2017. This is installed using the old > mailman-bundler method. I use postfix and postgres. > > I really have two questions: > > First: What is the normal way to upgrade such a setup? I guess that I > just can get the updated versions of all packages through git, set up > new venv's to simplify a rollback, back up the database and then just > restarting with the new version hoping for the best. That's more or less correct. I did this on mailman3.org a little over a year ago. I suggest you see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which describes much of what I did. you can also see <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=re…> for what I had with Mailman Bundler. The biggest hurdle is now Postorius and Hyperkitty are Python3 so you need Python3 versions of various dependencies. Here's roughly what I did. git clone everything from GitLab. As a developer, I've always been running off the heads. There are occasional glitches, but I can work around these. You can also install from PYPI if you want more stability. Everything is mailman, mailman-hyperkitty, mailmanclient, django-mailman3, hyperkitty and postorius. But, I'm getting ahead. Create a new python3.5+ virtualenv. Python3.5 is the minimum, but 3.6 or 3.7 would be even better. Activate that virtualenv and if you are using the branches from GitLab, in each branch directory, do python setup.py clean --all python setup.py install or just pip install everything. You also need to do the things indicated in the Preliminaries and Installation sections of <https://wiki.list.org/DOC/Mailman%203%20installation%20experience>. Also see the Migration section for scripts I use to update from GitLab and build 'everything' and the rest of the document too. Then once you have things set up, it's pretty much a matter of just updating the various scripts you use to run things to point to the new command files in, in my case, /opt/mailman/mm/bin/. One caveat to note is if you are using the Whoosh backend. The Python2 version is incompatible with Python3 so you need to remove the fulltext_index directory and run the django management rebuild_index command to recreate it. You should be able to just run rebuild_index or maybe clear_index followed by update_index without removing the old index first, but there are reports that this doesn't work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 4 months

Re: User cannot reset password

by Greg Newby

On Sun, Aug 11, 2024 at 11:10 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/11/24 10:56, Greg Newby wrote: > > I imported MM2.1 lists to Mailman3 (using import21 - details are in my > > previous messages to mailman-users), and have had a couple of reports of > > people for whom the password reset function via "Forgot password" on the > > list login screen doesn't work as expected. > > > Django (web) accounts (Postorius and HyperKitty) are separate from > Mailman core. Users inported from MM 2.1 do not have web accounts. They > have to sign up, not request a password reset. > 1. Will the new (Django) and imported (Postorius) usernames automatically be matched to the same email address? The goal is for someone to use the web-based front end to manage their migrated subscriptions. 2. How can I customize the email that went to users who selected "Forgot password?" ( You are receiving this email because you, or someone else, tried to access an account with email I didn't find that string in the source code. Thanks as always! ~ Greg

2 years, 1 month

Re: My list has been switched from public to private archives, but they are still visible

by Abhilash Raj

On Thu, Sep 19, 2019, at 11:15 AM, Enrique Terrazas wrote: > I am having a very similar issue. Here is what I have found: > > There are basically three archive settings we can select via the > postorious web front end for archives. These can be found in: Settings > > Archiving and they are: > Public archives > Private archives > Do not archive this list This is interface of Mailman to set the archives. > > In the Django administrative interface we can find those > same(?/similar?) settings here: Main Page > Hyperkitty > Mailing lists > > Mailing List object(x) > Archive policy: > never > private > public This is basically a hotline to the database. You can change these values, but they would be overriden with the values that are in Mailman Core on the daily cron job run. I would suggest not to tinker with values there since you could leave database in a corrupted state. Since there is an ORM layer there, chances are less but still a possibility :) > > I’m not sure which of the two takes precedence. My guess is postorius > since that is a list owner accessible setting and the Django > administrative interface would typically not be accessible to list > owners. We have noticed the following odd behavior, not sure if it is a > bug. For existing lists with private archives, when switching to “Do > not archive this list” in postorious, the desired effect of no longer > archiving the list is instantaneous. However, after the daily cron job > that syncs with Mailman Core happens, the existing archives now become > publicly accessible. Is this behavior based on the assumption that the > list will no longer be archived and will therefore be purged? Source of truth is Mailman Core's database. Postorius is a front-end to change that and owners have permissions to do that. Hyperkitty only syncs back that information daily. I have a fix in the master which makes such that this information is synced synchronously and is available immediately to Hyperkitty. For now, you could either run the "python manage.py runjobs --daily" or wait for a day if that is possible. > Enrique > > > On Sep 19, 2019, at 1:08 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Thu, Sep 19, 2019, at 3:31 AM, Paul Arenson wrote: > >> Can anyone help with this? > >> > >> I set my list to private archives today. Up until then, it was pubic. > >> And yet, if you go to the list page, you will see that if you click > >> archives (top left), you can see them. (Filled with a bunch of tests > >> posts for now) > > > > This change takes a bit of time to sync up Hyperkitty. THere is a daily > > cron job which syncs this information from Mailman Core. > > > > I have made a change which should fix this problem and the process would > > become synchronous. > > > > You can run `python manage.py runjobs --daily` command to force sync > > that information. > > > >> > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flist.toky… > >> > >> Am I misunderstanding what a private archive is? > > > > Not really, your expectation is right. > > > >> > >> Is something wrong with my setup (which is hosted)? > >> > >> Thank you. > >> _______________________________________________ > >> Mailman-users mailing list -- mailman-users(a)mailman3.org > >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org > >> https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > >> > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > Mailman-users mailing list -- mailman-users(a)mailman3.org > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > > https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai… > > -- thanks, Abhilash Raj (maxking)

7 years

Re: Error Logging - what changed with the New Year releases?

by Mark Sapiro

On 1/14/23 11:44, Odhiambo Washington wrote: > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> Nothing in those releases per se would affect this. This is Django and >> django-allauth. Perhaps when you updated the Mailman packages, you also >> updated these dependencies. >> > > Which dependencies would those be? Django and django-allauth. > When I upgraded, the command I ran was: > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > mailman-hyperkitty django-mailman3 Do you mean --force-reinstall? pip has no --force option. I *think* --force-reinstall will upgrade dependencies. Depending on your pip version, --upgrade alone may or may not upgrade dependences. Older versions of pip will, but newer versions, at least without --force-upgrade require --upgrade-strategy eager to update dependencies. > And how do I find out what is suppressing the logging for the social > accounts? That's a django-allauth question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: MM2 -> MM3 Migration: listinfo page

by Jeremy Stanley

On 2023-03-09 13:49:09 +0300 (+0300), Odhiambo Washington wrote: [...] > I'd rather not touch the MM2.1 domain because references have been made to > it in publications. > What I am struggling with is the listinfo.html file: > ``` > https://lists.kictanet.or.ke/mailman/listinfo/kictanet > ``` > I am struggling to add reference to the MM3 subscription link user the > " Subscribe to KICTANet by filling out the following form:" > The HTML code to insert there beats me :) Redirecting the listinfo pages to your Postorius interface should be sufficient to keep those URLs which are referred to in publications working. We do basically the same thing Mark mentioned, for the reasons you say you don't want to: https://opendev.org/opendev/system-config/src/commit/ae7884a/playbooks/role… If someone follows a link to the old MM2 https://lists.opendev.org/cgi-bin/mailman/listinfo/service-discuss URL they get redirected to https://lists.opendev.org/mailman3/lists/service-discuss.lists.opendev.org/ so that there's no risk they'll try to use the old MM2 subscription form. -- Jeremy Stanley

3 years, 6 months

Re: configuring postfix local recipient table

by Alexander Inzinger-Zrock

Am 28.04.25 um 16:27 schrieb Stephen J. Turnbull: > Alexander Inzinger-Zrock via Mailman-users writes: > > > + also checked that command ''postmap'' (under /usr/sbin) is available > > for user 'mailman' (usr/sbin was not in path; it is now). > > This should not matter since the full path is in postfix.cfg, so > Mailman should find it and run it unless there is some permissions > problem or the executable itself is broken, regardless of PATH. > > You've probably run all these pretty recently, but if you've made any > changes since then: > > What is the output of the "mailman lists" command? (expect the test > list with domain) 2 matching mailing lists found: testliste01@MY_DOMAIN testliste02(a)my-example.com + MY_DOMAIN - replaced my domain by MY_DOMAIN + second was a test domain, created via postorius to check if i mesed up with the first one - no differences > What is the output of the "mailman aliases" command? (expect none) Indeed, none. > After "mailman aliases" do you get aliases in the postfix_lmtp file? > No.

1 year, 5 months

Mailman-users search results for query "Postorius"