Search results for "Postorius" - Mailman-users

Re: Error while mass operation, no progress display while mass operation is running

by Mark Sapiro

On 2/6/25 04:53, Markus Grandpré wrote: > > At the University of Konstanz we have mailing list administrators who > frequently add and remove up to 10000 (and sometimes more) list members. > I have therefore tested the “Mass subscription” and “Mass removal” > operations and found that both the “Remove ALL members” operation and > the “Mass subscription” operation report an internal server error on the > website, but continue to run in the background until all new members > have been successfully added or deleted. The internal server error is probably due to the wsgi server timing out waiting for a response. See https://docs.gunicorn.org/en/stable/settings.html#timeout for Gunicorn or https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri for uWSGI > Unfortunately, I have not found > any error message in the log files. If you are using uWSGI, a harakiri timeout should be logged in uWSGI's log. > I also tested that mass operations > “Remove listed users” and “Remove Selected” ran successfully and without > any errors. You may want to increase the appropriate timeout and see if that helps. > Regardless of whether a mass operation process runs without errors or > continues to run despite an error, I find it hard that Postorius does > not display the progress of such a mass operation in order to monitor > the process, as mass operations with more than 1000 members are very > time-consuming. Perhaps this could be changed in a future version of > Postorius? This is a reasonable request. The best place for such a request is https://gitlab.com/mailman/postorius/-/issues/new Requests and suggestions on the mailing list, no matter how reasonable, get lost over time. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: Moderator e-mails only going out once a day

by Stephen J. Turnbull

jkoral(a)luc.edu writes: > -Mailman was installed using the virtual environment. > -Mailman info: > -I use systemd to stop and start the services. OK, this is all about as close to the environment most of the Mailman devs run as you can get. On the one hand, it's easiest for us to understand, but it also makes it more mysterious when something doesn't work ... "works for me", you know. > REST credentials: restadmin:restpass You should change this. It just makes it a little more annoying for someone unauthorized who gets access to port 8001, but it's very low cost to change. > -Virgin is running: > Note: Not sure how to check the queue, but when I run mailman3 > notify, the moderator e-mails get sent. Good. The queues are implemented with Python pickle files in the "queue" subtree, probably /opt/mailman/var/queue in your case, or maybe /opt/mailman/mm/var/queue if you use Mark's preferred setup. You're looking for .pck files in subdirectories of that directory which are older than about 5 minutes. I don't have a suggestion why the "notify immediately" option isn't working. Both the 'mailman notify' command and the 'notify immediately' option work the same way, by composing the notification and dropping it in the virgin queue. This should tell you the same thing that Postorius does, but you could try "su - mailman" followed by activating the virtual environment, then type mailman withlist -l list.with.problem and then m.admin_immed_notify expecting the response True according to your setting. If it comes up False, there's your problem but we need to figure out why that's different from what Postorius is telling you. You should be able to change it as well by typing m.admin_immed_notify = True commit() and exiting. Steve

1 year, 1 month

Re: Template - "You can use these variables in the templates" - The variable for "leave" is missing

by Mark Sapiro

On 11/4/23 06:28, Stephen J. Turnbull wrote: > Wikinaut writes: > > > fxied in merge request > > https://gitlab.com/mailman/postorius/-/merge_requests/852 > > I wish you wouldn't. It's just bloat in the code and in the > docstring. Better to document that the administrative addresses can > be constructed using ${short_listname}. I believe Mailman still > supports both "list-leave" and "list-unsubscribe", as well. Actually, https://gitlab.com/mailman/postorius/-/merge_requests/852 only added documentation of the existing $description replacement which is appropriate, but it duplicates part of https://gitlab.com/mailman/postorius/-/merge_requests/851 which does that and adds a bit more documentation. Also see https://gitlab.com/mailman/mailman/-/issues/1108 and https://gitlab.com/mailman/mailman/-/merge_requests/1153 -- 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: Held messages: Long time waiating for response of the Mailman API

by Stephen J. Turnbull

