Search results for "Postorius" - Mailman-users

Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 4:19 PM, Ken Alker wrote: > > What else is stored in /var/messages, if not archives? I see 4711 > messages in that directory (which I presume would be as many messages > are in the archive database). If there is a write-up on this, feel free > to point me to it. I found > <https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode…> but this isn't really answering my question. These are probably artifacts from your old Debian package. There have been issues in the past with handled messages not being removed from the message store. See https://gitlab.com/mailman/mailman/-/issues/257 This was fixed in 3.3.5 and the task runner implemented in 3.3.5 removes orphaned messages from the message store, but if they are still referenced in pendings they won't be deleted. > I didn't think so, but I'll certainly buy that. So, I'm assuming by > this you are implying that there is no helper function that needed to > run and the number of held messages should have dropped to zero > immediately upon a refresh of the web page? Correct, assuming your changes were committed. > So if I run the script, exist the shell, then come back in again, I > can't rely on the request.id being the same? I'd need to re-run the > script and get a new request.id? No. The request id for a given held message won't change. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: A new issue with installation

by Abhilash Raj

On Sat, Feb 20, 2021, at 9:28 AM, Abhilash Raj wrote: > > > On Sat, Feb 20, 2021, at 8:51 AM, Brian Carpenter wrote: > > As usual, a new issue has arisen with installing Mailman 3. It seems > > Postorius and Hyperkitty want to install a module called cryptography. > > Which I am unable to install because of this: > > > > error: Can not find Rust compiler > > You need to install a Rust compiler. Depending on which distro you are > using, you can run `sudo apt install rustc` or same command with `yum`. Also, it is possible depending on your distro that packaged Rust compiler is too old. cryptography requires a more recent version of Compiler, 1.45 is the min supported version I think. FAQ: https://cryptography.io/en/latest/faq.html#installing-cryptography-fails-wi… You can skip the Rust components by setting `CRYPTOGRAPHY_DONT_BUILD_RUST` but that would work just for this release and you won't be able to skip from the next release of cryptography. > > > > > Question 1: Is cryptography a new addition to Hyperkitty/Postorius? Or > > was cryptography always included and something else is different about > > my installation process? > > It was always included. The recent change has been in the underlying > security library to use Rust language in some parts of it. That has resulting > in 100s and 1000s of applications/CI and other stuff failing. The fix is quite > simple in most cases, just install rust compiler. > > > > > "Building wheels for collected packages: hyperkitty, django-haystack, > > django-mailman3, mailmanclient, robot-detection, rcssmin, > > django-allauth, cryptography" > > > > Question 2: Will Hyperkitty/Postorius work without cryptography? I > > haven't proceed with this installation once I received the above error. > > It is a transitive dependency for P/HK and is required by django-allauth. > I don't think you can skip it. > > > > > Question 3: Are there any Mailman 3/Postorius/HK documentation that > > addresses with the installation of cryptography? > > Since this issue arose about 2 weeks ago, there isn't anything there yet. > > > > > > > > > -- > > Brian Carpenter > > Harmonylists.com > > Emwd.com > > _______________________________________________ > > 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/ > > > > -- > thanks, > Abhilash Raj (maxking) -- thanks, Abhilash Raj (maxking)

4 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

7 years, 10 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>

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

3 years, 7 months

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 6 months

Re: Installed from Howto_Install_Mailman3_On_Debian10, web not quite working

by Volkmar Grote

On 07.05.23 23:13, Mark Sapiro wrote: > On 5/7/23 10:51, Volkmar Grote wrote: >> thanks for the quick reply. >> I am one step closer to a solution, >> "http://127.0.0.1:8000/postorius/lists/?all-lists#" seems to work now. >> I get the functionality, but it looks ugly w/o any graphics, for >> which I get yet another, slightly similar, error message: >>> >>> >>> Page not found (404) >>> >>> Request Method: GET >>> Request URL: >>> http://127.0.0.1:8000/static/postorius/img/mailman_logo_small_trans.png >>> >>> ... >> >> Nginx, /etc/nginx/conf.d/me.domain.de.conf >>> server { >>> listen 80; >>> listen [::]:80; >>> >>> server_name me.domain.de; >>> ... >>> location /static/ { >>> alias /opt/mailman/mm/static/; >>> } >> >> Again, many thanks in advance for any clue > > The above in nginx is correct, but you aren't getting the static files > via nginx. You need to go to a URL like > http://me.domain.de/postorius/lists/. Going to > http://127.0.0.1:8000/postorius/lists/ goes directly to your wsgi > server and doesn't involve nginx at all. You need to go to port 80 > where nginx is listening and nginx then proxys requests to > 127.0.0.1:8000. Do you also have > > location / { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > > } > > in /etc/nginx/conf.d/me.domain.de.conf. You need that. > Thanks, port :80 did the trick. In my old Mailman3 installation on an outdated Linux VM it runs on :8000. Life's good again :-) VGVG

2 years, 6 months

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

1 year, 10 months

[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

9 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.

6 years, 9 months

Mailman-users search results for query "Postorius"