Search results for "Postorius" - Mailman-users

Re: New platform administrators

by Abhilash Raj

On Tue, Sep 18, 2018, at 1:14 PM, Simon Hanna wrote: > On 9/18/18 5:42 PM, Hellen Cubero wrote: > > Hello! > > I would like to know how to add a new site administrator to the mailman 3.2 > > platform. Can you help me please? > > You are probably referring to Postorius the webui? > > If yes, you just add another superuser. If the admin is enabled, you can > just visit https://you-url/admin sign in, and create a new user with > staff and superuser permissions. > > You can also do that on the cli using ./manage.py createsuperuser A better way would be to ask them to sign-up as a regular user and then you can go into the Admin Console (/admin) and add flags for Superuser for the user you want to promote. Create Superuser and Django's create user interfaces don't tie up with all-auth, which creates problems because their EmailAddress records aren't created, like they should be. -- thanks, Abhilash Raj (maxking)

7 years, 2 months

Re: Default setting for Delivery status

by Mark Sapiro

On 10/10/22 15:31, Mark Dale via Mailman-users wrote: > > Where and how do I set the default setting of "Delivery status" to be > "Enabled". It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… > I'm not seeing any clues in mailman3-web/settings.py > > At the moment, a new subscriber is neither "Enabled" or "Disabled". That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 2 months

Re: New year releases!

by Torge Riedel

Dears, I like to know and discuss ideas to get the update process more stable! Today I updated core and web of mailman3 and ran into all the issues you can have: - Dependencies are not updated properly - In case you use "--force-reinstall" Django gets also updated in web and you need to update the urls.py file accordingly - Enhancement of settings file required (DEFAULT_AUTO_FIELD = ...) Finally I got it working, but there is always the fear for breaking something on update. I know it is open source and no one gets paid for the work. But I think there is space for improvement here. Kind regards Torge Am 04.01.23 um 10:59 schrieb Abhilash Raj: > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > 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/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > 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 > > > > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to torgeriedel(a)gmx.de

2 years, 10 months

Re: New year releases!

by Jeff

I finally got around to doing this upgrade. I followed the instructions at: https://docs.mailman3.org/en/latest/upgrade-3.2.html Everything seemed to go fine but, mailman3 failed to start because “_BindParamClause” could not be found in sqlalchemy.sql.expression. It looks like alembic-1.6.2 is not completely compatible with SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in alembic-1.6.2, but should Mailman start requiring a newer version of alembic? > On Jan 4, 2023, at 4:59 AM, Abhilash Raj <maxking(a)asynchronous.in> wrote: > > Hello Everyone, > > Happy new year! > > I am pleased to announce several new releases for GNU Mailman project. > > 1. Mailman Core 3.3.8 [1] > 2. Postorius 1.3.8 [2] > 3. Hyperkitty 1.3.7 [3] > 4. Mailmanclient 3.3.5 [4] > 5. Django-mailman3 1.3.9 [5] > 6. Mailman-hyperkitty 1.2.1 [6] > > 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/mailman/en/latest/src/mailman/docs/NEWS.… > [2]: https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > [3]: https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > [4]: https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > [6]: https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > Finally, the minimum Python version required is 3.7, and all the components now support Python 3.7 to 3.11. > > Thanks to all the contributors for making this release possible! > > If you find any issues, you can report them at the respective bug tracker for the projects. The links to issue trackers are available > here: https://docs.mailman3.org/en/latest/ > > 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 > > > -- > thanks, > Abhilash Raj (maxking) > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to mm3(a)steele.com ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/vnd.microsoft.icon Name: favicon.ico Replaced multipart/alternative part with first alternative.

2 years, 8 months

Re: Mailman Header Behavior

by Samir Faci

Perfect, Thanks. Is there a way to set this as a default for all new lists being created? Still working on the new styles, I imagine that can be set there during the selection of the list type. -- Samir Faci On Fri, May 15, 2020 at 9:44 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/15/20 9:31 AM, Samir Faci wrote: > > > > Is there a way to force mailman to ensure that the list name shows up in > > the from field? > > In Postorius Settings -> DMARC Mitigations set DMARC mitigation action > to Replace From with list address and set DMARC Mitigate unconditionally > to Yes. > > -- > 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://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 6 months

