Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: Confirmation emails aren't sent to users.

by Ibiam Chihurumnaya

Mark Sapiro wrote: > On 2/14/26 01:04, Stephen J. Turnbull wrote: > > mailman-web diffsettings also works. (As far as I know > > mailman-web is effectively an alias for django-admin.) > > Actually, in our recommended virtualenv install mailman-web is preferred > because django-admin doesn't load /etc/mailman3/settings.py by default. > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan I mostly use mailman-web for this reason.

8 months

[MM3-users] Re: Opinions wanted.

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/8/26 10:18, Stephen J. Turnbull wrote: > > Mark Sapiro writes: > > > > > How significant an issue do you think that is? > > > > Very, if you have 20K lists. > > That's not the issue I was asking about. That issue is if the > selection The point is a user story where it was important to be able to narrow the window conveniently. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

7 months, 1 week

[MM3-users] Re: LTMP to Postfix problem

by Mark Sapiro

On 6/18/20 5:38 PM, Brian Carpenter wrote: > > Then there was this little bit of info: > > Jun 18 00:00:12 mm4 kernel: [19548549.442555] Out of memory: Kill > process 29676 (python3) score 37 or sacrifice child > Jun 18 00:00:12 mm4 kernel: [19548549.444508] Killed process 29676 > (python3) total-vm:192224kB, anon-rss:93084kB, file-rss:0kB, shmem-rss:0kB > Jun 18 00:00:12 mm4 kernel: [19548549.464907] oom_reaper: reaped process > 29676 (python3), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB > > I suspect the above process was ltmp. > > So the server has 2 gig of ram with about a dozen MM3 lists on it. Is > this an issue with tuning performance of the Postgresql server or do I > need to add more memory. I am curious how much ram your server is > running and if you had run into any OOM of problems. I haven't seen any OOM issues on the servers I manage. Those include mail.python.org 16 GB RAM 261 MM2.1 lists, 139 MM 3 lists lists.mailman3.org 4 GB RAM and other than tests and demos, only this list www.grizz.org 8 GB RAM This is my bicycling club's server. 7 MM 2.1 lists, only 2 of which are really active, 7 MM 3 lists including 2 test/demo - MySQL for the club database and Postgres for Mailman 3. It also supports some non Mailman club email and the club's web site including a MoinMoin wiki. The grizz.org domain was recently migrated from from a larger server in a colo that supported multiple domains to a DigitalOcean droplet which initially had only 4 GB RAM, but that seemed marginally enough at best, so I upgraded it to 8 GB. So the bottom line is I haven't run Mailman 3 on a server with only 2 GB and that may well not be enough. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Five Year Old Issue

by Brian Carpenter

On 3/14/21 8:10 PM, Mark Sapiro wrote: > On 3/14/21 5:07 PM, Mark Sapiro wrote: >> It turns out Abhilash had done all the heavy lifting on this [1] but I didn't realize it because [2] hadn't been done. Since the rest was easy, [3] now fixes it. >> >> [1] https://gitlab.com/mailman/mailman/-/merge_requests/779 >> [2] https://gitlab.com/mailman/mailman/-/merge_requests/796 >> [3] https://gitlab.com/mailman/mailman/-/merge_requests/795 >> > > Ooops, [2] and [3] are reversed > > [2] https://gitlab.com/mailman/mailman/-/merge_requests/795 > [3] https://gitlab.com/mailman/mailman/-/merge_requests/796 > So this means the fix will show up in the next stable release? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 7 months

[MM3-users] Re: Moderate mails from owner

by Mark Sapiro

On 3/21/19 3:02 AM, Malcolm Austen wrote: > > 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. Isn't there a footer at the bottom of wach page with something like: Postorius Documentation • GNU Mailman • Postorius Version 1.2.5 > 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. New (non-)members always have Moderation set to List default. This means their posts are governed by the applicable Settings -> Message Acceptance settings. Setting a user's Moderation to Default Processing means that users posts will not be held/rejected/discarded/accepted immediately based on "Default action to take when a (non-)member posts to the list", but additional checks will not be bypassed. See <https://mailman.readthedocs.io/en/latest/src/mailman/rules/docs/rules.html>. > Are my deductions correct? And if so, could this be the explanation of > the issue detailed in this thread? Setting a user's Moderation to Default Processing (or Accept) would bypass the list defaults and could be the explanation of this issue. When the non-member owner first posts to the list that address becomes a non-member of the list. I.e. it is in the roster of known non-members of the list and that non-member record could have had its Moderation set to Accept or Default Processing at some point which would explain why the posts are accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 6 months

