Search results for "Postorius" - Mailman-users

Re: Error -- postorius Un-handled exception

by Stephen J. Turnbull

Odhiambo Washington writes: > The issue you're dealing with in that case is this change in > PostgreSQL-15 discussed in this blog: > https://www.cybertec-postgresql.com/en/error-permission-denied-schema-publi… Thank you for the reference! If you have a Mailman-only host, with a Mailman-only PostgreSQL, or The Cabal of equally responsible maintainers are the only people who work on the Postgres cluster, the two approaches are basically equivalent. My take is that the default "right thing" is to transfer ownership of the 'mailman' database to the 'mailman' user, and use "GRANT ALL ON SCHEMA public TO fred" in the case that you don't want to give "sudo mailman" to Fred. Rationale: I believe there are a number of things that the 'postgres' user can do that other users cannot, and you probably don't want random contractors or new volunteers to have those privileges. On the principlee that 'postgres' should only do those things that only 'postgres' can do, you want to make the 'mailman' user the owner of the 'mailman' database (and 'mailmanweb' too if you go that route). Then if you have a user 'fred' who may be working on both mailman and non-mailman databases in a session, then instead of giving sudo mailman to Fred, 'mailman' can grant all on schema public in mailman to 'fred'. It's a really fine difference, and probably will matter to almost nobody running Mailman 3. I do think user 'mailman' owns the 'mailman' database is conceptually simpler than user 'postgres owns the 'mailman' database and 'mailman' has ALL privilege on the PUBLIC schema Right? Steve

2 years, 9 months

Re: Where is postorius.wsgi?

by Peter Münster

On Fri, Jan 26 2018, Simon Hanna wrote: >> from email.message import EmailMessage >> ImportError: cannot import name EmailMessage > > You appear to be using a prerelease version of django-mailman3 which is not > compatible with the other parts. Install an earlier version and it should > work. Hi, I did not install it. I guess, it has been installed automatically by the command "pip2 install -r requirements.txt" or similar. Anyway, with my patch (EmailMessage -> Message) it works. I just needed to fiddle about some dependency issues. These commands were needed in the end: pip2 install djangorestframework==3.7.3 pip2 install cryptography==1.8.2 pip2 install pyOpenSSL==16.2.0 > You also appeared to have used Python3 for the frontend in earlier > posts. Yes, first I tried it, but now I use Python2 for any Django related things (HyperKitty and Postorius). Kind regards, -- Peter

8 years, 9 months

Re: Apache Configuration for Subdomain

by Mail Person

Ok, progress with tinkering some. Using the below configuration I can manually navigate to lists.example.com/mailman3/postorius/lists/ and all is working fine. If I go to lists.example.com/mailman3 it for some reason redirects to lists.example.com/mailman/postorius/lists/ which generates a 404. Going to lists.example.com also hits a 404. So closer, but not perfect. Any ideas? The current, sort of working config: <VirtualHost *:80> ServerAdmin admin(a)example.com ServerName lists.example.com ServerAlias www.lists.example.com Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost </IfModule> RewriteEngine on RewriteCond %{SERVER_NAME} =lists.example.com [OR] RewriteCond %{SERVER_NAME} =www.lists.example.com RewriteRule ^ https://%%7BSERVER_NAME%7D%%7BREQUEST_URI%7D [END,NE,R=permanent] </VirtualHost>

4 years, 3 months

Re: How to upgrade to 3.10

by Mark Sapiro

On 3/4/26 16:11, Paul Tomblin via Mailman-users wrote: > > > On Tue, Mar 3, 2026, at 4:31 PM, Mark Sapiro wrote: > >> pip install git+https://gitlab.com/mailman/mailman@master >> ``` >> That version is compatible with Python 3.13. > > Ok, that works. Now what do I need to do to get base_url and the dependent template text variables set? Is it just the same with mailman-web@master ? Updating mailman-web from gitlab won't do it because you need to update postorius and mailman-client from gitlab and an update of mailman-web will pull those from PyPI. You need to do ``` pip install git+https://gitlab.com/mailman/mailman-client@master pip install git+https://gitlab.com/mailman/postorius@master ``` -- 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

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

by Mark Sapiro

