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

[MM3-users] Re: LMTP on unix socket

by Stephen J. Turnbull

Mark Sapiro writes: > You would have to modify mailman/runners/lmtp.py to listen on a unix > socket. The docs imply the aiosmtpd.controller.Controller class has a > make_socket() method which "allows subclasses to customize the creation > of the socket before binding" which I suppose could be used to create a > unix socket, but mailman/runners/lmtp.py currently doesn't make use > of that. If someone is thinking about doing this, I suggest comparing the asyncio event loop's create_server method with create_unix_server, which will probably give ueful hints about implementation. BTW, I object to the smtpd package's lmtp_host=UNIX_SOCKET_PATH style of configuration. There should be a separate parameter for this. Steve

6 years, 9 months

[MM3-users] Re: Mailman 3 on Fedora - Core only ?

by Lars Bjørndal

On Sat, Jun 13, 2020 at 12:55:25PM -0700, Mark Sapiro wrote: > On 6/13/20 2:17 AM, Lars Bjørndal wrote: > > I'm about to set up a new list, and want to try out Mailman3. > > > > The only component available in Fedora, is the Mailman core package. > > > I find that strange as <https://lists.fedoraproject.org/> is Mailman 3 > and the core developer who did most of the HyperKitty development works > or did work for Fedora. I asked on the Fedora developers list, and they told me that it's worked on. They pointed me to <https://pagure.io/fedora-infrastructure/issue/8455> for more info. Thanks Lars

6 years, 2 months

[MM3-users] Re: About to Install MM3 -- Seeking clarification

by Onyeibo

On Mon, 2 Jan 2023 09:57:45 -0800 Mark Sapiro <mark(a)msapiro.net> wrote: > MAILMAN_REST_API_URL = 'http://localhost:8001' > MAILMAN_REST_API_USER = 'restadmin' > MAILMAN_REST_API_PASS = 'restpass' I've not had any occasion to set these while following the documentation. > > match > > $ mailman info > ... > REST root url: http://localhost:8001/3.1/ > REST credentials: restadmin:restpass > > Note the 3.1/ in REST root url is not included in > MAILMAN_REST_API_URL. > > What do you get from, e.g. > > curl -urestadmin:restpass http://localhost:8001/3.1/lists > > It should return JSON with information about your lists. > I get the following: {"start": 0, "total_size": 0, "http_etag": "\"678678567346533573674563786538\""}

3 years, 7 months

[MM3-users] Re: Congrats on the instructions for installation on ubuntu, what about migration?

by Peter Adebahr

On 10/9/24 22:18, Mark Sapiro wrote: > > The easiest scenario is if you want to migrate everything. You just dump > the database on the old server and load it on the new one using the > database manager's tools. > Thank you Mark, this is exactly my task to be in the near future. Loading the old database will overwrite the current version's newer settings: Don't I have to run something like 'mailman3 migrate' to update the database, or is this taken care of automatically by using the alembic version when I just restart mailman3? Best regards, Peter

1 year, 10 months

[MM3-users] Re: Problem migrating from Ubuntu packaged Mailman to Virtualenv, including Hyperkitty

by Tim Cutts

