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

[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

5 years, 5 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\""}

2 years, 11 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, 2 months

[MM3-users] Re: Mailman 3 Keeps Forgettings Imported Lists

by Ryan McClung

Scratch that. Ran with the corrected script and getting the following: [root@mailman3(stg) archives]# mailman lists No matching mailing lists found Any thoughts? On Tue, Jul 31, 2018 at 9:35 AM Ryan McClung <rmcclung(a)afilias.info> wrote: > Hey there, > > Im going to breakdown my response into sections: > > 1) Yes, there is only one install of mailman on the box. > > 2) I created the list using the script below > > 3) My method of importing it is by copying the lists to > /opt/mailman/old/lists and running these commands (within lists) > > MYDIR="/opt/mailman/old/lists" > DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` > for DIR in $DIRS; do mailman import21 "${DIR}"@afilias.info > "${DIR}"/config.pck; done > > However, if you look at the above you can see where I am going wrong. What > it should actually be doing is: > > > MYDIR="/opt/mailman/old/lists" > DIRS=`ls -l $MYDIR | egrep '^d' | awk '{print $9}'` > for DIR in $DIRS; do mailman create "${DIR}"; mailman import21 "${DIR}"@ > afilias.info "${DIR}"/config.pck; done > > Sorry for wasting your time on this one. Coffee is on me. > > > On Mon, Jul 30, 2018 at 6:05 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 07/30/2018 07:37 AM, Ryan McClung wrote: >> > GNU Mailman 3.2.0 (La Villa Strangiato) >> > Python 3.6.5 (default, Apr 10 2018, 17:08:37) >> > [GCC 4.8.5 20150623 (Red Hat 4.8.5-16)] >> > config file: /opt/mailman/var/etc/mailman.cfg >> > db url: sqlite:////opt/mailman/var/data/mailman.db >> > devmode: DISABLED >> > REST root url: http://localhost:8001/3.1/ >> > >> > Shortly after I run an import on a bunch of lists they all disappear. >> > [root@mailman3(stg) mailman]# mailman lists >> > No matching mailing lists found >> > >> > I have 30+ lists. >> >> >> Does the 'mailman lists' command invoke the identical 'mailman' file as >> the 'mailman import21' command that did the imports. And how did you >> create the lists before importing them? >> >> We have done several imports of 2.1 lists to >> <https://mail.python.org/mm3/mailman3/> and have never seen an issue >> like this. >> >> -- >> 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/ >> > > > -- > > Ryan McClung > Systems Administrator @ Afilias Canada > A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 > <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> > W. www.afilias.info > T. +1.416.646.3304 x4186 > -- Ryan McClung Systems Administrator @ Afilias Canada A. 204-4141 Yonge Street, Toronto, ON, Canada, M2P 2A8 <https://maps.google.com/?q=4141+Yonge+Street,+Toronto,+ON,+Canada,+M2P+2A8&…> W. www.afilias.info T. +1.416.646.3304 x4186

7 years, 4 months

[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

6 months

[MM3-users] Re: Multiple domain problem

by Lars Bjørndal

Hi, Mark, Odhiambo and list! Thanks for your feedback. Here is the web configuration. Thank you for taking your time to investigate. The domain that works: <VirtualHost *:80> AddDefaultCharset UTF-8 ServerAdmin webmaster(a)lamasti.net DocumentRoot /var/www/html ServerName lamasti.net ServerAlias www.lamasti.net ErrorLog logs/lamasti-error_log CustomLog logs/lamasti-access_log common Redirect permanent / https://lamasti.net/ </VirtualHost> <VirtualHost *:443> AddDefaultCharset UTF-8 ServerAdmin webmaster(a)lamasti.net DocumentRoot /var/www/html ServerName lamasti.net ServerAlias www.lamasti.net ErrorLog logs/lamasti-error_log CustomLog logs/lamasti-access_log common Alias /mailman3/static /opt/mailman3/web/static Protocols h2 http/1.1 include conf.d/certref.inc <Directory /opt/mailman3/web/static/hyperkitty/img/> Allow from all Require all granted Options FollowSymLinks </Directory> <Directory /opt/mailman3/web/static/> Options FollowSymLinks Allow from all Require all granted </Directory> <IfModule mod_headers.c> RequestHeader unset X-Forwarded-Proto <If "%{HTTPS} =~ /on/"> RequestHeader set X-Forwarded-Proto "https" </If> </IfModule> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/mailman3/archives" "http://127.0.0.1:8000/archives" ProxyPass "/mailman3/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/admin" ProxyPass "/mailman3/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> </VirtualHost> The domain that doesn't work: <VirtualHost *:80> ServerAdmin webmaster(a)list.punktskriftutvalget.no DocumentRoot /var/www/list.punktskriftutvalget/ ServerName list.punktskriftutvalget.no ErrorLog logs/list.punktskriftutvalget-error_log CustomLog logs/list.punktskriftutvalget-access_log common Redirect permanent / https://list.punktskriftutvalget.no </VirtualHost> <VirtualHost *:443> ServerAdmin webmaster(a)list.punktskriftutvalget.no DocumentRoot /var/www/list.punktskriftutvalget/html ServerName list.punktskriftutvalget.no ErrorLog logs/list.punktskriftutvalget-error_log CustomLog logs/list.punktskriftutvalget-access_log combined include conf.d/certref.inc Alias /mailman3/static /opt/mailman3/web/static <Directory /opt/mailman3/web/static/hyperkitty/img/> Allow from all Require all granted Options FollowSymLinks </Directory> <Directory /opt/mailman3/web/static/> Options FollowSymLinks Allow from all Require all granted </Directory> <IfModule mod_headers.c> RequestHeader unset X-Forwarded-Proto <If "%{HTTPS} =~ /on/"> RequestHeader set X-Forwarded-Proto "https" </If> </IfModule> <IfModule mod_proxy.c> ProxyPreserveHost On ProxyPass "/mailman3" "http://127.0.0.1:8000/mailman3" ProxyPass "/mailman3/archives" "http://127.0.0.1:8000/archives" ProxyPass "/mailman3/accounts" "http://127.0.0.1:8000/accounts" ProxyPass "/mailman3/admin" "http://127.0.0.1:8000/admin" ProxyPass "/mailman3/user-profile" "http://127.0.0.1:8000/user-profile" </IfModule> </VirtualHost> Thanks Lars On Mon, Feb 13, 2023 at 05:27:55PM -0800, Mark Sapiro wrote: > On 2/13/23 02:05, Lars Bjørndal wrote: > > > > I've now followed the documentation for configuring Apache here: https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur…. I want both domains to start mailman3 when contacting example1.com/mailman3 and example2.com/mailman3. I have the sam configuration in both virtualhost section in Apache. For example1.com/mailman3, it works perfectly. For example2.com/mailman3 however, the browser (elinks), reports Host not found: example2.commailman3 e.g. without a slash after the domain name. What could cause this to happen? > > > Something wrong in the web server configuration. I can't begin to guess what > without seeing it. > > -- > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to lars(a)lamasti.net

2 years, 9 months

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

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

Search results for query "sapiro"