Search results for "Postorius" - Mailman-users

Mailman 3 install questions: HAYSTACK_CONNECTIONS

by heller＠deepsoft.com

I am using the debian 12 repo versions of mailman3, django, posterious, hyperkitty, and xapian: sharky5% dpkg-query -l python3-{django,django-mailman3,django-hyperkitty,django-postorius,xapian} mailman3\* | grep '^ii' ii mailman3 3.3.8-2~deb12u2 all Mailing list management system ii mailman3-doc 3.3.8-2~deb12u2 all Mailing list management system documentation ii mailman3-web 0+20200530-2.1 all Django project integrating Mailman3 Postorius and HyperKitty ii python3-django 3:3.2.19-1+deb12u1 all High-level Python web development framework ii python3-django-hyperkitty 1.3.7-1 all Web user interface to access GNU Mailman3 archives ii python3-django-mailman3 1.3.9-1 all Django library to help interaction with Mailman3 (Python 3 version) ii python3-django-postorius 1.3.8-3 all Web user interface to access GNU Mailman3 ii python3-xapian 1.4.22-1 amd64 Xapian search engine interface for Python3 Before adding the HAYSTACK_CONNECTIONS options, I have this: sharky5% sudo mailman-web haystack_info --no-color --skip-checks Number of handled 1 index(es). - Model: Email by Index: <hyperkitty.search_indexes.EmailIndex object at 0x7fd0de1b0470> When I add this to /etc/mailman3/maymail_web.py (adapted from the section titled: "Setting up Fulltext search (xapian)" on https://docs.mailman3.org/en/latest/install/virtualenv.html#set-up-xapian HAYSTACK_CONNECTIONS = { 'default': { 'PATH': "/var/lib/mailman3/web/fulltext_index", 'ENGINE': 'xapian_backend.XapianEngine' }, } I get: File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "<frozen importlib._bootstrap>", line 1206, in _gcd_import File "<frozen importlib._bootstrap>", line 1178, in _find_and_load File "<frozen importlib._bootstrap>", line 1142, in _find_and_load_unlocked ModuleNotFoundError: No module named 'xapian_backend' So, do I use Xapian or not? Is something missing somewhere? Is this a documentation bug or something else? -- Robert Heller -- Cell: 413-658-7953 GV: 978-633-5364 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 year, 6 months

Re: More Mailman releases!

by Wikinaut

before upgrade (half-way upgrade works → thus: Postorius Version 1.3.10 ; GNU Mailman 3.3.9 (Tom Sawyer) works; the problem pops up when upgrading hyperkitty/mailman-web): https://mydomain/mailman3/lists/mylist.mydomain/ => works https://mydomain/postorius/lists/mylist.mydomain/ => does not work (404 not found) apache2: <VirtualHost *:443> ServerAdmin webmaster@localhost DocumentRoot /var/www/html ServerName mydomain Alias /static "/opt/mailman/web/static" <Directory "/opt/mailman/web/static"> Require all granted </Directory> <IfModule mod_headers.c> RequestHeader unset X-Forwarded-Proto <If "%{HTTPS} =~ /on/"> RequestHeader set X-Forwarded-Proto "https" </If> </IfModule> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/archives" "http://127.0.0.1:8000/archives" ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/admin" "http://127.0.0.1:8000/admin" ProxyPass "/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> Include /etc/letsencrypt/options-ssl-apache.conf SSLCertificateFile /etc/letsencrypt/live/mydomain/fullchain.pem SSLCertificateKeyFile /etc/letsencrypt/live/mydomain/privkey.pem </VirtualHost>

2 years, 2 months

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, 6 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, 11 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, 11 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, 5 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, 8 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, 8 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, 8 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, 11 months

Mailman-users search results for query "Postorius"