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

[MM3-users] Re: SpamAssassin and clamav?

by Marisa Giancarla

Ok sounds good... Marisa On 3/15/24 18:40, Mark Sapiro wrote: > On 3/15/24 17:52, Marisa Giancarla via Mailman-users wrote: >> Is there a way to have mm3 use SpamAssassin and/or clamav? >> Marisa > > It would require custom code modification to invoke SpamAssassin > and/or ClamAV from mailman. It is much better to integrate these in > the MTA. >

1 year, 5 months

[MM3-users] Re: mailman3 3.2.2 python3.8 problem on focal

by Thomas Stein

Thanks! Am 21. März 2024 01:19:36 MEZ schrieb Mark Sapiro <mark(a)msapiro.net>: >On 3/20/24 10:24, Thomas Stein wrote: >> >> Answering my own post for now. >> >> Replacing time.clock() with time.process_time() in /usr/lib/python3/dist-packages/mailman/utilities/uid.py seems to fix the current issue for me. Don't know what else I broke with it though. :) > > >Mailman 3.2.2 is not compatible with Python>=3.8. Unfortunately, at least one Debian/Ubuntu release included that combination. Your fix is the correct one, see https://gitlab.com/mailman/mailman/-/commit/ea05bdd0f74ba06d85adad1f7d190a6… >

1 year, 5 months

[MM3-users] Re: Sibling lists in Mailman3

by Markus Grandpré

Thank you. Am 27.03.24 um 17:26 schrieb Mark Sapiro: > On 3/27/24 08:05, Markus Grandpre wrote: >> >> after I migrated a list from Mailman21 to Mailman3 I missed the >> Mailman21 setting "regular_include_lists" (or something similar) in >> Mailman3. How are sibling lists treated in Mailman3? > > The sibling list features do not exist in Mailman 3. > -- Markus Ludwig Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung und Lehre, B803, Tel: ++49 7531 88 4342

1 year, 5 months

[MM3-users] Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark Sapiro wrote: > What's in var/logs/mailman.log? Good question! > 2024-04-10 12:42:08 [FALCON] [ERROR] GET /3.1/lists/new_test.domain.tld/arch ivers => Traceback (most recent call last): > ... > ModuleNotFoundError: No module named 'mailman_hyperkitty' That has me confused, as the footer says > Powered by HyperKitty version 1.3.9.

1 year, 4 months

[MM3-users] Re: Error -- postorius Un-handled exception

by admin＠bclug.ca

Mark Sapiro wrote: > > ModuleNotFoundError: No module named 'mailman_hyperkitty' > > That has me confused, as the footer says > > Powered by HyperKitty version 1.3.9. > > mailman_hyperkitty is a separate package which is a shim between Mailman > core and HyperKitty. In your venv or wherever Mailman is installed, you need > pip install mailman_hyperkitty It should be already installed, as it shows in the footer? > (venv) mailman@mail:~$ pip install mailman_hyperkitty > Requirement already satisfied: mailman_hyperkitty in ./venv/lib/python3.10/site-pa ckages (1.2.1) > ... > (venv) mailman@mail:~$

1 year, 4 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-24 03:58, Mark Sapiro wrote: > What do you get if you do > ``` > sudo -u mailman curl > https://lists.mydomain.com/mailman3/api/templates/list/mytestlist.lists.myd… > ``` > with the template set in Postorius? The welcome message is returned. root@hel:~# sudo -u mailman curl https://LISTS.MYDOMAIN.COM/mailman3/api/templates/list/MYTESTLIST.LISTS.MYD… Test Welcome message for new subscribers.root@hel:~#

1 year, 4 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-04-24 14:18, Mark Sapiro wrote: > So all the runners are running as user mailman. That's good. What > exactly is the issue now. Is it retrievals timing out or an empty > welcome message? The issue is: A. With POSTORIUS_TEMPLATE_BASE_URL = 'http://<REDACTED-PUBLIC-IPv4-ADDRESS>', it sends an empty Welcome message when a new member is added. B. With POSTORIUS_TEMPLATE_BASE_URL = 'https://MYDOMAIN.COM', no Welcome message gets sent and a timeout error appears on the webpage, although the new member gets added.

1 year, 4 months

[MM3-users] Re: Welcome message template errors

by Mark

On 2024-05-01 03:12, Mark Sapiro wrote: > I have now reinstalled Mailman from scratch on the development server > in a Python 3.12.3 venv using the heads of the gitlab branches and > getting the current versions of all the dependencies and this > installation gets no error. So while I still have an older venv that > produces this error, I cannot duplicate the error in a new install. In the new installation, are the template.uri (in the mailman DB) records written as http://localhost:8000/... ?

1 year, 4 months

[MM3-users] Re: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by admin＠bclug.ca

Mark Sapiro wrote on 2024-05-24 05:15: > Are you gating messages to/from usenet for this list? Is nntp common enough these days to be a useful default runner? I disabled it in mine when I noticed it, but it seems (IMHO) a waste of resources (yet another Python interpreter running) for a fairly edge case of mailing list <--> nntp transits. rb

1 year, 3 months

[MM3-users] Re: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Ron / BCLUG

Mark Sapiro wrote on 2024-05-25 08:38: > The host name displayed in the web UI is based on the SITE_ID setting in > Django's settings. This is a system configuration not associated with > any lists. it references an entry in the django_sites table in the > database. Specifically, the `mailmanweb` DB, table `django_site`. In this case, I found the GUI to be easier: https://$your_domain/admin/sites/site/ rb

1 year, 3 months

Search results for query "sapiro"