Search results for "Postorius" - Mailman-users

User with abo to list can not set to another moderation flag

by Chris

Hi again, I've one weird problem. I've some lists and a user which is a moderator on both lists. Steps to reproduce Postorius -> Users -> search for the user to change -> manage Both Lists are shown Moderarion Flag on a newer List was changed from standard to accept -> On the older list I've tried from Standard to Accept -> click on the button to accept changes result in reverting to "standard" (the setting which I want to change). Any hints on that? (can't find any difference between those lists except name und descriptions. )

4 months, 2 weeks

Missing styling on select pages

by grodriguez＠usra.edu

Hello all, I installed mailman3 on Rocky Linux 9 via the Virtualenv Installation installation guide. I configured Apache httpd to proxy gunicorn. For the most part, everything is looking good except for some select pages that do not contain the styling like all other pages. When a user sees the "Verify Your Email Address" screen, it's without any of the styling. /accounts/confirm-email/ Same for when a user tries to reset their password. The initial screen looks good (with styling), but after entering the email address and clicking "Reset My Password", the following screen is bare. /accounts/password/reset/done/ I have Mailman 3.3.10, Postorius Version 1.3.13, and HyperKitty version 1.3.12. Any suggestions?

2 months, 1 week

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 12, 2016, at 12:18 PM, Mark Sapiro wrote: >It is the intent that Postorius will eventually expose all these >settings. We're not there yet. At present you could possibly do this by >interacting with mailmanclient, although I'm not certain the settings are >exposed there. I'm not sure if they're exposed in mailmanclient, but they are exposed in the core's REST API, on the member resource. It's the `delivery_mode` attribute and it takes as legal values one of 'regular', 'plaintext_digests', 'mime_digests', and 'summary_digests' (IOW, the enum item names for the DeliveryMode enum). Cheers, -Barry

9 years, 1 month

Re: Rejection Reason for refusing a subscription request

by Brian Carpenter

On 3/27/21 6:03 PM, Mark Sapiro wrote: > It's in Postorius since 1.3.3. If in the held message view, you click > the subject of a held message, you get a popup dialog the shows the > message with options to also show headers or the raw message. There is > also a dropdown t=o set the poster's moderation action and a box for a > reject reason if you click the reject button in the dialog. > > Do you not see this? I am referring to "Subscriptions pending approval". I apologize if I did not make that clear. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 2 months

An archive/read-only list on a full setup?

by Andreas Schamanek

I have a working full installation of mailman3, postorius and hyperkitty (on Debian 11). Now I wanted to host the archive of a remote list, and I am wondering how to do this properly. After I found no documentation and no posting I simply created a list in mailman3 with only 1 dummy member. The list address is subscribed to the actual remote list. So, messages arrive and are archived. But that's not optimal because hyperkitty thinks it's a normal list where it should be read-only and do not allow subscriptions etc. What's the proper way to set up a hyperkitty-only list? -- -- Andreas :-)

2 years, 2 months

Re: FYI: Django security releases issued: 4.0.6 and 3.2.14

by David Newman

On 7/7/22 10:25 AM, Mark Sapiro wrote: > I just upgraded from Django 3.2.11 to 3.2.14 on mail.python.org and > lists.mailman3.org. How to upgrade mailman-web to align with Django? I upgraded from Django 3.0.14 to 3.1.14 and then 3.2.14 using these docs: https://docs.djangoproject.com/en/4.0/howto/upgrade-version/ But then this upgrade command returned a complaint that mailman-web 0.0.5 requires Django<3.1: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi and it downgraded Django back to 3.0.14. I did not see anything about this in the Django for Mailman Admins doc, but I may have missed something. https://docs.mailman3.org/en/latest/django-primer.html Thanks. dn

2 years, 11 months

Mailman 3 Core user assistance

by Tony Deshields

I currently have a docker mailman stack that utilizes Django LDAP backend for authentication. I have my users attributes mapped as you see below in my settings.py file. Whenever a user logs into postorius with their 'uid', mailman-core uses their 'uid' as their email address instead of the 'email' attribute. Is there anyway to change this functionality? I would like my users to be able to login with their enterprise uid but be mapped to their email but I feel like there is a disconnect between Django and MM3 core. Any assistance is much appreciated. AUTH_LDAP_USER_ATTR_MAP = { "uid" : "userPrincipalName", "first_name": "givenName", "last_name": "sn", "email" : "mail", }

1 year, 5 months

Re: Assistance with mailman3

by Abhilash Raj

On Wed, Mar 13, 2019, at 8:47 AM, ayen(a)afilias.info wrote: > Hi all > > I'm pretty new to mailman but been trying to install mailman 3 and been > running into issues, following the documentation at > http://docs.mailman3.org/en/latest/prodsetup.html > installed Python 3.6, nginx, ruby-sass > then with pip installed whoosh mailman-hyperkitty postorius hyperkitty > mailman > > tried to start mailman core, symlinked master and runner -> /usr/bin/ > (otherwise it wouldn't run) > mailman core starts but when I hit the api url I get this in the logs > > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/database/transaction.py", line 50, in wrapper > rtn = function(*args, **kws) > File > "/usr/local/lib/python3.6/dist-packages/mailman-3.2.2-py3.6.egg/mailman/rest/wsgiapp.py", line 218, in __call__ > return super().__call__(environ, start_response) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 248, in __call__ > responder, params, resource, req.uri_template = > self._get_responder(req) > File "/usr/local/lib/python3.6/dist-packages/falcon/api.py", line > 664, in _get_responder > route = self._router_search(path, req=req) > TypeError: find() got an unexpected keyword argument 'req' > Mar 13 10:54:44 2019 (17273) 127.0.0.1 - - "GET /3.1/ HTTP/1.1" 500 59 > > and on frontend "A server error occurred. Please contact the administrator." Inside your virtualenv, please run: $ pip install -U falcon==1.4.1 This should fix the above error. > > that leads to my gnu not working and throwing keyerrors for postorius. > > I'm using a clean install of ubuntu 18.04 but have also tried to > install on centos 7 with no success. > > Are there any missing dependencies or steps that I've missed any > assistance would be appreciated. > > Andy > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

Re: Unknown attribute: max_message_size

by Mark Sapiro

On 06/21/2018 03:29 AM, Alexander Klotz wrote: > Hi, > > unfortunately we still have problems configuring a list so that it > allows a message size larger than 40 KB. Neither the workaround > described here: > https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… > (required was already set to false) nor this docker setup by yova > https://gitlab.com/mailman/postorius/issues/246 worked. Are there any > other options we could try? Use 'mailman shell'. I.e. 'mailman shell -l listname@domain' and set m.max_message_size = N where N is the number of KB you want. -- 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: Where does sender postorius@ come from?

by Mark Sapiro

On 6/15/23 14:03, Jens Günther wrote: > > > Am 15.06.23 um 00:34 schrieb Mark Sapiro: >>> - Then I tried settings_local.py with: >>> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' Sorry, this is actually a different setting. There are actually two more that control this. These are DEFAULT_FROM_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#default-from-email> and SERVER_EMAIL <https://docs.djangoproject.com/en/4.2/ref/settings/#server-email>. Note that the defaults mentioned in the Django docs are probably overridden in your settings.py, but you should set them in settings_local.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Mailman-users search results for query "Postorius"