Search results for "Postorius" - Mailman-users

Re: Default values for lists in Mailman 3

by Mark Sapiro

On 9/30/24 02:17, Markus Grandpré wrote: > Dear Mark, dear list, > > in Menu "Mass Operations / Mass Subscription" I have set the default > value for checkbox "Invitation" in file > </usr/lib/python3/dist-packages/postorius/forms/list_forms.py> (on > Debian 12) as you had suggested: > > > invitation = forms.BooleanField( > label=_('Invitation'), > initial=True, > required=False, > help_text=_( > 'If checked, the other checkboxes are ignored and the users > will ' > 'be sent an invitation to join the list and will be > subscribed ' > 'upon acceptance thereof.' > ), > widget=forms.CheckboxInput(), > ) This is correct. > However, administrators of mailing lists on our Mailman3 demo system > report that the invitation is still sent, even if they have deactivated > the sending of the invitation via the “Invitation” checkbox. If the admin is unchecking the Invitation box but not checking the Pre Verified box, the user will still be sent an address confirmation request. Perhaps the admins are mistaking this for an invitation. It the desire is to immediately subscribe the user with no further interaction, in addition to the Invitation box being unchecked, all three of the Pre confirm, Pre approved and Pre verified boxes must be checked. You may wish to set the Pre Verified default to checked in a manner similar to the above, or with Postorius >=1.3.14 (not yet released) you will be able to add ``` POSTORIUS_DEFAULTS = { 'mass_subscription_pre_verify': True } ``` to your Django settings to accomplish this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

El 26/12/22 a las 16:08, Odhiambo Washington escribió: > On Mon, Dec 26, 2022 at 5:07 PM Eggert Ehmke<eggert(a)eehmke.de> wrote: Odhiambo, I didn't change anything from my config as I wrote down in https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128, save the python version (I upgraded to 3.9 moths ago, as I posted in this list). My urls.py looks like this: ################### from django.conf import settings ### mod. 30/10/22 ###from django.conf.urls import include, url from django.conf.urls import include from django.urls import re_path as url ##### from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView urlpatterns = [ url(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), url(r'^postorius/', include('postorius.urls')), url(r'^hyperkitty/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), ] >> Ok, >> >> I hope this is readable. I just copíed the content of some files into the >> pastebin, don't know if it is possible to post tar.gz there. >> https://pastebin.ubuntu.com/p/mmRJJwKDc3/ >> >> Just tell me if this works for you, and when something is missing. >> Most of the settings are copied from some other sites and just adjusted >> for my >> needs. >> Good luck! > > So it seems your WSGIDaemonProcess is defined somewhere outside the VHOST, > right? Or it wasn't necessary? > And what does your urls.py look like? > > My setup is PUBLIC for everyone so I will not hide the domain name :-) > > In my setup, MM3 is installed in /opt/mailman/mm/. and mod_wsgi is enabled > in Apache. > I am running uwsgi on a TCP socket, not unix socket. > > The whole of my *VHOST:* > <CUT> > WSGIDaemonProcess mailman-web display-name=mailman-web > maximum-requests=1000 umask=0002 user=mailman group=mailman > python-path=/opt/mailman/mm:/opt/mailman/mm/venv/lib/python3.9/site-packages:/opt/mailman/mm/venv/lib/python3.9 > python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var > WSGIRestrictSignal Off > <VirtualHost *:443> > ServerName mm3-lists.kictanet.or.ke > > SSLEngine on > SSLCertificateFile "/usr/local/etc/letsencrypt/live/ > mm3-lists.kictanet.or.ke/cert.pem" > SSLCertificateKeyFile "/usr/local/etc/letsencrypt/live/ > mm3-lists.kictanet.or.ke/privkey.pem" > SSLCertificateChainFile "/usr/local/etc/letsencrypt/live/ > mm3-lists.kictanet.or.ke/chain.pem" > CustomLog /var/log/mm3-lists-access.log combined > ErrorLog /var/log/mm3-lists-error.log > LogLevel info > Alias /favicon.ico /opt/mailman/mm/static/hyperkitty/img/favicon.ico > Alias /static "/opt/mailman/mm/static" > <Directory "/opt/mailman/mm/static"> > Require all granted > </Directory> > WSGIScriptAlias / /opt/mailman/mm/wsgi.py > <Directory "/opt/mailman/mm/"> > <Files wsgi.py> > Order deny,allow > Allow from all > Require all granted > </Files> > WSGIProcessGroup mailman-web > </Directory> > </VirtualHost> > </CUT> > > *2. uwsgi.ini:* > <CUT> > [uwsgi] > http-socket = 127.0.0.1:8000 > pidfile = /opt/mailman/mm/var/uwsgi.pid > chdir = /opt/mailman/mm/ > virtualenv = /opt/mailman/mm/venv/ > module=mailman_web.wsgi:application > env =PYTHONPATH=/opt/mailman/mm/ > env =DJANGO_SETTINGS_MODULE=settings > master = true > process = 2 > threads = 2 > attach-daemon = /opt/mailman/mm/venv/bin/mailman-web qcluster > req-logger =file:/opt/mailman/mm/var/logs/uwsgi.log > logger = qclusterfile:/opt/mailman/mm/var/logs/uwsgi-qcluster.log > log-route = qcluster uwsgi-daemons > logger = cronfile://opt/mailman/mm/var/logs/uwsgi-cron.log > log-route = cron uwsgi-cron > logger =file:/opt/mailman/mm/var/logs/uwsgi-error.log > uid = mailman > gid = mailman > </CUT> > > *3. uwsgi - *Running supervised (supervisord): > <CUT> > [program:uwsgi] > directory=/opt/mailman/mm/ > environment=PYTHONPATH=/opt/mailman/mm/ > command=/usr/bin/su -m mailman -c '/opt/mailman/mm/venv/bin/uwsgi --ini > /opt/mailman/mm/uwsgi.ini' 2>&1 | logger -t uwsgi > autostart=true > autorestart=true > user=mailman > group=mailman > stopasgroup=true > killasgroup=true > </CUT> > > *4. urls.py*: > <CUT> > from django.conf.urls import include > from django.urls import re_path > from django.contrib import admin > from django.urls import reverse_lazy > from django.views.generic import RedirectView > from django_mailman3.views.profile import delete_account, user_profile > 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'^user-profile/delete$', delete_account, > name='mm_user_account_delete'), > re_path(r'^user-profile/$', user_profile, name='mm_user_profile'), > re_path(r'^accounts/', include('allauth.urls')), > re_path(r'^admin/', admin.site.urls), > re_path(r'^mm/', include('postorius.urls')), > re_path(r'^archives/', include('hyperkitty.urls')), > ] > </CUT> > > And that's pretty much what I am using on my FreeBSD server. > > > PS: Possible to bottom-post instead of top-posting? :) > -- ___________________________________________ 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, 5 months

