Search results for "Postorius" - Mailman-users

Re: Postorius permissions granularity

by Liam Reilly

The issue is we don't want first line support staff to have superuser permissions, just the ability to assist end user list owners by being able to administer all lists. So something that is lower level than full superuser would be ideal. I'm considering a cron job that adds a web account as Owner to all lists but this feels like a bit of a bodge.

1 month

Re: More Mailman releases!

by Jered Floyd

Everything looks good to me in my multi-site install! I've updated my simple container install to pin the new versions: https://github.com/jeredfloyd/mailman-container --Jered ----- On Oct 22, 2023, at 2:10 AM, Abhilash Raj maxking(a)asynchronous.in wrote: > Hello, > > I missed one important merge request in django-mailman3, so here are a > couple more versions. > > I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which > requires django-mailman >= 1.3.11). > > Gitlab releases are available here: > > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 > > I have also yanked mailman-web 0.0.7 since that'll cause spurious errors > due to change in session serializer. > > Abhilash > > > On 10/22/23 00:05, Abhilash Raj wrote: >> Hello Everyone, >> >> I am pleased to announce several new releases for GNU Mailman project. >> Thanks to all the contributors for making these releases possible! >> >> 1. Postorius 1.3.10 [1] >> 2. Hyperkitty 1.3.8 [2] >> 3. Django-mailman3 1.3.10 [3] >> 4. Mailman-web 0.0.7 [4] >> >> All the releases are published to PyPI and you can find links to all the >> PyPI projects: >> >> https://docs.mailman3.org/en/latest/ >> >> A full list of change logs are available below: >> >> [1]: >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-10 >> [2]: >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 >> [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst >> [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst >> >> Do note that for Postorius, I released 1.3.9, but I forgot to update >> dependency metadata to require `django-mailman3>=1.3.10` (which is >> required for the new bootstrap 5 upgrade across packages) and so I also >> released Postorius 1.3.10 just after. >> >> Installation documentation is available at >> >> https://docs.mailman3.org/en/latest/install/install.html >> >> and if you are upgrading an existing virtualenv install you can refer >> >> https://docs.mailman3.org/en/latest/upgrade-3.2.html >> >> If you find any issues, you can report them at the respective bug >> tracker for the projects. The links to issue trackers are available >> at https://docs.mailman3.org/en/latest/. >> >> Finally, similar to Mailman Core, note that PyPI doesn't accept >> signatures anymore so each packages' release page now has the tarball >> uploaded to them along with the signature: >> >> Django-mailman3: >> https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 >> Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 >> Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 >> Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 >> > > -- > thanks, > Abhilash Raj (maxking) > > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to jered(a)convivian.com

2 years, 2 months

Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Wikinaut

Hmmm, regarding POSTORIUS_TEMPLATE_BASE_URL , just as a remark, 'http://localhost/mailman3/', this was the installed default value. Regarding the django issue: I do not remember to have triggered an update or so when suddently the error popped up, I did the pip install -U after that. Do you have a recommendation for me, a hint, how to fix the problem without losing the database and settings of my mailing lists? It is so strange to see the error just right now (while only concentrating on the "template problem"); mailman3 worked for a long time.

2 years, 3 months

Re: MM3 on debian - redirect problem

by Gelpi Andrea

Il 28/04/20 18:31, Mark Sapiro ha scritto: > On 4/27/20 8:17 AM, Gelpi Andrea wrote: >> Hi, >> on a debian10 I have mm3 installed via apt-get >> >> apt-get install mailman3-full >> dpkg-reconfigure mailman3 >> dpkg-reconfigure mailman3-web >> >> I have this minor issue >> >> https://webserver/mailman3 redirects to >> http://webserver/mailman/postorius/lists/ >> >> that doesn't exist. >> >> The same problem form django admin page to return to lists >> >> https://website/mailman3/admin/sites/site >> >> In the upper right corner I have a link to https://webserver/mailman3 >> that redirects to https://mailman/postorius/lists/ >> >> I searched for a redirect but without success. > > > The redirection must be a web server issue. > > There is a urls.py file probably in the same directory as your django > settings - probably /usr/share/mailman3-web/urls.py in your case. > > You can make a URL like http://webserver/mailman/postorius/lists/ work > by adding > > url(r'^mailman/postorius/', include('postorius.urls')), > > to the urlpatterns list in the urls.py file. > > The problem seems to be inside the uwsgi proxy. Also django admin web interface has the some problem. I add /mailman in the apache mailman config installed by the debian package. --------------------------------------- Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> ------------------------------------- -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 8 months

