Search results for "Postorius" - Mailman-users

Re: Delete User

by Mark Sapiro

On 05/25/2018 02:41 PM, Kaleb White wrote: > Is it possible to delete a user from postorius completely so that they cannot log in again? Users and their email addresses appear in multiple places. A user can be a member, owner and/or moderator of one or more email lists. These roles are all maintained in Mailman core, but can be accessed and deleted via Postorius. A user's actual login for Postorius and HyperKitty is maintaind in Django and a user can be deleted via the Django admin interface. That would prevent the user from logging in, but I don't think anything prevents the user from re-registering with the same email address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years

Re: postorius ssl-certificates for virtual hosts

by Mark Sapiro

On 11/14/19 3:05 PM, Wolfgang Bock via Mailman-users wrote: > > Hello, > > On my server are several virtual hosts running with different lists per > host. The appropriate webaddress is in general: > https://lists.[domain]/mailman3/postorius/lists/[listname].lists.[domain]. > My domains: > [domain-1] starts with a b* > [domain-2] starts with a s* > [domain-3] starts with a t* > > If I use the webadress > https://lists.[domain-1]/mailman3/postorius/lists/[listname].lists.[domain-… > and I do a click on the https-symbol in the address line of my browser I > get the secury-information " every thing is ok" and the > certificate-information is about the wildcard-certificate I just created > for the right domain. > > Different result is for the webadress > https://lists.[domain-2]/mailman3/postorius/lists/[listname].lists.[domain-…. > In this case I get an information like "you are using a wrong > certificate" clicking on the https-symbol references tot he certificate > of [domain-1] > > I set in my apache2 configuration a symbolic link to apache.conf in the > /etc/mailman3/directory and made this active. > > What did I wrong?? Your Apache config needs to define separate a VirtualHost for each domain, either by IP address or ServerName, and each VirtualHost points to its own SSL certificates. > If I set use_https to yes in mailman.cfg I get on the website for all > lists: > > postorius: Something went wrong > Mailman REST API not available. Please start Mailman core. > > In the logs I found … ... > mailman-web.log > ERROR 2019-11-14 22:20:41,471 1405 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File > "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", > line 95, in call > response, content = Http().request(url, method, data_str, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, > in request > (response, content) = self._request(conn, authority, uri, > request_uri, method, body, headers, redirections, cachekey) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, > in _request > (response, content) = self._conn_request(conn, request_uri, method, > body, headers) > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, > in _conn_request > conn.connect() > File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1012, > in connect > self.sock = self._context.wrap_socket(sock, server_hostname=self.host) > File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket > session=session > File "/usr/lib/python3.7/ssl.py", line 853, in _create > self.do_handshake() > File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake > self._sslobj.do_handshake() > ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number > (_ssl.c:1056) Does your setting in settings(_local).py for MAILMAN_REST_API_URL have an https scheme? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: hello， Discussion on how to subscribe to themailing list

by 朱超

thank you for your reply 1. It is not the MTA that refuses to send emails because the recipient's mailbox is too long, but the MUA that refuses to send the email because the recipient's mailbox is too long. Of course, you can use the confirm $token message to dev-request@domain for confirmation. This is a comparison Troublesome process, by visiting https://www.example.com/mailman3/lists/$list_id/confirm/?token=$token, but he reported 404. 2. It is recommended to modify postorius, in order to keep the logic function of the underlying mailman-core unchanged, and optimize postorius at the application layer to increase user experience; even if there is no mailman-web service or postorius service, mailman-core can still run normally. If you look at the separation of the application layer and the underlying software, I think it is possible From: Tom At 2023-01-17 19:44:20, "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: >朱超 writes: > > > Yes, You got it. It is too cumbersome to ask the user to write a > > reply email for email confirmation. > >Surely clicking on "reply" then "send" is not cumbersome (unless >there's a way to get rid of confirmation altogether). Your problem is >that some of your subscribers can't do that. > >I have not previously heard of a MTA that refuses to *send* mail >because the addressee's mailbox is too long. IIRC there's a limit of >256 characters on domains, but only the (long-obsolete) recommendation >that lines in the message be 998 bytes or less restricts the length of >the local-part. > >I don't really see a good reason to change this default because there >are a number of configurations where there is no web service >available. I suggest a partial remediation in the issue I just filed. >(I think dealing with the rest of the issue is a Simple Matter of >Programming, but the question of determining existence and status of >an appropriate web service is more complex so I did address that.) > > > Why do you need to modify the mailman-core service， > >I suggest we should modify the code of the postorius, > >We are not going to do that, because >1. Mailman provides no guarantee that any web service is present, and > we're not going to make changes that require one. >2. Mailman provids no guarantee that the web service is Postorius > even if there is one, and we are definitely not going to make > creating compatible implementations more annoying than necessary. > > > Currently I have achieved it this way。 > >We encourage you to use your code. ;-) But using it exclusively to >accomplish this change would go against several of our goals in term >of separation of concerns. If we can do it in an alternative way that >serves those goals, there's no point in complexifying Postorius in >this way as well. > >Regards, >Steve >_______________________________________________ >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 tom_toworld(a)163.com

