Search results for "Postorius" - Mailman-users

Re: Disabling Mass operations

by Mark Sapiro

On 1/23/26 17:39, iMark wrote: > Hi All, > > Can anyone give me a pointer on disabling "Mass operations" > (subscribe/removal) in Postorius. > > Just removing the menu link from the list-owners administration pages > would be a good start. This patch will do that ``` --- a/src/postorius/templates/postorius/menu/list_nav.html +++ b/src/postorius/templates/postorius/menu/list_nav.html @@ -84,6 +84,7 @@ {% if user.is_superuser or user.is_list_owner %} <li class="nav-item"><a href="{% url 'list_template_list' list.list_id %}" class="nav-link {% nav_active_class current 'templates' %}">{% trans 'Templates' %}</a></li> <li class="nav-item"><a href="{% url 'list_settings' list.list_id %}" class="nav-link {% nav_active_class current 'list_settings' %} ">{% trans 'Settings' %}</a></li> + {% if user.is_superuser %} <li class="dropdown nav-item"> <a href="#" class="{% nav_active_class current 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"> @@ -98,6 +99,7 @@ <li><a href="{% url 'mass_removal' list.list_id %}" class="dropdown-item">{% trans 'Mass removal' %}</a></li> </noscript> </li> + {% endif %} <li class="nav-item"><a href="{% url 'list_bans' list.list_id %}" class="{% nav_active_class current 'list_bans' %} nav-link">{% trans 'Ban List' %}</a></li> <li class="nav-item"><a href="{% url 'list_header_matches' list.list_id %}" class="nav-link {% nav_active_class current 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> <li class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` Some lines in the above may be wrapped but basically it just adds {% if user.is_superuser %} and {% endif %} around the Mass operations code. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by volkmar＠grote-family.com

Hi, today I installed MM3 with Nginx on Debian 11 following the document with a bit of "Mailman 3 installation experience" thrown in (many thanks to the authors!) with some minor changes, i.e. no encryption, and "re_path" instead of "url". I cannot get the web interface to run. "admin" is OK, but Postorius und Hyperkitty refuse to show up with > Page not found (404) > Request Method: GET > Request URL: http://127.0.0.1:8000/mailman3/lists/ > > Using the URLconf defined in urls, Django tried these URL patterns, in this order: > > ^$ > ^postorius/ > ^hyperkitty/ > ^user-profile/delete$ [name='mm_user_account_delete'] > ^user-profile/$ [name='mm_user_profile'] > ^accounts/ > ^admin/ > > The current path, mailman3/lists/, didn’t match any of these. > > You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. The error logs are all OK, the GET requests are logged without any error. My urls.py: > (venv) mailman@me:/opt/mailman/mm$ grep -v "^#" urls.py > from django.contrib import admin > from django.urls import include, reverse_lazy, re_path > from django.views.generic import RedirectView > > urlpatterns = [ > re_path(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > re_path(r'^postorius/', include('postorius.urls')), > re_path(r'^hyperkitty/', include('hyperkitty.urls')), > re_path(r'', include('django_mailman3.urls')), > re_path(r'^accounts/', include('allauth.urls')), > # Django admin > re_path(r'^admin/', admin.site.urls), > ] It must be something either really complex or, most likely, rather stupid. I switched from PC Assembler and C to Unix shell scripts some three decades ago, so I must admit that my Python skills are zero, my idea of the inner workings of all the packages is very vague. Any hints where I may look for installation errors? TIA Volkmar

