Search results for "Postorius" - Mailman-users

Re: Emergency Moderation

by Mark Sapiro

On 5/24/20 10:59 AM, Allan Hansen wrote: > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ If you imported your MM 2.1 lists with `mailman import21`, `emergency` was set appropriately for the imported list and should be working to hold posts regardless of other settings. > My own current top-of-the-list issues: > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. Editing membership beyond what could be done via the admindb interface (i.e. clearing a moderated poster's mod flag) was never allowed for a moderator in MM 2.1. In MM 3, a moderator can set a member's moderation when handling a held post. Do you think a non-owner moderator should be able to make other changes to a member? > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're working on it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 11 months

Re: Converting discussion list to read-only list (settings)

by Paul Arenson

>allow_list_posts is the name of the attribute in Mailman core. It is >exposed in Postorius as "Include the list post header". I.e., they are >the same thing. Ok, thanks. >Note however that unless your users are using MUAs to reply by email and >their MUAs offer a "reply-list" function for replies to mailing list >posts, this setting will make no difference. It is the presence of the >List-Post: header in the message that allows the MUA to offer/process >the "reply-list" function. >Assuming MUA means a mail application. And if that mail application has no reply list function then the setting doesn't work. Uh-oh: I AM LOST AGAIN. (will all caps give me a larger font?) >It is the presence of the >List-Post: header in the message that allows the MUA to offer/process >the "reply-list" function. Ok, I asked how to make it ANNOUNCE ONLY and you said to use "allow_list_posts is False" which is the same as "Include the list post header". So does this mean that for a subset of users I cannot make it ANNOUNCE ONLY? And is it some other setting (send to moderator) that prevents it from being a DISCUSSION list?

6 years, 6 months

Re: UnicodeEncodeError: 'ascii' codec can't encode character

by Marvin Gülker

Hi, Am 13. Dezember 2019 um 17:10 Uhr -0800 schrieb Mark Sapiro: >key is the <message-id> of the request message >request_type is 1 for a held message >mailing_list_id is a numeric index into the mailinglist table > >The issue is there are still held message requests there for the >messages you removed. You need to delete those entries from the _request >table. Thank you again for your valuable help. I've now taken the easy route and ran DELETE FROM _requests WHERE request_type=1; , i.e. I cleared the entire held messages queue. As it turned out, there were no requests of any other type than type 1. I've deleted all remaining files below /var/lib/mailman3/messages as well (after seeing it was only spam anyway, this time non-broken spam, but still spam). Now, finally, I can go to the held messages queue in Postorius again without a 500 error. The list of held messages there is now empty, but this is obviously expected. Let's hope that disabling SMTPUTF8 prevents the problem from further occuring. In any case, I've asked a friend report the problem to the Ubuntu tracker: https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1856181 I'm back on track now. Thanks everyone! Marvin -- Blog: https://mg.guelker.eu

6 years, 4 months

Mailman3 migration and/or archiving problem

by hnpilot＠phnet.fi

I have installed a mailman3 server following this documentation: https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-inst… After a few hiccups I got mailman and postorius working and migrated one list according to this documentation: https://docs.mailman3.org/en/latest/migration.html It seemed to work and also hyperkitty_import was run without errors (or at least none shown up). Running update_index command said that there were 0 threads copied but I kjnow that the archive isn't empty. But now when I tried to open the list info page from lists view it dies with 500 error. After diving into the different log files I found an error message that it cannot find /etc/mailman3/mailman-hyperkitty.cfg. Great. Only that the cfg file exists and seems to my (unexpert) eyes correct. After that problem I tried to create a new list. Creation seemed to go all right but also with it, trying to open the list info page it shows 500 error. When googling for a solution I landed on a message stating that there might be double entries for the same list in listarchiver table but when I checked ot turns out that the table is empty! I am a bit confused how to figure out the base cause of the problem and would very much appreciate any pointers. wbr hank

1 year, 8 months

Re: Migration from 2.1 to 3

by Ryan Morash

I figured it out. It was a stupid mistake on my part, running the ‘mailman create’ commands as root… chown’ing the /var/lib/mailman3/lists directories to lists:lists solved the issues. From: Mark Sapiro <mark(a)msapiro.net> Date: Wednesday, January 8, 2020 at 1:20 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Migration from 2.1 to 3 On 1/8/20 6:38 AM, Ryan Morash wrote: > I'm running into the same issue, but after some troubleshooting I think the issue isn't with the import21 command. I'm running into the same issue when I create a list using 'mailman create' without importing anything. New lists created through Postorius work fine. Can you please post the `mailman create` command options you are using to create the list. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.mailman3.org%2fma… Confidential Transmission This correspondence is confidential and may contain privileged materials or information. It is intended for the use of the addressee only and all others are prohibited from copying or disseminating this message or its contents. If you have received this transmission in error, delete it immediately and notify the sender.

6 years, 4 months

Re: hyperkitty installation: Unclear instructions

by Mark Sapiro

On 1/5/23 15:00, Johannes Rohr wrote: > Dear all, > > I just installed mailman and mailman3-web in virtualenv as described in > https://docs.mailman3.org/en/latest/install/virtualenv.html > > Next I moved on to set up hyperkitty as described in > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html. I > got confused by the instructions: You are confused because you are mixing incompatible ways of installation. Installing mailman-web per https://docs.mailman3.org/en/latest/install/virtualenv.html#installing-web-… installs both HyperKitty an Postorius as dependencies of mailman-web. > But then, hyperkitty seems to be already have been pulled in by > mailman-web, looking at its dependencies. Yes. > If that's the case, then neither the instructions at > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html nor > those at > https://docs.mailman3.org/projects/hyperkitty/en/latest/development.html > are correct. They are correct, but they are for different methods of installation. > Can someone enlighten me on what the canonical way is of installing and > setting it up in virtualenv? Just follow the instructions at <https://docs.mailman3.org/en/latest/install/virtualenv.html>. They are the current recommendation and will result in a complete installation. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

nginx configuration on a multitasking server

by David Newman

Couple of questions about the sample nginx configuration given in the venv doc and the Mailman Mailman Suite Documentation v. 3.3 PDF: server { listen 443 ssl default_server; listen [::]:443 ssl default_server; server_name MY_SERVER_NAME; location /static/ { alias /opt/mailman/web/static/; } location / { proxy_pass 127.0.0.1:8000; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } ssl_certificate /path-to-ssl-certs/cert.pem; ssl_certificate_key /path-to-ssl-certs/privkey.pem; } 1. At least on my system, the proxy_pass statement will only run without errors if I change this to a fully formed URL, e.g., 'proxy_pass http://127.0.0.1:8000'. Is this a typo in the docs? 2. What document root(s) and alias(es) to use for Postorius and Hyperkitty and the Django admin on a server that also runs other services (e.g., Postfix for non-list mail and Roundcubemail)? With MM2, I use location statements with their own root and aliases: location /mailman { root /usr/lib/cgi-bin; fastcgi_split_path_info (^/mailman/[^/]+)(/.*)$; fastcgi_pass unix:///var/run/fcgiwrap.socket; include /etc/nginx/fastcgi_params; fastcgi_param SCRIPT_FILENAME \ $document_root$fastcgi_script_name; fastcgi_param PATH_INFO $fastcgi_path_info; } location /images/mailman { alias /var/lib/mailman/icons; } location /icons { alias /var/lib/mailman/icons; } location /pipermail { alias /var/lib/mailman/archives/public; autoindex on; } What is the MM3 equivalent way to do this? I think root would be somewhere under /opt/mailman but don't know exactly where, or which locations to point to. Many thanks! dn

4 years, 5 months

Guidance Request: Migrating Existing Mailman 3 Installation to Docker-Based Deployment

by Stephen J. Turnbull

Prasanth Nair writes: > I am currently running a Mailman 3 setup on a standalone server and > planning to migrate it to a Docker-based deployment using the official > Docker Mailman images. I would appreciate your guidance on the recommended > approach for this migration. docker-mailman is basically a hobby of the maintainer's. It's not even maintained in the GitLab project. As far as I know it's there because it's frequently requested and folks who run docker usually know what they're doing so it doesn't impose a particular burden on us. But really the only expert on docker-mailman is Abhilash himself. All three of the major Mailman suite applications (core, Postorius, and HyperKitty) use object-relation managers with automated schema updates. So contrary to Odhiambo's advice, I would try to replicate the versions of the Mailman components and PostgreSQL, then do upgrades in-place in Docker. Doing a database dump (in the current host) and restore (in the containerized PostgreSQL) is safe if you have the same schema on both hosts. (Upgrading the PostgreSQL version is much less risky but why tempt the software gremlins?) An alternative if you know PostgreSQL well would be to setup a "failover and failback" system, where you start with your current PostgreSQL as the primary and the container's as a replica, then when you're ready to go live you swap primary and replica for the database and point the DNS to the containerized Mailman. This probably involves less downtime (although in my experience PostgreSQL dump and restore is quite fast, and the Mailman databases for core and Postorius are small), but the big advantage is if you have a problem with the containers you can switch back right away. I know this works because I worked on a project where high availability was required, but another guy did the PostgreSQL work so I can't provide details. Networking is a FAQ for mailman-docker. I've only run it out of the box with all its defaults, and that worked fine. But somehow people have problems with it. My guess is that they're trying to fit the Mailman containers into some predetermined scheme, either a Docker host that hosts other containers and there are IP conflicts, or some organizational constraints. If you know what you're doing, no problem I think, but if you're newish to containers, you might want to set up docker on a host dedicated to Mailman. Other than that, I think Abhilash provided a preferred channel for discussing docker-mailman in the docs in his repo, that would be where to get your best (and more detailed) information. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

1 month

Re: Inaccessible User Profile

by Mark Sapiro

On 2/14/26 08:02, awingnut wrote: > I have a long time user that cannot access their profile. When I click > on users/members then that user as superuser, I get this error. > > Page not found > > This page either doesn't exist, or it moved somewhere else. It appears you may have an older version of the Users->members page cached in your browser or somewhere. > When I click that uers manage button, the page comes up but it says > there are no subscriptions. This user was subscribed as of couple of > days ago. Can this be fixed via admin functions? It appears the user was somehow unsubscribed. Unfortunately, Mailman's subscribe.log (by default part of mailman.log) is incomplete. See https://gitlab.com/mailman/mailman/-/issues/1143 This is fixed for the next release (3.3.11) but unless you've installed Mailman core from the head of the GitLab branch you don't have the fix. Even so, grepping Mailman's logs for the user's address may give a clue as to how the user was unsubscribed. To re-subscribe the user, you can use Postorius Mass operations->Mass subscribe or the command line `mailman addmembers`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 4 weeks

Re: Problem with list creation

by Abhilash Raj

On Thu, Sep 17, 2020, at 4:17 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > On 9/16/20 8:25 AM, Pawel Grzywaczewski wrote: > > > > We increased timeout in mailman.cfg > > This looks like the issue in Shashikanth's post, too: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > They are also creating more than 1000 lists. > > Do we know why these timeouts are happening? (Search for "list > creation times out" returns no results in either core or Postorius > issues.) This is the first time I am actually seeing this. I tried hammering a local server with default number of workers, 2, and created 5000 lists in a loop and went through pretty smooth. I am probably not replicating the exact situation, I am using the sqlite database (which I presumed would be slow and choke up faster but...it didn't). Creating list isn't one of the slow operations AFAIK, so I am actually surprised that it needs increasing timeout. It could be the interaction with database layer maybe, but I can't be sure without more debugging. > _______________________________________________ > 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)

5 years, 7 months

Mailman-users search results for query "Postorius"