Search results for "Postorius" - Mailman-users

MM3 Bounces status

by Ruth Ivimey-Cook

Hi, I have some lists which are used primarily as a distribution method (rather than chat) and the person who uses these lists doesn't have access to the detailed MM logs and is not interested in that. It would be very helpful for message bounces (& any other anomalous events, if any) were to be available to that person for each message that is sent out, in a manner similar to mailgun et al. I know something of the bounce processing MM3 does, but it seems to be totally hidden from e.g. the postorius end of things (unless I'm missing something?). Is there a way for bounce events to be emailed to the list owner, or for something to be available in postorius to show this info? If not in the standard package, do other people have ad-hoc solutions to this issue? My ideal option would be for a configurable per-message email or postorius link that reports the number of emails to send (=number in mlist), the number on 'no-mail', the number sent successfully (=no bounce?), the emails of those who bounced (with bounce score), and emails of blocked sends (eg by multiple bounces). So for example: Bounce report for listname: Email Subject: Announcement Sent: today at time From Email: user(a)example.com received (today at time) To List: listname(a)example.com with 100 subscribers; 89 successful; 4 bounces; 3 blocks; 4 nomail; Bounces: - foo(a)bar.example.com (no mailbox) - bar23(a)foo.example.com (timeout) - alice(a)baz.example.org (mailbox full) - bob(a)example.net (bounce-reason) Blocked: - foo(a)bob.example.com (score 3) - bar23(a)alice.example.com (admin ban) - alice(a)alice.example.org (score 2) I suspect that my ideal option would require changes to the internal processing, because MM would need to keep more information about bounces than I think it currently does. It might also need to retain more information about LMTP delivery statuses? Thanks in hope? Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog:http://www.ivimey.org/blog LinkedIn:http://uk.linkedin.com/in/ruthivimeycook/

2 years, 1 month

Using REST api to subscribe member

by Brian Carpenter

I have a development server that only has Mailman core installed on it. I used a virtual environment to do the installation but I did not install Postorius or Hyperkitty as I am currently working on developing a custom u.i. for Mailman 3. My programmer said the following: "I have a problem with mailman on development server ... I was trying to add member to a list using REST api, but to no avail. After I tried all possible and impossible things, I finally looked at the logs. Error I found in log file is: IsADirectoryError: [Errno 21] Is a directory: '/opt/mailman/mm/venv/lib/python3.7/site-packages/mailman/templates' I guess mailman was looking for a template for welcome mail, and failed for some reason. I also guess this has something to do with locale or language settings I tried googling, but couldn't find anything" The log that gave the error was /opt/mailman/mm/logs/mailman.log My programmer tried it on another server that has both Postorius and Hyperkitty working and the api call worked, i.e. added the member to the list and sent out a welcome email. So what else do I need to install to be able to use the api to add members to a list using a non-postorius interface? Any assistance would be appreciated. Thanks, Brian

6 years, 8 months

Re: First time mailman installation

by Roland Giesler

On 2024/07/25 08:51, Odhiambo Washington wrote: > On Wed, Jul 24, 2024 at 12:23 AM roland--- via Mailman-users > <mailman-users(a)mailman3.org> wrote: > > I have installed mailman3 on Ubuntu including postorius & > hyperkitty (from the packages). > > I have questions now which are not quite clear to me from the docs: > > > Hi Roland, > > Which guide did you use to install mailman3? I simply installed it from Ubuntu packages. > > 1. How do I specify my mail server details (which is my own server > running postfix, etc) > > > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h… That is a guide that provides basic info, but there's not reference to secure protocols, so I suppose it's just a bit dated. I have a great, secure couple of server (running power-mail-in-box), so I don't want to venture into the manual mail-server setup territory, with all it's accompanying spam and security requirements. The mailings list should just use one (or more) or those servers. As I have written in another post I made, I have set the (apparently) appropriate parameters in the mailman.cfg, but I still get "relay access denied" from my external MTA, which mean that authentication is not even attempted, or am I mistaken? > 2. How do I create new lists from the postorius UI, or can I only > do that in the config files or the command line console for mailman3? > > > Once everything is up and running and you have the Postorius UI, you > can always use the Django Admin interface to manage stuff. > It's available at https://FQDN-FOR-YOUR-SITE/admin > <https://FQDN-FOR-YOUR-SITE/admin>. > How do you log in? You create a "superuser" account using CLI, then > use it. Now that depends on how you installed MM3. I figured that out already. Thank you. Roland

