Search results for "dO" - lists.mailman3.org

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Mark Sapiro

On 1/26/22 00:11, Stephan Krinetzki wrote: > > After we enabled the "slow query log", we got in the postgresql database the following output: > > 2022-01-25 12:49:41.538 CET [16126] LOG: unexpected EOF on client connection with an open transaction > 2022-01-25 15:34:36.047 CET [16864] LOG: duration: 30760.028 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 15:34:36.047 CET [3900] LOG: duration: 9372.471 ms statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX > 2022-01-25 16:42:07.243 CET [3900] LOG: unexpected EOF on client connection with an open transaction > > Pretty sounds like a database problem? The unexpected EOF is because the gunicorn worker timed out and was killed. There are two `DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX` transactions because the first one timed out. These came from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… The `accept` action is processed and ultimately we get to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.… and that in turn is doing the DELETE at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.… There must be some kind of database locking causing this, but I have no clue as to what it might be. If you haven't done so, I would stop all the mailman services and the database server and then start them again. I don't know if that would help, but it might. > sometimes the log (mailmansuite.log) show us this error That too is from the gunicorn worker timing out and being killed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 3 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/7/25 02:30, MegaBrutal via Mailman-users wrote: > On Mon, Apr 7, 2025, 03:04 Mark Sapiro <mark(a)msapiro.net> wrote: > >> so it is saying there is only one choice for sender which I think means >> there is only one address associated with your login. That still doesn't >> explain why it thinks you're not a list member. >> > > Indeed, it doesn't explain. Are there any maintenance scripts or DB queries > you recommend to run to get to see what's happening under the hood? Not offhand. What is the exact email address that you are logging on to the web UI with. Does it match exactly with the address of a list member or are there mixed-case differences? You might try an interaction like this: ``` mailman-web shell Python 3.12.8 (main, Dec 21 2024, 12:52:28) [GCC 9.4.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> from django_mailman3.lib.mailman import get_mailman_client >>> client = get_mailman_client() >>> list_id = 'test.example.com' # your actual list_id >>> rest_list = client.get_list(list_id) >>> email = 'user(a)example.com' # your actual email >>> member = rest_list.get_member(email) >>> member This should print something like <Member 'user(a)example.com' on 'test.example.com' with role 'member'> ``` This is exactly what HyperKitty is doing except in your case rest_list.get_member(email) is throwing a ValueError exception instead of returning the member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/22/20 1:22 AM, Torge Riedel wrote: > > I like to ask what to do with other packages when upgrading mailman. I > noted, that after upgrading mailman, all requirements are fulfilled, but > a lot updates are available: > > (venv) mailman@basis2:~/core$ pip3 list --outdated > Package Version Latest Type > ------------------- ------- ------ ----- > aiosmtpd 1.2 1.2.2 sdist > alembic 1.4.2 1.4.3 wheel > atpublic 1.0 2.1.1 sdist > dkimpy 1.0.4 1.0.5 sdist > dnspython 1.16.0 2.0.0 wheel > flufl.i18n 2.0.2 3.1.3 sdist > flufl.lock 3.2 5.0.3 sdist > idna 2.9 2.10 wheel > importlib-metadata 1.6.1 2.0.0 wheel > importlib-resources 2.0.1 3.3.0 wheel > passlib 1.7.2 1.7.4 wheel > PyMySQL 0.9.3 0.10.1 wheel > requests 2.23.0 2.25.0 wheel > SQLAlchemy 1.3.17 1.3.20 wheel > urllib3 1.25.9 1.26.2 wheel > zipp 3.1.0 3.4.0 wheel > zope.component 4.6.1 4.6.2 wheel > zope.event 4.4 4.5.0 wheel > zope.interface 5.1.0 5.2.0 wheel > > Should I update them (regularly) or may I break something in mailman? In some cases and at some times, Mailman itself specifies a version <= something for a dependency. There have been issues where an upgraded dependency is not compatible with current Mailman. You can look at the install_requires section of setup.py to see if there are any specific version requirements, but this is not fool proof. For example, flufl.lock 5.0 broke Mailman core (See https://gitlab.com/mailman/mailman/-/issues/754) This was fixed in core version 3.3.2. Thus, If Mailman is working with the set of installed dependencies that you have and all of them satisfy >= requirements in setup.py, it's probably safest to leave them as is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Ugnius

Hi. I have fixed my RO database issue. Thank You for help, Abhilash. It was 100% my stupid fault. I had issues with "django-admin". If I ran manage.py it works correct, if I run django-admin - it not: only basic commands. I did not find way how to give correct environment. Then I found on some notes, that manage.py does exactly the same what django-admin does. So I made work around : I had created /usr/local/bin/django-admin to my project file manage.py and it started to work. Later I installed mailman from 0 under another user, and I forgot about that sym link. So why because database was Read Only. It had simply leaking write privileges to database file. Understandable, because owner was another user... > On 6 Sep 2019, at 00:20, Abhilash Raj <maxking(a)asynchronous.in> wrote: > >> On Thu, Sep 5, 2019, at 1:49 PM, Ugnius wrote: >> >> Thank You. This is very valuable information. According documentation I understood that "runserver" should run on some internal port and uwsgi just works like proxy connects to the same as runserver port and serves content to apachi. Because when I was playing with the setup without "runserver" Web interface didn't work. >> Yes, I have stopped "runserver" and page still works fine. :) This didn't solve me database RO issue, but this information was important. Thank You. I am thinking what to do now... Maybe to recreate database (make initiation once again). It could take 2-3 hours. I did not noticed option to export/import lists setting. Or to try find solution how to make sqlite3 multiple >> writable. > > I think your problem about locked database might be solved. Like I mentioned, it is possible that those two running server could be stepping over each other toes. > > After removing the "runserver" process, I think you shouldn't fall into anymore of those locking issues. > > FWIW, it is also highly recommended to not use sqlite for any production use cases. Either postgres or mysql is preferred. > >> SQLite version 3.16.2 2017-01-06 16:32:41 >> Enter ".help" for usage hints. >> >> BR >> Ugnius >> >>> On 5 Sep 2019, at 23:31, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>> On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: >>>> >>>> I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? >>> >>> No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. >>> >>> The doc mentions that it is "development" server[1][2]. >>> >>> [1]: # Run the Django's "development" server at localhost:8000 >>> [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project >>> >>> Perhaps it should be more descriptive about what does it mean. >>> >>>> >>>>> On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>> >>>>> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >>>>> >>>>> You only need one of those, since they both do the exact same thing. Please remove >>>>> whatever is running the "python manage.py runserver" part and only use uwsgi. >>>>> >>>>>> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>>>>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>>>>> May mailman processes are next: >>>>>> >>>>>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>>>>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>>>>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>>>>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>>>>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>>>>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>>>>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>>>>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>>>>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>>>>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>>>>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>>>>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>>>>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>>>>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>>>>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>>>>> >>>>>> Looks like there are no double. Nothing more is running. >>>>>> >>>>>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>>>> >>>>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>>>> $ sudo pip3 install mailman >>>>>>> $ sudo pip3 install postorius >>>>>>> $ sudo pip3 install hyperkitty >>>>>>> $ sudo pip3 install mailman-hyperkitty >>>>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>>>> >>>>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>>> >>>>>>> >>>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>>> > Hi. All the project installation is under the same user / path and >>>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>>> > I have found work around - it is possible to change list as private in >>>>>>> > "admin" page. >>>>>>> > I started to get issues with runjobs after I have created couple of >>>>>>> > new lists with "no archive" option. >>>>>>> >>>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>>> >>>>>>> > >>>>>>> > If as owner user from project home I run: >>>>>>> > >>>>>>> > django-admin mailman_sync >>>>>>> > >>>>>>> > Traceback (most recent call last): >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>>> > line 84, in _execute >>>>>>> > return self.cursor.execute(sql, params) >>>>>>> > File >>>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>>> > line 383, in execute >>>>>>> > return Database.Cursor.execute(self, query, params) >>>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>>> > >>>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>>> > END TRACEBACK >>>>>>> > >>>>>>> > I did not find information how to fix this. It was worked without errors >>>>>>> > before. >>>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>>> > to work. >>>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>>> > again. >>>>>>> > I did not check other jobs, but I think what is related to database, >>>>>>> > will get errors. >>>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>>> > >>>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>>> > I have returned this database file back, postorius started to work >>>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>>> > only". >>>>>>> > Please help me how to fix this issue. >>>>>>> > _______________________________________________ >>>>>>> > 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) >>>>>> >>>>>> -- >>>>>> thanks, >>>>>> Abhilash Raj (maxking) >>>>>> >>>>>> >>>>> >>>>> -- >>>>> thanks, >>>>> Abhilash Raj (maxking) >>>>> >>>>> >>> >>> -- >>> thanks, >>> Abhilash Raj (maxking) >>> >>> > > -- > thanks, > Abhilash Raj (maxking) > >

6 years, 7 months

[MM3-users] Re: Mailman 3 localization

by Simon Hanna

> We would like to contribute further german translations, since there > are still some parts missing, e.g. in the postorious interface. Would > https://translations.launchpad.net/mailman/3.0/+pots/mailman/de/+translate > be the right place to do so, so that everybody could use our > translations? > > If there are other areas in which you could use our help, please let > us know. > > Regards, > Alex I wanted to set it up, but the requirement is to use a free hosted solution. (So transifex and crowdin are a no-go, they would be great to get translations, especially crowdin looks very active in that regard) I tried out zanata.org but it's extremely slow... The other option at the time was pootle (http://pootle.translatehouse.org) which doesn't offer hosting but some folks at gnu had a customized instance set up, but they discontinued the service. I searched for a translation service for a private project and found weblate.org . They offer hosting (hosted.weblate.org) for open source projects and it looks like a couple of people are using it. You need to contact them if you want to set it up for an open-source project though and I didn't want to invest in it without knowing what the end-result would be... Since I'm also mainly interested in German translations for my own installation, I opted to just use plain .po files and filed merge requests against the repositories. Postorius has translations (not perfect, but a start for the moderators that use my instance) included by now but my merge request for core is still outstanding https://gitlab.com/mailman/mailman/merge_requests/400/ Since I don't use Hyperkitty, I didn't translate that. cheers, Simon

7 years, 9 months

[MM3-users] New problem on new installation of Mailman

by Brian Carpenter

I am just about done with installing Mailman 3 on a new Debian 10 server and when I go to run ./mailman-post-update, I am running into the following error: ./mailman-post-update + '[' False == False ']' + mkdir -p /opt/mailman/mm/static + /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput --verbosity 0 Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/django-admin", line 10, in <module> sys.exit(execute_from_command_line()) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 401, in execute_from_command_line utility.execute() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 377, in execute django.setup() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/__init__.py", line 24, in setup apps.populate(settings.INSTALLED_APPS) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/registry.py", line 91, in populate app_config = AppConfig.create(entry) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/apps/config.py", line 90, in create module = import_module(entry) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/__init__.py", line 11, in <module> from haystack.utils import loading File "/opt/mailman/mm/venv/lib/python3.7/site-packages/haystack/utils/__init__.py", line 9, in <module> from django.utils import six ImportError: cannot import name 'six' from 'django.utils' (/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/__init__.py) I assume it has something to do with Haystack. Suggestions for a fix? Thanks, Brian

5 years, 10 months

[MM3-users] Fwd: Incoming command emails (i.e. listname-leave) routed to list itself

by Abhilash Raj

Hi Mark, Excerpts from Mark Lindsay's message of April 20, 2017 5:37 pm: <snip> Here are some baffling lines from /var/log/exim4/mainlog from the incoming > potato-leave(a)lists.mydomain.org email: > > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r DKIM: d=nervous-org.20150623. > gappssmtp.com s=20150623 c=relaxed/relaxed a=rsa-sha256 [verification > succeeded] > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r <= redacted(a)nervous.org H= > mail-qk0-f170.google.com [209.85.220.170] P=esmtp S=2466 id= > CABPy5zyQtJHXtCgrN37GHCUOjuo3J=DO_j0ZD03zm8gk+4shww(a)mail.gmail.com > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r => potato(a)lists.mydomain.org < > potato-leave(a)lists.mydomain.org> R=mailman3_router T=mailman3_transport > H=localhost [127.0.0.1] C="250 Ok" > 2017-04-21 00:25:03 1d1MNj-0007OQ-5r Completed > > Why does it say `potato(a)lists.mydomain.org <potato-leave(a)lists.mydomain.o > rg > >> `? >> > > I think this is actually an exim4 problem, so if the solution is to just > switch to postfix, then I will definitely do that. But I'm just asking in > case someone had a similar issue with exim4 and was able to work through > it. > > Yes, I had the exact same problem very recently and was able to fix it. The updated documentation[1] should fix your problem. The basic gist of the problem is that the exim configuration on the older documentation is missing a critical part. Exim4 by default strips off any prefixes/suffixes when delivering mail to the mailman, which causes mailman to post all the messages to mailing list instead of processing them as commands. `rcpt_include_affixes = true` Adding the above line to the transport fixes that problem. [1]: https://mailman.readthedocs.io/en/latest/src/mailman/docs/mt a.html#exim4-configuration thanks, Abhilash

9 years

[MM3-users] Re: Why is it so difficult to setup Mailman3?

by Peter Chubb

>>>>> "Thomas" == Thomas Ward via Mailman-users <mailman-users(a)mailman3.org> writes: Thomas> On 2026-04-08 10:28, alain williams wrote: >> On Wed, Apr 08, 2026 at 11:07:42PM +0900, Stephen J. Turnbull >> wrote: >> >>> To the best of my knowledge, the recommended installation >>> documents at >>> https://docs.mailman3.org/en/latest/install/virtualenv.html are >>> complete and straightforward for "typical" one-domain >>> installations. >> No they are not. I struggled, part of the reason is that I am not >> imbued in the python mindset and the documentation is written >> assuming that background. So I used the Debian package and a lot >> of work was needed on top of that. There are still problems: it is >> a resource hog and parts crash - generating large numbers of >> incomprehensible emails (I have talked about here, no real help). Thomas> The Debian package is inherently old and inefficient I'm using it with Nginx, Postgresql and exim4; on sid it's at Mailman3 3.3.10 with postorious 1.3.13; it has been stable for me since the upgrade before last (before that, there was a memory leak somewhere). I did find configuring it initially a pain; the way Django works was (still is) a mystery to me; plus a couple of the upgrades have been rocky and broken things (which I expect when working with the unstable distribution) The README in /usr/share/doc/mailman3/README.Debian was enough to get me going. And sudo -u list /usr/bin/mailman <args> gets you the CLI so you can do the things in the official docs. Peter C

3 weeks

[MM3-users] Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

On Thu, Sep 5, 2019, at 1:15 PM, Ugnius wrote: > > I do not know... In the setup example settings was something like process number = 2. But I understand at least 1 uwsgi and 1 run server should run? No, only uwsgi needs to run. It is fine if there are two of those, since it probably forks to have 2 worker process. There shouldn't be any "python manage.py runserver" processes running at all, it is meant only for testing purposes. The doc mentions that it is "development" server[1][2]. [1]: # Run the Django's "development" server at localhost:8000 [2]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-django-project Perhaps it should be more descriptive about what does it mean. > > On 5 Sep 2019, at 23:08, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >> >> This fishy, why do you have both uwsgi and "python manage.py runserver" running? >> >> You only need one of those, since they both do the exact same thing. Please remove >> whatever is running the "python manage.py runserver" part and only use uwsgi. >> >> On Thu, Sep 5, 2019, at 1:02 PM, Ugnius S wrote: >>> Thank You, Abhilash, to helping. I have checked the processes, but also I have read, that sqlite3 can run in multi writing mode. >>> May mailman processes are next: >>> >>> 6644 ? S 0:12 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6645 ? S 0:00 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6653 ? Sl 636:28 /usr/bin/python3 /opt/home/manage.py runserver 0:8015 >>> 6656 ? Sl 0:27 /usr/bin/uwsgi --master --ini /opt/home/uwsgi.ini >>> 6643 ? S 0:00 /usr/bin/python3 /usr/bin/master -C /opt/home/mailman.cfg >>> 659 ? S 0:46 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=in:0:1 >>> 6660 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=nntp:0:1 >>> 6661 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=digest:0:1 >>> 6662 ? S 0:48 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=pipeline:0:1 >>> 6663 ? S 0:44 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=archive:0:1 >>> 6664 ? S 0:41 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=command:0:1 >>> 6665 ? S 0:01 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=retry:0:1 >>> 6666 ? S 0:45 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=virgin:0:1 >>> 6667 ? Sl 0:16 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=lmtp:0:1 >>> 6668 ? Sl 1:30 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=rest:0:1 >>> 6669 ? S 0:42 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=bounces:0:1 >>> 6670 ? S 0:49 /usr/bin/python3 /usr/bin/runner -C /opt/home/mailman.cfg --runner=out:0:1 >>> >>> Looks like there are no double. Nothing more is running. >>> >>> 2019-09-05, kt, 03:16 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>> __ >>>> On Wed, Sep 4, 2019, at 2:05 PM, Ugnius S wrote: >>>>> >>>>> I have installed using documentation. My linux distribution version has no full package available. I have installed step by step: >>>>> $ sudo pip3 install mailman >>>>> $ sudo pip3 install postorius >>>>> $ sudo pip3 install hyperkitty >>>>> $ sudo pip3 install mailman-hyperkitty >>>>> And of course all mandatory components... Everything without errors, I can drop db files and I can download mailman-suite again and start from empty page again. But it will not guarantee that DB will not become READ ONLY again. Here should be logic. No developing support here? >>>> >>>> Could you be running two separate processes such that the database is locked by one and so other finds it as READ Only? When you find a read only database, can you check if it is open in some other process? >>>> >>>>> >>>>> >>>>> >>>>> 2019-09-03, an, 19:36 Abhilash Raj <maxking(a)asynchronous.in> rašė: >>>>>> >>>>>> >>>>>> On Sun, Sep 1, 2019, at 3:22 AM,ugniusviln(a)gmail.com wrote: >>>>>> > Hi. All the project installation is under the same user / path and >>>>>> > it works. Archiving working as well, (just one remark: no matter what >>>>>> > to set in postorius, hyperkitty shows list as public) >>>>>> > I have found work around - it is possible to change list as private in >>>>>> > "admin" page. >>>>>> > I started to get issues with runjobs after I have created couple of >>>>>> > new lists with "no archive" option. >>>>>> >>>>>> How did you install all these components. It seems there the installation is broken in weird ways. >>>>>> >>>>>> > >>>>>> > If as owner user from project home I run: >>>>>> > >>>>>> > django-admin mailman_sync >>>>>> > >>>>>> > Traceback (most recent call last): >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/utils.py", >>>>>> > line 84, in _execute >>>>>> > return self.cursor.execute(sql, params) >>>>>> > File >>>>>> > "/home/user/.local/lib/python3.5/site-packages/django/db/backends/sqlite3/base.py", >>>>>> > line 383, in execute >>>>>> > return Database.Cursor.execute(self, query, params) >>>>>> > sqlite3.OperationalError: attempt to write a readonly database >>>>>> > >>>>>> > "django-admin runjob sync_mailman " - makes read only errors as well. >>>>>> > "django-admin runjob new_lists_from_mailman" >>>>>> > django.db.utils.OperationalError: attempt to write a readonly database >>>>>> > END TRACEBACK >>>>>> > >>>>>> > I did not find information how to fix this. It was worked without errors >>>>>> > before. >>>>>> > I noticed, that if I stop mailman, "django-admin mailman_sync" starts >>>>>> > to work. >>>>>> > If I start "mailman start", then "django-admin mailman_sync" failing >>>>>> > again. >>>>>> > I did not check other jobs, but I think what is related to database, >>>>>> > will get errors. >>>>>> > Seems mailman locking the database. It is not a file permissions issue. >>>>>> > Mailman db location is: /project_directory/var/data/mailman.db >>>>>> > >>>>>> > if to rename /project_directory/var/data/mailman.db to something, >>>>>> > mailman creates database file size 0, django-admin runjobs start >>>>>> > working, but of course postorius stops working. I did it for testing. >>>>>> > I have returned this database file back, postorius started to work >>>>>> > again, but django-admin runjobs does not work, error: "database read >>>>>> > only". >>>>>> > Please help me how to fix this issue. >>>>>> > _______________________________________________ >>>>>> > 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) >>>> >>>> -- >>>> thanks, >>>> Abhilash Raj (maxking) >>>> >>>> >> >> -- >> thanks, >> Abhilash Raj (maxking) >> >> -- thanks, Abhilash Raj (maxking)

6 years, 7 months

[MM3-users] Re: Adding members to a mailman3 mailing list

by Mark Sapiro

On 10/15/20 2:07 AM, Onyeibo Oku wrote: > > In the meantime, I moved to option #3 (recommended for production). > I hit a grey area when setting up the virtual environment. At > https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst…, > I see: > > $ cd /opt/mailman > $ python3 -m venv venv > > The documentation imply that a 'user' creates the virtual environment > but is not explicit about that 'user'. The user can be any user you want. I use `mailman` on my production installations and `mark` on my development installation. The key is that user should be set as owner of /opt/mailman and then creating the venv and subsequent steps are all done as that user. > (1) Is it better to have a dedicated user (say 'mailman') then use that > while following the docs? I see a lot of docs referring to a 'mailman' > user. Installing mailman3 from distribution repository introduced a > 'mailman' user to my box (with special UID). There has to be reasons > for that. Yes, a dedicated Mailman user is best. > (2) Should the setup proceed with 'root'? (why do I get the feeling > that this is not the design?) No. setup should proceed as the Mailman user. > (3) How about using an already existing local user? What are the > implications? That's OK, but there are potential security implications due to the fact that the Mailman processes running as that user have access to all that user's non-mailman stuff. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: Upgrading packages

by Mark Sapiro

On 10/13/22 03:49, Eggert Ehmke wrote: > > pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master > > I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. > > All packages were upgraded fine. I applied the patch to > venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py It shouldn't have been necessary to apply any patch. The head of the GitLab hyperkitty master branch is already compatible with mistune 2.0.4 > to change the mistune import line. When I run now > mailman-web migrate > I get: > *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration > graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* > *To fix them run 'python manage.py makemigrations --merge'* > > However, when I run the suggested command as: > $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- > merge > No conflicts detected to merge. There's something strange here. If you look at the migrations at the head of the gitlab branch at https://gitlab.com/mailman/postorius/-/tree/master/src/postorius/migrations, you'll see that migration 17 is named 0017_alter_emailtemplate_language.py, not 0017_auto_20220628_1132. I suggest comparing the content of your postorius/migrations/ directory with the GitLab head and resolving any differences. > Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my > production system. Would be nice to shed some light on this. I'm guessing at some point you installed something which required you to manually make this migration and that produced this conflict. Do you have both 0017_alter_emailtemplate_language.py and 0017_auto_20220628_1132 in your postorius/migrations/ directory? If so, probably just removing 0017_auto_20220628_1132 will fix this? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 6 months

[MM3-users] Time Stand Still

by Barry Warsaw

Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation. I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps. I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken. Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org. It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals. My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced. And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader. If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient. This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate. Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention. -Barry https://www.wefearchange.org/

8 years, 5 months

[MM3-users] Re: Request for help with configuring "from" headers in mailman3 list

by Stephen Daniel

That worked! I apologize for needing to ask for help on this. I am very appreciative of how quickly and accurately my issues were resolved. On Thu, Jan 6, 2022 at 5:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/6/22 12:52 PM, Stephen Daniel wrote: > > > > Sendgrid requires that the "From:" address on any email reference an > > authenticated domain. > > > > In the old mailman2 implementation, emails sent by mailman are listed as > > > > From: <human name via LISTNAME> LISTNAME(a)LISTDOMAIN.org > > > > Reply-to: <human name> sender(a)senderdomain.com (the original email's > sender) > > > > Sendgrid would be happy with this, because LISTDOMAIN.org is a > > validated domain. > > > > However, in my mailman3 implementation, the From: header lists the > original > > email's sender. Sendgrid rejects this because the original email's > > sender's address is not one of the validated domains. > > > > How do I configure mailman3 to generate headers in the same style as the > > old mailman2 implementation? > > > In the list's Settings -> DMARC mitigations, set DMARC mitigation action > to Rrplace From: with list address and DMARC Mitigate unconditionally to > Yes. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

4 years, 3 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Mark Sapiro

On 12/6/23 11:00, Jered Floyd wrote: > > These errors are generated to me as the admin, and in the elided environment section SITE_ID is indeed 0, but I'm at a loss to imagine why this happens only sometimes! For me, on a test installation with SITE_ID = 0, this only occurs at https://example.com/accounts/social/connections/ Other URLs such as https://example.com/accounts/password/change/ and https://example.com/accounts/email/ do not throw this exception. Here's the code: ``` def get_current(self, request=None): """ Return the current Site based on the SITE_ID in the project's settings. If SITE_ID isn't defined, return the site with domain matching request.get_host(). The ``Site`` object is cached the first time it's retrieved from the database. """ from django.conf import settings if getattr(settings, "SITE_ID", ""): site_id = settings.SITE_ID return self._get_site_by_id(site_id) elif request: return self._get_site_by_request(request) raise ImproperlyConfigured( 'You\'re using the Django "sites framework" without having ' "set the SITE_ID setting. Create a site in your database and " "set the SITE_ID setting or pass a request to " "Site.objects.get_current() to fix this error." ) ``` I tried patching it from ``` if getattr(settings, "SITE_ID", ""): ``` to ``` if getattr(settings, "SITE_ID", None) is not None: ``` but that's even worse. It throws a bunch of "django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist." errors. Somehow, get_current is being called without a request object in the cases where it fails. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/28 15:42, Roland Giesler via Mailman-users wrote: > > On 2024/07/28 15:26, Roland Giesler via Mailman-users wrote: >> On 2024/07/28 00:39, Mark Sapiro wrote: >>> On 7/27/24 15:16, Roland Giesler via Mailman-users wrote: >>>> >>>> The server runs power-mailinabox, which uses Postfix indeed. All my >>>> mail, and quite a few others' mail is sent from the using SMTP-Auth >>>> on port 465. Actually, this message is sent via that server too. >>>> So it's clear to me that MM3 is not authenticating for some reason. >>> >>> What do you see in Mailman's smtp.log and in the mail.log on the >>> mail server? >> >> The smtp log is in syslog... > > I also see this in /var/log/mailman3/web/mailman-web.log The /etc/mailman3/mailman3-web.py file contains inter alia these lines: # Set default domain for email addresses. EMAILNAME = 'fast.za.net' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius@{}'.format(EMAILNAME) # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root@{}'.format(EMAILNAME) fast.za.net was giesler.za.net before, so I changed it.

1 year, 9 months

[MM3-users] Mailman 3 install questions: HAYSTACK_CONNECTIONS

by heller＠deepsoft.com

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 year, 9 months

[MM3-users] Re: Migrating from SQLite to PostgreSQL

by Stephen J. Turnbull

Sebastian Hagedorn writes: > I have only now started playing around with Mailman 3.2, because I never > managed to get the earlier releases to work, and reading through the > documentation I thought that such situations could be handled with Alembic, > as described here under "Database Migrations": > > <http://mailman.readthedocs.io/en/latest/src/mailman/docs/database.html> > > Is that not the case, and if not, in what cases can or should it be used? No. What is being discussed in the thread is changing the backend RDBMS, behind the SQL schema. Alembic operates in front of the SQL schema, managing the relationship between Python objects and the SQL schema. As the "Migration" section states, Alembic is used to handle changes in the model (ie, the Python objects), so that they are reflected in the SQL used to access the backend. Users don't need to use it unless they customize the Python objects (ie, patch Mailman themselves). If *we* change the model between versions, Alembic will automatically be invoked to update the SQL, but the user doesn't need to do anything about it. The potential issues Mark refers to involve differences in the way the different backend implementations handle SQL (this includes issues like default encodings for strings). These should be few because all the supported backends support standard SQL, but we can't guarantee there will be none. Differences in implementation also mean that you can't use the more efficient and compact dump formats that most implementations provide, because they are implementation- dependent. You need to use the textual format that is actually SQL programs that individually create each table, insert each record, create any needed indices, and so on.

7 years, 9 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

On 5/24/20 7:20 PM, Alan So wrote: > Really thanks for your hard work Mark! It is a bit strange that parseaddr behave differently with CRLF and LF. Maybe if the server is a Windows, the behavior is consistent. It might be that on Windows, `mailman inject` would create the message with CRLF line endings. > May I know when or whether will this patch be committed to the repository so that it will be effective in future release of Mailman? Thanks. In the absence of an issue at <https://gitlab.com/mailman/mailman/-/issues>, probably never. <hint> The bottom line is the original mail created by Outlook is defective.[1] While Mailman could defend against this defect, starting to do that opens the possibility that there are other areas of the code that need a similar defense. Have you asked Microsoft to fix Outlook to not create these defective messages? That's the real solution. That said, if an issue is filed, someone might consider adding something along the lines of <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> to the code base. [1] given an address of the form display-name (comment) <addr-spec> in a header, it can be folded either between the display-name and the (comment) or between the (comment) and the <addr-spec>, but if display-name (comment) is quoted as in "display-name (comment)" <addr-spec> "display-name (comment)" is now a phrase within which folding is not allowed and this can only be folded between the "display-name (comment)" and the <addr-spec>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Mailman Core 3.3.2 is now out

by Mark Sapiro

On 11/24/20 7:22 PM, Abhilash Raj wrote: > > I think I should keep in mind next time to use the #<heading-name> like `#3.3.2` pointed out by Torge, instead of `#id` (which is what I see when I hover over the Link in browser so I copied ;). It's more complicated than that. Sometimes the fragment name is the heading and sometimes it is `#idn`. At the moment, neither #3.3.2 nor #3.3.3 work at all as these are #id2 and #id1 respectively. Currently the fragment for 3.3.3 Bugs is #bugs and the fragment for 3.3.2 Bugs is #id3, but presumably prior to the addition of 3.3.3, #bugs was Bugs under 3.3.2, Just as now, #command-line is Command line under 3.3.2, but when a Command line section is added under 3.3.3, that will probably get the command-line id. Thus, the note "Permalink to this headline" es misleading at best because it isn't very permanent fo an evolving document. > You can specify explicit anchor name in .rst too, I think just adding a `.. _news-3.3.2` just above the heading will generate an anchor on the page with #news-3.3.2 (I haven't verified this but I think it will!) which links to the heading. I too think this is correct. I suppose it might be worth doing for NEWS.rst in particular since Sphinx doesn't seem to like fragments like n.n.n. Another way to deal with this would be to always use code names. It seems like a heading `n.n.n` will always get a `#idn` id, but, e.g. `3.3.0 – “Tom Sawyer”` gets `#tom-sawyer` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

[MM3-users] Re: what process creates webui tables (mailmanweb db)?

by Mark Sapiro

On 9/26/22 09:14, tflatley(a)gmail.com wrote: > hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate Probably not. First of all, `mailman-web migrate` will only affect the mailmanweb database, not the mailman database, migrations for which are run implicitly when Mailman core is started. Also, migrations will only affect tables for which there are migrations, not all tables. > this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file > > python3 manage.py migrate Yes. > Operations to perform: > Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount > Running migrations: > No migrations to apply. > Your models have changes that are not yet reflected in a migration, and so won't be applied. > Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. The above message saying you need to make migrations because of changes to models indicates that your Debian/Ubuntu package is broken as the packager should have created all necessary migrations. > i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? I am confused as to why you are trying to run an out of date and possibly broken Debian/Ubuntu package when it appears you have successfully installed the latest PyPI packages in a venv. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Out there plugin idea for tech cost sponsorship

by Steven Clift EDem

After spending 20 years running a non-profit that hosted email lists for local communities as my day job, that's now all volunteer as I run a startup. Figuring out how to raise money to cover server costs without selling out our members with targeted social media advertising, was a continuous challenge. Anyway, today I am still involved in efforts to route around digital ad behemoths, but I a trying to help small businesses and shop for good brands gain new customers. So here is the question - do you think a Mailman add-on/plugin/module/whatever you'd call it that allowed list admins to reward their new subscribers to email lists with custom themed "for good" discounts would be of interest to many??? Normally, we (GoodCarts) reward people post-checkout with discounts in reciprocity powered circles of online stores. Stores essentially grow together by sharing customers instead of bidding against each other. The way I could see working with email list providers is basically adding an affiliate marketing style commission where purchases with post-subscription rewards would go to the partner based on results. When we go from hundreds of brand members to thousands and add in a "buy local" or brands by theme/values/impact, in theory my non-profits local online community forums could mission align by offering discounts to locally owned businesses. Our view is that exclusive discounts as rewards post transaction (purchase, email list subscription, volunteer sign-up, event registration, online petition signature, etc.) is far better than plastering ads everywhere. Anyway, I'd be curious if you think idea might have legs with Mailman list hosts/admins??? Nothing urgent, just a Saturday morning think different idea. Steven Clift

3 years, 3 months

[MM3-users] Re: Held messages not delivered after approval

by Stephen J. Turnbull

Krinetzki, Stephan writes: > Now in the mailman.log I see the HOLD messages and the approved > messages. The smtp.log logs just the incoming Mail, which seems to > be fine. By that you mean the incoming mail is fine? Or smtp.log is fine? smtp.log should include two (or more) lines for each successful post, like Jan 02 16:09:17 2025 (42985) <43007@turnbull> smtp to list-1(a)turnbull.jp for 1 recips, completed in 0.6027507781982422 seconds Jan 02 16:09:17 2025 (42985) <43007@turnbull> post to list-1(a)turnbull.jp from list-1-owner(a)turnbull.jp, 992 bytes, 1 failures Jan 02 16:09:17 2025 (42985) <43007@turnbull> delivery to list-1-owner(a)turnbull.jp failed with code 550, b'5.1.1 <list-1-owner(a)turnbull.jp>: Recipient address rejected: User unknown in local recipient table' (That last line shows an example of a failure report.) > Aug 05 10:21:05 2025 (217986) Cannot connect to SMTP server localhost on port 25 Postfix for some reason doesn't know about the alias "localhost" (it has something to do with trusting the DNS and not reading the /etc/hosts file). 127.0.0.1 works. I don't understand how any lists' posts get delivered at all with that. If it's postfix it's possible that the connection pool is exhausted intermittently (but that wouldn't explain why it's consistently impossible to post to a subset of lists). You can specify that connections from the loopback interfaces are less restricted. That might help. > Even after changing the smtp_host in mailman.cfg this error appears > randomly. Note that > Sadly the mail does not get delivered. :-( -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 3 weeks

[MM3-users] Re: Reg Archive Inactive Status

by Nirmal J

Yes I have it. I am also sharing that also settings_local.py -----Original Message----- From: Stephen <steve(a)turnbull.jp> To: Nirmal <nirmal(a)iitm.ac.in> Cc: mailman-users <mailman-users(a)mailman3.org> Date: Friday, 26 September 2025 3:09 PM IST Subject: [MM3-users] Re: Reg Archive Inactive Status Nirmal J via Mailman-users writes: > Hereby I am sharing the full settings.py file. Are you sure this is the settings.py being used by your installation? It appears to be the distribution file, unchanged. > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')# Application definition If this is from the installed settings.py, it isn't going to work, since you specified a routable domain (I think, although "list1.iitm.ac.in" is not in the public DNS), which will have a routable address, not localhost. What IP does your DNS report for "list1.iitm.ac.in"? > HOSTNAME = 'localhost.local' That isn't what you told Mailman via hyperkitty.cfg. I'm not sure it matters, but I think you should make sure all the config files agree on the name of the host. > # If you enable email reporting for error messages, this is where those emails > # will appear to be coming from. Make sure you set a valid domain name, > # otherwise the emails may get rejected. > # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL > # SERVER_EMAIL = 'root(a)your-domain.org' > SERVER_EMAIL = 'root@{}'.format(HOSTNAME) This can be problematic, at least if you enable error messages by email. > try: > from settings_local import * > except ImportError: > pass Do you have a "settings_local.py" file? -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months

[MM3-users] Re: Creating users via RestAPI / User-Management - a bunch of questions

by Mark Sapiro

On 6/20/25 06:39, Christian Schneider wrote: > Dear Mark and companions, > > somehow I can not cope with the user management... > (I am running a venv-installation, latest stable versions) > > I read this manual: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > and played with the RestAPI calls... > > I know about the fine grained differences between user and member, admin/owner, superuser... > and about the two user databases in PostgreSQL and Django-Framework. I'm not sure what distinction you are making between PostgreSQL and Django-Framework. There are two separate and distinct users, Django users and Mailman core users. Information about both is in the PostgreSQL database. Django users are in the `auth_user` table and Mailman core users are in the `user` table, both in the public schema, although if you split the data into a `mailman` database and a `mailmanweb` database the `auth_user` table is in `mailmanweb` and the `user` table is in `mailman`. > What I stumble upon is the RestAPI calls to create a "working" user (with the ability to login via WebUI). > When I follow the manual (from the url above) I create a user (including password) that appears in the PostgreSQL database. > (And this user is visible on the User-URL (https://example.com/mailman3/users)) > Even when I (via WebUI) set the user as "approved" this user is not able to log in... > I assume this restriction is in accordance to the fact that there is not equivalent Django user. > (There was a mail in the archive of the MM3 user group...stating that one has to use the Django RestAPI to create the appropriate user) The above is correct. The Mailman REST API only deals with Mailman core. Mailman core knows nothing about Django. > When I create the user using the WebUI (https://example.com/accounts/signup/?next=/mailman3/lists/) > the new user is created in the right (complete) way...appearing in the PostgreSQL database and as a user in Django. > How is this sync between the two databases realized? I'm still looking into that, but it isn't the creation of the Django user per se that creates the Mailman user. The process has multiple steps. 1) Sign-up for an account. This creates the Django user and sends an address confirmation email. 2) Click the link in the confirmation email. This takes you to a page with a `Confirm` button to confirm the email address. 3) Click the confirm button. It is not until step 3) that the Mailman user and address records are created. > (The Django user also has the correct status (no staff status / no superuser status / just active status) how is this realized?) Presumably by the sign-up process not setting staff status and superuser status. > As I am not very familiar with python programming (I know Perl/Java/C++ and have an (maybe outdated) concept of OOP), > is there a quick way to implement this kind of sync by copying the register logic from mailman's python action script for registering? I think it must be django-mailman3 that's doing this, but I haven't been able to see how so far. django-mailman3 does override the template for the /accounts/confirm-email page, but this is only to include styling. > Other questions: > Will there be a create_admin_user-script that is callable via CLI (like createsuperuser or create_list)? > (This script ought create a user in PostgreSQL and as Django user) No plans. There are `mailman addmembers` and `mailman admins` commands to add members or admins to a list. Adding an owner or moderator to a list via `mailman admins` will also create a Mailman user for that person if there isn't one already, but it won't create a Django user. > How will a social account provider (like oidc) linkage (in Django) fit in this concept? > Will oidc-accounts be copied to the Django's user database (or PostgreSQL db) or is it an on-the-fly check against the oidc-provider? (I assume second option) > What are the status-flags (staff status/superuser status/active status) of the linked oidc-accounts? (Can I specify the status flags?) I don't offhand know the answers to that, but I think logging in via a social account provider creates a Django user.. > A conceptual thought: > When "user1" (with email user1(a)example.com) is known to django via oidc linkage > and I create "user1" (also with email user1(a)example.com) via RestAPI calls > (following the url https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) > do I have a "complete" user then? > I mean a user who is able to login and who can be assigned to a list as admin (e.g.) > (In this case I would not have to care about the Django user database... ;-)) If the user can log in to the web UI with an associated email address, if that address is an admin of a list, the logged in user can admin the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 1 week

[MM3-users] Re: mass subscribers disablement!?

by Christian Stalberg

After the first time where users were unsubscribed automatically, I added back one at a time all the subscribers who were unsubscribed. Now they have all been unsubscribed again automatically. They are valid working email addresses. How can I stop this behavior from occurring please? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, October 26, 2021 11:03 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: mass subscribers disablement!? On 10/26/21 5:14 AM, Christian Stalberg via Mailman-users wrote: > Yes I upgraded to a version >=3.3.1 and had 70 subscribers disabled. > Is there a way to see via the web GUI which subscribers were disabled? > Correspondingly, can I re-enable delivery for them via the web GUI? Only one at a time. You could modify the shell session I posted previously to just display the members. ``` $ bin/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. >>> lm = getUtility(IListManager) >>> for mlist in lm.mailing_lists: ... for member in mlist.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print('Delivery disabled by bounce for member {} on list {}' ... .format(member.address.email, mlist.list_name)) ... <print output here> >>> exit() ``` Alternatively you can script some mailman commands as in ``` #!/bin/bash for list in `bin/mailman lists|sed '1d'`; do echo $list bin/mailman members --nomail bybounces $list done ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/

4 years, 5 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 7 Nov 2021, at 10:54 am, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: I wound up taking a different approach. I check for other references to the message in the message store and only delete the message if there are none. The fix is at https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs<https://gitlab.com/mailman/mailman/-/merge_requests/932/diffs> Oh nice. That seems like a sensible solution. Thanks for tackling so quickly. I’ll do some testing today and roll it out once testing is complete. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 5 months

[MM3-users] Re: Healthchecks and Django

by Philip Colmer

On Tue, 4 Jan 2022 at 09:36, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: > Philip Colmer writes: > > > For the MM3 servers, we're probing "/mailman3/lists/". > > You could create a path in urls.py called "250" that does nothing but > respond with a 250 status (and maybe a hello-world page). The issue > with /mailman3/lists/ is that it queries core for the lists (which, if > successful, proves that core is up as a side effect). > > > Is there another URL we could use to check the health of a MM3 server > > What does this mean to you? Our Mailman 3 suite consists of three > applications, core, Postorius, and HyperKitty, which might or might > not be installed, and if installed might or might not be running on > the same host. Core in turn depends on the MTA and starts a bunch of > qrunners. Any of the above might fall over on its own. (I don't > think there's any way to check on the health of a particular qrunner > from the net, though.) > That's a very good point. It would be nice if, at some point, an actual healthcheck endpoint could be included that returned some information about the state of the different applications as a JSON blob. It is increasingly useful to try and spot application problems before users do :) > > > Or, if not, is there a way of stopping Django from sending out the > > emails? > > There probably is, but I don't know it. Mark might, but if not asking > on a Django list would be a better place. > > Thank you. Regards Philip

4 years, 3 months

[MM3-users] Re: Dealing with recipients' servers spam filtering

by Gilles Filippini

Brian Carpenter a écrit le 12/02/2021 à 17:33 : > On 2/12/21 10:59 AM, Gilles Filippini wrote: >> It says: host mx1.free.fr[212.27.48.7] said: 550 spam detected >> (in reply to end of DATA command) I don't have any SPF record setup. >> DMARC mitigation is configured to 'Replace From: with list address' >> and 'DMARC mitigate unconditionally' set to 'No'. > > Well make sure you set up SPF records for your list domains. They do > help in mail delivery. I personally set DMARC mitigate unconditionally > to yes for my lists. Unfortunately the 550 spam detected message is too > generalized to be helpful. If you have more informative information from > your logs then please share them. Writing down what I've learned so far, in case it may help others: 1- The lists server DNS record (lists.example.com) should be of 'A' type (no 'ALIAS' or 'CNAME') 2- The SPF record should be set for the very same DNS name; e.g. lists.example.com (not just example.com) 3- This record seems to work for my server: lists.example.com. IN TXT "v=spf1 ip4:123.123.123.123 -all" Where the IP address is the same as the one registered for the 'A' record. How to check the SPF record: 1- Create a dummy mailing list and register your email address and check-auth(a)verifier.port25.com. 2- Send an email to this list. You should receive a report from auth-results(a)verifier.port25.com Here is what I've received for my server: ========================================================== Summary of Results ========================================================== SPF check: pass "iprev" check: pass DKIM check: none Let's see it this is enough to mitigate the problem with Hotmail addresses. Best, _g.

5 years, 2 months

[MM3-users] Re: Current status and issue deleting Archives in Mailman3

by Abhilash Raj

> On Nov 2, 2021, at 12:51 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/2/21 11:50 AM, bob B wrote: >> So I am teaching myself to fish, and see that it is actually django-admin, so that is in >> mailman-web? (in docker) >> But i get this: >> $ docker exec -it mailman-web /bin/bash >> bash-5.0# django-admin shell >> Python 3.8.10 (default, May 6 2021, 06:30:44) >> [GCC 9.3.0] on linux >> Type "help", "copyright", "credits" or "license" for more information. >> (InteractiveConsole) >>>>> from hyperkitty.models import MailingList >> Traceback (most recent call last): > ... >> raise ImproperlyConfigured( >> django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. > > > Do what it says. I.e. run > > DJANGO_SETTINGS_MODULE=path/to/settings; django-admin shell DJANGO_SETTINGS_MODULE expects a Python import path, instead of a filesystem path. The docker has documentation on running management commands, which in this case is “shell” [1] $ docker exec -it mailman-web python3 manage.py shell [1]: https://asynchronous.in/docker-mailman/web/#django-management-commands I know there are plethora of ways to run Django management commands, but this is the easiest one for docker. django-admin will work too, but you have to be in the right working directory for the import path to work and it get weird. I’ve always disliked how Django management commands work unfortunately and in trying to “fix” that with “mailman-web” (which isn’t adopted by container images), i feel I might have re-invented a third option. -- thanks, Abhilash Raj (maxking)

4 years, 5 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/29/20 12:15 AM, Odhiambo Washington wrote: > > Yes, the same problem. > I created the file __init__.py in /opt/mailman/mm > However, when I run using the wsgi.py I ended up (still do!) with the error: > > [Wed Jul 29 10:08:51.869144 2020] [wsgi:info] [pid 79132] [remote > 197.232.81.246:64709] mod_wsgi (pid=79132, process='mailman-web', > application='mm3-lists.server.name|/mm3'): Loading Python script file > '/opt/mailman/mm/wsgi.py'. What is the contend of the file /opt/mailman/mm/wsgi.py? You previously posted the setting of WSGIDaemonProcess in your Apache config as: > WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 user=mailman3 \ > group=mailman3 python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 \ > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var Is it still that? ... > 197.232.81.246:64709] mod_wsgi (pid=79132): Exception occurred processing > WSGI script '/opt/mailman/mm/wsgi.py'. > [Wed Jul 29 10:08:51.872754 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] Traceback (most recent call last): > [Wed Jul 29 10:08:51.872827 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File "/opt/mailman/mm/wsgi.py", line 38, in <module> > [Wed Jul 29 10:08:51.872835 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] application = get_wsgi_application() > [Wed Jul 29 10:08:51.872847 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/wsgi.py", > line 12, in get_wsgi_application ... > [Wed Jul 29 10:08:51.872984 2020] [wsgi:error] [pid 79132] [remote > 197.232.81.246:64709] ModuleNotFoundError: No module named 'settings' > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: changing adverstised status

by Mark Stuart

I can confirm the issue is happening to me as well postorius 1.2.1 / Django 2.0.7. If you're logged in and go to the list setting page, check the radio button for 'Show list on index page' to 'No' and click save at the bottom, it reverts back to 'Yes'. Then it still shows up on the index page. I haven't tried the mmclient method to see if that works. -- Mark (stuieordie) On Wed, Aug 22, 2018 at 1:30 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change "show > > list on index page" via the settings, but the value isn't saved. Is > > there a way to set advertised = False to a specific list via the shell? > > Could be related to > https://gitlab.com/mailman/postorius/merge_requests/352 > > The behavior of some of our boolean fields changed with newer releases of > Django, but it has been fixed in master branch. > > > > > Thanks & Regards, > > Alex > > > > (Kulturserver editorial staff) > > _______________________________________________ > > 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) > _______________________________________________ > 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/ >

7 years, 8 months

[MM3-users] Re: Weekend releases

by Abhilash Raj

On Tue, Dec 10, 2019, at 8:27 AM, Mark Sapiro wrote: > On 12/10/19 2:58 AM, Paul Arenson wrote: > > Thank you. The setup I am using now has Hyperkitty 1.3.0 and I just wanted to confirm. Somewhere I thought I read there is a facility in the Hyperkitty archive interface to format text. Probably I misunderstood, but if there is such a facility, I am not seeing it. Maybe I am looking for something like Tiny Ice and thus can't find it. > > > Markdown rendering of message bodies in Hyperkitty is > <https://gitlab.com/mailman/hyperkitty/merge_requests/160>. This is > installed on <https://lists.mailman3.org/mailman3/> and > <https://mail.python.org/mailman3> but is not yet released. > To add more, if you look at the merge request, there are some pieces missing before it can be merged. Especially, a mechanism to opt-out on a per-list basis from this. While markdown is pretty nice to look at when you are dealing with certain mailing lists which communicates in plain text, it can be horrible to look at if the users aren't aware about markdown and/or the special markdown syntax. In practice, there is only so much we can do to render a random email as HTML using markdown syntax. Maybe I can get to it this holiday season and it can go out for interested folks in the next Hyperkitty release :) > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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)

6 years, 4 months

[MM3-users] Re: Detectors and Bounces

by Mark Sapiro

On 8/5/22 09:17, summersan(a)nclack.k12.or.us wrote: > > My Questions: > > Is it normal to see large amounts of `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` lines in logs? > > Should there normally be other detectors listed in the logs beyond the `DSN` one? > > If so, is there a setting I can change somewhere to make this happen? Prior to flufl-bounce 4.0, it would run all detectors on every message to the -bounces address. Beginning with 4.0, it runs the detectors in a defined order from most specific/authoritative to least. If you are seeing only or mostly the `DSN` one, you have 4.0 and the `DSN` detector recognizes a RFC 3464 compliant bounce. > For reference, I can only find one other logcheck log that shows a `Running detector: <class 'flufl.bounce._detectors.dsn.DSN'>` line from before the recent Mailman 3 upgrade. In that past logcheck log, there are other detectors listed as well, which makes me wonder if something is still stuck with the new Mailman 3 install (or if maybe something needs to be changed in a setting file somewhere): Probably the upgrade also upgraded flufl.bounce to 4.0. So the real question is why are you seeing large numbers of bounces. Since it appears they are recognized by `DSN`, they probably aren't spam to the -bounces address. Do you have verp probes enabled (verp_probes = yes in the mta section of mailman.cfg)? If so, it's possible that you are getting bounces for spam and the like, but the probes don't bounce so the user's delivery is never disabled. -- 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

[MM3-users] Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3

by John Covici

On Sat, 13 Mar 2021 03:25:41 -0500, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > On 13/3/21 8:53, John Covici wrote: > >> We recommend installing Mailman and the web components in a virtualenv, > >> but it is not a requirement. We also suggest that postgresql is a better > >> choice than MariaDB. > >> > > I sort of am installing from source, gentoo installs from source. No > > one on the gentoo users mailing list seems to be able to help me, > > except to tell me to use a different mailing list mechanism called > > mlmmj. > > > From the perspective of someone who was in the same place (but > installing in a FreeBSD S.O.), I would recommend you to follow > the "virtualenv" guide but without executing the "env" > commands. It will produce a system wide mailman3 installation but > it will work (as it is for me since a few moths ago) > > I writed down a step by step path of my installation and it could > be of your interest (maybe you have to locate and install some > packages by different name, but I think it will be not much > difference). It could provide you a overall view of all the > processes implied. > > I'ts here: https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 Thanks, by the env commands you mean the creation and activation commands? I will certainly look at your thread. -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 1 month

[MM3-users] Re: only show mail domains from web host on web-host-url

by Mark Sapiro

On 3/19/21 11:14 AM, Jens Günther wrote: > Just checked again and saw: > > - in the setup it works perfectly in Hyperkitty, that's nice > > - for the first web host I have 2 mail domains registered, so it also > matches (unfortunately) with what you said :-( > > Anyway, I dceleted one of it, still both lists are shown on either web > host, so it's generally not working. I don't know why this didn't work. If there is only one mail host in the domains that has the current web host as its web host, it should work. > If I can do something on this issue, please advise me. Thanks. The issue is that neither Postorius or HyperKitty as a direct way of getting lists by web host as the web host information is not an attribute of the list. We have to see which mail hosts are associated with the current web host and then display only those lists that match one of those mail hosts. The issue with Postorius is if there was more than one mail host associated with the web host, this code https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… could be relatively easily made to work by extending all_lists to include all the mail hosts, but it wasn't clear to me how to fix https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list… in the case where there was more than one mail host. If you can suggest a fix, that would help. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

[MM3-users] Trouble Installing Mailman3

by Henry Hartley

I'm having problems installing mailman3 following the instructions on https://docs.mailman3.org/en/latest/install/virtualenv.html Everything goes well until I get to the Installing Mailman Core<https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail…> step, which has me do the following in my venv environment: (venv)$ pip install wheel mailman psycopg2-binary Ubuntu 24.04.02 LTS Python 3.12.3 pip version 24.0 First, I was getting problems because my company firewall was blocking outbound traffic. I got that taken care of. Next, I was seeing certificate errors, saying there was a self-signed certificate: WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))': /simple/wheel/ Could not fetch URL https://pypi.org/simple/wheel/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/wheel/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1000)'))) - skipping When I added --trusted-host pypi.org that error went away but I'm still unable to install anything: (venv) mailman@wz-prd-tpmd-1:~$ pip -v --trusted-host pypi.org install wheel mailman psycopg2-binary Using pip 24.0 from /opt/mailman/venv/lib/python3.12/site-packages/pip (python 3.12) ERROR: Could not find a version that satisfies the requirement wheel (from versions: none) ERROR: No matching distribution found for wheel The same error shows up if I try to install just mailman or psycopg2-binary, except the word "wheel" is replace with whichever package I've requested. I've rerun the apt install of python3-dev and python3-venv to make sure those are present and up to date. Any help you can provide will be greatly appreciated. -- Henry Hartley Westat

10 months, 3 weeks

[MM3-users] Re: Lookup Table Questions

by Mark Sapiro

On 12/7/21 4:09 PM, Peter Williams wrote: > > - The Mailman documentation notes that either hash or regexp tables are > supported. Is it ok to use LMDB or will I run into issues at some point? Mailman only supports hash and regexp tables for automatic maintenance of the tables as lists are created and removed. If you use LMDB tables you will need to maintain them yourself. The `mailman aliases` command won't do it. > - If LMDB tables are not a good idea to use, are there any drawbacks to > switching over to regexp tables? My main concern is that we currently have > 7000+ mailing lists, and I'm worried that switching over to regexp may > result in slower lookups. I am also wondering if there are potential issues > if the 'mailman aliases' command is run simultaneously alongside another > 'mailman aliases' command. In the past it seems like the hash table was > locked (which was good), and I'm not sure if this behavior is kept by > moving over to regexp. This may be more of a Postfix question and I > apologize in advance if I am asking the wrong mailing list for this. The locking is done in mailman/mta/postfix.py regardless of table type. I.e. it's the same for hash and regexp table updates. I wonder why you are manually running `mailman aliases`. This really shouldn't be necessary as the files are regenerated automatically as lists are created and removed. As far as performance of regexp vs hash tables, I have no idea. That's really a Postfix question. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 09:51 AM, Rubén Rivero Capriles wrote: > > In order to avoid compatibility issues, I reinstalled CentOs 7. Firewalld, Apache and BIND are operational. I also installed Python 3.4 at http://www.codeghar.com/blog/install-latest-python-on-centos-7.html; however I understand that Python 2.7 is still available and am confused about usage of each version. Mailman 3 consists of several pieces. There is a core engine which is Python 3. The core does the basic email list management and exposes many options and settings via a RESTful API. There is also mailman.client which provides Python bindings for the REST API. This is Python 2. We also provide a web management UI, Postorius and an archiver, HyperKitty. These are Django applications and all of this is Python 2. There are other pieces as well. > I downloaded the tarball for mailman 3.0.3. I will greatly appreciate if you quickly let me know how to install it. I do not wish to use mailman bundler. This is only the core. You can install it with python3 setup.py install either in a python 3 virtualenv or not, but this will only give you the core. I suggest you see the docs at <http://docs.list.org/en/latest/>, and if you don't want to use bundler, see <https://wiki.list.org/DEV/SetupDevEnvironment>, although bundler is the recommended way to set up a working, non-development Mailman suite. In short, the core requires Python 3.4, most of the rest of the suite requires Python 2.7 because of dependencies not yet ported to Python 3. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 11 months

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Mark Sapiro

On 3/20/19 5:43 PM, Ralph Seichter wrote: > With archiving enabled, mail is sent with headers like the following: > > Archived-At: <https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/> > List-Archive: <https://example.com/hyperkitty/list/foo-users@lists.example.com/> > List-Post: <mailto:foo-users@lists.example.com> > List-Subscribe: <mailto:foo-users-join@lists.example.com> > > The 'mailto:' entries are fine, but I need all 'https:' links to be > prefixed with https://lists.example.com instead of https://example.com . > > Does Mailman extract CN parts from the SSL certificate to populate the > header values (that would explain 'example.com' in my tests), or is this > something I can influence using configuration parameters? I searched the > docs for Mailman Suite and HyperKitty, but did not find an answer. It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py > def _get_url(mlist_fqdn, msg_id=None): > # We can't use HttpRequest.build_absolute_uri() because the mailman API may > # be accessed via localhost. > # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Htt… > # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-curren… > # result = urljoin(public_url, urlunquote( > # reverse('hk_list_overview', args=[mlist_fqdn]))) > # We use the MailDomain association from django_mailman3 to find out the > # proper domain. What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/ Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 1 month

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Abhilash Raj

On Thu, Oct 26, 2017, at 06:39 PM, Mark Sapiro wrote: > On 10/26/2017 06:16 PM, Fabian A. Santiago wrote: > > > > > But in my testing, I replied to a subscription confirmation message and received back an undeliverable looping email error message from postfix. Any clues there you can offer? I can post to the list from any email added via the admin console. The test subscriber address was local to my server. From an outside address, same error. > > > This usually means that postfic is trying to deliver to an address and > the message already has a Delivered-To: header with that address. > > What are the headers of the "looping" message in the report? What are > the Postfix log messages related to that message? > > > > Once I registered the new email domain, I reverted my postfix config back to the default suggested by maxking's docker instructions. > > > > https://github.com/maxking/docker-mailman > > > I have essentially no knowledge of the docker container images, so I > can't be much help with issues specific to them. The Postfix integration in container images is basically just using regex instead of hash maps and everything else is same. I do remember atleast one other person facing a similar issue where Postfix wouldn't accept listname+token@domain addresses with our regex. I am thinking this is the same issue. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] User management page [was: Changing subscription address]

by Stephen J. Turnbull

Core implementation details, so I beinging this here from Mailman Users @ mailman3.org. Abhilash Raj writes: > I have started working on designing a User management page[2] in > Core which should make it easy for superuser to manage several > things about a User, including the ones that don’t have an account > in Postorius to manage their own. I don't understand this design with a "page in Core". I was thinking about this kind of problem, and tentatively came to the conclusion that any reference to something that can be resolved to a User should generate a Django account for that User in Postorius or HyperKitty. Authorization to use that account would still require authentication via the usual email verification dance, or some level of admin privilege. The thing is that emails that have not been added to a User are unique. They will be the only Address attached to User created to manage them until authenticated, and transitively the only address attached to an automatically-created Django account (since those are 1-1 with core Users if they exist AFAIK). What's missing here is the ability to merge core Users and their corresponding Django accounts. Doing this with nothing more than the usual email verification dance is not *obviously* provably secure to me, so we need to be careful, but I think it probably will turn out to be as secure as you can get. It seems to me that User merging is the most pressing problem of this kind. (At least, it affects me on a couple of list hosts, as well as on GitHub and GitLab.) > [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 I'll take a look tomorrow or early next week. Steve

5 years, 1 month

[MM3-users] Re: Deleting default "example.com" domain breaks everything

by Abhilash Raj

On Fri, Jul 16, 2021, at 12:12 PM, Mark Sapiro wrote: > On 7/16/21 11:31 AM, mcarter(a)corneredrats.com wrote: > > Hello. I'm new with v3 of mailman. > > Installed via aptitude on deb10. > > After I logged in as admin, I created my actual domain, as "example.com" was there by default. > > I then deleted example.com, and everything broke. > > The only site I had was still using example.com. > > How do I either a) restore example.com in config or CLI (as web UI is completely broken now), or b) move my one and only "Site 1" to the domain I created? > > > Try setting `SITE = 0` in your Django settings file. If that doesn't > work, try successively 1, 2, etc. One of these should work. Usually, example.com is always 1 and then it increases sequentially. So, if this is the first one you created, I'd try using 2. > > Also going back to your prior thread, you had > > > root@mail:/usr/share/mailman3-web# python manage.py createsuperuser > > Aside from the python/python3 issue, you should run any Mailman and > Django management commands as the Mailman user (probably `list` in your > case), not as root. See https://gitlab.com/mailman/mailman/-/issues/920 > and https://gitlab.com/mailman/mailman/-/issues/776. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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)

4 years, 9 months

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Jacob Sievert

Hello, we seem to have the same problem right now. We are still on python3.6 and postgresql 12.9 I looked at our Table pendedkeyvalue and we have roughly 35k rows in that table, is that normal or shouldn't those get cleaned up after a while? with regards Jacob On 2022-01-28 15:57, Stephan Krinetzki wrote: > Stephen J. Turnbull wrote: >> Mark Sapiro writes: >> > mailmancore/API ->database >> > that seems to have an issue and only with this one >> > DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX >> > query. However, like you, I have no idea as to what you could do further >> > to debug this. >> > I have an idea, but it seems so obvious that presumably it's already >> been tried: log in to the database as mailman with pgsql and try >> deleting something. If that works immediately, try with mailmanclient >> and the mailman command line utility. >> Steve > > Well, we didn't try this. Since we don't know what the query for > deleting a held message in the database needs to look like, we left > that out for now. If someone can help me there, it would be great. > > Over the mailman shell it hangs as long as on the web ui (using > mailman shell -l list@host and iterating over the held messages). So > it is the communication Mailman API <-> Database. > _______________________________________________ > 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/

4 years, 3 months

[MM3-users] Re: Query on how to change moderator message to non-members

by Mark Sapiro

On 7/4/18 7:45 AM, robert.kydd(a)gmail.com wrote: > Hi Mark, thanks for this. I was away and only got back now. > It's great to get rid of the reason text. > Is there any way I can find out what is i18n message catalog. It would be nice to give a more pleasing message to the users I am still not clear on what Mailman version you are using. If it is Mailman 3, i18n translations for Mailman core are still a work in progress, and I can't tell you how to do this. For Mailman 2.1, you will find within Mailman's file system, a messages/ directory with several 'language code' subdirectories, but not 'en'. You need to create messages/en/ and messages/en/LC_MESSAGES/ and then create the file messages/en/LC_MESSAGES/mailman.po with contents like: ---------------------------------------------------------- # SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR ORGANIZATION # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. # msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "POT-Creation-Date: Sun Jun 17 12:22:07 2018\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=CHARSET\n" "Content-Transfer-Encoding: ENCODING\n" "Generated-By: pygettext.py 1.4\n" #: Mailman/Handlers/Hold.py:61 msgid "Post by non-member to a members-only list" msgstr "WHAT YOU WANT TO REPLACE IT WITH" ---------------------------------------------------------- with the various UPPERCASE things replaced appropriately and then 'compile' it via > msgfmt -o messages/en/LC_MESSAGES/mailman.mo messages/en/LC_MESSAGES/mailman.po -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

[MM3-users] Re: Modify approval email

by Odhiambo Washington

On Fri, Sep 15, 2023 at 5:33 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > pau.baiges(a)csuc.cat writes: > > > Is there a way to modify the email that is sent by default to list > > owners when a non-list member sends email to the list? > > Yes. As list owner (or site admin) in Postorius go to Templates, and > click on "New Template". Select list:admin:action:post from the > drop-down menu to the right of "Name". Copy the current message > (site-packages/mailman/templates/en/list:admin:action:post.txt is the > original, but do not edit this -- it will be overwritten on upgrades) > to the text box and edit to taste. Unfortunately there is no "web > site" variable but typically that is the same for all lists, so adding > > https://your.host.here/mailman3/lists/$list_id/held_messages > > in some appropriate place probably does what you want. > > There is no way to indicate that this is a link because these messages > are plain text. However, most mail clients will turn a URL into a > link. If your moderators are not so lucky, try wrapping it with > > <URL:https://your.host.here/mailman3/lists/$list_id/held_messages> > > or even the usual HTML: > > <a href="https://your.host.here/mailman3/lists/$list_id/held_messages"> > Moderation Page > </a> > > One of those may help. > Also, you can take a look at this documentation: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 7 months

[MM3-users] Re: Hyperkitty not receaving messages / empty archive [Django] ERROR (EXTERNAL IP): Internal Server Error: /hyperkitty/api/mailman/urls

by Mark Sapiro

On 1/21/25 05:44, Helge Baumgart wrote: > Hyperkitty-Api-Key in the docker-compose.yml is set via .env Variabel, > so it should be identical. I don't know how this works in the Docker image, but ... > Traceback (most recent call last): > File > "/usr/lib/python3.11/site-packages/django/core/handlers/exception.py", > line 56, in inner > response = get_response(request) > File > "/usr/lib/python3.11/site-packages/django/core/handlers/base.py", line > 197, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File "/usr/lib/python3.11/site-packages/hyperkitty/views/mailman.py", > line 109, in _decorator > not hmac.compare_digest( > > Exception Type: TypeError at /hyperkitty/api/mailman/urls > Exception Value: unsupported operand types(s) or combination of types: > 'str' and 'NoneType' The above code is doing auth = authorization.split() if (len(auth) != 2 or auth[0] != 'Token' or not hmac.compare_digest( auth[1], settings.MAILMAN_ARCHIVER_KEY)): and the exception says either auth[0] is None or auth[1] or settings.MAILMAN_ARCHIVER_KEY is None. But > META: ... > HTTP_AUTHORIZATION = 'Token (value)' and > Settings: > Using settings module settings ... > MAILMAN_ARCHIVER_KEY = '********************' So The Authorization header is the appropriate `Token value` which should result in auth[0] being 'Token', auth[1] being the value and MAILMAN_ARCHIVER_KEY is set > That is my docker-compose.yml: ... > mailman-web: ... > - HAYPERKITTY_API_KEY=${MM3_HYPERKITTY_API_KEY} #someapikey_longAndTrustworty I don't really understand why the above typo (HAYPERKITTY_API_KEY, not HYPERKITTY_API_KEY) would cause this error, but it needs to be fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

[MM3-users] Re: Mailman List Lost on URL transfer

by Mark Sapiro

On 09/20/2017 10:28 AM, heartsandbones(a)zoho.com wrote: > > Here’s the scoop: > I did a web site redesign for a non-profit. They didn’t mention to me that they had a mailman list associated with the site. When we transferred the url to Squarespace their list quakers(a)sbfriends.org stopped functioning and the administration login link: http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org results in a “server not found” error. > > I don’t know how to set up the site so that their mailman list works again. Please tell me exactly what to do to make this work. Let me know if I can provide any additional information to help you help me. As I have told you in other communications, you need a DNS A record for the mail.sbfriends.org pointing to the IP address of the Mailman server that hosts the list. We have no idea what that IP address is. You will have to ask your client what Mailman hosting service they were using for their sbfriends.org domain. That A record will probably suffice to get to the web UI for the list, but you will probably also need an MX record for the sbfriends.org domain pointing to mail.sbfriends.org for mail delivery to the list. > This is my first post to this forum, so I hope I’ve done so correctly. The correct list for Mailman 2.1 issues (http://mail.sbfriends.org/mailman/admin/quakers_sbfriends.org is a Mailman 2.1 URL) is mailman-users(a)python.org <https://mail.python.org/mailman/listinfo/mailman-users>. This list is for Mailman 3. However, you won't get a different answer from that list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 7 months

[MM3-users] Re: Warning on EL8: django-mailman 1.3.12 prefers Django 4.2 which requires Maria DB>10.4

by Jered Floyd

The weird client version was, of course, my fault... I had followed the instructions here in my settings.py: https://adamj.eu/tech/2020/02/04/how-to-use-pymysql-with-django/ This fix was incorporated into PyMySQL some time ago and is no longer necessary. The requirement for MariaDB remains real. --Jered ----- On Apr 3, 2024, at 7:36 PM, Jered Floyd jered(a)convivian.com wrote: > A heads-up for anyone else on RHEL 8, because the error is mystifying. > > django-mailman 1.3.12 bumps the preferred django version from 4.1 to 4.2. Django > 4.2 requires MariaDB 10.4 or later. RHEL 8 has full lifecycle support for > MariaDB 10.3. > > For some reason I haven't yet been able to identify, this causes pyMySQL > integrations to fail with the mysterious error: > django.core.exceptions.ImproperlyConfigured: mysqlclient 1.4.3 or newer is > required; you have 1.4.6. > > (Yes, Database.version_info contains "(1, 4, 2, 'final', 0)" while > Database.version contains "1.4.6" and I am totally stumped where that 1.4.2 is > coming from as it appears... nowhere.) > > Bypassing that error check gives the more informative: > django.db.utils.NotSupportedError: MariaDB 10.4 or later is required (found > 10.3.39). > > Doing a pip install with django\<4.2 works. This is not ideal since 4.1 is past > LTS, so I would recommend that Mailman systems be migrated to RHEL 9. > > --Jered > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years

[MM3-users] Re: Mailman3 upgrades

by Caballero, Danny (Dan)

Thank you! Yes, it was my fault. I have some customization in base.html. I'll need to track those changes across updates. Thank you! ---- Dan Caballero Systems Administrator Academic Computing Solutions IMSS - Caltech https://imss.caltech.edu ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Tuesday, October 19, 2021 8:02 PM To: Caballero, Danny (Dan) <dancab(a)caltech.edu>; mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Mailman3 upgrades dancab(a)caltech.edu writes: > "Loading failed for the <script> with source > “https://mailman3.caltech.edu/static/hyperkitty/libs/jquery/jquery-1.10.1.min.js” > > Sure enough, I do not have that script. In fairly freshly updated sources, I have references to one or the other of > -rw-r--r-- 1 gunicorn root 117370 Oct 19 14:55 jquery-ui-1.10.3.custom.js > -rw-r--r-- 1 gunicorn root 58173 Oct 19 14:55 jquery-ui-1.10.3.custom.min.js in hyperkitty/hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bunudle.min.js.map hyperkitty/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js hyperkitty/hyperkitty/templates/hyperkitty/base.html The last file also refers to hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css My guess is all the files you listed are from a recent installation or upgrade, but somehow base.html didn't get upgraded. Based on the principle "always blame the user" ;-), I'd start by checking if our version is shadowed by your local version? Anyway, I bet the version number is wrong in base.html and if you fix that everything else will fall in line. If not, check if popper and boostrap are either older versions or perhaps shadowed by older versions somewhere. A word to the wise: grep(1)ing the .min.js.map files is not advised. They're huge and all one line it seems. Better to use an editor's search function.

4 years, 6 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by gordon＠dickens.com

Hello everybody, I successfully resolved the owner:group issue and I am no longer getting the permission errors. Basically, I had to set the ownership:group to mailman:www-data and make the group permissions rw for everything to work successfully with Apache and Mailman3. As I mentioned earlier, I have mailman (core) now working, however, I cannot seem to get the web interface to work. I believe that I have gotten rid of all of the permissions issues and the mailman3-web service starts and stops without error. However, when I use a browser to go to the web interface, I get File Not Found errors in the browser window and my Apache2 logs say: 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /mailman3/postorius/lists/members.georgiajets.org/ HTTP/1.1" 404 282 173.165.166.34 - root [04/Feb/2022:12:54:06 -0500] "GET /favicon.ico HTTP/1.1" 200 318 So, I get File Not Found error 404 for the web page but the favicon.ico file appears to be found successfully. Therefore, I suspect that my apache configuration file for mailman3 may be at the source of my problems and specifically the alias for the static directory. Here is my apache configuration file: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! # ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> By the way, this is the Apache configuration file that the Debian package installed with my initial installation. Does anybody see any problems in my Apache configuration file that could be causing my problems? Do you see or suspect any other issues? Thanks, Gordon

4 years, 2 months

[MM3-users] Re: 500 error on Held Messages page

by Mark Sapiro

On 9/21/22 16:24, Dan Caballero wrote: > Mark, > > I'm seeing this issue pop up this week with several lists. You previously mentioned two conflicting browsers potentially causing the issue. Can you elaborate? That would only cause a transient issue which would not occur on a subsequent get of the held message view. I gather this is not the case here. I.e. once the error occurs on a get of the held message view, it is persistent. > In addition, is there a way for me to run this cleanup using mailman shell -r "somescript" so that I can check all the lists instead of one by one? For a -r script, try ``` # In non-interactive scripts, we need the explicit imports. from mailman.interfaces.listmanager import IListManager from mailman.interfaces.requests import IListRequests, RequestType from zope.component import getUtility def somescript(): for mlist in getUtility(IListManager): requestdb = IListRequests(mlist) for req in requestdb.held_requests: if req.request_type == RequestType.held_message: if not requestdb.get_request(req.id): print(f'List: {mlist.list_id}, Bad request id: {req.id}, deleting') requestdb.delete_request(req.id) ``` The real question here is what are these spurious requests and how are they occurring. If you do a query like ``` SELECT * FROM _request; ``` Are there entries with empty `data_hash` or entries with an `id` that is not the value of any `pended_id` in the `pendedkeyvalue` table. BTW, I understand why you thought an import was needed in the interactive script in my message at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… - the `from mailman.interfaces.` line was a mistake on my part and shouldn't have been there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 11 months

[MM3-users] Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 11 months

[MM3-users] Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 5/18/22 10:48, dancab(a)caltech.edu wrote: > Mark, > > We have a question related to this thread. We use LDAP for authentication. It seems that the name attributes can only be edited via the LDAP synchronization when a user logs in for the first time and thus creates their user account. > > But what about list members that are not in LDAP? What happens behind the scenes when a member is added to a list? The user's display name is set when the user record is initially created. Assuming someone who is initially unknown, this can happen when the unknown user signs up for a web account, when the unknown user subscribes to a list via the web UI or when the unknown user is mass subscribed to a list. > Manually subscribing members has different results with our configuration. > > I've seen the manually entered name show up as "None" <foobar(a)caltech.edu>. There was a pre-existing user with that address and no display name. > I've seen the entry be accepted as is, eg. "John Doe" <jdoe(a)example.com> > I've seen the name entry be ignored but the email accepted eg. "Foo Bar" <foobar(a)caltech.edu> is subscribed but the member list only shows <foobar(a)caltech.edu> The display name has nothing to do with message acceptance. That is based only on the address. In Postorius >=1.3.6 there is a `Users` selection at the top of most pages if you are logged in as a superuser. This allows management of users including their display name. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 06:00, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > we are now getting feedback from people, who say that they are unable to > sign up, with mailman3 telling them: > > Subscription request already pending > > this is somewhat bad as: > > - at least some of the users (who reported the problem) tried to > subscribe 2 months ago (2022-01-04) - if they did not confirm their > email back then, i'm pretty sure that this email has been lost by now > - my /etc/mailman3/mailman.cfg has "pending_request_life: 3d" This is https://gitlab.com/mailman/mailman/-/issues/729 fixed in Mailman 3.3.5. > - i (as administrator) do not see any "pending subscriptions" (the list > is setup with a simple "Confirm" subscription policy The count badge only counts subscriptions waiting moderator approval. If you pull down the Subscription requests tab and click Pending Confirmation you should see them and be able to discard them. > i wonder: > - why are the pending subscriptions not expired? (i guess they should > have expired after 3 days) It's a bug fixed in Mailman core 3.3.5 > - why can't people re-subscribe while there's a subscription pending > (e.g. if the confirmation mail got lost)? Because that's the way it was implemented. > - how can i list all pending subscriptions (for a given mailinglist)? Pull down the Subscription requests tab and click Pending Confirmation. > - how can i resolve the situtation (e.g. send out another reminder; > manually expire the pendings; manually confirm the pendings,...) If the above doesn't answer that. provide more detail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

[MM3-users] Re: Connection lost during _handle_client()

by Mark Sapiro

On 11/28/24 9:17 AM, Alain D D Williams wrote: > > /var/lib/mailman3/queue/out/ contains 4 .pck files and one .bak file. There are > being continually read & replaced by other files of similar names - like 1732809409.1069376+eb3354a0fc1f0a9bfa95ff7e15e2430ab7c2b885.pck > The process doing this is a 'qrunner' The .bak file is the one currently being processed by the `out` runner. The others are waiting to be sent. I don't know why they are continually being dequeued and requeued I suggest you stop Mailman core and then examine these files with `mailman qfile` to see if there is some issue with one or more of them, but this seems unlikely. More likely is some issue with the `out` runner itself, but I have no idea what that would be except that issues like this can be caused by files in Mailman's var/templates/ directory that aren't readable by the Mailman user (often caused by running `mailman import21` as root). > I am getting ~50 lines/second appended to /var/log/mailman3/web/mailman-web.log > > [pid: 1348330|app: 0|req: 4366/4366] ::1 () {54 vars in 1065 bytes} [Thu Nov 28 17:02:18 2024] GET /mailman3/hyperkitty/api/mailman/urls?mlist=chat%40bray.phcomp.co.uk&msgid=Z0iJAoTHHrzK2ypO%40phcomp.co.uk => generated 126 bytes in 3 msecs (HTTP/1.1 200) 7 headers in 220 bytes (1 switches on core 1) This looks like some kind of DOS attack. Look at the GET requests in the web server log. > /var/lib/mailman3/queue/shunt/ contains 4 .pck files. For each of these, there should be an entry in mailman.log indicating the exception with a traceback. Look for entries in the log ending with a `SHUNTING` message. -- 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

[MM3-users] Re: Running mailman3 on AWS and dealing with SES email verification

by Mark Sapiro

On 4/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > This seems to be a very basic question and/or issue, but I could not find a reliable for it: > > Assume a list member with the email address like (just as an example) > joe.student(a)university.edu > sends an email to a list, Mailman gets the email, processes it and would try to send that email to all members with a sender field as: 'joe.student(a)university.edu'. plus listname(a)listserver.TLD Are you referring to the envelope sender or to the From: header? The envelope sender will be listname-bounces(a)listserver.TLD or if VERP is enabled, listname-bounces+recipient=recipient.domain(a)listserver.TLD. The From: header will be unchanged from the incoming message. If yo want the From: to be the list, you can apply DMARC "Replace From with list address" unconditionally and the From: will look like From: joe.student via listname <listname(a)listserver.TLD> ... > I found some solution: > > > * Asking the members to add their email to the signature > * manipulating the from field and add the name of the sender as a comment, not that easy, needs some Python code > * manipulating the from files and replacing the @ with something else, not that easy, needs some Python code > * . . . The DMARC mitigations will do these thing for you. > More important: None of these would allow a simple click on the reply bottom to send the email to the original sender. And they will add the poster's original From: address to Reply-To: -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: HyperKitty and duplicate emails across maillists

by Stephen J. Turnbull

Derek Lambert writes: > For new messages does mailman generate unique message IDs for each > recipient? Mailman in principle doesn't generate message IDs at all. That's the job of originating clients or their MTAs. Mailman is what is called an "intermediary": it may do useful transformations on a message (such as adding RFC 2369 header fields and the List-Id field, as well as headers, footers, and subject decorations, removing banned media types, and even changing the format of text parts (such as removing HTML parts from multipart/alternative messages, or translating HTML to plain text by formatting with a browser such as Lynx), but in some sense the content of the message remains faithful to the author's intent. In such cases, the message is considered to be the same for the purposes of assigning Message-Id, so Mailman doesn't touch it. In the case that Mailman receives a message that has no Message-Id, it may be a good idea to generate one. (I don't think this is implemented. It has its problems as well as its benefits.) Otherwise, no, Mailman leaves the existing Message-Id alone. > E.x. if multiple lists (children) are members of another list > (parent), will the children lists all be able to archive the same > message sent by parent? Yes. I'm not sure whether the message body is stored multiple times or only once[1], but the primary key for archived message is effectively the list id plus the message-id. Steve Footnotes: [1] Probably multiple times, once for each list that has archiving turned on. Ensuring that any relevant decorations (headers, footers, Subject tags) are consistent would require pretty fragile analysis of the messages and complicated storage and indicies.

6 years, 7 months

[MM3-users] To what extent can mailman 3 handle images and html?

by Paul Arenson

Hi The other day I attempted to send a message from my mail client (Apple computer, Mail program, html--well, what they call Rich Text). While a user was able to send a message previously that contained an image, I was unsuccessful. As well, links were weird. LINKS ===== Because My wordpress often has a Japanese URL and they can become very long, I tried both the URL as is and embedded (made a clickable html link). URL === So while I typed https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis.... It came out double as https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... <https://www.tokyoprogressive.org/journalist-ito-shiori-sues-alleged-rapis... (The full link was truncated with ... at the end, and the link appeared twice with the second instance preceded by "">") The embedded one did not come out embedded buy showed the text like this: Alternate link: 多摩川河川敷に男性の遺体、増水した川に流されたか <https://www.tokyoprogressive.org/%e5%a4%9a%e6%91%a9%e5%b7%9d%e6%b2%b3%e5%... QUESTION 1: Is there a preferred way to write links, or will there always be problems with the mail clients? (Even the web archive shows this problem though): https://list.tokyoprogressive.org/hyperkitty/list/discuss@list.tokyoprogres… See the top item Homeless man drowns in river during Typhoon and what I mean. IMAGE No image appears though one was added inline. And, as I said, a user was previously able to add one. I do not know how she did it. I also posted it to my web site instead of the newsletter for unrelated reasons. But there was an image (Originally got a warning the message was held because the attachment or something). So are there guidelines one whether/how to attach an image so that it makes it? Thanks

6 years, 6 months

[MM3-users] Re: equivalent mailman 3 commands from 2.0

by Mark Sapiro

On 10/25/21 9:16 AM, bob B wrote: > For my 2.0 environment, I have scripts to dump list info, but i can't find the equivalent in mailman 3, for some commands, for example I use: > > /usr/lib/mailman/bin/list_lists which equates in mailman3 to "mailman lists" > /usr/lib/mailman/bin/list_members which equates in mailman3 to "mailman members [listname]" > > But I also use > /usr/lib/mailman/bin/list_admins [listname] > /usr/lib/mailman/bin/config_list [listname] > > Are there equivalent command line commands to get this info in mailman3? for list_admins you can use `mailman members --role administrator [listspec]`. See `mailman members --help`. There is no mailman command equivalent to config_list at this time > The mailman3 "mailman withlist [listname]" takes me into an interactive prompt not sure where to go from there. From there you enter Python statements to do what you want. e.g. ``` $ /opt/mailman/mm/bin/mailman withlist -l list.example.com 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. The variable 'm' is the list.example.com mailing list >>>for property in dir(m): ... if not property.startswith('_'): ... print(f'{property}: {m.__getattribute__(property)}') ... ``` You can also create scripts to run with the --run option, See `mailman withlist --details`. > I can use the API > > curl --user [ADMIN]:[password] http://[IP]]/3.1/lists/[listname]/config | python3 -m json.tool > > > But just curious if there is a command line equivalent like in mailman2? Not at this time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

[MM3-users] Re: Strange URL in error message

by waps＠tantalus.jena.thur.de

Hi Mark, thanks for your patience. But now I get a little spinning wheel on the archive site, 3 "Error 500" in the Browser console and /var/log/mailman3/web/mailman-web.log shows repeatedly the error: ERROR 2024-07-18 08:34:38,261 1760 django.request Internal Server Error: /mailman3/hyperkitty/list/latex-team(a)latex-project.org/posted-to Traceback (most recent call last): File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner response = get_response(request) ^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/lib/view_helpers.py", line 137, in inner return func(request, *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/views/mlist.py", line 304, in overview_posted_to for thread in mlist.recent_threads: ^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 162, in recent_threads return self.cached_values["recent_threads"]() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/common.py", line 58, in __call__ return self.get_or_set(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 317, in get_or_set return [Thread.objects.get(pk=pk) for pk in thread_ids] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/hyperkitty/models/mailinglist.py", line 317, in <listcomp> return [Thread.objects.get(pk=pk) for pk in thread_ids] ^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 435, in get raise self.model.DoesNotExist( hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. Since the archive is still quite empty and we have only one mailing lis, it would not be a big loss if it could resettet. But how I can do the, without resettinh the member data? Could it be that the Sqlite interface is not as stable as one the the "real databases"?

1 year, 9 months

[MM3-users] Re: toward improving correctness when running on single core system ...

by Ruth Ivimey-Cook

One of the simpler ways of experimenting with mailman on a restricted system is using an SBC - something like a Raspberry Pi 2 or 3, or a Beaglebone, or similar. Both have limited memory and CPU, and are relatively slow systems. I would avoid a Pi 4 because it's too powerful in this context! Logging errors always changes the behaviour, but you can do much by noting things to internal variables and then after the event printing those (e.g. set a variable to count the number of times a try-lock operation found the lock held), and perhaps then doing the logging to a memory filesystem (Linux: tmpfs) which will have much lower latency. Normally a linux /tmp is using tmpfs. A multicore system will have different behaviour to a single core, but the kernel will almost always be preemptive (force timeslice). So one option might be to experiment with a fast-tick (e.g. 1000Hz or higher) kernel such that the timeslices are shorter. (It used to be the case Linux ran on 100Hz - I know most kernels are now "tick-less", meaning there is no persistent timer interrupt marking time, but there will be a unit of timeslice). A final option: if the problem is (as it appears to be) one of starvation, then perhaps the system is better run (on that hardware) with fewer worker processes. That is, cut the 13 workers down to e.g. 8. That said, starvation is something that can normally be designed out of systems though I know far to little about the architecture here to say if that is the case here. HTH, Ruth On 19/06/2023 18:51, Stephen Daniel wrote: > I'm currently running the entire mailman3 stack, including postgres and > postfix, plus my production web server, all on a GCP e2-small instance. > e2-small is two virtual CPUs running on a single physical core, restricted > to consuming at most 50% of the CPU cycles on that core. The system has 2 > GB of memory, 10GB of disk space. > > The entire stack runs well, albeit slowly, on this configuration, for which > I pay about $13/month. The entire stack is shut down every night so I can > take a snapshot while the applications are down. Once the snapshot is > complete, the stack is restarted. I have no startup issues in this > configuration. > > It is hard to imagine a more limited pool of resources, yet everything > works. > > On Mon, Jun 19, 2023 at 12:38 PM Nelson Strother < > justfixit(a)marilynstrother.com> wrote: > >> [My apologies for the mangled formatting of the diffs in [2] and [3] >> above. at least as shown on the web view of this list. Will happily >> repost or resend by direct email if anyone expresses interest.] >> >> > Presumably there's also a chance for the runner to detect and log the >> expired lock before it dies. >> >> This may require some cleverness, as the delays introduced by recording >> a log message e.g. "I'm the nntp runner holding the lock, and it has not >> expired yet." are likely to change the results of the lock competition, >> maybe even allowing all runner processes to continue as intended. It is >> unclear to me whether a process would ever have an opportunity to record >> a log message e.g. "I'm the nntp runner holding the lock which has >> expired, but I am not dead yet." before it dies. If such an opportunity >> exists, it should extend the lock's lifetime via e.g >> Lock.refresh(timedelta(seconds=10)). >> >> As I attempted to summarize at the end of [3] above, each time I tried >> shorter sleep intervals (1, 10, 15 seconds) within >> .../flufl/lock/_lockfile.py the original problem remains, namely one or >> more locks are broken and runner processes die. >> >> On 6/19/23 03:00, Stephen J. Turnbull wrote: >>> > The best "performance" I have yet obtained on this single core >>> > system is [by] [3] [which waits 20s before trying to obtain the >>> > lock]. >>> >>> Is 20s necessary? There are a lot of runners, you may be able to cut >>> the startup time by 2-3 minutes if you can cut that to 5s or less. >>> That would still be 100x longer than the naive #cores * seconds >>> estimate, but perhaps significant. >> _______________________________________________ >> 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to swd(a)pobox.com >> > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to ruth(a)ivimey.org -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

2 years, 10 months

[MM3-users] All list messages shunted due to mailman core database lock

by Ryan Curtin

Hi there, I have been trying to debug a git commit development list for a project I maintain: http://lists.mlpack.org/mailman3/hyperkitty/list/mlpack-git@lists.mlpack.or… The list is run on mailman3 as provided by Debian. Messages are successfully received---you can see all the test messages in the archives I just linked to if you want to click on it. However, no messages are actually relayed to subscribers. I spent a while digging into logs and found that every message sent to the list results in an error like this in /var/log/mailman3/mailman.log: ``` Oct 02 17:01:26 2023 (2957556) Uncaught runner exception: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlite3.OperationalError: database is locked The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 173, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 266, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/runners/pipeline.py", line 37, in _dispose process(mlist, msg, msgdata, pipeline) File "/usr/lib/python3/dist-packages/mailman/core/pipelines.py", line 50, in process handler.process(mlist, msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/handlers/acknowledge.py", line 46, in process member = mlist.members.get_member(sender) File "/usr/lib/python3/dist-packages/mailman/model/roster.py", line 120, in get_member memberships = self._get_all_memberships(email) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/roster.py", line 116, in _get_all_memberships return members_a.union(members_u).all() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3373, in all return list(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 3534, in __iter__ self.session._autoflush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1633, in _autoflush util.raise_(e, with_traceback=sys.exc_info()[2]) File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 1622, in _autoflush self.flush() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2540, in flush self._flush(objects) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2682, in _flush transaction.rollback(_capture_exception=True) File "/usr/lib/python3/dist-packages/sqlalchemy/util/langhelpers.py", line 68, in __exit__ compat.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/orm/session.py", line 2642, in _flush flush_context.execute() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 422, in execute rec.execute(self) File "/usr/lib/python3/dist-packages/sqlalchemy/orm/unitofwork.py", line 586, in execute persistence.save_obj( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 230, in save_obj _emit_update_statements( File "/usr/lib/python3/dist-packages/sqlalchemy/orm/persistence.py", line 994, in _emit_update_statements c = cached_connections[connection].execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1011, in execute return meth(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/sql/elements.py", line 298, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1124, in _execute_clauseelement ret = self._execute_context( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1316, in _execute_context self._handle_dbapi_exception( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1510, in _handle_dbapi_exception util.raise_( File "/usr/lib/python3/dist-packages/sqlalchemy/util/compat.py", line 182, in raise_ raise exception File "/usr/lib/python3/dist-packages/sqlalchemy/engine/base.py", line 1276, in _execute_context self.dialect.do_execute( File "/usr/lib/python3/dist-packages/sqlalchemy/engine/default.py", line 609, in do_execute cursor.execute(statement, parameters) sqlalchemy.exc.OperationalError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (sqlite3.OperationalError) database is locked [SQL: UPDATE mailinglist SET last_post_at=?, post_id=? WHERE mailinglist.id = ?] [parameters: ('2023-10-02 21:01:21.702224', 99565, 2)] (Background on this error at: http://sqlalche.me/e/13/e3q8) Oct 02 17:01:26 2023 (2957556) SHUNTING: 1696280486.719109+114cb2cc738a61874a5eed7e3f66a3ac111f5b90 ``` I have tried a handful of things: * Restart mailman3 and mailman3-web systemd services. * Ensure that there are no stale locks in /var/lib/mailman3/locks/ when mailman3 core is stopped. * Move the database in /var/lib/mailman3/data/mailman.db out of the way and replace it with a copy, in case some process is holding it open. * Unshunt all the messages with `sudo /usr/bin/mailman3 unshunt` (didn't realize this would drop all the shunted messages, but not a big deal). Most threads I have read appear to be related to the Django interface encountering a locked database, but this looks different---it seems mailman core is having the problem, not anything having to do with mailman3-web or Django. Does anyone have any thoughts on things I can do to fix this error? I am not a mailman3 expert (and to be perfectly honest I don't want to be one, I just want to post things to the list :)). One extra caveat: rebooting the machine I am using is not a realistic option. Thanks in advance for any help. Ryan -- Ryan Curtin | "Not like this... not like this." ryan(a)ratml.org | - Switch

2 years, 6 months

[MM3-users] Re: Auth question

by Mark Sapiro

On 03/30/2017 02:27 PM, David Krantz wrote: > > I tried to upgrade today. The result is a broken install which fails > when trying to upgrade the database. > > > $> ./bin/mailman-post-update > [...] > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/utils.py", > line 94, in __exit__ > six.reraise(dj_exc_type, dj_exc_value, traceback) > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/db/backends/base/base.py", > line 236, in _commit > return self.connection.commit() > django.db.utils.IntegrityError: update or delete on table "auth_user" > violates foreign key constraint > "social_auth_usersocial_user_id_193b2d80880502b2_fk_auth_user_id" on > table "social_auth_usersocialauth" > DETAIL: Key (id)=(3) is still referenced from table > "social_auth_usersocialauth". This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > I have tried to drop and recreate the databases but I get the above > result anyway. I'm not sure what you mean by drop and recreate the databases. You should just drop the `social_auth*` tables, or if there's nothing in the database you want, just starting with an empty database should work. > The description in > https://wiki.list.org/DOC/Mailman%203%20installation%20experience is > very hazy. The process of symlinking in libraries is fiddly to say the > least. I get mailman to start but not any web interface. I have not > tested mailman so if it works rather than just start I do not know. Sorry about that. The symlinking was due to my starting with bundler and then "undoing that" without trying to find everywhere the old paths might be referenced. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years

[MM3-users] Re: Invalid confirm text

by Mark Sapiro

On 8/14/20 3:28 AM, w.schoener(a)alp.dillingen.de wrote: > > Now, when I try to subscribe to the list, I get my first message in german language, with the confirm request: > return the message unchange. > > When I return the message, I get an answer: > Invalid confirm text. With current releases of Mailman, the confirm request you receive should be: From: <listname>-confirm+<hex-token>@<list.domain> Subject: confirm <hex-token> with actual values for <listname>, <hex-token> and <list.domain>. This will change in Mailman 3.3.2, see <https://gitlab.com/mailman/mailman/-/merge_requests/678> > My request is pending. And there is no way to solve this pending request, in the webinterface, no subscription request is shown, no member is shown and no no-member is shown. Your reply should go to <listname>-confirm+<hex-token>@<list.domain>. Some MTA/MDA in the delivery chain may drop the ++<hex-token> suffix. If this is the issue, you can send a message with the one line confirm <hex-token> as either the Subject or body of the message to <listname>-request@<list.domain>. That should work. Note in the web UI (Postorius), at least in recent versions, even though it shows "Subscription requests 0" that should be a pull-down with the two choices Pending Approval and Pending Confirmation and selecting Pending Confirmation should show yours. The count badge only counts Pending Approval. > Have you any hint, what is going wrong. What do I have to respect to create a message, where the confirmation is working. See the current English confirmation template at <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/templates/en/l…> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 8 months

[MM3-users] Xapian error on RHEL9 - module 'xapian' has no attribute 'QueryParser'

by Stephen J. Turnbull

l.reilly(a)ucl.ac.uk writes: > I first tried to install it using Method 1 > (https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian) > however, xapian_wheel_builder.sh seems to just exit right as it > starts "preparing xapian wheel...". I suppose this probably includes an invocation of "python -m build ...". Try editing the xapian_wheel_builder.sh script to add the "-v" option after "build" to try to get more information about what it did and (I hope) why it didn't. Not sure if multiple "-v" gives more information. I believe you could also use the distutils build instead of wheel, and ask pip to install that into the venv. (I could be wrong, one of the motivations for wheels was handling installation of binary Python modules and auxiliary DSOs better.) > I ended up installing Xapian 1.4.29 from source and symlinking > xapian in the venv as per Method 2. Method 2 is Debian-specific (it depends on Xapian and python-xapian both being packaged). What exactly did you do? > Has anyone else encountered this before? I've done the python-xapian build and install for an Ubuntu host with no problem. I used the Ubuntu Xapian package and installed python-xapian directly into the site-packages directory in the venv, though. I did need to work out a g++ version compatibility problem. I assume you're building the Python bindings in the same tree and at the same time as the main application? If so, you shouldn't have a problem with library version mismatches. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 1 week

[MM3-users] Re: Please help - Held message is crashing mailman.

by Alex King

Thanks for your help Mark, it's ideal having the pointer to the issue in gitlab. I'll raise a bug with Ubuntu because this makes mailman3 in their LTS version unusable for me. Perhaps they can backport a fix for their version in LTS, otherwise they may have a backport or PPA source where I can get a 3.2 version, or just pin some packages from cosmic or disco. I think documenting this will be useful to people who hit the issue in future (Bionic/18.04 is supported until 2023, and likely the most used until 20.04 is released). Thanks, Alex On 7/04/19 4:29 AM, Mark Sapiro wrote: > On 4/5/19 10:27 PM, Alex King via Mailman-users wrote: >> Hi, >> >> I've used mailman a lot in the past, and decided to install mailman3 in >> a recent install. I'm unimpressed so far, it seems buggy. >> >> Running on Ubuntu 18.04.2 LTS from packages, mailman3 3.1.1-9, >> mailman3-web 0+20170523-14, python-django-postorius 1.1.2-3. >> >> After a few messages, I now can't go to the "Held Messages" in >> postorius, I get a 500 error. >> >> I tried to interact on the command line, but could not work out how. >> Reading >> https://mailman.readthedocs.io/en/latest/src/mailman/docs/install.html >> and >> https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…, >> I tried: >> >> # mailman shell >> Welcome to the GNU Mailman shell >> >>>>> command = cli('mailman.commands.cli_withlist.shell') >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> NameError: name 'cli' is not defined >> >> I did a lot of reading of the manual and googled, but I have no idea >> where the cli object is supposed to come from.....? The documentation >> is confusing. > > The line > > command = cli('mailman.commands.cli_withlist.shell') > > in > <https://mailman.readthedocs.io/en/latest/src/mailman/commands/docs/shell.ht…> > is dependent upon some behind the scenes setup to make the doctests > work. Granted this is confusing, but basically all that does is set > things up for the doctests to run the 'mailman shell' command. It is not > intended to be run from within 'mailman shell'. > > >> Anyway, after some trial and error, i found: >> >> # mailman shell >> Welcome to the GNU Mailman shell >>>>> list_manager = getUtility(IListManager) >>>>> m=list_manager.get("committee(a)[redacted].org") >>>>> from mailman.interfaces.requests import IListRequests >>>>> requests = IListRequests(m) >>>>> [x for x in requests.held_requests][0].id >> 8 >>>>> requests.get_request(8) >> Traceback (most recent call last): >> File "/usr/lib/python3.6/code.py", line 91, in runcode >> exec(code, self.locals) >> File "<console>", line 1, in <module> >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/requests.py", line >> 120, in get_request >> result.data_hash, expunge=False) >> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", >> line 85, in wrapper >> return function(args[0], config.db.store, *args[1:], **kws) >> File "/usr/lib/python3/dist-packages/mailman/model/pending.py", line >> 138, in confirm >> value = json.loads(keyvalue.value) >> File "/usr/lib/python3.6/json/__init__.py", line 354, in loads >> return _default_decoder.decode(s) >> File "/usr/lib/python3.6/json/decoder.py", line 339, in decode >> obj, end = self.raw_decode(s, idx=_w(s, 0).end()) >> File "/usr/lib/python3.6/json/decoder.py", line 355, in raw_decode >> obj, end = self.scan_once(s, idx) >> json.decoder.JSONDecodeError: Unterminated string starting at: line 1 >> column 1 (char 0) >> >> It seems something was written out to disk that can't be read in for >> some reason (assuming a json object on disk?) > > This is <https://gitlab.com/mailman/mailman/issues/385> which should be > fixed by <https://gitlab.com/mailman/mailman/merge_requests/333>. The > fix in in Mailman core version 3.2.0 > > >> How do I debug this further? How do I find the json being decoded? Any >> help would be appreciated. (I found mailman2 just worked, I was happy >> with that.) > > The issue is in storing a pickled representation of the json encoding of > 'rule_misses'. This gets very long if you have lots of header filters, > and with at least the mysql backend gets truncated in the database which > causes the Unterminated string error. > > I'm not sure what your options are for upgrading. The current Debian > packages are all >= 3.2.0 [1], but Ubuntu doesn't get 3.2.0 until cosmic > (18.10) [2]. > > [1] https://packages.debian.org/search?keywords=mailman3 > [2] https://packages.ubuntu.com/search?keywords=mailman3 > >> (My colleague posted a bug about this I believe but I don't have the >> link to that.) > > I haven't seen it. > >

7 years

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Mark Sapiro

On 07/31/2018 01:52 PM, Ryan McClung wrote: > That explains a lot. Is there any documentation you can provide to show me > where I can set a static config/db? See <http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html> That may not specifically address your question, but it will explain the issue in detail. An example of what I do on several servers I support is this. First, I install Mailman in a virtualenv which is /opt/mailman/mm/venv. Then the commands I run are all put in /opt/mailman/mm/bin. the actual installed 'mailman' command is /opt/mailman/mm/venv/bin/mailman but I never run that directly or as 'mailman' with the venv active. My var/ directory is /opt/mailman/mm/var. My mailman.cfg is actually outside of the var/ directory in /opt/mailman/mm/mailman.cfg. (In some cases for historical reasons it's in /opt/mailman/mm/deployment/mailman.cfg, but ignore that.) In /opt/mailman/mm/bin/mailman, I have #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/mm/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ The details such as installing in a venv or where things are are not the important things. The important thing is the only 'mailman' command I ever run invokes Mailman with a -C option that points to the only config I want to use and that in turn has a var_dir setting pointing to, in my case, /opt/mailman/mm/var. Also, the 'unset PYTHONSTARTUP' is there to address an issue with 'mailman shell' that would double the size of the shell history file each time it was run. I'm not certain that's still needed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 8 months

[MM3-users] Re: mailman import21 passwords

by Sam Darwin

> There is no guarantee that any Mailman Core installation into which a MM 2.1 list is imported actually also supports Django users for Postorius and/or HyperKitty. There is no guarantee that a mailman-core installation also includes Postorius and/or HyperKitty. However we can imagine that the vast majority do utilize all those components. If you've installed mailman3, you are probably installing Postorius and HyperKitty. To account for the fact that it's not 100% guaranteed, the import script could require a flag such as --django-accounts. Or it could even be another script entirely. So, the step wouldn't be automatic, but at least it would be an option. > inherently not secure The passwords were good enough for mailman2. If a mailman2 instance has been in production for 20 years and users aren't complaining about security, maybe it's not a show stopper. The point is to make the upgrade seamless. That means... being able to say that everyone gets to keep their user account and password. To be able to easily tell the users "Your account is still the same. Just log in. Change your password when you like." In the current context, passwords are associated with django accounts rather than mailman-core accounts. So this is about creating django users. > creating a django user is "expensive". "poor performance" I didn't follow what that means. What is expensive? What is poor performance? Creating new django accounts en masse would be a one-time operation. It doesn't matter if it's slow, or expensive, since it only happens once. And it would be optional. With the --django-accounts flag. Or another separate script. Then you can tell users "Your account is the same as before. A transparent upgrade. Just log in".

1 year, 7 months

[MM3-users] Re: MM3 shunting mails

by Mark Sapiro

On 03/17/2017 03:59 AM, Anders Nilsson wrote: > > I do have problems with some lists occasionally going into some kind of > shunt mode, where alla mails sent to them gets shunted. In the Mailman > log I get entries for each shunted email: > > Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows > were found for one_or_none() ... > File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", > line 70, in process > archiver_set = IListArchiverSet(mlist) mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list. ... > File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", > line 607, in __init__ > ListArchiver.name == archiver_name).one_or_none() and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list. The above is the last line of exists = store.query(ListArchiver).filter( ListArchiver.mailing_list == mailing_list, ListArchiver.name == archiver_name).one_or_none() which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry > File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", > line 2733, in one_or_none > "Multiple rows were found for one_or_none()") but finds more than one. > sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for > one_or_none() > Mar 17 11:54:11 2017 (6217) SHUNTING: > 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819 So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen. I have not seen this error. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 years, 1 month

[MM3-users] Re: Change digest frequency and default threshold

by Mark Sapiro

On 10/04/2018 12:19 AM, Henrik Rasmussen wrote: > > Currently I am running Mailman version 3.2.0a1 which doesn't seem to have a --periodic option. 3.2.0a1 was never an 'official' release. It could be any HEAD version between June 4, 2017 and Jul 10, 2018. The --periodic option was added April 28, 2018. > When running "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com", output is "listname.lists.example.com sent volume 11, number 4" and this increases each time, but even I do approve held mails, none are sent (according to the smtp.log and docker logs posrfix). Are there accumulated messages for the digest when you run the command?. I.e., is there a var/lists/listname.lists.example.com/digest.mmdf file with messages in it? Are there list members receiving digests? If so, there should be something in Mailman's smtp.log. > As I understand, using --sent should send a digest immediately (except when used with --dry-run). Correct,if there is one to send. > As the default Digest size threshold was 30KB, making very small digests being sent, I increased this (for test) to 5000 KB (or is it Kilo bits, as the text says "How big in Kb should a digest be before it gets sent out?"? It is Kilobytes. > Could Digest size threshold have any impact on why no digests are sent even I run "docker exec mailman-core mailman digests --send --verbose -l listname(a)lists.example.com" or is this an issue in the version I am using? The digest size threshold has no effect on whether or not a digest is sent by 'mailman digests'. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Archive import fails: "IndexError: list index out of range"

by Stephen J. Turnbull

Johannes Rohr writes: > IndexError: list index out of range That isn't the problem, it's the earlier failure, I think: > File "/usr/lib/python3.8/email/_header_value_parser.py", line 2069, > in get_msg_id > token, value = get_dot_atom_text(value) > File "/usr/lib/python3.8/email/_header_value_parser.py", line 1334, > in get_dot_atom_text > raise errors.HeaderParseError("expected atom at a start of " > email.errors.HeaderParseError: expected atom at a start of dot-atom-text > but found '@localhost>' It appears that HyperKitty is trying to find a domain name (the common use for "dot_atom_text" in mail headers in a Message-ID), but is finding "@localhost>" instead. First I would try the check_hk_import script which is provided with HyperKitty. (You may also want to use the Mailman 2.1 cleanarch script to check for unescaped 'From ' lines, or the script at https://www.msapiro.net/scripts/cleanarch2 which can do that and check for unparseable Date: headers as well.) If that fails to identify the problem, try grep -iE '^(Message-ID|In-Reply-To).*@localhost>' problem_mbox_file | wc -l to see how how often that string appears, then grep -iE '^(Message-ID|In-Reply-To).*@localhost>' problem_mbox_file | head -15 to see if you can identify the problem text.[1] The problem character before the "@" is probably "<", "@", or ".", but maybe it's one of these: ()<>[]:;@\,." (note the double quote is a disallowed character). Other ASCII punctuation are allowed in message IDs. Once we know how the message id(s) is (are) malformed, we can discuss how to deal with them. Steve Footnotes: [1] In theory we should also check References but those usually have multiple continuations, which is annoying to deal with in grep.

3 years, 3 months

[MM3-users] [Solved] PAM error (was Re: Re: OK, so I backed out completely and re-installed....)

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > 1) I set up a mailinglist (tradfp(a)forensicpath.us) for "old school" > > forensic pathologists to discuss cases. > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. Yes, I created a "lists.forensicpath.us" early on. > > > > In my previous attempt, I added > > > > hash:/opt/mailman/mm/var/data/postfix_lmtp > > > > to both virtual_mailbox_maps and virtual_alias_maps, but I haven't > > done that yet here. I thought I'd ask and make sure I should. > > > > Should that be my next step? > > You should add hash:/opt/mailman/mm/var/data/postfix_vmap to > virtual_alias_maps only. Done. I started getting the disappearing mail problem again, though none of the references to errors from the changes I made originally. After spending a few hours going over debug files, I noticed that I kept getting a pam error. The mails were getting rejected over authentication errors. It turns out it was all a permissions problem with /sbin/unix_chkpwd. Apparently the sticky bit was not set correctly on installation. Here's a discussion of the problem: https://unix.stackexchange.com/questions/422411/pam-authentication-failure-… I still don't understand why this was a problem with mailman and not with "regular" mail, but doing the "chmod u+s /sbin/unix_chkpwd" resulted in things magically working just like it's supposed to. Thanks for the help! billo

1 year, 6 months

[MM3-users] seems solved (was: Re: error changed after restart)

by Guillermo Hernandez (Oldno7)

On 7/2/21 19:33, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 7/2/21 19:04, Abhilash Raj wrote: Well... I did reinstall all mailman relationed apps with a pip install --upgrade --force-reinstall --no-deps --no-cache-dir django-mailman3 mailman mailman-hyperkitty mailmanclient Restarted thee apache24 server... Aaaaaand closed de admin session and reopened it... (just for a "what if" sensation). I can not tell what have been the solution here, but now I can access the administrative pages and attend de pending subscriptions and discard retained messages. Thanks Abhilash and Mark for your support. >> >> On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >>> On 6/2/21 21:19, Abhilash Raj wrote: >>>> >>>> On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via >>>> Mailman-users <mailman-users(a)mailman3.org> wrote: >>>>> On 6/2/21 18:08, Abhilash Raj wrote: >>>>> >>>>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) >>>>> via >>>>> Mailman-users wrote: >>>>> >>>>> I restarted de server and the error changed. Now the log >>>>> shows "KeyError: 'subscription_mode'": >>>>> >>>>> Did you also restart Mailman Core after the upgrade? >>>>> >>>>> Yes, indeed: I stopped mailman core and all the processes related. >>>>> Did the upgrades. Started all again. Find the errors in the web user >>>>> interface. Stopped all again. Looked for errors in the log. Restarted >>>>> the complete server. Found the second error that this second mail is >>>>> about to. It happens when, in the main page that shows all the lists >>>>> you click to see one of them. It seems to me that it has been >>>>> database structure changes in django that the upgrade is not aware... >>>>> but it's a very long shot from my side. >>>> `subscription_mode` was added in Mailman Core 3.3.2 and it is actually >>>> a derived atrribute and not stored in Database. Mailman's API >>>> should be >>>> returning this attribute for each Member, but for some reason it seems >>>> to me like it isn't doing that even though do have Mailman 3.3.3 >>>> running >>>> like you said. >>>> If you have Curl installed, can you send me the output of: >>>> $ curl -u <user>:<pass> >>>> http://localhost:8001/3.1/members?count=5&page=1 >>> This is the output you asked for (it's the same you can see when you >>> try >>> to interact with one list): >>> >>> /usr/local/mailman3 # curl -u XXXXXX:XXXXXX >>> http://localhost:8001/3.1/members?count=5&page=1 >>> /usr/local/mailman3 # <html> >>> <head> >>> <title>Internal Server Error</title> >>> </head> >>> <body> >>> <h1><p>Internal Server Error</p></h1> >>> >>> </body> >>> </html> >>> >>> No log entry has been produced... >> This is weird, if you have working Core, then there should be *some* >> json returned >> from the above command. Do you have the Gunicorn running? > I have the uwsgi approach running... >> What is the >> output of `ps -ef | grep mailman`? > > none > > but if I do an ps ax | grep mailman it shows > > /usr/local/mailman3 # ps ax | grep mailman > 26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master > --force -C /usr/local/mailman3/var/et > 26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner > -C /usr/local/mailman3/var/etc/mailma > 50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 50481 2 S+J 0:00.00 grep mailman > 26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > 26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini > /usr/local/mailman3/uwsgi.ini > >> Are you able to run `mailman members` command to list the members of >> a list? > > Yes. All the commands are working as expected. > >> Also, how did you actually install Mailman? > > Using pip. Here is a detailled post of how I did put all together: > > https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128 > > Thanks for your support > >> >> Abhilash. >> >>> TIA. >>> >>> >>> >>> >>>> It should ideally return an output that looks something like shown >>>> here[1]. You >>>> can put the username/password of Core's API server in the above >>>> command. >>>> [1]: >>>> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… >>>> >>>> >>>> Abhilash >>>>> I'm using sqlite as django database and mysql for mailman. >>>>> >>>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >>>>> Server Error: >>>>> /mailman3/mailman3/lists/name_and_domain.of.the.list >>>>> Traceback (most recent call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'subscription_mode' During handling of the above exception, >>>>> another exception occurred: Traceback (most recent call >>>>> last): File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >>>>> line 34, in inner response = get_response(request) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 115, in _get_response response = >>>>> self.process_exception_by_middleware(e, request) File >>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >>>>> >>>>> line 113, in _get_response response = >>>>> wrapped_callback(request, *callback_args, **callback_kwargs) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 71, in view return self.dispatch(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >>>>> line 74, in dispatch return super(MailingListView, >>>>> self).dispatch(request, *args, **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >>>>> >>>>> line 97, in dispatch return handler(request, *args, >>>>> **kwargs) File >>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >>>>> line 295, in get member.subscription_mode == File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 124, in __getattr__ self.__class__.__name__, name)) >>>>> AttributeError: 'Member' object has no attribute >>>>> 'subscription_mode' *********************** some info about >>>>> the installed versions via pip list: pip list | grep django >>>>> django-allauth 0.44.0 >>>>> django-appconf 1.0.4 >>>>> django-compressor 2.4 >>>>> django-extensions 3.1.0 >>>>> django-gravatar2 1.4.4 >>>>> django-haystack 3.0 >>>>> django-mailman3 1.3.5 >>>>> django-picklefield 3.0.1 >>>>> django-q 1.3.4 >>>>> djangorestframework 3.12.2 pip list | grep mailman >>>>> django-mailman3 1.3.5 >>>>> mailman 3.3.3 >>>>> mailman-hyperkitty 1.1.0 >>>>> mailmanclient 3.3.2 pip list | grep >>>>> postorius >>>>> postorius 1.3.4 On 6/2/21 11:12, >>>>> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >>>>> >>>>> I've just upgrade mailman 3 installation following Mr. >>>>> Sapiro advice: did a pip install --upgrade >>>>> django-mailman3 hyperkitty mailman mailmanclient >>>>> mailman-hyperkitty postorius I did a "python3 manage.py >>>>> migrate" after, too. And all seemed to run well. All the >>>>> lists showed in postorius via web, but when I try to >>>>> accesss into one of them the browser shows an error. In >>>>> the log you can see: *-*-*-*-*-*-* Traceback (most >>>>> recent >>>>> call last): File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 119, in __getattr__ return self._get(name) >>>>> File >>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >>>>> >>>>> line 86, in _get raise KeyError(key) KeyError: >>>>> 'get_requests_count' .. (And after all the traceback >>>>> lines) AttributeError: 'MailingList' object has no >>>>> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >>>>> seem to be distributing messeages well.. but I cannot >>>>> acces via web administration (django/postorius) Can >>>>> anyone point me in the right direction to solve this, >>>>> please? _______________________________________________ >>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send >>>>> an email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Mailman-users >>>>> mailing list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an >>>>> email to mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>>>> >>>>> _______________________________________________ Mailman-users mailing >>>>> list -- mailman-users(a)mailman3.org >>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >>>>> mailman-users-leave(a)mailman3.org >>>>> <mailto:mailman-users-leave@mailman3.org> >>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >>>>> >>> >>> _______________________________________________ >>> 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/ >>> > _______________________________________________ > 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/ >

5 years, 2 months

[MM3-users] Re: Question about message bounce stats

by Ruth Ivimey-Cook

Stephen, Thanks for your comments. I kinda-thought that was the state of affairs but am glad there is at least some work on it in the pipeline. If Abhilash has a starting point, and there is acceptance from others to integrate something of this sort, then I could possibly help make it happen. Ruth On 30/08/2021 16:46, Stephen J. Turnbull wrote: > Ruth Ivimey-Cook writes: > > > Does Mailman3 keep such stats, and if so is there any way to get > > access to them, even if only API? I would think it useful to do so > > (and yes, for individual outgoing messages at least for a period). > > In released versions, it currently does not, as far as I know. This > kind of thing should be available from your MTA, of course, and I > think there was a visceral opposition to keeping track of people's > behavior that way from the early days. So those are our excuses. > > However, it's something that comes up occasionally on the list as well > as as a GSoC proposal, and I think there's some code on a branch for > this that Abhilash has been threatening to release. And of course > HyperKitty now publishes stats on posting behavior. So there's really > no reason to oppose it, now it's just a matter of time to implement. > > Abhilash's participation has been kind of spotty recently (and > apologetic about it, he's not going anywhere), but hopefully he'll > pick up the thread shortly and at least confirm or deny what I wrote > here. > > Steve -- Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 8 months

[MM3-users] Re: using SSH/TLS with external MTA

by Roland Giesler

On 2024/07/29 22:45, Odhiambo Washington via Mailman-users wrote: > On Mon, Jul 29, 2024 at 10:09 PM Roland Giesler via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> On 2024/07/29 16:26, Roland Giesler via Mailman-users wrote: >>> However, the response URL doesn't not respond when I click it. It >>> opens in a browser, but the processes times out. I'm now checking why >>> that is. >> I found out why. Firefox and Brave (Chromium) have a bug in their https >> redirect functionality, so one cannot disable https redirection on any >> site at this stage. Since I don't have the https certificates in place, >> I had to use Edge to be able to visit >> >> http://192.168.161.103/accounts/confirm-email/Mg:1sYQR2:xt3_639JwJ78GW9Xhrp… >> >> Account verified. >> > The actual issue is that the verification email URL is sent with HTTPS://...... > You cannot blame a browser for NOT respecting the HTTPS and redirecting it > to HTTP. > So one has to know that their site is not secured with SSSL certs, and so > change httpS:: to http:// > I don't think Edge is the only one that does that. On my tests, I use VMs > and Brave/Chrome/Firefox to access the link. I just change HTTPs to HTTP > manually. > It's a situational awareness type of thing. My browsers do not respect it when I change https to http. I have an issue open with Firefox on this. They change the URL back to https, so the address cannot be loaded. I have since added Let'sEncrypt certificates to the nginx config, so now https is being accepted. > >

1 year, 9 months

[MM3-users] Re: Add domain to Mailman, can't create list with that new domain

by Mark Sapiro

On 10/17/24 13:41, Andy Matthews wrote: > > and then rebuilt kubernetes, I found that when I hit the API to get all lists, the list mailman(a)foobar.com existed, and was the default. I could create lists against foobar.com but could no longer create them against mydomain.com. > > So it looks like when you're initially configuring mailman you have to create your first mailing list, and whatever domain you use becomes your "primary domain". I don't know where this is documented, but could someone confirm this behavior for me so that I know that I'm on the right path? And previously you wrote: > 1. Shell into the mailman server > 2. Shell into the mailman Python environment: mailman shell > 3. Add a new mailing list. > from mailman.interfaces.domain import IDomainManager > from zope.component import getUtility > manager = getUtility(IDomainManager) > manager.add('testing.com') > show_domains() # with method from the above documentation URL > <Domain testing.com> > <Domain mydomain.com> Did you commit() after doing the above? I'm not sure how kubernetes fits in to this, but `mailman create` for a list in an unknown domain will create the domain unless -D or --no-domain is specified. See `mailman create --help`. Mailman core has no concept of `primary domain` which is why it's not documented. Are you creating lists via REST as you posted previously. If so, the domain must exist, but if you created domains as above, they should exist as long as you committed your changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Mark Sapiro

On 2/5/25 13:03, Ron / BCLUG wrote: > > I've been digging into MM3 resource usage vs MM2 and have been > wondering: are there any other runners that can be disabled, or invoked > via cron job to run every $interval then exit again? The task runner is a candidate. It only actually does anything at intervals defined by the run_tasks_every setting in the [mailman] section of mailman.cfg, default 1 hour https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.…, but it still wakes up and comes into memory every sleep_time which defaults to 1 second. If just having the runners sleep longer works for you, you can set, e.g. ``` [runner.task] sleep_time: 10m ``` to only wake up the task runner every 10 minutes. If you really want it gone, you could put ``` [runner.task] start: no ``` in mailman.cfg to prevent starting it as a persistent runner, and make a python script like: ``` #!/opt/mailman/mm/venv/bin/python from mailman.core import initialize from mailman.runners.task import TaskRunner initialize.initialize() TaskRunner('task')._do_periodic() ``` and run that periodically via cron. I'm not certain, but I think task runner is the only runner for which it's that simple. > Second question, similar topic but MM2: how to disable NNTP? (if that's > what this is doing): > > /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Put this in mm_cfg.py del QRUNNERS[QRUNNERS.index(('NewsRunner', 1))] or if you already have some modifications to the QRUNNERS list in mm_cfg.py, make the appropriate adjustment to remove the NewsRunner entry. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: deployment recommendation(?)

by Marc SCHAEFER

Hello, On Thu, Jul 18, 2024 at 09:05:28AM -0000, noc(a)iem.at wrote: > (my current Debian box running mailman3 is frozen at Debian/buster ("old-old-stable") because of mailman3). Which is no longer supported (unless you subscribed to ELTS) -- for more than two weeks now. I upgraded from Mailman2 (buster) to Mailman3 (bookworm). I took the opportunity to isolate mailman in its own container, so I really imported the lists & archives. PostgreSQL is also in another container now. The main mail server also. So far I have not seen any issue that I could not fix easily, in part with the help of this list, which is very efficient. > what are the drawbacks, limitations, advantages and benefits of the various deployment methods? Some of the enhancements (e.g. password forgotten mail only sent to actual account holders) will not be backported: only real security fixes will. I might apply some of those by hands, using diversions, as I was doing for Mailman2. I will also implement a IPS using mailman's log, looks useful since, opposite to some Perl web apps I run, it does not seem there are any built-in counters in Python/Django (e.g. max number of logins per minute, hour, day; max number of e-mails to an e-mail address per minute/hour/day, etc). Maybe I just don't know enough of Django though. It's handy eg. when people mass-create accounts, etc. The main issue I had is the enormous amount of resources (disk, database, memory) that Mailman3 uses over Mailman2 (about 10x more RAM, and the mailmanweb DB backup, zstd compressed, is 2 GBytes, where the archives were AFAIR 500M in Mailman2). With some tweaking, I could reduce the 8 GB memory footprint to 2 GB. But as you already run Mailman3 it should not be new.

1 year, 9 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by mark＠suburbia.org.au

Hi Mark, Thanks for taking the time to reply. Mark Sapiro wrote: > On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > > However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. > > Am I missing something with the expected functionality? > > A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? > Actually, it is good practice to set that to Hold for moderation for > all lists or at least all those that don't require moderator approval > for subscription to prevent a spammer from subscribing and spamming the > list. Then, upon approving a member's post you can also set the member's > moderation action to default processing and upon discarding a spammers > post, you can also set the spammer's moderation action to Discard. I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. I'm happy to do more testing, provide other information/logs as desired if that would help? cheers, Mark

1 year, 5 months

[MM3-users] Re: Cannot setup announce-only mailing list

by Abhilash Raj

On Thu, Jan 30, 2020, at 9:58 AM, Mark Sapiro wrote: > On 1/30/20 5:42 AM, Alberto Granzotto wrote: > > > > Of course, I want to keep this mailing list "read only" for members, and > > I want only selected people to post to that mailing list. > > > > Any idea on how to achieve that? > > > There is only one difference between the `Discussion` and `Announce` > list styles, and that is for an `Announce` list, the `allow_list_posts` > attribute is set to `False`. In turn, all that does is cause the > List-Post: header to be set to NO rather than the list posting address. > > There is a discussion at <https://wiki.list.org/x/4030685> of how to set > up an announce list for Mailman 2.1. Most of this translates > straightforwardly to Mailman 3, although not all the relevant settings > are exposed in Postorius. > > In short, you need to set this up manually using things like moderation > settings and custom templates for the welcome message. Mark, do you think we should make the actual announce-only style reflect these settings so folks don't have to manually set these after they create a announce-only list? I am not sure the reason behind these settings lacking for the current announce-only style. Are there situations where announce-only list would have different list setting? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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)

6 years, 2 months

[MM3-users] Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Mark, I tried doing this. I unsubscribed myself from a list, set the policy as you suggest and re-applied. I got no confirmation messages but as moderator I got the moderate message. I then tried a bogus email and saw that a message was sent to that and no moderator message to me. Would the server skip the verification message because I'm a moderator/admin? Yours, Allan On 3/28/23, 08:57, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 01:49, Allan Hansen wrote: > > There is a template, 'list:user:action:subscribe' that almost does this, but it gets sent only if the email address of the applicant is unverified. A good number of our applicants are already on our lists, so they would not get this template if we set the Subscription Policy to 'Confirm, then moderate'. > > Our Subscription Policy is currently: 'Moderate' for all lists. If you set the subscription policy to 'Confirm, then moderate' the user will receive a confirmation request based on the list:user:action:subscribe template whether or not the address is verified. -- Mark Sapiro <mark(a)msapiro.net <mailto:mark@msapiro.net>> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org <mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/ORDAIBK4JUICZADYPEPWDVV2WP5EXWEB/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

3 years, 1 month

[MM3-users] Re: Error message from monthly cronjob

by Danil Smirnov

Check this: https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… BR, Danil Smirnov On Tue, Dec 5, 2023 at 1:40 PM Johannes Rohr <johannes(a)rohr.org> wrote: > Dear all, > > Mailman3 on my system is installed in virtualenv. Each month I get the > following error message. This error does not seem to have a serious > impact on the functioning of mailman, still, what does it mean and how > do I get rid of it? > > Thanks for any hints! > > Johannes > > > > -------- Weitergeleitete Nachricht -------- > Betreff: Cron <mailman@*** /opt/mailman/venv/bin/mailman-web > runjobs > monthly > Datum: Fri, 1 Dec 2023 05:56:40 +0100 (CET) > Von: Cron Daemon <root(a)mail.rooot.de> > An: mailman@*** > > > > ERROR OCCURED IN JOB: update_and_clean_index (APP: hyperkitty) > Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.10/site-packages/django_extensions/management/commands/runjobs.py", > > line 40, in runjobs > job().execute() > File > "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/jobs/update_and_clean_index.py", > > line 37, in execute > run_with_lock(update_index, remove=True) > File > "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", > line 177, in run_with_lock > with lock: > File > "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", > line 470, in __exit__ > self.unlock() > File > "/opt/mailman/venv/lib/python3.10/site-packages/flufl/lock/_lockfile.py", > line 420, in unlock > raise NotLockedError('Already unlocked') > flufl.lock._lockfile.NotLockedError: Already unlocked > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to danil(a)smirnov.la >

2 years, 4 months

[MM3-users] Re: share directories between postfix and mailman 3

by Stephen J. Turnbull

Thomas Schachtner via Mailman-users writes: > I just saw that mailman does not start (systemctl start > mailman3.service) on my debian installation if the postfix > configuration file is not there, so I thought it might be needed by > mailman3. Mark explained this. > But maybe [the Mailman won't start issue] is not a mailman issue > but a debian-only issue... It's that Mailman 3 recreates the postmapped database files at startup. It will happen on any stock Mailman 3 + Postfix installation if postmap can't find main.cf. > Nevertheless, I just put the file on the mailman box and > everything is fine. It does not seem to be changed when starting > mailman, so maybe that's safe... At startup, Mailman reads the postfix-lmtp and postfix domains files, and (re-)creates the .db files using Postfix's postmap utility. When creating a domain or list, it adds an entry to the appropriate file, and then compiles it with postmap. Otherwise Mailman does not touch or even read those files. > I'll definitely have a look at the callout approach (currently, I > have no clue what that might be...), but I also see that exposing > LMTP to the Internet is dangerous... Exposing anything to the Internet is dangerous. Since LMTP is (usually) cleartext and unauthenticated (I'm pretty sure both Postfix and Mailman can do authenticated TLS), yes, it's riskier than say ssh. That's why I suggest firewalls and TLS connections, and then you're basically as secure as ssh. Or you can avoid exposing LMTP by having Postfix on the Mailman host, and use virtual alias or mailbox hosts with virtual_transport = lmtp:[127.0.0.1]:8024 to catch the Mailman traffic. Steve

2 years, 3 months

[MM3-users] Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:04 AM, Andrew Bernard wrote: > > Where is the Django config area for the > pip installed modules? It is this that I find obscure. The short answer is wherever you put it. If you look at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which Abhilash mentioned, you'll see what I do. Abhilash mentioned creating the virtualenv in /opt/mailman/. I actually have another level below that, /opt/mailman/mm/, but this is only for convenience to separate things as I also have directories for the git branches and for local patches, so if we are just working with /opt/mailman/, you can put your Django settings.py and settings_local.py files there. I also put various other config things there like Mailman's var/ directory Django's static/ directory mailman.cfg mailman-hyperkitty.cfg gunicorn.conf and an empty __init__.py file so Django can import settings. Then I create a /opt/mailman/bin/ directory and in that I put small bash scripts to run things. for example: opt/mailman/bin/mailman contains #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ opt/mailman/bin/django-admin contains #!/bin/bash . /opt/mailman/venv/bin/activate cd /opt/mailman/ export PYTHONPATH=/opt/mailman/ export DJANGO_SETTINGS_MODULE=settings django-admin $@ and opt/mailman/bin/gunicorn contains #!/opt/mailman/venv/bin/python import sys sys.path[0:0] = [ '/opt/mailman/', ] import os os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' import gunicorn.app.wsgiapp if __name__ == '__main__': sys.exit(gunicorn.app.wsgiapp.run()) Then I use those commands to run Mailman, Django and gunicorn. Some of this may not be directly applicable to you, but I hope it gives you the basic idea. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Re: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 9:44 AM, Massimo Zappalà wrote: > Hi everyone, > Mark thanks for the reply. > My installation was done on Debian Buster by installing the mailman3-full package > > I can't find the path you indicated: >> Mailman core in mailman/messages/ >> Hyperkitty in hyperkitty/local/ >> django-mailman3 in django-mailman3/local/ >> postorius in postorius/local/ > Maybe some packages are missing? I doubt things are missing. I can't keep track of where all the downstream packages put things, but look in /usr/lib/mailman and/or /var/lib/mailman or use tools like `find` or `locate`. >> To set language for Django (i.e. hyperkitty and postorius) see >> https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-di.... > What are the files to be edited? settings_local.py >> For Mailman core, set [mailman] default_language: in mailman.cfg. > Ok Done > >> You also need to (re)generate the .mo file which can be done with the >> generate_mo.sh script. > I can't find the script It probably isn't included in the Debian package. This is what it does. #!/bin/bash # This script generates .mo files from all the .po files in the source. echo 'Generating mo files for GNU Mailman ...' for file in `find -name 'mailman.po'` do echo $file msgfmt $file -o ${file/po/mo} -v done >> For Django, you need to generate .mo files with >> django_admin compilemessages > Where should this be written? You give the compilemessages subcommand to whatever command you use for django-admin or manage.py or whatever the Debian package calls it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 2:21 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > On 11/22/22 13:40, Hirayama, Pat wrote: > > > > There is only one uwsgi.ini file, and it is in the same directory as settings.py, > settings_local.py and wsgi.py > > > What is the content of that file? uwsgi.ini: [uwsgi] uwsgi-socket = :8000 chdir = /opt/mailman/mailman-suite/mailman-suite_project wsgi-file = /opt/mailman/mailman-suite/mailman-suite_project/wsgi.py harakiri = 60 master = true process = 4 threads = 4 uid = mail gid = mail attach-daemon = ./manage.py qcluster The referenced wsgi.py looks pretty vanilla: """ import os # import sys # import site # For some unknown reason, sometimes mod_wsgi fails to set the python paths to # the virtualenv, with the 'python-path' option. You can do it here too. # # # Remember original sys.path. # prev_sys_path = list(sys.path) # # Add here, for the settings module # site.addsitedir(os.path.abspath(os.path.dirname(__file__))) # # Add the virtualenv # venv = os.path.join(os.path.abspath(os.path.dirname(__file__)), # '..', 'lib', 'python2.6', 'site-packages') # site.addsitedir(venv) # # Reorder sys.path so new directories at the front. # new_sys_path = [] # for item in list(sys.path): # if item not in prev_sys_path: # new_sys_path.append(item) # sys.path.remove(item) # sys.path[:0] = new_sys_path from django.core.wsgi import get_wsgi_application os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") application = get_wsgi_application() > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org Thanks! -p Pat Hirayama Pronouns: he/him/his Systems Engineer IT | Systems Engineering Fred Hutchinson Cancer Center O 206.667.4856 phirayam(a)fredhutch.org

3 years, 5 months

[MM3-users] Re: mailman.log file owned by 'list' user

by Mark Sapiro

On 1/7/23 14:14, Mike Wertheim wrote: > I'm on Debian 11, trying to troubleshoot an installation of Mailman 3.3.3 > that was done by someone else. > > Mailman is running as a non-privileged (non-root) user called 'xyz'. On the > day that Mailman was installed, that non-privileged 'xyz' user was able to > execute mailman commands successfully to create, view and modify lists. The Debian package uses 'list' as the Mailman User. Whoever did the installation apparently tried to change that to 'xyz' and did an incomplete job. > A couple of days later, when the 'xyz' user tried running those same > mailman commands, they failed with this error: PermissionError: [Errno 13] > Permission denied: '/var/log/mailman3/mailman.log' > > Doing "ls -l" on the file /var/log/mailman3/mailman.log showed this: > -rw-r----- 1 list list 0 Jan 6 00:00 /var/log/mailman3/mailman.log > > When I did a 'ps' command, I saw that all of the mailman processes are > running as user 'xyz'. No processes were running as the user 'list'. > > It seems that some process is rotating the mailman.log file at midnight, > and the newly-created mailman.log is being owned by user 'list'. > > Can anyone explain why this is happening, and how to fix it? It is happening because the logrotate script (maybe /etc/logrotate.d/mailman3) sets the user to 'list'. change that to 'xyz'. Also sudo chown -R xyz:xyz /var/log/mailman3/ and wait for the next issue to arise. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

[MM3-users] Re: Apache shows No Lists

by ceo＠sartrack.nz

Thanks; There has never been a 'Mailman' user. I do have a www-data user (all Apache2 data' and there is a 'list' user. I may have run the import fuction as root, but I then used chown() to set the directory tree /var/lib/mailman3/* to user 'list'. So I upgraded Debian 10 to Debian 11. This also upgraded Apache2 I assume, but I kept the original (single) config file. I then installed the whole Mailman3 package with 'apt'. I may also have installed additional missing bits afterwards, as I think it was not complete. I initially tried to use MariaDB but the installation failed completly because it never asked for the MariaDB root password, and as a result of that everyting else failed too. Then I un-installed 5 times, and then I finally went for the 'default' database system. I then edited the file with the recommended settings for Mailman3: Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> So clearly Apache2 manages to access the data supplied by Postorius because it sees the lists (at least the empty ones). -What user should the whole system running under: 'list'? of 'www-data'? - Is there anything else I should tell Apache2? Now I tried to use "django-admin createsuperuser". This also fails because of this error: ImportError: cannot import name 'force_text' from 'django.utils.encoding' (/usr/local/lib/python3.9/dist-packages/django/utils/encoding.py) And I cannot find where this 'force_text' is called from. It must be removed as it is too old.

2 years, 11 months

[MM3-users] Re: Error: ConnectionRefusedError at /accounts/login/

by Mark Sapiro

On 2/27/25 05:44, Kim Sunggun via Mailman-users wrote: > Hello, > > /opt/mailman/venv/lib/python3.9/site-packages/django/conf/global_settings.py:EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" > /opt/mailman/venv/lib/python3.9/site-packages/mailman_web/settings/base.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' OK. > I installed mailman3 in rhel 9 based on https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… > I set up Postfix as the MTA. I added the code as mentioned in the document. > > unknown_local_recipient_reject_code = 550 > owner_request_special = no > > transport_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > local_recipient_maps = > hash:/opt/mailman/mm/var/data/postfix_lmtp > relay_domains = > hash:/opt/mailman/mm/var/data/postfix_domains These are good but not relevant to your issue. They affect delivery of incoming mail to Mailman. Your issue is with outgoing mail from Django. There are various settings that affect this SMTP connection as described at https://docs.djangoproject.com/en/5.1/topics/email/#smtp-backend The defaults are EMAIL_HOST = "localhost" EMAIL_PORT = 25 and for the optional settings EMAIL_HOST_USER = "" EMAIL_HOST_PASSWORD = "" EMAIL_USE_TLS = False EMAIL_USE_SSL = False EMAIL_SSL_CERTFILE = None EMAIL_SSL_KEYFILE = None Have you set any of those to other than default in your Django settings? If not, what do you get if you run this python snippet as the Mailman user ``` import smtplib connection = smtplib.SMTP(host='localhost', port=25) ``` If you have, you can specify them as args to smtplib.SMTP, e.g. ``` connection = smtplib.SMTP(host='localhost', port=25, username='...', password='...') ``` or if EMAIL_USE_SSL is True, ``` connection = smtplib.SMTP_SSL(host='localhost', port=25, username='...', password='...', ssl_keyfile='...', ssl_certfile='...') ``` See https://github.com/django/django/blob/ea1e3703bee28bfbe4f32ceb39ad31763353b… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 2 months

[MM3-users] Re: list footer questions

by Mark Sapiro

On 6/7/20 9:40 AM, kelly.close(a)lrewater.com wrote: > > So I have a template file here: > /var/lib/mailman3/templates/lists/f2p2-test.udfcd-lists.org/en/list:member:regular:footer.txt > > I had to create everything below templates/ as that folder was empty on install. I made sure what I created had the same permissions as the templates folder. I'm not sure what else to do. Is there a configuration file somewhere perhaps the identifies the path of the templates folder and maybe I need to adjust it? There are two things. One is the location of the `templates/` directory. That is located in `$var_dir` and the value of that depends on the settings for ``` [mailman] layout: ``` and ``` [paths.<layout_value>] var_dir: ``` in mailman.cfg. I'm not certain, but I think `/var/lib/mailman3/` is correct for the Debian/Ubuntu package. The other thing that affects this is the value of the URI for the template in the database. This is somewhat tricky. The docs are at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but there isn't an example of retrieving URIs via REST. I.e. something like ``` curl -urestadmin:restpass http://localhost:8001/3.1/lists/f2p2-test.udfcd-lists.org/uris ``` should work, but returns a 404 when I try it on one of my lists that has a URI. I look in mailman's database with a query like ``` select name, context, uri from template; ``` What you are looking for is a row with `name` = `list:member:regular:footer` and `context` = `f2p2-test.udfcd-lists.org`. If there is one and it has a uri other than `mailman:///$listname/$language/list:member:regular:footer.txt` then Mailman will look there for the template. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 10 months

[MM3-users] Re: mailman3 not working for mailman21 lists

by Stephen J. Turnbull

Diana von Bidder writes: > I have several entries in /var/lib/mailman3/queue/shunt/ with Aug 21 > timestamps, Evidence! Preserve it! You can look at those using "mailman qfile <file>", where the specification for <file> needs to be a regular path. the 'qfile' command does not assume a prefix of /var/lib/mailman3/queue/, unfortunately. Look for non-ASCII characters in headers, very long lines, a line with no indentation that doesn't match the "name: content" pattern that header follow (indented lines are considered to be "logically" part of the previous line so that's not a problem), and empty lines in the header. (There is always an empty line between the message header and the message body, but an empty line in the middle of the header will often cause problems.) Check the size of the files; probably all these messages were short test messages and it won't matter but in real life you might have a huge attachment which I think would be printed out. Start with the short ones. :-) > and several entries in /var/lib/mailman3/queue/shunt/ with > current timestamp (i.e. everytime I ls -l there is a new timestamp with > the current time). I'm not sure what's going on with that. The point of the shunt queue is that Mailman doesn't know what to do and it's putting the messages there to wait for human intervention. So timestamps shouldn't be changing. > My output looks exactly the same. Good! If you want you can send me one of those entries in shunt (assuming you're satisfied with my assurance of privacy of any identifying information such as IP addresses, domain names, and mailbox names). Steve

3 years, 8 months

[MM3-users] Re: Enable delivery

by Mark Sapiro

On 12/10/24 10:43, Hirayama, Pat wrote: > Apologies, I should've said my "Mailman 3" server, not listserv. > > MTA logs do not show messages being sent to the member(s) in question, even though other members are being sent messages. Nothing out of the mailman server, and nothing received by our outbound Postfix MTAs. > > As for the CLI commands, I keep getting Attribute Error when I try them, like: > > /opt/mailman # mailman shell -l listname(a)mailman.tld > 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. > The variable 'm' is the listname(a)mailman.tld mailing list >>>> from mailman.core.constants import system_preferences >>>> mbr = m.members.get_member('user(a)domain.com.') >>>> print(mbr.delivery_status) > Traceback (most recent call last): > File "<console>", line 1, in <module> > AttributeError: 'NoneType' object has no attribute 'delivery_status' Are you literally typing mbr = m.members.get_member('user(a)domain.com.') That needs to be an actual list member's email without a trailing period. The fact that mbr is None means whatever you provided is not a member of the listname(a)mailman.tld list. Curious that the member(s) in question are not amongst the recipients delivered to the MTA even though >> when I run: >> >> mailman members --nomail any listname@listserv >> >> Nothing is returned. This should only happen if the members are digest members (are they) or are directly addressed in To: or Cc: of the post. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] HyperKitty archiver <h1>Server Error (500</h1>

by Daniel Erlendson

Hello all, I'm getting the following in the logs in our MM server: Nov 01 14:00:17 2021 (26843) HyperKitty failure on http://localhost/mailman3/hyperkitty/api/mailman/archive: <h1>Server Error (500)</h1> (500) Nov 01 14:00:17 2021 (26843) Exception in the HyperKitty archiver: <h1>Server Error (500)</h1> Nov 01 14:00:17 2021 (26843) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ValueError: <h1>Server Error (500)</h1> which is mirrored in the mailman-web.log with this 21:57:07 [Q] INFO Enqueued 1962530 21:57:08 [Q] INFO Process-1:36 processing [sender_mailman_id] 21:57:08 [Q] INFO Processed [sender_mailman_id] ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): plus a bunch of python errors and this: ValueError: A string literal cannot contain NUL (0x00) characters. ERROR 2021-11-01 21:57:07,969 17847 django.request Internal Server Error: /mailman3/hyperkitty/api/mailman/archive Traceback (most recent call last): We are on v3.1 on Ubuntu 18.04. I do have a project beginning to move to Ubuntu 20.04 eventually. For now, I'm struggling to find the resolution to this error. I've looked at the site here, did a rebuild on the whoosh index, I've found and tested the suggestions to add a localhost non-https in apache for HyperKitty, I've edited HyperKitty to be https rather than HTTP, none of these settings / changes seem to resolve the issue. Oddly for all intents and purposes, the server appears to run fine, the archive might be a bit slow but it doesn't seem to have issues other than the constant errors coming into the admin emails. Happy to post any configs or detail anything, appreciate any replies. Respectfully,

4 years, 5 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 12/02/19 11:25 AM, worik wrote: > Friends > > On a fresh install (docker) on a fresh VPS I am getting all Mailman > messages to Gmail addresses bouncing telling me I am sending too many > messages. Has anybody else have this problem? > > I am getting the following error in mail.log: "Our system has detected > an unusual rate of 550-5.7.1 unsolicited mail originating from your IP > address. To protect our 550-5.7.1 users from spam, mail sent from your > IP address has been blocked. 550-5.7.1 Please visit 550-5.7.1 > https://support.google.com/mail/?p=UnsolicitedIPError to review our 550 > 5.7.1 Bulk Email Senders Guidelines. l26si395949wme.8 - gsmtp" > > I have been to the URL mentioned and exhausted my options there. > > Worik > Well. Golly. I complained to Google, and heard nothing back. But with no changes on my end they have stopped bouncing my emails. Now they are just marked as spam. I can live with that. Very frustrated with google's levels of service. What a pain! Thank you Brian Carpenter, who may well have been right about "warming up the IP". What ever that might mean. I have not read that RFC, but I have a lot to learn. Thank you Mark Sapiro, for your patience. Thank you every body for the obviously hard work creating this system. I have a long way to go until I know how to use it properly, but I am no longer stopped at the google cliff. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand) I have a lot of onion pie, that explains the aroma

7 years, 2 months

[MM3-users] Hyperkitty archive: date format in thread overview of list does not honor DATETIME_FORMAT of settings.py

by Christian Schneider

Dear mailman community, with the help of you I was able to set up a new mailman3 environment (a big THANK YOU!!! :-)): OS: Ubuntu 24.04-LTS mailman: GNU Mailman 3.3.10 (Tom Sawyer) Python: 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] Method: Python Virtual Environment Installation My configuration files are placed in the following directory: /etc/mailman3 - gunicorn.py - mailman.cfg - settings.py The environment is up and running: A list for testing is set up and mails are transfered (and archived) using the test-list - successfully... :-) Looking at the thread overview of the list (in Hyperkitty archives) I realized that the shown date format is unusual (for Germany), like: Do Mai 22, 3:57 nachm. (meaning: Thu May 22, 3:57 p.m.) I would prefer a format like: 22-05-2025 15:57:24 So I tried to reconfigure this setting in settings.py according to this URL: https://docs.mailman3.org/en/latest/config-web.html#configure-postorius-hyp… In settings.py I set DATETIME_FORMAT to 'd-m-Y H:i:s' but the format did not change. (After changing settings.py I initiated a restart of mailman3 and mailmanweb) I also set USE_L10N to False as suggested in Django-Docs: https://docs.djangoproject.com/en/3.1/ref/settings/#std:setting-DATETIME_FO… My /etc/mailman3/settings.py is parsed - as far as I can say because changing USE_I18N to false (in /etc/mailman3/settings.py) switches date to English as this is my locales-setting on Ubuntu... Nevertheless the format stays the same (in this case: Thu May 22, 3:57 p.m.) How can I adjust the date format (in the discussion boxes) at the thread overview page (url: https://my-domain.de/archives/list/test-list@lists.my-domain.de/)? Any hint is appreciated! Thank you very much and kind regards Christian

11 months, 1 week

[MM3-users] Re: Installing mailman 3

by Rafael Mora

I tested with python3 and got this: (env) [mailman@localhost mailman-suite_project]$ python3 manage.py migrate Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 363, in execute_from_command_line utility.execute() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/core/management/__init__.py", line 337, in execute django.setup() File "/var/lib/mailman/env/lib/python3.6/site-packages/django/__init__.py", line 27, in setup apps.populate(settings.INSTALLED_APPS) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/registry.py", line 85, in populate app_config = AppConfig.create(entry) File "/var/lib/mailman/env/lib/python3.6/site-packages/django/apps/config.py", line 94, in create module = import_module(entry) File "/usr/local/lib/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 978, in _gcd_import File "<frozen importlib._bootstrap>", line 961, in _find_and_load File "<frozen importlib._bootstrap>", line 948, in _find_and_load_unlocked ModuleNotFoundError: No module named 'hyperkitty' Why does it say that hyperkitty is not installed? El vie., 21 jul. 2017 a las 14:37, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 07/21/2017 12:33 PM, Rafael Mora wrote: > > > > I'm getting an error doing: > > > > (env) [mailman@localhost mailman-suite_project]$ python2 manage.py > migrate > > Traceback (most recent call last): > > File "manage.py", line 8, in <module> > > from django.core.management import execute_from_command_line > > ImportError: No module named django.core.management > > > Have you installed Django in your 'env' virtualenv? > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: Mailman3 on FreeBSD

by John Poltorak

I'm making progress, albeit slowly. Any progress I make I will post on the FreeBSD forums... https://forums.freebsd.org/threads/61050/ On Sun, Aug 13, 2017 at 7:14 PM, Barry Warsaw <barry(a)list.org> wrote: > Thanks for the reference John, > > > On Aug 13, 2017, at 06:52, John Poltorak <karotlopj(a)gmail.com> wrote: > > > > Regarding location of mailman.cfg...FreeBSD adopt a strict directory > > hierachy > > > > https://www.freebsd.org/cgi/man.cgi?hier(7) > > > > Anything installed outside the base OS belongs in /usr/local > > I looked over that page. Does this mean that even if you were to install > Mailman 3 via the FreeBSD package manager (i.e. ports), you’d still want > mailman.cfg in /usr/local/etc instead of /etc? That would differ from most > Linux distributions where package manager installed packages would have > their configuration files in /etc, and where “third party” packages would > have them in /usr/local/etc. > > > I guess that issue is something for the FreeBSD porters of Mailman3… > > I think so. I think for now I don’t want to support > /usr/local/etc/mailman.cfg out of the box, although I’m open to persuasion > if there are some more generic use cases. OTOH, the internal function that > calculates the search paths could be refactored to make it easy for > distributions to carry small deltas to add that as a search path (it really > wouldn’t be that hard to do now, but it’s a little icky). Of course, you > can’t add a configuration file to find a configuration file. :) > > Cheers, > -Barry > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

8 years, 8 months

[MM3-users] FILTER_VHOST for 3.2.1 not working after install

by Élodie BOSSIER

Hello, I'm using Mailman 2.1.29 since several years and all was perfect except the virtual_host which was "faked" : it was possible to have several mailing list by domain linked to their own domain and url but not same mailing list name for multiple domains. Example (with lighttpd) : - at http://ml.bossier.fr/listinfo we can see ONLY mailing list "test2@", "Test3@" and "Test4@" for @ml.bossier.fr - and at http://ml.franceserv.fr/listinfo we can see ONLY mailing list "bar@", "newsletter@" and "test@" for @ml.franceserv.fr Each url_host have their "own" mailing list. It's the main reason I would like migrate and use Mailman 3 and be able to have "test(a)ml.bossier.fr" and "test(a)ml.franceserv.fr". So I installed Mailman 3.2.1 and I have set "FILTER_VHOST = True" into /etc/mailman3/mailman-web.py then : mailman create --language fr --owner admin(a)franceserv.fr --domain test(a)ml.franceserv.fr mailman create --language fr --owner admin(a)franceserv.fr --domain test2(a)ml.bossier.fr And I have this result (with nginx as front) : - at http://ml.franceserv.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" - and at http://ml.bossier.fr:81/postorius/lists/ we can see mailing list "test(a)ml.franceserv.fr and test2(a)ml.bossier.fr" (same result) And it's my problem, I would like be able to see the linked mailing list to their own url. I would like with Mailman 3.2.1 see into : - "example1.com/postorius/lists/" only the mailing list related to example1, - and into "example2.com/postorius/lists/" only the mailing list related to example2 as Mailman 2.1.x do it. I don't understand what I missed, could you help me please ? Best regards, Élodie PS. Sorry for my english language I'm french.

6 years, 3 months

[MM3-users] Re: Error -- postorius Un-handled exception

by Odhiambo Washington

On Thu, Apr 11, 2024 at 11:00 PM Ron / BCLUG <admin(a)bclug.ca> wrote: > Mark Sapiro wrote on 2024-04-10 14:09: > > > I suspect you are not starting the services with your venv active. > > What's in your mailman3.service and mailman3-web.service files? > > Thanks for the pointer! > > I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` > somehow. > > > I changed that to match the docs, did the `systemctl daemon-reload`, > etc. but still had similar problems. > > > I went through all my config files carefully, I wiped the static folder > completely and rebuilt it, and I finally have the last piece of the > puzzle in place and my web interface is working! > > I'm not sure which change actually fixed the issue though. > > > (When looking at "Available lists" my header has "example.com" in the > top-left corner?!?) > See also this: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… But read it as "example.com", not example.org :-) I think I need to backup what I have and do a clean re-install so I have > a better grasp of what's going on with all these components. > Way to go! Before I got MM3 working on the sites that I manage, it took me lots of installs and wipes until I could figure out what's going on. I was literally being hand-held by the good developers. -- 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]

2 years

[MM3-users] Re: Archive not working - Reg.

by Stephen J. Turnbull

Nirmal J via Mailman-users writes: > While I am opening mailman.log.1 It is displaying this. Everything up to this ACCEPT is irrelevant: > Oct 28 15:46:33 2025 (678430) ACCEPT: <176164659325.678449.14176354478536014912(a)list1.iitm.ac.in> Looks like the Mailman configuration is correct, at least up to the point of contacting the HyperKitty archiving code: > Oct 28 15:46:34 2025 (678434) Exception in "hyperkitty" archiver But your TLS is misconfigured (probably not configured at all?): > ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:992) (Haven't we been here before?) The most likely problem is that you did not configure the base_url in mailman-hyperkitty.cfg. If your SSL configuration is correct, then changing that line to something like base_url: https://list1.iitm.ac.in/archives/ should do the trick (be careful, pretty sure it will be similar but the host part must match the SSL certificate used by the host). In the most common installation, Mailman and HyperKitty are on the same host. If so, there's no point in using SSL. At least I cannot think of a scenario where an adversary can tap a local connection but doesn't have a dozen other ways to steal the same information. So if that is the case, an alternative to fixing the SSL configuration is to have a virtual host listening on port 80 that doesn't accept any requests except those reverse proxied to HyperKitty. Or even just going directly to http://localhost:8000/archive should work. (This has the possible disadvantage that accesses to HyperKitty from Mailman won't be logged by your webserver, but they will still normally be logged by HyperKitty itself I think.) -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

[MM3-users] Re: user self registration

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > Something strange is now going on. Now when a user tries to > subscribe themself and they get the ' Please check your inbox for > further instructions' no such email arrives in their mailbox. Please check your mail server and Mailman logs to see whether mail is being sent. The most relevant Mailman log is smtp.log (or possibly virgin.log, but almost nobody uses the latter any more). Also check that all the runners are running. > Relatedly, if I as an admin try adding someone to a list via the > Mass Subscribe, they are not added to the list, but they do appear > in the listing of all Users. I don't see how the setting ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ could have either of the effects above. It effectively sets a flag that is used internally by Django, but nowhere in the mailmanweb code. That is all it does. But once Django hands off the subscription request to the Postorius code, Django is no longer involved. So I am quite sure that the ACCOUNT_ADAPTER change did not cause either issue. I seem to recall that you have tried a number of things to disable the sign-in. Please review all changes made in the last couple of months to mailman.cfg, settings.py, and your mail server to see if any of those have been left in place, or whether apparently unrelated changes were made. Also, are you sure these problems started immediately after making the change to ACCOUNT_ADAPTER? If you can determine when these issues started accurately, it may help in localizing the issue to a particular change or set of changes. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months, 2 weeks

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Mark Sapiro

On 5/23/22 11:11, Darren Hart via Mailman-users wrote: > When attempting to visit the hyperkitty archives list overview for one of my two lists: > > Https://lists.mydomain.com/hyperkitty/list/mylist@mydomain.com/ > > The area where the threads should appear shows the loading spinner (but the activity summary bar chart and most active posters post counts do eventually load). > > The following appears in /var/log/mailman3/web/mailman-web.log: > > > ERROR 2022-05-23 17:50:50,201 1694 django.request Internal Server Error: /hyperkitty/list/mylist(a)mydomain.com/posted-to > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 406, in get > raise self.model.DoesNotExist( > hyperkitty.models.thread.Thread.DoesNotExist: Thread matching query does not exist. > > Viewing “All Threads” or Threads by month (any month) work as expected, displaying the appropriate threads. > > The archives for this list worked previously. There was an incident that resulted in DNS not working and the archiver failing for a few days. The mail that came in during that time does show up in the other views. > > The hyper kitty archives for a second list on this Mailman3 instance is working correctly. > > How can I fix this view of the archives? Or how can I get more information on what might be failing? I'm not sure if this will help, but try running your django management command with arguments `runjob recent_threads_cache`. Note that this will be run daily if you are running the Cron Jobs for Mailman Web. See https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=perio… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Which folder should I share between pods with kubernetees persistentVolumeClaim ?

by antoine.depoisier＠ikmail.com

I use mailman with kubernetees, and I have four pods. I currently use persistentVolumeClaim for two folders in the mailman configuration "cache" and "messages". I share these folders, as mailman needs to be consistent for these two folders, but I'm wondering if I should share other folders as well, like locks and such. There are all the folders in mailman archives cache data etc lists locks logs master.pid messages queue templates I ask this question because I often have a problem when creating a mailing list. I think I have a problem with the locks, but I'm not sure if the problem is due to the fact that the locks folder is not shared. If you want more details, here's the trace I sometimes get, when someone tries to create a mailing list: File "falcon/app.py", line 365, in falcon.app.App.__call__ File "/usr/lib/python3.12/site-packages/mailman/rest/lists.py", line 322, in on_post mlist = create_list(**validator(request)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/mailman/app/lifecycle.py", line 102, in create_list call_name(config.mta.incoming).create(mlist) File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 96, in create self.regenerate() File "/usr/lib/python3.12/site-packages/mailman/mta/postfix.py", line 106, in regenerate with Lock(lock_file): ^^^^^^^^^^^^^^^ File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 467, in __exit__ self.unlock() File "/usr/lib/python3.12/site-packages/flufl/lock/_lockfile.py", line 417, in unlock raise NotLockedError('Already unlocked') flufl.lock._lockfile.NotLockedError: Already unlocked When I check the lock folder, I have these two files, and I'm wondering if I should delete these two files : -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck -rw-rw---- 2 mailman nogroup 97 Feb 6 2025 master.lck|mailman-core-deployment-5f59557b66-bkkf4|16|4268829230172994873 Do you have any answer for me ?

1 year, 2 months

[MM3-users] Re: Importing mbox files into archive defect with lines with From

by Mark Sapiro

On 6/21/19 12:57 AM, andrew.bernard(a)gmail.com wrote: > A curious problem, but seems to be well defined. I am importing mbox format files with 25 years worth of archives in 250 files from a Listserv list into hyperkitty. All is going swimmingly, except I get lots of partial emails with sender of None put into the current month, with text that has clearly been truncated. As I look at each one, I see that the line in the imported text is immediately after a line starting with 'From'. Clearly, 'From:' is an RCS-82 header, but 'From ' is not, and yet there is much evidence here that this is messing up the import. > > Is this a known bug? If not, how do I report it? As other responses in this thread have pointed out, it is a well known issue with mbox format in that lines beginning with 'From ' are message separators. There is a (Python 2) script at <https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/bin/cle…> that will process a mbox and prefix with '>' all lines beginning with 'From ' that don't look like real 'From ' lines or which aren't immediately followed by a line that looks like a valid header line. It isn't perfect because it won't handle a message that contains in it's body a copy of another message containing a Unix From_ line, but it can helm with most unescaped From_ lines. If you want to use that script, replace lines 55 and 56 import paths from Mailman.i18n import C_ with def C_(s): return s -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 10 months

[MM3-users] Performance of member listing [was: How to remove a nonmember...]

by Stephen J. Turnbull

skenny(a)scss.tcd.ie writes: > Actually, I came across another thread where you suggested > increasing the "graceful_timeout" in gunicorn.cfg. In fact this > didn't work for me, but I followed your reference to the > documentation Which documentation? An exact reference would be nice, but I'm not even sure if you're talking about Mailman or gunicorn docs here -- whatever you have off the top of your head would help! I'd like to find a place to put this in the Mailman docs. > and tried increasing just "timeout" instead - and that worked! > > It's pretty slow, but I can now get all my (very long) mailing list > members via the REST API, which is great. Do you mind saying just how long your very long list is (ie, the number of subscribers)? It's useful to us to have some idea of the scales at which people are operating (and having performance issues :-/ ). (The biggest list I run in Mailman 3 is 17, so I'm not much help with that.) I'm not happy about your "pretty slow" remark. We've had Mailman 2 lists get seriously big (seven digits worth of subscribers, I think). If we can improve the performance of listing, or help you to improve it by using a different API, it would be good for you, and help with scaling Mailman 3. I forget the context, but let me confirm: you're using the REST interface to get the member list, right? The main point: I'm wondering if you might not get better performance by getting using the paginated interface, and assembling the list at the receiving end instead of trying to get it all at once. Steve

6 years

[MM3-users] Re: integrate subscribe form in Website -> CSRF-token

by Mark Sapiro

On 6/21/21 11:58 AM, Jens Günther wrote: > > We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): > > <form method="POST" > action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> > > <input name="email" value="" type="text"><br> > <input name="email-button" value="Anmelden" type="submit"> > </form> > > When I now enter a mailaddress, the quoted error occurs. This is Django protecting against CSRF. You need to GET the for with the (hidden) CSRF token before you can POST it. > Checking another answer directly to me, there seems to be another hint :-) > > > I believe you are attempting to use the MM Core API via http > GET/POST, rather than via Postorius? That you have tried and get the > CSRF error reported? > > > > Typically this is because you need to add a token to the request to > indicate to the MM Core that your request isn't a forgery. Typically > this token is requested from Core and then presented with subsequent > requests. Have you tried this? > > > > Therefor it is needed to send also a token!? Or use another URL, not > postorius in order to subscribe!? How can I submit such a token? To submit the Token, you need to first GET the form which will have the token. Then you can include it in the POST data. This is not a satisfactory solution for your case. As hinted above, you need to use the REST API. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- 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

[MM3-users] Single Click Unsubscribe

by Stephen J. Turnbull

J D writes: > However, Google has recently announced that they will be enforcing > one-click unsubscribe for bulk senders: > https://techcrunch.com/2023/10/03/gmail-to-enforce-harsher-rules-in-2024-to… > > Thoughts? One-click unsubscribe for bulk senders of *commercial* email. For those of you who are using Mailman to send bulk commercial email, I guess you have to worry whether they're going to apply this to your advertising and product announcement lists only, in which case I guess you end up with a higher than current unsubscribe rate (but if you're smart you'll figure out how to use that expression of disinterest to advantage! ;-) Or if they are going to apply it to user discussion forums as well, in which case you have to think about the issue of user-on-user mischief (eg, redact OTKs or whole footers in quoted material). I'm not sure if we should be in the business of providing those features (they're kinda getting into content and business model), but I'd at least consider adding them to contrib, dunno about the other devs tho. For one thing, we already provide the OTK infrastructure for email verification. The rest is a nothingburger too. It looks like they're just saying they're going to enforce best practices, like publishing SPF and DKIM policies and signing your outgoing mail with valid keys. Mailman users should already be doing those things, because a lot of sites already bounce or discard unsigned email without valid signatures. It's the rules that Google does not announce, especially when they have publicly announced the opposite, that are a big threat. Personally I think the company has long since gone over to the Dark Side of the Force, and I'm rooting for the FTC. Steve

2 years, 6 months

[MM3-users] Slow performance when listing members on Postorius

by Alan So

We are about to upgrade to Mailman core 3.3.9 and Postorius 1.3.10. We notice that for setup with large number of members, the performance is much slower when listing members on web (Postorius). Further troubleshooting show that there are quite a number of API calls which do not appear in Mailman core 3.3.5 and Postorius 1.3.6 when we list members. [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/33a6266d0a04472c8d5d6c78869a964c/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/7a18b7cb90a34ac98881a3f01b5488d1/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/61c6c3e2aaf443babd3bd191519b0424/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" [17/Apr/2024:14:12:22 +0800] "GET /3.1/members/8dd681165b8c436fac6793cae1ed2c27/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5" Further tests showing that each database query using "_member_id" in table member can take as much as 0.3 to 0.5 seconds for some large installations. The default 25 members per page mean that it will take at least 7.5 to 12.5 seconds. Changing to 200 members per page will take even longer time. We wonder whether "_member_id" should be indexed just like most other id in the database mailman_core in order to solve the issue. Or are there any other workarounds? +----------------------+--------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------------------+--------------+------+-----+---------+----------------+ | id | int(11) | NO | PRI | NULL | auto_increment | | _member_id | char(32) | YES | | NULL | | | role | int(11) | YES | MUL | NULL | | | list_id | varchar(255) | YES | MUL | NULL | | | moderation_action | int(11) | YES | | NULL | | | address_id | int(11) | YES | MUL | NULL | | | preferences_id | int(11) | YES | MUL | NULL | | | user_id | int(11) | YES | MUL | NULL | | | bounce_score | int(11) | YES | | NULL | | | last_bounce_received | datetime | YES | | NULL | | | last_warning_sent | datetime | YES | | NULL | | | total_warnings_sent | int(11) | YES | | NULL | | +----------------------+--------------+------+-----+---------+----------------+

2 years

[MM3-users] Re: Error after HyperKitty 1.3.x upgrade

by Florian Schulze

On 30 Jun 2020, at 8:22, Florian Schulze wrote: > On 29 Jun 2020, at 23:40, Mark Sapiro wrote: > >> On 6/29/20 1:38 AM, Florian Schulze wrote: >>> Hi! >>> >>> After upgrading to HyperKitty 1.3.x I get the following error for >>> qcluster: >>> >>> File ".../lib/python3.7/site-packages/django_q/cluster.py", line >>> 300, >>> in pusher >>> task = SignedPackage.loads(task[1]) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 31, >>> in loads >>> serializer=PickleSerializer) >>> File ".../lib/python3.7/site-packages/django_q/core_signing.py", >>> line >>> 38, in loads >>> return serializer().loads(data) >>> File ".../lib/python3.7/site-packages/django_q/signing.py", line >>> 44, >>> in loads >>> return pickle.loads(data) >>> AttributeError: Can't get attribute 'process_task_result' on <module >>> 'hyperkitty.tasks' from >>> '.../lib/python3.7/site-packages/hyperkitty/tasks.py'> >>> >>> How do I recover from that? It seems like there are still persisted >>> tasks in the qcluster queue using the old code from 1.2.x with the >>> old >>> locking implementation. >> >> Have you stopped ans started qcluster since upgrading? > > Yes > >> Are you running the Django periodic jobs? > > They were disabled because of the errors (someone else did the > upgrade). I have enabled them again and will watch it and report back. The cronjobs seem to work fine, no errors so far. The queue doesn't seem to change at all. In "qmonitor" there is nothing listed and the statusline remains the same at ORM default Queued 303(118) Success 100 Failures 0 Regards, Florian Schulze

5 years, 9 months

[MM3-users] Re: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://gitlab.com/mailman/mailman/-/issues/473>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://gitlab.com/mailman/mailman/-/issues/659>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Wed, 19 Oct 2022 23:38:05 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > Judging from the traceback, Onyeibo Oku's > /opt/mailman/venv/bin/mailman is quite different from mine which is > just ``` > #!/opt/mailman/venv/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: > 'mailman==3.3.5','console_scripts','mailman' __requires__ = > 'mailman==3.3.5' import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( > load_entry_point('mailman==3.3.5', 'console_scripts', > 'mailman')() ) > ``` > What is yours? and can you start mailman as the mailman user with > ``` > /opt/mailman/venv/bin/mailman start > ``` > without activating the venv? > True mine is different: **************** /opt/mailman/venv/bin/mailman ************ #!/opt/mailman/venv/bin/python # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.5','console_scripts','mailman' import re import sys # for compatibility with easy_install; see #2198 __requires__ = 'mailman==3.3.5' try: from importlib.metadata import distribution except ImportError: try: from importlib_metadata import distribution except ImportError: from pkg_resources import load_entry_point def importlib_load_entry_point(spec, group, name): dist_name, _, _ = spec.partition('==') matches = ( entry_point for entry_point in distribution(dist_name).entry_points if entry_point.group == group and entry_point.name == name ) return next(matches).load() globals().setdefault('load_entry_point', importlib_load_entry_point) if __name__ == '__main__': sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) sys.exit(load_entry_point('mailman==3.3.5', 'console_scripts', 'mailman')()) *************** end of /opt/mailman/venv/bin/mailman *********** I have tried setting environment path (PYTHONPATH) by specifying either "Environment" or "EnvironmentFile" in /etc/systemd/system/mailmain3.service. None works. I had: EnvironmentFile=/opt/mailman/.systemd_vars where the contents of .systemd_vars are: PYTHONPATH=/usr/lib64/python310.zip:/usr/lib64/python3.10:/usr/lib64/python3.10/lib-dynload:/usr/lib64/python3.10/site-packages:/usr/lib/python3.10/site-packages:/opt/mailman/venv/lib64/python3.10/site-packages:/opt/mailman/venv/lib/python3.10/site-packages At this point, I am frustrated. Is there something else I can do to get mailman3 on this server? from a frustrated Onyeibo

3 years, 6 months

[MM3-users] Re: MTA setup

by Mark Sapiro

On 12/23/24 09:01, Arte Chambers via Mailman-users wrote: > Output from mailman log after sending a test message to the list: > > Dec 23 16:52:23 2024 (684048) Traceback (most recent call last): > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > line 158, in _archive_message > url = self._send_message(mlist, msg) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > File > "/opt/mailman/venv/lib/python3.12/site-packages/mailman_hyperkitty/__init__.py", > line 228, in _send_message > raise ValueError(result.text) > ValueError: > <!doctype html> > <html lang="en"> > <head> > <title>Bad Request (400)</title> > </head> > <body> > <h1>Bad Request (400)</h1><p></p> > </body> > </html> mailman_hyperkitty is sending the message to hyperkitty to be archived and receiving the 400 response. Presumably it has previously requested and received the list_url and the permalink to put in the message headers. This can be confirmed by the presence of List-Archive: and Archived-At: headers with values in the messages from the list. So the configuration seems to be correct to allow mailman_hyperkitty to communicate with hyperkitty. It is not clear why, but this code https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/views/mailma… is getting the ValueError. That can come from one of three places in https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming…. The lack of a Message-ID: is not it because Mailman's lmtp runner will add one. Most likely it is the non-ascii sender address from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/lib/incoming… What do you get from ``` mailman qfile var/archives/hyperkitty/spool/xxx.pck ``` where xxx.pck is one of the (hopefully smaller) files. In particular, what is the From: header in that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

[MM3-users] Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

On 21/06/2020 04:52, Mark Sapiro wrote: > On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: >> ... the Body of reply, with the JSON text: >> >> { >> "start": 0, >> "total_size": 1, >> "entries": [ >> { >> "alias_domain": null, >> "description": null, >> "mail_host": "ch-bc.org.uk", >> "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", >> "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" >> } >> ], >> "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" >> } > > All these self_link references are generated from self.api.path_t which > is a reference to (in the case of 3.1) > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… > which gets the host portion from config.webservice.hostname, i.e. the > value of hostname in the webservice section of mailman.cfg, and actually > <sigh>, looking back at > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > that's exactly where you said you set it to 0.0.0.0. > > Change that to greyarea-post Problem is, if I do that (which I did in the beginning), the core rest service listens on localhost / 127.0.0.1 (it obviously recognises that as the , and so cannot be connected to by anything. That is why I set it to 0.0.0.0 to begin with, and what the documentation implies (fairly strongly) that this parameter is about. IMO, the hostname parameter needs to be split up into a "what address should the rest of the world use to address me" and separately "what address(es) should I listen on". Multiple listen addresses enable multihomed hosts to get the right connectivity, too. Would that be hard? Ruth -- -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

5 years, 10 months

[MM3-users] OIDC (was: username)

by Jörg Schulz

The most recent version of Django-allauth has some nice changes, it's now straightforward to include oidc. Just include SOCIALACCOUNT_EMAIL_AUTHENTICATION=True ## This allows existing users to login MAILMAN_WEB_SOCIAL_AUTH = [ "allauth.socialaccount.providers.openid_connect"] in settings.py and use the Django admin to configure the socialauth.... While it is _possible_ to add things like ---- SOCIALACCOUNT_PROVIDERS = { "openid_connect": { "APPS": [ { "provider_id": "mm3", "name": "TheNameThat shows up in the button", "client_id": "configuredID", "secret": "yourOIDCproviderGivesItToYou", "settings": { "server_url": "https://keycloak.wherever.com/realms/yourRealm/.well-known/openid-configura…", "token_auth_method": "client_secret_basic", }, } ] } } ---- I think it's preferable to do that within the Django Admin Gui. Does anybody dare to include this info in the documentation, or are we afraid the next django_allauth breaks things again (this time: Keycloak has been replaced by openid_connect)? -------- Weitergeleitete Nachricht -------- Betreff: Re: [MM3-users] Re: username Datum: Wed, 13 Sep 2023 07:34:35 +0000 Von: info(a)joergschulz.de An: Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> Hi, probably you are looking for https://django-allauth.readthedocs.io/en/latest/index.html and https://github.com/lokeish/django-all-auth-and-keycloak-integration but https://github.com/pennersr/django-allauth/commit/ab704687f438c06fd23e72bce… will be helpful once implemented. Am 12. September 2023 um 05:54 schrieb "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp <mailto:turnbull.stephen.fw@u.tsukuba.ac.jp?to=%22Stephen%20J.%20Turnbull%22%20%3Cturnbull.stephen.fw%40u.tsukuba.ac.jp%3E>>: bryan.kartzman(a)yu.edu writes: > Just to let you know, there is a maintained SAML2 plugin available > on github (https://github.com/grafana/django-saml2-auth) that I was > able to install and get to work with AZURE SSO. There are multiple ways to solve this problem. My employer wanted a host-wide solution so they chose Shibboleth. Some day I'll go out and collect the ones I can find and document them (in summary form: source site, recency of stable version, recency of maintenance, etc). Steve

2 years, 6 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Michael.Sanderson＠ubc.ca

Mark, thanks for your response. It is perhaps non-fatal, but we do have a different number of templates processed. This is from a successful run with django-allauth==0.57.0. Note the different count of templates from the “failed” processing and this one. (venv) [mailman@rubytears ~]$ mailman-web compress Compressing... done Compressed 2 block(s) from 124 template(s) for 1 context(s). Is this compression of web content that will served to clients? Compressed data would be preferred over non-compressed to decrease data volume, but non-compressed will be served if compressed isn’t available? Michael Sanderson > On Nov 7, 2023, at 7:46 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > [CAUTION: Non-UBC Email] > > On 11/7/23 16:26, Michael.Sanderson(a)ubc.ca wrote: >> Despite earlier comments that django-allauth 0.58.1 has been released to fix this issue (and presumably 0.58.2 would have the fix as well), there appears to still be an issue. As Odhiambo indicated with django-allauth==0.57.0, mailman-web compress completes without errors. With django-allauth 0.58.1 and 0.58.2, I still get >> (venv) $ mailman-web compress >> Compressing... Error parsing template socialaccount/signup.html: socialaccount/base.html >> done >> Compressed 2 block(s) from 78 template(s) for 1 context(s). > > > I don't think this is fatal, but I have reported it at https://github.com/pennersr/django-allauth/issues/3513 > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to michael.sanderson(a)ubc.ca

2 years, 5 months

[MM3-users] Re: Hyperkitty CPU usage

by Abhilash Raj

On Sat, Apr 27, 2019, at 9:40 AM, Alain Kohli wrote: > I have run "python manage.py rebuild_index" before, doesn't that do > clear_index as well? Apart from that, I run hyperkitty in a docker > container and didn't know fulltext_index should be persistent, so that > got deleted after every version update for sure. Which images are you using and how are you deploying them? You should persist fulltext_index, yes, and possibly logs if you need them for debugging later. Can you paste the entire error traceback? > > > On 4/26/19 10:18 PM, Mark Sapiro wrote: > > On 4/26/19 11:14 AM, Alain Kohli wrote: > >> I see loads of "A string literal cannot contain NUL (0x00) characters." > >> messages, but I haven't found missing messages in the archives yet. Not > >> sure how that could be related, though. Apart from that I don't see > >> anything unusual. The other jobs (quarter_hourly, hourly, etc.) seem to > >> run and finish normally. > > > > Did you upgrade from a Python 2.7 version of HyperKitty to a Python 3 > > version? The Haystack/Whoosh search engine databases are not compatible > > between the two and "A string literal cannot contain NUL (0x00) > > characters." is the symptom. > > > > You need to run 'python manage.py clear_index' or just remove all the > > files from the directory defined as 'PATH' under HAYSTACK_CONNECTIONS in > > your settings file (normally 'fulltext_index' in the same directory that > > contains your settings.py. > > > _______________________________________________ > 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

[MM3-users] Re: Migration failure (2.1.29 to 3.3.8 on Debian testing)

by {16/7}

Hi Odhiambo, thank you for responding. Let me first say that I am familiar with Python virtualenv, and while it may be the recommended **generic** installation procedure, there is no denying that Linux distros will offer software using their own packaging mechanisms. It would seem that moving this conversation over to the Debian community would be the best move to take then, if I continue to have issues and their packaging is to . It turns out that I left the "-l" in the hyperkitty_import command. So I re-ran it with the "-l" included. I got the same warnings about primary keys but on first glance it appears to have successfully imported the entire set of archives. Something interesting to note: if I examine the mailman-web script, it attempts to run that same python script as the user www-data. This is just as I was doing (lucky guess!), but using su instead of sudo. It seems like I've managed to complete the full process of migrating my list documented on that webpage (apart from rmlist'ing the old list). FWIW, Here's the output: $ sudo -H -u www-data /usr/share/mailman3-web/manage.py hyperkitty_import -l mylist(a)mysite.com /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox ... warnings ... Importing from mbox file /var/lib/mailman/archives/private/mylist.mbox/mylist.mbox to mylist(a)mysite.com Computing thread structure Synchronizing properties with Mailman Warming up cache The full-text search index is not updated for this list. It will not be updated by the 'minutely' incremental update job. To update the index for this list, run the Django admin command with arguments 'update_index_one_list mylist(a)mysite.com'. And here's the result of rebuilding the index. $ sudo -H -u www-data /usr/share/mailman3-web/manage.py update_index_one_list mylist(a)mysite.com ... very similar warnings ... Indexing 1497 emails

2 years, 10 months

[MM3-users] Re: Finding a user to delete them

by Allan Hansen

You log on to the member’s account using the admin password. Then one of the options is to list all the accounts. I think that the site admin (in own account) and a member (ditto) should be able to do this easily in the Postorious interface. I had expected that. Yours, Allan Hansen hansen(a)rc.org > On Mar 13, 2020, at 11:26 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 3/13/20 1:02 PM, Allan Hansen wrote: >> The Django Admin Interface is better, but it also does not give a full picture of a member, as it does not show the lists that member is a member of. >> MM2 had that feature, which was very useful. When I heard of MM3 supporting ‘users’ as opposed to ’subscribers’, I was expecting an interface that was >> ‘user’ centered, both at the user level and at the admin level. As a site admin I don’t have a way to get a comprehensive view of a user account (attached email addresses, subscribed lists, etc.). > > Hi Allan, > > What feature in MM2 allowed the function to see what lists a member was subscribed to? For some reason my mind is coming up empty. > > Your above comments is something we will be considering seriously as we continue to develop Affinity. > > -- > Please let me know if you need further assistance. > > Thank you for your business. We appreciate our clients. > Brian Carpenter > EMWD.com > > -- > EMWD's Knowledgebase: > https://clientarea.emwd.com/index.php/knowledgebase > > EMWD's Community Forums > http://discourse.emwd.com/ > > _______________________________________________ > 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/

6 years, 1 month

[MM3-users] Re: Bottom line of message footer

by Mark Sapiro

On 2/14/21 5:40 PM, Tom Stoddard wrote: > Here's another question that I have. A regular message just came into my > email from one of the lists I'm a member of and it had a 3 line footer. > The first two lines are fine, they just include the list's email address > and an address to send unsubscribe requests to. The third line is this: > > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s > > It looks to me like it should be a link to the group's list info page. > Is this a bug or is there something I can do to fix it? It looks like it > might be missing a forward slash after the first "s". This is a list whose msg_footer was imported by The Mailman 3 process that imports Mailman 2.1 lists. This import process will recognize the default msg_footer and not create a list specific template for it, but other things in the footer result in a list specific template which needs to be reviewed for issues like this. The way for you to fix it is to create a list:member:regular:footer (and maybe a list:member:digest:footer) template in your web UI which will then override the existing list specific template. The available replacements are listed at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>. In templates they are all $ strings, e.g. $name. The %(name)s replacements are Mailman 2.1 and won't work. Also, there is no replacement for web_page_url because Mailman Core doesn't know what that is, so you have to include the actual 'https://.../' value if you want to include a web link. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: new list not working

by Christian

Mail.log Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: connect from box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: 11516101258: client=box.ecovillage.cc[45.79.28.18] Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: warning: header Subject: fifth test message from box.ecovillage.cc[45.79.28.18]; from=<christian(a)naturalintelligence.us> to=<redlatinleg(a)lists.ccalternatives.org> proto=ESMTP helo=<box.ecovillage.cc> Mar 9 22:03:30 zarathustra postfix/cleanup[26926]: 11516101258: message-id=<033101d952d3$0fe82730$2fb87590$(a)naturalintelligence.us> Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: from=<christian(a)naturalintelligence.us>, size=3496, nrcpt=1 (queue active) Mar 9 22:03:30 zarathustra postfix/smtpd[27337]: disconnect from box.ecovillage.cc[45.79.28.18] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 9 22:03:30 zarathustra postfix/lmtp[27338]: 11516101258: to=<redlatinleg(a)lists.ccalternatives.org>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.02, delays=0/0.01/0/0.01, dsn=2.0.0, status=sent (250 Ok) Mar 9 22:03:30 zarathustra postfix/qmgr[9973]: 11516101258: removed -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, March 9, 2023 2:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: new list not working On 3/9/23 14:32, Christian via Mailman-users wrote: > When I ran > > mailman members -r -n enabled redlatinleg(a)lists.ccalternatives.org > > I did receive a list of subscribers for the new list I created, not > just the owner or moderator. > > Upon closer examination, another of my longtime working lists is also > not working. Similar behavior as the new list I created in that I see > the message has been archived, but not distributed to the subscribers. What do your MTA logs show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ EOYMZXS4WPQGLDLVVWOGC67WY576665F/ This message sent to csa(a)web-analysts.net

3 years, 1 month

[MM3-users] help with startup scripts

by Piet Barber

Hello, I'm trying to get mailman3 working on Ubuntu. I'm following these instructions: https://docs.list.org/en/latest/install/virtualenv.html#setup-virtualenv I've gotten to the point where I can successfully su - to the mailman3 user, and manually start the mailman3 process with the startup command. However, when I follow the systemctl startup scripts as per the instructions at the URL above, it get stuck in the startup ... forever Starting from the command line works great! (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman start Starting Mailman's master runner Generating MTA alias maps (venv) mailman@arcus:~$ (venv) mailman@arcus:~$ /opt/mailman/venv/bin/mailman status GNU Mailman is running (master pid: 47815) But when I try to start it from systemctl, it just hangs forever... root@arcus:/etc/nginx# systemctl start mailman3 If I background it, and check it out from systemctl status, I get that It's stuck in the startup mode. root@arcus:/etc/nginx# systemctl status mailman3 ● mailman3.service - GNU Mailing List Manager Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: enabled) Active: activating (start) since Wed 2025-08-13 23:12:05 UTC; 29s ago Process: 49024 ExecStart=/opt/mailman/venv/bin/mailman start (code=exited, status=0/SUCCESS) Tasks: 17 (limit: 4605) Memory: 878.0M (peak: 878.5M) CPU: 11.030s I've tried this with and without the forking entry in the systemctl configuration. No matter what I do, it's stuck in the ... Active: activating (start) since Wed 2025-08-13 23:13:37 UTC; 27s ago What am I missing? root@arcus:/etc/nginx# cat /etc/systemd/system/mailman3.service [Unit] Description=GNU Mailing List Manager After=syslog.target network.target postgresql.service [Service] Type=forking PIDFile=/opt/mailman/mm/var/master.pid User=mailman Group=mailman Environment="MAILMAN_CONFIG_FILE=/etc/mailman3/mailman.cfg" ExecStart=/opt/mailman/venv/bin/mailman start ExecReload=/opt/mailman/venv/bin/mailman restart ExecStop=/opt/mailman/venv/bin/mailman stop Restart=on-failure RestartSec=15 [Install] WantedBy=multi-user.target root@arcus:/# -- Piet Barber http://www.pietbarber.com/ http://blog.pietbarber.com/

8 months, 2 weeks

[MM3-users] Re: URL-lines in templates get folded

by Frank Steinberg

> Am 18.10.2022 um 18:37 schrieb Mark Sapiro <mark(a)msapiro.net>: > > On 10/18/22 06:52, Frank Steinberg wrote: >> Hi, >> I’ve added links to some templates to give owners and moderators >> shortcuts to the postorius UI for moderation tasks, e.g., I’ve added >> https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> >> Unfortunately those lines seem to exceed a certain limit and get >> folded, so that they appear as, e.g. >> https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> >> messages >> (or similar) and are not directly useful. > > How are you editing the templates? I.e., are you editing them via Postorius or by putting them in Mailman's var/templates/ directory or ?? I am using the docker containers and have been putting files into the directory mapped to var/templates/site/. > Also are those lines of the form > > https://... <https://...> I am sorry, my Mail program changed the encoding here. In fact the template files just contain the plain URL. No blanks no angle brackets. Just one URL containing the $list_id variable. > what you are entering or is that duplication and artifact of your mail client? You should be entering just a URL either with or without angle brackets, but not both. > > Is the folding actually in the raw message or is it an artifact of the mail client viewing the message? The folding appears in the raw message sent by Mailman and put into the users INBOX. I thought there could be a kind of filter in Mailmans mailout processing that cares for line breaks in order to not exceed approx. 75 chars per line? I will do some more testing tomorrow (european time).

3 years, 6 months

[MM3-users] External MTA incoming mail: configuration

by Roland Giesler

I have mailman set up to send mail via an external MTA, which is supported by mailman and described in the documentation here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…. Specifically it says: |lmtp_host|and|lmtp_port|are parameters which are used by Mailman, but also will be passed to the MTA to identify the Mailman host. The “same host” case is special; some MTAs (including Postfix) do not recognize “localhost”, and need the numerical IP address. If they are on different hosts,|lmtp_host|should be set to the domain name or IP address of the Mailman host.|lmtp_port|is fairly arbitrary (there is no standard port for LMTP). Use any port convenient for your site. “8024” is as good as any, unless another service is using it. However, there is a practical problem with LMTP (to receive incoming email) which is as follows: The setup in mailman.cfg: lmtp_host: lists.fast.za.net lmtp_port: 8024 Now, lists.fast.za.net is the mailman server. The docs say that mailman passes these on to the MTA. However, the MTA (postfix) on box2.gtahardware.co.za has the following setting in it main.cf: virtual_transport=lmtp:[127.0.0.1]:10025 If I reply to a signup confirmation email for example, the mail is received and processed by box2.gtahardware.co.za, and it is not passed on to the mailman server. So what is meant by "but also will be passed to the MTA to identify the Mailman host" in the docs? If I change the config of the MTA (postfix) to be "virtual_transport=lmtp:[lists.fast.za.net]:8024", I assume the incoming mail will be forwarded, but how does postfix know that only the mailman emails should be forwarded and not all the other mail that the server at box2.gtahardware.co.za receives? This is quite fuzzt to me at this stage. Could someone help me with some clarity please?

1 year, 9 months

[MM3-users] Re: Google auth issue redirect_uri_mismatch

by Abhilash Raj

On Sun, Sep 8, 2019, at 2:12 PM, Ugnius S wrote: > Hi. > New question about configuration, maybe somebody has experience and know > what I should change it. I have tried to implement Google authorisation. > I have created Google credentials keys and successfully added using Django > admin page. > I use UWSGI proxy for apache setup like "ProxyPass / http://127.0.0.1:8002", > UWSGI runs on 0.0.0.0:8002. (So Appache from external address redirects to > internal) What happens when I try Google auth... > If I set Authorised redirect URIs: > http://lists.example.com/accounts/google/login/callback/ , Google gives me > error 400 Error: redirect_uri_mismatch and requests for: > http://127.0.0.1:8002/accounts/google/login/callback/ > If I set that requested address to Google, then Google authorises me, > but and after authorisation redirects to > http://127.0.0.1:8002/accounts/google....../.... (very long line) Of > course this internal address does not open, but... > If I just manually replace part of address just: http://127.0.0.1:8002 > replace to https://lists.example.com/.../...(long line) this makes me get > in as authorised user to the page. > How to make django to send external request to Google? Because > Google should not point back to internal address... This seems simple, but > I do not find what I should change in the configuration: Apache or Django > or uwsgi.ini I hope anybody of You have experience and made it to run. You need to set this in nginx under your location directive, where you setup your proxy_pass or uwsgi_pass proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; Something similar should exist for Apache. > > Kind regards > Ugnius > _______________________________________________ > 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)

6 years, 7 months

[MM3-users] Re: message duplication and an NNTP related error

by Laurens Kils-Hütten

Am Tue, Feb 24, 2026 at 01:16:45PM -0800 schrieb Mark Sapiro: > On 2/24/26 09:23, Laurens Kils-Hütten wrote: > > > > I've used the debian packages: > > > > apt install mailman3-full mailman3-web > > Then this may be a Debian issue and should be reported there in any case. > See <https://wiki.list.org/x/12812344>. I will, once I convinced it's really a bug. Right now I'm thinking it's a misconfiguration on inn2's side. From scrutinising the message headers this is what happens: mailman sends the message to the newsserver where it get's injected properly receiving an Injection-Information: header field. Then however this new message is sent back to mailman. Now there's a duplicate with identical message ID. Mailman then sends it back to inn2 which refuses to take it and the python nntp client throws an error, thus preventing an endless loop. Why inn2 even sends the message back to mailman I can't tell right now. These are the relevant snippets from my inn2 setup: # this is from /etc/news/news2mail.cf # no surprises, and it basically works. News from the grenzland.test # group is forwarded to the proper list address test-grenzland-club test(a)grenzland.club # this is in /etc/news/newsfeeds news2mail!:!*:Ac,Tc,Wn*:/usr/lib/news/bin/news2mail test-grenzland-club/grenzland.club:!*,grenzland.test:Ap,Tm:news2mail! # this last line should do two things: forward messages from the # test(a)grenzland.club list to the grenzland.test newsgroup, # AND don't send any messages back which have grenzland.club # in their Path header. This last bit seems to fail however, # and I fail to spot the error. I'll ask about this in the inn2 places I known of. Cheers, lkh -- Laurens Kils-Hütten https://lkh.sdf-eu.org

2 months

[MM3-users] Mailman not able to process "big" requests

by Jonas Felber

Hi, We migrated from mailman2 to mailman3 a week ago. Since then we are unable to send messages the our students through the mailing list. Here are some symptoms: 1. I go to mass subscribe and subscribe 400 emails 2. I click subscribe, the browser (in my case safari) tries to load the page for a few seconds 3. The request times out 4. Once the service becomes responsible again, I see that only part of my emails got subscribed (~50 in this case). For me this really looks like the emails are sent on the "web-thread" that gets killed once the request times out. Looking at this https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p… <https://gitlab.com/mailman/postorius/blob/master/src/postorius/views/list.p…> seems to confirm my suspicions. Some quick overview of our infrastructure: The TCP endpoints are: browser -> haproxy in kubernetes-entry-router -> nginx in kubernetes-ingress -> nginx in mailman -> mailman We mitigated the issue by giving it more CPU power and increasing the timeouts in one of the nginx endpoints. We also have a problem with sending out emails to "large" (>50) groups, as they seem to not getting sent out at all. Do you have any idea what the problem here could be? We would be really glad if you can help us getting our mailman up and running, as I currently have to send emails out by "hand". I will happily provide you with more details about our configuration, just let me know what you need. Kind regards, Jonas Jonas Felber <jonas.felber(a)vis.ethz.ch <mailto:jonas.felber@vis.ethz.ch>> Aktuar & CTF Präsident VIS - Verein der Informatik Studierenden an der ETH Zürich CAB E 31, Universitätstr. 6, ETH Zentrum, CH-8092 Zürich https://www.vis.ethz.ch <https://www.vis.ethz.ch/>

8 years

[MM3-users] Re: translating templates (was: Re: spanish localization)

by Mark Sapiro

On 2/15/21 2:38 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > On 13/2/21 20:00, Mark Sapiro wrote: >> Also note that the translations on weblate only affect strings in the >> core code. The Mailman core templates are not currently translated in >> weblate and there are currently no Spanish language templates. One would >> need to create Spanish translations of all the templates in >> <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/templates/en> >> >> and submit a merge request to add them to a mailman/templates/es/ >> directory. > > I downladed the templates and I'm beginning the translation process, but > I have a question. What language map has to be used? In my S.O. it's > ISO-8859-15 but I'm concerned it has to be UTF-8... Better ask before > having to do a remapping of the files after... They should be encoded as UTF-8. > It comes to my attention that three files have 0 bytes. The 0-byte files can either be left out of templates/es or put in as empty files. They are things for templates which are empty by default. Also, help.txt is unused and doesn't need to be translated. At one time it was intended to be the template for the response to the email `help` command, but it is not used for that purpose. Finally, although I said previously that the translated templates should be submitted as a merge request, that can still be done, but is not necessary. They can be translated in weblate. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> and <https://gitlab.com/mailman/mailman/-/issues/825>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Set domain inactive / archive import from other domain.

by Johannes Winter

Am Sat, 15 Sep 2018 09:31:53 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 09/15/2018 07:15 AM, Johannes Winter wrote: > > > > we've migrated a list from another domain and would like to keep the > > archives. Hyperkitty doesn't recognize the emails in the mbox > > archive during import due to the other domain name. > > > I don't understand the problem. I just ran a test where I imported a > mbox containing 3 messages which were not even list posts and in > which I had changed all the domain names to 'example.com'. I.e., in > the mbox I imported, the headers containing domain names looked like > > From root(a)example.com Sun Aug 26 09:12:06 2018 > Return-Path: <root(a)example.com> > Delivered-To: root(a)example.com > Received: by example.com (Postfix, from userid 0) > From: Anacron <root(a)example.com> > To: root(a)example.com > Message-Id: <20180826161158.F154D34010C(a)example.com> > X-msapiro-MailScanner-From: root(a)example.com > > and the 3 messages were all added to the archive. > > Why do you think the domain name is an issue? Perhaps the issue is > there is already one or more messages in the archive and the messages > you are importing are older. If you don't specify --since to > hyperkitty_import it won't import messages older than the newest > message in the existing archive. Thanks a lot for your excellent and fast support! That was the problem. Maybe it would be wise to include that into the help of the hyperkitty_import command? Although this command successfully imported 3/4 of the huge (1.7GB) mbox, it stumbled upon an error after some minutes: https://gitlab.com/mailman/hyperkitty/issues/200 -- Johannes Winter matrix: @yova:matrix.allmende.io

7 years, 7 months

[MM3-users] Re: [Mailman-Users] mailman 3 and freeipa

by Abhilash Raj

On Mon, Mar 18, 2019, at 12:16 AM, Stephen J. Turnbull wrote: > Crossposting and redirecting replies to mailman-users(a)mailman3.org. > > Steven Jones writes: > > > I cant find anything on this so far but can Mailman3's webui use > > freeipa as the authentication mechanism? > > Hi Steve, > > I don't have a complete answer offhand (and right now I'm just > reducing my inbox so a single google search is as much as I can do), > but searching for "freeipa django" indicates that there are > "connectors" for Django and FreeIPA. The nicest option would be a > plugin for Django's socialauth application. > > If that doesn't seem to exist, perhaps you can just add a FreeIPA > application to the Django configuration. You would need to add it to > both Postorius and HyperKitty configurations. Here is a list of all the providers Django-allauth(and hence us) support[1]. You can definitely add more providers and if Django-allauth isn't ready to merge that, you could create a completely separate python package that providers that functionality. If you need examples, here is a custom provider we have in our source code to authenticate using Fedora's auth management system[2]. [1]: https://django-allauth.readthedocs.io/en/latest/providers.html [2]: https://gitlab.com/mailman/django-mailman3/tree/master/django_mailman3/lib/… > > Steve > > > -- > Associate Professor Division of Policy and Planning Science > http://turnbull.sk.tsukuba.ac.jp/ Faculty of Systems and Information > Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba > Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN > _______________________________________________ > 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, 1 month

[MM3-users] Re: list footer questions

by Kelly Close

I agree Mark. I can't see the issue but those search rules are clear. I'm glad to know I can "force" it to work with the table records but I would like to figure out the more systemic issue in case it could affect other things. ~Kelly -- K. Kelly Close, P. E. Senior Project Manager | Water Rights Engineer | Technology Team Lead Office: 303-455-9589 | Direct: 303-867-7665 Kelly.Close(a)LREwater.com <http://www.lrewater.com/> LREWATER.COM <http://lrewater.com/> 1221 Auraria Parkway, Denver, CO 80204 ***CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. Thank you.* On Sun, Jun 7, 2020 at 5:14 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/7/20 3:47 PM, Mark Sapiro wrote: > > > > However, you shouldn't have needed to do that. I only mentioned it in > > case there was an entry for the name and context with a URI pointing > > elsewhere. The default if there is no entry is to use Mailman's normal > > search rules which include > > templates/lists/<list-id>/en/list:member:regular:footer.txt. > > > > The search rules are documented in the code at > < > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/utilities/i18n… > >. > > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

5 years, 10 months

[MM3-users] Re: Emails about moderation are sent to list owners, want them sent to moderators instead

by Mark Sapiro

On 7/2/22 1:56 AM, Elias Rudberg wrote: > Hello, > > This is about GNU Mailman 3.3.3 (Tom Sawyer). > > For each list there are both "owners" and "moderators". As I understand > it, the idea is that owners have the power to change configuration for > the list, while moderators have more limited power, they can only > moderate but not change configuration. Correct. > When an email is sent from a non-member to a list that requires > moderation in such a case, an email with subject like "[listname] post > from [sender] requires approval" is sent to the list owners. I would > like those emails to be sent to moderators instead. Such notices are actually sent to the LISTNAME-owner@... address, received by Mailman and resent to all the owners and moderators. Both owners and moderators should receive the message. > The reason why I want it to work that way is that list owners sometimes > want to delegate the work of moderating to the moderators. List owners > then want to keep the power to change list configuration, but they do > not want to be bothered by individual moderation emails. > > Is there a way to configure mailman3 to make it send moderation emails > to moderators instead of owners? As I said, the notices are sent to both owners and moderators. There is no simple configuration to change this. Change would require modifying mailman/handlers/owner_recipients.py or possibly defining a sub-class of mailman.pipelines.OwnerPipeline which overrides the _default_handlers method and arranging for that to be used. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: SPF check fails for lists subdomain

by Odhiambo Washington

On Thu, Jan 5, 2023 at 10:56 AM Jan Eden via Mailman-users < mailman-users(a)mailman3.org> wrote: > On 2023-01-04 15:07, Mark Sapiro wrote: > > > On 1/4/23 14:02, Jan Eden via Mailman-users wrote: > > > > Although I could specify the IP address in my SPF records directly (as > > > you suggested), I do hope that my understanding of DNS records laid out > > > above is not entirely misguided. My current setup does work as expected > > > for eden.one, after all. > > > > As I said at < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > I was misreading your DNS and now I am as puzzled as you about the > failure. > > It gets even more mysterious. I tried sending messages from both > lists.eden.one and janeden.net (my other domain) to a gmail account and > to another mail provider. Both messages passed the SPF checks on both > services (s. the relevant headers quoted below). Now because I send > those messages via my SMTP user (smtpuser(a)eden.one) and use SRS, the SPF > check operates (and succeeds) on e.g. > > srs0=jdm+=5c=lists.eden.one=testlist-bounces+gmailuser=googlemail.com(a)eden.one > (and not on somethingsomething(a)lists.eden.one or > somethingsomething(a)janeden.net) Could this be the reason for the failed > SPF checks in Yahoo's and Google's DMARC reports? > > - Jan > Might you be willing to use proven tools instead of trying so hard to understand the myth? I use https://easydmarc.com/tools#spf-tools It allows me to generate, lookup, test SPF, DKIM, DMARC, etc. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: 404 on fresh install (Debian11)

by Stephen Turnbull

Sorry about breaking the thread, institution system "upgrade" to O365 broke my world so I'm cutting and pasting into Outlook. comprepair_jimberg--- via Mailman-users writes: > Can you setup Mailman3 for me? I have done apt install > mailman3-full but I have no clue whaat I am doing. You should seriously consider either going for a managed host or hiring somebody. Unfortunately, you're asking a bit much for volunteer help. The problem is that Debian uses the FHS layout with the system Python,while we core devs recommend and use a self-contained "virtual environment" with an /opt-style layout. Debian also applies patches that may or may not be backports from more recent versions. We just don't know what's going to go wrong on a distro install. Mailman also has dependencies on several system components (webserver, mailserver, WSGI implementation, SQL database, text indexer) which each come in multiple flavors, but the range of combinations we're familiar with is limited and may not even include the Debian default list. Once you have a working Mailman installation we'll be happy to help you tune it, though. (And you don't need core devs for that anyway, other Mailman site admins who hang out here can often help as well as well as we can.) We are much more likely to have knowledge and experience to help with a virtual environment install as described in https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… Here's an alternative, "from the ground up" step by step description of a specific combination of components: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I think it should work just fine for Debian 11 as well. The author of "Mailman3 On Debian10" was a hosting and mailing list service provider, and used this recipe for all his hosts. Regards, Steve

3 years, 1 month

[MM3-users] Re: spf/dkim/dmarc

by Christian

Using https://www.spf-record.com/ I have checked my SPF records which are reported as 'SPF check passed'. My DKIM also passes various test suites. Yet, Google is still rejecting mailman messages to any and all gmail users. I have even filled out their short form for delisting at https://support.google.com/mail/contact/bulk_send_new all to no avail. Example of block logfile message: May 18 12:53:11 lists postfix/smtp[28104]: C9D7A1005DA: to=<billb6951(a)gmail.com>, relay=gmail-smtp-in.l.google.com[142.250.138.27]:25, delay=0.69, delays=0.01/0.01/0.14/0.53, dsn=5.7.26, status=bounced (host gmail-smtp-in.l.google.com[142.250.138.27] said: 550-5.7.26 The MAIL FROM domain [lists.ccalternatives.org] has an SPF record 550-5.7.26 with a hard fail policy (-all) but it fails to pass SPF checks with 550-5.7.26 the ip: [192.46.218.224]. To best protect our users from spam and 550-5.7.26 phishing, the message has been blocked. Please visit 550-5.7.26 https://support.google.com/mail/answer/81126#authentication for more 550 5.7.26 information. p3-20020a056870868300b001926c1449a6si1393979oam.240 - gsmtp (in reply to end of DATA command)) Could the hard fail policy be implicated in the gmail rejection? Other than readdressing my server, is there anything else I can do? -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, May 17, 2023 11:50 AM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: spf/dkim/dmarc On 5/17/23 07:20, Odhiambo Washington wrote: > > You can only have 1 SPF record. For a domain. But as Jeremy Stanley noted, mail.ccalternatives.org and lists.ccalternatives.org are different domains and it is fine for each to have its own spf record. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message/ WAUVS6WWYOYQBJGIDP3HK6L3NHM4RGHF/ This message sent to csa(a)web-analysts.net

2 years, 11 months

[MM3-users] Re: mailman 2.1 or 3.0 (or another MLM)

by David Newman

On Jan 25, 2022, at 06:56, Stephen J. Turnbull <stephenjturnbull(a)gmail.com> wrote: >> Or is there a better MLM for simple use cases? I used Majordomo >> back in the 90s and was happy to get onto Mailman from >> that. Something similar to Mailman 2.1 in features/functionality. > > It's been years since we had an answer to that question. Mark might > have more to say, but the last time we were challenged on this, the > rival was Sympa, and the conclusion I came to was that the use cases > are different. I prototyped Sympa and mlmmj along with MM3, and found the latter was the closest match to MM2’s feature set. It also provided some features not available with the others, at least not available by default. > > Depending on your Linux distro, and your attitude to risk, Python 2 > plus Mailman 2 in a container, VM, or even a dedicated host in the DMZ > or outside the firewall might be a reasonable solution. Yes, this is possible. The IETF, the body that defines Internet technical standards, is still on MM2. I’m with them; given my druthers I’d run MM2 forever because it Just Works. Then again, I put a high priority on keeping the base OS and applications patched against current security vulnerabilities. That’s getting harder to do with MM2. Debian and FreeBSD have deprecated Python 2. MM2 still has maintenance releases but no new development. MM2 also has some archaic design decisions such as sending user passwords in plaintext email. Like it or not, MM3 and related components are current, and currently maintained. I wasn’t crazy about the learning curve to get MM3 working, but I pressed on because it will provide a platform I can keep running much farther into the future. dn

4 years, 3 months

[MM3-users] Re: Auto discard after max_days_to_hold not working.

by Hitashi mancho

Hi Mark, As you have mentioned about implementation of "Auto discard after max_days_to_hold" in a next release. How do I install that release? I have installed mailman3 using pip in virtual environment and whenever I try to upgrade the release using pip install -U, it gives package already compiled and up to date. My Mailman version is as follows. Mailman version: GNU Mailman 3.3.10 (Tom Sawyer) Python 3.11.9 Rocky Linux 9.5 Regards, Hitachi. On Thu, May 1, 2025 at 12:51 PM Hitashi mancho <huhamails(a)gmail.com> wrote: > Thank you so much, Mark and Stephen, for the quick action and response. > Waiting for the next release. > > On Tue, Apr 29, 2025 at 10:52 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 4/28/25 10:55, Mark Sapiro wrote: >> > >> > `mailman import21` will import the setting, but per the above comment, >> > it doesn't yet work. The setting exists and is exposed in REST, but it >> > appears it is not actually implemented. >> >> >> This is now implemented for the next release. See >> https://gitlab.com/mailman/mailman/-/issues/1215 and >> https://gitlab.com/mailman/mailman/-/merge_requests/1346 for Mailman >> core and https://gitlab.com/mailman/postorius/-/issues/628 and >> https://gitlab.com/mailman/postorius/-/merge_requests/1001 for Postorius. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> _______________________________________________ >> 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to huhamails(a)gmail.com >> >

7 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Guillermo Hernandez (Oldno7)

On 15/5/21 0:29, Odhiambo Washington wrote: > > > On Sat, May 15, 2021 at 1:08 AM Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org > <mailto:mailman-users@mailman3.org>> wrote: > > > On 14/5/21 23:52, Odhiambo Washington wrote: > >> Which OS are you using? > > FreeBSD. > > > > > As Mark pointed, you probably have installed the textproc/sassc > port (or > package). I'ts an equivalent for sass. Do the config as advised. > > I have mailman3 installed and running smoothly in a pair of 12.2 > RELEASE > FBSD servers. > > There is a thread about this installations that can help: > https://forums.freebsd.org/threads/mailman-3.61050/post-488128 > <https://forums.freebsd.org/threads/mailman-3.61050/post-488128> > > > > I will look into this. I know FreeBSD has a mailam3 port, The mailman3 port runs, but aaaaaall the other apps needed, just no. Following the FreeBSD ports route ended in a failure. In the previous post on the link I explained all the failed tries. > but I have mailman2 in production and the port installs to > /usr/local/mailman I had mailman2 indeed. And migrated to mailman3 all my lists (17 in one server, 2 in other). One of them with more than 8000 suscribers. I know it's not much, but in that thread you can find example config files than you can compare. They are working. > so I have to be careful - install mailman3 in /opt, then plan on > hosing mailan2 and moving mailman3 to it's place after migration. > It's not simple. Yes, I know. I did. Best luck. > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 11 months

[MM3-users] Re: Hyperkitty

by Odhiambo Washington

On Mon, Jan 30, 2023 at 10:58 PM Onyeibo <onyeibo(a)schemefusion.com> wrote: > On Mon, 30 Jan 2023 16:01:16 +0300 > Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > So an array?? > > > These are defaults. I have also added my IPs. Nothing is happening. > > > > > Perhaps I did something wrong here. Any documentation on this? > > > > > > > https://mailman-web.readthedocs.io/en/latest/settings.ht > > > > > > My instance is not archiving. > > > > Things to check: > > 1. Is your MAILMAN_ARCHIVER_KEY value in settings.py (quoted here!) > > the same as api_key in mailman-hyperkitty.cf (unquoted here!)? > > I have double-checked this. Yes ... I got it right > > > 2. Your MM3 log files - do they say anything? > > > Nothing! No new errors. It is very strange and frustrating > Simply put: Mailman3 uses the following components for archiving: Archiver: responsible for storing messages and metadata, such as message header information, in the archive database. Archiver API: provides an interface for accessing the archived messages. Archiver REST API: allows access to the archives through a RESTful interface. To configure Mailman3 archiving, you can: Choose an archive backend, such as the built-in HyperKitty backend, or a third-party archive backend. Set up the archive backend, including database connection details and other required configurations. Configure Mailman3 to use the chosen archive backend. This typically involves updating the Mailman3 configuration file and specifying the backend's configuration information. You can find more information about Mailman3 archiving and its configuration in the Mailman3 documentation. Now you need to go over the archiver configuration/enablement with a toothcomb :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 months

[MM3-users] Re: Subscription confirmation email

by Mark Sapiro

On 3/14/26 07:19, Eric Broens via Mailman-users wrote: > While doing some tests I subscribed to a mailinglist by sending an email to > <list>-join@<domain> > > Mailman correctly emailed the confirmation request, and the mail was > accepted by my ISP. > > For some reason the confirmation mail did not arrive in my mailbox nor in my > spam folder, it seems to have been silently dropped. This is a problem, but we can't help with that. Only your ISP knows why it dropped it. > A day later, I again sent a subscription request to <list>-join@<domain>, > and I received a mail from <list>-bounces@<domain> with subject "The results > of your email commands" saying that I have a pending subscription for that > mailinglist. > > However, no confirmation link is included, nor instructions to visit the > website to confirm the subscription. > > Am I missing something in the configuration? No. The original request is pending and needs to be confirmed or discarded or time out. If you are a list admin you can go to Subscription requests -> Pending Confirmation and discard the pending request. The time out is configured as pending_request_life with a default of 3 days. > I would expect that a confirmation request is mailed again to the > subscriber. Most subscribers don't use the web interface to manage their > subscriptions. I see your concern. Currently the frustrated subscriber whose original confirmation request is lost has to contact the list owner and may not even understand that need. You could submit an RFE at <https://gitlab.com/mailman/mailman/-/issues/new> to request that the pending request response include the confirmation link. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Things I miss about mailman2

by Quanah Gibson-Mount

Hi Mark, --On Tuesday, March 17, 2020 1:43 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > The message comes from Mailman core. Mailman core does not know what > web management UI you are using or the URI to access it. You need to > change the template for the message to include the URL. Ok great, thank you!. >> b) When a post is made to a moderated list in mailman2, when I went to >> the page to approve/deny/discard, there was additionally an option to >> remove the moderated flag from the user for all future emails. This >> option no longer exists. This was EXTREMELY useful, as we force all new >> members of the list to be moderated for a time while we evaluate the >> quality of their postings. Now I have to go manually track down the >> user and their settings. Unnecessary extra hoops to jump through > > > Click on the subject in the held messages list. At the bottom of the > dialog that opens, there is a drop down to set the user's moderation. > Normally, you would set it to 'default processing'. I do not see any such option. After clicking on the header the only options available at the bottom are: Accept, Reject, Discard, Show Source, Show Header There are zero drop downs anywhere. > This was not "removed". It just hasn't been implemented in MM 3 yet. So in terms of available functionality that was present in MM2, it was removed. It may need to be re-implemented, but this was a core feature that was present in the prior version that is no longer available. --Quasnah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 1 month

[MM3-users] Re: disabled users

by Mark Sapiro

On 10/25/23 10:44 AM, Stephen J. Turnbull wrote: > Servizio Informatico U.I.C.I. Sezione territoriale di Brescia writes: > > > Wher I find the disabled user of a mailing list and wher I can > > reactivate them? > > If you are the list owner or superuser, when you visit the list's > information page there will be a horizontal menu across the top. One > of the entries is Users. Click to open the dropdown menu and choose > Members. There doesn't seem to be an explicit notation for disabled > users, but if the entry in the far right column "bounce score" is > None, the member may be disabled. I don't think this is correct. Members with delivery disabled by bounce will normally show 0 rather than None for bounce score. If you have shell access to the server as the Mailman user, you can run this shell interaction to find members with delivery disabled by bounce. ``` $ mm/bin/mailman shell -l test(a)example.com 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. The variable 'm' is the test(a)example.com mailing list >>> for member in m.members.members: ... if member.delivery_status == DeliveryStatus.by_bounces: ... print(member.address.email) ... >>> ``` But the question is, why do you want to re-enable their delivery. Granted, there are situations such as a misconfigured MTA or not applying needed DMARC mitigations that could result in 'spurious' bounced deliveries, but normally bounce processing disables delivery, sends warnings to the bouncing address and ultimately unsubscribes them because the address it truly not deliverable. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Mailman 3 Status Update Please?

by Barry Warsaw

Thanks for the kind words, David. I just want to mention one thing. > On Jul 24, 2017, at 16:42, ddw David Wilson <ddw.256(a)gmail.com> wrote: > > Personally, when it comes to contributing, I like to have my funds tied or directed to specific, measurable, delivered goals such as frequently seen with crowdfunding applications, rather than simply contributing to an open pool of cash, not earmarked for something specific. Just me, perhaps, but tying the dollars to results makes me feel good, even if it's awkward for those who simply want to delve into the code to fix an irritating bug or work on the next inter-application interface, etc. Very understandable, and we’ve done this in the past. Our initial donation seed money came from Control.com to implement the topics feature of Mailman 2. It’s not unfeasible to do something similar today, although as always, such funding focused development work has to serve the needs of our users and overall project goals. We wouldn’t take money to implement something completely antithetical to our vision or principles. An example of something worthy to fund would be the dynamic lists/nosey lists feature that Systers pioneered, porting that to Mailman 3 proper. But funded development work is difficult because it requires a motivated donor, developer resources (i.e. time), and a project need. One important thing that our pool of donations has supported in the past has been bringing GSoC students to Pycon to sprint with the core team. We need only point to Abhilash Raj, who started out as a GSoC student and is now a core developer working on amazing things. Talk about the multiplier effect! :) For many of us (well, I’ll speak for myself), Mailman has been a labor of love. It’s hard to believe it’s been something near 20 years, and somehow it’s still fun! -Barry

8 years, 9 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Mark Sapiro

Mark Sapiro wrote: > Thus, the issue occurs downstream of lmtp runner. It will take more > investigation to determine where. The issue occurs in mailman/handlers/avoid_duplicates.py. That module will rewrite the Cc: header after possibly deleting some of the entries. That module calls msg.get_all('cc') to get the original Ccs and calls email.utils.getaddresses() on that to get a list of all the name, address pairs. In our case, msg.get_all('cc') returns one of two things. If the message came via LMTP with CRLF line endings, it returns ['"ABC DEF\r\n (XYZ)" <mark(a)msapiro.net>'] If the message came from `mailman inject` with LF line endings, it returns ['"ABC DEF\n (XYZ)" <mark(a)msapiro.net>'] then email.utils.getaddresses() calls internally email.utils.parseaddr on each item in the list to make a list (of one in our case) of name, address pairs. The result is different depending on the line endings which explains why it works with `mailman inject` but not with LMTP. In the case where the line endings are LF, the return is [('ABC DEF\n (XYZ)', 'mark(a)msapiro.net')] but if the line endings are CRLF, the return is [('XYZ', 'ABC DEF')] If the "folding" is not quoted as in ABC DEF (XYZ) <mark(a)msapiro.net> then the return is ('ABC DEF (XYZ)', 'mark(a)msapiro.net') regardless of the line ending as it should be. I can't really fault parseaddr() here because the only time it produces an unexpected result is when the CRLF line folding occurs in the middle of a quoted string which is clearly non-compliant. For Mailman to defend against this, something like the attached patch would do. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

[MM3-users] Re: Mailman3 / Exim4: Router fails

by Mark Sapiro

On 5/22/23 07:44, Stephen J Turnbull wrote: > From: "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> > To: ceo(a)sartrack.nz > ... > > > But it fails with this: > > MM3_LISTCHK=/var/lib/mailman3/lists/${local_part}@${domain} > > For reasons I do not understand, although Mailman 3 keeps list > configurations in the RDBMS, when it creates a list it *also* > "touches" a directory for that list in the directory $var_dir/lists. > (If I remember correctly, these are empty. It's a real directory, not > "virtual".) Since I already knew how to search for the > lists/$LIST/config,pck file used by Mailman 2, I used the same method > for Mailman 3. That directory is used to store messages being accumulated for the next digest in a digest.mmdf mailbox file. > $var_dir is set somewhere near the top of mailman.cfg. I don't know > where to find that file in your installation, it's often in > /etc/mailman3. `mailman conf -k var_dir` will show the setting for $var_dir for various layouts and `mailman conf -k layout` will show the layout in use. > Later you wrote: > > > mailman3 create templist(a)sartrack.nz templist.lists.sartrack.nz (?) > > I tried to create it as: > > create templist(a)sartrack.nz templist(a)sartrack.nz > > but it would not accept that. > > I believe that's because "mailman create" wants the posting address > and the list ID. It just wants the posting address, not the list ID. I.e. mailman create templist(a)sartrack.nz `create` is a subcommand of the `mailman command. `create` by itself as opposed to `mailman create` looks like an artifact from cPanel's Mailman 2.1. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

[MM3-users] Mailman Core 3.3.1rc1 release

by Abhilash Raj

Hey Everyone, I have just released Mailman Core 3.3.1rc1. The final release is scheduled for next week, 17th April. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#rc1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1rc1/ To install this release via pip, you can run: $ pip install --upgrade --pre mailman Note the `--pre` flag because this is a pre-release. If you can, I encourage you to try this out with your environment and report any major breakage to us. We have been running this code on the server hosting this list, so it has already seen some testing, but it is always nice to have some more. If there aren't any major breaking changes reported, the final release will be identical to this one. -- thanks, Abhilash Raj (maxking)

6 years

[MM3-users] Re: Error -- postorius Un-handled exception

by Stephen J. Turnbull

Mark writes: > After working my way through your suggestions with no joy I > discovered to my embarrassment that I hadn't created the > "mailman-hyperkitty.cfg" file. Once created all was well. We really should create a "mailman-lint" utility that checks for things like that. > This was of course after I had begun the installation process again > from scratch. My apologies for the waste of bandwidth and your > time. It's not a waste. There are reasons for having these random include files, but they do make configuration more complex, and these stumbles more likely. I did myself in on the postfix-pgsql patch: not using postmap, the postfix.cfg doesn't need a postmap_command setting right? Wrong! "Wasted" my own time there. :-D Anyway, ask here, somebody probably has done the same before. Maybe it will come up again and you can go, "when I had that error ...." ;-) > couple of issues that others might also stumble over: > > 1. Installing Xapian needed clang. It didn't like gcc I'm pretty sure that installing Xapian requires the C++ compiler (vendor and version) that was used for the packaged library. With the last year I've definitely compiled a Haystack package for Xapian using GCC, clang didn't work and neither did my existing GCC nor the most recent GCC, I had to look up how Ubuntu had compiled it to find the right version (9.3). > 3. For the user "mailman" to access the databases I needed to > change the owner to mailman (even though all privileges has been > granted) ... Can confirm. This was NOT necessary in November 2022; it is now. Probably a PostgreSQL > 13 thing, but since the change is sane and simple I didn't bother to investigate further. Steve

2 years, 3 months

[MM3-users] Mailman 3 Status Update Please?

by Stephen J. Turnbull

Adding a slightly different perspective to Abhilash's and Barry's. ddw David Wilson writes: > From my perspective of being an senior (ie overaged) person > desirous of implementing fully-featured, capable, scalable, > reliable, secure I'm not sure if "secure" is a real requirement, a nice-to-have, or intended as a compliment to Mailman, but "secure" is not something we can claim. Mail is inherently a security problem, because there is no universal way to authenticate senders. It's possible under certain conditions to configure a system to be secure in the sense of allowing only authentic senders, but even when possible it is not easy. Ask John Podesta (for a well-known example) or Matt Tait (aka Twitter's @pwnallthethings, a security expert who has publically admitted that he's come "this close" to clicking on spear-phishing attachments). Mailman itself is a complex application with a very large attack surface. If containerized, it will be rather difficult to exploit the rest of the system, but Mailman itself contains a lot of private data (email addresses and associated display names, which are frequently real names), and in enterprise situations may have access to enterprise databases "containing the whole store". > applications such as Mailman, I am convinced that I am thoroughly > over my head. That's what we're here for! Of course we're volunteers, so our availability is less than 99% reliable and time is limited. I don't know of any consulting services providing Mailman 3 consulting yet, but given the activity of this list I believe we'll see them soon. If you have funding to offer and want to kickstart the process, you could go to the vendors page on our website and talk to some of them. > From my limited perspective, it would seem to me that a 'nice to > have' system would incorporate the following. > > 1. An open container standard configurable system install, compatible > with different web & mail servers, DB utilities, etc; We have a container system which is configurable. However, IMHO "standard" and "configurable/compatible" are incompatible goals. What we can reasonably provide is a full system-in-a-box for people who only want to configure Mailman itself (ie, add lists and users, and configure their settings in the web interfaces). For people with specific desiderata such as a particular mail transport agent or web server different from those provided by our "Mailman-3-in-a-box", they're going to need somewhat advanced sysadmin skills for the forseeable future because the configuration requirements of web services and mail services must be coordinated, and have subtle, implementation-dependent interactions. We hope that the vendors referred to above (including mail hosts, mail consultants, and system management framework vendors like cPanel) will soon start providing more "Mailman 3 in a box" services (both software distributions and as VMs in cloud services), as well as consulting services for those with specific needs not served by existing containerized versions. > 2. Python 3 version Django utilities for archiving and mail list name > management; In progress. > 3. A design/plan from an inside expert perspective stating costs, time > and resources to implement the plan, incorporating crowdfunding to > pay for project. We don't have spare cycles at the moment. None of us actively consult for money on Mailman, which means neither direct engineering capability nor management capability are available. I'm considering this, but since I'm currently a life-long academic with a full-time job for the next few years, I'm not in a big hurry, and would need to acquire skills/partners for the aspects I've no experience in. :-) (I guess that's :-( from your perspective.) With a two-year timeline, if I decide to do it, likely I'd actually open for business in about 1.5-2 years (based on seasonal cycles in free time). I don't know offhand of anyone else even thinking about it. This could change at any time with entry of new developers, of course, but it's only fair to warn you that this is the current status. > 4. As a backup incentive to the crowdfunding plan might be the offer of > an expert to set up a system for each significant amount donated, > say US$1,000, such as might be accomplished by an SSL session on the > target computer/server after the user has specified all necessary > detail as required in a template. We do have ways to donate via our relationship with the FSF, but the same issues described above (no reliable gobs of available time for project oversight or actual development) apply. > I am sure that the program author and other major contributors could > greatly enhance this list. > > In summary, I guess what I am requesting is an overview forecast by half > year period and out for the next two years? For 6 and 12 months out, Abhilash's summary list, and Barry's, all are goals I support. We should also have a plug-in implementating the ARC protocol which improves authentication capabilities by allowing a list's subscribers (more precisely, their mail hosts) to extend transitive trust to senders that the list has authenticated. Although providing such authentication services *in Mailman* is suboptimal and sometimes impossible, we can provide containerized Mailman with that service. Steve -- Associate Professor Division of Policy and Planning Science http://turnbull/sk.tsukuba.ac.jp/ Faculty of Systems and Information Email: turnbull(a)sk.tsukuba.ac.jp University of Tsukuba Tel: 029-853-5175 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

8 years, 9 months

[MM3-users] Re: Unable to get mailman3 working on Ubuntu 20.04 LTS

by Shawn Heisey

On 10/28/2021 5:28 PM, Abhilash Raj wrote: > The instructions are basically in the issue description, pending move to a documentation page: > > https://github.com/maxking/docker-mailman/issues/293 > > If you are upgrading the latest 0.4.x release from 0.3.x, you also want to look at > > https://asynchronous.in/docker-mailman/news/#upgrading-to-040-release Awesome! Thank you for that info! I just upgraded from 0.4.1 (which was the tag I used for the initial install) to 0.4.2 and it all looks good. The lists are still there in the output of this command on the host: docker exec -u mailman mailman-core mailman lists After the upgrade, I sent a test message to one of the mailing lists that looks like it worked perfectly. I assumed that it would be necessary to update the tags in the docker-compose.yaml file, and I did so. Should that be added to the instructions? One thing that was very non-obvious is how to get the containers to start at boot time. A command like this, issued three times with the actual ID values for the containers, took care of it for me: docker update --restart=unless-stopped 0576df221c0b If it is possible to have the docker-compose.yaml file set that flag when it creates the containers, I think that would be a good idea. I did notice that the postorius and mysql docker-compose configs do set the database container (but not the mailman containers) to restart always ... but my limited experience with docker tells me that unless-stopped is a better option. > If you can send a PR for the config you set up for Apache in Github, or just an issue, I can include it in the docs :-) I created an issue and included a sanitized copy of my virtualhost config. Thanks, Shawn

4 years, 6 months

[MM3-users] Re: Badsignature on uwsgi-error.log

by Mark Sapiro

On 3/22/24 09:48, David Partain via Mailman-users wrote: > > Right now, archiving is not working on the new installation, both building the archive on the new installation after the move and for new messages. > > uwsgi-error.log is getting blasted with constant errors along the lines of what follows. I suspect that these errors are why archiving isn't working, but I obviously don't know that: > > Message: BadSignature('Signature "ZWBXqQmWZwHTfa390lLIacpp8NQ" does not match') I'm not sure if this is the issue with archiving or not. > What we have in our config files on the old installation and new installation are (the quotes are exactly as they are in the files): ... > settings.py > > SECRET_KEY = 'somerandomstringiaintputtinginmail' > MAILMAN_ARCHIVER_KEY = 'somerandomstringiaintputtinginmail' > > mailman-hyperkitty.cfg > > api_key: somerandomstringiaintputtinginmail > > All of that says that the value is the same for all three (whether I should have done so or not...) and those settings were carried along to the new installation as well. See my reply at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… As I say there, SECRET_KEY is not related in any way to MAILMAN_ARCHIVER_KEY and api_key. The latter two have to do with archiving and must match. The former is a Django thing and is completely separate. At this point, put ``` SECRET_KEY_FALLBACKS = [ 'F6V0Dr_SvBsx5-cY8vcvLXrX8tA', 'ZWBXqQmWZwHTfa390lLIacpp8NQ', ] ``` in your local Django settings file. If you continue to get BadSignature: Signature "..." does not match' errors, add those unmatched signatures to SECRET_KEY_FALLBACKS. Once you are no longer seeing BadSignature errors, if archiving is still not working, report any errors you are seeing from Mailman's mailman.log and Django's log. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 1 month

[MM3-users] Re: Does hyperkitty show JPEGs in line and what about attachments?

by Mark Sapiro

On 07/12/2017 04:47 AM, Jason Glazer wrote: > > Does anyone know if Hyperkitty can be configured to allow for inline > images to be maintained so that an HTML file looks like a normal HTML > message? > > Also, can attachments to a message under Hyperkitty preserve their name > rather than being "scrubbed" into "attachment-*.*" files? The answer to some of this is at <https://lists.mailman3.org/archives/list/test@mailman3.org/message/N3XVN3DC…>. One question unanswered by that post is what happens with an inline image in an HTML message body. In the original message, the image is referenced by an IMG tag with "src=" pointing to the image MIME part. Since this structure is not maintained in HyperKitty, inline images probably don't work. Also, with respect to Mailman 2.1, if you want the scrubber to preserve file names and extensions, set the following in mm_cfg.py SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = False SCRUBBER_USE_ATTACHMENT_FILENAME_EXTENSION = True and if you want scrubbed HTML to not be HTML escaped so it renders rather than looking like raw html, set ARCHIVE_HTML_SANITIZER = 3 but note this comment from Defaults.py > # 3 - Remove text/html as attachments but don't HTML-escape them. Note: this > # is very dangerous because it essentially means anybody can send an HTML > # email to your site containing evil JavaScript or web bugs, or other > # nasty things, and folks viewing your archives will be susceptible. You > # should only consider this option if you do heavy moderation of your list > # postings. This is an issue with HyperKitty as it appears this is what HyperKitty does and there's no way to turn it off. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 9 months

[MM3-users] Re: Cannot show archives

by qiuhong su

Mark Sapiro wrote: > On 9/26/19 5:48 PM, Qiuhong.Su 蘇秋紅 wrote: > > Hi all, > > After I setup mailman3 and run mailman-suite, I can do: > > > > > > Register user > > > > Login > > > > Create new Domain > > > > Create new List > > > > Subscribe to the list > > When I try to send email to the list by run command: echo “test email” | mail –s “test > > email” test(a)example.com > > User test can receive this email, but I cannot find it on Archives, and other members > > cannot receive this email too. > > > > > > You say "User test can receive this email". Is test(a)example.com a user > or the list's posting address? > If you are saying that test(a)example.com should be the list's posting > address, but the mail is instead delivered to the user test(a)example.com, > you have not set up your MTA to properly deliver list mail to Mailman. > See https://mailman.readthedocs.io/en/latest/src/mailman/docs/mta.html. After check MTA settings, still cannot resolve this issue. I create a new list "list1", and after subscribe it, send an email to list1(a)example.com And then check ./var/archives/hyperkitty/spool/, ./var/messages Both are empty. Click "Archives" it will access http://example.com/hyperkitty/, and show "No archived list yet." Could you help me? Here is my mailman.cfg: ------------------------------------------------------------------ [mta] verp_configurations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 lmtp_host: example.com lmtp_port: 8024 smtp_host: example.com smtp_port: 25 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes -------------------------------------------------------------------------------- My mailman-hyperkitty.cfg, example.com can be resolved to 10.0.0.120 -------------------------------------------------------------------------------- [general] base_url: http://10.0.0.120/hyperkitty api_key: SecretArchiverAPIKey -------------------------------------------------------------------------------- In mailman-suite settings.py, already add '10.0.0.120' to MAILMAN_ARCHIVER_FROM MAILMAN_ARCHIVER_FROM = ( '127.0.0.1', '::1', '10.0.0.120' )

6 years, 7 months

[MM3-users] Re: How to import mailman2 into mailman3 in Docker, getting error with archives.

by Abhilash Raj

On 9/15/21 11:30 AM, Jens Günther wrote: > For importing the archives, it's the mailman-web container. For me it > was like: > > python manage.py hyperkitty_import -l listxy(a)somedomain.org > /opt/mailman-web-data/listxy.mbox > > Before I connected into container as the user mailman! Also, you want to add the listxy.mbox at /opt/mailman/web/listxy.mbox on your host for the above command to work. > > Hope this helps. > > Am 15.09.21 um 19:36 schrieb bob B: >> I know you can't run mailman commands in the docker images and I have >> to copy the data to an area where he docker images can access it, but >> in looking that the commands I got the list settings to import >> >> docker exec -it mailman-core mailman import21 >> [REDACTED](a)REDACTED].REDACTED].org >> /opt/mailman/migration/config.pck *** this worked >> >> >> But having issues importing the archives? do i run this on >> mailman-core OR mailman-web? I tried both but it does not like >> python? >> >> docker exec -it mailman-core python manage.py hyperkitty_import -l >> [REDACTED](a)REDACTED].REDACTED].org /opt/mailman/migration/[REDACTED].mbox >> OCI runtime exec failed: exec failed: container_linux.go:380: starting >> container process caused: exec: "python": executable file not found in >> $PATH: unknown >> _______________________________________________ >> 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/ >> > _______________________________________________ > 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)