[MM3-users] Re: Postorius endless loading on Sign in / Register then "Internal Server Error"

by Mark Sapiro

On 6/9/20 12:16 PM, Jacob Bargery wrote: > Pre-cursor, I am in a new position to learn on the go and new to Linux but have been tasked with setting up a List Serv and they wanted Mailman 3 with Postorius and HyperKitty. Running on Ubuntu 20.04 LTS using Postfix and MySQL. I can open up the initial pages. With no Lists created yet. I can open up Register, Login, and Forgot Password but when I submit anything it spins the loading icon for a long time then reads" > > "Internal Server Error > The server encountered an internal error or misconfiguration and was unable to complete your request. Apache/2.4.41 (Ubuntu) Server at groups.smccme.edu Port 80" ... > This is a traceback I could find from another attempt: > > Traceback (most recent call last): ... > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API What are your Django settings for MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' Those match the defaults defined in mailman/config/schema.cfg [webservice] # The hostname at which admin web service resources are exposed. hostname: localhost # The port at which the admin web service resources are exposed. port: 8001 # Whether or not requests to the web service are secured through SSL. use_https: no # The administrative username. admin_user: restadmin # The administrative password. admin_pass: restpass If all that seems to match, what happens if you try telnet localhost 8001 If that doesn't work, but telnet 127.0.0.1 8001 works, there is some issue with `localhost` involving /etc/resolv.conf or /etc/hosts, most likely an ipv6 definition like ::1 localhost in the latter. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Displaying addresses in emails from a Mailman 3 installation

by Mark Sapiro

On 7/2/25 19:50, Steve Brown via Mailman-users wrote: > Thanks, Mark. As usual, your reply was rapid and helpful. I infer that you don't see the instability that my subscriber does. I'm pretty sure I don't, but I'm not completely certain I would notice. > Do (can?) email providers passing the posts to the subscriber alter the headers in ways that might lead to that unstable behavior? It is possible, but I don't think likely that the final mail delivery agent would do this. It's also almost certain that no intermediate MTA is doing it. > Or can it occur because of the way T-bird tries to help the user associate display names with email addresses--autofill and address book automation? That seems unlikely since those things would be tied to the email address which is always the same list posting address. > Do you have those kind of features turned off in your T-bird? Or is it more likely that the subscriber makes some mistakes that get interpreted as needing a change in From displays? Because only one of my subscribers is complaining regularly, it's not very important for me to do anything, but I'm still curious about the origin of this behavior. I don't think I have any non-default settings in my T-bird, and I do have address book entries for various lists and I don't see T-bird showing messages From the display names in my address book. I am curious as to what the complaint is. Does the user feel that something important is missing or is the concern just the inconsistency? Also, is there any correlation between the inconsistent behavior and what the poster's name is? -- 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

[MM3-users] Re: Moderation via command line

by Mark Sapiro

On 9/24/26 09:49, alain williams wrote: > Where is the API for this written down, ie defined, so that I can look at it ? The API you are looking at is Mailman;'s REST API. It is documented at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> of which <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> is a part. Following those docs is somewhat tricky as they use helper functions so that the doctests work. In practice, instead of doing something like ``` json = call_http('http://localhost:8001/3.0/lists/my-list@leavesden.org.uk/held') ``` in `mailman shell`, you would just do ``` curl -urestadmin:restpass http://localhost:8001/3.0/lists/my-list@leavesden.org.uk/held ``` If you want to do these things in `mailman shell` you're better off dealing directly with Mailman's models and methods, although documentation for those things is just the source code. For example ``` $ mailman shell -l my-list(a)leavesden.org.uk 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 test_hold(a)msapiro.net mailing list >>> # get the ids of the held messages >>> for rq in IListRequests(m).held_requests: ... print(rq.id) ... >>> # The above prints the request IDs. You can then handle them with >>> from mailman.app.moderator import handle_message >>> # If you want to discard them all you could do >>> for rq in IListRequests(m).held_requests: ... handle_message(m, rq.id, Action.discard) ... >>> # or you could handle them individually with various actions like >>> # 'accept', 'defer', 'discard' or 'reject' >>> # and when you're satisfied >>> commit() ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 weeks, 4 days

