Search results for "Postorius" - Mailman-users

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

8 months

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

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

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

4 years, 6 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, 11 months

Re: Multi-domain oddities in Hyperkitty and Postorius

by Mark Sapiro

On 2/15/23 18:35, Mark Sapiro wrote: > > $ django_admin shell > >>> from django.contrib.sites.models import Site > >>> new_site = Site(id=5, domain='5.example.com', name='display_name') > >>> new_site.save() > > Of course the values are up to you and you can omit the id= to have > Django assign the first available.. Also note that the above is a django_admin shell interaction. You can also do this in python, but you need to precede the above with ``` >>> import os >>> import sys >>> sys.path.insert(0, '/path/to/directory/containing/settings.py') >>> os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' >>> import django >>> django.setup() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

mailman import21 passwords

by Sam Darwin

Hi, On https://docs.mailman3.org/en/latest/faq-migration.html it says "Mailman 3 has a completely new account management system, none of the passwords from Mailman 2 will work with Mailman 3. Each user needs to sign up in Postorius for a new account to manage their memberships on all lists on a single instance." "Each user needs to sign up in Postorius for a new account" I am (personally) satisfied with this answer. However others at the company are asking for a detailed explanation. Consider that - - Mailman2 has access to password information. - Import scripts such as "import21" are able to import list information. - It seems that scripts such as "import21" could also generate new user accounts and passwords based on the previous ones. Why can't passwords be imported from mailman2 to mailman3? How difficult would it be to do? (is there a link to where this is already explained? ) Thanks

1 year, 2 months

Re: Hiding the "subscribe without creating an account"

by Matthew Blissett

On 13/07/2024 07:17, Mark Sapiro wrote: > On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >> >> Is there a configuration option that does this, or was it a custom >> change made in >> the templates? Was the change made to reduce fake registrations? Did >> it work? > > > It was added in Postorius 1.3.9. See the UI section at > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 > > Yes, the change was made in an attempt to reduce fake registrations. > > We haven't really studied it's effectiveness. It seems to help > somewhat, but it also seems that bots may already have a template to > POST so removing it from the UI is not a complete solution. They would be missing the CSRF token (a hidden field on the anonymous signup form) so this ought to fail. > There is also a lot of email to innocent third parties and > non-existent addresses from attempts to register them for an account. There are patches to integrate a Captcha system here: https://gitlab.com/mailman/django-mailman3/-/issues/33 I think it's needed, as less than 24 hours after migrating to Mailman 3 I already see bots retrieving the signup form to get the CSRF token (GET /accounts/signup/?next=/postorius/lists/) then POSTing the request for a new user account (POST /accounts/signup/). There's also the setting ACCOUNT_EMAIL_UNKNOWN_ACCOUNTS = False, which prevents spam from the "forgot password" address, see https://gitlab.com/mailman/postorius/-/issues/591 -- Matt

1 year, 5 months

Re: Timeout in Postorius when trying to approve or reject moderated messages

by Mark Sapiro

On 8/27/20 8:07 AM, Sebastian Hagedorn wrote: > > Right now everything is running as root (except for Apache). I realized > too late that I should've used a mailman user. Could that be the reason > for the issue? Since you have determined it was a browser issue, that probably isn't the reason, but running Mailman as root is a bad idea in general for security reasons. I don't know if it's relevant or not, but I have just recently had issues with Firefox not working properly on two different (not mailman) web sites, and these issues were fixed by clearing cookies and cached data from the affected sites and restarting Firefox. -- 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: Error when click on mailing list: An error occurred while processing your request.

by Mark Sapiro

On 7/9/24 6:11 PM, adam.heathcote(a)utas.edu.au wrote: > > mailman members -R owner your_list(a)your.domain > > Shows myself as an owner as well as the imported owners from the previous list. You originally wrote: "but now when clicking on the list, Postorius shows: An error occurred while processing your request." I'm guessing you are clicking the list in the Postorius `Mailing Lists` view, i.e. something like https://example.com/mailman3/ or https://example.com/mailman3/lists, and you are logged in, and the link is to https://example.com/mailman3/lists/listname.example.com. What if you go to that page without being logged in, or logged in as a different user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Mailman-users search results for query "Postorius"