2 years, 3 months

Mailman Suite release announcement

by Abhilash Raj

Hi All, I am pleased to announce new releases for Mailman Suite, including - Mailman Core 3.3.0 (Tom Swayer) - Mailmanclient 3.3.0 - django-mailman3 1.3.0 - Postorius 1.3.0 - Hyperkitty 1.3.0 This is a feature release and also includes a bunch of bugfixes. I am really really thankful to a lot of contributors who have helped out with this release. It is really nice to see Mailman 3 gaining more users and contributors. Python 3.5 is the minimum supported version, but all the releases have been tested to work with Python 3.5-3.7. This is the last release to support Python 3.5 since it has been in security only maintenance mode for a while now. Some of the highlights of this release includes: Mailman Core 3.3.0 - Support for ARC signing. Thanks to Gene Shuman and Stephen Turnbull. - Many many improvements to "mailman import21" command. Thanks to Mark Sapiro. - Addition of French templates. Thanks to Stéphane Parunakian. - A better and more scalable REST API server using Gunicorn. - Support for SMTPS/STARTTLS. Thanks to J08ny. A full copy of change log is available at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html Postorius 1.3.0 - Many more settings for MailingList configuration exposed, including preferred language, digest related settings. - Support for FILTER_VHOST to filter MailingLists based on the serving domain. Thanks to Nate Coraor. - Ability to write MailingList info in Markdown to render info in HTML instead of Plaintext. A full copy of change log is available at: https://postorius.readthedocs.io/en/latest/news.html Hyperkitty 1.3.0 - Unread messages, when logged in, are more easily recognizable with blue envelope icon. - Improved thread view with colored background for quoted parts of messages. - Improved readability on small screens by removing the indentation in thread view. A full copy of the change log is available at: https://hyperkitty.readthedocs.io/en/latest/news.html All the packages are available to download from PyPi (https://pypi.org) https://pypi.org/project/postorius/ https://pypi.org/project/hyperkitty/ https://pypi.org/project/django-mailman3/ https://pypi.org/project/mailman/ https://pypi.org/project/mailmanclient/ -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Re: HyperKitty failure

by Mark Sapiro

On 1/2/22 4:34 AM, horvath.arpad.szfvar(a)gmail.com wrote: >> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a >> response from Django REST framework which is a json representation of >> your mailing lists info? > > In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . when you view https://lists.xxx.hu/postorius/lists/ is there a Filter by Role dropdown at the top of the listing? If so, if you select `All` do you then see the lists. Postorius by default shows only those lists in which you have a role. If you still don't see the lists, what does the command `mailman lists` show? > I guess the setting below is not good. > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Should I set it to > ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. It needs to be an IP. Set it to `('xxx.xxx.xxx.xxx', '127.0.0.1', '::1')` where xxx.xxx.xxx.xxx is the IP of lists.xxx.hu or just `('xxx.xxx.xxx.xxx',)` would probably work. > And what about MAILMAN_REST_API_URL? > How can I found its proper value? It's currently the default value > but if I try to reach it with > wget http://localhost:8001 > I get a 404. not found. How can I find the right value? If Postorius works, It's good. `wget http://localhost:8001` returns a 404 as it should because this is a REST API and `/` is not a known endpoint. Something like `wget --user restadmin --password restpass http://localhost:8001/3.1/lists` should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: which mailman3 containers to use?

by jesper.holck＠ibsgaarden.dk

