Search results for "Postorius" - Mailman-users

Re: hidden list is hidden even to the owner

by Mohsen Masoudfar

As always: Thanks a lot! To answer your question, I am running 1.1.2-3 # apt search postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] Web user interface to access GNU Mailman3 This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, July 1, 2020 5:43 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: hidden list is hidden even to the owner [EXTERNAL EMAIL] On 7/1/20 2:05 PM, Abhilash Raj wrote: > > Which version of Postorius are you running? > > Newer version shows all the lists you are related to by default when you are logged-in. So, the ones you own, moderate, subscribe to. That's correct, but it's tricky. If as an owner of an unadvertised list, you go to a URL like https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… you will see the unadvertised list(s) that you own as well as any that you are a member or moderator of. Likewise you will see the unadvertised list(s) you own at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp… and if you are a member as well as owner of an unadvertised list, you will see it at https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…. But (here's the tricky part) if you go to https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.examp…, you will not see any unadvertised lists, not even ones you own. -- 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…

5 years, 4 months

Timeout in Postorius when trying to approve or reject moderated messages

by Sebastian Hagedorn

Hi, I just set up a new Mailman 3 Suite installation (GNU Mailman 3.3.1 (Tom Sawyer)) on CentOS 7 using the virtualenv installation guide: https://docs.mailman3.org/en/latest/install/virtualenv.html I encountered a few issues, but I was able to resolve all of them, I think. All three components of the suite are up and running. The backend is a MariaDB database, the frontend is Apache with mod_wsgi. I can send messages to the server, and they are delivered to list members. One thing that I can't figure out is why I can't approve or reject messages that are held for moderation. In case it matters, I'm trying to moderate the list using the "root" account. Discarding works, but when I try to either accept or reject a message, there is a timeout. I can't find anything in mailman.log, mailmansuite.log or even /var/log/httpd/access_log. I managed to reject and approve messages manually using mailmanclient and the REST API, so the issue appears to be somewhere between Postorius 1.3.3 and mailmancore. Any ideas? -- .:.Sebastian Hagedorn - Weyertal 121 (Gebäude 133), Zimmer 2.02.:. .:.Regionales Rechenzentrum (RRZK).:. .:.Universität zu Köln / Cologne University - ✆ +49-221-470-89578.:.

5 years, 2 months

Re: mm3 installation question

by Mark Sapiro

On 3/6/24 1:33 AM, Odhiambo Washington wrote: > On Wed, Mar 6, 2024 at 12:13 PM Stephen J. Turnbull < > turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > >> Odhiambo Washington writes: >> >> > The odd thing is that the HOWTO that he followed never involves the >> > manipulation of any urls.py at all - it's not even mentioned at any >> > point. So obviously the issue is caused by something else and I >> > suspect something within Apache needs to be re-evaluated in the >> > guide. The HOWTO installs mailman-web which contains a urls.py. >> >> Note that Apache doesn't know about the "/postorius" and "/hyperkitty" >> URI paths. It is quite unclear to me how this works at all with >> either the >> >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> >> version of urls.py or the reverse order version >> >> path('postorius/', include('postorius.urls')), >> path('hyperkitty/', include('hyperkitty.urls')), >> path('mailman3/', include('postorius.urls')), >> path('archives/', include('hyperkitty.urls')), This is an issue with Django. I'm not sure of the exact mechanism, but consider the first of the above two sets. If you go to the mailman3/ URL that gets redirected to the postorius/ URL. I.e. two paths that ultimately reference the same thing wind up considering the second path as the canonical path and redirecting the first path to the second. I was not initially aware of this when I added the postorius/ and hyperkitty/ paths to mailman_web/urls.py. I did this with the intent of making either set of paths work, and I added those paths after the mailman3/ and archives/ paths, and this version got released as mailman-web 0.0.8. That caused the recommended Apache config to fail because now the mailman3/ and archives/ paths were redirected to the postorius/ and hyperkitty/ URLs which are not in the recommended Apache config. I have since reordered the paths in mailman_web/urls.py, but that version isn't yet released. Thus the issue. See https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… for some background. > My thinking then is that the documentation at > https://docs.list.org/en/latest/install/virtualenv.html#apache-configuration > needs to be fixed by adding the missing bits, What needs to be done is a mailmab-web 0.0.9 release in PyPI. This will fix the issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Docker Support Sucks

