Search results for "Postorius" - Mailman-users

Re: Domain admin

by Mark Sapiro

On 04/24/2018 11:57 PM, Johannes Winter wrote: > > We would like to give our users the priviledge to create lists per > domain. I Haven't found any options for that in the web interface. > > Is this possible somehow with mailman3? It is not currently possible. From the point of view of Mailman Core, anyone who can run the 'mailman' command or access the REST API can create domains and lists. Postorius could support this in some way and could maintain it's own 'authorized users' data, but it would be better to also add some concept of domain admin to core. These would be significant changes. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: django fake users

by Brian Carpenter

On 1/17/21 6:24 AM, Andrew Hodgson wrote: > I don't think this would help the issue. What I am seeing here is users signing up through Postorius using the sign up option which then creates an account in Django (but not Mailman). Yesterday alone I had over 700 of these accounts created. I don't know whether they pass email confirmation or not (I don't see this in Django admin), however they don't get added as users in Mailman and they don't attempt to subscribe to any list. You can select "Email Addresses" in Django. On the "Email Addresses" page, select No under the By verified heading in the FILTER box. There you should see a list of unverified email/users. -- Brian Carpenter Harmonylists.com Emwd.com

4 years, 10 months

New domain cannot set set host

by Alain D D Williams

I have created a new domain - via postorius I want to set the 'Web Host' to be the same as the new domain but I cannot see that domain in the drop down list. Even if I save it and then edit the domain I still cannot see it. I went into mailman3-web/settings.py and added it to ALLOWED_HOSTS - no joy. I can see the domain in table mailman3.domain and mailman3web.django_mailman3_maildomain But it is not in table mailman3web.django_site Please how do I do this ? Thanks -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year

Re: Moderator e-mails only going out once a day

by jkoral＠luc.edu

-Mailman was installed using the virtual environment. -Mailman info: GNU Mailman 3.3.9 (Tom Sawyer) Python 3.12.3 (main, Feb 4 2025, 14:48:35) [GCC 13.3.0] config file: /etc/mailman3/mailman.cfg db url: postgresql://mailman:PasswordBlanked@localhost/mailman devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass -I use systemd to stop and start the services. -Virgin is running: mailman 2041324 0.0 1.1 118832 91972 ? S Mar24 0:29 /opt/mailman/venv/bin/python3 /opt/mailman/venv/bin/runner -C /etc/mailman3/mailman.cfg --runner=virgin:0:1 mailman 2897963 0.0 0.0 6544 2304 pts/1 S+ 14:51 0:00 grep virgin Note: Not sure how to check the queue, but when I run mailman3 notify, the moderator e-mails get sent. -Versions: Mailman 3.3.9 Postorius Version 1.3.10 HyperKitty version 1.3.9 Postfix = 3.8.6 Django version = 4.2.13

8 months, 2 weeks

Re: Installing mailman 3

by Rafael Mora

DEBUG var True: [02/Aug/2017 16:43:42] "GET /postorius/lists/ HTTP/1.1" 200 3645 [02/Aug/2017 16:43:48] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10950 [02/Aug/2017 16:43:49] "GET /static/CACHE/css/hyperkitty.2f591b4e31fe.css HTTP/1.1" 200 156657 DEBUG var False: [02/Aug/2017 16:46:46] "GET /accounts/login/?next=/postorius/lists/ HTTP/1.1" 200 10001 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/css/d6cbfc945441.css HTTP/1.1" 404 107 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 [02/Aug/2017 16:46:46] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" 404 105 El mié., 2 ago. 2017 a las 10:56, Mark Sapiro (<mark(a)msapiro.net>) escribió: > On 08/02/2017 07:55 AM, Rafael Mora wrote: > > HyperKitty is looking for some files in /static/CACHE/... but it doesn't > > find them: > > > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/b3547a2ab51b.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/4c17bb8058aa.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/css/2fa1cba00450.css HTTP/1.1" > > 404 107 > > [02/Aug/2017 14:53:38] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > [02/Aug/2017 14:53:39] "GET /static/CACHE/js/4ce1260ef558.js HTTP/1.1" > 404 > > 105 > > > > > > Should I run any command to activate the CACHE dir? > > > You need to ensure you have a working sass compiler. As I said at > < > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > >, > See the third bullet under > <http://docs.list.org/en/latest/prodsetup.html#dependencies>. > > Then you need to run commands like > > django-admin collectstatic --clear > django-admin compress > > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 4 months

Re: Heads up: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated

by Andreas Vetter

I created a new issue: https://gitlab.com/mailman/mailman-web/-/issues/35 On Freitag, 7. Februar 2025 12:19:22 CET Andreas Vetter wrote: > Hello, > I have a venv installation of: > mailman postorius django-mailman3 hyperkitty mailman-web > I just did a > pip install -U --upgrade-strategy eager > > When running > mailman-web runjobs -l > I get the following Warning: > System check identified some issues: > > WARNINGS: > ?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: > settings.ACCOUNT_LOGIN_METHODS = {'email', 'username'} > > I guess this is from allauth (version django-allauth-65.4.1). > > Changing ACCOUNT_AUTHENTICATION_METHOD to ACCOUNT_LOGIN_METHODS in > /etc/mailman3/settings.py is not enough. One has to edit > venv/lib/python3.11/site-packages/mailman_web/settings/mailman.py -- Mit freundlichen Gruessen, Andreas Vetter

10 months

Re: Message Personalization: embed User name in header/footer

by Mark Sapiro

On 05/06/2018 11:30 PM, Johannes Winter wrote: > Am Sun, 6 May 2018 07:26:45 -0700 > schrieb Mark Sapiro <mark(a)msapiro.net>: >> >> We're working on getting template editing in Postorius for release >> later this month. >> > > Cool! I hope you also fix this issue > https://gitlab.com/mailman/mailman/issues/409 while doing do? The two things are related only in that they both involve templates which is not to say that we won't come up with something for https://gitlab.com/mailman/mailman/issues/409 but only that they aren't a "package". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

Re: Python 3.9 support

by dancab＠caltech.edu

Thanks for your help Mark. We use AWS RDS for MySQL. I found there was an automated update applied by AWS around the time show in the logs for the error. Feb 23 23:27:10 2022 (300) Uncaught runner exception: (pymysql.err.OperationalError) (1053, 'Server shutdown in progress') The outage lasted for about 1 minute. We have Mulit-AZ failover configured for RDS and a new DB instance started within that minute. What is interesting is that Hyperkitty archiving continued to work and Postorius was still responsive. Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Thanks again. -- Dan

3 years, 9 months

Update a member's display_name

by Nick Wynja

Hi all, I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck. I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change. The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet. I'd appreciate any help pointing in the right direction. Thanks, Nick

6 years, 10 months

Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

The concept of a Django user sounds like the big thing I was missing. Thank you; I believe I have resolved the immediate need. I'm thinking, then, that if I want to be able to programmatically create the Django users in parallel with our Mailman users (I don't want to have registration open to the world), I'm going to have to do some coding... either create some sort of Postorius API or perhaps better would be to make a social / OAuth plug-in that will use our existing membership site. (Once I get stuck on that, I'll switch to the developer list.) Thanks again.

3 years, 10 months

Mailman-users search results for query "Postorius"