Search results for "Postorius" - Mailman-users

Re: upgrading in FreeBSD 13.1-p7: problem with aiosmtpd and lmtp runner

by Mark Sapiro

On 4/3/23 23:12, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Just to make it clear: It happened upgrading from 3.3.7 to 3.3.8 > > The upgrade procedure I did all the times is > > pip install --upgrade django-mailman3 mailman mailman-hyperkitty > mailmanclient postorius django hyperkitty uwsgi mod-wsgi > > and if I see some trouble I did it with a --force-reinstall parameter > (not that I remember it happened last times that I upgraded) > > (and then the collectstatic, etc.) > > If I missed something, I don't know. Mailman 3.3.5, 3.3.6 and 3.3.7 all required aiosmtpd>=1.4.1 so your prior upgrades should have installed aiosmtpd>=1.4.1. Possibly aiosmtpd>=1.4.1 was installed somewhere, but your jail configuration was such that it wasn't the one actually used by lmtp runner. -- 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

API errors making member changes to one list but not others

by Stephen J. Turnbull

Stephen Willey Mats Mats writes: > mailman3 should do a better job of reporting errors and recovering > when accidents happen. It appears that the side which is logging the errors is working fine. It expects to receive data which is not arriving, so there's a timeout. So probably it's on the Postorius side, which is not in these logs. I don't recall offhand if Django keeps its own logs, if it does and you have them, it would help to understand the problem and design a mitigation. But since it's a network connection, it could be any number of things in the middle, too -- even a kernel problem. If you have ideas about how better to report, fine, but it seems to me that in case of a major system incident, it's better to leave the diagnosis of faults in the interactions such complex systems to the humans. Steve

5 years, 1 month

Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save

by Henrik Rasmussen

I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? I am currently using Postorius Version 1.3.5 and HyperKitty version 1.3.4. /Henrik

1 year, 7 months

Re: User settings triggers error

by Mark Dadgar

On Jun 18, 2020, at 3:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/18/20 2:23 PM, Mark Dadgar wrote: >> >> There is definitely something sketchy going on here. As an admin, I am not getting accurate subscription status about people on a list. For example, I search for a list member, find their listing, check the box and click Unsubscribe Selected, and get an error because it turns out that they had already unsubscribed themselves previously. But Postorius thought they were still subscribed. >> > ... >> Could this somehow be related to my recent migration from sqlite3 to postgres? > > I think it's quite likely that that migration is involved and your > database is now corrupted in some way. Exactly how or in what way, I > don't know, but it seems likely to me that that's the issue. Oh good. Any thoughts on how to salvage ~20 years of list archives? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 9 months

Members (and moderators) can't view the list of members.

by mrl＠psfc.mit.edu

I installed Mailman 3 almost 2 years ago. I only now noticed that members of a mailing list can't view the list of members. Even moderators can't see the list. Only Owners. The error message is "You do not have permissions to visit this page." Mailman Core Version GNU Mailman 3.3.8 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] Postorius Version 1.3.8 Any ideas? I did make a few "minor" changes to the code, but hopefully it didn't cause this problem. What file(s) contains the code that checks for permissions? Or maybe there is a config file? I also notice by default, for all users, in their "Global Mailman Preferences", the default setting for "Hide Address" is "Yes". How can I change that to be "No". And can I reset that setting for all my present users? Thanks. - Mark

1 year, 4 months

Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 10/26/25 10:38, Cathryn McGuire wrote: > > Since setting to Default Processing, ALL members posts are being held for moderation. That's what happened last time. Obviously there's some setting somewhere that's telling the list to do that with that setting. We'll try to find it by doing testing like you said. Meanwhile, we're quite busy in our other endeavours and having to unblock every post (some days more than others, and not that many relatively speaking) is what we're doing. What is the reason given for the post being held? I don't know about affinity, but Postorius gives the reason in the list of held messages. Also the message itself has a X-Mailman-Rule-Hits: header that says which rule caused the message to be held -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 months, 3 weeks

Re: No styling for web apps?

by Mark Sapiro

