Search results for "Postorius" - Mailman-users

Re: Postorius no connection to REST API

by Richard Rosner

Abhilash Raj wrote: > is the config to talk uwsgi protocol and you want to configure Web server to Proxy using the same protocol. You can find that in the uwsgi docs here: https://uwsgi-docs.readthedocs.io/en/latest/Apache.html You probably need an apache module to speak uwsgi, the docs should have the details. > Notice the URL is uwsgi:// instead of http://. > Other way is to configure uWSGI to speak HTTP, which can be done by replacing "uwsgi-socket" by "http-socket” in the uwsgi.ini configuration. This might be the easiest for you to try, do make sure to restart the mailman-web service after making the change in uwsgi.ini. Thanks, that already helped quite a bit. The website is now loading again, but unfortunately not much else. The site still shows no Connection to REST API.

3 years, 9 months

Re: How to change the language in mailman3

by Massimo Zappalà

Hi everyone, Mark thanks for the reply. My installation was done on Debian Buster by installing the mailman3-full package I can't find the path you indicated: > Mailman core in mailman/messages/ > Hyperkitty in hyperkitty/local/ > django-mailman3 in django-mailman3/local/ > postorius in postorius/local/ Maybe some packages are missing? > To set language for Django (i.e. hyperkitty and postorius) see > https://docs.djangoproject.com/en/3.0/topics/i18n/translation/#how-django-di.... What are the files to be edited? > For Mailman core, set [mailman] default_language: in mailman.cfg. Ok Done > You also need to (re)generate the .mo file which can be done with the > generate_mo.sh script. I can't find the script > For Django, you need to generate .mo files with > django_admin compilemessages Where should this be written? Thank you Max

4 years, 10 months

Re: Things I miss about mailman2

by Mark Sapiro

On 3/17/20 1:59 PM, Quanah Gibson-Mount wrote: > >> Click on the subject in the held messages list. At the bottom of the >> dialog that opens, there is a drop down to set the user's moderation. >> Normally, you would set it to 'default processing'. > > I do not see any such option. After clicking on the header the only > options available at the bottom are: > > Accept, Reject, Discard, Show Source, Show Header > > There are zero drop downs anywhere. This was implemented by <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released in Postorius 1.3.0. >> This was not "removed". It just hasn't been implemented in MM 3 yet. > > So in terms of available functionality that was present in MM2, it was > removed. It may need to be re-implemented, but this was a core feature > that was present in the prior version that is no longer available. Yes, we are aware of many things that are not yet exposed/implemented in Postorius and elsewhere. There are currently 580 open issues at <https://gitlab.com/groups/mailman/-/issues>. We are working on these things as we can. We would love to have your help in fixing these. In the mean time, there are really only 2 or 3 core developers working on this and we are all volunteers, so it takes time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

[MM3-users]Re: Installation issues

by Simon Hanna