Krinetzki, Stephan writes: > Hi everyone, > > any news here? We are running with Pyton 3.6 - maybe a Python > Upgrade can speed Mailman up? It would help if you provide the original description. I see you're running Apache + uswgi. uwsgi has been pretty finicky, and most of the developers use gunicorn as the WSGI host. I suggest you ask on the uswgi channels as well. (I don't think that's a *better* place to ask, just a relevant place.) You wrote: > If we try to approve them via Postorius, the message is delivered > to the list immediately, but the success message in Postorius takes > a long time - on average the process hangs for three minutes until > the message is no longer displayed. You jump to the conclusion that the REST API is slow, but there's zero evidence to localize to the REST API. If your browser isn't running on the same host as the webserver it could even be some kind of network timeout (reverse DNS?) completely unrelated to Mailman (unlikely, but can't be ruled out with the information provided). 1. What is in the various logs? Mailman core, Django, your backend database, the webserver, the WSGI hosts all may be writing to logs, especially if there's some kind of time out or other error condition. 2. Are all the relevant components running on the same host? Are there other web services running under Apache and/or WSGI? 3. What are the relevant configurations (Apache, uswgi, gunicorn, Mailman, Postorius, Django, database, DNS A/AAAA/CNAME)? This would be anything like port numbers and host names or IP addresses, user names and passwords (we don't need to know these, but you should provide obfuscated versions so we can check syntax, and of course you should check for typos). Steve

4 years, 3 months

Re: Moderate mails from owner

by Malcolm Austen

On Thu, 21 Mar 2019 16:58:45 -0000, Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Thu, Mar 21, 2019, at 8:47 AM, Malcolm Austen wrote: >> On Wed, 20 Mar 2019 18:42:10 -0000, Mark Sapiro <mark(a)msapiro.net> >> wrote: >> >> > However, this is apparently not relevant because both the Member and >> > Non-Member actions are Hold. Thus, the post should be held unless it >> has >> > an Approved: header with the list's moderator_password attribute if >> > there is one, or it matches a Header filter rule with an accept >> action. >> >> At the risk of getting this really wrong - I have only limited MM3 >> knowledge - I will ask what is, I fancy, a closely related question ... >> >> My only experience of MM3 is with Ancestry's 'RootsWeb' installation. >> From >> the emails I can see a header "X-Mailman-Version: 3.1.0" but I can't >> find >> anything to identify Postorius which is the only interface I have to the >> system. >> >> From symptoms seen and described by others, I have deduced that the >> Postorius admin-per-user moderation options of "Default processing" and >> "List default" mean that a user may be set (by default on the rootsweb >> system!) to use the system default moderation settings rather than the >> list default settings. > > "Default Processing" means the default pipeline defined in Thanks, I will do some (more!) reading. > List > Settings > Alter Messages > 'Pipeline' ( in the bottom). This > pipeline is > system wide and is defined in source code, so it can't be customized by > site administrator. Unfortunately, that is not available to list-owners on the system concerned. Ancestry must have removed it. Malcolm. -- Malcolm Austen <malcolm.austen(a)weald.org.uk>

7 years, 1 month

Re: Reset bounce count in MM3

by Mark Sapiro

On 3/8/26 20:57, iMark wrote: > =========== > > My thinking was that to reset that member's bounce_count from 4 to 0, I > could just delete the records (resulting from the query) in the > "bounceevent". > > But as the query result only shows 2 bounces, I'm looking for where the > Admin web UI is getting "4" from (ie. the processed bounce events older > than 24 hours). The list member's bounce score is the bounce_score column in the member table, but finding the correct row is dificult because you need the list_id which you'd look up in the mailinglist table and either the address_id from the address table or the user_id from the user table. It's much easier to use mailman shell as in ``` $ mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> mbr = m.members.get_member('user(a)example.com') >>> mbr.bounce_score = 0 >>> commit() ``` But what is the point of doing this? If the member is bouncing, the score will continue to increment, and if not the bounces will become stale and a future bounce will set the score to 1. You mentioned reset_bounce.py, but that doesn't reset scores. It sets delivery enabled for users whose delivery is disabled by bounce, but you can do that, albiet one by one, in Postorius just by clicking the user in the membership list and setting Delivery Status to Enabled. In Postorius <=1.3.13, Delivery Status doesn't show in the membership list, but it will in the next release. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months

Mailman 3 Web Application Startup Time or Availability - 502 Bad Gateway and Postorius

by summersan＠nclack.k12.or.us

