Search results for "Postorius" - Mailman-users

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, 5 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

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 "^$|^.*#" :-)

3 years, 11 months

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.

2 years, 10 months

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, 5 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

1 week, 1 day

Re: Bounce processing

by Mark Sapiro

On 4/23/20 2:27 PM, Andrew Hodgson wrote: > > When users are set to disabled after their bounce score reaches a certain threshold, I seem to recall on Mailman 2 they were sent an email with a link to reactivate their subscription. On Mailman 3 they are told to contact the list admin, I have had messages from a few subscribers regarding this asking how they can re-enable delivery. The message the user is sent in built from the list:user:notice:warning template. The next release of Postorius will offer that template as one you can edit, but the current release doesn't. You can make an edited template in the var/templates/ directory. The logged-in user can go to her settings pages in Postorius at accounts/subscriptions/ to set delivery status. The generic template can't be that specific because Mailman Core doesn't even know if you have Postorius. > I am also getting bounces that look like they are coming from Qmail (Yahoo addresses) which are being forwarded to the list owner as unrecognised bounces. Should the type of bounces that Mailman 2 was handling be handled in Mailman 3 or is the way that the addresses are extracted different? I have disabled the relevant users but do have the bounces to hand. The bounce recognition for Mailman 3 is essentially the same as Mailman 2.1. If you post one of these complete bounce messages, we'll investigate why it isn't recognized. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: Character set for postorius

by Simon HANNA

It's a known issue. There is a fix, but it's held up... If you want you can manually merge the fix for the time being https://gitlab.com/mailman/mailmanclient/merge_requests/10 On May 18, 2017 9:29:11 PM GMT+02:00, David Krantz <gazorg(a)gmail.com> wrote: >Hi, > >I'd like to have my descriptions of maillists with the correct >characters for my languages... Where is the character set for this >determined? > >If I input e.g. 'è' (è) or 'ö' (ö) it is substituted with >a '?'. Of course the html entities are not allowed either, the >ampersand '&' is escaped somewhere between output and input. > >Cheers >// David >_______________________________________________ >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.

7 years, 11 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Fri, May 14, 2021 at 2:41 PM Odhiambo Washington <odhiambo(a)gmail.com> wrote: > > > On Wed, Feb 3, 2021 at 5:00 AM Abhilash Raj <maxking(a)asynchronous.in> > wrote: > >> Hey Everyone, >> >> I am pleased to announce new stable releases for Mailman Core, Postorius, >> Hyperkitty. >> >> These include both new features and bug fixes. Complete change log for >> each components: >> >> Mailman Core 3.3.3: >> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… >> Postorius 1.3.4 >> https://docs.mailman3.org/projects/postorius/en/latest/news.html >> Hyperkitty 1.3.4 : >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html >> >> Minimum supported Python version is 3.6. >> >> You can install them using: >> >> $ pip install --upgrade postorius hyperkitty mailman >> > > I don't know if this is necessary, but I used to do it with another update > method documented by Mark. > After running the upgrade script (from that method) I would run these too: > > /opt/mailman/mm/bin/django-admin collectstatic --clear --noinput > --verbosity 0 > /opt/mailman/mm/bin/django-admin compress > /opt/mailman/mm/bin/django-admin compilemessages > /opt/mailman/mm/bin/django-admin migrate > > Now I did run them and got an error and I wonder if I should be worried: > > > (venv) [mailman3@gw ~]$ /opt/mailman/mm/bin/django-admin compress > CommandError: *An error occurred during rendering > /opt/mailman/mm/venv/lib/python3.7/site-packages/django_allauth-0.42.0-py3.7.egg/allauth/templates/account/password_reset.html: > /bin/sh: sass: Permission denied* > Compressing... (venv) [mailman3@gw ~]$ > It actually turns out to be a show-stopper: ERROR 2021-05-14 11:48:12,691 7086 django.request Internal Server Error: /mm3/accounts/login/ Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/base.py", line 145, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/core/handlers/base.py", line 143, in _get_response response = response.render() File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/response.py", line 105, in render self.content = self.rendered_content File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/response.py", line 83, in rendered_content return template.render(context, self._request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 171, in render return self._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/loader_tags.py", line 150, in render return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 163, in _render return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 936, in render bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/Django-3.0.8-py3.7.egg/django/template/base.py", line 903, in render_annotated return self.render(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 143, in render return self.render_compressed(context, self.kind, self.mode, forced=forced) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 97, in render_compressed return self.render_offline(context) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_compressor-2.4-py3.7.egg/compressor/templatetags/compress.py", line 82, in render_offline 'is the original content:\n\n%s' % (key, original_content)) compressor.exceptions.OfflineGenerationError: You have offline compression enabled but key "fa788b08b65fd318d68cfc5afebc18acd3exxxxxx54d863572ad1754f368" is missing from offline manifest. You may need to run "python manage.py compress". Here is the original content: <link rel="stylesheet" href="/static/hyperkitty/libs/fonts/icomoon/icomoon.css" type="text/css" media="all" /> <link rel="stylesheet" href="/static/hyperkitty/libs/fonts/droid/droid.css" type="text/css" media="all" /> <link rel="stylesheet" href="/static/django-mailman3/css/main.css" /> <link rel="stylesheet" type="text/x-scss" media="all" href="/static/hyperkitty/sass/hyperkitty.scss" /> -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

3 years, 11 months

Re: Postorius fails to show list because of a large message being held

by Mark Sapiro

On 12/21/21 4:42 PM, dancab(a)caltech.edu wrote: > > I'm considering the settings below for gunicorn.cfg > > [gunicorn] > OK > # No of seconds to wait before killing the worker processes. > graceful_timeout = 600 I don't think this is relevant. It only affects the delay before killing a worker when gunicorn is restarted, but I suppose it won't hurt. > # Timeout for the requests. > timeout = 900 I wonder if this is really the issue. Do you have tracebacks from these timeouts? I think there may be something else causing this that increasing the timeout won't solve. Maybe some database locking deadlock or similar issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Mailman-users search results for query "Postorius"