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

[MM3-users] Re: Disabled by bounce

by Mark Sapiro

On 2/17/23 13:39, denise.mcgeachy--- via Mailman-users wrote: > Hi all - new to this forum but am trying to work out a similar issue raised by a list member's IT department. I'm a bit out of my depth here and hoping you all can help. > > They have recommended: > > - When the mailing list relay an email from a member of the list to other members, the email from address should be the mailing list and not the user sending the original email. For example: list-name(a)mydomain.ca (on behalf of Sally Brown) > - The mailing list should not modify the original email and thus breaking the DKIM signature > > I have clicked the DMARC mitigation unconditionally option which seems to solve the second point but haven't managed to have it sent by the list name but not as suggested in the first point. I either get "my email via list(a)mylist.ca" or list(a)mylist.ca" > Is anyone aware of a setting to do this? Those two points are contradictory. You can't do both. Not modifying the message in ways that break DKIM requires no content filtering, no addition of list headers or footers and no munging of From: or Reply-To: headers. Normally the list will make some modification that will break DKIM signatures. If you set DMARC mitigation action to Replace From: with list address, and set DMARC Mitigate unconditionally, that should address the first point and individual messages from the list will be From the list and that's all you should need. For example, the message to which I'm replying is From: denise.mcgeachy--- via Mailman-users <mailman-users(a)mailman3.org> While this is not identical to the format you quote, the address is the list's address which is the important thing. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

[MM3-users] Re: list footer questions

by Mark Sapiro

On 5/14/20 2:49 PM, Mohsen Masoudfar wrote: > > It is on Ubuntu18.04 and has been installed with Ubuntu package Mailman-full. There is no update available yet. So it looks like I cannot use the easy way of modifying the templates. > Question: Is there a way to achieve the same by updating the code? You don't have to modify code. You can set a footer in Mailman's file hierarchy. There is a var/templates directory, maybe somewhere like /var/lib/mailman/templates in the Ubuntu package. This directory can contain subdirectories lists, domains and site. These may or may not existb but the layout is the site directory contains subdirectories for language codes, i.e. 'en', 'fr', 'de', etc. The domains directory contains subdirectories for domains like 'example.com', example.net, etc. and those contain the language subdirectories. The lists directory contains subdirectories for lists like list.example.com and those contain the language subdirectories. Now when mailman is looking for a template, it looks in this hierarchy first, e.g. when looking for an English language footer for the list(a)example.com list for regular members it will look in this order: templates/lists/list.example.com/en/list:member:regular:footer.txt templates/domains/example.com/en/list:member:regular:footer.txt templates/site/en/list:member:regular:footer.txt before falling back to a default. The name for a digest footer is list:member:digest:footer.txt, or there can be a list:member:generic:footer.txt file which is for both regular and digest deliveries. There is documentation at <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…>, but it can be difficult to follow. <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> describes the various templates and the substitutions available. Note that the name of a file in the above hierarchy is the template name with `.txt` appended. -- 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: 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

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

6 years, 11 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

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

7 months, 3 weeks

[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, 1 month

[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

1 month

[MM3-users] Re: What is the recommended format for mailbox interchange as files?

by Mark Sapiro

On 6/21/19 8:38 PM, J.B. Nicholson wrote: > > What is the recommended file format for mail archives to share? > > I ask because I often see mailman mailing list archives available as > some format of mbox file. I like this feature. I want to quickly import > a bunch of archived messages into my account so that I can read old > threads and get more discussion context anytime I need it. Some flavor of mbox is ubiquitous in the *nix world. The problem with this format is lines in the message body beginning with 'From '. Most modern software that writes mbox format files avoids this problem by somhow mangling such lines. The Python mailbox package will prefix such lines with '>' when writing a message to a mbox. Before Mailman 3, Mailman kept a cumulative archive in mbox format. Even after pipermail was included, the cumulative mbox was normally written and could be used to rebuild the pipermail archive or move the archive elsewhere. The problem is that the Python mailbox package didn't always mangle 'From ' lines in the body, so archive mboxes that go back many years are likely to have problems. A more robust mailbox format which is still a single file is MMDF format. This is similar to mbox with the addition that each message is preceded and followed by a line consisting of exactly four control-A bytes. I.e., there is one such line at the beginning and at the end of the file and two such lines between each message. Mailman 3 uses this format for the mailboxes that accumulate messages for digests. However, lot's of things including HyperKitty's importer and Mailman 2's bin/arch tool require input in mbox format. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

[MM3-users] Re: Member Issue Discovered

by Mark Sapiro

On 10/20/20 6:54 AM, Brian Carpenter wrote: > > Respectively, I think you are asking the wrong question here. The real > question is why isn't a display_name being removed when a list > subscriber is unsubscribed. I'd like to understand the real requirement. It seems to me that this issue has come up because a list admin wanted to change the display name shown in the membership roster for a user. Since there is currently no UI to do this, the list admin tried to do it by unsubscribing and resubscribing the user. That didn't work which led to this "unsubscribing a user should remove the user's information" thread, but the real issue is the lack of a UI for changing display names. It seems if that UI existed and was available, the "unsubscribing a user should remove the user's information" issue would never have been raised. So perhaps what we should be talking about is UIs for changing user information, what they would look like and who should be able to change what. Note that I personally am a member of many lists, an admin of multiple lists and a site admin for multiple mailman installations. I am well aware of the frustrations of list admins who wind up just doing it because it's way easier than instruction some users as to how to do it themselves. However, I don't think that is necessarily sufficient reason to hand over control of global, non-list specific user information to the admin of one particular list that the user happens to be a member of. Even in mailman 2.1, while a list admin could go to a user's options page for the list and change things, the "change globally" check boxes only worked for the user, not for the list admin. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Search results for query "sapiro"