4 years, 7 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/26/24 10:41, Bryan Fields wrote: > On 7/26/24 1:30 PM, Bryan Fields wrote: > >> mailman=> \c mailmanweb >> You are now connected to database "mailmanweb" as user "mailman". >> mailmanweb=> SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM >> date_active) < 1000; >> id | thread_id | date_active | >> category_id | mailinglist_id | starting_email_id >> -------+----------------------------------+------------------------+-------------+----------------+------------------- >> 35670 | GHLCKUC7TDEBAI27SKRQN5PWX3TGB26Q | 0102-04-15 20:06:12+00 >> | | 3 | 150555 >> (1 row) >> >> mailmanweb=> SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM >> date) < 1000; >> id >> -------- >> 136872 >> 150555 >> (2 rows) >> >> Does this mean it imported archives with an invalid date somehow? Yes, I suspect this bad date is part of the issue. I would do a few things. First, SELECT message_id FROM hyperkitty_email WHERE thread_id = 35670; If this returns just the one message_id, I would then DELETE FROM hyperkitty_thread WHERE id = 35670; DELETE FROM hyperkitty_email WHERE id = 150555; and see if that fixes the internal server error when accessing the archive. I would also SELECT * FROM hyperkitty_email WHERE id = 136872; and maybe update the `date` in that entry. After deleting that one message and thread, you can make a mbox with just the one message with the date corrected and run hyperkitty_import with `--since 2000-01-01` and that mbox as input to add the message back to the archive. Also, FYI, assuming those messages with very old Date: headers had reasonable unix from dates, the hyperkitty/contrib/cleanarch3 script would fix them, except you have to get the script from https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… or https://www.msapiro.net/scripts/cleanarch3 because the script in the latest release has a bug. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: Managing mailman3 via curl (using bash-scripts or perl-scripts)

