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

[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, 10 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, 9 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, 9 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, 9 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, 8 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, 8 months

[MM3-users] Re: A few more MM3 questions

by Marc SCHAEFER

Hello, On Wed, May 29, 2024 at 09:23:07AM -0400, Mark Sapiro wrote: > I don't know the details of where the Debian package puts things, but there > may be Postfix related files in /var/lib/mailman3/data, but yes, all Yes, exactly. Mailman3 under Debian can generate Postfix aliasesdb (it requires a manual Postfix configuration though to reference those files: I think it was already in the example deployment script I posted a few days ago). Also, the start script of Mailman3 under Debian *seems* to systematically regenerate those files at Mailman startup, so it would probably not even be needed to restore this. Great new! Thank you.

1 year, 8 months

[MM3-users] Re: Problem with digests not being sent daily

by Mark

> On 6/22/24 17:51, Mark Sapiro wrote: > With digests enabled and > the threshhold set to 0, on each post a digest.mmdf will be created > and then immediately moved to digest.<vol>.<num>.mmdf and an entry > queued for digest runner to create the digest(s) from that file and > remove it, so within probably a few seconds > /opt/mailman/mm/var/lists/<LISTID>/ will be empty again. Digests are enabled and the threshold = 0. Is it possible to temporarily disable the digest runner so that I can see if a post is actually creating the digest.mmdf file (before the runner removes it)?

1 year, 7 months

[MM3-users] Re: Where to put static files referred to from list Info page?

by Greg Newby

On Mon, Aug 5, 2024 at 3:30 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/5/24 15:02, Greg Newby wrote: > > > > My question: Is there a place I can put these files within the Mailman > > directory hierarchy so they can be linked from the list Info page? > > You could put them in Mailman's static/ directory and reference them > with a /static/... URL. > > Confirmed - thanks! The 'static' location was just what I was looking for. ~ Greg

1 year, 6 months

[MM3-users] Re: Trying to understand the mailman.cfg from the virtualenv installation guide

by Danil Smirnov

Hi Mark, ср, 11 сент. 2024 г., 06:26 Mark Sapiro <mark(a)msapiro.net>: > On 9/8/24 01:04, unite42--- via Mailman-users wrote: > > [mta] > > verp_confirmations: yes > > verp_personalized_deliveries: yes > > verp_delivery_interval: 1 > > > > What is the background of these recommendations? > > > These settings enable VERP for all list messages. This results in more > reliable bounce processing. > Is there any downsides of using it, so it's not enabled by default? TIA Danil >

1 year, 5 months

Search results for query "sapiro"