Re: Unable to remove non-member

by Mark Sapiro

On 9/29/20 4:54 AM, Brian Carpenter wrote: > On 9/29/20 12:40 AM, Mark Sapiro wrote: >> Is that all it said? The code says it is >> >> The user could not be removed: <error message> >> >> Where <error message> is the relevant HTTP error. > > It says: > > The user could not be removed: > > Nothing comes after the colon. > I see the issue. when mailmanclient processes the delete request from Postorius it calls the REST API DELETE method with the URL lists/<listname>/<role>/<address> and the address is `quoted` with urllib.parse.quote_plus, co in this case, the URL becomes lists/<listname>/nonmember/z_email%2Fdomain.org.za(a)domain.org.za This is all fine except the REST API doesn't call urllib.parse.unquote_plus to change the %2F back to slash. This is now reported at <https://gitlab.com/mailman/mailman/-/issues/774>. -- 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: Django Internal Server Error on held_messages

by Mark Sapiro

On 3/24/22 04:02, Hasan Berkay Çağır via Mailman-users wrote: > Hello, > > We've been running a Mailman3 instance with Debian 10's official package: > > Mailman Core Version: GNU Mailman 3.2.1 (La Villa Strangiato) > Mailman Core API Version: 3.0 > Mailman Core Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] > > For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: > > """ > Internal Server Error: /postorius/lists/list.example.com/held_messages As Andrew suggests, you will probably find exceptions with tracebacks in Mailman core's mailman.log. This is probably /var/log/mailman/mailman.log in the Debian package. If you find such and you can't determine the problem from them, post one here. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Mark Sapiro

On 3/31/25 06:26, Philip Bondi wrote: > My /etc/mailman3/urls.py is empty. > > Should I, like it indicates in https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > cp /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py /etc/mailman3/urls.py > chown mailman:mailman /etc/mailman3/urls.py > and add to /etc/mailman3/settings.py > > ROOT_URLCONF = 'urls' You can do all of that, but it's probably unnecessary. What is in /opt/mailman/venv/lib/python3.11/site-packages/mailman_web/urls.py? compare it to https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/urls.py > After completing above, https://systemdatabase.ca/mailman3 still gives > Service Unavailable It appears that https://systemdatabase.ca/postorius works so the issue is almost certainly that your urls.py is missing path('mailman3/', include('postorius.urls')), -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 1 week

Re: Not able to start mailman server

by Stephen J. Turnbull

Mark Sapiro writes: >>>>> Kartheek wrote: > > I am trying to setup postorius using this website - I've used up all my bandwidth for now with the "can't send mail in Docker" thread, but FWIW Kartheek appears to be using Homebrew to manage third party packages on Mac, and in particular to install Python. I don't recall specifically with respect to Python, but I suspect that there's a "Homebrew system 'python'" (I know Homebrew does that with certain important programs that the Homebrew system depends on). That might very well confuse pip and other setup programs, since Homebrew likes to put stuff in places where you normally wouldn't find them to avoid conflicts (eg, multiple versions of Python). I can't be more specific about problems, and you'd hope that such stuff would "just work", but that might at least explain Mailman looking for stuff in "wrong places" (which might actually be right for Homebrew). Steve

4 years, 4 months

REST API for list owners/moderators

by Stephen J. Turnbull

mathias(a)koerber.org writes: > Does Mailman 3 have an REST API that allows list-owners/moderators > to perform list-management functions without having access to the > whole server/other lists etc? No. You can provide selective access to a selection of REST API endpoints via a front-end webserver such as Apache or nginx, but it would be rather painful, and possibly also rather insecure.[1] > The documentation seems to only indicate a single one-admin-user > REST API that should not even be accessible from outside? That's right. If the documentation only "indicates" that, we should fix the documentation. The point of separating Postorius from core was to put authentication and authorization in the hands of people who know how to do it (ie, Django). Footnotes: [1] That depends on what threats you're worried about. But the endpoint hierarchy is designed to make sense to application programmers, not to make it easy to disable access to "dangerous" endpoints that allow deleting lists or extracting user information.

1 year, 11 months

Mailman-users search results for query "Postorius"