Search results for "Postorius" - Mailman-users

Re: How to upgrade to 3.10

by Paul Tomblin

On Tue, Mar 3, 2026, at 12:30 AM, Mark Sapiro wrote: > > But it looks like here it's trying to install 3.3.10. > >> Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) >> ... a bunch of these ... >> INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. >> Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) >> ...a bunch more... > > Is there any conflict reported in this `bunch more` to force 3.3.9? What > if you do `pip install mailman==3.3.10`? All the "...a bunch more..." lines are "Requirement already satisfied". And here's what happens when I try to do as you suggested: (venv) $ pip install mailman==3.3.10 Collecting mailman==3.3.10 Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: aiosmtpd>=1.4.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.4.6) Requirement already satisfied: alembic!=1.7.0,>=1.6.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.18.4) Requirement already satisfied: atpublic in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (7.0.0) Requirement already satisfied: authheaders>=0.16 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (0.16.3) Requirement already satisfied: authres>=1.0.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.2.0) Requirement already satisfied: click>=8.0.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (8.3.1) Requirement already satisfied: dnspython>=1.14.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (2.8.0) Requirement already satisfied: falcon>=3.1.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.2.0) Requirement already satisfied: flufl.bounce>=4.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.0) Requirement already satisfied: flufl.i18n>=3.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (6.0.0) Requirement already satisfied: flufl.lock>=5.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (9.0.0) Requirement already satisfied: gunicorn in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (25.1.0) Requirement already satisfied: lazr.config in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (3.1) INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13" I guess I need to upgrade my python version? -- Paul Tomblin

3 months, 2 weeks

Re: Hyperkitty performance problem

by Mark Sapiro

On 12/28/24 05:19, monochromec via Mailman-users wrote: > Following the root cause analysis which Tobias started all those weeks ago we (the admin team behind the installation) are still struggling with the following phenomenon: messages on average take more than 24 hours to be processed, more precisely, the average lifetime of a pickled message object in `/var/lib/mailman3/queue/pipeline` clocks in at around 26 hours). This issue is with Mailman core's pipeline runner. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/8-mil… for an overview of message handling and queues in Mailman core. It seems that the pipeline runner(s) are taking an inordinately long time to process a message through the pipeline of handlers causing the pipeline queue to become backlogged. > Couple of stats of the installation: standard installation from Bookworm OS repos, Hyperkitty as archiver and Postorius as web frontend as explained above, running Python 3.11.2 from the standard systemd service as packaged with the Bookworm deb file. All backends (Core + Hyperkitty) are supported by Postgres version 15+248. The MTA is a standard Postfix installation, again from OS packages. The primary support for Debian packages is Debian. See https://wiki.list.org/x/12812344 > The underlying VM has 7 cores with just under 24 GB of main memory. This production instance is handling less than 130 mailing list (MLs) with an average of less than 10 postings per day per ML. CPU core utilisation hovers around 50% with the lion share allocated to the four pipeline runners as part of the MM configuration. This is an average of less than 1 message per minute. Processing a message through the pipeline should take nowhere near a minute. Possibly there is an issue in the rfc_2369.py handler. This handler communicates with HyperKitty via mailman_hyperkitty to obtain values for the List-Archive: and Archived-At: headers added to the message. Possibly there is some configuration issue with mailman_hyperkitty that causes these queries to take a long time and possibly eventually time out. Are there any `Connection to HyperKitty failed:`, `HyperKitty failure on ...` or `Invalid response from HyperKitty` type messages in mailman.log? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Mailmanweb RAM Usage

by Odhiambo Washington