by Brian Carpenter

Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: ### The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: [webservice] configuration: /path/to/gunicorn.cfg and then in the gunicorn.cfg you can add [gunicorn] timeout = 90 graceful_timeout = 30 ### I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. After restarting docker-mailman, I can't access Postorius due to the following error: ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 160, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 84, in create_connection raise err File "/usr/lib/python3.6/site-packages/urllib3/util/connection.py", line 74, in create_connection sock.connect(sa) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 677, in urlopen chunked=chunked, File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 392, in _make_request conn.request(method, url, **httplib_request_kw) File "/usr/lib/python3.6/http/client.py", line 1254, in request self._send_request(method, url, body, headers, encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1300, in _send_request self.endheaders(body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1249, in endheaders self._send_output(message_body, encode_chunked=encode_chunked) File "/usr/lib/python3.6/http/client.py", line 1036, in _send_output self.send(msg) File "/usr/lib/python3.6/http/client.py", line 974, in send self.connect() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 187, in connect conn = self._new_conn() File "/usr/lib/python3.6/site-packages/urllib3/connection.py", line 172, in _new_conn self, "Failed to establish a new connection: %s" % e urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f96340a2e10>: Failed to establish a new con$ During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/requests/adapters.py", line 449, in send timeout=timeout File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", line 725, in urlopen Commenting out "configuration: /opt/mailman/gunicorn.cfg" brings Postorius back up. I am really frustrated here. All I want to do is export a 3000 member list and I can't. Updating Mailman 3 using new Docker images shouldn't break a stable installation either. Please help. Brian

5 years, 3 months

Another set of new releases

by Abhilash Raj

Hi Everyone, Hope everyone had a great weekend! I am pleased to announce new set of releases: - Postorius 1.3.2 - Django-mailman3 1.3.2 - Hyperkitty 1.3.2 This release was required as it turned out 1.3.1 releases did not includes translations in the tarballs that I created and uploaded to PyPI. They do include a couple of bugfixes and more translations. - Hyperkitty (https://hyperkitty.readthedocs.io/en/latest/news.html#id1) - Postorius (https://postorius.readthedocs.io/en/latest/news.html#id1) All three of these releases also officially drop support for Django 1.11. Although, there hasn't been any code change that breaks compatibility with 1.11. It has just been dropped form our CI machinery since our dependencies no longer support 1.11. All the releases are available on PyPI, as usual! -- Thanks Abhilash Raj

5 years, 9 months

Re: More Mailman releases!

by Abhilash Raj

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)

2 years

Approve an email

by Lars Bjørndal

Hi, list! I'm on Fedora 36 with the packages mailman3-3.3.4-6.fc36.noarch and postorius-1.3.6-2.fc36.noarch installed. with the command sudo -u mailman mailman3 create <listname> I was able to create a list. I'm not able to find out how to setup and configure the postorius package. There's no mailman-web command. Hyperkitty will not installed du to a dependency conflict, but I dont need archiving for the list. Here comes my quesitons: - What's the easiest way to approve an email sent to the list? - How can I configure the list to accept messages also from non members? - How can I setup postorius to work on Fedora? I have django-admin, but I'm not sure where to go. Thanks in advance, Lars

2 years, 10 months

Re: Docker Support Sucks

by Mark Sapiro

On 7/21/20 5:40 PM, Brian Carpenter wrote: > Ok, now that I got that out of the way. Maybe I can get some help here for a Docker Installation of Mailman 3. Abhilash (@maxking) is one person and he has a $DayJob. We're all doing the best we can. > I updated a Maxking's Docker installation to Postorius 1.3.3. It made my client's list unusable to a continual stream of removals due to ghost bounce processes. This is not a Docker issue per se. It is a consequence of upgrading Mailman core to 3.3.1+ and processing many old, stale, previously unprocessed bounces. See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. > > I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: > > ### > The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: > > [webservice] > configuration: /path/to/gunicorn.cfg > > and then in the gunicorn.cfg you can add > > [gunicorn] > timeout = 90 > graceful_timeout = 30 > ### > > I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. > > After restarting docker-mailman, I can't access Postorius due to the following error: > > ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available Is Mailman core running? If not, whats in core's mailman.log as to why not? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 3 months

Re: Editing "automatic responses" tab i Postorius does not work

by David Krantz