Thanks Mark. The migration seems to have done the trick for the archive - thanks for the pointer. Given that I have mailman-web running as www-data in Debian-style, I had to use: sudo -u www-data /opt/mailman/venv/bin/mailman-web migrate But that did the trick, and my archives have reappeared, so thank you. > On 7 Jul 2022, at 19:35, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 7/7/22 8:12 AM, tim(a)thecutts.org wrote: >> Hi everyone, >> As we all know, mailman3 got dropped from Ubuntu 22. So I updated the operating system anyway, and decided to switch to a virtualenv setup, keeping the old Debian/Ubuntu database and log locations etc. >> With some lumps and bumps, this has gone OK; the web interface appears to be working, and I can use the mailman CLI to manipulate the lists. So far so good. >> However, there do seem to be two problems, which might be linked: >> 1. If I send a message to my test list, it does not get sent on to any members. I can see the lmtp delivery to mailman. But nothing comes out again. I can see the two test messages in the “shunt” directory > > > Look in mailman.log. There will be exceptions and tracebacks associated with the shunted messages. What are these? Right, thanks for the pointer (there are so many separate log files, I’d been looking in the wrong one!) Jul 07 17:17:44 2022 (117110) SHUNTING: 1657210664.44771+e859f37833c541df3582ea334ab4b7b016557f77 Jul 07 17:23:39 2022 (117110) Uncaught runner exception: no nameservers Jul 07 17:23:39 2022 (117110) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 176, in _one_iteration self._process_one_file(msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/runner.py", line 269, in _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/runners/incoming.py", line 79, in _dispose process(mlist, msg, msgdata, start_chain) File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/core/chains.py", line 57, in process if link.rule.check(mlist, msg, msgdata): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 316, in check if maybe_mitigate(mlist, address): File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 288, in maybe_mitigate answer = is_reject_or_quarantine( File "/opt/mailman/venv/lib/python3.10/site-packages/mailman/rules/dmarc.py", line 177, in is_reject_or_quarantine resolver = dns.resolver.Resolver() File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 758, in __init__ self.read_resolv_conf(filename) File "/opt/mailman/venv/lib/python3.10/site-packages/dns/resolver.py", line 850, in read_resolv_conf raise NoResolverConfiguration('no nameservers') dns.resolver.NoResolverConfiguration: no nameservers Jul 07 17:23:39 2022 (117110) SHUNTING: 1657211019.9355967+2e5a440ca577e112e092e03072660a4314f012eb Purging the resolvconf package and configuring resolv.conf manually fixed that little issue. Thanks again for the help Tim > >> Are these issues likely to be related, or do I have two things going on here? > > > The shunted messages are not related to the Django migration issues. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > _______________________________________________ > Mailman-users mailing list -- mailman-users(a)mailman3.org > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

4 years, 1 month

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

> -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > To: mailman-users(a)mailman3.org > Sent: Thursday, June 12, 2025 17:39 > Subject: [MM3-users] Re: Trouble Installing Mailman3 > > I think the issue may be that normally pip installs build requirements in an > isolated temporary directory so as not to create potential conflicts with installed > packages. >. > Specifying --no-build-isolation on the pip command will disable this. > If you specify --no-build-isolation on the pip command, it should use setuptools > and wheel from your venv. Eureka! (more precisely, YOU found it!) Adding --no-build-isolation did the trick and I think I'm in business. I cannot thank you enough. -- Henry Hartley Westat RB 2151

1 year, 2 months

[MM3-users] Re: High IO for 8+ hours

by Paul Tomblin

On Sun, Mar 1, 2026, at 3:38 PM, Mark Sapiro wrote: > On 3/1/26 05:10, Paul Tomblin via Mailman-users wrote: > The HyperKitty update_and_clean_index job runs monthly and does the same > thing as the hourly update_index job plus removing index entries for > messages that have been deleted from HyperKitty. It is very long running Does that mean that removing the cron job for the monthly task would do the same thing as the patch? > > It's purpose is to drop entries for messages that have been removed. How do messages get removed? Is that an automatic thing or if not, is it something a user can do or only a list owner? -- Paul Tomblin

5 months, 2 weeks

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Friday, November 3, 2017 12:26:06 PM EDT Mark Sapiro wrote: > The partucular "@daily mailman digests --send" would have to go in the > user crontab for the Mailman user. If this is not 'mailman' it is what > ever user "owns" Mailman. Further it would require that the path to > Mailman's bin/mailman command be in that users $PATH. There's nothing in http://docs.mailman3.org/en/latest/config-core.html or http://docs.mailman3.org/en/latest/prodsetup.html about adding a Mailman user. This should be a system user, right? Should it have a home directory? Could you add that to the documentation? Pierre -- I believe in Yellow when I'm in Sweden and in Black when I'm in Wales.

8 years, 9 months

[MM3-users] Re: "Cannot connect to SMTP server localhost on port 25"

by Manos Pitsidianakis

Thanks for the reply Mark, Στις 2019-09-21 16:19, Mark Sapiro έγραψε: > It's a stretch, but I suggest you examine the list membership and > remove > any invalid local addresses. There aren't any local addresses. > Also, look in the mail server's logs to see if you can see anything > about incoming connections being established and then dropped. Unfortunately no. Listening on all interfaces with tcpdump and there are no packets when mailman starts and the "Cannot connect to SMTP" log appears. It looks like there is no connection at all. Can I use a debugger to see exactly what happens in the runner?

6 years, 10 months

[MM3-users] Re: mailman-web: ResponseNotReady

by Dmitry Makovey

On 10/18/2017 12:28 PM, Mark Sapiro wrote: > On 10/18/2017 09:00 AM, Dmitry Makovey wrote: >> >> It seems like mailman-core is still operating properly, but for some >> reason mailman-web is not. Can I reset mailman-web somehow to re-initiate? > > > I'm not very well versed in the docker images, but I think mailman-web > uses uWsgi and sending the uwsgi process a SIGHUP should do it. I think I didn't express myself clearly - I want to reset any saved state for mailman-web - not just in-memory stuff. I've restarted my setup several times with mailman-web having exact same problem every time. -- Sr System and DevOps Engineer SoM IRT

8 years, 10 months

Search results for query "sapiro"