Search results for "Postorius" - Mailman-users

Re: combine postorius and hyperkitty into one Apache vhost

by Mark Sapiro

On 12/29/22 05:51, Wolfgang Rosenauer wrote: > Hi, > > I'm in the process to set up a new mailman3 site. > (Migrating from mailman2) > > There are RPMs for my distribution which integrate postorius and > hyperkitty with uwsgi. I think you'll be much happier if you don't use the distro's RPMs which are probably out of date and instead follow <https://docs.mailman3.org/en/latest/install/virtualenv.html>. Those instructions use uWSGI as a WSGI interface, but Gunicorn <https://gunicorn.org/> is what is used on the site supporting this list. The advantages of Gunicorn are it's already installed as a dependency of Mailman core, and it's what the Mailman developers are more familiar with. I'll work on updating <https://docs.mailman3.org/en/latest/install/virtualenv.html> to include Gunicorn as an alternative. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: Internal Server Error, Need 2 values to unpack in for loop; got 1

by Mark Sapiro

On 7/11/24 11:06 AM, Elias Rudberg wrote: > Hello! > > I am using mailman3 (version 3.3.8) and it mostly works fine, but > sometimes (usually several times every day) the error below appears. > > Any suggestions for what could be done about this? ... > Here is what the error message looks like: > ------------------------------------------- > > [Django] ERROR (EXTERNAL IP): Internal Server Error: > /mailman3/postorius/lists/ > > Internal Server Error: /mailman3/postorius/lists/ > > ValueError at /postorius/lists/ > Need 2 values to unpack in for loop; got 1. Can you get the page at /mailman3/postorius/lists/ and /mailman3/postorius/lists/?all-lists If those are OK, look in your web server access logs for `GET /mailman3/postorius/lists/` messages with the same timestamp as those errors. Is there some bogus query fragment on those? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Managing users in postorius

by Lieuallen, Thomas Otis

In our environment, people have multiple email addresses, any/all of which might be used as members or admin addresses. I try to steer people in the right direction, but inevitably, we end up with people registering the ‘wrong’ address or even both addresses. I don’t seem to have very much control with the site admin account. I’d like the ability to add a secondary address for a user instead of talking them through the process of doing it themselves. Is there a way that I’m not aware of? Additionally, when I look up users and choose ‘manage’, it only lists a person’s member roles. It doesn’t list any other roles (owner/admin, moderator, etc). Any way to fix that? I’m also curious what the process would be for merging two postorius accounts into one? My thought process was that I should remove one and then have the user add that email address to the other account. But, if you delete the account, it will unsubscribe the user. Thank you Tom Lieuallen Oregon State University

10 months

Re: So, why are css & js files only served with "DEBUG = yes" ?

by Odin Hørthe Omdal

> js and css files are static and should be served by your web server of choice. Actually, Python is able to do this very nicely and quickly these days. I've started using WhiteNoise (added as a django staticfiles provider) which does all the right things for you directly (uses sendfile, sets cache headers, does compression correct, all real work done at initialization time, if you best speed just add CDN, etc etc). It might be something to make MM3 setup a bit nicer and quicker (note, I still haven't migrated to MM3 so don't know much about it); http://whitenoise.evans.io/ A point against it is an extra dependency ofc. Odin 2017-05-07 15:12 GMT+01:00 Simon HANNA <simon.hanna(a)serve-me.info>: > js and css files are static and should be served by your web server of > choice. In a development environment you usually don't have a web server > running, so django serves the files itself. > > Your webserver can serve these static files much faster than django can, > so django doesn't serve them in production by default. You can find > instructions on how to do so online (Google is your friend) but since > that's not incouraged there is no point in including these in the repos. > > Simon > > Am 7. Mai 2017 16:06:17 MESZ schrieb Simon Liebold via Mailman-users < > mailman-users(a)mailman3.org>: > >Hello List, > > > >I did see this discussed in #180 > ><https://gitlab.com/mailman/postorius/issues/180>, but I didn't quite > >understand if this is an issue or not. > > > >Why is it that I can run the development server just fine. > > > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/postorius/css/style.css > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/django-mailman3/js/main.js > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/django-mailman3/css/main.css > > HTTP/1.1" 304 0 > > [07/May/2017 13:23:47] "GET /static/postorius/js/script.js HTTP/1.1" > > 304 0 > > [07/May/2017 13:23:47] "GET > > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 304 0 > > > >And as soon as I comment out > > > > # SECURITY WARNING: don't run with debug turned on in production! > > # DEBUG = True > > > >in mailman-suite/mailman-suite_project/settings.py and restart it 404s > >on me. > > > > [07/May/2017 13:41:36] "GET > >/static/postorius/libs/bootstrap/css/bootstrap.min.css HTTP/1.1" 404 > >127 > > [07/May/2017 13:41:36] "GET /static/django-mailman3/css/main.css > > HTTP/1.1" 404 109 > > [07/May/2017 13:41:36] "GET /static/postorius/css/style.css > > HTTP/1.1" 404 104 > > [07/May/2017 13:41:36] "GET /static/django-mailman3/js/main.js > > HTTP/1.1" 404 107 > > [07/May/2017 13:41:36] "GET > > /static/postorius/libs/bootstrap/js/bootstrap.min.js HTTP/1.1" 404 125 > > [07/May/2017 13:41:36] "GET > > /static/postorius/libs/jquery/jquery-1.11.3.min.js HTTP/1.1" 404 123 > > [07/May/2017 13:41:36] "GET /static/postorius/js/script.js HTTP/1.1" > > 404 103 > > [07/May/2017 13:41:36] "GET > > /static/postorius/img/mailman_logo_small_trans.png HTTP/1.1" 404 123 > > > > > >So the choice is insecure vs. ugly? Neither of those sounds very > >tempting. > > > >I guess, I am missing something, or no? > > > >Simon > > > >_______________________________________________ > >Mailman-users mailing list > >mailman-users(a)mailman3.org > >https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Beste helsing, Odin Hørthe Omdal <odin.omdal(a)gmail.com> English, technical: http://tech.velmont.net Norsk, personleg: http://velmont.no

