Search results for "Postorius" - Mailman-users

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

4 years, 8 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

4 years, 8 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.

4 years, 8 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.

4 years, 8 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

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

4 years, 6 months

set a new default for max_message_size

by Paul Paulchen

Hi MM Community, I guess Mark can answer this question in a split second. We want another default than 40kb for the max_message_size. I know you can change it with the mailman shell or with postorius. But we want to skip this part an set the default to 4000kb for instance. I read about the max_message_size in this thread from 2020 https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… According to the answer of Mark you can change the "/usr/lib/python3/dist-packages/mailman/styles/base.py" - mlist.max_message_size. Now time went by, is there a possibility to use the mailman.cfg to set a new default? Cheers and thanks in advance!

4 years, 5 months

What's the difference between (purpose of) reject and ignore

by denis.bitouze＠univ-littoral.fr

Hi, at a page of the form .../postorius/lists/mylist/held_messages, it is possible to: - Accept - Reject - Ignore messages to be moderated. I didn't find any documentation about the difference between (the purpose of) “Reject” and “Ignore”. Since the list I'm currently moderating suffers from a lot of spammers, I wonder if there is a way to at the same time: - remove the spam from the moderation list (“Reject”? “Ignore”?), - add the emails from the removed spams to the list of banished emails (since copying-pasting each mail to be banished is a pain). Thanks in advance!

4 years, 3 months

Apache Configuration for Subdomain

by Mail Person

I'm trying to move my mailman3 web interface from example.com/mailman3 to just lists.example.com like this site. I am not having luck with the apache configuration. I've tried below but I just get a 403: <VirtualHost *:80> ServerAdmin admin(a)example.com ServerName lists.example.com ServerAlias www.lists.example.com <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /favicon.ico ! ProxyPass /static ! ProxyPass / unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> </VirtualHost> Alias /favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /static /var/lib/mailman3/web/static

4 years, 2 months

Re: Apache Configuration for Subdomain

by Mail Person

So adding the slashes did not fix, but I did get a workaround to work from the other thread: ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost Now makes it so that lists.example.com/mailman3 works sort of correctly. Weirdly enough, however, it redirects to lists.example.com/mailman/postorius/lists/ rather than */mailman3/* AND, if you go to lists.example.com/mailman it errors out with a 404 but redirects to lists.example.com/mailma So somehow a letter is getting deleted for some reason.

4 years, 1 month

Mailman-users search results for query "Postorius"