3 years

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 2:16 PM, Odhiambo Washington wrote: > > root@gw:/usr/home/wash # ls -al /usr/local/include/sass > total 104 > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . > drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. > -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h > -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h > -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h > -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h > -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h > > I imagined I needed an executable. > > drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass Those are headers for compiling some sass. Possibly you actually have a `sassc` installed in which case you may need COMPRESS_PRECOMPILERS = ( ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), ) in your settings_local.py. See https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#instal… and the Sass compiler section at https://docs.mailman3.org/en/latest/install/virtualenv.html#dependencies. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 10:12 PM, Torge Riedel wrote: > Am 21.04.20 um 23:08 schrieb Brian Carpenter: >> Maybe I can get the client to agree to use the web domain as part of >> their list address. > > Hi, > > maybe it is a solution for you what I did on my side (since it was > already the setup for mailman2 my customer is happy with it): > > Set everything up in mailman3 with lists.domain.com and define in > postfix (if you use postfix, others should support it also) aliases from > - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail > list. > > In the list setup in mailman3 (available via postorius) define > list1(a)domain.com as an allowed alias for list1(a)lists.domain.com This is a good workaround, however to be complete, you may also want MTA aliases for the list1-*(a)domain.com addresses. Note, I'm currently working on a fix for <https://gitlab.com/mailman/postorius/-/issues/394>. Hopefully that will be in the next Postorius release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

SSO

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > Is it possible to set up SSO so that once users (owners,moderators) > set up an account in Postorius on the mailman3 server we have > created , they can authenticate against Azure to login instead of > the password for the local account Postorius created? Probably yes. This depends on how Azure passes on authentication data. I've done this with Shibboleth as the SAML 2.0 Service Provider. It's basically one line in /etc/shibboleth/attributes.xml[1], one line in the httpd conffile, and a short Python library wrapping Django's backend and middleware for the RemoteUser[2] class. I also populate the Mailman User profile with display name, email, etc, from the Identity Provider requiring one line per additional attribute in the same places. If this basic architecture works for you, depending on your WSGI provider, you may be able to eliminate the httpd conf. If you don't care about anything but the user id, you may be able to use the stock RemoteUser class. But I know nothing about how Azure does authentication, so I'll leave it there for now. Footnotes: [1] I've probably spelled that incorrectly, but you'll know it when you see it. :-) [2] This one, too. :-/

2 years, 10 months

Re: How to upgrade to 3.10

by Mark Sapiro

On 3/2/26 18:21, Paul Tomblin via Mailman-users wrote: > I installed 3.9 with pip last week, but i want to upgrade to 3.10. But > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web > doesn't upgrade it. Mailman core 3.3.10 was released to PyPI in October 2024 at any time thereafter `pip install mailman` should have installed Mailman 3.3.10. > Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) I don't know why 3.3.9 would have been installed at all. > Collecting mailman > Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) But it looks like here it's trying to install 3.3.10. > Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) > ... a bunch of these ... > INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. > Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) > ...a bunch more... Is there any conflict reported in this `bunch more` to force 3.3.9? What if you do `pip install mailman==3.3.10`? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

Re: Confirm and Moderate Unsubscribe Requests

by Brian Carpenter

On 10/21/20 1:14 PM, Mark Sapiro wrote: > On 10/21/20 8:53 AM, Brian Carpenter wrote: >> If you set the unsubscription policy to confirm then moderate for a list >> and someone unsubscribes, they receive a confirmation request. That is >> good. They respond to it. That is also working fine. However the list >> owner/moderator than gets a request to approve the unsubscribe request >> and well, unless I am missing something, I don't see an interface to >> handles such requests via Postorius. > > This is <https://gitlab.com/mailman/postorius/-/issues/332>. > > >> How does one handle an unsubscribe request that requires moderator >> approval? > > I'm not sure at this point, I can look further later, but if the notice > to the admin has a token, it might work to send a `confirm <token>` > command to the list-request address. > > Otherwise, don't moderate unsubscription requests. Well I can't dictate that to my list owners and there is no confirm token sent with the moderation notice. Why include this option in Postorius when it can't be properly handled? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

Re: Can't subscribe on new site/domain

by Flo

On 10/10/25 03:59, Mark Sapiro wrote: >> >> Is there a possibility to export all members including real names. It >> doesn't work with Postorius, yet, is there another possibility? If I >> have my user data exported, I could delete everything and start from >> scratch. Maybe this is the most reasonable ... > > You can install mailman following https://docs.mailman3.org/en/latest/ > install/virtualenv.html and keep your existing database(s) which will > include all lists and memberships. > I think I am still using a sqlite database. This is the database when I installed the packages. There is a hint that it should be replaced by mysql or postgres. I only have very few lists, yet. The only thing I really don't want to loose is the addresses and names. > The current released versions of Postorius include only emails in the > csv export. This is fixed for the next release by https://gitlab.com/ > mailman/postorius/-/merge_requests/993 > > You can currently get a list of members with display names with the > `mailman members` command. See `mailman members --help`. > This is working! That's great. Thank you! Flo