8 years, 2 months

Re: Customising hyperkitty and postorius

by Mark Sapiro

On 11/18/20 5:16 PM, peter(a)chubb.wattle.id.au wrote: > > Hi, > I've put up a mailman3 instance, with hyperkitty enabled, and > imported all my mailman2.1 archives -- it all seems to be > working. > > How do I now customise the look and feel of my site? > > In particular, I'd like to render archived emails with a > monospace font, and I'd like to change the colour scheme and > styles of all the pages to match other pages on the same website. HyperKitty will display a message in monospace if you click the 'A' icon at the bottom of the message. I don't know offhand how you would make that the default. For styles, they are mostly SCSS in the directory hyperkitty/static and CSS in the directory postorius/static/postorius. I think you'd have to find the relevant styles and edit them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Re: [Django] ERROR (EXTERNAL IP): Internal Server Error:

by Wolfgang Bock

Hello Mark, thanks for your reply. I'll check it out and report. Reagrds Wolfgang Am 18.11.2019 um 18:57 schrieb Mark Sapiro: > On 11/18/19 9:26 AM, Wolfgang Bock via Mailman-users wrote: >> Hello, >> >> I got an errormessage via mail to root@[domain-01]. >> >> The complete text is attached in a utf-8-text-file. >> >> In the lines ...6, 8, 12, 119, 138, 141, 149, 150, 151, 155, 161, 162, >> 165, 166, 169, 187, 247, 251, 321 ....you can find links to different >> domains anonymised as [domain-01], [domain-02], [domain-03], [domain-04]. > > You attempted to delete testliste02.[domain-01] via Postorius and > Mailman's REST API returned a 500 status. You may find more information > in mailman.log. > > I'm only guessing, but possibly this is because you posted to the URL > <https://[domain-02]/mailman3/postorius/lists/testliste02.[domain-01]/delete>. > I.e., you were accessing Postorius at > https://[domain-02]/mailman3/postorius/ (domain-02) and deleting a > domain-01 list. >

5 years, 8 months

Re: Postorius 1.2.3 and MailmanClient 3.2.1 is now out

by Jonas Meurer

Jonas Meurer: > Abhilash Raj: >> On Mon, Jan 28, 2019, at 2:39 PM, Jonas Meurer wrote: >>> Abhilash Raj: >>>> On Sat, Jan 26, 2019, at 5:10 AM, Jonas Meurer wrote: >>>>> Hey Abhilash, >>>>> >>>>> Thanks a lot for your work on mailman3! >>>>> >>>>> Abhilash Raj: >>>>>> I am very pleased to announce (a bit late) that Postorius 1.2.3 and MailmanClient 3.2.1 is now out. >>>>>> >>>>>> The full set of changelog can be found in the documentation[1][2]. The most notable feature that >>>>>> I can think of is non-member management in Postorius. >>>>>> >>>>>> New releases are available on PyPI[3][4]. >>>>> >>>>> For earlier releases, you provided GnuPG signature files to >>>>> cryptographically verify that the release files were not tampered with. >>>>> >>>>> I couldn't find such signature files for the two latest releases. Would >>>>> you mind adding them? When packaging for Debian, I prefer to check the >>>>> GnuPG signatures before uploading new releases. Also, the signature >>>>> files get uploaded to the Debian archive as well so they can be checked >>>>> by everybody. That way we can cryptographically proof that the Debian >>>>> package is based on the original tarball that got packaged and signed by >>>>> upstream. >>>> >>>> >>>> Ah, sorry about that. I completely forgot about that. >>>> >>>> I am not sure if I can upload signatures after uploading the tarballs, I'll try to find out if that is possible. >>> >>> Thanks a lot, that would be awesome. I'll wait for it before doing the >>> Debian package uploads. >> >> If it is not possible to upload signatures, I'll bump up patch versions >> and push out new tarballs with signatures. > > Perfect, thanks a lot! For the record: Abhilash released mailmanclient 3.2.2 and postorius 1.2.4 with tarball signatures in the meantime. Thanks a lot for doing this, Abhilash! Both are uploaded to Debian already. Cheers jonas