But this one is already exposed. But I cannot change it anyway as the tab requires URIs for the different templates to allow saving. I do not use those URIs as I have configured the defaults as I like them. I tried once and it failed so I decided to set the defaults instead. cheers. // David On Sun, May 21, 2017 at 3:48 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/21/17 5:22 AM, David Krantz wrote: >> >> I am trying to change e.g. the value of "notify admin on membership >> changes" through postorius. > > > There are still many settings not yet exposed in Postorius. We are > painfully aware of this and will probably be working on some of this at > the PyCon sprints starting tomorrow. > > Until we get more of these addressed, you will need to use tools like > "mailman withlist" to set these things. > > -- > 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/

8 years, 5 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 1:37 PM, Ruth Ivimey-Cook wrote: > Thanks Mark, Ignore bracketed numbers below ([1], [2], etc.) They come from conversion of the HTML only post to plain text. > On 20/06/2020 03:53, Mark Sapiro wrote: > > What are your Django settings for MAILMAN_REST_API_URL, > MAILMAN_REST_API_USER and MAILMAN_REST_API_PASS and do these agree with > the [webservice] settings for hostname, port, use_https, admin_user and > admin_pass in mailman.cfg in core and is the port open to the outside on > the core machine? > > greyarea-post is the mailman-core and exim server. > > greyarea-web1 is the postorius and hyperkitty server. > > On greyarea-web1, in django-settings.py, > > MAILMAN_REST_API_URL = '[1]http://greyarea-post:8870' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = XXXX > > and both the above-named hosts are also included in ALLOWED_HOSTS along > with localhost. > > On greyarea-post, in mailman.cfg: > > [webservice] > admin_pass: XXXXX > admin_user: restadmin > api_version: 3.1 > hostname: 0.0.0.0 > port: 8870 > use_https: no > > The password and username are as on web1. That all looks good. > Do you see REST requests from the Postorius machine in core's > mailman.log and access.log? > > Yes, there are lots of requests of the form: > > [07/Jun/2020:15:00:01 +0000] "GET /3.1/lists?count=10&page=1 > HTTP/1.1" 200 470 "-" "GNU Mailman REST client v3.3.1" > > I made a new list using the core CLI, and as a result of navigating > directly to the list archive page I get to see: > > [06/Jun/2020:23:00:02 +0000] "GET /3.1/lists/chbcdaily(a)ch-bc.org.uk > HTTP/1.1" 200 365 "-" "GNU Mailman REST client v3.3.1" > > ... but in neither case do I get a complete screen on the browser or > 'follow-up' requests. > > I don't have a file access.log on the greyarea-post. Yes, that's actually a gunicorn log so would only be on greyarea-web1, but the mailman.log tells us the requests are getting to the core REST API, so we don't need that info. > On the greyarea-web1 I have mailmansuite.log with the last few lines: > > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/ba > se.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File > "/opt/mailman3/lib/python3.6/site-packages/mailmanclient/restbase/co > nnection.py", line 124, in call > 'Could not connect to Mailman API: ', repr(e)) > mailmanclient.restbase.connection.MailmanConnectionError: ('Could > not connect to Mailman API: ', > 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', > port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk > (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection > object at 0x7f5416db8518>: Failed to establish a new connection: > [Errno 111] Connection refused\',))",),)') > ERROR 2020-06-03 01:02:06,115 29002 django.request Service > Unavailable: /postorius/lists/ OK. This is telling us that mailmanclient (the REST API Python bindings that Postorius uses to access core) is having trouble establishing a connestion to the core REST server, but it clearly gets there some of the time based on the mailman.log entries. > the uwsgi-error_*.log contains many lines of the form: > > api: url is > [2]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > api: url is > [3]http://greyarea-post.cam.ivimey.org:8870/3.1/lists?count=10&page= > 1 > > My reason for thinking, in my original post, that the wrong host > address is being used is that the ConnectionError above contains > 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as > the listen address on the core web service and does not appear in the > config for postorius. The ConnectionError above comes from requests.request (docs at <https://requests.readthedocs.io/en/master/>). Client only provides a URL in the call to request and the URL is the baseurl + the path and the baseurl is MAILMAN_REST_API_URL which you have as http://greyarea-post:8870. Entries above have http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? I suspect a DNS lookup issue. How does greyarea-web1 resolve greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS rather than relying on /etc/resolv.conf and/or /etc/hosts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Mailman-users search results for query "Postorius"