On 5/12/16 9:16 AM, deu8yz2mpq(a)snkmail.com wrote: > Digest delivery in mailman 2 encapsulated the individual message/rfc822 messages in a multipart/digest container. This allowed email clients to show the messages in the particular digest in a threaded view. This format vs. plain text digests was a user option in Mailman 2. > It seems like the various digest options that I have tried [1] in mailman 3.1.0 (as implemented for the fedora-users mailing list) no longer encapsulate messages in multipart/digest. The core still supports the same plain text and MIME format digests and the same individual subscriber and per-list default formats as did Mailman 2. The issue is none of these things are exposed in Postorius. If you subscribe to digests on this list, you will receive the 'encapsulated' MIME format because the lists mime_is_default_digest setting is True, but currently that has to be set through the bin/mailman shell tool. > Is this intentional? Is it a bug - feature that was lost in translation from 2 to 3? Is there a delivery option I'm missing that will turn that back on? 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. You can do it via bin/mailman shell if you have access and know what you're doing (see <http://mailman.readthedocs.io/en/release-3.0/src/mailman/runners/docs/diges…>) If you file an issue at <https://gitlab.com/mailman/postorius/issues/new>, it might help expedite this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 6 months

Templates do not work

by Stephen J. Turnbull

Eggert Ehmke writes: > When I look into mailman/mm/var/templates the directory is empty. > Nevertheless, the templates I create in Postorius seem to be stored > (where?), That is expected when you create templates in Postorius, because they are stored in the RDBMS (eg, PostgreSQL). > they just do not work. My first guess would be that there's a language mismatch. You need to create a variant template for each language that is used. I'm not sure offhand how the system chooses the language for stored templates vs the language for templates used for messages (I suspect the used template is the one for the list's default language), but an incomplete set of variant templates and a mismatch between the language the variant template was created in and the default language of the list is what I would guess. Steve

4 years, 6 months

Re: Turn off social logins?

by Stephen J. Turnbull

Nick Wynja writes: > INSTALLED_APPS = [a for a in INSTALLED_APPS > if not a.startswith('allauth.socialaccount.providers') > and not a.startswith('django_mailman3.lib.auth.fedora')] > This way if Postorius ever adds any apps you won't need to update > your local settings. Anyone see any downsides to doing it this way? Aside from the circular import issue mentioned by Abhilash 1) AIUI, the OP didn't want to present options to users that they don't need and might confuse/annoy them. This does the wrong thing for the OP if so. 2) Implicitly adding apps in this way increases the attack surface on the system by allowing additional opportunities to access resources.[1] This approach doesn't even necessarily get rid of all social authentication providers: others may be special-cased in the same way as Fedora in the future. Of course, the default configuration in the containers will be good for a very common use case, and sufficiently secure for most instances. But the general rule for Internet-facing applications is "shut off all access by default, and explicitly open up only the channels you need." I'm not saying your "subtract the social authentication applications" has a downside in all cases. Just that some of us prefer to expend the effort to (a) follow that general rule, and (b) advise others of its existence :-). Footnotes: [1] You're right, the admin has to intervene if Mailman adds new "must-install" apps, or Postorius won't run. It's possible we should do something about this, such as dividing the set of apps into those we are sure Mailman needs and and having the user configure only those that provide more or less optional features that users should make their own decisions about.

7 years, 9 months

Re: templates

by Odhiambo Washington

They're in the DB. On Thu, May 4, 2023, 20:33 Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > I'm having issues with my lists. For each list I have created a template [ > list:user:action:subscribe ]which has a prospective subscriber have to > consent to list rules before they are subscribed. This template I created > is > listed in Postorius for each list. I have noticed that there are no other > templates listed in Postorius. Furthermore, there is no 'lists' > subdirectory under Mailman's var/templates/. > > > > Help (please)! > > > > _______________________________________________ > 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 odhiambo(a)gmail.com >

3 years, 6 months

Re: Filter who can send on mailman3 list?

by Marcus Granath

Mark Sapiro wrote: > > As Ruth said in her reply at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > in Postorius, go to the Users dropdown and select Non-Members. On that > page there is a form to enter Email Address and Display Name with an Add > nonmember button. Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? Maybe then I need to try contact our mailman server admin, or? Or any other way for me as just an mailman-list admin to add this "Non-Member"?.... ;-)

5 years, 7 months

Re: Help with installing Postorius and Hyperkitty on Ubuntu 19

by Mark Sapiro

On 6/8/19 4:04 AM, Andrew Bernard wrote: > > Where is the Django config area for the > pip installed modules? It is this that I find obscure. The short answer is wherever you put it. If you look at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience> which Abhilash mentioned, you'll see what I do. Abhilash mentioned creating the virtualenv in /opt/mailman/. I actually have another level below that, /opt/mailman/mm/, but this is only for convenience to separate things as I also have directories for the git branches and for local patches, so if we are just working with /opt/mailman/, you can put your Django settings.py and settings_local.py files there. I also put various other config things there like Mailman's var/ directory Django's static/ directory mailman.cfg mailman-hyperkitty.cfg gunicorn.conf and an empty __init__.py file so Django can import settings. Then I create a /opt/mailman/bin/ directory and in that I put small bash scripts to run things. for example: opt/mailman/bin/mailman contains #!/bin/bash unset PYTHONSTARTUP exec /opt/mailman/venv/bin/mailman \ -C "/opt/mailman/mm/mailman.cfg" \ $@ opt/mailman/bin/django-admin contains #!/bin/bash . /opt/mailman/venv/bin/activate cd /opt/mailman/ export PYTHONPATH=/opt/mailman/ export DJANGO_SETTINGS_MODULE=settings django-admin $@ and opt/mailman/bin/gunicorn contains #!/opt/mailman/venv/bin/python import sys sys.path[0:0] = [ '/opt/mailman/', ] import os os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' import gunicorn.app.wsgiapp if __name__ == '__main__': sys.exit(gunicorn.app.wsgiapp.run()) Then I use those commands to run Mailman, Django and gunicorn. Some of this may not be directly applicable to you, but I hope it gives you the basic idea. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 months

Mailman-users search results for query "Postorius"