by Jeremy Stanley

On 2025-09-30 00:15:09 +0900 (+0900), Stephen J. Turnbull wrote: >Jeremy Stanley writes: > >> Note that "activating" a venv is typically not necessary (I never do >> it), you just have to make sure to type the full path to executables >> in the bin directory of the venv when running them, or add that >> directory to PATH in your shell environment. > > I don't recommend the latter to folks who aren't experienced with > Python. It can be confusing if you get a different Python from the > one you expect due to upgrades/installations of other Python versions. > Typing full paths or creating shell aliases/functions containing the > full path is safe. Yes, I should have included the caveat that adding a venv's bin/ directory to your PATH should only be for temporary measure or e.g. if you have a dedicated account you want to log into specifically for running those commands. This is part of what the activate script in a venv does too, FWIW, it just gets undone again by the deactivate command if/when you remember to run it later. While understanding executable search order helps avoid accidentally shadowing other commands like your Python interpreter executable (append vs prepend), obviously altering your shell's PATH should not be done unless you fully comprehend the risks, which is why I suggested using the full path to the executable as the first recommendation. A middle ground I take between those two is to add ~/bin to my PATH and then populate it with symlinks to executables in various venvs that contain my Python-based tools. This gives me the flexibility to only include the specific executables I want in my command search while omitting the rest. -- Jeremy Stanley