2 years, 4 months

Re: MM3 not starting afte an upgrade -addendum

by Mark Sapiro

On 7/27/20 12:38 AM, Gelpi Andrea wrote: > To solve the problem I had to remove VHOST parameter from config file. > I remember that Vhost was mandatory for my configuration when I set it > up two month ago. > So I don't understand why now I had to remove it to have MM3 working. Are you talking about FILTER_VHOST in your Django settings(_local).py or something else. If something else, I don't know what. If FILTER_VHOST, It has nothing to do with Mailman core. There is this issue with Postorius <https://gitlab.com/mailman/postorius/-/issues/394> which is fixed in Postorius 1.3.3. -- 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

Re: Postorius no connection to REST API

by Richard Rosner

postorius, admin, hyperkitty and user-profile work now, accounts doesn't WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts WARNING 2021-08-21 10:52:41,931 3975 django.request Not Found: /accounts [pid: 3975|app: 0|req: 26/26] 127.0.0.1 () {56 vars in 1208 bytes} [Sat Aug 21 10:52:41 2021] GET /accounts => generated 5651 bytes in 433 msecs (H\ TTP/1.1 404) 5 headers in 170 bytes (1 switches on core 0) pid 3975 is /usr/bin/uwsgi --plugin python3 --ini /etc/mailman3/uwsgi.ini PS: now I seem to have done something stupid. I wanted to switch everything from example.com to the real domain. So I added it in admin and got rid of example.com. Seems there was some configuration missing, now nothing is working. How do I get everything back and have it use the right domain?

3 years, 9 months

Postorius, Hyperkitty new release candidates

by Abhilash Raj

Hi Everyone, I am pleased to announce a couple of more releases: - Postorius: 1.3.3rc1 Changelog: https://docs.mailman3.org/projects/postorius/en/latest/news.html#rc1 Download: https://pypi.org/project/postorius/1.3.3rc1/ - Hyperkitty: 1.3.3rc1 Changelog: https://hyperkitty.readthedocs.io/en/latest/news.html#rc1 Download: https://pypi.org/project/HyperKitty/1.3.3rc1/ - Mailmanclient: 3.3.1rc1 Changelog: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… Download: https://pypi.org/project/mailmanclient/3.3.1rc1/ - Django-mailman3: 1.3.3rc1 Changelog: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst Download: https://pypi.org/project/django-mailman3/1.3.3rc1/ Python 3.6+ and Django 2.0+ is supported for all of them. Django 3.0 support for Hyperkitty requires manually upgrading a dependency (django-haystack>=3.0b2, once a stable version of this has been released, it shouldn't require manually upgrading). There are tons of bug-fixes across the board and some new features. Biggest visible change is switch to Bootstrap 4, which has been long pending for us. Bootstrap 4 completely changes the CSS grid model using the new Flexbox. There might be some small changes or breakages when using on mobile. Please report such issues to us via Gitlab! Some other notable changes are in Postorius, which includes many more list settings exposed include content filtering settings, bounce processing (which was added in the previous release of Mailman Core) settings and some other ones. You can now also specify a reason when rejecting held messages. There was also a gnarly bug, which caused the name of some members to be the string "None". For the longest time, I couldn't figure out the reason for it, but it ended up being a simple fix in mailmanclient's json serialization of display_name, which would result in Python's None value being passed as string "None" to Mailman's API for subscription. There is also better support for filtering visible lists based on the current vhost, which I see a few people are already waiting for from mailman-users list. A full changelog has been added to each project in the top. These are still pre-releases and if you are installing via pip, you would need the `--pre` flag, for e.g. $ pip install --pre --upgrade postorius hyperkitty As with all other releases, these have also been running on mail.python.org and lists.mailman3.org for some time now, so it should be relatively safe to upgrade to. Stable releases for this is now scheduled in 1 week, hopefully, next weekend. -- thanks, Abhilash Raj (maxking)