On Sun, Oct 12, 2025 at 9:48 AM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Odhiambo Washington via Mailman-users writes: > > On Sat, Oct 11, 2025 at 5:10?PM Stephen J. Turnbull <steve(a)turnbull.jp> > > wrote: > > > > Do you mean only HyperKitty + Postorius? That seems like a lot. > > > Yes, just Hyperkitty+Postorius: Please see > > https://imgur.com/a/LPAY69N It represents what I see daily when I > > run btop. It's always around 2GB, but rarely do I see above. I > > only have 1 major active mailing list on this server. There are > > other inactive ones. > > I'm not sure what's going on. I'm pretty sure you would save up to > 1.5GB by switching to gunicorn vs the uwsgi configuration you have. > > But the uswgi project has acquired functionality the way systemd has > over the last few years. It seems likely that you could configure it > to save a lot of memory by removing functionality you don't use. Not > sure whether than involves recompiling or just disabling unused > plugins, I'm not really familiar with uwsgi, since even for the > largest instances I've seen gunicorn is sufficiently performant and > secure. > I will switch to gunicorn and see how that goes. > The MySQL footprint also seems a bit high. but not insane, my > PostgreSQL weighs in at about 1.2GB-1.5GB. > My MariaDB is running some WordPress websites. Mailman is just one other application using it. Last week, I tried to migrate the MM3 DB to PostgreSQL, but didn't quite succeed at the last minute. It's an exercise for another day. Overall, you don't have an insane configuration, but it depends on > what you're optimizing for. > Thank you for looking into this. I will update once I have made the changes. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

8 months, 1 week

Re: Welcome Message

by Abhilash Raj

On Wed, Apr 17, 2019, at 1:41 PM, brian(a)emwd.com wrote: > Abhilash Raj wrote: > > If the URL for template is wrong, or Postorius is down for whatever reason, > > the subscription will fail with the error that you saw before. > > Explain URL for template. You mean "POSTORIUS_TEMPLATE_BASE_URL"? That > is not wrong. I am confident of that. It is back to > "http://mailman-web:8000". I can successfully ping mailman-web:8000 > from bash. POSTORIUS_TEMPLATE_BASE_URL is used to create the template urls, yes. > > > > I logged out of Postorious and subscribed using the > > > subscribe form on > > > the info page and the change to the welcome template showed up. So it > > > looks like being logged in as admin while trying to subscribe someone > > > was what was causing the problem. Is that a bug I discovered? > > I suspect stopping-restarting and re-creating the template (idk, if you > > really did that) might have something to do with it. I am not sure if this > > is a bug unless you can reliably reproduce this. > > This error is absolutely reproducible. It even impacts other list > admins who are trying to use a custom welcome message and subscribing a > member while logged into Postorious. Everything else is working fine on > this server and I followed your directions precisely when I set this > server up. Please help. Can you reply here with the output of this query on your server: $ curl --user restadmin:restpass -L http://172.19.199.2:8001/3.1/lists/mailman-users.mailman3.org/uris Please replace "restadmin:restpass" with the username password of the rest api, if you have customized it. It not leave it as it because that it the default. Also, replace "mailman-users.mailman3.org" with the the List-ID of your mailing list. (replace @ with .) in your posting address. If you don't have curl, choose whatever http client you have. > > Thanks, > Brian > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Re: Hyperkitty on Debian 12

by Michael Oberrauch

On Tue, 2024-03-26 at 08:06 +0100, Markus Grandpré wrote: > Dear Mr Sapiro, > > thank you very much for your help. The required command is: > > # mailman-web hyperkitty_import \ > -l mailman21-migration-test-04(a)mailman.uni-konstanz.de \ > /var/mailman21/testlist.mbox > > Due to the following warnings, I still have to customize Hyperkitty: > > django_mailman3.MailDomain: (models.W042) Auto-created primary key > used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > DjangoMailman3Config.default_auto_field attribute to point to a > subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. > ... > > Can you give me another hint? As Linux admin I installed the packages > mailman and mailman-web that were offered to me under Debian 12. > Although during the installation of the packages user "list" was > created, I cannot use it: > > # su - list > This account is currently not available > > As with Mailman 2.1, I will probably have to continue working with > Mailman3 as root. Too bad that there is no documentation for Debian > admins like me, who don't want to dive too deep into the python > framework. Or have I overlooked something? > > Best regards, > Markus > > Hi Markus, we are also running MM3 on Debian 12 from Package Repositories. First of all, you should not try to directly switch user (su) to the lists user, it's generally intended to executes commands as that user, if necessary; either using `runuser`, `sudo`, or `su -c`. However, the prepackaged scripts `mailman-wrapper` and `mailman-web` already do this and therefore you ca run those as root without permission problems. On Debian there are two relevant users for MM3: the list user runs mailman core, whereas the www-data user runs Postorius and Hyperkitty. So you have to make shure, that the www-data user can access the .mbox files while importing. Hope that helps. Cheers, Michael -- Michael Oberrauch (er/ihm) Computerreferent Fachschaft Mathematik/Physik/Informatik/Chemie Studentische Vertretung Technische Universität München Boltzmannstraße 3 85748 Garching eMail: oberrauch(a)fs.tum.de Tel: (+49) 089 289 18545 Fax: (+49) 089 289 18546 https://mpic.fs.tum.de