7 months

[MM3-users] Mails for 1 specific mailinglist not being send and looping in out queue

by Eric Broens

For some reason, the mail for 1 specific mailinglist doesn't get distributed. It worked fine before, and no changes have been made.The mailman3 debug log shows that mailman keeps attempting to distribute the mail.The mailman3 error log show that there is a connection failure to port 25.A tcpdump however shows that there are *NO* further connection attempts on port 25 (postfix) to distribute this mail.Also after stopping and starting mailman3 again, no further connection attempts to the mailserver (postfix) are being made for this mail.Using qfile, the pck file of this mail looks fine. New emails on this specific mailinglist are not distributed either.For all other mailinglists on this server, and which are on the same domain, there are no problems. Does anyone know how to get this mailinglist functioning properly again, and what is causing this issue?Below are the relevant extracts from the log files for the particular case. mailman smtp.log: Jan 09 12:00:57 2021 (1571668) Peer: ('127.0.0.1', 51752)Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) handling connectionJan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'LHLO ****'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'MAIL FROM:<****@****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) sender: *****@*****Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'RCPT TO:<*****@*****>'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) recip: ******@********Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'DATA'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) Data: b'QUIT'Jan 09 12:00:57 2021 (1571668) ('127.0.0.1', 51752) connection lost... Message has been archived properly, mailmansuite.logINFO 2021-01-09 12:01:00,277 1164814 hyperkitty.views.mailman Archived message <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> to *** mailman error.logJan 09 12:01:00 2021 (1571670) Cannot connect to SMTP server 127.0.0.1 on port 25 mailman debug.log Jan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: validate-authenticityJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: mime-deleteJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: taggerJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: member-recipientsJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: avoid-duplicatesJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanseJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cleanse-dkimJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: cook-headersJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: subject-prefixJan 09 12:00:58 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: rfc-2369Jan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-archiveJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-digestJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-usenetJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: after-deliveryJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: acknowledgeJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: dmarcJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: arc-signJan 09 12:00:59 2021 (1571671) <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com> pipeline default-posting-pipeline processing: to-outgoingJan 09 12:00:59 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:00:59 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571671) [PipelineRunner] finishing filebase: 1610190058.1544778+e952a743e8df115e8fff9c60f98b189d4800e7e6Jan 09 12:00:59 2021 (1571671) [PipelineRunner] doing periodicJan 09 12:00:59 2021 (1571671) [PipelineRunner] committing transactionJan 09 12:00:59 2021 (1571671) [PipelineRunner] checking short circuitJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 1Jan 09 12:00:59 2021 (1571671) [PipelineRunner] starting oneloopJan 09 12:00:59 2021 (1571671) [PipelineRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571674) [VirginRunner] starting oneloopJan 09 12:00:59 2021 (1571674) [VirginRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571669) [NNTPRunner] starting oneloopJan 09 12:00:59 2021 (1571669) [NNTPRunner] ending oneloop: 0Jan 09 12:00:59 2021 (1571675) [DigestRunner] starting oneloopJan 09 12:00:59 2021 (1571675) [DigestRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>Jan 09 12:01:00 2021 (1571664) [ArchiveRunner] starting oneloopJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing filebase: 1610190059.1079752+2644b9a3eab17d52203a2c2648a1db5ff146eb6dJan 09 12:01:00 2021 (1571664) [ArchiveRunner] processing onefileJan 09 12:01:00 2021 (1571666) [CommandRunner] starting oneloopJan 09 12:01:00 2021 (1571666) [CommandRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] finishing filebase: 1610190059.1591551+dcfcb22d5156b0a4d4267eabf83c5bb68f945e41Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] doing periodicJan 09 12:01:00 2021 (1571670) [OutgoingRunner] committing transactionJan 09 12:01:00 2021 (1571670) [OutgoingRunner] checking short circuitJan 09 12:01:00 2021 (1571670) [OutgoingRunner] ending oneloop: 1Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] starting oneloopJan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing filebase: 1610190060.1351898+91420b755194277d1236a36b6e2195eff547c8b0Jan 09 12:01:00 2021 (1571670) [OutgoingRunner] processing onefileJan 09 12:01:00 2021 (1571667) [IncomingRunner] starting oneloopJan 09 12:01:00 2021 (1571667) [IncomingRunner] ending oneloop: 0Jan 09 12:01:00 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:41 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>...Jan 09 12:16:42 2021 (1571670) [outgoing] <function deliver at 0x7f612989dea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>......Jan 09 14:06:30 2021 (1601275) [outgoing] <function deliver at 0x7f038df80ea0>: <91B190F7-EEA3-4FA7-9808-2C35774E665A(a)gmail.com>... Thanks in advance,Eric