Re: One-click unsubscribe?

by Stephen J. Turnbull

Jered Floyd writes: > > I guess it would be a matter of keeping 2 tokens in the database. > > In the case we sign/encrypt a tuple of (list, subscriber, > timestamp) we don't need to store anything in the database. True, but I'm concerned with the computation cost of validation. That shouldn't matter ordinarily, legit unsubscribes will be rare, but it could be a vulnerability to a DOS attack. > Option 1: signed/encrypted tuple (list, subscriber, timestamp) > Option 2: UUID referencing a unique subscription in the database > > Sounds like you are favoring the 2nd option? Yes, with explicit timestamp. The concerned party has knowledge of the first two. None of that is anybody else's business. Nerds like me would be pleased to be told the third component, and if expiration times are going to be "several months" as you suggested, I figure they should last as long as the signing key does. > RFC 8058 doesn't specify response codes or really any behavior in > response to the POST request. The user never sees this interaction. Probably not. It's a little surprising that they said almost nothing (except some dark mutterings about hints that the address is valid). Maybe it's not necessary. If the list wants to they can provide a goodbye message, and if it fails the subscriber will get a valid token. :-) I just think it would be kind of rude not to give a response in the case of an expired token, because the subscriber did everything right as far as they can see. > On the other hand, in Postorius we probably want to support a GET > interaction against the same URI which provides a page with a > button that generates the equivalent POST. I don't think so. We can already put the list and address in the footer's unsubscribe link.[1] That would likely involve a login interaction.[2] The token alone wouldn't be sufficient credentials, because the footer is extremely likely to leak into public spaces. > Incidentally, I imagine 8058 defines this as a POST interaction to > avoid the mail-scanner issue we talked about last message. Ah, good point. I've worked with John Levine, he's that smart and definitely that WG is that smart. > Ah, to be outside the US, where the concept of consumer protections > still exists... Lina Khan lives! Footnotes: [1] Of course this would require changing GET processing of the unsubscribe link, it doesn't work that way now. But this should be a separate feature from RFC 8058 processing. [2] If the user has a Postorius session active, they'll be whisked on through. But most users won't. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 2 weeks

Customizing Postorios web templates

by Stephen J. Turnbull