2 years, 2 months

Error after upgrading mailman3

by Gelpi Andrea

Hi, in my installation the command mailman notify does not exist. Checking the debian packages I noticed the I could upgrade mailman form 3.2.1 to 3.2.2; mailman-web form 20180916-8 to 20180916-10; python3-django-hyperkitty from 1.2.2 to 1.3.2 I did it with apt-get install After that when I try to go to a postorius page the error Mailman REST API not available. Please start Mailman core in mailman log I found: May 4 15:13:08 posta mailman3[10259]: Cannot import runner module: mailman.runners.rest.RESTRunner May 4 15:13:08 posta mailman3[10259]: Traceback (most recent call last): May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/bin/runner.py", line 55, in make_runner May 4 15:13:08 posta mailman3[10259]: runner_class = find_name(class_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/utilities/modules.py", line 52, in find_name May 4 15:13:08 posta mailman3[10259]: module = import_module(module_path) May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module May 4 15:13:08 posta mailman3[10259]: return _bootstrap._gcd_import(name[level:], package, level) May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 1006, in _gcd_import May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 983, in _find_and_load May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 677, in _load_unlocked May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap_external>", line 728, in exec_module May 4 15:13:08 posta mailman3[10259]: File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/runners/rest.py", line 27, in <module> May 4 15:13:08 posta mailman3[10259]: from mailman.rest.wsgiapp import make_server May 4 15:13:08 posta mailman3[10259]: File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 25, in <module> May 4 15:13:08 posta mailman3[10259]: from falcon.routing import map_http_methods, set_default_responders May 4 15:13:08 posta mailman3[10259]: ImportError: cannot import name 'map_http_methods' from 'falcon.routing' (/usr/lib/python3/dist-packages/falcon/routing/__init__.py) I think there is a dependency error somewhere. Is there a way to solve it? Thank You -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

6 years, 1 month

Re: An archive/read-only list on a full setup?

by Mark Sapiro

On 4/11/23 09:36, Andreas Schamanek wrote: > > I have a working full installation of mailman3, postorius and hyperkitty > (on Debian 11). Now I wanted to host the archive of a remote list, and I > am wondering how to do this properly. > > After I found no documentation and no posting I simply created a list in > mailman3 with only 1 dummy member. The list address is subscribed to the > actual remote list. So, messages arrive and are archived. But that's not > optimal because hyperkitty thinks it's a normal list where it should be > read-only and do not allow subscriptions etc. > > What's the proper way to set up a hyperkitty-only list? There really isn't one as HyperKitty is intended to archive Mailman lists, however, it is possible to have a list in HyperKitty without a corresponding Mailman list. Thus, in your case you could just remove the Mailman 3 list you created and leave the HyperKitty list. Then you have an issue with posts, so you can keep sending the posts to be archived to the prior list address, but arrange for the incoming MTA to pipe mail to that address to a process. That process would do the following. Add a Unix From_ line at the beginning of the message and write the result to a temp file. Invoke a command like django-admin hyperkitty_import --no-sync-mailman --since 1990-01-01 \ -l list(a)example.com /path/to/the/tempfile where list(a)example.com is the actual HyperKitty list. This will archive the message. The addition of a Unix From_ line is to make the message file look like a mbox. Since there is no Mailman list, attempts to post or reply directly from HyperKitty will fail, although such attempts using email software will probably succeed in archiving the mail, and mail directly to that list address will be archived, but such messages won't go to the remote list. This may not be any better than what you're currently doing. -- 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: "The content of this message was lost."

by Jens Günther