I tried to ask Claude what it will take to update Mailman 3 for Docker (https://github.com/maxking/docker-mailman/releases/tag/v0.5.2) to the newest versions of the included programs and libraries. Here is Claude's answer: ----------------------------------------------------------------- The short answer: much less than you might expect for Mailman itself, because there’s nothing newer to upgrade to. The real work is in the base OS and Django, and the Django part is blocked upstream. The Mailman suite is already current. v0.5.2 (October 2024) pins mailman 3.3.10, mailman-hyperkitty 1.2.1, mailmanclient 3.3.5, postorius 1.3.13, hyperkitty 1.3.12 and django-mailman3 1.3.15. I checked PyPI today and those are still the newest releases of every one of them. The only exception is the separate Postorius-only image, which still installs postorius 1.3.10; bumping that to 1.3.13 is a one-line change. Django is the real problem. Postorius, HyperKitty and django-mailman3 all require Django 4.2 or newer but below 5.1, and the web Dockerfile caps it further with Django<4.3. That leaves you on 4.2 LTS. Django 4.2’s security support ended in April 2026 and 5.0 is also end-of-life, so every Django version the suite accepts is now unsupported. You can’t fix this from the Docker side: forcing Django 5.2 LTS or 6.x past the pins means patching the three Django apps yourself and testing them. Until upstream Mailman ships releases that support newer Django, the practical choice is to stay on 4.2.x and keep the instance behind a reverse proxy. Alpine base images are the main thing that’s actually upgradeable. v0.5.2 uses Alpine 3.20. The repo’s main branch (last touched June 2026) has moved core and web to Alpine 3.23.4 and the Postorius image to 3.21.3, but that hasn’t been tagged as a release. Alpine 3.24 is also out, with point releases up to 3.24.2 carrying OpenSSL fixes. The catch is that each new Alpine brings a newer Python, which is what tends to break builds. For example, Mailman needs the nntplib backport on Python 3.13+, and some compiled packages fail on musl. Other things to change, all already on main: * uwsgi is pinned to 2.0.25 because newer builds don’t compile on aarch64. PyPI has 2.0.31; you can try it if you’re on x86-64 only. * SMTP_USE_TLS and SMTP_USE_SSL now parse correctly. In v0.5.2, any non-empty value, including "false", turned TLS on. * urls.py adds /mailman3/ and /archives/ URL aliases. * docker-compose gets a Postgres healthcheck, so the other services wait until the database is ready. * The bundled compose file still uses postgres:12-alpine, which is long out of support. Moving to a current Postgres means a dump and restore (or pg_upgrade), not just changing the tag. What it would take in practice: * Build from main, or cherry-pick the changes above onto v0.5.2. * Try Alpine 3.24 and fix whatever Python or musl build failures come up. * Stay on Django 4.2.x, or take on patching the Mailman Django apps yourself. * Upgrade Postgres separately, with a backup first. * Run tests/test.sh and smoke-test a list end to end: post, archive, moderation and login. Expect an afternoon for steps 1–2 and 4, plus testing. Step 3 is a real porting project unless upstream releases new versions first. Sources: * docker-mailman v0.5.2 and its main branch (I inspected the repo directly) * Alpine 3.24.1 released * Alpine 3.24.2 OpenSSL security updates

3 weeks, 1 day

REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Eric Vyncke

Postorius 1.3.6 does not work anymore when displaying the details of a list that I own (https://lists.XXX.org/mailman3/postorius/lists/rapcs-pilotes.listsXXXorg/) . It worked before but there was several upgrades in between (Ubuntu, apt packages, MySQL, Python). It displays the usual header/footer of the page but with "Something went wrong" above a red box with "HTTP Error 404:". /var/log/mailman3/mailman.log last entries are below (note the 404 result codes in the REST API): Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94 HTTP/1.1" 200 418 Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 Apr ... 127.0.0.1 - - "GET /3.1/addresses/eric(a)XXX.org HTTP/1.1" 200 379 Apr ... 127.0.0.1 - - "POST /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 /var/log/mailman3/web/mailman-web.log of course has an exception about this 404 result code. Using the MM3 shell, the preferred_address can be displayed and even modified. There are also good values in the MySQL database. Other API endpoints for users work fine (preferences, addresses, ...) Postorius system information is: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, Mar 13 2023, 10:26:41) [GCC 9.4.0] Running Ubuntu 20.04.4 LTS and Python 3.8 Thanks in advance for any hint to solve this issue (I have held messages that I would love to accept)

3 years, 7 months

Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (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 > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (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 > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Postorius List members

by Alain D D Williams

I have a test list with a few members. For each member it is showing me: Address, Delivery mode, Moderation action, bounce score. It is NOT showing Delivery status (Enabled, Disabled, Disabled by owner, ...). The only way of seeing this is by clicking on the email address (Subscription options). Is it possible to add delivery status to the summary where many users are shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of what is happening to users. Regards -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 11 months

Re: Reject with notification not working

by MegaBrutal

Stephen J. Turnbull <steve(a)turnbull.jp> ezt írta (időpont: 2026. márc. 26., Cs, 8:37): > MegaBrutal via Mailman-users writes: > > > I get different errors depending on whether I define > > the list:user:notice:rejected template. > > > > When the template is not defined: > > > > Mar 26 01:48:02 2026 (28606) Uncaught runner exception: 'ascii' codec > can't > > encode character '\xed' in position 21: ordinal not in range(128) > > The 21st byte of the stock version of the template is interpolated > from $listname. It appears to either be (Latin1) LOWERCASE LETTER I > WITH ACUTE or the leading byte of a 3-byte UTF-8 character (that > appears to be a private use block). > Hmm, probably I set "Hírlevél" for the list's title or something (it means "newsletter"). The 'ascii' codec for English is a legacy misfeature. We should be > able to use UTF-8 but this can have bad effects on some systems. You > can try to use UTF-8 instead by adding > > [language.en] > charset: utf-8 > Where do I set this? Just append to settings.py? > And this is what happens when I define the template: > > How did you define the template? In the file system, or via > Postorius? I'm guessing Postorius because of the "port=8000" and the > "/mailman3/api/..." path, but please confirm. > In Postorius. > Mar 26 01:35:55 2026 (28606) Uncaught runner exception: > > HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded > with > > url: /mailman3/api/templates/list/ > > hirlevel.lista.autistaktol.hu/list:user:notice:rejected (Caused by > > NewConnectionError('<urllib3.connection.HTTPConnection object at > > 0xf46e5910>: Failed to establish a new connection: [Errno 111] > Connection > > refused')) > > I don't understand this error. The ultimate reason that Mailman core > is looking for a template via HTTP at Postorius is that core and the > management UI may not be able to access a common file system. So > Postorius puts it somewhere, and provides a callback to core to access > it. On the Postorius side that is set in settings.py, like this: > > POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' > I don't have this variable defined, so it's probably using the default. I shall add it with 128.8.0.1:8000 then... But it didn't help! Restarted the mailman service, but it still wants to fetch the template from localhost. May it be hardcoded? See above. I didn't check thoroughly but I think that for modern > Mailman, every language except US English uses UTF-8. > To be fair, in the past I was trying to set my mailing lists to my native language, but then I found that many templates have no translation. In cases like this, most software just falls back to English, which would be fine for my use case. However, Mailman doesn't: I just noticed that empty automatic notifications are being sent out. > 2. I configured uwsgi to listen on 127.8.0.1:8000, practically > > because I didn't want to litter the main 127.0.0.1 address > > with a plethora of ports. > > I don't understand what you mean by "litter the address with a > plethora of ports". You need to use two separate ports, one for > mailman-web's Django (aka uwsgi in your case, usually 8000) and one > for Mailman core's REST API (usually 8001). That's all. Not sure why > that is a problem. > Yeah, it might not be a big deal, but 8000+ ports are often used for various local HTTP services, I may have another one running on 127.0.0.1:8000. Then true there are many ports being available, so I could just pick a different one, but using a dedicated localhost IP like 127.8.0.1 looked just nicer. I can immediately identify the listen ports belonging to Mailman; and I get to use the default port numbers appearing in the documentation. Alternate port numbers might have caused confusion later. So I just felt I got the best of both worlds with this method, and didn't expect these problems to come along. > Why does it ever want to use localhost:8000 for anything? > > See above about the arm's length relation between core and Postorius > in template handling. Undoubtedly somebody was incautious about > properly handling configuration, and that's the default buried in the > fallback configuration. > > File a bug (I need to run and pick up my wife at work). Cite this > email in it (get the URL from the Archived-At header). > Is this the official bug tracker on Launchpad? https://bugs.launchpad.net/mailman Would be quite convenient, as I used to file bugs for Ubuntu, so I already have an account there. Surprised that you use Ubuntu's tracker though. I know it's free to use, but I thought you tend towards BugZilla or something. Hope you succeeded to pick up your wife. My replies are also sporadic because at standard work hours I have a regular job that I must prioritize. > Grepping through the config files, I'm consistent about > > 127.8.0.1:8000, where does it get localhost (that is 127.0.0.1) > > from? > > You've outsmarted yourself. Try modifying or adding > > POSTORIUS_TEMPLATE_BASE_URL = 'http://127.8.0.1:8000' > > in /etc/mailman3/settings.py (or wherever your primary settings file > is). No promises about getting your templates, but that should at > least fix your "can't connect" problem. You may have to edit and save > the template to get the core side updated, though. Yeah, certainly outsmarted. :D Unfortunately it didn't work, as I told above.

7 months, 2 weeks

Mailman-users search results for query "Postorius"