Hello, I've been setting up a new Mailman 3 installation earlier this year, and I think things have been going okay so far. I've noticed, however, that after a long amount of time passes (for example, a weekend), when I try to visit the local Mailman 3 web application (e.g., example.mailman.site/mailman3/lists/, where it says "Postorius" at the top left corner of the page and shows a list of mailing lists in the body of the page), I sometimes get a 502 Bad Gateway type of error (referenced from my notes). As far as I can tell, this looks like a normal web server (nginx?) error. If I try visiting the Mailman 3 server location again in a web browser shortly thereafter, I still might get a 502 Bad Gateway error. If I wait a while longer (maybe a minute or more?), the Mailman 3 web application appears to load as expected. I've tried looking at the gunicorn documentation (https://docs.gunicorn.org/en/stable/index.html) and searching online (including in this Mailman3 mailing list) to see if there's something that can be done to fix this issue. The closest thing I can find for now is advice for something that, while possibly being technologically unrelated, includes the idea of "warmup requests", which makes me think of simply setting up some sort of script to periodically load a page on the Mailman 3 web application in order to keep it more available for visitors (https://stackoverflow.com/a/57056170) Is there a setting or something in any of the Mailman 3 related programs that could help with keeping the Mailman 3 web application up and running more often without having to resort to making an ongoing, automated request to the Mailman 3 web application? Thank you. * Note: "Mailman 3" terminology is referenced from this page: https://lists.mailman3.org/archives/

5 years

Re: Error -- postorius Un-handled exception

by Mark

> On Sat, Jan 27, 2024 at 8:17 AM Mark <imark(a)posteo.net> wrote: >> 3. For the user "mailman" to access the databases I needed to change >> the >> owner to mailman (even though all privileges has been granted) ... ------------------------------------------------------------------------------------------------------- On 2024-01-27 18:51, Odhiambo Washington wrote: > > 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… > > I have never needed to do `psql -d mailman -U mailman -W`. > I used the steps documented above to enable mailman user to write to > the > database. > > postgres=# \c mailmanweb postgres > You are now connected to database "mailmanweb" as user "postgres". > mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; > GRANT > mailmanweb=# \c mailman postgres > You are now connected to database "mailman" as user "postgres". > mailmanweb=# GRANT ALL ON SCHEMA public TO mailman; > GRANT > > TBH, I am not sure which method is the best although I think this > option is > :) > ------------------------------------------------------------------------------------------------------- Thanks for the heads up on that blog Odhiambo. Agreed. it is a better way of doing it. --- SNIP --- In PostgreSQL 14 and in prior versions, by default anybody can create a table. The new table will simply end up in the PUBLIC schema. The problem with this approach is that the public schema can quickly turn into a trash can containing all kinds of used and unused tables – which is neither desirable nor recommended. An even bigger problem is security: almost any privilege escalation attack on a PostgreSQL database requires the attacker to create malicious objects. ... The public schema is the perfect vector for such a privilege escalation attack. Therefore PostgreSQL has made a major leap forward and changed this behavior. In version 15, only the database owner can create objects in the public schema. ---

2 years, 3 months

Re: Templates

by Mark Sapiro

On 11/17/20 1:23 AM, Odhiambo Washington wrote: > On Tue, 17 Nov 2020 at 06:09, Mark Sapiro <mark(a)msapiro.net> wrote: > >> >> How did you create this footer?. If you created it by creating a file in >> Mailman's var/templates directiory, can Mailman read it? >> >> > I went into Postorius and selected the list. It's the only one. > Selected Templates -> New Template. And previously > requests.exceptions.HTTPError: 404 Client Error: Not Found for url: > http://localhost:8000/mm3/mailman3/api/templates/list/kictanet-2.lists.kict… ... > Message: 'Cannot retrieve template at > http://localhost:8000/mm3/mailman3/api/templates/list/kictanet-2.lists.kict… > (<no authorization>)' This is Mailman core trying to get the template from Postorius. What happens if you try to get that URL in a browser? What if you try your domain instead of localhost:8000? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: list footer web customization procedure

by Mark Sapiro

On 11/30/21 1:11 AM, Stephen J. Turnbull wrote: > > Does Django empty out the "spacetebasket" if it's all white space, or > does spurious whitespace in that box lead to an (apparently) empty > footer being added? Postorius used to remove leading and trailing whitespace from the template, but not since https://gitlab.com/mailman/postorius/-/issues/301 was fixed. > Anway, I recommend to the OP that they make sure there's no whitespace > in the Data box. A good recommendation. While a header or footer template with some whitespace might not be noticeable when added to a text/plain message, it will cause extra mime parts to be added to more complex messages. Also, if the goal in setting an empty footer is to avoid breaking a DKIM signature, even adding a bit of whitespace to a text/plain message is an issue. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 5 months

Mailman-users search results for query "Postorius"