5 years, 3 months

[MM3-users] Re: mail host choices when creating a new list

by Abhilash Raj

On Tue, Oct 24, 2017, at 12:24 PM, Andrew Hodder wrote: > Abhilash, > I'm not sure what you're referring to, there's no "web hosts" in the > admin panel and I already added the "mail hosts" there (of the four > added, only the first one shows up in the postorius drop down). Ah! I mis-read your email. You need to add new domains in Postorius before you can create new lists using them. You are looking for '/postorius/domains/', add a new domain there, and then it will show up in the 'mail hosts' in create-new-list form. > > Sincerely, > > Andrew Hodder Systems Administrator Support Operations, Afilias E- > mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 > 416.646.1541> > On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> Hi Andrew, >> >> On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: >> > Hi! >> > >> > So, I'm trying to create a new list and pick one of the other mail >> > domains we have configured (from the django admin panel), yet in >> > the "Create New List" page in postorius, I see only a single >> > option (the first domain we'd added/set as the default) in the drop- >> > down under "Mail Host". Am I missing somewhere else I need to add >> > alternative mail domains to? Thanks in advance! >> >> Yes, you can add new 'Web Hosts' from the Django's Admin console>> (admin/django_mailman3/maildomain/). Note that you need to be a >> superuser to do this. >> >> >> -- >> Abhilash Raj >> maxking(a)asynchronous.in -- Abhilash Raj maxking(a)asynchronous.in

8 years, 6 months

[MM3-users] Re: Hyperkitty Missing Theme/Style Sheets?

by Simon Hanna

On 10/26/2017 11:51 PM, Abhilash Raj wrote: > On Thu, Oct 26, 2017, at 11:23 AM, Andrew Hodder wrote: >> I have an odd one, my Hyperkitty is functionally working fine (archived >> several lists without issue, can login/out), however I must have done >> something wrong during it's setup as it's layout is completely broken >> (and >> it keeps throwing Example.com up in the top-left corner). > You need to change SITE_ID in your Django's configuration to point to > your domain name you want to be show there. Default is set to > `example.com` which corresponds to SITE_ID=1 in the Django's > configuraiton. > > How to find the SITE_ID of your domain? > > This is rather no-so-nice right now, you will basically have to go to > the admin console (/admin/) and login as admin. Then you visit > `/admin/django_mailman3/maildomain/` and you should see your domain > there. Clicking on it will how your it's id in URL bar, like > /admin/django_mailman3/maildomain/2 or something. > > I understand this is rather difficult thing to do, there is an issue > open to make this information visible in the UI. Ideally, SITE_ID is > sequential, so if you have only one domain, it is most probably 2. You shouldn't get it from maildomain but the real site instead which is under the sites entry /admin/sites/site/ Also the default is actually 1 and not 2 Django automatically creates a site with id 1 if the sites framework is activated. Only if you delete the existing entry and add another, you will get an id of 2. Just editing will leave you with 1. as mentioned in the issue on gitlab, I think we should just drop the SITE_ID or maybe only enable it for DEBUG==True

8 years, 6 months

[MM3-users] Re: problem with postorius initial setup

by John Covici

On Tue, 16 Mar 2021 12:14:36 -0400, Stephen J. Turnbull wrote: > > John Covici writes: > > > Hi. I am trying to setup postorius, but I have run into a problem. I > > am using the example project, except I am using postgresql instead of > > sqlite3. I ran python manage.py migrate which was successful. > > > > On running the development server I get: > > Exception in thread django-main-thread: > > Traceback (most recent call last): > > File > > "/usr/lib/python3.8/site-packages/django/utils/module_loading.py", > > line 20, in import_string > > return getattr(module, class_name) > > AttributeError: module 'postorius.middleware' has no attribute > > 'APICountingMiddleware' > > This appears to be another version mismatch. The > APICountingMiddleware appears to be a debugging or development > instrumentation tool. It was added on 2021-02-28, so it's very > recent. Somehow your Postorius settings.py is newer than your > Postorius middleware.py. I would guess you have checked out or pip'ed > a very recent version of Postorius but the example_project is picking > up an older version, possibly from the Gentoo package. Why that could > happen depends on whether you've set up a venv for the up-to-date > Postorius, whether it's active, and so on. I think I know what is happening, but not how to fix. The example_project which the docs told me to get is from the postorius git which is, of course, recent, whereas the postorius I have from the gentoo package is 1.3.3, which is not that old, but maybe not up to the git version. Should I be using the git version? -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una covici(a)ccs.covici.com

5 years, 1 month

[MM3-users] Re: cannot import name 'parse_header' from 'django.http.multipartparser

by Stefan Bauer

Thank you Mark for your swift reply :) Am Do., 27. Feb. 2025 um 20:32 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 2/26/25 07:40, Stefan Bauer via Mailman-users wrote: > > Dear Users, > > > > i recently tried to upgrade to latest MM3 and followed this[1] steps. > > > > However > > > > (venv) $ mailman-web migrate > > > > fails with: > > > > from rest_framework import mixins, views > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/views.py", > > line 15, in <module> > > from rest_framework.request import Request > > File > "/opt/mailman/venv/lib/python3.10/site-packages/rest_framework/request.py", > > line 17, in <module> > > from django.http.multipartparser import parse_header > > ImportError: cannot import name 'parse_header' from > > 'django.http.multipartparser' > > > (/opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py) > > (venv) mailman@edmmal03$ vi > > > /opt/mailman/venv/lib/python3.10/site-packages/django/http/multipartparser.py > > > > Could this be a broken dependency? > > > You have an incompatible configuration. > django.http.multipartparser.parse_header was removed in Django 4.2. See > https://docs.djangoproject.com/en/5.1/releases/4.2/#miscellaneous > > Your version of djangorestframework is incompatible with Django>=4.2. > Try in your venv > ``` > pip install --upgrade djangorestframework > ``` > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com >