On 04/25/2016 03:50 PM, Hellings Simon (EAST KENT HOSPITALS UNIVERSITY NHS FOUNDATION TRUST) wrote: > Hi Simon > > I have tried to re-install MM3 this morning but am now facing a different error message: > > Output from DJANGO log as follows: > > ERROR Internal Server Error: /mailman3/lists/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index > lists = sorted(List.objects.all(only_public=only_public), > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all > objects = getattr(get_client(), self.resource_name_plural) > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists > response, content = self._connection.call('lists') > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call > response, content = Http().request(url, method, data, headers) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request > (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, he aders) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse > response.begin() > File "/usr/lib/python2.7/httplib.py", line 415, in begin > version, status, reason = self._read_status() > File "/usr/lib/python2.7/httplib.py", line 379, in _read_status > raise BadStatusLine(line) > BadStatusLine: '' > ERROR Internal Server Error: /mailman3/lists/ > Traceback (most recent call last): > File "/opt/mailman/mailman-bundler/eggs/Django-1.8.12-py2.7.egg/django/core/ha ndlers/base.py", line 132, in get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/vi ews/list.py", line 511, in list_index > lists = sorted(List.objects.all(only_public=only_public), > File "/opt/mailman/mailman-bundler/eggs/postorius-1.0.3-py2.7.egg/postorius/mo dels.py", line 144, in all > objects = getattr(get_client(), self.resource_name_plural) > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 158, in lists > response, content = self._connection.call('lists') > File "/opt/mailman/mailman-bundler/eggs/mailmanclient-1.0.1-py2.7.egg/mailmanc lient/_client.py", line 105, in call > response, content = Http().request(url, method, data, headers) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1609, in request > (response, content) = self._request(conn, authority, uri, request_uri, metho d, body, headers, redirections, cachekey) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1351, in _request > (response, content) = self._conn_request(conn, request_uri, method, body, he aders) > File "/opt/mailman/mailman-bundler/eggs/httplib2-0.9.2-py2.7.egg/httplib2/__in it__.py", line 1307, in _conn_request > response = conn.getresponse() > File "/usr/lib/python2.7/httplib.py", line 1051, in getresponse > response.begin() > File "/usr/lib/python2.7/httplib.py", line 415, in begin > version, status, reason = self._read_status() > File "/usr/lib/python2.7/httplib.py", line 379, in _read_status > raise BadStatusLine(line) > BadStatusLine: '' > [25/Apr/2016 06:21:10] "GET /mailman3/lists/ HTTP/1.1" 500 121854 I'm sorry I respond so late. Somehow lost this message in my inbox. I'm not sure what that error means... If you're still suffering from this issue, could you post the exact versions of all the components you are using in your virtualenvironments? And also the exact python versions you are using. Did you modify any files during the mailman-bundler installation?

9 years

Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org>

3 years, 7 months

Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Mark Sapiro

On 3/29/20 6:46 PM, Abhilash Raj wrote: > Do you have something like this[1] in your settings.py file? > > [1]: https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… > > `EMAIL_BACKEND = 'django.core.mail.backends.console.EmailBackend'` > > `This is a dummy email backend which will basically only print the email to stdout, which seems to happen in your uwsgi-error.log. If you do, please comment it out and see if that solves your issue.` I know Ralph previously posted > $ grep ^EMAIL settings.py > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 but is this perhaps overridden in a settings_local.py file? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:04 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:52 PM, Odhiambo Washington wrote: > > > > Do I need to install sassc in the base OS or in the virtualenv? > > Have you checked `which sassc` to see if you don't already have it. It > doesn't matter whether it's in the base OS or the virtualenv. Things > running in the virtualenv can still access the base OS, just not vice > versa. > I install sassc, because sass installation always failed - after some upgrade. <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I remember posting about it in 2020 or 2019 :) root@gw:/usr/home/wash # which sassc /usr/local/bin/sassc -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 1 month

How to stop minutely mails about readme_renderer

by Stephen J. Turnbull

Axel Rau writes: > /usr/local/py_venv/mailman_33/lib/python3.9/site-packages/readme_renderer/markdown.py:44: > UserWarning: Markdown renderers are not available. Install > 'readme_renderer[md]' to enable Markdown rendering. > warnings.warn(_EXTRA_WARNING) > > I installed cmarkgfm 0.8.0 in my venv, Why did you do that? Is it something in our documentation? The error message is specifically asking for readme_renderer, which is a package available from PyPI. Try installing that. I'm not sure what the "[md]" means (the suffix "[md]" is also in postorius/setup.py), but it probably doesn't matter since readme_renderer.markdown is imported directly by Postorius. Just installing the package should make Postorius happy. Note that something is not right because running setup.py in the venv should automatically install readme_renderer, and I would expect you may have other problems if setup.py did not work correctly.

3 years

Re: mail host choices when creating a new list

by Andrew Hodder

Ah, so obvious I can't believe I hadn't noticed it before, thanks! Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Tue, Oct 24, 2017 at 3:50 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Tue, Oct 24, 2017, at 12:24 PM, Andrew Hodder wrote: > > Abhilash, > I'm not sure what you're referring to, there's no "web hosts" in the admin > panel and I already added the "mail hosts" there (of the four added, only > the first one shows up in the postorius drop down). > > > Ah! I mis-read your email. You need to add new domains in Postorius before > you can create new lists using them. > > You are looking for '/postorius/domains/', add a new domain there, and > then it will show up in the 'mail hosts' in create-new-list form. > > > Sincerely, > > Andrew Hodder > Systems Administrator > Support Operations, Afilias > E-mail: drew(a)afilias.info > Phone: +1 416.673.4164 > Fax: +1 416.646.1541 > > On Tue, Oct 24, 2017 at 3:08 PM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > Hi Andrew, > > On Tue, Oct 24, 2017, at 11:58 AM, Andrew Hodder wrote: > > Hi! > > > > So, I'm trying to create a new list and pick one of the other mail > > domains > > we have configured (from the django admin panel), yet in the "Create New > > List" page in postorius, I see only a single option (the first domain > > we'd > > added/set as the default) in the drop-down under "Mail Host". Am I > > missing > > somewhere else I need to add alternative mail domains to? Thanks in > > advance! > > Yes, you can add new 'Web Hosts' from the Django's Admin console > (admin/django_mailman3/maildomain/). Note that you need to be a > superuser to do this. > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > > -- > Abhilash Raj > maxking(a)asynchronous.in > > >

7 years, 7 months

Re: Unable to ban users via mailman-shell

by Mihai Moldovan

* On 4/13/25 14:43, Mihai Moldovan wrote: > I can't seem to be able to add bans via mailman-shell: What I haven't tested before, but should have done: I can, however, add new bans from Postorius (the web interface) and immediately query them via mailman-shell: >>> for ban in bans: ... print('{0}: {1}'.format(ban.list_id,ban.email)) ... x2go-commits.lists.x2go.org: x(a)y.z Obviously, requests via Postorius also go through the REST API via a POST request, as I'd expect, and are immediately committed to the database (I've checked it by directly opening with SQLite3). I'm quite stumped why the shell interface doesn't commit the data to the DB. Unfortunately, the web interface doesn't allow mass-adding addresses, which is why I wanted to do that via the shell. Mihai

2 months

Mailman-users search results for query "Postorius"