Search results for "Postorius" - Mailman-users

Re: Where does sender postorius@ come from?

by Jens Günther

Am 16.06.23 um 01:10 schrieb Mark Sapiro: > On 6/15/23 14:03, Jens Günther wrote: >> >> >> Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>>> - Then I tried settings_local.py with: >>>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > Sorry, this is actually a different setting. There are actually two more > that control this. These are DEFAULT_FROM_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> > and SERVER_EMAIL > <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note > that the defaults mentioned in the Django docs are probably overridden > in your settings.py, but you should set them in settings_local.py Thank you Mark. I changed now DEFAULT_FROM_EMAIL to my address, restartet container and it works. Also it works if I delete the EMAIL_CONFIRMATION_FROM-line again and do not put the SERVER_EMAIL, at least for the password-reset. Can you tell the diffenrence between the 3? Would you recommend to set all 3 to my admin-mailaddress?

2 years, 5 months

Re: old usernames appearing in mailman.log

by Mark Sapiro

On 6/26/23 10:12 PM, Ken Alker wrote: > --On Monday, June 26, 2023 5:03 PM -0700 Mark Sapiro <mark(a)msapiro.net> > wrote: >> >> Your urls.py file probably contains in its urlpatterns list >> ``` >> re_path(r'^mailman3/', include('postorius.urls')), >> re_path(r'^archives/', include('hyperkitty.urls')), >> ``` >> The simplest fix is to add >> ``` >> re_path(r'^postorius/', include('postorius.urls')), >> re_path(r'^hyperkitty/', include('hyperkitty.urls')), >> ``` >> to that list. > > I see many ursl.py files all over the system, but none that appear to be > where I'd expect them to be for processing by any executables. Is this > a file I should have copied over and edited, or created from scratch and > somehow missed? I don't see anything about it in the instructions at > <https://docs.mailman3.org/en/latest/install/virtualenv.html> (although > I do see a post from last July from someone stating it got missed in the > instructions back then). In your case, it is the one in /opt/mailman/venv/lib/python3.x/site-packages/mailman_web/, but it is not a good idea to change that as changes will be overwritten when mailman_web is updated. It's OK to not change it. Just do the following. >> Another way to fix this is in your mailman-hyperkitty.cfg, you have >> ``` >> base_url: https://lists.netlojix.com/hyperkitty >> ``` >> Change that to >> ``` >> base_url: https://lists.netlojix.com/archives >> ``` > > Done, and restarted both services, but I'm not seeing a difference when > I go to <https://lists.netlojix.com/hyperkitty/api/> (I was getting a > "Page not found", and still get that). That's because going to the 'hyperkitty' url won't work, but nothing should be doing that so it's OK if it doesn't work. Fixing mailman-hyperkitty.cfg will tell mailman-hyperkitty to use the 'archives' url, so now it should be working. The next post after you fixed it should archive OK and all the messages in /opt/mailman/mm/var/archives/hyperkitty/spool/ should also be archived and the files removed. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Installing mailman 3

by Rafael Mora

Clever idea Abhilash! Thanks El mié., 2 ago. 2017 a las 11:50, Abhilash Raj (<raj.abhilash1(a)gmail.com>) escribió: > When you set DEBUG=False, Django doesn't serve static files because of > which you see only text and no styles. > > > http://docs.mailman3.org/en/latest/pre-installation-guide.html#django-stati… > > If you do set DEBUG=False, you need to serve the static pages somehow. > > Alternatively in you case, you can remove the part of the `settings.py` > which changes the Emailbackend when `DEBUG=False` so that you don't have > to worry about serving static files and still send out emails. > > On Wed, Aug 2, 2017, at 09:46 AM, Rafael Mora wrote: > > For testing purpose I turned back to false the DEBUG var and everything > > started working fine with HyperKitty > > > > I don't understand... this is the trace when I click Login from Postorius > > to HyperKitty > > > > [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 > > [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ > > HTTP/1.1" 200 10950 > > [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css > > HTTP/1.1" 200 156657 > > > > > > What should I check? > > > > > > > > > > > > > > > > > > El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) > > escribió: > > > > > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > > > HyperKitty is looking for some files in /static/CACHE/... but it > doesn't > > > > find them: > > > > > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css > HTTP/1.1" > > > > 404 107 > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js > HTTP/1.1" > > > 404 > > > > 105 > > > > > > > > > > > > Should I run any command to activate the CACHE dir? > > > > > > > > > You need to ensure you have a working sass compiler. As I said at > > > < > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > >, > > > See the third bullet under > > > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > > > > > Then you need to run commands like > > > > > > django-admin collectstatic --clear > > > django-admin compress > > > > > > > > > -- > > > 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 > > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > > > -- > > > > Atentamente / Best Regards > > > > Ing. Rafael Mora > > _______________________________________________ > > Mailman-users mailing list > > mailman-users(a)mailman3.org > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > > -- > thanks, > Abhilash Raj > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

Re: [Mailman-Developers] Mailman 3.1 beta coming soon

by Terri Oda

On 2016-12-03 12:22 PM, Florian Fuchs wrote: > I did some manual integration testing today > (core+mailmanclient+postorius) which looked fine so far. I didn't get > to test HyperKitty and the bundler though, so any help testing those > would be very much appreciated. I will have some more time tomorrow. I tried to do some testing based on these wiki instructions last weekend https://wiki.list.org/HyperKitty/DevelopmentSetupGuide and hit a "[Errno 61] Connection refused" issue when attempting to log in to Postorius. I suspect it might be an issue with the mac, since googling for the error (it's a django one) seems to find a lot of people on macs with problems, but I didn't manage to narrow it down more than that to make a useful bug report. I did set up a new linux install on another machine to work on next, though, so I may have something else to say on that front tomorrow. Terri

9 years

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

4 years, 10 months

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, 3 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, 9 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, 5 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, 1 month

Mailman-users search results for query "Postorius"