Search results for "Postorius" - Mailman-users

Re: Python 3.13 compatibility

by Thomas Krichel

Thomas Krichel writes > What now? Actually it looks I could do pip install -U mailman==3.3.9 postorius django-mailman3 hyperkitty mailman-web To get back to a working system But that still leaves me without 3.3.11 which I apparently need for my import21. -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22213th day.

5 months, 3 weeks

Changing default language for lists

by Wessel Kraaij

How can I change the default language for lists (and other defaults)? I changed it in mailman-core but Postorius overrides these core defaults with a patch. I am using the docker version of maxking Wessel

5 months, 1 week

FutureWarning: Use `header_id_prefix` instead

by Andreas Vetter

Hi, after a recent update of the prerequisites using: pip install -U --upgrade-strategy eager mailman postorius django-mailman3 hyperkitty mailman-web I get warnings from the cronjobs: /opt/mailman/venv/lib64/python3.11/site-packages/readme_renderer/ markdown.py:44: FutureWarning: Use `header_id_prefix` instead gfm_extension_options.header_ids = _HEADER_ID_PREFIX What would be the best way to silence the warnings? Google does not find the warning message yet. Cheers, Andreas

1 month, 3 weeks

Re: FutureWarning: Use `header_id_prefix` instead

by Andreas Vetter

Am Tuesday, 28 July 2026, 10:40:51 Central European Summer Time schrieb Andreas Vetter: > Hi, > after a recent update of the prerequisites using: > pip install -U --upgrade-strategy eager mailman postorius django-mailman3 > hyperkitty mailman-web > > I get warnings from the cronjobs: > > /opt/mailman/venv/lib64/python3.11/site-packages/readme_renderer/ > markdown.py:44: FutureWarning: Use `header_id_prefix` instead > gfm_extension_options.header_ids = _HEADER_ID_PREFIX > > What would be the best way to silence the warnings? Google does not find the > warning message yet. > > Cheers, > Andreas Quick fix is to change line 44 in /opt/mailman/venv/lib64/python3.11/site- packages/readme_renderer/markdown.py from gfm_extension_options.header_ids = _HEADER_ID_PREFIX to gfm_extension_options.header_id_prefix = _HEADER_ID_PREFIX Greetings, Andreas

1 month, 3 weeks

Restrict the visible mailing lists to the current domain?

by dirk＠computer42.org

Hi! my mailman instance is hosting mailing lists for different domains. How can I restrict the visible mailing lists to only the mailing list of the current domain. See e.g. https://lists.weg-der-sterne.de/mailman3/postorius/lists/ or https://lists.computer42.org/mailman3/postorius/lists/ Both web sites are displaying all public lists – also from the „foreign“ domain. Best regards, H.-Dirk Schmitt

2 days, 16 hours

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >It is the intent that Postorius will eventually expose all these >settings. We're not there yet. At present you could possibly do this by >interacting with mailmanclient, although I'm not certain the settings are >exposed there. I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the `delivery_mode` attribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum). Cheers, -Barry

10 years, 4 months

Re: Rejection Reason for refusing a subscription request

by Brian Carpenter

On 3/27/21 6:03 PM, Mark Sapiro wrote: > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I am referring to "Subscriptions pending approval". I apologize if I did not make that clear. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

Re: sqlite3 Database "read only" error on mailman_sync job

by Abhilash Raj

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)

7 years

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

by Andreas Schamanek

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

3 years, 5 months

Fwd: Re: Removing a mail addresses and users

by Allan Hansen

All, This disconnect between Mailman Core and Django and Postorius is, by far, the weakest and, for subscribers, most confusing aspect of MM3 (once it has been installed, which is extremely hard and confusing). In a true account-centric system, you set up a web account and from there manage your emails and, for each email, your subscriptions. Subscription options would be hierarchical: account/email/list, with lower levels inheriting/overriding settings from/the level above. That’s really what I had expected when I pushed for us to move our 50 email lists to MM3 and I was very excited about the prospect, as it would solve a lot of system/subscriber management issues I had managing MM2. Alas, I was very surprised that that’s not how MM3 works. Some things got harder, even, such as the inability to change subscription addresses, which should have been a showstopper from the start! I still hope that MMxx OOTB will get there, but I guess it’ll be along haul. Would we be talking about MM4 to be released 20 years from now? Some dedicated and skilled developers are currently investing heavily in a replacement for Postorius, but I really believe that any work is better spent transforming Mailman Core etc. into a true account-based system. Then, and only then, will it make sense to build new and better interfaces on top, as, without a healthy core, such interface will currently may have to inherit the confusion and disconnect that currently is so aggravating. The above is not meant to aggravate the MM3 development team, for which I have utmost respect and gratitude, and which I admire for their tireless support given over decades to the community of admins. Software development is devilishly hard and time consuming. Yours, Allan Hansen hansen(a)rc.org > Begin forwarded message: > > From: Mark Sapiro <mark(a)msapiro.net> > Subject: [MM3-users] Re: Removing a mail addresses and users > Date: June 10, 2020 at 12:46:01 PDT > To: mailman-users(a)mailman3.org > > On 6/10/20 10:23 AM, Abhijith PA via Mailman-users wrote: >> Hello. >> >> I tried to remove random email address signing ups (which I signed up >> while testing) via admin panel. After removing I tried to sign up again, >> but I am getting, >> >> 'A user is already registered with this e-mail address' > > You removed the user's subscription from the list, but you didn't remove > the user from the system. > > Mailman3 has a concept of `user` which didn't exist in Mailman 2.1. > User's have addresses and a user or one of the user's addresses can > belong to a list with one or more roles (non-member, member, moderator > or owner) > > >> Combing through the database, I found auth_user table in mailman3web db >> still contain those mail address. How to wipe email address entirely >> from the db so I can signup again without the 'forget password' method > > There are a couple of things. If you log in to the web UI as a django > superuser, you can go to the django admin UI -> Users section and delete > the User, but I think that will only delete the web user and not delete > the user from Mailman core. > > You can also log in to the web UI as the user and go to > <https://lists.mailman3.org/user-profile/delete>, but that again only > deletes the web user, and if you could do that, you could just subscribe > once you're logged in, so I assume that's what you want to avoid. > > I don't think there is a way for a user as opposed to a site admin to > delete her user record from Mailman core and even for a site admin, > there's no way in Postorius to delete a user from core. It has to be > done via REST > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> > or `mailman shell`. > > -- > 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/

6 years, 3 months

Mailman-users search results for query "Postorius"