On 11/26/20 8:44 PM, Morris Jones wrote: > I have most of a new mailman suite server built and working ... > > collectstatic gathered a good array of static files (uncompressed so far) > > nginx appears to be serving them successfully > > The Firefox developer tools show css and js files all being delivered > > But none of the postorius or hyperkitty pages exhibit any styling at > all, only bare HTML elements. > > The Firefox inspector will show the available styles being requested and > delivered (style.css, bootstrap, jquery, all the things). > > But if I use the inspector to look at the page, nothing has any CSS > properties. > > I know I'm missing something simple. Try running collectstatic and, if you use it, compress again. These have to be run following various kinds of changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Help Setting Up Mailman 3 on an Ubuntu Server

by smith.ja1ck＠gmail.com

Hello All Community Member, I am in the process of setting up Mailman 3 on an Ubuntu 22.04 server & have faced some challenges during the configuration phase. Also I have followed the installation guide & while Mailman Core and Postorius seem to be working I am struggling to configure the Mailman web interface correctly with NGINX. Also I have tried a few different configurations for the reverse proxy but I m running into 502 Bad Gateway errors. Does anyone have experience setting up Mailman 3 with NGINX who might be able to offer some guidance? ?I am interested in seeing a working configuration file for NGINX and any tips on troubleshooting Mailman 3 issues during this phase. As well, I found these resources when doing research on this; https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://redacted If anyone have any resources, tutorials or personal experiences please share with me, It would be greatly appreciated!!

1 year, 5 months

Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by Mark Sapiro

On 2/18/22 11:28, gordon(a)dickens.com wrote: > Thanks Mark! > > Here is the Traceback from the error: > > Traceback (most recent call last): > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 34, in inner > response = get_response(request) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 115, in _get_response > response = self.process_exception_by_middleware(e, request) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 113, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 71, in view > return self.dispatch(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/views/generic/base.py", line 97, in dispatch > return handler(request, *args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/views/list.py", line 326, in get > primary_email = set_preferred(request.user, mm_user) > File "/opt/mailman/venv/lib/python3.9/site-packages/postorius/utils.py", line 64, in set_preferred > primary_email = EmailAddress.objects.get_primary(user) > File "/opt/mailman/venv/lib/python3.9/site-packages/allauth/account/managers.py", line 30, in get_primary > return self.get(user=user, primary=True) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/venv/lib/python3.9/site-packages/django/db/models/query.py", line 419, in get > raise self.model.MultipleObjectsReturned( > > Exception Type: MultipleObjectsReturned at /mailman3/lists/testing.dickens.com/ > Exception Value: get() returned more than one EmailAddress -- it returned 3!\ Thank you for this info. I've never seen this exact issue. What you have is a Django User with more than one primary email address. It may be you. Go to the Django web admin UI at https://host2.mailhub4u.com/admin/account/emailaddress/?q=gordon where you should see multiple email addresses for user `gordon`, three of which are primary. Go to each address and uncheck primary for all but one of them. If it's not you, see the Mult_primary script at https://gitlab.com/mailman/django-mailman3/-/issues/53#note_842641913 to find who, but this script would need to be modified for other than a postgresql database. -- 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

Re: archiving problem & updates

by Brian Carpenter

On 2/18/21 1:00 PM, Christian Stalberg via Mailman-users wrote: > Archiving has stopped working. No changes were made to the server. How can I diagnose and troubleshoot this please? > > Are there instructions for how to update mailman3 somewhere? Is there a listing of bug fixes also? > > Thank you! > _______________________________________________ > 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/ If this is in regards to the server I install Mailman on, then here are the update instructions to use: # cd /opt/mailman/mm # su mailman # source /opt/mailman/mm/venv/bin/activate # pip install --upgrade mailman hyperkitty postorius # pip install --upgrade django-mailman3 mailmanclient mailman-hyperkitty You may need to update flufl.lock as well: # pip install --upgrade flufl.lock # bin/mailman-post-update # deactivate # exit (this should take you back to root user) # systemctl restart mailman # systemctl restart qcluster # systemct restart gunicorn -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

Mailman-users search results for query "Postorius"