[MM3-users] Re: required cron entries?

by Mark Sapiro

On 12/31/20 2:49 AM, Andreas Barth wrote: > Hi together, > > as I found some mails in queue/shunt, I thought who should be running > them. See below. > On my (standard debian) reference system, there are no cron entries > for mailman3 but only for mailman3-web. The crons for Mailman core are discussed at <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs>. > Looking in the source code, there is a ./cron/crontab.in.in however > references to scripts in port_me/ directory. That's all old Mailman 2.1 stuff. ignore it. > Should I (still) install (parts of) the crontab? Or > are these functions handled elsewhere? Again, see <https://docs.mailman3.org/en/latest/config-core.html#configuring-cron-jobs>. > Also, who picks up mails in queue/shunt? Or are they lost somehow? When processing of a message in Core throws an uncaught exception, the error is logged with a traceback in var/logs/mailman.log and the message's queue entry is saved in the /var/queue/shunt/ queue. These messages can be retried via the `mailman unshunt` command, but unless the underlying cause has been fixed, they will throw the same exception and be shunted again. Each shunted message requires manual inspection of the var/logs/mailman.log entry and possibly examination of the message via `mailman qfile /var/queue/shunt/....pck`. Some of these are spam messages which are somehow defective causing the exception, and these can just be manually removed from the shunt queue. I've seen a couple that are transient errors[1] that can just be successfully unshunted. The rest require some underlying issue to be fixed before they can be successfully unshunted. [1] In particular, I've seen an apparent race condition in building the list of recipients where we try to determine the delivery status for a member that is no longer a member. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

[MM3-users] Re: Disabling Mass operations

by Mark Sapiro

On 1/23/26 17:39, iMark wrote: > Hi All, > > Can anyone give me a pointer on disabling "Mass operations" > (subscribe/removal) in Postorius. > > Just removing the menu link from the list-owners administration pages > would be a good start. This patch will do that ``` --- a/src/postorius/templates/postorius/menu/list_nav.html +++ b/src/postorius/templates/postorius/menu/list_nav.html @@ -84,6 +84,7 @@ {% if user.is_superuser or user.is_list_owner %} <li class="nav-item"><a href="{% url 'list_template_list' list.list_id %}" class="nav-link {% nav_active_class current 'templates' %}">{% trans 'Templates' %}</a></li> <li class="nav-item"><a href="{% url 'list_settings' list.list_id %}" class="nav-link {% nav_active_class current 'list_settings' %} ">{% trans 'Settings' %}</a></li> + {% if user.is_superuser %} <li class="dropdown nav-item"> <a href="#" class="{% nav_active_class current 'list_mass_ops' %} dropdown-toggle nav-link" data-bs-toggle="dropdown" role="button" aria-haspopup="true" aria-expanded="false"> @@ -98,6 +99,7 @@ <li><a href="{% url 'mass_removal' list.list_id %}" class="dropdown-item">{% trans 'Mass removal' %}</a></li> </noscript> </li> + {% endif %} <li class="nav-item"><a href="{% url 'list_bans' list.list_id %}" class="{% nav_active_class current 'list_bans' %} nav-link">{% trans 'Ban List' %}</a></li> <li class="nav-item"><a href="{% url 'list_header_matches' list.list_id %}" class="nav-link {% nav_active_class current 'list_header_matches' %}">{% trans 'Header filters' %}</a></li> <li class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` Some lines in the above may be wrapped but basically it just adds {% if user.is_superuser %} and {% endif %} around the Mass operations code. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 months, 3 weeks

Search results for query "sapiro"