1 year, 1 month

[MM3-users] Re: Where to start looking?

by Mark Sapiro

On 3/11/26 17:05, Paul Tomblin via Mailman-users wrote: > So I imported all our mailman2 lists into mailman3, and it appears it didn't preserve passwords. So my wife (who administers 3 lists of her own) tried to use the reset password link (multiple times) but she never gets the email. I don't see any outgoing email to her in mail.log, or any of the mailman logs. I do the exact same thing as her and I get the email. Any suggestions on what I should be looking for? Mailman 2.1 passwords have no meaning in Mailman 3 and aren't imported. in MM 2.1 passwords were per list per member. In Mailman 3 core, there are no corresponding passwords. Passwords are for logging in to the web UI which is separate. Bottom line. You need to go to <https://your.site/accounts/signup/> and signup for an account. Then if you have more than one email address, go to <https://your.site/accounts/email/> and add your other addresses. Then, once logged in you should be able to manage any lists for which one of your addresses was imported as an owner and moderate any lists for which one of your addresses was imported as a moderator. Your wife can't get a password reset email because she hasn't signed up for an account and there is no password to reset. Apparently you did sign up for an account or maybe if you've configured any social account logins, you logged in with one of those which will create an account for you. You might find <https://docs.mailman3.org/en/latest/django-primer.html> useful. It discusses a bit about Django which is the web framework for Postorius and HyperKitty. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 month, 2 weeks

