Search results for "Postorius" - Mailman-users

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, 2 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 23:53, Mark Sapiro wrote: > On 2/13/21 11:52 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> On 13/2/21 20:00, Mark Sapiro wrote: >>> If there are issues in this mailman.po, they exist in weblate too and >>> need to be fixed there. >> That clarifies all. Thanks. As I said in my previous message, I'll wait >> for the next upgrade and hopingly the translations done after 7h of >> november (by others and me) will be there. > > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. > Well.. It surely is in the case of mailman core, but not in postorius, hyperkitty and django_mailman3. And these are what are serving the translated terms what the users see. 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. I saved a backup copy of the "django.po" that lies in the packages path for the es language. In my case /usr/local/lib/python3.7/site-packages/[package]/locale/es/LC_MESSAGES and replaced by the downladed file, changing the name (as all of them was named django.po in destination). Then I did, as you pointed in a message and Victoriano found the right way in our systems, a django-admin compilemessages for each package. And now I have all the postiorius web interface correctly translated (at least almost all of it). Now I can make a tutorial for my moderators and users without them complaining about the mixing language terms. I have also a screencopy of before-after If someone wants to see the changes. Thanks all for your support.

4 years, 8 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, 4 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

11 months, 2 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

4 years, 10 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

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

4 years, 8 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

3 years, 8 months

Re: Held messages page not rendering the message

by Odhiambo Washington

On Sun, Mar 19, 2023 at 1:12 PM <mike-mailman(a)earth.li> wrote: > Thanks - may be on to something. > > The sources tab shows everything ok except for > /mailman3/static/postorius/js/script.js for which it says "Unable to fetch > script source" > However the network tab shows it successfully retrieving it. > > /var/lib/mailman3/web/static/postorius/js/script.js exists and contains > only comments > Is anything showing up in your webserver logs that is related to this? Just maybe. I have tested on my setup (although I use a virtualenv setup) and I see as a click on a held message corresponds to a log entry in my webserver log. I do get a pop-up like this: ``` https://imgur.com/a/esxmDsK ``` And that is the same across all my browsers. My Desktop is running Winblows11 though. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 7 months

Re: Issues with @gmail.com addresses

by Mohsen Masoudfar

Thank you Mark for your response as always! I checked the lists having the issue of sending emails to @gmail.com subscribers. They had already these settings (so no changes): DMARC Mitigate unconditionally : yes DMARC mitigation action: Replace From: with list address DMARC rejection notice: empty DMARC wrapped message text: empty I wonder three points: * What would be the next action to fix the issue? * This issue started around the beginning of August. Could it be due to some changes google made recently? * Give the number of Gmail users, this should annoy a bigger community, are you seeing that many upset people? Thanks, Mohsen ________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Tuesday, September 5, 2023 4:17 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Issues with @gmail.com addresses [EXTERNAL EMAIL] On 9/5/23 12:59, Mohsen Masoudfar wrote: > Hi, > > since 8/1/2023 I get complains from users with @gmail.com addresses, that they are not getting any emails. > I checked the logs and I see that the emails are going out: > > to=<xxxx(a)gmail.com>, relay=email-smtp.us-east-1.amazonaws.com[35.169.171.20]:587, delay=0.46, delays=0.03/0.06/0.13/0.24, dsn=2.0.0, status=sent (250 Ok xxx ) > > But it seems the users are getting email delivered to them. > I’ve advised them to check their spam, promotions, and social folders and to add the list address to their email safe-senders lists, but still no success. > Is there any way to help this list members? Even though gmail publishes a DMARC policy of none, it has recently started enforcing a stricter policy for mail From: the gmail.com domain. You need to apply DMARC mitigations to mail From: the gmail.com domain. There are two ways to do this. One way is to set DMARC Mitigations -> DMARC Mitigate unconditionally to Yes (and set DMARC mitigation action appropriately) The other way requires upgrading Postorius and Mailman core to the heads of the GitLab branches (core=3.3.9b1, postorius=1.3.9b1). Doing this enables a DMARC Addresses setting which can be set to `^.*(a)gmail\.com$` to apply DMARC mitigatations to mail From: the gmail.com domain regardless of it's published policy. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

2 years, 1 month

Mailman-users search results for query "Postorius"