5 years

Re: Broken web interface Ubuntu 20.04

by Simon Brown

On Thursday, 30 September 2021 11:43:00 CEST Simon Brown wrote: > Whilst I wasn't looking something has broken the web interface to mailman on > our list server. On the list index page I get the Postorius header, but no > list index, instead a Page not found error. Curiously the Postorius header > is also broken, the links point to > https://host/mailman/(postorius/lists|hyperkitty) not > https://host/mailman3/(postorius/lists|hyperkitty) like it should > > I've poked around and I can't find any useful errors and I don't know > exactly when this happened, but I think it was this week. Mailman itself is > running happily underneath. I've managed to get things working again with help from a colleague familiar with Django. The bug seems to be in the Debian/Ubuntu packaging. In the apache.conf file there is the line: ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ and the problem was caused by the final trailing slash. Changing it to ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost fixed the problem. I presume something has changed with Apache in Ubuntu 20.04, as this used to work. I expect others will also hit this problem. Simon -- Simon Brown System Engineer EISCAT Scientific Association P. O. Box 812, SE-981 28 Kiruna, Sweden simon.brown(a)eiscat.se

3 years, 8 months

Re: How to change the language in mailman3

by Mark Sapiro

On 7/17/20 8:22 AM, maszap(a)tin.it wrote: > Hi everyone, > from here: > https://hosted.weblate.org/projects/gnu-mailman/hyperkitty/it/ > I see that there is a way to change the language of mailman3, postorius and hyperkitty > But I don't find how. > I read that you can download the .po files for the chosen language, but I didn't understand how to use these files. > Could anyone show me how to do it? The various message catalogs for Mailman core are in mailman/messages/ and those for hyperkitty, django-mailman3 and postorius are respectively in hyperkitty/locale/, django-mailman3/locale/ and postorius/locale/. The translations from weblate are incorporated in the distribution, but depending on how Mailman is installed, may be out of date. To set language for Django (i.e. hyperkitty and postorius) see <https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-d…>. For Mailman core, set `[mailman] default_language:` in mailman.cfg. You also need to (re)generate the .mo file which can be done with the generate_mo.sh script. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/inter…> For Django, you need to generate .mo files with `django_admin compilemessages` -- 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

Re: Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by Mark Sapiro

On 5/3/21 3:27 PM, summersan(a)nclack.k12.or.us wrote: > Hi Mark, > > Thank you for your quick response! > > When setting up Mailman 3, I went through much of this "how to" guide here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10. Which uses gunicorn as the wsgi server for Django. > As far as I can tell, my current setup appears to be proxying from Nginx to Gunicorn, according to the related Nginx and mailman3-project-specific Gunicorn config files. Specifically, I checked the local address:port being used in the Nginx file and compared that to the mailman3-project-specific Gunicorn bind address. It looks like I might have "separated out" the REST API to a different server block in the Nginx config file, so I think I'm looking at the correct server block with this conclusion. Nginx has nothing to do with the REST API. The REST API is accessed by Postorius and HyperKitty via mailmanclient and django-mailmane which are installed by pip as dependencies of Postorius and Hyperkitty. > For what it's worth, I don't recall this type of "slow first visit startup" issue happening in the past when using web applications with uwsgi, and I've had the opportunity to use uwsgi with a variety of programs. I think Gunicorn is fairly new to me. I do, however, remember that something like this might have happened in the past when using Passenger (https://www.phusionpassenger.com/) a long time ago, but that might have been setting related on my part. > > Okay, thanks for the encouragement about the potential solution to periodically accessing the related "example.mailman.site/mailman3/lists/" type location (from my earlier email). Wanted to check on that and was also hoping that there might be some setting I'm missing in the overall Mailman 3 project setup related to the "slow first visit startup" issue. I'm not aware of anything you missed. I think this has to be a gunicorn issue or possibly related to Django, but I'm not specifically aware of any issues. There might be something you can set in gunicorn, but I don't know what. -- 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: combine postorius and hyperkitty into one Apache vhost

by Eggert Ehmke

So you prefer Gunicorn over uWSGI? When I have a working installation that uses uwsgi, should I reconfigure for Gunicorn? At the moment I see no reason for this, and while I am open for alternate solutions, ... ´ never change a running system Am Donnerstag, 29. Dezember 2022, 21:48:54 CET schrieb 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.

2 years, 5 months

Mailman-users search results for query "Postorius"