Stefan Bethke writes: > I have two list servers that I would like customize the web pages > for, specifically I need to add some legal information to the > footer, and I might want to apply some light branding to the > site. I can't find any hints on how to do that, maybe I'm looking > in the wrong place? Postorius is a Django application. There are copious docs on djangoproject.com. We really don't want to duplicate the upstream project's documentation, especially since our downstream (ie, OS distros) are likely to have various different versions of Django installed in their packages. The basic procedure is to add a local template path (I use /etc/mailman3/templates) early in Django's template path in /etc/mailman3/settings.py. Then copy any templates you want to modify to the right place in that local template hierarchy and modify them there. > If Postorious does not currently allow that outright, It does, there's no need to vendor Postorius. > If so, would there be interest in adding a feature to define some > blocks that can be overridden more easily, Don't think this approach is better than overriding base.html if you want sitewide legal and branding. It would be more appealing if it were list-specific. It might be slightly more convenient, but you still need to create the local template hierarchy. On the other hand, it would increase the documentation burden. And for obvious reasons we don't want to make it too easy to replace our own branding. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

4 months

mailman-web: ResponseNotReady

by Dmitry Makovey

We've had an odd experience with mailman3 containers: ERROR 2017-10-18 15:47:09,448 60 django.request Internal Server Error: /postorius/lists/ Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/django/core/handlers/exception.py", line 39, in inner response = get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 249, in _legacy_get_response response = self._get_response(request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 187, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 185, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", line 590, in list_index choosable_domains = _get_choosable_domains(request) File "/usr/local/lib/python2.7/site-packages/postorius/views/list.py", line 524, in _get_choosable_domains return [(d.mail_host, d.mail_host) for d in domains] File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 217, in __getattr__ return self._get(name) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 183, in _get return self.rest_data.get(key) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 172, in rest_data response, content = self._connection.call(self._url) File "/usr/local/lib/python2.7/site-packages/mailmanclient/_client.py", line 109, in call response, content = Http().request(url, method, data_str, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1659, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1399, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/local/lib/python2.7/site-packages/httplib2/__init__.py", line 1355, in _conn_request response = conn.getresponse() File "/usr/local/lib/python2.7/httplib.py", line 1108, in getresponse raise ResponseNotReady() ResponseNotReady It seems like mailman-core is still operating properly, but for some reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? -- Sr System and DevOps Engineer SoM IRT

8 years, 8 months

Problems with mailman core translation and other details

by celi＠dieese.org.br

Hi. We did a fresh install of the Debian Mailman 3 full package. I'd like all components to be translated into pt_BR. I downloaded the latest updated translations from weblate, which says that 100% of the project (all components) are translated. I checked and recompiled mailman.po with msgfmt without errors. I followed all instructions I saw, included the ones from the topic How to change the language in mailman3 in this list. Everything almost OK, except from the fact that none of mailman's core email messages are being translated, even though mailman.po shows the right messages. Also, strange things happen to these .po files. The web interface is almost perfect, but some messages (just some) are not correct - although the corresponding django.po appears to be OK. It´s the case below: the pair msgid/msgstr seems to be OK, but this particular sentence is not being translated. #: templates/postorius/lists/summary.html:88 #, python-format msgid "" "\n" " To subscribe you can send an email with 'subscribe' in the " "subject to\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " or use the form below:\n" " " msgstr "" "\n" " Para se inscrever você pode enviar um e-mail com o assunto " "'subscribe' para\n" " <a href=\"mailto:%(address)s?subject=Subscribe\">" "%(address)s</a>\n" " ou use o formulário abaixo:\n" What am I doing wrong? Or what can I do to make things suitable? Additional info: GNU Mailman 3.3.3 (Tom Sawyer) Python 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] Postorius v. 1.3.4 HyperKitty v. 1.3.4 Thanx for any help

2 years, 4 months

Re: Incorrect error log message in OutgoingRunner._dispose()

by Mark Sapiro

On April 25, 2026 10:27:06 PM GMT+02:00, Craig Leres via Mailman-users <mailman-users(a)mailman3.org> wrote: > >One feature the existing mailman 2 lists uses that I can't get working with mailman 3 are templates. After using "mailman import21" I found files with names such as list:member:regular:footer.txt in the list tree. However they were ignored so I removed them I tried tried creating a template using the web postorius gui. When a message is injected, I see an error log from the out runner: Did you by chance run import21 as root or another non-mailman user resulting in template files unreadable by Mailman? > Apr 25 12:32:22 2026 (82977) Cannot connect to SMTP server 127.0.0.1 on port 25 This is a well known issue. See <https://gitlab.com/mailman/mailman/-/work_items/582> and related issues referenced therein. >Following the error message, the out runner goes cpu bound, creating and deleting queue files in queue/out with .pck and .bak extensions, very quickly. > >I updated the code to print the exception and it tells a completely different story: > > Apr 25 12:38:15 2026 (83339) Cannot connect to SMTP server 127.0.0.1 on port 25 (HTTPConnectionPool(host='localhost', port=8000): Max retries exceeded with url: /api/templates/list/test.example.com/list:member:regular:footer (Caused by NewConnectionError("HTTPConnection(host='localhost', port=8000): Failed to establish a new connection: [Errno 61] Connection refused"))) > >I'm using the default webservice port (8001) so I would not expect anything to ever be listening on 8000. The default web service port (Postorius and HyperKitty) is 8000. Port 8001 is Mailman core's rest api. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 month, 4 weeks