[MM3-users] Re: Flushing/syncing hyperkitty with mailman

by Mark Sapiro

On 06/16/2018 06:38 PM, Eric Abrahamsen wrote: > > > A bump for this, I've been getting this series of errors once a minute > for weeks now. There must be some way to clear out dangling thread > references? And I take it that for the meantime we shouldn't be using > the "delete thread" feature of hyperkitty... > >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:1 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:2 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> [Q] INFO Process-1:3 processing [rebuild_email_cache_votes] >> [Q] ERROR Failed [rebuild_email_cache_votes] - Email matching query does not exist. >> [Q] INFO Process-1:4 processing [rebuild_thread_cache_votes] >> [Q] ERROR Failed [rebuild_thread_cache_votes] - Thread matching query does not exist. >> >> Is there something more I should be doing to sync hyperkitty's database >> with mailman? I've got the crontab file in place, and that appears to be >> running without error. Anything else? Except that 'django-admin runjobs minutely' is probably what's producing the errors. You might try 'django-admin runjob empty_threads' (normally a monthly job) or 'django-admin runjob thread_order_depth' (normally a yearly job). I don't know if they will clear this up or not, but I don't think it would hurt to try. See 'django-admin runjob --list' to see the various jobs and note that 'django-admin runjob update_index' which runs minutely and does an incremental update is not the same as 'django-admin update_index' which only runs manually and does a full search index update. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 10 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo Oku

On Sat Oct 22, 2022 at 1:40 PM WAT, Stephen J. Turnbull wrote: > Onyeibo Oku writes: > > (backtrace reformatted for readability) > > > Oct 22 04:13:55 mail.server.tld mailman[9253]: PermissionError: [Errno 13] > > Permission denied: > > '/opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10.egg-info/PKG-INFO' > > That's just an ordinary attempt to read a file, nothing special about zope. > It seems that that package was installed with the wrong ownership or > permissions. Most likely you installed the package as root rather > than the mailman user. > > Everything in a venv should be owned by the user:group it is intended > for.[1] Assuming that the user that Mailman processes are running under > is "mailman" with group "mailman", then > > chown -R mailman:mailman /opt/mailman/venv > > should do the trick. > > Steve Strangely, all files in /opt/mailman/venv belong to the mailman group ls -lh /opt/mailman/venv/lib/python3.10/site-packages/zope* -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.component-5.0.1-py3.8-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.configuration-4.4.1-py3.9-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.event-4.5.0-py3.6-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.hookable-5.2-py3.10-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.i18nmessageid-5.0.1-py3.10-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.interface-5.5.0-py3.10-nspkg.pth -rw-r--r--. 1 mailman mailman 529 Oct 19 18:31 /opt/mailman/venv/lib/python3.10/site-packages/zope.schema-6.2.1-py3.8-nspkg.pth and so it goes in the subdirectories. Yet I set "mailman" as the User and Group in the systemd service file. Onyeibo

3 years, 6 months

[MM3-users] Another interesting error...

by Darren Smith

So it appears that there was a message sent to one of our mailing lists that was put into the held message queue. However, when attempting to go to the message to do the moderation, the web page returns and Error 500. Looking in the mailman log, I found this: Apr 23 14:21:02 2018 (17878) REST request handler error: Traceback (most recent call last): File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/database/transac tion.py", line 50, in wrapper rtn = function(*args, **kws) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/wsgiapp.py" , line 214, in __call__ return super().__call__(environ, start_response) File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", line 227 , in __call__ responder(req, resp, **params) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 167, in on_get resource = self._make_collection(request) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" , line 159, in _make_collection for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/helpers.py" , line 159, in <listcomp> for resource in collection] File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 157, in _resource_as_dict resource = self._make_resource(request.id) File "/opt/mailman3/conda/lib/python3.6/site-packages/mailman/rest/post_modera tion.py", line 100, in _make_resource make_header(decode_header(resource['subject']))) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in make_he ader h.append(s, charset) File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in append s = s.decode(input_charset, errors) UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: illegal multibyte sequence It LOOKS as if there might be a character in the email somewhere - possibly in the subject or sender fields? - that is somehow unexpected. I am attempting to find the held message - can someone point me where I can go to see the message so that I can see what might be causing the problem? -Darren

8 years

[MM3-users] Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 14/2/21 18:42, Mark Sapiro wrote: > On 2/14/21 3:21 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I did some exploration this morning (Spain time) in the weblate >> statistics and archives and I found that the changes done from >> Victoriano and me were recorded. I did a screencopy of all that if >> someone has any doubt about it. I downloaded this files: >> >> -rw-r--r-- 1 1002 wheel 11037 Feb 14 10:57 gnu-mailman-django-mailman3-es.po >> -rw-r--r-- 1 1002 wheel 34511 Feb 14 10:54 gnu-mailman-hyperkitty-es.po >> -rw-r--r-- 1 1002 wheel 143758 Feb 14 10:51 gnu-mailman-mailman-es.po >> -rw-r--r-- 1 1002 wheel 104997 Feb 14 10:49 gnu-mailman-postorius-es.po >> >> The thing is that they differ from the .po installed via pip upgrade. >> Mostly, as said, postorius, hyperkitty and django_mailman3. > > The latest packages in PyPI (pip) were released on Feb 2 except for > django-mailman3 which was released on Jan 15. They don't include updates > after those dates. > And I say that I (and others ) have made translations in postorius, hyperkitty an Django_mailman3 in January. Yes, I've made some changes in february 10th, but It were a pair of messages. But that's all about this from me. If in the next upgrade I find that there is any translation missing, I know, thanks to you and Victoriano, how to handle it. And if some new admin installs mailman 3 and try to localize it to spanish and comes to this list to ask how to do a more complete translation... well, these messages can point him or her to the right direction. My postorius web access to the lists is now almost completely translated to spanish and now I can help the users without hesitating language problems. Thanks. Thanks a lot.

5 years, 2 months

[MM3-users] Re: mailman 3.x upgrade and downgrade

by Mark Sapiro

On 7/12/22 6:12 AM, skooperit(a)gmail.com wrote: > Hi all, > > I have a few contradictory questions. > > 1. How to upgrade the 3.x version? > > 2. Is it possible to migrate (downgrade) the lists from mailman 3.x to 2.1? > > 3. If so, what would be the best way to do that? > > > My mailing list server is running on a CenOS-7x with postgreSQL and the following mailman packages: > > django-mailman3 1.3.5 > mailman 3.3.2 > mailman-hyperkitty 1.1.0 > mailman-web 0.0.3 > mailmanclient 3.3.2 > postorius 1.3.3 > > We have ~200 lists with more than a decade of history. So you have installed Mailman 3, apparently following https://docs.mailman3.org/en/latest/install/virtualenv.html. There is a caveat. Current released versions of HyperKitty (I don't see your version above) don't work with mistune >= 2.0.0. This is https://gitlab.com/mailman/hyperkitty/-/issues/431, fixed by https://gitlab.com/mailman/hyperkitty/-/merge_requests/379 but not yet released. If your installed mistune is not 2.0.0rc1, you can work around this with this patch ``` --- a/hyperkitty/lib/renderer.py +++ b/hyperkitty/lib/renderer.py @@ -4,7 +4,7 @@ from django.conf import settings import mistune from mistune.plugins.extra import plugin_url -from mistune.scanner import escape_html, escape_url +from mistune.util import escape_html, escape_url class MyRenderer(mistune.HTMLRenderer): ``` Or you can downgrade mistune with ``` pip install mistune==2.0.0rc1 ``` in your virtualenv. To answer your questions, to migrate your lists, you use `mailman import21` and to migrate archives, `mailman-web hyperkitty_import`. Give these commands with the `--help` option for more info. Downgrading lists from Mailman 3 to Mailman 2.1 is not currently possible. There is no inverse to `mailman import21`. You can export a HyperKitty archive as a mbox to use as input to Mailman 2.1s bin/arch. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Enforcing SSO and subscription options

by dlb-ml＠anl.gov

Contrary to the messages I found in the archive, rather trying to delete or remove the social login portion of the sign in page, I'm looking to see if there's any way to isolate the third-party login section and prevent local account sign in and sign up. This way, we can ensure that the people within our organization are using a stronger auth method that prioritizes MFA, rather than just username/password. To do this, our plan is to block signups using "ACCOUNT_ADAPTER = 'django_mailman3.views.user_adapter.DisableSignupAdapter'" and to remove the portions of the login template such that the username/password/forgot password fields are removed, leaving just the button to our SSO instance. I'm anticipating that this should be sufficient to block username/password sign ins, and is resistant to page manipulation due to CSRF tokens, but I wanted to ask to see if there was a better way, like an official configuration (which I have not found yet). I did see that there is the SOCALACCOUNT_ONLY option, as provided by allauth (https://docs.allauth.org/en/latest/socialaccount/configuration.html) but that broke any attempt to display the sign in page, and I'm assuming is not supported with the current version of MM3. Is my plan to modify the templates viable? Additionally, because external users would not have access to their own dashboards within the web UI, and since we are planning on disabling anonymous subscriptions with "SHOW_ANONYMOUS_SUBSCRIBE_FORM=False", the only two viable ways to subscribe to a list for them would be: 1) Send a request directly to the list owner or a superadmin to subscribe/unsubscribe the address 2) Allow email commands to subcribe/unsubscribe users (i.e. $LISTNAME-join@$DOMAIN) Given the discussions on disabling the anonymous subscription form, are the email commands a less spam-susceptible solution or are they just as vulnerable as the form? Thanks

1 year, 2 months

[MM3-users] Re: Using external services for deliverability?

by Brian Carpenter

On 6/30/20 9:56 AM, tom(a)gather.coop wrote: > I have a Mailman 3 server up and running but I'm terrified to migrate to it from my existing Mailman 2 provider for fear that services like Gmail will randomly start blacklisting my IP with little I can do about it. I have SPF records set up so I'm hoping I'll be Ok but I'd like to have a backup plan. > > Has anyone ever tried using an external service like Mailgun or Sendgrid as a relay? I tried both but couldn't get either to work due to their sender authentication mechanism. They want all 'From:' headers to be from domains that are pre-authenticated as senders. But Mailman keeps the 'From' header from the original sender so it won't match any authenticated domains. Right? There is no reason to be afraid if you are sending out legitimate communications. SPF records will help. You will also need to enable DMARC mitigation on your lists and Mailman 3 does that very well as Mailman 2 did. It also helps if you sign your outbound mail with DKIM. With those 3 things in place, you should have no problem sending mail. Keep in mind AT&T will probably block you if the IP address you are using is new. That is standard practice for them. It's easy to get that block remove. Same goes for Comcast using their Vader RBL. I have found Gmail to be the easiest mail provider to work with. I don't think I have ever seen a permanent block from them. But then again, I don't host spammers. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 10 months

[MM3-users] Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Mark Sapiro

On 10/25/20 8:22 AM, Shashikanth Komandoor wrote: > Hi Team, > > I am currently running Mailman 3 with version 3.3.2rc2 and in > built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.9 version > with default values. As of now, we don't have any lists and just installed > software components only. > > After the installation and configuration, I have tried > creating the domains and lists. I was successful in creating them but when > I tried to login and browse the lists using LDAP authentication, I am > getting the "Mailman REST API not available. Restart Mailman core". > > I see the below trace in the mailmansuite.log. > > *Traceback (most recent call last): File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 119, in __getattr__ return self._get(name) File > "/var/lib/mailman/venv3/lib64/python3.6/site-packages/mailmanclient/restbase/base.py", > line 86, in _get raise KeyError(key)KeyError: 'get_requests_count ... > > I don't see any error messages in the mailman.log. And I > also executed a few curl commands in getting the details of the lists > created and list info which I got their results successfully. > > Could you please guide where exactly I am missing or do I > need to make any changes in my customizations ? I think the issue is your mailmanclient is too old. The version of Postorius you are running requires mailmanclient >3.3.1 which is only available from GitLab <https://gitlab.com/mailman/mailmanclient>. What version of Postorius is this? It appears to be >1.3.3. If you install Postorius from unreleased code on GitLab, you have to install all of mailman, mailmanclient and django-mailman3 as well. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

[MM3-users] Re: how to delete a list member using the Linux command line

by Mike Wertheim

Thanks! I'm on Debian 10, and the latest Mailman version that's available in the Debian package manager is 3.2.1. I really have no idea how packages get updated in the package manager. Do you know why Mailman 3.3.1 is not yet available in Debian's package manager? (Does someone on the Mailman project need to push it there? Or does someone on the Debian side need to pull it in?) On Fri, Jun 19, 2020 at 1:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/19/20 7:29 AM, Mike Wertheim wrote: > > I have Mailman 3.2.1 installed (on Debian Linux), using exim4 as the MTA. > > > > I have been trying to figure out how to use the Linux command line to add > > members to a list and delete members from a list, but am having trouble > > with deleting. > > The --delete option to `mailman members` was introduced in Mailman > 3.3.0. Your version doesn't have it. > > Note that as of the next (3.3.2) release, the --add, --delete and --sync > options to `mailman members` are deprecated in favor of new `mailman > addmembers`, mailman delmembers` and `mailman syncmembers` commands. > > It should be possible for you to install the current versions of all of > these without upgrading just by copying the `cli_*members.py` files from > <https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/commands> > to the `mailman/commands/` directory in your current installation. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

5 years, 10 months

[MM3-users] Cannot setup HTTPS support for mailman3-web

by jean-christophe manciot

Ubuntu 20.04 mailman3 3.2.2-1 mailman3-web 0+20180916-10 python3-django 2:2.2.9-2ubuntu1 In ```/etc/mailman3/uwsgi.ini``` (example.org is defined in the local /etc/hosts as 10.0.0.1): ``` [uwsgi] # Port on which uwsgi will be listening. ### suwsgi: uwsgi protocol over TLS uwsgi-socket = example.org:8430 # https://uwsgi-docs.readthedocs.io/en/latest/HTTPS.html?highlight=ssl https = /etc/ssl/example.org.crt,/etc/ssl/example.org_rsakey.pem.decrypted,HIGH ... # Drop privileges and don't run as root. uid = www-data gid = www-data ... ``` I suppose that uwsgi reads the certificate & its private key before dropping root privileges. Right now, uwsgi cannot access them as ```www-data```. In ```/etc/mailman3/mailman-web.py``` (symlinked to django settings.py) : ``` ... SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' ... POSTORIUS_TEMPLATE_BASE_URL = 'https://example.org:8430' ``` In ```/etc/nginx/sites-enabled/example.org.conf``` ``` ... location / { include /etc/nginx/uwsgi_params; # upstream app server uwsgi_pass suwsgi://example.org:8430; } ``` uwsgi is listening on the right address/port: ``` # networks-list-connections.sh | grep :8430 tcp 0 0 10.0.0.1:8430 0.0.0.0:* LISTEN 33 54336045 1768187/uwsgi ``` Despite those settings and all the relevant systemd services restarted, I get ```502 Bad Gateway``` while browsing to ```https://example.org/postorius/lists/?all-lists``` (or any other page) with the following error nginx message: ``` *1 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 10.0.0.1, server: example.org, request: "GET /postorius/lists/?all-lists HTTP/2.0", upstream: "suwsgi://10.0.0.1:8430", host: "example.org", referrer: "https://example.org/postorius/lists/" ``` Of course, without those specific https/suwsgi settings, everything works fine. What am I missing/doing incorrectly? Does uwsgi need access to the certificate/private key while running as non-root for instance?

6 years, 3 months

[MM3-users] Re: Imported Digest Settings

by Mark Sapiro