6 years, 5 months

Re: mm3 installation question

by Mark Sapiro

On 3/5/24 1:52 PM, advorkin(a)cs.princeton.edu wrote: > > I went with the apache/uswgi configuration. The site is up and running, but if I click Postorius, it gets redirected to https://mysite.com/postorius/lists and I get not found error message. > > The same goes for Lists and Archives. Compare your urls.py to <https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py?re…>. Some of the `path` settings are probably not in the same order as in that file. The ``` path('mailman3/', include('postorius.urls')), path('archives/', include('hyperkitty.urls')), ``` settings should come after the ``` path('postorius/', include('postorius.urls')), path('hyperkitty/', include('hyperkitty.urls')), ``` settings (unfortunately, mailman-web 0.0.8 has these in the wrong order). Or you can just delete the 'postorius/' and 'hyperkitty/' ones or you can add ``` ProxyPass "/postorius" "http://127.0.0.1:8000/postorius" ProxyPass "/hyperkitty" "http://127.0.0.1:8000/hyperkitty" ``` to your Apache config. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Odhiambo Washington

On Mon, Mar 31, 2025 at 9:32 PM Philip Bondi <pjbondi(a)systemdatabase.com> wrote: > Thank you, Mark, and the whole community for your help, so far. Gosh, it > feels so close. > > It works from browser on Debian virtual machine: > > But still fails through Apache: > > root@shackleton12:~# *cat /etc/mailman3/urls.py* > # > > **************************************************************************** > # > # $Id: urls.py 165750 2025-03-31 18:19:32Z svn_beechwood $ > # $URL: > > https://systemdatabase.com/svn/svn-sdi/sdi-sysadmin/trunk/SHACKLETON12-root… > $ > # $Date: 2025-03-31 14:19:32 -0400 (Mon, 31 Mar 2025) $ > # > # Description: > https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > # > # > > **************************************************************************** > # -*- coding: utf-8 -*- > # Copyright (C) 2023 by the Free Software Foundation, Inc. > # > # This file is part of mailman-web. > # > # Postorius is free software: you can redistribute it and/or modify it > under > # the terms of the GNU General Public License as published by the Free > # Software Foundation, either version 3 of the License, or (at your option) > # any later version. > # > # Postorius is distributed in the hope that it will be useful, but WITHOUT > # ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or > # FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for > # more details. > # > # You should have received a copy of the GNU General Public License > along with > # Postorius. If not, see <http://www.gnu.org/licenses/>. > > > from django.conf.urls import include > from django.contrib import admin > from django.urls import path, reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > path( > '', > RedirectView.as_view(url=reverse_lazy('list_index'), > permanent=True), > ), > # Include alternate Postorius and HyperKitty URLs. > path('postorius/', include('postorius.urls')), > path('hyperkitty/', include('hyperkitty.urls')), > # Order counts for various links. Put the above first and the > following > # after so the suggested Apache config still works. > *path('mailman3/', include('postorius.urls')),* > path('archives/', include('hyperkitty.urls')), > path('', include('django_mailman3.urls')), > path('accounts/', include('allauth.urls')), > path('admin/', admin.site.urls), > ] > > When I hit https://systemdatabase.ca/mailman3, I see the following in > /var/log/apache2/systemdatabase.ca_error.log > > [Mon Mar 31 13:48:21.074890 2025] [proxy:error] [pid 3075263:tid > 3075272] (2)No such file or directory: AH02454: uwsgi: attempt to > connect to Unix domain socket */run/mailman3-web/uwsgi.sock* ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ uwsgi running outside virtualenv?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

3 months, 3 weeks

Re: mailman.cfg (use_https: yes) fails

by Wolfgang Bock

Hi again, in this case I'll check out either and report. Regards Wolfgang Am 18.11.2019 um 05:06 schrieb Mark Sapiro: > On 11/16/19 4:54 AM, Wolfgang Bock via Mailman-users wrote: > I will look at the https issue further when I get time. > > >> In this context I faced a strange behavior: >> >> In the database mailman3web in table django_site are listed several >> domains, either in the django-domain-management site >> https://[mydomain]/mailman3/admin/sites/site/ >> >> id domain name >> 1 example.com Example.com >> 2 [mydomain-1] [mydomain_name_1] >> 3 [mydomain-2] [mydomain_name_2] >> 4 [mydomain-3] [mydomain_name_3] >> >> In case I delete line 1 with the id 1, in the database or in the >> django-web-site, postorius fails to work. After re-inserting this line, >> postorius works again. > > In your settings.py, you probably have SITE_ID = 1. Thus, when you > delete the site with id = 1, Postorius fails. You need to set SITE_ID to > an existing site in settings_local.py. >

5 years, 8 months

Mailman-users search results for query "Postorius"