Mailmanweb RAM Usage

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > Using the uwsgi.ini from the virtualenv method documentation, > mailmanweb is constantly using 2GB RAM on my server. Do you mean only HyperKitty + Postorius? That seems like a lot. My experience is that even on an insanely heavily loaded server (20k+ lists) the whole suite uses about 2.0G. Since on that server, Mailman core was forking 22 processes at ~83MB each (very little shared, not sure the technical reason for that, maybe the Python heap just can't be shared?), core was taking up about 1.8G. HyperKitty and Postorius took a little more (I don't recall exactly, maybe 250MB?) My more standard setup (that one had like 2 IN queue slices and 8 OUT queue slices) I ran Mailman suite + PostgreSQL (dedicated to Mailman) + Postfix + nginx (also mostly dedicated to Mailman) + Cyrus IMAPd in a nominal 2GB Digital Ocean droplet. It didn't run "comfortably", adding any serious load that chewed up 100s of MB RAM would get things OOM-killed, but 2GB total (including kernel and all) was barely enough for that system in normal situations. > My database (MariaDB) size is 2GB. Do you mean in memory or on disk? Either way that should have ~0 effect on the size of the Mailman core and web processes. > Is this expected? Depends on if you mean exactly what you said ("mailmanweb"). If so, no, I would expect mailmanweb (only) to run in 500MB easily and probably be OK in 250MB. If you mean "when I start Mailman and mailmanweb, memory usage jumps by about 2GB", then yes, that's what I'd expect. -- 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

Re: Patch/kludge suggestion and a question on adding accepted addresses

by David Krantz

On Sun, Apr 23, 2017 at 11:04 PM, Barry Warsaw <barry(a)list.org> wrote: > On Apr 23, 2017, at 10:33 PM, David Krantz wrote: > >>I'd suggest adding a catch for AttributeError similar to the one for >>KeyError in _HeldMessageBase in rest/post_moderation.py. It solved my >>immediate problem at least. I run the version from git with the tag >>263711b3b7988c7c474e3b8952dc7e0f02f04fa2 > > Can you file a bug and attach either the problematic message or the traceback? Will do. I have lost the message (I was too quick in removing it), but I of course still have the stacktrace. And I have a patch for my kludge. > Did you talk to your MTA's SMTP port, to Mailman's LMTP port, or some other > process? It matters because LMTP is the way messages get from the upstream > SMTP daemon (e.g. Postfix, Exim) into Mailman, and the LMTP server rejects any > messages that don't have a Message-ID. It was to the SMTP port of the MTA. I can try to recreate it although I have better filters now so it might be difficult to get passed to mailman. >>I have another question: In the old mailman you could add accepted >>senders without adding them to the list. Is that possible in Mailman >>3/Postorius? > > You do this by creating a "nonmember" subscription for the sender, and then > setting that member's moderation_action to Action.accept. Okay. I see no way of doing that in my instance of Postorius but in this case it is okay to do it in the command prompt. cheers, // David

9 years, 1 month

Re: Change language to welcome message in mailman3

by Mark Sapiro

On 7/24/20 2:10 PM, Massimo Zappalà wrote: > Hi everyone, > > My Version installed on Debian buster: > mailman3: 3.2.1 > postorius: 1.2.4 > hyperkitty: 1.2.2 > > All interfaces work well in Italian language, but "Welcome message" is in English. First question: Is the Subject: in English or Italian? If the Subject: is in English you need to compile the Italian message catalog as I described in my reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. Then, as far as the message body is concerned, it is built from a template. At present, in the Mailman source distribution, the only templates that are translated are French and German You will find the complete set of English templates at /usr/lib/python3/dist-packages/mailman/templates/en/. You have choices. 1) You can create /usr/lib/python3/dist-packages/mailman/templates/it/ and make Italian translations of all the English templates in the it/ directory in files of the same names, and submit a merge request at <https://gitlab.com/mailman/mailman/-/merge_requests> to merge them into the source distribution. If you are not familiar with software development in general and Mailman development in particular, this is probably beyond what you can do. 2) Find Mailman's var/ directory. This is the directory containing archives/, data/, etc/, lists/, locks/, logs/ and perhaps other sub-directories. You then need to create the full path to var/templates/site/it/ and place Italian translations of some or all the templates there. When doing so, you can add site customizations. 3) You can use Postorius to create templates for individual lists. -- 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

Mailman-users search results for query "Postorius"