On 2/16/21 7:56 AM, Brian Carpenter wrote: > I am still seeing digest formatting issues with the import of Mailman 2 > lists into Mailman 3. I am running the latest stable version of Mailman > 3 core which is 3.3.3. This is what my client reported: > > >> For the last three REDACTED digests I have been getting unusual and >> unreadable characters? See example below. >> >>> Begin forwarded message: >>> >>> *From: *REDACTED >>> *Subject: *REDACTED*Digest, Vol 2453, Issue 2* >>> *Date: *February 13, 2021 at 12:30:24 AM PST >>> *To: *REDACTED@REDACTED >>> *Reply-To: *REDACTED@REDACTED >>> >>> �P*+]4�LaG@��[� S� XZ[ [�� \� �X�Z\��[ۜ� ‚] [� [�ܙ‚� � �X��ܚX�H ܈ ... > > So the questions I have are: > > 1. Why does the formatting of digests change for some members when > coming from MM2 to MM3? Could this be <https://gitlab.com/mailman/mailman/-/issues/473>? That should be fixed in Core 3.3.3. > 2. What proble does the above example reveal? Insufficient headers to begin to guess. > 3. What is the best approach to mitigate these issues? Depends what the issue is. The two most obvious approaches are upgrade to Mailman 3.3.3 if you aren't already there and switch from plain to MIME digests, but I would really like to see the full raw source of this digest messages to try to see if there is some other issue. > What I did: I had the client change the list member's digest setting > from plain-text to mime. Was that the right instruction to do? It will probably help, but if this is Mailman 3.3.3, there's still a bug somewhere that needs to be diagnosed and fixed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users] Re: Mailman sends Welcome emails, but does not send [List] postings emails

by Mark Sapiro

On 5/31/23 22:49, justfixit(a)marilynstrother.com wrote: > FWIW, looking back at this time period in mailman.log the only instances of "runner exiting" are in groups, at the times when I had manually issued "mailman restart" to try a few different debug logging options. I.e. there was no single / multiple record of "runner exiting" from e.g. an unexpected program fault. When you issued a restart and the logs show runners restarting, did all the runners restart or was one or more missing. If you grep the log for `runner started`, you should see groups of messages like Jun 01 08:00:27 2023 (21930) in runner started. Jun 01 08:00:27 2023 (21938) virgin runner started. Jun 01 08:00:28 2023 (21932) bounces runner started. Jun 01 08:00:28 2023 (21935) command runner started. Jun 01 08:00:28 2023 (21941) retry runner started. Jun 01 08:00:28 2023 (21934) archive runner started. Jun 01 08:00:28 2023 (21931) lmtp runner started. Jun 01 08:00:28 2023 (21942) pipeline runner started. Jun 01 08:00:29 2023 (21939) out runner started. Jun 01 08:00:29 2023 (21936) digest runner started. Jun 01 08:00:29 2023 (21937) nntp runner started. Jun 01 08:00:30 2023 (21940) task runner started. and if any runners are sliced, there will be multiple entries for that runner, one per slice. Also, because of the way the `rest` runner is run, it will be in the list on a start but not on a restart. If a runner had previously died so it was not running when you did the restart, it won't be started and will be missing from the above list. In order to restart runners which have died, you need to do `mailman stop` followed by `mailman start` as opposed to `mailman restart` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

[MM3-users] Re: Can't post to my own list from HyperKitty

by Mark Sapiro

On 4/10/25 18:30, MegaBrutal via Mailman-users wrote: > > Thanks, I successfully removed my unwanted address, so it now doesn't > appear anywhere. (Looks like .remove(n) wasn't needed, it only gave an > exception, and the settings were saved even without commit() – which is > concerning because I would have assumed that I can cancel transactions by > omitting it.) As it says when you first invoke `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. > However, the problem still persists: I can't post to the list from > HyperKitty. In this regard, nothing has changed since my original report. > I'm subscribed to the list with my primary, preferred address, which is the > GMail address right now. So your gmail.com address is a list member and your megabrutal.com address is only an owner. Is that correct? What if you add your megabrutal.com address as a list member - you can set delivery to disabled if you don't want it to get mail. Does that work? How are you logging in to the web UI. I am concerned, because if you are logging in to an account that has both addresses linked, you should see the ``` This message will be sent as: user(a)example.com Link another address ``` line below the text box in the message dialog and if you click on user(a)example.com, you should be able to pick the other address. Also, if you go to https://example.com/user-profile/ you should see a Primary email: and Other emails:. Do you see that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: Not able to start mailman server

by Mark Sapiro

On 8/5/21 12:53 AM, Kartheek Reddy Bondugula wrote: > Hi, > > I am trying to setup postorius using this website - > > https://docs.mailman3.org/projects/mailman/en/release-3.0/src/mailman/docs/W... That documentation is out of date. Start at https://docs.mailman3.org/en/latest/ > I am trying to create a mailling list and it web interface for the users in my group > > The command 'pip install -e ./'(python3) runs successfully but still i am not able to start the server Is the result the same as in your post at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…, i.e., /usr/local/Cellar/python(a)3.9/3.9.5/bin/python3.9: can't open file '/usr/local/opt/python(a)3.9/bin/master': [Errno 2] No such file or directory > my mailman info shows - > > GNU Mailman 3.3.5b1 (Tom Sawyer) > Python 3.9.5 (default, May 4 2021, 03:36:27) > [Clang 12.0.0 (clang-1200.0.32.29)] > config file: /Users/.../Documents/mailman/var/etc/mailman.cfg > db url: sqlite:////Users/.../Documents/mailman/var/data/mailman.db > devmode: DISABLED > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass We recommend following this guide https://docs.mailman3.org/en/latest/install/virtualenv.html What is the content of the /Users/.../Documents/mailman/var/etc/mailman.cfg file? The 'pip install -e ./' command should have created a bin/ directory containing both `mailman` and `master` executable files and this `mailman` command is the one you should be running. It appears the `mailman` command you are running is '/usr/local/opt/python(a)3.9/bin/mailman'. If that is in fact a symlink to a different bin/mailman file, there should also be a symlink from '/usr/local/opt/python(a)3.9/bin/master' to the existing bin/master or you should adjust your path. What do `which -a mailman` and `which -a master` show? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

[MM3-users] Re: Search function returning results from another list

by Marco van Tol

Hi there, For completeness, I could fix the issue by issuing a './manage.py rebuild_index' from the hyperkitty container. (We're running mm3 in containers) Thanks! Marco van Tol RIPE NCC On Mon, 14 Oct 2024 at 16:53, Marco van Tol <mvantol(a)ripe.net> wrote: > Hi there, > > We actually found that if you look for "*" it will find exclusively > messages from the other list, from the first looks of it. > > But if you "show the archive" in the normal way, without using the search > function, it will work as expected. > Other lists on the same server show the correct messages when you search > for "*", I wonder what went bad with this list. > > It originally came from a mailman2 server and was imported from that. > > Thanks! > > Marco van Tol > RIPE NCC > > > On Mon, 14 Oct 2024 at 16:06, Marco van Tol <mvantol(a)ripe.net> wrote: > >> Hi there, >> >> We have several lists on our list server here, and noticed that if we do >> this: >> - go to the archive of public list x >> - type in "minutes" in the search bar >> >> If will: >> - show a screen: list-x search results for query "minutes" >> - have 3 results in there for another private list >> - show a message that you need to login to view the message if you click >> on one >> >> Our current mailman core version is: 3.3.9 >> Our current hyperkitty version is: 1.3.10 >> Our index engine is: xapian_backend.XapianEngine >> >> Does this make sense? >> >> Thanks! >> >> Marco van Tol >> RIPE NCC >> >

1 year, 6 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Odhiambo Washington

On Mon, 27 Jul 2020 at 02:49, Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/26/20 9:12 AM, Odhiambo Washington wrote: > > On Sun, 26 Jul 2020 at 18:48, Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 7/26/20 3:15 AM, Odhiambo Washington wrote: > >> > >>> There is still some confusion on my part about the directives in the > file > >>> so allow me to seek some clarifications. > >>> > >>> The following are the contents of a file I have created and placed in > my > >>> Apache Includes/ directory. > >>> I was hoping that with it, I can now access http://lists.my.server/mm3 > >> and > >>> get the UI. > >>> > >>> <CUT> > >>> > >>> # Global section > >>> WSGIDaemonProcess mailman-web display-name=mailman-web > >>> maximum-requests=1000 umask=0002 user=mailman3 \ > >>> group=mailman3 > >>> > >> > python-path=/opt/mailman/mm/venv/lib/python3.7/site-packages:/opt/mailman/mm/venv/lib/python3.7 > >>> \ > >>> python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > >>> WSGIRestrictSignal Off > >>> > >>> <VirtualHost *:80> > >>> ServerName lists.my.server > >>> ServerAdmin odhiambo(a)gmail.com > >>> > >>> # (I'm not sure that WSGIRestrictSignal Off is required, but it was in > >> the > >>> # provided example so I kept it. I also made changes to > WSGIDaemonProcess > >>> # based on my own mod_wsgi experience elsewhere.) > >>> > >>> ErrorLog /var/log/myserver-error.log > >>> LogLevel debug > >>> > >>> # This goes in the VirtualHost block for the domain. > >>> > >>> # Mailman 3 stuff > >>> Alias /static "/var/spool/mailman-web/static" *<----- Where is this > >>> directory supposed to be and what/who creates it and with what > >> permissions?* > >> > >> > >> It is created/updated by the mailman-post-update script based on CONFDIR > >> and STATIC_DIR. > >> > > > > The fact that I have run the mailman-post-update script and these > > directories aren't created means there is a problem in my setup, yes? > > > If your mailman-post-update script is essentially the same as > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > and it ran successfully, it would have created opt/mailman/mm/static and > populated it. What was the output when you ran it? > > > Yes, I have these files: > > (venv) [root@gw /opt/mailman/mm]# ls -al /opt/mailman/mm/settings* > > -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 > > /opt/mailman/mm/settings.py > > -rw-r--r-- 1 mailman3 wheel 15773 Jul 26 10:33 > > /opt/mailman/mm/settings_local.py > > > Is there an empty /opt/mailman/mm/__init__.py file? > No. root@gw:/usr/local/mailman # ls -al /opt/mailman/mm/ total 88 drwxr-xr-x 8 mailman3 wheel 512 Jul 26 14:55 . drwxr-xr-x 6 mailman3 wheel 512 Jul 26 18:38 .. drwxr-xr-x 8 root wheel 512 Jul 25 22:16 .sass-cache drwxr-xr-x 2 mailman3 wheel 512 Jul 26 16:35 __pycache__ drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:42 bin -rw-r--r-- 1 mailman3 wheel 248 Jul 25 14:37 gunicorn.conf -rw-r--r-- 1 mailman3 wheel 266 Jul 26 15:34 gunicorn.conf.py lrwxr-xr-x 1 mailman3 wheel 24 Jul 25 14:39 logs -> /opt/mailman/mm/var/logs -rw-r--r-- 1 mailman3 wheel 370 Jul 25 14:32 mailman-hyperkitty.cfg -rw-r--r-- 1 mailman3 wheel 1291 Jul 26 17:12 mailman.cfg -rw-r--r-- 1 mailman3 wheel 15518 Jul 25 14:34 settings.py -rw-r--r-- 1 mailman3 wheel 15805 Jul 26 21:22 settings_local.py drwxr-xr-x 9 mailman3 wheel 512 Jul 25 22:16 static -rw-r--r-- 1 mailman3 wheel 1395 Jul 25 14:35 urls.py drwxr-xr-x 12 mailman3 wheel 512 Jul 26 19:30 var drwxr-xr-x 5 mailman3 wheel 512 Jul 26 17:11 venv -rw-r--r-- 1 mailman3 wheel 1170 Jul 26 11:39 wsgi.py > > > PS: I made my /opt/mailman to be owned by mailman3:wheel because of a > > confusion with the instructions at some point in the reading > > of some documentation previously (in my previous attempt last year!) and > > had noted that in my NOTES. I'll change this once things get clear for > me. > > Also, the fact that one of the init scripts > > < > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > > > > in your "reflection" page was calling sudo :) > > > It does `sudo -u $USER ...` so that it runs Mailman as the Mailman user > as it should. Have you set > > USER=mailman3 > in yours? > Yes. However, that also means the /opt/mailman should be owned by mailman3, right? So I wasn't quite mistaken. PS: There is the issue with qcluster, which doesn't seem to have been documented in details from your "experience". I see the configuration file and the init script, but not how to install it, or whether the procedure already installed it. Kindly clarify. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 9 months

[MM3-users] Re: MM2 to MM3 on debian 10

by Mark Sapiro

On 4/27/20 8:26 AM, Gelpi Andrea wrote: > Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 > mailing lists. I know that not all can work. > > In my old lists I have email and regular expressions in > reject_these_nonmembers and discard_these_nonmembers > > After importing the list all these email are in non member list. > > All these email have Delivery status enabled. Delivery status is not relevant for non-members and only has to do with receiving list posts in any case. What version of Mailman core is this? There have been changes in `mailman import21` that may affect this, but an address in `reject_these_nonmembers` should be imported as a non-member with a moderation action of `reject` and similarly for `discard`. Note that regexps in *_these_nonmembers should be imported into the MM 3 legacy *_these_nonmembers attributes. Some older versions of import21 also imported non-regexp addresses here, but that was wrong. > Does this mean that all of them will receive any message sent to the list? > The moderation rule is correct, but if I understood correct Delivery > status should be disabled. Delivery status is irrelevant for non-members. Only members are candidates for delivery. > For migration I followed this link > https://docs.mailman3.org/en/latest/migration.html > > To migrate archives it states to run > > python manage.py hyperkitty ... > > I cant' find a manage.py on debian 10 manage.py is a Django generic term for the Django admin command. You probably want something called django-admin or similar. > A search shows the only /usr/share/mailman3-web/manage.py exists. > > Is there any documentation specific for debian? That would be up to Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

[MM3-users] Re: So near, and yet so far (Configuring Mailman)

by Joel Lord

On 1/29/2021 12:01 PM, Jack Lenox via Mailman-users wrote: > Hello all, > > I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails. > > When I try to send emails to lists I'm rebuffed with undelivered notices with: > > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found > and: > <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again > > This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that: > > lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. > lists.fiftyshadesof.green. 0 IN A 193.37.35.191 > > I have driven myself mad with this and would very much appreciate any advice anyone can offer. The key here isn't in your mailman config, or even your postfix config (you might be able to fix it there, I'm not sure). The key is in the error: <testlist(a)lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found Specifically, type=AAAA. It's looking for an IPv6 host record and you don't have one. I'm going to guess you got that bounce not from your lists host, rather from your mail relay? Somewhere along the way something is trying to use IPv6 and needs to get kicked to either not do that or at least fall back to IPv4. -- Joel Lord

5 years, 3 months

[MM3-users] ValueError: The ADMINS setting must be a list of 2-tuples.

by David Partain

Greetings, We're trying to move from an ancient and bad Ubuntu-package based installation of mailman3 to a venv-based do-it-the-right-way installation. # mailman --version GNU Mailman 3.3.9 (Tom Sawyer) Things seem much better than past migration attempts. We are, though, seeing tons of errors in uwsgi-error.log that look like this: Traceback (most recent call last): File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 131, in __call__ response = self.get_response(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 140, in get_response response = self._middleware_chain(request) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 58, in inner response = response_for_exception(request, exc) File "/local/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 144, in response_for_exception log_response( File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 241, in log_response getattr(logger, level)( File "/usr/lib/python3.10/logging/__init__.py", line 1506, in error self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.10/logging/__init__.py", line 1624, in _log self.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 1634, in handle self.callHandlers(record) File "/usr/lib/python3.10/logging/__init__.py", line 1696, in callHandlers hdlr.handle(record) File "/usr/lib/python3.10/logging/__init__.py", line 968, in handle self.emit(record) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 128, in emit self.send_mail(subject, message, fail_silently=True, html_message=html_message) File "/local/mailman/venv/lib/python3.10/site-packages/django/utils/log.py", line 131, in send_mail mail.mail_admins( File "/local/mailman/venv/lib/python3.10/site-packages/django/core/mail/__init__.py", line 124, in mail_admins raise ValueError("The ADMINS setting must be a list of 2-tuples.") ValueError: The ADMINS setting must be a list of 2-tuples. Our ADMINS setting in /etc/mailman3/settings.py has ADMINS = ( ('Mailman Suite Admin', 'someone(a)our.domain', 'someoneelse(a)our.domain'), ) Can someone point me in a direction to correct this? Thanks in advance. David

2 years, 1 month

[MM3-users] Re: Python 3.13 compatibility

by Thomas Ward

Okay, so links get purged apparently [1] was supposed to point at https://docs.mailman3.org/en/latest/install/install.html On 2026-03-30 13:49, Thomas Ward via Mailman-users wrote: > With recent revisions I made to the general Installation page that > leads to other pages [1], we could write a > "Install-From-HEAD-DANGEROUS" document (akin to the existing > virtualenv install documents but then specify alternative install > commands to install from HEAD), detailing how to install from HEAD > with the major disclaimer notice about this NOT being recommended > unless you want or need to track Git HEAD. > > The parent page there at [1] can thus have a huge disclaimer saying > "You should only do this if you really need to or are intending to > work with development of Mailman 3 and its components." > > Happy to write a proposal of such a document for review. > > > Thomas > > > On 2026-03-30 13:45, Stephen J. Turnbull wrote: >> Stephen J. Turnbull writes: >> >> > Putting that recipe as is in the developer docs also doesn't make >> > that much sense to me, as developers are expected to have full >> > clones of the components they're working on. On the other hand >> > something that points at the dev's local repos of the Mailman Suite >> > components does make a lot of sense to me. >> >> That would be somewhere in the neighborhood of >> mailman/src/mailman/docs/install.rst. >> >> Steve >> > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to teward(a)thomas-ward.net

1 month

[MM3-users] Re: Odd behavior: "Invalid" list destinations result in mail routing loop w/ SMTP relay in line

by Mark Sapiro

On 12/6/23 11:11, Thomas Ward via Mailman-users wrote: > See, that's the oddness. There appears to be SOME weird mail loop here > where $ORIGIN (MS365/Exchange) hands it once, then there's > back-and-forth between SMTPPROXY and Mailman. IT's really odd how it > behaves, and I have no explanation for it. > > Right now I'm away from the office where this happens, but when I'm back > there I'll grab logs from both sides. > > > Thomas > > On 12/5/23 17:54, Mark Sapiro wrote: >> On 12/5/23 10:08, Thomas Ward via Mailman-users wrote: >>> We use a multi-hop SMTP system to go from the inside of our network >>> out to the Internet at the domain test.lists.example.com. >>> >>> The setup is this way for ingress: >>> >>> {EXTERNAL} -> MS365 (relay/antispam) -> MS On-Prem (via 365 >>> Connector) -> Mailman for delivery to listserv Presumably the EXTERNAL to MS365 SMTP transaction includes MAIL FROM: <user(a)example.com> RCPT TO: <invalid(a)test.lists.example.com> It seems that somewhere in the path to Mailman this is getting changed to MAIL FROM: <invalid(a)test.lists.example.com> so the outbound DSN is sent to invalid(a)test.lists.example.com instead of user(a)example.com. The question is which one of the MTAs in the path is doing this and why. But even more mysterious is the fact that the DSN from Mailman should be sent with MAIL FROM: <> so when it's undeliverable, no further DSN is sent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

[MM3-users] Re: Problem updating mailman

by Brian Carpenter

Mark Sapiro wrote: > On 1/24/21 1:03 AM, Odhiambo Washington wrote: > > I uninstalled rubygem-sass from the OS. I don't > > remember consciously > > installing that because it was never in the guide I followed (which is your > > own writeup). > > But I still have a problem: > > (venv) [mailman3@gw ~/mm]$ /opt/mailman/mm/bin/mailman-post-update > > > > '[' False == False ']' > > mkdir -p /opt/mailman/mm/static > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > > --verbosity 0 > > /opt/mailman/mm/bin/django-admin compress > > CommandError: An error occurred during rendering > > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3-1.3.5-py3.7.egg/django_mailman3/templates/socialaccount/signup.html: > > /bin/sh: sass: not found > > > > You can't just uninstall rubygem-sass. You have to replace it. Here's > one recipe for Ubuntu > cd /usr/local/lib > # See https://github.com/sass/dart-sass/releases/tag/1.32.5 for the > # appropriate version. > wget > https://github.com/sass/dart-sass/releases/download/1.32.5/dart-sass-1.32.5-... > sudo tar -xf dart-sass-1.32.5-linux-x64.tar.gz > sudo chmod -R o-w dart-sass > sudo ln -s dart-sass/sass /usr/local/bin/sass > rm dart-sass-1.32.5-linux-x64.tar.gz > Then you should see the command > sass --version > prints > 1.32.5 > Then, because dart-sass doesn't recognize the short form -t option for > --style, you have to edit your settings(_local).py and change > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > to > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass --style compressed {infile} {outfile}'), > ('text/x-sass', 'sass --style compressed {infile} {outfile}'), > ) I had to do a new installation of Mailman 3 with Postorius/Hyperkitty today and these directions were very helpful. Thank you, Mark.

5 years, 3 months

[MM3-users] Re: Template for Password Reset Email

by Mark

On 2024-11-18 01:38, Mark Sapiro wrote: > On 11/17/24 16:57, Mark wrote: >> >> I can see the French text for the "Password Reset Email" in the >> django.po file. And running the compilemessages command reports the >> "django.po" for French is okay and up to date. Should I be recompiling >> the ".mo" file? > > No, It's fine. The issue is the language context for this message has > nothing to do with any Mailman list's preferred language. > > Again, see > https://docs.djangoproject.com/en/5.1/topics/i18n/translation/#how-django-d… > > If all the lists on your server are French, you could set > > LANGUAGE_CODE = 'fr' > > in your Django settings. Otherwise, the user's browser has to include > an Accept-Language: header specifying French as the most preferred > language in it's request. > > Also note the ordering of SessionMiddleware, LocaleMiddleware and > CommonMiddleware in the above doc. I have recently updated the various > places where we suggest or supply MIDDLEWARE settings, but you may > find that your settings have LocaleMiddleware after CommonMiddleware > and you should fix that. It's just the one list that is using French. Others are in English I've edited the order of the middleware settings in this file ... /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/settings/base.py I reordered as below, restarted everything but no joy :-( ... at Line 76 ... MIDDLEWARE = ( 'allauth.account.middleware.AccountMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ... I'm thinking this is not the file I'm looking for. Apologies for my cluelessness here.

1 year, 5 months

[MM3-users] Re: (Custom) Plugins: Proper file path(s) for adding a handler?

by Abhilash Raj

On 10/23/23 20:37, Thomas Ward via Mailman-users wrote: > I want to add a custom handler that implements customized thread IDs in > the system. I already have the DB logic worked out, but the > documentation for plugins is NOT clear on how to define a handler in a > plugin, nor does the example plugin in the documentation on Gitlab have > any custom handlers. > > I'm looking to add a custom handler so that the private pipeline for > threaded-subject-list can use thread-subject (the custom handler) > instead of subject-prefix (builtin). https://gitlab.com/mailman/mailman/-/tree/master/src/mailman/plugins/testin… https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/plugins/do… These are two places you can find docs for an example plugin that ships with Mailman's code. Adding a new "component", like a Handler, works very similar to the "rules" in the example shown above. You will probably need a directory tree like: ``` example/ __init__.py hooks.py handlers/ __init__.py handlers.py ``` Installing the handler is same as per shown in docs using below (do note that the above example is the name of the package that is importable): ``` [plugin.example] class: example.hooks.ExamplePlugin enabled: yes [logging.plugins] propagate: yes ``` Finally, you can verify that your handler was loaded properly using something along the lines of: ``` $ 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. >>> for each in config.handlers: ... print(each) ... member-recipients to-archive cleanse-dkim file-recipients to-outgoing mime-delete after-delivery decorate to-digest avoid-duplicates arc-sign cook-headers replybot tagger acknowledge dmarc subject-prefix validate-authenticity owner-recipients to-usenet cleanse rfc-2369 ``` -- thanks, Abhilash Raj (maxking)

2 years, 6 months

[MM3-users] Re: Subscribe only to one thread

by Ivan Perez

I don't have the skills but, is there any other way I can help? Ivan On 7 May 2018 at 19:45, Terri Oda <terri(a)toybox.ca> wrote: > We've already got the code for it. It was the "dynamic sublists" project. > Systers built dlists for their needs with mailman 2 and we had a student > implement it on mailman 3. > > The problem has just been in getting the patches integrated, which was > mostly on me not being able to follow through at the critical time (as > opposed to there being technical reasons it wasn't done). I still don't > have the volunteer time necessary to port them forward to the latest > version of mailman now and do the integration, but would be happy to help > answer questions if someone else is interested in working on it. > > Terri > > On May 7, 2018 12:59:32 PM PDT, Ivan Perez <ivanperezdominguez(a)gmail.com> > wrote: > >> Dear Mailman users, >> >> There are many high-traffic mailing lists in which I would only be >> interested in receiving messages in specific threads (not all messages, nor >> some topics, nor a daily digest). >> >> Is there a way of "subscribing" to individual threads only, mainly those I >> initiate, or I actively participate in, but generally not receiving any >> emails from the list? >> >> If not, would others find this useful, and could it be implemented? (I >> understand that everyone wants features; I just don't know if it's a 2-hour >> patch or a 2-month project). >> >> Best wishes >> >> Ivan >> ------------------------------ >> >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> >>

7 years, 11 months

[MM3-users] Re: Problems after upgrading from bullseye to bookworm

by Thomas Ward

FYI I updated my workaround on the linked issues on Gitlab to reflect this. Technical Note that this may not apply after the PDM backend updates which are in the works to not normalize metadata (which causes this problem). I have not tested a fresh setup yet since the issue was first identified but it is possible the issue is easily resolved once updated versions of these flufl libraries land in PyPI with the pdm backend fixes in place for the build envs of those libraries. Sent from my Galaxy -------- Original message -------- From: Mark Sapiro <mark(a)msapiro.net> Date: 6/26/23 16:23 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Problems after upgrading from bullseye to bookworm On 6/26/23 12:35 PM, Ken Alker wrote: > I'm brand new to this, so take this with a grain of sale, but, I had a similar problem a few days ago, however, mine was "flufl.i18n>=3.2". Perhaps the same thing is happening with flufl.lock (but that didn't bite me). > > I solved my problem by following this: <https://gitlab.com/mailman/mailman/-/issues/1085> and, ultimately modifying "$VENV_ROOT/lib/$PYVERSION/site-packages/mailman-3.3.8.egg-info/requires.txt" per that thread (see <https://gitlab.com/mailman/mailman/-/issues/1085#note_1442207929> by Thomas Ward section called "The WORKAROUND"). Maybe you need to do the same thing, but for flufl.lock. Yes, the same issue now affects flufl.lock as well as flufl.i18n. You will need to change both flufl.lock->flufl_lock and flufl.i18n->flufl_i18n. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

2 years, 10 months

[MM3-users] Re: psycopg2 error?

by Mark Sapiro

On 10/26/23 01:03, Odhiambo Washington wrote: > > <CUT> > root@debian12:/home/wash# systemctl status mailman3.service > × mailman3.service - GNU Mailing List Manager > Loaded: loaded (/etc/systemd/system/mailman3.service; enabled; preset: > enabled) > Active: failed (Result: exit-code) since Thu 2023-10-26 09:36:41 EAT; > 8s ago > Process: 1893842 ExecStart=/opt/mailman/venv/bin/mailman start > (code=exited, status=1/FAILURE) > CPU: 789ms > > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: dbapi = > dbapi_meth(**dbapi_args) > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: > ^^^^^^^^^^^^^^^^^^^^^^^^ > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/sqlalchemy/dialects/postgresql/psycopg2.py", > line 690, in import_dbapi > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: import psycopg2 > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: File > "/opt/mailman/venv/lib/python3.11/site-packages/psycopg2/__init__.py", line > 51, in <module> > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: from > psycopg2._psycopg import ( # noqa > Oct 26 09:36:41 debian12.wash.lan mailman[1893842]: SystemError: > initialization of _psycopg raised unreported exception > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Control > process exited, code=exited, status=1/FAILURE > Oct 26 09:36:41 debian12.wash.lan systemd[1]: mailman3.service: Failed with > result 'exit-code'. > Oct 26 09:36:41 debian12.wash.lan systemd[1]: Failed to start > mailman3.service - GNU Mailing List Manager. > </CUT> Is your database PostgreSQL or some other? If it's not PostgreSQL, see the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… - particularly https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… Also see https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-mail… where it now says in part "This will install latest release of Mailman Core, and Python bindings for Postgresql database. If you are using a different database manager, do not install psycopg2-binary." -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

[MM3-users] Re: Why is it so difficult to setup Mailman3?

by Thomas Ward

Most of that can be done with scripting in the container. It would ultimately though end up as a 'ready to go' venv environment if people want it. I'm already working on an approach to automate install and setup of MM3 for other things I'm working on, so I'll keep this as a backup consideration for contributions. Thomas Sent from my Galaxy -------- Original message -------- From: "Stephen J. Turnbull" <steve(a)turnbull.jp> Date: 4/8/26 16:21 (GMT-05:00) To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Why is it so difficult to setup Mailman3? Thomas Ward via Mailman-users writes: > Stephen, would a prebuilt LXD-style container or VM that is respun > quarterly but is still a base virtualenv setup based on Ubuntu > 24.04 and otherwise fully 'setup' except for actual domain configs, > etc. be useful here as an 'alternative' to 'do it yourself' but > still work as a full venv setup? That's a good question, but I don't know the answer. I can see that it has fewer moving parts than docker-mailman, but whether the people who find the current venv install too complex would find it appealing, I can't say. There is also the problem that you will need some way to generate the various authentication tokens and install them in the image ex post -- they can't be hard-coded. I don't think that's too hard, though. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan _______________________________________________ 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/ Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… This message sent to teward(a)thomas-ward.net

3 weeks

[MM3-users] Re: Attachement processings questions

by Mark Sapiro

On 2/3/20 4:27 AM, Lars Schimmer wrote: > > In a mailinglist it seems some mails are not forwarded to a member, but > is listed in archive in hyperkitty. > That mail did include a PDF attachement, but HyperKitty does not list > any attachement. There are two issues here. Why wasn't the message delivered to list members?, and why is there no attachment in Hyperkitty? For the first issue, you need to examine mailman.log for the time of the post looking for errors and tracebacks. Also, the MTA logs may have useful info if the messages were sent but not delivered. For the second, there are many content filtering settings not (yet) exposed in Postorius. These include filter_extensions, filter_types, pass_extensions and pass_types which control which MIME parts are removed. For a newly created Mailman 3 list, these four settings are empty, but importing a Mailman 2.1 list will set them according to the corresponding MM 2.1 list's settings. > All I found was "convert HTML to plaintext", but does this setting > remove attachements? It would only affect HTML parts, not pdfs. > Is there any generel documentation about attachement processing in MM3? <https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/filterin…>. > I would like this mailinglist to accept mails with attachements, send it > to the members and archvie the attachments in HyperKitty, to. You can set Settings -> Alter Messages -> Filter content to No in Postorius to not do any content filtering at all. This will override the Collapse alternatives and Convert html to plaintext settings and pass the message without removing any MIME parts. But, I think you must have other issues, either with this mail in particular or in general as evidenced by the mail not being received by list members. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 2 months

[MM3-users] Hyperkitty: Error when rebuilding Index

by M4tze

Dear list members, if there is any Hyperkitty expert here, I have issues in Hyperkitty (just updated Maxkings Docker images) when rebuilding the Index. Unfortunately, there are more than 25,000 mails and I do not know which one is/might be broken. Does the error mean that the rebuilding process is incomplete or does it simply skip the erroneous message? Thank you in advance - M4tze Traceback (most recent call last): File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 297, in handle self.update_backend(label, using) File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 342, in update_backend max_pk = do_update( File "/usr/lib/python3.8/site-packages/haystack/management/commands/update_index.py", line 100, in do_update current_qs = list(current_qs) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 269, in __len__ self._fetch_all() File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 1308, in _fetch_all self._result_cache = list(self._iterable_class(self)) File "/usr/lib/python3.8/site-packages/django/db/models/query.py", line 53, in __iter__ results = compiler.execute_sql(chunked_fetch=self.chunked_fetch, chunk_size=self.chunk_size) File "/usr/lib/python3.8/site-packages/django/db/models/sql/compiler.py", line 1156, in execute_sql cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute return self._execute_with_wrappers(sql, params, many=False, executor=self._execute) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers return executor(sql, params, many, context) File "/usr/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute return self.cursor.execute(sql, params) File "/usr/lib/python3.8/site-packages/django/db/backends/mysql/base.py", line 73, in execute return self.cursor.execute(query, args) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 209, in execute res = self._query(query) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 317, in _query self._post_get_result() File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 352, in _post_get_result self._rows = self._fetch_row(0) File "/usr/lib/python3.8/site-packages/MySQLdb/cursors.py", line 325, in _fetch_row return self._result.fetch_row(size, self._fetch_type) UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position 3209: invalid continuation byte

4 years, 5 months

[MM3-users] Race condition when mass subscribing same email addresses to two lists?

by Stephen J. Turnbull

Alan So writes: > 1) Create two lists with default setting > 2) Prepare a list of 1000 fresh email addresses not added to the > system before > 3) Mass subscribe both lists of these 1000 email addresses around > the same time with all three Pre (confirm, approved, verified) > checked [...] > (psycopg2.errors.UniqueViolation) duplicate key value violates > unique constraint "ix_address_email" > DETAIL: Key (email)=(testemail999(a)example.com) already exists. I think there's some kind of race condition. I would bet it's in Mailman core, not in the RDMBS code or the ORM. The process is 1. Check if the address is known. 2. If yes: a. Get the address's user. b. Add the subscription pair (address, list) to the user. c. Add the address to the list. 3. If no: a. Create the address object. b. Create a user for the address, and link them together. c. Add the subscription pair (address, list) to the user. d. Add the address to the list. Each line is a separate database query, I suspect, so the race is between 1 and 3a. If two requests for the same new address arrive at the "same" time, both will try to create the address, only one can succeed. I guess we should catch the error and retry. Raising and handling exceptions in Python is relatively slow, so even in your well constructed worst case, this shouldn't happen on every address, so I don't think having a separate queue or putting the whole thing in a transaction would be better. If you still have the log, I'd be curious to know how many unique errors you got. I need to do other work for the next 48 hours, but a patch would be very welcome. I don't know offhand where this code lives, sorry. Steve

4 years, 6 months

[MM3-users] Re: 'Failed adding message' error when migrating a list from mailman2 to mailman3

by Prasanth Nair

Thank you, Mark. Kind regards, Prasanth On Thu, 14 Oct 2021 at 19:17, Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/14/21 9:04 AM, Stephen J. Turnbull wrote: > > Prasanth Nair writes: > > > > > *2%Failed adding message <mailman.2.1593699619.32248>: 'ascii' codec > can't > > > encode character '\ufffd' in position 252: ordinal not in > range(128).* > ... > > > I ran the check_hk_import script before migrating and it was not > > > giving any error. > > > > In order to catch this kind of error, the check script would have to > > pretty much do the import but throw it away. > > > The check_hk_import script > <https://www.msapiro.net/scripts/check_hk_import> is designed to detect > and report conditions which would cause the django hyperkitty_import > process to abort and stop processing the mbox. It doesn't catch errors > like the above, but these are non-fatal and just cause the offending > message to be skipped. > > As Steve says, the Message-ID was reported so find it in the mbox and if > you want it in the archive, extract it from the mbox, fix it and then > just rerun the import with just that message as input[1] and a > --since=1970-01-01 option. > > Note the issue could be in a header, but also could be in a body part > implicitly or explicitly declared as charset="us-ascii". > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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/ >

4 years, 6 months

[MM3-users] Setting up on ubuntu server 22.04

by Stephen J. Turnbull

Kyriakos Terzopoulos writes: > ImportError: cannot import name 'path' from 'importlib_resources' Try putting the error message into Google with "" around it. (This is generic advice for the future, obviously I already know what it is and will tell you. :-) This is a known issue where Python changed some APIs that Mailman uses. Discussion is here: https://gitlab.com/mailman/mailman/-/issues/1093 There's a simple patch to requirements.txt at the end of the comments. Edit it, and delete and reinstall the mailman package, it will take 10 minures. If you're familiar with Python and pip you can also force remove that package, then reinstall with the additional version constraint. > In general would it be better or/and easier to set this up on a new > machine in my Hetzner cloud e.g. on Debian which seems to have > packages of mailman available? That depends. Do you want to get your Mailman help from Debian (the answer is "NO!!"[1] unless you mostly expect to need no help -- that probably works for 70% of Debian + Mailman users) or from us? Unless your use case is exactly what the distro maintainer envisions, you will occasionally run into issues that are impossible for them to figure out, and rather expensive for us to help you with since they depend on old and modified versions. We strongly prefer you use a venv install, and if Mailman is at all important to your site's mission, you probably will too. Footnotes: [1] At least for servers, I prefer Debian myself. Distros are the best thing since sliced bread. But Mailman is still a relatively fast-moving target[2] and none of the distros keeps up. [2] In part because Gmail, Yahoo!, and O365 hate mailing lists, almost as much as the spammers hate us, and we keep tweaking things to deal with both kinds of Internet mischief.

2 years, 6 months

[MM3-users] Re: hyperkitty threads by month question

by Mark Sapiro

On 7/25/24 11:20, Bryan Fields wrote: > Sorry for the delay, I was on some travel last week. > > On 7/19/24 7:30 PM, Mark Sapiro wrote: >> That URL gives me as server error. What's in the Django (mailman-web) >> logs for that? > > I did notice hitting a 500 error on occasion, sometimes it works. I just tried it twice more and got the error both times. > When this happens, I get an email error below. This is really wierd. See below. >> Are you running all the Django periodic jobs and is qcluster running? > > Ok, the docs said that qcluster service wasn't needed under uWSGI > https://docs.mailman3.org/en/latest/install/virtualenv.html#automatically-s… > qcluster does appear to be running: Right, you don't need to create a separate service for it with our recommended uWSGI configuration because uWSGI runs it, but it does need to run. ... > line 88, in reverse > return resolver._reverse_with_prefix(view, prefix, *args, **kwargs) > File > "/opt/mailman/venv/lib/python3.10/site-packages/django/urls/resolvers.py", line 828, in _reverse_with_prefix > raise NoReverseMatch(msg) > > Exception Type: NoReverseMatch at > /archives/list/nanog(a)nanog-mm3.keekles.org/ > Exception Value: Reverse for 'hk_archives_with_month' with keyword > arguments '{'year': 999, 'mlist_fqdn': 'nanog(a)nanog-mm3.keekles.org', > 'month': 12}' not found. 2 pattern(s) tried: > ['archives/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$', 'hyperkitty/list/(?P<mlist_fqdn>[^/@]+@[^/@]+)/(?P<year>\\d{4})/(?P<month>\\d\\d?)/$'] > Raised during: hyperkitty.views.mlist.overview It appears to be trying to get the threads for December, 999. What do these queries show? SELECT * FROM hyperkitty_thread WHERE EXTRACT(year FROM date_active) < 1000; SELECT id FROM hyperkitty_email WHERE EXTRACT(year FROM date) < 1000; -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 9 months

[MM3-users] Re: no mails to list members

by Thomas Stein

On 04.01.19 16:05, Abhilash Raj wrote: > > > On Fri, Jan 4, 2019, at 7:02 AM, Thomas Stein wrote: >> On 04.01.19 15:55, Abhijith PA via Mailman-users wrote: >> > >> > >> > On Friday 04 January 2019 08:19 PM, Thomas Stein wrote: >> >> On 04.01.19 09:40, Thomas Stein wrote: >> >>> >> >>> Turns out mailman was not able to read a specific template. That seemed to be enough to throw an exception. Maybe >> >>> i missed something else but after adjusting the permissions of that template everything worked as expected. >> >> >> >> While we`re at it. Is /var/lib/mailman3/templates/lists/$listname the right location for customized templates? Should >> >> I name the template list:member:generic:footer.txt or list_member_generic_footer.txt? Is there some documentation >> >> what variables i can put in those templates? >> > >> > If you are using 3.2.0, you can do that from webapp itself. [ I haven't >> > tried though] >> >> Running 3.1.1 right now. 3.2.0 isn`t in the ubuntu repo yet afaik. >> >> https://launchpad.net/ubuntu/+source/mailman3 > > This link mentions that 3.2.0-1ubuntu1 is the current stable version. But not for ubuntu 18.04. This one indeed does. https://launchpad.net/~efficios/+archive/ubuntu/mailman3 cheers t. >> >> thanks and cheers >> t. >> >> > >> > --a >> > _______________________________________________ >> > 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/ >> > >> _______________________________________________ >> 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/ >> >

7 years, 3 months

[MM3-users] Notes about successfuly upgrade from python 3.7 to 3.9

by Guillermo Hernandez (Oldno7)

I've successfuly upgrade servers with mailman3 lists from FreeBSD 12.3 with python 3.7 to FreeBSD 13.1 with python 3.9 After doing the O.S. and all the python related apps upgraded I did the following steps: (note that my mailman3 installation is system-wide, pip drived and apache24/uwsgi served. The user that owns mailman3 is "mailman3" and all the stuff lies in "/usr/local/mailman3") -> su -> cd /usr/local/mailman3 -> pip install --upgrade django-mailman3 mailman mailman-hyperkitty mailmanclient postorius django hyperkitty uwsgi mod-wsgi -> mod_wsgi-express module-config (it returns the path for the apache24 httpd.conf adjustments. I edited it) -> su -m mailman3 -c "python3 manage.py collectstatic" -> su -m mailman3 -c "python3 manage.py migrate" -> su -m mailman3 -c "python3 manage.py compress" -> cd /usr/local/lib/python3.9/site-packages/ -> cd postorius -> django-admin compilemessages -> cd ../hyperkitty -> django-admin compilemessages -> cd ../django_mailman3 -> django-admin compilemessages I had to edit again /usr/local/lib/python3.9/site-packages/mistune/scanner.py and add this two lines (this is a little bit annoying) from mistune.util import escape_html from mistune.util import escape_url And that was all. Restarted the servers and all is going smoothly All of this steps have been documented in this list by Mark & Stephen whom I'm very grateful. P.S.: As I did some upgrades ago, I didn't have to modify settings.py in the Hyperkitty area to add DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' But if you come from an old mailman/Hyperkitty version, you'll have to include in it. And the it's same if you are using UWSGI, you have to include in your apache config: WSGIPassAuthorization On -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

3 years, 9 months

[MM3-users] Re: Cannot Install Web UI

by Stephen J. Turnbull

dap1--- via Mailman-users writes: > I made all the suggested changes and now am down to the next layer > of the onion when starting mailmanweb: You should have gunicorn installed in your Mailman virtual environment. Here's what that looks like for me (your "/opt/mailman3" may vary, your "/.v" almost certainly does, the part from /lib on down should be the same except maybe for the minor version of python3): $ ls /opt/mailman3/.v/lib/python3.13/site-packages/gunicorn/ __init__.py app debug.py http reloader.py util.py __main__.py arbiter.py errors.py instrument sock.py workers __pycache__ config.py glogging.py pidfile.py systemd.py $ > gunicorn[53945]: ModuleNotFoundError: No module named > 'gunicorn.app'; 'gunicorn' is not a package This error message appears to be saying that the file __init__.py is missing (that's how Python defines a folder to be a package). It's also possible that the gunicorn package is installed somewhere other than Mailman's virtual environment, and so missing entirely from Mailman's virtual environment. > I hope all this gets added to the docs for the next poor sole that > has to do this on Ubuntu. :-) I'm not really sure what to add, except to recommend gunicorn instead of uwsgi. uwsgi is a FAQ because it's usually installed as a system package, and so has different ideas where things go in the file system from Mailman. uwsgi is not a Python app so can't be installed automatically in the virtual environment. uwsgi issues come up several times a year. gunicorn has traditionally been unproblematic because it's a requirement of Mailman core anyway. When we figure out why your installation doesn't seem to have gunicorn, maybe there will be something to say. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months

[MM3-users] Mailing lists as the main collaboration centre at SME

by Stephen J. Turnbull

Rodrigo Camacho writes: > If your company uses mailing lists to run, please reach out. We are > currently using Gitlab issues to collaborate which has been quite > successful. I would be very interested to trade tips. While (obviously :-) I support the use of mailing lists for collaboration and have used them successfully in multiple contexts for decades, you should pay careful attention to the user experience. 1. Mail user agents vary widely in their capabilities and user interfaces. Sometimes that means quality. For example, Gmail's customizable filters seem to be ordinary Sieve filters, that's fine, but the user interface is terrible. In other cases, they're just different (think Emacs-based MUAs vs Gmail). You should consider providing support to users of various MUAs, and lean to "more" resources for that rather than "less". Make sure that users have access to good threading in their MUAs. Gmail "conversations" aren't a great model; that's about the minimum capability. For corporate mail, both internal and incoming from suppliers and customers, etc, you should provide an IMAP server. This allows you to deal with document retention policy and privacy requests centrally. But you need to remember that users may be keeping local copies. You may also want to provide a corporate webmail server. I can't recommend a good one; we just decommissioned ours in favor of IMAP access because everybody has a personal MUA with a better UI. (I think we're using Cyrus imapd suite.) 2. Avoid the temptation to create many precisely defined lists. In my experience, it's more important that it be easy to choose the lists to post to and to subscribe to, than they be closely focused on specific interests. Focus is better served by an MUA that allows collapsing and suppressing individual threads and subthreads. 3. More important than wiping out top-posting is that everyone agree on style. I've seen a few lists where people absolutely could not get the concept of "appropriate amount of context" where switching to top-posting improved the flow. In general for technical content interlinear responses are best. However for managerial content ("Do this" -> "Done" -> "What about" -> "That too" conversations) top-posting is often fine because it's so linear. "Bottom posting" of course is right out. 4. The HyperKitty archiver was designed with the "we demand Discord" crowd in mind. As an archive, it provides the obvious features, including integration with various full-text indexers for search. But the authors also added a bunch of forum-like features, including the ability to post from the HyperKitty web ui and likes. There are alternatives, such as the IETF's MailArchive, which uses a maildir message store, which makes it easy to add an IMAP server to the archive, one feature that HyperKitty doesn't provide. This allows seamless access to the archive via the MUA (personally I don't like switching back and forth between the MUA and the browser). I think it's also possible to configure IMAP servers like Cyrus to function as list archives, but I'm not sure about how to configure MUAs for that architecture. (Note that IETF is the kind of place where people are always experimenting and don't hesistate to rewrite applications to test it. But I thought the idea was cool.) 5. Choice of full-text indexing backend is important. We default to Whoosh because it's pure Python and just a pip away. We recommend Xapian for production, but I don't think we thought terribly carefully about it. The Django-Haystack project appears to recommend Solr or ElasticSearch for Haystack 2.0.0 (and these are "included" in Haystack 2.0,0, not sure what that means, while Xapian is a separate download). I don't think we support Haystack 2 yet, but surely we will. 6. Colleagues who are new to mailing lists will need training and encouragement in netiquette. Reply style (top vs interlinear) is mentioned above. Mailing lists are prone to branching threads. Members need to learn to (1) change the subject when mutating the topic so that subthreads can be distinguished and (2) use new posts to start a new topic (ie, "don't hijack threads"). You write that GitLab collaboration has been successful for you, so it may be that your discussions are usually quite linear, and (1) may not be so important for you. 7. Some people (like me :-) may take naturally to "long form", which is enabled by mailing lists. Others may find long, discursive posts annoying. Be sensitive to people who have different preferences. 8. Some posters will tend to combine several somewhat related issues in one post, which naturally leads to many branches into subthreads. This likely will work itself out, but it can be a point of irritation for some users. Just remember that mailing lists afford that style of posting more so than forums or tracker issues do. 9. Remember that email is not adapted to modern affordances such as live editing. Nor is it suitable for realtime interactions such as incident response. Often it will be obvious, but sometimes it will take some time to work out which channels are well-served by mailing lists and which need an alternative medium. In general, just remember that people will respond to the change in different ways, and the goal is to improve communication, not to get people to adapt to a particular notion of "how it *should* work". Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 4 weeks

[MM3-users] Re: Dealing with spam from Web users

by Mark Sapiro

On 4/1/23 08:09, Jeremy Stanley wrote: > We recently migrated a bunch of lists from 2.1 to 3.3.7 and have > started to get spammers posting via HyperKitty (because I guess > that's easier for them than SMTP). It looks like I should be able to > set posts from HyperKitty to be automatically moderated by creating > a header filter on "User-Agent" matching "HyperKitty" but is there a > better/easier way? Typically, these would be non-members posting from HyperKitty and then being automatically subscribed. Set `Default action to take when a member posts to the list` to `Hold for moderation` so that all posts from members you haven't seen before are held. Then when handling a held post, if it is spam set the posters moderation action to discard and discard the message; if it is on topic, set the posters moderation action to default processing and accept the message. > Also, for things which already went out to the list, obviously I can > ban the spammer but what's the cleanest solution for removing > their posts from list archives so that we don't further their goals > by continuing to publish their handiwork? List owners should be able to delete messages and threads from HyperKitty, but they can't. See <https://gitlab.com/mailman/hyperkitty/-/issues/261>. You need to be a superuser to do this. If you are logged in as a user with Superuser status there will be a `Delete this thread` link in the thread view and a `Delete this message` link in the message view. You can use the `django-admin createsuperuser` command to create superusers. Also, anyone who is a superuser can set this for any user via the Django admin web UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Search results for query "dO"