You have to incorporate these 2 changes: https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs and https://gitlab.com/mailman/mailman/-/merge_requests/933/diffs We made it persistent in the Dockerfile of mm-core, so that it will be rewritten every time when building the container: COPY ./moderator.py /usr/lib/python3.8/site-packages/mailman/app/moderator.py COPY ./test_moderation.py /usr/lib/python3.8/site-packages/mailman/app/tests/test_moderation.py It is already fixed in Postorius 3.3.6, but it's not clear, when maxxking's containers will be bumped to that version. Am 09.09.22 um 16:33 schrieb skenny(a)scss.tcd.ie: > I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). > > This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. > > In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read > > The content of this message was lost. It was probably cross-posted to > multiple lists and previously handled on another list. > > I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? > > Thanks for any advice. > Stephen > > PS: > The Mailman web interface "System Information" link reports: > Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) > Mailman Core API Version 3.1 > Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0] > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

3 years, 9 months

Re: Moderator e-mails only going out once a day

by Odhiambo Washington

On Mon, Apr 21, 2025 at 10:16 PM dgoldsmith--- via Mailman-users < mailman-users(a)mailman3.org> wrote: > I am having a similar issue as Joe. > > Our Mailman 3 server is running on Rocky Linux 9.5. It is deployed using > a Python virtual environment. > > (venv) [mailman@<server> shunt]$ mailman info > GNU Mailman 3.3.9 (Tom Sawyer) > Python 3.9.21 (main, Dec 5 2024, 00:00:00) > [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] > config file: /etc/mailman3/mailman.cfg > <output trimmed> > > Mailman 3.3.9 > Postorius Version 1.3.10 > HyperKitty version 1.3.9 > Postfix = 3.5.25-1.el9 (may have some newer bits backported into it - RHEL > way) > Django version = 4.2.13 > > Output of the for loop Mark provided above shows that all the lists on the > server have admin_immed_notify set to True. > > Here is the activity from the mailman.log file when I send a message to > the list and it gets held: > > Apr 21 19:11:37 2025 (2564) sans-faculty: DMARC lookup for > dgoldsmith(a)sans.org (_dmarc.sans.org) found p=reject in _dmarc.sans.org. > = v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email > Apr 21 19:11:37 2025 (2564) HOLD: sans-faculty(a)mlm.sans.org post from > dgoldsmith(a)sans.org held, message-id= > < > SJ0PR18MB5112D63A7D9F3851A4A6B0C0AEB82(a)SJ0PR18MB5112.namprd18.prod.outlook.com>: > The message comes from a moderated member > > No further activity indicating it sends (or attempts to) a notice to the > list admins/mods about a held message. > Assuming you did run the mailman shell command and the output was: ```List sans-faculty(a)mlm.sans.org Immed notify True``` What do you have in your MTA logs around the same time? Nothing? That would imply that for this list, you have set "Default action to take when a non-member posts to the list" to "Discard" If you change that setting to "Hold for moderation", then you will receive a notification. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 1 month

Re: There are currently no mailing lists!?

by Odhiambo Washington

On Mon, Jul 22, 2024 at 9:06 PM Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > I recently upgraded Debian 10 'buster' and when I logged in to Postorius in > the browser I got the ' Mailman REST API not available. Please start > Mailman > core' message. So I started it up from the command line doing 'sudo -u > mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded > You upgraded Debian from Buster to what??? Bullseye or Bookworm? Why not just 'sudo systemctl start mailman'? > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists > ' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? > The lists are there since your DB is intact and your venv is intact as well. > > What am I doing wrong/what's going on here please? Thank you in advance. > I suspect your Python was upgraded to a version different than the one you use to create your virtualenv in the 1st place. If that is the case, you'll need to create a new virtualenv and migrate the data. > One more thing...I am running mailman core version GNU Mailman 3.3.5, Core > API Version 3.1, and Core Python Version 3.7.3. > Is there a reason you did not upgrade MM3 core and MM3 Web all this time? Anyway, check the version of Python used to build your virtualenv against the system version after you upgraded: # cat /opt/mailman/mm/venv/pyvenv.cfg home = /usr/local/bin include-system-site-packages = false version = 3.11.2 executable = /usr/local/bin/python3.11 command = /usr/local/bin/python -m venv /opt/mailman/mm/venv If older than the system version, you just need to build a new virtualenv and migrate the data. HTH. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

Mailman-users search results for query "Postorius"