Search results for "Postorius" - Mailman-users

Re: Renaming a server after building

by Mark Sapiro

On 11/26/21 1:46 AM, Philip Colmer wrote: > > However, although the above works, if I then go back to the *Mailman* > interface and go to /mailman3/domains/, the web interface recreates a > domain for the original domain name that was in place when the server was > created, i.e. we end up with "lists" and "new-lists". > > We've tried deleting that "new-lists" domain, rebooting and trying again > but "new-lists" keeps on being created again. > > What am I overlooking here? Is there a better/approved way to achieve what > we want to achieve? Each list has a mail_host attribute. this is not displayed in Postorius other than as the domain part of the list posting address which is displayed near the top of each page. Is this the new-lists.example.com domain? If so, you probably would need to change it. I think by having mailman domains like new-lists.example.com is asking for trouble. Why don't you set up Mailman on the new server(s) with domains like lists.example.com and just rely on DNS to get to the correct server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Re: Docker Support Sucks

by Allan Hansen

Hi Brian, You have been one of the good and generous people providing support. I hope i can repay a bit with this: These are one-line bash scripts I wrote after moving to MM3, so I could do things not yet in MM3, such as letting my moderators request a list’s members from me. I need one more script that will sync a text file to an existing list, deleting and adding as necessary. The scripts are for public use, reuse, misuse and overuse. I claim no rights and no responsibilities. mm3Members.bash #!/bin/bash # mm3Members # # Obtain a list of members of a given list # # Usage: # mm3Members.bash <listName> # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members $1 |grep -v -e "has no members"|sed -e 's/.*/\L&/‘ mm3ASddMembers.bash #!/bin/bash # mm3AddMembers # # Add members from a given list. # # Usage: # mm3AddMembers.bash <fileName> <listName> # <fileName>: text file with addresses to add. Same legal formats as in mass subscribe # # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --add $1 $2 mm3DeleteMembers.bash #!/bin/bash # mm3DeleteMembers # # Deletes members from a given list # <fileName> List of members to delete. Legal format the same a formats used for mass subscribes # # Usage: # mm3DeleteMembers.bash <fileName> <listName> # # Revisions: # # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # exec /opt/mailman/mm/venv/bin/mailman -C "/opt/mailman/mm/mailman.cfg" members --delete $1 $2 mm3MemberCount.bash #!/bin/bash # mm3MemberCount # # Obtain count of the members of a given list # # Usage: # mm3MemberCount.bash <listName> # # Revisions: # Date Name Reason for change # 28-Mar-2020 Allan Hansen Initial # /home/hansen/scripts/mm3Members.bash $1|wc Yours, Allan Hansen hansen(a)rc.org > On Jul 21, 2020, at 18:31 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > > On 7/21/20 8:55 PM, Mark Sapiro wrote: >> On 7/21/20 5:40 PM, Brian Carpenter wrote: >> >> Abhilash (@maxking) is one person and he has a $DayJob. We're all doing >> the best we can. > > Well, I still need support. > >> This is not a Docker issue per se. It is a consequence of upgrading >> Mailman core to 3.3.1+ and processing many old, stale, previously >> unprocessed bounces. See >> <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> > > I am not worried about the bounce issues at this point. I am just trying to get a membership list exported for a client. > >> >>> So, I want to totally move away from the use of Docker (mainly because I have found it buggy and the support is simply lacking) and install Mailman 3 for this client from source. However I need to get an export of their list members. But of course, I can't. Rest API times out and I don't know how to apply the instructions I was given to fix it and I don't have days to way for one. So please help. >>> >>> I increased the gunicorn workers to 4, hoping that would allow me to do the CSV export. No. So was given these instructions: >>> >>> ### >>> The issues seems to be due to timeout not due to high load. You want to increase the timeout for gunicorn and you can do that by specifying a gunicorn.ini config file: >>> >>> [webservice] >>> configuration: /path/to/gunicorn.cfg >>> >>> and then in the gunicorn.cfg you can add >>> >>> [gunicorn] >>> timeout = 90 >>> graceful_timeout = 30 >>> ### >>> >>> I applied the above changes to /opt/mailman/core/mailman-extra.cfg and created the gunicorn.cfg file. Restarted the docker container (mailman-core) and no access to Postorius due to no REST api. >>> >>> After restarting docker-mailman, I can't access Postorius due to the following error: >>> >>> ERROR 2020-07-20 20:16:27,351 15 postorius Mailman REST API not available >> Is Mailman core running? If not, whats in core's mailman.log as to why not? > > It looks like but no error message in mailman.log. However I noted that the gunicorn process did not start. > > This is with the configuration line enabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:25:17 2020 (22) in runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (25) out runner exiting. > Jul 22 01:25:17 2020 (21) command runner exiting. > Jul 22 01:25:17 2020 (22) in runner exiting. > Jul 22 01:25:17 2020 (24) nntp runner caught SIGTERM. Stopping. > Jul 22 01:25:17 2020 (24) nntp runner exiting. > [2020-07-22 01:25:19 +0000] [27] [INFO] Shutting down: Master > Jul 22 01:25:21 2020 (1) Master stopped > Jul 22 01:25:26 2020 (1) Master started > Jul 22 01:25:44 2020 (27) rest runner started. > Jul 22 01:25:44 2020 (26) pipeline runner started. > Jul 22 01:25:44 2020 (20) bounces runner started. > Jul 22 01:25:45 2020 (22) in runner started. > Jul 22 01:25:45 2020 (28) retry runner started. > Jul 22 01:25:46 2020 (29) virgin runner started. > Jul 22 01:25:46 2020 (25) out runner started. > Jul 22 01:25:46 2020 (23) lmtp runner started. > Jul 22 01:25:46 2020 (24) nntp runner started. > Jul 22 01:25:47 2020 (30) digest runner started. > Jul 22 01:25:47 2020 (19) archive runner started. > Jul 22 01:25:47 2020 (21) command runner started. > > This is with the configuration line disabled in mailman-extra.cfg: > > # docker-compose restart mailman-core > Restarting mailman-core ... done > [root@nicu-net docker-mailman]# tail -f /opt/mailman/core/var/logs/mailman.log > Jul 22 01:27:49 2020 (1) Master stopped > Jul 22 01:27:53 2020 (1) Master started > Jul 22 01:28:10 2020 (30) digest runner started. > Jul 22 01:28:10 2020 (29) virgin runner started. > Jul 22 01:28:10 2020 (24) nntp runner started. > Jul 22 01:28:10 2020 (25) out runner started. > Jul 22 01:28:10 2020 (22) in runner started. > Jul 22 01:28:11 2020 (28) retry runner started. > Jul 22 01:28:11 2020 (27) rest runner started. > [2020-07-22 01:28:11 +0000] [27] [INFO] Starting gunicorn 19.9.0 > [2020-07-22 01:28:11 +0000] [27] [INFO] Listening at: http://172.19.199.2:8001 (27) > [2020-07-22 01:28:11 +0000] [27] [INFO] Using worker: sync > [2020-07-22 01:28:11 +0000] [32] [INFO] Booting worker with pid: 32 > [2020-07-22 01:28:11 +0000] [33] [INFO] Booting worker with pid: 33 > [2020-07-22 01:28:11 +0000] [34] [INFO] Booting worker with pid: 34 > [2020-07-22 01:28:11 +0000] [35] [INFO] Booting worker with pid: 35 > Jul 22 01:28:11 2020 (19) archive runner started. > Jul 22 01:28:11 2020 (21) command runner started. > Jul 22 01:28:12 2020 (23) lmtp runner started. > Jul 22 01:28:12 2020 (20) bounces runner started. > Jul 22 01:28:12 2020 (26) pipeline runner started. > > -- > Please let me know if you need further assistance. > > Thank you for your business. We appreciate our clients. > Brian Carpenter > EMWD.com > > -- > EMWD's Knowledgebase: > https://clientarea.emwd.com/index.php/knowledgebase > > EMWD's Community Forums > http://discourse.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/

5 years

Re: Setting archive_policy "private" using REST changes web UI setting Archive policy, but does not hide archive until UI Save

by Mark Sapiro

On 8/14/24 01:15, Henrik Rasmussen wrote: > I am working on disabling a list removing all members using REST and then setting archive_policy to "private" also using REST. This changes the UI Archive policy setting to Private archives as I would expect, but I just discovered that the (now previous) member, still logged in, and alså public (not logged in), still have access to the archive. It is not browser cache. > > At the moment I click Save in the UI settings/archiving, both logged in user and not logged in user (other browser) changed to "This mailing list is private. You must be subscribed to view the archives." on page reload. > > It seems that i need to click Save on every list having been changed, before the archive is hidden. Is that a bug? The daily Django hyperkitty sync_mailman job will probably do it. Or, you can figure out what REST calls saving the settings in Postorius does and do that. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

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, 2 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?

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

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

11 months, 2 weeks

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.

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

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

3 years, 8 months

Mailman-users search results for query "Postorius"