6 months, 4 weeks

[MM3-users]Moderation Emails & Page

by Douglas R Taber

Hey All- Having a bit of a problem, hoping maybe someone can provide some insight. I’m running the current MM3 from the bundler on RHEL7, and most things seem to be working properly. However, when i go to the moderation queue from the web interface, i’m presented with a 500 error instead of a page listing the messages being held. The error in the log (and on the page if i enabled debug) is: ERROR 2016-04-20 14:58:05,959 base 3256 140375419246336 Internal Server Error: /mailman3/lists/listname/held_messages Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python2.7/site-packages/postorius/auth/decorators.py", line 77, in wrapper return fn(*args, **kwargs) File "/usr/lib/python2.7/site-packages/postorius/views/list.py", line 413, in list_moderation paginator_class=utils.MailmanPaginator) File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 89, in paginate results = paginator.page(1) File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 62, in page number = self.validate_number(number) File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 39, in validate_number if number > self.num_pages: File "/usr/lib/python2.7/site-packages/django/core/paginator.py", line 86, in _get_num_pages if self.count == 0 and not self.allow_empty_first_page: File "/usr/lib/python2.7/site-packages/postorius/utils.py", line 75, in _get_count result = self.function(count=1, page=1) File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 681, in get_held_page return Page(self._connection, url, HeldMessage, count, page) File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 333, in __init__ self._create_page() File "/usr/lib/python2.7/site-packages/mailmanclient/_client.py", line 363, in _create_page self._connection, entry['self_link'], entry) KeyError: u’self_link' Anyone have any insight on what be causing the error? Thus far it only seems to be this page that is causing the issue, and only when messages are actually being held in the moderation queue. Semi-related, is there anyway to include the link to the moderation page from the moderation emails, similar to MM2? Thanks.

10 years

Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

El 26/12/22 a las 19:19, Mark Sapiro escribió: > On 12/26/22 07:42, Odhiambo Washington wrote: > >> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >> >> Does your https://site.name/user-profile/ work? > > Again, Guillermo is using uWSGI, not Apache mod_wsgi Well... now I am not sure, you know I've been confused before about that. In my httpd.conf I have: ############## LoadModule wsgi_module "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty ############### And in then end of my vhost definition file there is this line: Include "/usr/local/mailman3/apache24.uwsgi.conf" In that file I have: ######### begin of apache24.uwsgi.conf Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman3/static ######### # for hyperkitty Alias /static/admin /usr/local/mailman3/static/admin Alias /static/CACHE /usr/local/mailman3/static/CACHE Alias /static/django_extensions /usr/local/mailman3/static/django_extensions Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 Alias /static/rest_framework /usr/local/mailman3/static/rest_framework # for postorius Alias /static/postorius /usr/local/mailman3/static/postorius Alias /static/archives /usr/local/mailman3/static/postorius ##### ###ErrorLog /var/log/httpd/hyperkitty_error.log ###CustomLog /var/log/httpd/hyperkitty_access.log combined <Directory "/usr/local/mailman3/static"> Require all granted </Directory> #### esto va en el httpd.conf ##WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman group=mailman ## esta es la de Sapiro #WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 ####user=mailman group=mailman ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var #### agregado el 08/07/22 WSGIPassAuthorization On #### WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ####################### end of apache24.uwsgi.conf And the related wsgi.py is as follows: """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os from django.core.wsgi import get_wsgi_application #### os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") ##os.environ["DJANGO_SETTINGS_MODULE"] = "{{ project_name }}.settings" application = get_wsgi_application() ################ I don't want to put more noise in the list. But I'm confused because I always updated via pip the apache mod_wsgi thinking is was needed for my configuration. If it is not, I will stop updating it. -- ___________________________________________ 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, 4 months

Mailman-users search results for query "Postorius"