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

[MM3-users] Re: Block members from sending cc's and bcc's

by Mark Sapiro

On 11/14/25 17:34, Cathryn McGuire wrote: > > You hinted there's a way to not hold posts with a Cc: to <neighbours(a)mailist.dunbar-vancouver.org> by adjusting our header rules, but I think yes, now we do want that. What would that header rule look like? You can use the following rule: Header = cc Pattern = ^(?!(\w+ )*<?neighbours(a)mailist.dunbar-vancouver.org>? *$) Action = Hold for moderation That will match any Cc: header that doesn't look like any of Cc: <neighbours(a)mailist.dunbar-vancouver.org> Cc: neighbours(a)mailist.dunbar-vancouver.org Cc: neighbours Mailist Dunbar <neighbours(a)mailist.dunbar-vancouver.org> Cc: any words <neighbours(a)mailist.dunbar-vancouver.org> That will probably be good enough. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months

[MM3-users] Re: Mail not going out

by Mark Sapiro

On 6/21/19 11:30 PM, andrew.bernard(a)gmail.com wrote: > What process handles the sending of the mail out to subscribers? > > My new installation suddenly stopped sending. Apologies for so many newbie questions. See <https://mailman.readthedocs.io/en/latest/src/mailman/docs/8-miles-high.html> Incoming messages are received by Mailman's `lmtp` runner and queued in the `in` queue. They are picked up from there by the `in` runner and processed through a chain of rules and if accepted processed through a pipeline of handlers, one of which will queue the message in the `out` queue. Then the `out` runner will pick up and send the message. Look at logs, particularly mailman.log, and queues and ensure Mailman and all the runners are running. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

[MM3-users] Re: First time mailman installation

by Mark Sapiro

On 7/25/24 00:19, Roland Giesler via Mailman-users wrote: > > As I have written in another post I made, I have set the (apparently) > appropriate parameters in the mailman.cfg, but I still get "relay access > denied" from my external MTA, which mean that authentication is not even > attempted, or am I mistaken? You may find this doc useful - <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/mta/docs/c…>. In your case, the secure connection is established and the user authenticated before the mail is sent, and the "relay access denied" is in response to the SMTP RCPT TO command which is part of sending the mail. I.e., authentication succeeded before the "relay access denied" occurred. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

[MM3-users] Re: New Lists Appear in HyperKitty Archives, But No Mail Data is Shown

by Mark Sapiro

On July 12, 2025 8:28:58 AM EDT, Asif Muzammil via Mailman-users <mailman-users(a)mailman3.org> wrote: >Hello, > >*Problem:* When I create a new mailing list in Mailman Core and then visit >the HyperKitty archives, the list is correctly displayed. However, when I >send an email to that list, no mail data (messages) are shown inside it. >The message count for the list remains at zero in the archives UI. The messages are probably queued in Mailman core's var/archives/hyperkitty/spool/ directory and the errors that cause this logged in var/logs/mailman.log. Once you fix the underlying issue, the messages will be delivered to hyperkitty on the next post. -- Mark Sapiro <mark(a)msapiro.net> Sent from my Not_an_iThing with standards compliant, open source software.

1 year, 3 months

[MM3-users] Re: Mailman3 without Hyperkitty in docker

by Mark Sapiro

On 2/27/19 12:38 PM, Danil Smirnov wrote: > Hi Abhilash, > > ср, 27 февр. 2019 г. в 22:21, Abhilash Raj <maxking(a)asynchronous.in>: > >> So, what errors are you looking at in uwsgi*.log? >> > > There are tons of errors like this: > > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] respawning "./manage.py qcluster" (uid: 100 gid: 101) > Unknown command: 'qcluster' > Type 'manage.py help' for usage. > [uwsgi-daemons] throttling "./manage.py qcluster" for 26 seconds do you have django-q in INSTALLED_APPS in your Django settings and what is set for Q_CLUSTER? Does the manage.py that's being run here point to the right settings.py? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 7 months

[MM3-users] Re: MM2 -> MM3 Migration: listinfo page

by Mark Sapiro

On 3/8/23 02:21, Odhiambo Washington wrote: > > For those who have migrated from MM2 to MM3, does someone have an elegantly > modified listinfo page they are willing to share? I remove the MM 2.1 list, but leave the archives. Instead of having any kind of listinfo page, I put a redirect in Apache for each migrated list. E.g. RedirectMatch permanent /mailman/listinfo/mailman-users(/.*)?$ \ https://mail.python.org/mailman3/lists/mailman-users.python.org/ For archives, I add a note to archives/private/<listname>/index.html. See https://mail.python.org/pipermail/mailman-users/ for an example. This works for public archives, but not for private archives because there is no longer a list to use for private archive authentication. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

[MM3-users] Re: Thread IDs on messages incrementing per reply?

by Mark Sapiro

On 10/18/23 14:54, Thomas Ward via Mailman-users wrote: > > Is there any way to have Subject based thread tagging, etc.? I ask this > only because we're trying to thread items for easy ID in a system right > now that does thread ID tagging in the subject line (i.e. > "[Test-0000004] Something" and "Re: [Test-0000004] Something" are > identified as the same thread, but a brand new message "Something" would > end up as "[Test-0000005] Something" in the chain if it was a new message.) It is not possible with the current design. The issue is the tagging is done by Mailman core and Mailman core knows nothing about threads. -- 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: After server upgrade debian 11→12 and reinstalling everything in (venv), I got this error when accessing → mailman3/lists

by Mark Sapiro

On 9/21/25 14:49, Wikinaut wrote: > Do you have a programmatic way to delete n ( n > 20) such entries in Postorius, e.g. via a python script + REST to loop through all lists and perhaps to exclude a few based on a small condition (like a text found in old template and/or list name)? I don't have anything off hand, and in the time it would take me to create one and for you to customize it for your exceptions, you could probably go through well over 20 lists/templates via the web UI. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

[MM3-users] Re: hidden list is hidden even to the owner

by Mark Sapiro

On 7/2/20 8:10 AM, Mohsen Masoudfar wrote: > > This is after a long fight with AWS and Redhat versions, I ended up installing the mailman3-full package on Ubuntu18. Installation was straight forward and easy, but it seems it is not easily possible to update/upgrade Postorius alone in this configuration, is it? You can't upgrade Postorius alone in any configuration because the latest Postorius requires recent Mailman core, mailmanclient and django-mailman3. Depending on how the Debian/Ubuntu package installs these things, it may be possible to upgrade them with pip3, but as I don't know the details of how they are installed in this package, I can't say how to do this. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

[MM3-users] Re: ERROR sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name xxxx to address

by Mark Sapiro

On 3/2/23 14:03, o.mankewitz(a)gmail.com wrote: > > This is the part of mailman.cfg: > [database] > class: mailman.database.postgresql.PostgreSQLDatabase > url: postgresql://mailman:<mypassword>@localhost/mailman > Full error: > sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name "assword>@localhost" to address: Name or service not known Do you have literally `<mypassword>` in `url: postgresql://mailman:<mypassword>@localhost/mailman` `<mypassword>` needs to be replaced with the actual password for the postgress `mailman` user. I.e. the password you provided when you did `CREATE USER mailman WITH PASSWORD 'secure-password';` in postgres (and hopefully didn't set it to literally `secure-password`). -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 7 months

Search results for query "sapiro"