Re: cc'd e-mail addresses rewritten with @invalid.domain

by pwilliam＠fredhutch.org

Hi Mailman Users, I've done some more testing with this issue and have determined that this seems to be an issue with how commas within the display name in cc'd messages are being processed with messages sent from the Outlook client. Here are some test scenarios. Note I set the mailing list I was testing with to hold messages in moderation. Once the message was held I copied the information from the headers directly from Postorius held message information into the space below: Test Scenario 1: Display name in Outlook: Williamss, Peterr C Outcome: Does not work as intended. The CC address is formatted as Williamss(a)invalid.domain in messages received by mailing list members, oddly the "Peterr C" part of the display name is not present anywhere in the CC addresses received by mailing list members. Header information from held message in Postorius CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williamss, Peterr C" <peterbw(a)test.com> Test Scenario 2: Display name in Outlook: Williams, Peter D Outcome: Does not work as intended. Interestingly, the CC address in the message received by mailing list members is formatted as two separate addresses in this case: Williams(a)invalid.domain and Peter(a)invalid.domain. "D" is not present anywhere. Could this issue be related to the number of characters? Header information from held message in Postorius: CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, "Williams, Peter B" <peterbw(a)test.com> Test Scenario 3: Display name in Outlook: Williamss Peterr C Outcome: Works properly. The CC address contains the correct address and display name information. The information in messages received from the mailing list contain the address formatted correctly as: "Williamss Peterr C peterbw(a)test.com" Header information from held message in Postorius: CC: "os-x-lion(a)lists.test.org" <os-x-lion(a)lists.test.org>, Williamss Peterr C <peterbw(a)test.com>

5 years, 3 months

Mailman, etc. upgrade woes and persistent bugs

by hansen＠rc.org

I just had my Mailman suite upgraded. When it got started, I starting receiving messages that hundreds of subscribers to the lists had been disables, including several of the list moderators. This version started supporting bounce processing, but how in the world was this upgrade allowed to act on bounces that were being collected PRIOR to enabling bounce processing?? I got many angry emails, messages and phone calls asking what was going on, as they were bona fide list members. I was very surprised myself. I then looked at several of the disabled accounts, but the subscription info page in Postorius had no information about whether an account was enabled or disabled. Why is this not displayed???. The members can't see if their account is enabled. Is this another example of the disconnect between Mailman and Postorius? Further, even after the upgrade, the moderators still cannot access the list memberships even though all the lists are set to allow that. I would have asked the moderators to do this if this access bug had been fixed, but they can't get there. As a result of these bugs, after consulting with Brian, who helped with the upgrade, I spent many hours re-enabling the several hundred accounts that had been disabled. I had to go through each email notification to find the address of a disabled account, then find the list, then the member, in Postorius, and finally enable the account (at which time Postorius DID show the enabled status). Please, can the next upgrade include these very basic fixes/enhancements, which I requested a long time ago: a. The ability of moderators to see the list membership (a bug). b. The ability of members to change their addresses for all lists they are subscribed to. and further, now: c. That when members go to look at their subscription info, they can actually see the settings. Thank you, Allan

4 years, 11 months

Re: Struggle on upgrading mailman3-web to new version - Not Found: /mailman//

by Stefan Bauer

