Search results for "Postorius" - Mailman-users

remove non members from a list

by Guillermo Hernandez (Oldno7)

Hi all: I need to remove all non members from a list. I know I can do it via Postorius, but it has to be done one at a time. (you can delete ALL suscribers but not all non members...) Anyone has a python recipe to do this? I've been searching and googling but I cannot find the way of doing it safely. And via DDBB there are more than one table involved and I'd rather not mess it all... Thanks in advance

4 years, 2 months

Re: django request error

by eggert＠eehmke.de

What's strange, my mailman-web is referred to by https://lists.tdl/mailman3/ this show the message as above: This page either doesn't exist, or it moved somewhere else. The links in that page refer to urls like: https://lists.tld/mailman/postorius/lists/ This URL does not exist, of course. Where is the mailman3 replaced by mailman? All my config files refer to mailman3.

4 years

Bulk update of members' moderation settings

by Alex King

I imported a list from mailman 2.1 using https://docs.mailman3.org/en/latest/migration.html. It happens that emergency moderation was set on the mailman 2.1 list, and this has resulted in all members having Moderation set to Hold. I now want to change that to Default Processing for all members. Is there a way to achieve that in bulk without clicking through the members options for each member in Postorius? Thanks, Alex

3 years, 11 months

Re-enable member after bouce processed disable

by Henrik Rasmussen

Recently I upgraded Mailman to GNU Mailman 3.3.4 (Tom Sawyer) (Postorius: 1.3.5 and HyperKitty: 1.3.4) which is now processing bounces. When a member have been disabled due to bounces, how is the member re-enabled? I would guess it would be under the "Users -> Members -> Member options -> Delivery status", but theses are both (Enabled and disabled) unchecked, not indicating whether or not the member is either or. How do I or the list admins re-enable a bounce-disabled member? Regards, Henrik

3 years, 10 months

REST API authorization failed

by Axel Rau

Hi all, I’m going to do a mailman2->3 migration in a FreeBSD jail. I installed mailman3 in an venv from pypi, along with nginx, uwsgi and exim. The above error happens when I try to open the base url of my server with a browser (is redirected to postorius/lists/) (no errors on admin/ and hyperkitty urls) Same passwords and users in mailman.cfg: [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: ??? and in settings.py: MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = ??? Its a long password, created as secret key by manage.py Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius

3 years, 9 months

Re: under which uid should uwsgi/manage.py run?

by Mark Sapiro

On 1/14/22 2:44 AM, Axel Rau wrote: > What is the recommended setting? All Mailman processes including Mailman core's runners and all Postorius, HyperKitty Django processes and Django management commands should run as the Mailman user. If things have been run as another user, particularly root, some files or directories may have been created that are not accessible by the Mailman user. This should be fixed by adjusting the ownership of those things. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Re: under which uid should uwsgi/manage.py run?

by Axel Rau

> Am 14.01.2022 um 18:11 schrieb Mark Sapiro <mark(a)msapiro.net>: > > All Mailman processes including Mailman core's runners and all Postorius, HyperKitty Django processes and Django management commands should run as the Mailman user. Including the uwagi processes ? I.e. uid=mailman gid=mailman in uwsgi.ini ? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 9 months

POSTORIUS_TEMPLATE_BASE_URL setting with unix socket

by Axel Rau

> Am 18.01.2022 um 13:20 schrieb Axel Rau <Axel.Rau(a)chaos1.de>: > > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock <unix:///tmp/uwsgi.sock>; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - How would I configure POSTORIUS_TEMPLATE_BASE_URL with this nginx config? Axel --- PGP-Key: CDE74120 ☀ computing @ chaos claudius ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Replaced multipart/alternative part with first alternative.

3 years, 9 months

sending messages in response to posts from non-members

by David Bremner

I'd like to turn off the "bounce messages" sent by mailman to non-members. My reasoning is that most such posts are spammers, and often use forged return-paths / From's, so I end of sending steady stream of backscatter to amazon.com etc... Is this configurable (without postorius) somehow? d

3 years, 8 months

Re: Delete user

by Mark Sapiro

On 3/14/22 09:10, Rainer Herbst wrote: > > But one problem remais open - how can I delete a user alltogether, i.e. > including his subscription and account data from the database? This is currently being worked on. See https://gitlab.com/mailman/postorius/-/issues/543 In the mean time, see this thread: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Mailman-users search results for query "Postorius"