Hi Eggert, thank you for your input. Unfortunately that did not work. After changing the line ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ to ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ and restarted apache2, still a similar behavior when accessing https://my.mailinglistserver.local/mailman/postorius/lists/ Page not found (404) Request Method: GET Request URL: https://mmy.mailinglistserver.local/mailma//postorius/lists/ What i find strange is that the URL is mangled. The 'n' from mailman is missing and now there is a second slash. This all must happen inside the uwsgi-container as my request is modified. Not Found: /mailma// [pid: 1346851|app: 0|req: 28/28] 10.254.253.13 () {52 vars in 827 bytes} [Mon Oct 25 17:47:21 2021] HEAD /mailman/ => generated 2773 bytes in 4 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on core 1) Am Mo., 25. Okt. 2021 um 17:19 Uhr schrieb Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org>: > Hello Stefan, > > I had the same problem. While I did not find the reason for this strange > behavior, I found a workaround. I changed the lines in the apache vhost > file > like this: > > <IfModule mod_proxy_uwsgi.c> > ProxyPass /mailman3/favicon.ico ! > ProxyPass /mailman3/static ! > ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > </IfModule> > > Note I only changed the single ProxyPass line from mailman3 to mailman. > The > url to access the web gui also changes like this: > > https://my.mailinglistserver.local/mailman/postorius/lists/ > > This works for me, tell us your success. Would be nice when the problem > could > be solved finally, this happened to a few people. > > Cheers, Eggert > > Am Montag, 25. Oktober 2021, 10:45:50 CEST schrieb Stefan Bauer: > > Dear Users, > > > > I recently upraded mailman3 from Ubuntu 18 to 20. After accessing the > > web-interface via > > > > https://my.mailinglistserver.local/mailman3/postorius/lists/ > > > > I receive > > > > Not Found: /mailman//postorius/lists/ > > [pid: 1346851|app: 0|req: 4/4] 10.254.253.12 () {70 vars in 1369 bytes} > > [Mon Oct 25 10:39:59 2021] GET /mailman3/postorius/lists/ => generated > 2821 > > bytes in 12 msecs (HTTP/1.1 404) 5 headers in 155 bytes (1 switches on > core > > 1) > > > > Where does the wrong path come from (mailman vs. mailman3) > > > > After enabling Debug, i see in the browser the following: > > > > > > Page not found (404) > > Request Method: GET > > Request URL: > https://my.mailinglistserver.local/mailman//postorius/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, /postorius/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. > > > > My apache configuration is very simply: > > > > # more /etc/apache2/conf-enabled/mailman3.conf > > Alias /mailman3/favicon.ico > > /var/lib/mailman3/web/static/postorius/img/favicon.ico > > Alias /mailman3/static /var/lib/mailman3/web/static > > > > <Directory "/var/lib/mailman3/web/static"> > > Require all granted > > </Directory> > > > > <IfModule mod_proxy_uwsgi.c> > > ProxyPass /mailman3/favicon.ico ! > > ProxyPass /mailman3/static ! > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ > > </IfModule> > > > > I dont see where the path gets traversed in the wrong way. Any help is > > greatly appreciated. > > > > thank you. > > > > Stefan > > _______________________________________________ > > 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/ > > > > > _______________________________________________ > 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/ >

4 years, 2 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 1/18/24 05:36, samuel.d.darwin(a)gmail.com wrote: > > However our latest plan as of this moment is to revert back to a one-server implementation. mailman-core and mailman-web will be on the same machine. Thus, the enhancement is not critical. It still seems "theoretically" useful to implement the fix, unless the documentation states "it is recommended that core and web should be on the same machine" or similar. See the fourth paragraph at https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Core, Hyperkitty and Postorius releases

by Mark Sapiro

On 5/14/21 5:02 AM, Odhiambo Washington wrote: > On Fri, May 14, 2021 at 2:52 PM Jeff Steele <jeff(a)steele.com> wrote: > >> >> >> On May 14, 2021, at 7:49 AM, Odhiambo Washington <odhiambo(a)gmail.com> >> wrote: >> >> /bin/sh: sass: Permission denied* >> >> >> >> Did you check the permissions on your sass binary? >> > > My mailman installed in /opt/mailman/mm > > find /opt/mailman/ -type f -name sass > > yielded nothing! Try `which sass` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 7 months

Re: django-mailman3 update causing errors

by Darren Smith

So we have pulled all fresh versions of these projects from gitlab as of last Friday: postorius hyperkitty django-mailman3 mailmanclient Django is version 1.11 When we installed, each of these were placed in a conda virtual environment. Postorius, Hyperkitty, and django-mailman3 are all still under a python 2.7 environment. Is that our problem here? Do they need to be in python 3 now? -Darren On Tue, May 1, 2018 at 3:47 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 05/01/2018 01:35 PM, Darren Smith wrote: > > Hello, > > > > In attempting to update our mailman3/postorius/hyperkitty installation, I > > have run into an error after upgrading the django-mailman3 project. > ... > > Any thoughts on why updating django-mailman3 would cause this? > > > To what version did you update? any 1.2 version is part of the migration > of Postorius/HyperKitty to Python 3 and requires > > postorius>=1.2.0b1 > hyperkitty>=1.2.0a1 > Django>=1.11 > django-mailman3>=1.2.0a2 > mailmanclient>=3.2.0b1 > > and is all Python 3 > > > -- > 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/ >

7 years, 8 months

Mailman-users search results for query "Postorius"