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

[MM3-users] Re: mailman3 auto-disabling of subscriptions

by Stephen J. Turnbull

Mark Sapiro writes: > Your issue is mail From: the gmail.com domain to the list and sent > to gmail users is being bounced because it fails DMARC. I.e. Gmail > applies a DMARC policy of p=reject to mail From: gmail.com even > though it's published DMARC policy is p=none. Gmail's DSN is so badly worded it's not clear to me *what* it's supposed to mean. I wonder if enabling ARC might not help with getting things through to Gmail. Google was very supportive of the ARC effort. > You need to apply DMARC mitigations to this mail. I agree this is the most straightforward approach. Steve

2 years, 10 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

3 years, 2 months

[MM3-users] Re: user mail not accepted

by Mark Sapiro

On 4/26/21 5:00 PM, Christian Stalberg via Mailman-users wrote: >>From smtp.log > > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'DATA' > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) Data: b'QUIT' > Apr 26 00:17:39 2021 (807) ('127.0.0.1', 38370) connection lost > Apr 26 00:17:39 2021 (807) Connection lost during _handle_client() > Apr 26 00:18:11 2021 (809) > <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> smtp to > ncpoa(a)lists.ccalternatives.org for 83 recips, completed in 29.13376259803772 > seconds > Apr 26 00:18:11 2021 (809) > <019301d73a31$8e8e54e0$abaafea0$(a)ncboliviapartners.org> post to > ncpoa(a)lists.ccalternatives.org from christian(a)ncboliviapartners.org, 5811 > bytes > Apr 26 00:18:11 2021 (809) > <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> smtp > to ncpoa(a)lists.ccalternatives.org for 1 recips, completed in > 0.0420069694519043 seconds > Apr 26 00:18:11 2021 (809) > <161939626169.810.9530678025639681522(a)zarathustra.ccalternatives.org> post > to ncpoa(a)lists.ccalternatives.org from > ncpoa-bounces(a)lists.ccalternatives.org, 869 bytes > Apr 26 11:52:22 2021 (819) > <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> smtp > to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.22335004806518555 seconds > Apr 26 11:52:22 2021 (819) > <161943793957.929.15640398646519288095(a)zarathustra.ccalternatives.org> post > to ssan(a)lists.ccalternatives.org from ssan-bounces(a)lists.ccalternatives.org, > 765 bytes > Apr 26 11:52:22 2021 (819) > <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> smtp > to ssan(a)lists.ccalternatives.org for 2 recips, completed in > 0.05862092971801758 seconds > Apr 26 11:52:22 2021 (819) > <161943793960.929.13309139087156940549(a)zarathustra.ccalternatives.org> post > to ssan(a)lists.ccalternatives.org from noreply(a)lists.ccalternatives.org, 810 > bytes > Apr 26 11:55:22 2021 (819) > <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> smtp > to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.1459965705871582 seconds > Apr 26 11:55:22 2021 (819) > <161943812108.929.10391982256874011271(a)zarathustra.ccalternatives.org> post > to ssan(a)lists.ccalternatives.org from > ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternatives.o > rg, 1526 bytes > Apr 26 12:01:30 2021 (817) Available AUTH mechanisms: LOGIN(builtin) > PLAIN(builtin) > Apr 26 12:01:30 2021 (817) Peer: ('127.0.0.1', 38556) > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) handling connection > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'LHLO > zarathustra.ccalternatives.org' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'MAIL > FROM:<christian(a)sewagesludgeactionnetwork.com>' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) sender: > christian(a)sewagesludgeactionnetwork.com > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'RCPT > TO:<ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternativ > es.org>' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) recip: > ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternatives.o > rg > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'DATA' > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) Data: b'QUIT' It looks like the above 12:01:30 are the relevant entries, and that message was sent to ssan-confirm+2144530ad102026077911eac6eb574bcbd04be92(a)lists.ccalternatives.org which is not the list, but the list's -confirm address. Was the response received by the user a "results of your email commands" message? > Apr 26 12:01:30 2021 (817) ('127.0.0.1', 38556) connection lost > Apr 26 12:01:30 2021 (817) Connection lost during _handle_client() > Apr 26 12:01:34 2021 (819) > <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> smtp > to ssan(a)lists.ccalternatives.org for 2 recips, completed in > 0.06680631637573242 seconds > Apr 26 12:01:34 2021 (819) > <161943849287.814.5890052642238479423(a)zarathustra.ccalternatives.org> post > to ssan(a)lists.ccalternatives.org from noreply(a)lists.ccalternatives.org, 821 > bytes > Apr 26 12:01:34 2021 (819) > <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> smtp > to ssan(a)lists.ccalternatives.org for 1 recips, completed in > 0.04269862174987793 seconds > Apr 26 12:01:34 2021 (819) > <161943849292.814.6140111398379700592(a)zarathustra.ccalternatives.org> post > to ssan(a)lists.ccalternatives.org from ssan-request(a)lists.ccalternatives.org, > 1335 bytes > > > Message sent that only the user receives: What I wanted to see was not the message sent to the list, but the message received by the one user from the list. If you are saying this message is that, it didn't come from any Mailman list. > Return-Path: <christian(a)sewagesludgeactionnetwork.com> > Delivered-To: ces(a)ecovillage.cc > Received: from box.ecovillage.cc ([127.0.0.1]) > by box.ecovillage.cc with LMTP id MDucNBythmCTSwAAMoO61A > for <ces(a)ecovillage.cc>; Mon, 26 Apr 2021 05:07:56 -0700 > X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on box.ecovillage.cc > X-Spam-Level: > X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, > DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE autolearn=ham > autolearn_force=no > version=3.4.2 > X-Spam-Report: > * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -0.1 DKIM_VALID Message has at least one valid DKIM or DK > signature > * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not > necessarily > * valid > * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from > * author's domain > X-Spam-Score: -1.1 > Received: from authenticated-user (box.ecovillage.cc [45.79.28.18]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 > bits)) > (No client certificate requested) > by box.ecovillage.cc (Postfix) with ESMTPSA id 6EADF3E8CC > for <ssan(a)lists.naturalintelligence.us>; Mon, 26 Apr 2021 05:07:54 > -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; > d=sewagesludgeactionnetwork.com; s=mail; t=1619438876; > bh=1M7F/uIS0bNG6cWjecy/a9QjskrHVwJHkjWRv+ffpM4=; > h=From:To:References:In-Reply-To:Subject:Date:From; > b=jXOswVZgFeHBB+sjIDqVkNBQqIbfZCj9ZUfpVwl10NQEkGaoxckPHNOKT6x9zIqsW > BZ7iZqqi2mWprVQ8LrK48Lp7gvCQ/ipqspMeLt3t+uljzTtryHmV6uJFEAU3hqM33Y > nQqX6Z8la8Ko40F9Ayb4h4e/MOfPdA4nadgf5hZzt/DzPFZvzUbG3V8lWcHuyJNA2y > SQkhbNubQ6iNEEB0SyBjoOjl3g3LVxjxY+9kMGGmX+1PFfW90CpDDShRmKkkscEWaA > NiV0fX6U5LENBBnc6Q9ImLgXuaLdCqlBRBumJBk+eUUr007rpXXVAPck2NvUzGyM2v > kNNGlT68hGzEg== > From: <christian(a)sewagesludgeactionnetwork.com> > To: <ssan(a)lists.naturalintelligence.us> > References: > In-Reply-To: > Subject: How US chemical industry lobbying and cash defeated regulation in > Trump era > Date: Mon, 26 Apr 2021 05:07:37 -0700 > Message-ID: <020501d73a94$cbe17440$63a45cc0$(a)sewagesludgeactionnetwork.com> > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_0206_01D73A5A.1F831170" > Thread-Index: Adc6h7I/qzBKx1yOT6aPOuipppacoQACatZAAADW1wA= > Content-Language: en-us > > How US chemical industry lobbying and cash defeated regulation in Trump era > Industry's congressional allies defeated nearly all PFAS legislation while > the Trump EPA killed, watered down or slowalked new rules > > https://www.theguardian.com/environment/2021/apr/26/us-chemical-companies-lo > bbying-donation-defeated-regulation > > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years

[MM3-users] Re: Separating Lists by Domain

by Abhilash Raj

On Thu, Jan 3, 2019, at 2:27 PM, brian(a)emwd.com wrote: > So who manages Postorius? Is that a whole separate application from > Mailman 3? Is there a way we can get whoever the developer is to update > it where we can separate lists by domain the way Hyperkitty does? Mark > Sapiro refers to this in the following post: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… You can file an issue at https://gitlab.com/mailman/postorius/issues > Thanks, > Brian > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 4 months

[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, 6 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

5 years, 10 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, 4 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, 6 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/

3 years, 10 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

10 months, 3 weeks

[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

2 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, 6 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, 7 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, 6 months

[MM3-users] Re: Templates location on the file system

by Odhiambo Washington

On Mon, Feb 13, 2023 at 11:06 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/13/23 08:06, Odhiambo Washington wrote: > > I am reading this: > > https://gitlab.com/mailman/mailman/-/issues/901#note_578684415 > > > > However, I cannot make heads or tails on what is meant by <LC>. > > > Language code. E.g. en for English. See > http://www.lingoes.net/en/translator/langcode.htm for a long list and > > https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/config/schema.… > for those supported by Mailman core. > Thanks for this. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 months

[MM3-users] Re: mm3 installation question

by Stephen J. Turnbull

Mark Sapiro writes: > On 3/6/24 12:56 PM, Odhiambo Washington wrote: > > > Is it possible that an Apache directive like below will fix everything > > (albeit discreetly with sysadmins driving blindly)? > > > > ProxyPass "/" "http://127.0.0.1:8000/" > > That only works if Apache serves only Django and no other URLs. It's reasonable for a few other paths under root, as well. For example, if you have Shibboleth provide SSO capability, it needs access to some path like /Shibboleth/shibboleth_is_here. Then you can place something like ProxyPass "/Shibboleth" "!" # check Apache dox before the ProxyPass "!", which disables the ProxyPass for paths starting with "/Shibboleth". Not scalable or dynamic, obviously.

2 years, 2 months

[MM3-users] Re: LTMP to Postfix problem

by Mark Dadgar

On Jun 18, 2020, at 10:23 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > The grizz.org domain was recently migrated from from a larger server in > a colo that supported multiple domains to a DigitalOcean droplet which > initially had only 4 GB RAM, but that seemed marginally enough at best, > so I upgraded it to 8 GB. My 4GB DO droplet runs a couple of mm3 lists, including one that does ~4000 posts/month times ~400 recipients, running postgres, with no signs of the OOM killer. In fact, the only time I’ve ever seen it is when I was using the mailman3 shell to search for bad characters in the archives the other day. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 10 months

[MM3-users] Re: Help understanding why some users don't receive emails

by Stephen J. Turnbull

Mark Sapiro writes: > On 9/21/22 14:06, Stephen Daniel wrote: > > Looking at one user in particular, I see in /var/log/syslog that postfix is > > sending the email. There is nothing in bounce.log. > <https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS>. It can > also possibly help for the server's domain to publish a DMARC policy > even if that is `p=none` The embarqmail.com domain publishes p=reject. This doesn't affect mail going *to* that domain, but it suggests they're aggressive about "fighting spam". It might help if the mailing list host were to participate in the ARC protocol. Steve

3 years, 7 months

[MM3-users] Re: Can't remove footer(s)

by Henrik Rasmussen

Mark Sapiro wrote: > The templates named list_member_digest_footer.txt and > list_member_regular_footer.txt (with underscores) were created by > import21 and set as the URIs for those templates. Had you just copied > /dev/null (or otherwise made empty) those files and done nothing else, > that would have done what you wanted, but since you deleted the template > URIs for the list, the template names are now the default How do I make these not default? > list:member:digest:footer.txt and list:member:regular:footer.txt names > (with colons) and those are the empty files you need to create. Or when I upgrade to V3.2.2 will I be able to just empty the templates in /postorius/lists/LISTNAME/templates? Henrik

7 years, 6 months

[MM3-users] Re: General question mailman3: message sender acceptance "always"

by Wikinaut

Mark Sapiro wrote: > On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). > > In the Postorius held messages view, click on the message's subject to > open a dialog showing the messages content Dear Mark, sorry: How should I know this? I'd rather prefer to have these both changes: i) relabel the existing one od three buttons from "accept" to "accept once" ; and ii) add a fourth button "accept all messages from this sender (i.e. add to white list)"

2 years, 6 months

[MM3-users] Re: OK, so I backed out completely and re-installed. Here's my *original* error. Should I modify virtual mailbox maps?

by Bill Oliver

On Wed, 2024-10-16 at 12:19 -0700, Mark Sapiro wrote: > On 10/16/24 10:26, Bill Oliver wrote: > > > > > Does the forensicpath.us domain have an alias_domain configured in > mailman causing mailman to create > /opt/mailman/mm/var/data/postfix_vmap > and /opt/mailman/mm/var/data/postfix_vmap.db? You need this. > Thanks for your reply. My wife has fallen ill, so I am taking a break from working on this to take care of her. I'll reply substantively in a week or so, I hope. billo

1 year, 6 months

[MM3-users] Rejection based on total message size including attachments

by leith＠khimaira.com

As a web hosting provider I have searched and searched for a way to limit the total size of messages posted to all lists. We have moderators who just can't get it through their heads to limit the size of attachments. One list today distributed a 6 mb pdf to over 700 recipients. I have found information on creating a custom handler and some old and brief logic on limiting max_message_size from Mr. Sapiro. Would anyone who has developed a custom handler to reject messages based on total size, mind sharing the full file? If so, could you also state where the handler was positioned in the chain of handlers. Thank you for your time.

7 years, 7 months

[MM3-users] Re: Permission denied for fulltext_index

by Jan Eden

On 2022-11-30 06:52, Mark Sapiro wrote: > On 11/30/22 05:32, Jan Eden via Mailman-users wrote: > > > > I tried setting permissions on /opt/mailman/fulltext_index to 777 > > temporarily, but the issue remained (as expected). > > Are you running some security manager (SELinux, apparmor, ???) > > I suspect that's the issue. apparmor is disabled, and the error is only triggered when the directory does not exist: > # Make sure the index is there. > if self.use_file_storage and not os.path.exists(self.path): > os.makedirs(self.path) > new_index = True /opt/mailman/fulltext_index exists (and is populated), so I must assume that the Whoosh backend uses some other (non-writeable) path at this point. - Jan

3 years, 5 months

[MM3-users] Re: Getting original message headers

by Peter Chubb

>>>>> "Mark" == Mark Sapiro <mark(a)msapiro.net> writes: Mark> On 1/5/26 01:32, Peter Chubb via Mailman-users wrote: >> >> We've been seeing some particularly pernicious spammers >> recently. They're using gmail accounts; I'd like to report them to >> Google. Mark> Only minimal information from headers is in the hyperkitty Mark> archive, but the headers should be in the delivered email and in Mark> the message archived by the prototype archiver if enabled Mark> (Mailman's var/archives/prototype/<list_address>/new/) I think they must have been posting via hyperkitty. The first received: line is localhost then the mailman server. Is there a way to turn that ability off? Peter C

4 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Alan So

Mark Sapiro wrote: > In the absence of an issue at > https://gitlab.com/mailman/mailman/-/issues, > probably never. <hint> Is that anyone with a gitlab account can file an issue? If it is appropriate, I can try to file one. > Have you asked Microsoft to fix Outlook to not create these defective > messages? That's the real solution. Yes and I agree. My colleague has actually done so but it is probably not yet escalated to the appropriate tier of support. Here is the comment of my colleague: "I can submit this problem to Microsoft. However, it may take a long time to fix it or not even important enough to be fixed."

5 years, 11 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On Jun 9, 2020, at 1:57 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> THANK YOU for all the help. > > > I'm glad we finally got it resolved. I may have spoken too soon: [ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): XSUBJECT95251413 (pid 729081): Term too long (> 245): XSUBJECT95251413 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/haystack/management/commands/update_index.py", line 97, in do_update backend.update(index, current_qs, commit=commit) File "/usr/local/lib/python3.8/dist-packages/xapian_backend.py", line 492, in update database.replace_document(document_id, document) xapian.InvalidArgumentError: Term too long (> 245): XSUBJECT95251413 "XSUBJECT95251413“ has some serious weirdness embedded in it. Not sure how to search for that in the django shell? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 10 months

[MM3-users] Re: MM3 statistics

by Tom Browder

On Sun, Jul 23, 2017 at 20:57 Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Mark Sapiro writes: > > On 07/20/2017 01:22 PM, Tom Browder wrote: > > > Are there any plugins or programs for mm3 statistics? ... > If you can be more specific about the statistics you want, I can > compare to the Systers' implementation. I have no real thoughts about it. I have been talking up my pending mm3 server to my friends who are familiar with using some the paid mail services that provide various usage stats I assume are like resposnes to marketing mails and such. Our local community and tech groups are always interested in surveys that may be sent by e-mail. Thanks, Steve. -Tom

8 years, 9 months

[MM3-users] Re: /bin/sh: sassc: command not found

by Ralf Wiegand

Thank you Mark, where do I find this section of code? On 4/22/20 2:56 PM, Mark Sapiro wrote: > On 4/22/20 11:38 AM, Ralf Wiegand wrote: >> /bin/sh: sassc: command not found - Not sure on what I am missing? > > You currently have something like: > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > > in your settings. > > Either install sassc or you can install ruby-sass and change the settings to > > COMPRESS_PRECOMPILERS = ( > ('text/x-scss', 'sass -t compressed {infile} {outfile}'), > ('text/x-sass', 'sass -t compressed {infile} {outfile}'), > ) > >

6 years

[MM3-users] Re: Archive date/time vs elapsed time

by Mark

On 2023-06-28 00:42, Mark Sapiro wrote: > On 6/26/23 11:41 PM, Mark wrote: >> >> No, I don't see it on the MM users' archive. >> The archive where I'm seeing it is HyperKitty version 1.3.4 on a >> Debian packaged MM 3.3.3 >> The problem lay therein? > > > I don't know if this is a change since 1.3.4 or an issue with the > Debian package. The latest Debian stable (bookworm) has more up to > date packages if you can upgrade. > > In any case, this does not seem to be an issue in current HyperKitty. > Thank you Mark. I will try out the upgrade and report back.

2 years, 10 months

[MM3-users] Re: Documentation for transferiering a list between mm3 and mm3

by Morris Jones

On 2/26/2021 10:55 AM, Mark Sapiro wrote: > Brian is correct. Essentially, you would need to run database queries to > get all the relevant data from the database and then add it to the > database of the new instance. A tool could be created to do the export > and import, but it doesn't currently exist unless some user has > developed one and not reported it. Would it be unreasonable to do a database dump on the old instance and a restore on the new one? Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 2 months

[MM3-users] Re: Mailman3 not working following distribution upgrade from Debian 10 to 11.

by David Newman

On 1/6/22 2:40 PM, gordon(a)dickens.com wrote: > the mailman3-web and mailman3-full post-installation scripts These look like the Debian packages. Mark Sapiro can speak to this much better than I can, but the packages both on 10 and 11 are outdated and have some components that don't work, or don't work well. Better IMO to uninstall these and install current versions using the venv and web instructions: https://docs.mailman3.org/en/latest/install/virtualenv.html https://docs.mailman3.org/en/latest/config-web.html There is some overlap between these docs, but I can verify that this setup worked on Debian 10, and continued to work after upgrading to Debian 11. dn

4 years, 4 months

[MM3-users] Re: List Migration from MM2.1 -> MM3

by Odhiambo Washington

On Mon, Aug 15, 2022 at 4:59 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/15/22 06:53, Odhiambo Washington wrote: > > > > That is exactly what I have in my mailman.cfg > > > > Installing Postfix suppresses that message though. I installed Postfix > and > > then disabled it. > > > > > Your /opt/mailman/mm/venv/bin/mailman is talking to a different Mailman > core than the one reading that mailman.cfg and the one Postorius is > talking to. > How can I track the one it's talking to? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 8 months

[MM3-users] Re: How to best disable message decoration for all lists defined for a domain

by Ralph Seichter

* Mark Sapiro: > It's still a work in progress. Of course. I did not mean to criticise, just point out what settings I was surprised not to find in the UI. > To not add headers and or footers, you need empty templates for them. > These could be created via the list's Templates form except until [1] > is fixed, you can't make empty templates. I actually found a workaround in the meantime: update template set uri='file:///dev/null' where id=123; Not that I like to modify the underlying database manually, but it seems to do the trick for now. -Ralph

7 years, 1 month

[MM3-users] Execution of msgfmt failed when performing post upgrade steps

by Torge Riedel

Hi, I'm currently running a test setup of MM3 using Mark Sapiros approach with two venv. I also adopted his post-upgrade-script for the web part (django). Just some minutes ago I updated the packages of my test setup with pip3 where hyperkitty is now 1.3.0 When runnin the post-upgrade-script I get the following error message: Execution of msgfmt failed: /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:630: duplicate message definition... /opt/mailman/web/venv/lib/python3.6/site-packages/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po:273: ...this is the location of the first definition msgfmt: found 1 fatal error Not sure whether this is an error of MM3 or one of its dependency packages. Best regards Torge

6 years, 7 months

[MM3-users] Re: mailman3 vs postfix

by Ralf Wiegand

Mark - I have a hard time following this. /path/to/where/your/settings/are located what settings? what do I am looking for? cd /opt/mailman # all mailman applications are under /opt/mailman ls django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty mailman-suite postorius venv-3.6 settings.py? /opt/mailman/mailman-suite/mailman-suite_project? I do not understand??? Ralf On 4/28/20 3:59 PM, Mark Sapiro wrote: > On 4/28/20 12:42 PM, Ralf Wiegand wrote: >> (venv-3.6) [root@empire mailman]# django-admin createsuperuser >> No Django settings specified. > > In that case, you need to specify additional options: > > --pythonpath /path/to/where/your/settings/are located > --settings name_of_your_settings_file_without_the_.py > > e.g. something like > > django-admin --pythonpath /usr/share/mailman3-web \ > --settings settings createsuperuser > >

6 years

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 6:11 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/24/23 16:07, Quanah Gibson-Mount wrote: >> >> Package: mailman3 >> Version: 3.2.1-1 > > For that version pendings don't have a token_owner. This script will > delete all pending subscriptions, even those waiting moderator approval, > so if there are any of those, they should be handled first. > ``` > >>> pendings = getUtility(IPendings) > >>> for token, data in pendings.find( > ... pend_type=subscription): > ... pendings.confirm(token, expunge=True) > ... > >>> commit() > ``` Thanks Mark! I had to change it to pend_type='subscription' but other than that it worked! :) Regards, Quanah

2 years, 11 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Simon Coggins

On 4 Nov 2021, at 11:57 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 11/4/21 1:02 AM, Simon Coggins wrote: > > All I’m doing is literally appending a subset of a hash of the mailing list rcpt address to the front of the message-id, so that if it gets moderated, each instance of the email has a different message-id and each moderation action has it’s own copy of the email to operate on. This seems to have gotten us out of the immediate issues. But I’m eager to find a better solution that might be more permanent. As you have seen, this is new in 3.3.5. I recognize this is a problem. Previously, attempts to accept the message on the second and subsequent lists would throw an uncaught exception - see https://gitlab.com/mailman/mailman/-/issues/914<https://gitlab.com/mailman/mailman/-/issues/914> and this was a fix for that. Yeah I’m seriously amazed we’ve not had complaints in the year we’ve been running mailman3 that people have lost emails to multiple lists. Only now that you fixed the exception have people seen missing emails :) Please file an issue for this at https://gitlab.com/mailman/mailman/-/issues<https://gitlab.com/mailman/mailman/-/issues> and I will try to find a better solution. Your approach of munging Message-IDs will create other issues. Consider a post to a list with direct CC to userx. userx replies-all to the message received directly. the In-Reply-To of this reply is the unmunged Message-ID which will affect threading in the archives and other recipient's MUAs. I realize this is preferable to losing the message, but I hope we can do better. Yeah it’s not a great solution but it’s the quickest I could come up with that works “for us”. 99% of our lists are announcement lists only with minimal replies so while this will break some. I’m hoping it will give us enough time to wait out a proper fix. I’ve created a new issue #955 with as much detail as I think you’ll need. Let me know if you need any more. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org> --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: attachment.png Content-Type: image/png Name: attachment.png Replaced multipart/alternative part with first alternative.

4 years, 6 months

[MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature'

by Mohsen Masoudfar

________________________________ From: Mark Sapiro <mark(a)msapiro.net> Sent: Thursday, April 13, 2023 1:11 PM To: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Transaction failed: Duplicate header 'DKIM-Signature' Thank you Mark, please see below the responses to your questions. On 4/13/23 07:25, Mohsen Masoudfar wrote: > I am observing the following error message in the logs for one specific list: > > = = = > relay=email-smtp.us-east-1.amazonaws.com[35.168.84.210]:587, delay=0.27, delays=0.05/0.04/0.12/0.06, dsn=5.0.0, status=bounced (host email-smtp.us-east-1.amazonaws.com[35.168.84.210] said: 554 Transaction failed: Duplicate header 'DKIM-Signature'. (in reply to end of DATA command)) > = = = This is non-compliant. Various parts of RFC6376, e.g. sections 5.6 and 6.1 clearly anticipate that a message can contain multiple DKIM-Signature: headers. > As I mentioned, this happens for one single list only and this list has not been able to send any email for a week now. After checking mailman-users, I came across the following setting, which seems kind of related to my issue: Is email-smtp.us-east-1.amazonaws.com the outgoing MTA for Mailman. I.e the value reported by `mailman conf -k smtp_host` or perhaps smtp_host is a local MTA which is configured to relay via email-smtp.us-east-1.amazonaws.com? > > # mailman conf -k smtp_host > > [mta] smtp_host: localhost In what log is that message? > > in /var/log/mail.log Presumably this error occurs on Mailman's attempt to deliver the mail to `smtp_host`. Otherwise, I don't see how it affects all mail from this list, but I also don't understand why this list's delivery would be different from other lists. Postfix is running on the local host and in /etc/postfix/main.cf, this is defined: relayhost = [email-smtp.us-east-1.amazonaws.com]:587 > = = = > To distribute messages with valid DKIM signatures, I set > remove_dkim_headers: yes > in /etc/mailman3/mailman.cf > = = = > > Here are my questions: > 1 - I have around 100 lists and this happens for this one list only, so, I am not sure, if the issue might be solved with this change. This setting will remove all DKIM headers from the message as Mailman receives it. Then, it depends on how and how many DKIM signatures are added to the outgoing mail. > > could this have any side effects? Is there a reason that this is NOT set per default? > 2 - Because this happens for this one list only, I would rather change it for this one list only, is there any option available changing it for one list only and not for the whole server? No, there is no such option. The fact that this happens for only one list is very strange. I would need more information to understand why. Do these messages get queued in Mailman's retry queue? If so, if you examine one such message with `mailman qfile`, what are the complete headers from that message. > > /var/lib/mailman3/queue/retry is empty Thanks again. M -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> This message sent to mmasoudf(a)aaas.org

3 years

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

On October 26, 2017 10:05:11 PM EDT, Mark Sapiro <mark(a)msapiro.net> wrote: >On 10/26/2017 06:49 PM, Fabian A. Santiago wrote: >... >> To: >test123-confirm+b7322edad83ae7ec99cfc5100161c7062d2c7685(a)gjb-online.com > > >There is an issue in Mailman 3.1 with regexp tables not working for >addresses of this form. As I posted at ><https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>, >see <https://gitlab.com/mailman/mailman/issues/401> and ><https://gitlab.com/mailman/mailman/merge_requests/323>. That was it. Perfect. I manually modified my regexp map and it works now. Excellent and Thank you. You're the man. Does mm3 ever refresh those maps or only as I add new domains / lists? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 6 months

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 4:25 PM, Mark Sapiro wrote: >> I am not at all fluent in django interactions (I'm still not entirely >> sure of what django actually *is*) so I have some reading to do. Any >> pointers on "django wrangling for n00bs" would be great. As I >> mentioned, I've not been hacking on mm3, just using it. I'm an >> accomplished programmer, but embedded C and assembler are a few >> galaxies away from python and web services! > > > Django is a Python based web framework. It is the framework used to > support HyperKitty and Postorius. To learn more, start at > https://www.djangoproject.com/ I'll get to reading. Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 9 months

[MM3-users] Re: Starting new thread in Postorius -> disappears

by Cameron Smith

Mark, My apologies for not investigating more thoroughly before opening my mouth (so to speak). You are, of course, correct in your analysis of what happened to my emails, and this is not the first time that my email setup has caused me problems. I’ve added my alternate email address to my lists.mailman3.org user profile, so hopefully it won’t happen again. > On 2017.11.29, at 18:09 , Mark Sapiro <mark(a)msapiro.net> wrote: > > On 11/29/2017 05:05 PM, Cameron Smith wrote: >> >> On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. > > > Your post was received: > > Nov 21 14:31:20 mailman postfix/cleanup[15735]: 2B3798008D: > message-id=<836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > Nov 21 14:31:20 mailman postfix/qmgr[20545]: 2B3798008D: > from=<ccsmith(a)mail2.cetsi.com>, size=10048, nrcpt=1 (queue active) > > delivered to Mailman core: > > Nov 21 14:31:20 mailman postfix/lmtp[15737]: 2B3798008D: > to=<mailman-users(a)mailman3.org>, relay=127.0.0.1[127.0.0.1]:8024, > delay=0.31, delays=0.28/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > and immediately discarded: > > Nov 21 14:31:21 2017 (19106) DISCARD: > <836BFAB0-4879-4EDF-9026-FEC17D4A2BEC(a)mail2.cetsi.com> > > >> Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. > > > Possibly you never received a list copy of his message because you were > directly addressed and your list option "Receive list copies (possible > duplicates)" is set to No. > > >> So, what’s going on? > > > As to why your post was discarded, unfortunately, the logs don't give > more info. There are a couple of possibilities. If your post contained > an attachment with Content=Type: application/subtype where sub-type > doesn't contain 'signature' it would have been discarded by a header > filter rule. Also it looks like you sent the message From: > <ccsmith(a)mail2.cetsi.com>. If that is not an address on your > <ccsmith(a)cetsi.com> account, it would have been discarded as a > non-member post. > > >> What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. > > > I see nothing so far to indicate anything at lists.mailman3.org is > broken in this respect. The only "unusual" thing is this is now a new > thread > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, > but presumably that is because your post was in reply to your earlier > post which wasn't archived. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ Cameron Smith Nanaimo, BC tel:1.604.803.0051

8 years, 4 months

[MM3-users] Re: Problem replying via Hyperkitty

by Jeff

I am finally getting around to revisiting the problems I have been having with replying or posting through the web of my Mailman 3 installation. Posts or replies simply disappear. Here is the Django log section from when I did a test post today: [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b HTTP/1.1" 200 388 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/users/30a0c1ee3d8c4c9681cc73ad25c9b00b/addresses HTTP/1.1" 200 824 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 90 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "POST /3.1/members/find HTTP/1.1" 200 1195 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/addresses/address(a)domain.com HTTP/1.1" 200 348 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org HTTP/1.1" 200 480 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname(a)lists.domain.org/config HTTP/1.1" 200 3878 "-" "GNU Mailman REST client v3.3.3" [26/Jul/2022:10:19:22 -0400] "GET /3.1/lists/listname.lists.domain.org/member/address%40domain.com HTTP/1.1" 200 544 "-" "GNU Mailman REST client v3.3.3" Nothing at all appeared in the Mailman log or the MTA log. Does anyone have any idea what is happening to the posts or what I can do to troubleshoot? Thanks much! > On Jun 30, 2022, at 6:44 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/30/22 10:07 AM, Jeff wrote: >> Hello Everyone, >> A few of my users read our mailing list through Hyperkitty. Whenever they reply through the web, their replies simply disappear. One example from today was logged as follows: >> [pid: 2287|app: 0|req: 116007/153551] xxx.xx.xx.xx () {72 vars in 1992 bytes} [Thu Jun 30 11:26:16 2022] POST /archives/list/listname(a)domainname.org/message/46WUOPZITVMKJN4TXR6CP3WMFUEAVJKD/reply => generated 3213 bytes in 70 msecs (HTTP/1.1 200) 6 headers in 188 bytes (3 switches on core 0) > > > This looks like the post of the reply to HyperKitty. What does the user see in response to that? > > There should be a brief alert popup indicating the message was sent. > > >> A couple of basic questions: >> 1) when a users replies in this manner, does their response go to the list or to the subscriber to whom they are replying? > > To the list. > > >> 2) what log files could I check to see what — if anything — happens to these emails? > > Mailman's var/logs/mailman.log, The MTA logs and the Django logs. > > >> 3) Are there any settings that need to be set to make this work? > > There shouldn't be as long as the list and archiving work. > > Note, a user can select 'Use email software' when replying which should open a composition dialog in their email client to post a reply yto the list. > > > -- > 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/

3 years, 9 months

[MM3-users] Re: Installation Wooes

by Samir Faci

@Marc disregard the direct email I sent you. Okay, so just to clarify both postfix and mailman are running on the same host. In theory, everything should be able to connect to localhost on port 25 to be able to send any emails it needs. 198.199.98.177 resolves is already added to my networks, but I added it explicitly. mydestination = $myhostname, localhost.localdomain, localhost, $mydomain, lists.domain.org, 198.199.98.177 I tried setting the values to the dns name which resolves to the public IP and the 127.0.0.1 and right now I keep on seeing these errors: connect to lists.geekbeacon.org[198.199.98.177]:8024: Connection refused So, I ended up having to tweak my /etc/hosts file a bit as well as ``` smtp_host: lists.domain.org smtp_port: 25 smtp_user: smtp_pass: # Where the LMTP server listens for connections. Use 127.0.0.1 instead of # localhost for Postfix integration, because Postfix only consults DNS # (e.g. not /etc/hosts). lmtp_host: lists.domain.org lmtp_port: 8024 ``` So, now it's finally working but here's a question. Does 8024 need to be publically accessible from the outside? On Sun, May 3, 2020 at 8:32 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 8:13 PM, Samir Faci wrote: > > > > Postfix Failed Logs. > > > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=0/1 rset=1 quit=1 commands=4/5 > > May 4 03:07:36 lists postfix/smtpd[1968155]: connect from > > unknown[198.199.98.177] > > May 4 03:07:36 lists postfix/smtpd[1968155]: 745B31473C6: > > client=unknown[198.199.98.177] > > May 4 03:07:36 lists postfix/cleanup[1968158]: 745B31473C6: > > message-id=<158856165549.136760.840427238489827082@lists> > > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: > > from=<booh-bounces(a)lists.domain.org > > So mailman and Postfix are on different machines. That may complicate > things, but > > > > <mailto:booh-bounces@lists.domain.org>>, size=5474, nrcpt=1 (queue > active) > > May 4 03:07:36 lists postfix/smtpd[1968155]: disconnect from > > unknown[198.199.98.177] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 > > May 4 03:07:36 lists postfix/lmtp[1968159]: 745B31473C6: > > to=<booh-owner(a)lists.domain.org <mailto:booh-owner@lists.domain.org>>, > > relay=lists.domain.org <http://lists.domain.org>[198.199.98.177]:8024, > > delay=0.03, delays=0/0/0/0.02, dsn=2.0.0, status=sent (250 Ok) > > This was a successful delivery. > > > > May 4 03:07:36 lists postfix/qmgr[1964759]: 745B31473C6: removed > > May 4 03:07:38 lists postfix/smtpd[1968155]: connect from > > unknown[198.199.98.177] > > May 4 03:07:38 lists postfix/smtpd[1968155]: NOQUEUE: reject: RCPT from > > unknown[198.199.98.177]: 554 5.7.1 <csgeek(a)domain.com > > <mailto:csgeek@domain.com>>: Relay access denied; > > from=<booh-bounces+csgeek=domain.com(a)lists.domain.org > > <mailto:domain.com@lists.domain.org>> to=<csgeek(a)domain.com > > <mailto:csgeek@domain.com>> proto=ESMTP helo=<[127.0.1.1]> > > You are sending from a remote machine 198.199.98.177 to a presumably > remote domain domain.com so relay access is denied as it should be. > > You need to add 198.199.98.177 to mynetworks in Postfix. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

6 years

[MM3-users] Re: Whitelist non subscriber

by Barry Warsaw

On Aug 10, 2017, at 13:05, Mark Sapiro <mark(a)msapiro.net> wrote: > > Mailman 3 defines the list attribute accept_these_nonmembers, but it is > not currently implemented to actually have any effect, nor is it exposed > in Postorius. Yes, that attribute is deprecated and (almost) completely removed. > At the present, I think you would have to create a user record with the > address and add that user to all lists with role nonmember and > moderation_action 'defer' to apply subsequent tests or 'accept' to > unconditionally accept posts from that address. That’s the way it should be done. Those actions may not be exposed yet in Postorius or the CLI, so you might have to do it with a `wishlist` script. -Barry

8 years, 8 months

[MM3-users] Re: Errors while importing mm2 list archives

by Odhiambo Washington

On Sat, Dec 10, 2022 at 9:45 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/10/22 01:13, Odhiambo Washington wrote: > > On Thu, Dec 8, 2022 at 10:41 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> In the DATABASES['default'] definition, you need to set `'OPTIONS': > >> {'charset': 'utf8mb4'}` > >> > > > > I added that: > > > > [database] > > class: mailman.database.mysql.MySQLDatabase > > url: mysql+pymysql://mailman_user:XXXXXXXXX@localhost > > /mailmansuite?charset=utf8mb4&use_unicode=1 > > > The above is for Mailman core. It doesn't affect HyperKitty. For that > you need to look at the DATABASES definition in > /etc/mailman3/settings.py > < > https://docs.mailman3.org/projects/mailman-web/en/latest/settings.html#mail…> > > and ensure that in addition to the other settings under `default {` you > have > ``` > 'OPTIONS': {'charset': 'utf8mb4'}, > ``` > > ... > >> You might also need to modify the tables, particularly hyperkitty_email > >> with something like > >> ``` > >> ALTER TABLE hyperkitty_email > >> DEFAULT CHARACTER SET utf8mb4, > >> MODIFY subject varchar(512) > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci, > >> MODIFY content > >> CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci; > >> > > > > > > So I removed my list, dropped the database, and proceeded as follows: > > > > create database mailmansuite CHARACTER SET utf8mb4 COLLATE > > utf8mb4_0900_ai_ci; > > ALTER TABLE hyperkitty_email DEFAULT CHARACTER SET utf8mb4; > > ALTER TABLE hyperkitty_email MODIFY subject varchar(512) CHARACTER SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY content longtext CHARACTER SET > utf8mb4 > > COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY sender_name varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > ALTER TABLE hyperkitty_email MODIFY in_reply_to varchar(255) CHARACTER > SET > > utf8mb4 COLLATE utf8mb4_unicode_ci; > > > > I did all those (although looks overzealous) just to be on the safe > side. I > > have seen people putting emojis in their names. > > > None of that should be necessary. `mailman-web migrate` should create > the database and tables as needed. > > > > After that, I did the mailman-web migrate, created the list, imported the > > config from MM2 and then proceeded to import the archives. > > However, the errors still are there, and several messages were not > imported > > Do you have the OPTIONS setting in your DATABASES definition in > settings.py? > Here is what I have tested lately in settings.py: # MySQL Database setup DATABASES = { 'default': { 'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailmansuite', 'USER': 'mm3', 'PASSWORD': 'XXXXXXXXX', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': { 'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4', }, } } I have dropped the DB, recreated, run the 'migrate', created the list, imported config from MM2. However, nothing seems to be able to address the errors with importing the archives. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: Issues with cross posted emails after upgrading to mailman 3.3.6

by Stephen J. Turnbull

Mark Sapiro writes: > Thanks for filing the issue. I'll work on a solution. My current > thinking is to add a `count` column to the message table, set the count > to 1 when initially adding a message-id, increment the count when adding > an existing message-id, decrement the count when deleting a message-id > and only delete the entry and message when the count reaches 0. Are we guaranteed to get a separate LMTP delivery for each list? That is, if the MTA receives 2 RCPT TOs to lists for one transaction, won't it do the same in LMTP when it sends forwards the message to Mailman? Steve

4 years, 6 months

[MM3-users] Re: Disabling mail/news gateway was: Moderation action "None" is misleading

by Ron / BCLUG

Mark Sapiro wrote on 2025-02-05 12:48: > As of Mailman 3.3.10 (not yet released) the nntp runner is not started > by default. This is a welcome change, thank you. > For older releases you can add > ``` > [runner.nntp] > start: no > ``` > to mailman.cfg I've been digging into MM3 resource usage vs MM2 and have been wondering: are there any other runners that can be disabled, or invoked via cron job to run every $interval then exit again? Second question, similar topic but MM2: how to disable NNTP? (if that's what this is doing): /usr/bin/python2 /var/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s Thanks again.

1 year, 3 months

[MM3-users] Re: Migrating Mailman 3 lists

by Andrew Hodgson

Mark Sapiro wrote: >On 5/19/20 7:25 PM, Mark Dadgar wrote: >> >> I get a bunch of these errors because identifiers in postgres are limited to 63 characters and mm3 creates some in sqlite that are longer than that: >> >> 2020-05-20T02:16:20.574000Z WARNING PostgreSQL warning: identifier "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6b632_uniq" will be truncated to "idx_44731_auth_user_user_permissions_user_id_permission_id_14a6" [...] >> For reference my pgloader script looks like: >> >> load database >> from sqlite:///var/lib/dbconfig-common/sqlite3/mailman3-web/mailman3web.db >> into postgresql://mailman3:XXREDACTEDXX@localhost/mailman >> >> with include drop, create tables, create indexes, reset sequences, no >> truncate Have you tried this without indexes and then run the migrate script? It may re-create them as part of the schema upgrade check. Andrew.

5 years, 11 months

[MM3-users] Re: list footer questions

by Mohsen Masoudfar

Hi, Thanks again for your help. When I check the postorius version, it says 1.1.2-3: [509]# apt list | grep postorius python-django-postorius/bionic,now 1.1.2-3 all [installed,automatic] It is on Ubuntu18.04 and has been installed with Ubuntu package Mailman-full. There is no update available yet. So it looks like I cannot use the easy way of modifying the templates. Question: Is there a way to achieve the same by updating the code? Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 8, 2020 4:44 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: list footer questions [EXTERNAL EMAIL] On 5/8/20 12:52 PM, Mohsen Masoudfar wrote: > Hi, > > This seems to me like basic simple questions, I have tried FAQ and other resources, with not much success. > > I have two questions: > > 1. When I send an email to a list, in gmail and yahoo I see the following text with the links at the end of the email body: > _______________________________________________ > Testlist_dmark1 mailing list - > listname(a)domain.tlb<mailto:testlist_dmark1@newlistserv.aaas.org> > To unsubscribe send an email to listname-leave(a)domain.tlb > > In<mailto:listname-leave@domain.tlb%0b%0bIn> outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? There are a few things going on here. First, the actual footer is _______________________________________________ Testlist_dmark1 mailing list - listname(a)domain.tlb To unsubscribe send an email to listname-leave(a)domain.tlb The <mailto:...> links are added by the Mail client displaying the mail. > In outlook this is added as an attachment in the form of a TEXT file, when you open it, you see the same text. > Question: Is there a way to change this, that it looks in outlook the same way as it appears in gmail/yahoo? > > I know MS does it own stuff sometime and we have no impact on that, but I was thinking maybe we might change the footer in a way that outlooks sees that as part of email body. Yes, this is an outlook thing, but you do have some control. See the FAQ article at <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.list…> for a more detailed explanation, but the issue is that after any content filtering has been applied, the message is still multipart so Mailman adds the footer as a separate MIME text/plain part at the end of the message. You can avoid this by doing heavy content filtering on the messages. Namely, accept only multipart, text/plain and text/html, collapse alternatives and convert html to plain text. Note that some of this involves updating the list's pass_types which is not exposed in Postorius before 1.3.3 which is not yet released. > 2. How may I change the format and the text in footer? > I was expecting it under list > setting, in postorius, but I could not find it. It's the top level Templates tab in Postorius (just left of Settings). It was added in Postorius 1.2.1. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 11 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Odhiambo Washington

On Sun, Apr 3, 2022 at 12:06 PM Yvan ♞ <elemac(a)free.fr> wrote: > Hello every body > I have progress to try to reinstall mailman3 on yunohost server but I > still have an error, if somebody can help me as I don't understand the log > https://paste.yunohost.org/raw/ugijepuyuv > Sincerely. > Yvan > Hi Yvan, As previously advised by Mark Sapiro, you are better off taking to the YunoHost support people for help. They will most likely help you with the failing dependencies issue. But I also wonder - why don't you follow the virtualenv method to install? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

4 years, 1 month

[MM3-users] Re: Subscribing users stuck in pending hell

by Quanah Gibson-Mount

--On Wednesday, May 24, 2023 10:13 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This was added in Postorius 1.3.0 which was released almost 4 years ago. > If you can't upgrade, see > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/messa > ge/6GKWYT3ZMXPHMGSXUW6OI6J2222AR7OV/ for a mailman shell script. That shell script seems to have errors: >>> pendings = getUtility(IPendings) >>> for token, data in pendings.find( ... token_owner=TokenOwner.subscriber, ... pend_type='subscription'): ... print("hello") ... Traceback (most recent call last): File "<console>", line 3, in <module> File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) TypeError: find() got an unexpected keyword argument 'token_owner' --Quanah

2 years, 11 months

[MM3-users] Re: Hyperkitty is not archiving due to 405 error - GET instead of POST

by Matthias

Hi Mark, Mark Sapiro wrote: ... > You could always try adding additional logging to > mailman_hyperkitty/__init__.py to log the entire result, but I suspect > the issue is that there is a redirect somewhere in the path from the > configured HyperKitty base_url (see mailman_hyperkitty.cfg) and the > actual HyperKitty API that is redirecting the POST to a GET and also > dropping the POST data. Thanks a lot...I assumed already the same, but your sentence was giving me again some hint...and I found the base_url...there it wasn't httpS but http, which then was redirected and lost the POST... Now it is working as intended! Great, Thanks, Matthias

2 years, 2 months

[MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list

by Mohsen Masoudfar

Hi Mark, Thanks again for the helpful hint. It seems that I still miss something. I am running Mailman3.1.1. I ran the following on my test server. I am trying, for test purpose only, to filter PDF attachments. First I just used the pass_type, assuming once this is set, everything else is filtered. # mailman withlist testlist3(a)x.com >>> m.pass_types = ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>> commit() >>> print(list(m.pass_types)) ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] This let PDF be send by Mailman3. Well, I need to add filter_types too, so I did this: >>> m.filter_types = ['application/pdf'] >>> commit() >>> print(list(m.filter_types)) ['application/pdf'] Mailman3 still distributes PDF files as attachment. What am I doing wrong? This is the final settings: >>> print(list(m.pass_types)) ['multipart', 'message/rfc822', 'text', 'application/pgp-signature'] >>> print(list(m.filter_types)) ['application/pdf'] Thanks Mohsen Thanks Mohsen -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Wednesday, September 30, 2020 1:07 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: How to prevent members to attach executables (exe, bat, ...) to the emails sent to list [EXTERNAL EMAIL] On 9/30/20 9:25 AM, Mohsen Masoudfar wrote: > Hi, > > I am trying to find a way for content filtering to remove executables from the emails sent to the list. I found some hints under: > https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail > man.readthedocs.io%2Fen%2Fstable%2Fbuild%2Flib%2Fmailman%2Fhandlers%2F > docs%2Ffiltering.html%3Fhighlight%3Dcontent%2520filter&data=01%7C0 > 1%7Cmmasoudf%40aaas.org%7Ceb728218f9884b4bfc1a08d865635075%7C2eebd8ff9 > ed140f0a15638e5dfb3bc56%7C0&sdata=mGUdz5NfrJgEyPmd5Isa0l01WWPQMpTA > 9thyWLZ0qbU%3D&reserved=0 > > but still not clear how to do it for all type of excecutables. There are four list settings that affect this. They are pass_types, pass_extensions, filter_types and filter_extensions. the pass_* settings specify message parts the list will accept while the filter_* settings specify message parts the list won't accept. The page at <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.r…> only discusses filter_types and needs updating for the others. Filtering by extension only works on message parts that have an associated file name. Thus, while you can add things like 'exe', 'bat', 'cmd', 'com', 'pif', 'scr', 'vbs' and 'cpl' to filter_extensions, it won't be completely effective. A better approach is to use MIME types[1] and only allow those you want. For a discussion list, a reasonable set is what this list uses: multipart message/rfc822 text application/pgp-signature This will accept any multipart and message/rfc822 parts for further analysis and ultimately accept only text/* and application/pgp-signature elemental parts. If you want to accept images and pdfs, you can add image application/pdf See <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.iana.…> for a list of all registered MIME types. Note that these are all of the form main_type/sub_type and putting just main_type in *_types passes or filters all subtypes for that maintype. [1] You can use both, e.g. filter_extensions to remove those you don't want and pass_types to accept the MIME types you do want. -- 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…

5 years, 7 months

[MM3-users] Re: Recommended way to backup a mailman3 instance

by Andrew Hodgson

Mark Sapiro wrote: >On 4/17/20 4:51 PM, Abhilash Raj wrote: >> >> If they are empty, perhaps the digest creation process should just re-create them instead of failing to create/send digests? We don't really need the directory structure to exist. >I created <https://gitlab.com/mailman/mailman/-/issues/699> for this. In my situation I noticed the directories weren't created very quickly as my Exim config looks for the list directories to identify whether that address exists. I don't know how Postfix does the aliasing but for my case it would make sense to get the directories created as soon as possible, not sure if the digest handler would be soon enough or not. Thanks. Andrew.

6 years

[MM3-users] Re: The dread "relay access denied" error

by Bill Oliver

On Sat, 2024-11-02 at 16:48 -0700, Mark Sapiro wrote: > On 11/1/24 19:07, Bill Oliver wrote: > > > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 mail.bill- > > oliver.com bill-oliver.com lists.bill-oliver.com > > I suspect this is the issue. mynetworks is a list of network > addresses > or network/netmask patterns. Domain names don't work. set > > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > 162.144.108.19 > Doh. That was exactly it. Thanks. There's another 20 hours of my life I'll never get back again... I ended up having to add my explicit IP address, but I dropped the names and it worked. Now it's running like a charm. Thank you so much. billo

1 year, 6 months

[MM3-users] Re: Excluding archives from a mailman3web database backup

by Andy Smith

Hi Mark, On Thu, Jun 23, 2022 at 09:43:10PM -0700, Mark Sapiro wrote: > On 6/23/22 17:38, Andy Smith wrote: > > is it safe to just exclude every table starting with > > "hyperkitty_" from the database backup of mailman3web? Dumping > > only the schema for these, I mean, so that an import would > > restore empty tables. > > That should be safe. The hyperkitty_import job should populate the tables as > necessary. You will lose things like favorites, last views, tags and votes, > but that may not be important. Thanks. In case it's useful for anyone, here is a script I came up with for this: https://gist.github.com/grifferz/6c6033c3067db5883c6413f653705691#file-mail… Cheers, Andy

3 years, 10 months

[MM3-users] Re: list's RSS feed has wrong URLs (base path instead of subdomain)

by roughnecks

Il 28/05/2025 05:41, Mark Sapiro ha scritto: > On 5/27/25 10:48, Simone via Mailman-users wrote: >> >> I have set this up and it's working well so far, but today I noticed >> that links in list's RSS feed point to https://mydomain.tld, while >> mailman is running on https://lists.mydomain.tld. >> >> I wouldn't know how to fix this.. any hints? > > I'm not seeing this in, e.g., output from https://lists.mailman3.org/ > archives/list/mailman-users(a)mailman3.org/feed/ > No worries, it was about the site domain setting. As soon as I fixed it, everything came back alright.

11 months, 1 week

[MM3-users] Re: Column 'starting_email_id' cannot be null

by Peppo Brambilla

On 18.08.25 12:42, Mark Sapiro wrote: > On August 18, 2025 9:35:13 AM GMT, Odhiambo Washington via Mailman-users <mailman-users(a)mailman3.org> wrote: >> It looks like you did not run some migrations. >> However, because this is packaged Mailman3, I am not sure I know how to do >> that. > > Django-admin migrate > > Where Django-admin is whatever the name of the Django admin command is. > > However, the primary support resource for the Debian/Ubuntu package is Debian. See <https://wiki.list.org/x/12812344>. > > On Debian the command is mailman-web migrate Cheers -- Peppo -- Universität Bern Phil.-nat. Fakultät Institut für Informatik Dr. Peppo Brambilla Systemadministrator Neubrückstrasse 10 3012 Bern Schweiz Telefon +41 31 684 33 10

8 months, 2 weeks

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 5, 2020, at 2:27 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/5/20 8:55 AM, Mark Dadgar wrote: > >> ERROR/MainProcess] Failed indexing 1 - 1000 (retry 5/5): Term too long (> 245): >> XSUBJECT95251413 > > It isn't clear from looking at it and I never would have noticed had I > not happened to look at the raw email with less, but the > XSUBJECT95251413 in the above is the entire long word. This is how less > displays it > >> XSUBJECT9<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>2<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>5<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>4<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>1<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B>3<U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B><U+200B> > > > Each of those <U+200B> represents a unicode zero width space. That’s gnarly. BTW, the patch did not fix it. I haven’t had a chance to look more deeply into it yet. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

6 years

[MM3-users] Re: only show mail domains from web host on web-host-url

by Jens Günther

Just checked again and saw: - in the setup it works perfectly in Hyperkitty, that's nice - for the first web host I have 2 mail domains registered, so it also matches (unfortunately) with what you said :-( Anyway, I dceleted one of it, still both lists are shown on either web host, so it's generally not working. If I can do something on this issue, please advise me. Thanks. Am 19.03.21 um 17:21 schrieb Mark Sapiro: > FILTER_VHOST is problematic. It works fairly well for HyperKitty, but > not so well for Postorius. In particular with Postorius it doesn't work > if there is more than one mail host domain with the current web host.

5 years, 1 month

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

by Onyeibo Oku

On Mon, 31 Oct 2022 09:38:37 -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 10/31/22 00:17, Onyeibo Oku wrote: > > > > It is not finding the logger file. The other django project on this > > machine is running fine. I can confirm that the logger plugin is > > installed. I must be missing something. > > If you are following > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… > take note of > ``` > # Make sure that this directory is created or Django will fail on > start. LOGGING['handlers']['file']['filename'] = > '/opt/mailman/web/logs/mailmanweb.log' > ``` > The file and exact path is existing. I made sure of that. Regards Onyeibo

3 years, 6 months

[MM3-users] Re: Installing mailman 3

by Simon Hanna

On 07/22/2017 03:46 AM, Rafael Mora wrote: > Can I use it for mailing lists? like MailChimp? > > El vie., 21 jul. 2017 a las 20:34, Mark Sapiro (<mark(a)msapiro.net>) > escribió: > >> On 07/21/2017 06:07 PM, Rafael Mora wrote: >>> I want to use Mailman to send emails to our customers. I would highly recommend using a service like MailChimp. MailChimp has a decent free tier and if you are above that, I'm not sure if you can handle configuring Postfix the right way. It's not my intention to be demeaning or anything, but it sounds like that would be a little too complicated for you... (I wouldn't want to manage a Mailserver in charge of tens of thousands of emails per month)

8 years, 9 months

[MM3-users] Re: MM3 generates long lines?

by Andreas Barth

* Mark Sapiro (mark(a)msapiro.net) [210623 16:21]: > On 6/23/21 7:10 AM, Andreas Barth wrote: > >One question, in order to ease debugging, can I forcefully activate > >the prototype archiver from the global configuration, or do I need to > >do that on a per-list basis? > > You need > > [archiver.prototype] > enable: yes > > in mailman.cfg. I'm not sure if that's enough for existing lists. > You may need to activate the archiver per list. Thanks Mark, that's what I did. After the restart I needed to activate it on a per-list basis. However, I'd prefer to be able to do that on global basis. Not a big issue, but still thought it worth asking. Andi

4 years, 10 months

[MM3-users] Re: mailman3 + postfix + dovecot + postfixadmin

by Geoff Nordli

On 2022-07-03 12:40 p.m., Mark Sapiro wrote: > On July 3, 2022 12:18:38 PM PDT, Geoff Nordli <geoffn(a)gnaa.net> wrote: >> Hi. >> >> Did anyone figure out the issue or have a working configuration with this: >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> I am getting the same error, with the same configuration. > > Did you read the whole thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > The OP posted his solution, and there is other information there too. > > Thanks, I didn't clue in that I was at the "message" level of thread and didn't see the entire thread. I will read through it.

3 years, 10 months

[MM3-users] Re: Delete a single email or thread from hyperkitty archive

by Andrew Bernard

Logged in a superuser, Mailman3, I am unable to see delete message above tags, only delete thread. I am unable to view a reply as a single message. What I am fundamentally missing? Andrew On 16/07/2019 3:02 am, Mark Sapiro wrote: > An example of thread view is > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…>, > and a message view is > <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> > > > You won't see the Reattach this thread, Delete this thread or Delete > this message links on those pages because you must be a superuser to see > them, but they are in the right sidebar just above TAGS. >

6 years, 9 months

[MM3-users] Re: How can i suppress sending moderation mail to all owners?

by Markus Grandpré

Thank you for you instant response. Best, Markus Am 8/11/25 um 12:46 schrieb Mark Sapiro: > On August 11, 2025 9:48:00 AM GMT, "Markus Grandpré" <markus.grandpre(a)uni-konstanz.de> wrote: >> >> How can I configure the list settings the way that emails intended for moderators are delivered only to them, and not to the owners/administrators of the list? > > You can't. You could modify code to do this either unconditionally or per list, but there is currently no configuration to do this. > L > -- Markus Grandpré (he/him) Universität Konstanz Kommunikations-, Informations- und Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur Sachgebiet Diensteadministration 78457 Konstanz Tel: +49 7531 88-4342D

8 months, 3 weeks

[MM3-users] Re: How to identify the exact reason behind the shunting of the mails ?

by Shashikanth Komandoor

Dear Mark, FYI, I observed this issue with the postfix that receives the mails from the previous MTA and hands it over to the mailman. But I fixed at postfix by upgrading it to the version postfix 3. But still Mailman is not able to understand Hindi (Indian local language) in which language the display names of the email ids are there. So, now what to do at Mailman so that it can also understand local languages or any work around or other alternate solutions for these sort of cases. On Fri, Jun 18, 2021 at 4:04 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Thank you Mark for your immediate response. > > The below are the tracebacks I could find in the mailman log. > > > > > > > > > > > > > > > > > *Jun 17 19:04:08 2021 (8642) Uncaught runner exception: sequence item 0: > expected str instance, Header foundJun 17 19:04:08 2021 (8642) Traceback > (most recent call last): File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 173, in > _one_iteration self._process_one_file(msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/core/runner.py", line 266, in > _process_one_file keepqueued = self._dispose(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/runners/pipeline.py", line 37, in > _dispose process(mlist, msg, msgdata, pipeline) File > "/var/lib/mailman/mailman/src/mailman/core/pipelines.py", line 50, in > process handler.process(mlist, msg, msgdata) File > "/var/lib/mailman/mailman/src/mailman/handlers/avoid_duplicates.py", line > 59, in process addrs = getaddresses(msg.get_all(header, [])) File > "/usr/lib64/python3.6/email/utils.py", line 112, in getaddresses all = > COMMASPACE.join(fieldvalues)TypeError: sequence item 0: expected str > instance, Header foundJun 17 19:04:08 2021 (8642) SHUNTING: > 1623936848.367641+4753f8127953071ddcabfe828ebe72fcf04d0ae2* > > In the shunt file, I see something like this as below in CC while To is > good: > > > > > > > > > *Cc: > =?unknown-8bit?q?=22Support_Zimbra=22_=3Csupport-zimbra=40nic=2Ein=3E=2C?= =?unknown-8bit?b?ICLgpLbgpLDgpKYg4KSu4KS+4KSl4KWB4KSwIC0gU2hhcmFkIE1hdGh1ciIgPHN1cHBvcnQtdmFqcmFAc3VwcG9ydGdvdi5pbj4s?= =?unknown-8bit?b?ICLgpLDgpL7gpJzgpYfgpLYg4KS44KS/4KSC4KS5IC0gUmFqZXNoIFNpbmdoIiA8cmFqc0BuaWMuaW4+LA==?= =?unknown-8bit?b?ICJTYWJ5YXNhY2hpIENob3VkaHVyeSIgPHNhYnlhQG5pYy5pbj4sIG1haWxhZG1pbkBuaWMuaW4s?= =?unknown-8bit?b?ICJNUklUVU5KQVkgS1VNQVIiIDxta0BuaWMuaW4+LCAiQmhyaWd1IEt1bWFyIiA8YmhyaWd1QG5pYy5pbj4s?= =?unknown-8bit?b?ICJPbSBQcmFrYXNoIiA8b3AubmhxQG5pYy5pbj4sICJIYXJpaGFyYW4gTSIgPGhhcmloYXJhbi5tQGdvdi5pbj4s?= =?unknown-8bit?b?ICJQaGlzaGluZyBQaGlzaGluZyIgPHBoaXNoaW5nQG5pYy5pbj4sICJpbmNpZGVudCIgPGluY2lkZW50QG5pYy5pbj4s?= =?unknown-8bit?b?ICJNYW5hdiBSYWtoZWphIiA8bWFuYXYucmFraGVqYUBuaWMuaW4+?=* > > Also, I came to know that two of the recipients in CC block have their > mail ID display name in their local language. While I am not sure, I doubt > if it could be the issue of getting shunted. > > Please confirm and suggest any solution. > > > > On Thu, Jun 17, 2021 at 8:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 6/17/21 6:56 AM, Shashikanth Komandoor wrote: >> > >> > Is there any chance to find out the reason for shunting of the >> > mails through any means ? >> > >> >> >> Look in Mailman's var/logs/mailman.log for the tracebacks associated >> with the shunted messages. >> >> -- >> 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/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 10 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > > Thank you. I tested that DSN with current flufl.bounce and it is > recognized as a temp failure for the reported address and that in turn > should just be ignored by Mailman's bounce runner and not reported as > unrecognized. > > What version of Mailman core is this and what version of flufl.bounce? > Sorry, meant to reply on list with the rest of the details, but got distracted by making dinner. So it sounds like the problem is old versions of flufl.bounce. This particular machine is running debian oldstable, so things are a bit out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look into upgrading at least flufl.bounce. thanks for your help, David

4 years, 6 months

[MM3-users] Re: Custom templates (was: Re: Re: nginx configuration on a multitasking server)

by David Newman

On 1/14/22 8:18 PM, Mark Sapiro wrote: >> https://${domain}/mailman3/lists/${short_listname}.${domain}/ > > FYI, ${short_listname}.${domain} is the same as ${list_id} Good to know. Thanks. > Also, ${domain} as the web site address may not be appropriate. For > example, on this list $domain is `mailman3.org`, but the base URL for > Postorius is `https://lists.mailman3.org/mailman3` and > `https://mailman3.org/mailman3` doesn't work. There is no replacement > for the web domain if it's different from the email domain for the same > reason that there are no web URLs in the default templates. Is there a variable for the base Postorius URL? Something like: https://${baseVarName}/lists/${list_id} Thanks dn

4 years, 3 months

[MM3-users] Re: mailman-web compress - Invalid template socialaccount/login_cancelled.html

by Odhiambo Washington

On Sat, Oct 28, 2023 at 9:46 PM Mark Sapiro <mark(a)msapiro.net> wrote: > This is definitely an issue with django_allauth 0.58. See > https://github.com/pennersr/django-allauth/issues/3503 and > https://github.com/pennersr/django-allauth/pull/3504 Thank you for following up on the fix. Consequent upon this django-allauth issue and the previous issue with psycopg2, how likely is it that new MM3 installations will suffer the effects? I am asking because I am doing my tests on a relatively vanilla system and just following the official documentation sin any deviations. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 6 months

[MM3-users] Re: Upgrade

by Darren Smith

Further debugging - using the python3.6 from the virtual environment where mailman is running, it looks like it is trying to use utf-8: >>> import locale >>> import codecs >>> print(locale.getpreferredencoding()) UTF-8 >>> print(codecs.lookup(locale.getpreferredencoding()).name) utf-8 >>> Thoughts? On Mon, Apr 16, 2018 at 11:29 AM, Darren Smith <silas.crutherton(a)gmail.com> wrote: > By the way, in reading the URL in the error, I attempted to set the LANG > and LC_ALL to en_US.utf8 (as was found in the error) but it still does not > work. > > > > On Mon, Apr 16, 2018 at 11:26 AM, Darren Smith <silas.crutherton(a)gmail.com > > wrote: > >> Nice...spoke too soon. >> >> Mailman info works, but when attempting to start mailman I'm now getting >> this: >> >> Traceback (most recent call last): >> File "/opt/mailman3/conda/bin/mailman", line 11, in <module> >> sys.exit(main()) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 722, in __call__ >> return self.main(*args, **kwargs) >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/core.py", >> line 676, in main >> _verify_python3_env() >> File "/opt/mailman3/conda/lib/python3.6/site-packages/click/_unicodefun.py", >> line 118, in _verify_python3_env >> 'for mitigation steps.' + extra) >> RuntimeError: Click will abort further execution because Python 3 was >> configured to use ASCII as encoding for the environment. Consult >> http://click.pocoo.org/python3/for mitigation steps. >> >> This system lists a couple of UTF-8 supporting locales that >> you can pick from. The following suitable locales where >> discovered: aa_DJ.utf8, aa_ER.utf8, aa_ET.utf8, (followed by a bijillion >> others) >> >> -Darren >> >> On Mon, Apr 16, 2018 at 11:25 AM, Darren Smith < >> silas.crutherton(a)gmail.com> wrote: >> >>> Boy howdy did that work... >>> >>> Thanks! >>> >>> >>> On Mon, Apr 16, 2018 at 11:22 AM, Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>>> On 04/16/2018 10:12 AM, Darren Smith wrote: >>>> >>>> > "/opt/mailman3/conda/lib/python3.6/site-packages/sqlalchemy/ >>>> engine/strategies.py", >>>> > line 160, in create >>>> > engineclass.__name__)) >>>> > TypeError: Invalid argument(s) 'pool_pre_ping' sent to >>>> create_engine(), >>>> > using configuration PGDialect_psycopg2/QueuePool/Engine. Please >>>> check that >>>> > the keyword arguments are appropriate for this combination of >>>> components." >>>> > >>>> > Anyone able to point me where to go to look for a solution for this? >>>> >>>> >>>> You need to update SQLAlchemy to >= 1.2 for this, but there is another >>>> issue that requires at least 1.2.3 (current is 1.2.6) >>>> >>>> >>>> -- >>>> 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 >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >>>> >>> >>> >> >

8 years

[MM3-users] Re: cc'd e-mail addresses rewritten with @invalid.domain

by Williams, Peter B

Hi Mark, Thanks for the help with this! Other list members will also see the e-mail as coming from user(a)invalid.domain<mailto:user@invalid.domain>. I will continue testing the other scenarios and will reply back as soon as possible. Thanks again for the help with this and have a nice day! Peter On Mon, Sep 21, 2020 at 9:00 PM Mark Sapiro <mark(a)msapiro.net> wrote: On 9/21/20 10:49 AM, peterbw(a)gmail.com<mailto:peterbw@gmail.com> wrote: > Hi, > > We've recently noticed an issue where users who are cc'd in a message where a mailing list is also within the cc list are getting rewritten a user(a)invalid.domain. > > This issue looks like it may be related to Outlook and how user names are displayed specifically. Here is an example: > > To: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; > > "Williams, Peter" maps to a user e-mail in the Outlook Global Address book. When the message is sent the list will send the message with the first name and last name separated, for example the message will appear: > > to: test_user(a)gmail.com<mailto:test_user@gmail.com> > cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, Williams(a)invalid.domain, Peter(a)invalid.domain Because apparently Outlook is sending the message with the literal > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>; Williams, Peter; instead of something like > Cc: listserv(a)lists.test.org<mailto:listserv@lists.test.org>, "Williams, Peter" <peters_real_address(a)example.com<mailto:peters_real_address@example.com>> Then some MTA in the chain is seeing the unqualified addresses Williams and Peter and appending its own local domain. > This only seems to happen with users who are cc'd who are also members of the list that is being cc'd. For example in the scenario above my e-mail that is cc'd is also a member of listserv(a)lists.test.org<mailto:listserv@lists.test.org>. In this case, where do you see this? i.e., do other list members see it in the message they receive from the list? I don't know why that would be. I'm certain that Mailman is not involved in this and the Williams(a)invalid.domain and Peter(a)invalid.domain addresses are in the Cc: as received by Mailman. > This issue does not occur if the user e-mail address is listed before the mailing list in the cc field. So for example, if the cc in the scenario above contained Williams, Peter; listserv(a)lists.test.org<mailto:listserv@lists.test.org>; it would route properly. Again, I think this is Outlook. What's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> receives directly? What happens if you send mail in this way with To: test_user(a)gmail.com<mailto:test_user@gmail.com> cc: other_user(a)gmail.com<mailto:other_user@gmail.com>; Williams, Peter; Again, what's in the Cc: of the mail that test_user(a)gmail.com<mailto:test_user@gmail.com> and other_user(a)gmail.com<mailto:other_user@gmail.com> receive? Also, please see <https://wiki.list.org/DOC/Mailman%20is%20not%20Listserv>. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<mailto:mailman-users@mailman3.org> To unsubscribe send an email to mailman-users-leave(a)mailman3.org<mailto:mailman-users-leave@mailman3.org> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/

5 years, 7 months

[MM3-users] Re: Table 'mailmansuite.django_q_ormq' doesn't exist ("Delete this thread" -> 'HTTP-500 -> NoneType' object has no attribute 'all')

by Simon Liebold

Am 30.05.2017 um 02:06 schrieb Mark Sapiro: > Do you have django_q in INSTALLED_APPLICATIONS in your Django config and > do you have > > # > # Asynchronous tasks > # > Q_CLUSTER = { > 'timeout': 300, > 'save_limit': 100, > 'orm': 'default', > } > > in your Django config and are you running > > django-admin qcluster > > at startup? > > See > <https://mail.python.org/pipermail/mailman-developers/2017-May/026064.html>. Thanks Mark. After adding django_q, running python manage.py migrate and starting the runners it now works nicely: Successfully deleted 2 messages. Simon

8 years, 11 months

[MM3-users] Re: Postorius password resets

by Andrew Hodgson

Mark Sapiro wrote: >On 10/14/20 11:11 AM, Andrew Hodgson wrote: >> I am having an issue with our system where password resets are giving the users an email with a http://localhost:8000 URL. I have made sure settings in settings_local.py (and even settings.py) are as follows: >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.hodgsonfamily.org' >This is not relevant. Does it need resetting back to http://localhost:8000? >> However emails are still coming through with the wrong URL. >I'm not sure offhand, but it's either domains in Postorius or sites in the django admin UI. I've checked both and cannot see any errors (I just have the one site lists.hodgsonfamily.org) and nothing is empty which seems as though it needs filling in. Thanks. Andrew.

5 years, 6 months

[MM3-users] Re: Migrating to Mailman3

by Stephen J. Turnbull

Mark Sapiro writes: > On 10/19/25 08:49, Dennis Putnam via Mailman-users wrote: > > *Oct 19 15:41:29 dap002 systemd[1]: mailman3.service: Can't open PID > > file /opt/mailman/mm/var/master.pid (yet?) after start: No such file or > > directory* > > This is not a concern as long as /opt/mailman/mm/var/master.pid exists > now and contains the PID of the running master process. > > The message occurs because systemd checks before the master has created. > That's why there is a (yet?) in the message. FYI, I'm working on a patch to fix this using a systemd-dbus package. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 2 weeks

[MM3-users] Re: stop mailmanweb

by Thomas Krichel

Mark Sapiro writes > These are qcluster processes. They are normally started and stopped > separately from mailmanweb. I thought they would only be required for gunicorn. Since I could not otherwise understand why I would get a "No such file or directory" reaction to all my mailman requests, I switched to uwsgi. But even your advice could not kill the process listening at 8000, until I had the idea of checking who listens. And it was webfsd. Since webfsd uses 8000 as a default. Let them uses such an unimaginative port. I suggest to use a more quaint port number in the Mailman documentation. Why not use Jon Postel's birthday 194386. This could the nicknamed the Postel port. Thanks and cheers! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22207th day.

1 month, 2 weeks

[MM3-users] Re: Configuring the List-Archive and Archived-At headers

by Ralph Seichter

* Mark Sapiro: > It has nothing to do with the ssl certificate. In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-) > What that means is the lists.example.com domain must first be known to > Django at <https://lists.example.com/admin/sites/site/ Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs. Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it. -Ralph

7 years, 1 month

[MM3-users] Re: Receiving 8bit-clean mail

by Stephen J. Turnbull

On 10/17/19 3:02 PM, Alyssa Ross wrote: > A subscriber to a mailing list I administer has been sending 8bit UTF-8 > encoded mail, with no further quoted-printable / base64 / > etc. encoding. Based on the symptoms, I'm guessing this means the SMTPUTF8 extension. Mailman is not prepared for this as far as I know. That is, Mailman expects that the headers will be ASCII, possibly MIME-encoded. I'm guessing the problem is that either the host MTA or Mailman's LMTP server doesn't handle SMTPUTF8 negotiation correctly, but I do not have time to analyze for some days. Mark Sapiro writes: > It works for me. I created this message Your message doesn't have UTF-8 in the *header* as far as I can see. Steve

6 years, 6 months

[MM3-users] Re: ARC issues

by David Krantz

On Mon, Mar 2, 2020 at 7:07 PM Mark Sapiro <mark(a)msapiro.net> wrote: > I've been trying openarc > <https://github.com/trusteddomainproject/OpenARC> with Postfix as well > as Mailman's ARC. I still haven't got it all worked out - I have a > fairly convoluted mail flow with the possibility of messages being > altered before they ever get to Mailman. I do not have that problem. The ARC implementation in Mailman accepts incoming DKIM signatures etc. so that is not a problem. > There is an issue with Mailman's ARC signing in a supporting library. > See <https://github.com/ValiMail/authentication-headers/issues/5>. I have not had that issue yet, I do not think any of my users format their name that way. Good to know, though. Cheers. // David

6 years, 2 months

[MM3-users] Re: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

3 years, 2 months

[MM3-users] Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Andrew Hodgson

Mark Sapiro wrote: >The script at https://www.msapiro.net/scripts/clean_users.py has been updated. As before, it has settings to control whether Django users are deleted if there is a corresponding Mailman user with no memberships or only if there is no corresponding Mailman user, and whether or not Mailman users with no >memberships are deleted. Thanks, I ran this script and it did delete a load of Mailman users, I got output similar to this: <User "" (47600399411039288509336192576257642185) at 0x7fb17a6a35e0> deleted from Mailman Why aren't we seeing the actual address here? Thanks. Andrew.

3 years

[MM3-users] Re: customized welcome message

by Nils

On 12/7/23 18:17, Mark Sapiro wrote: > These messages are sent with `Content-Type: text/plain`. Any html > included in a template will be rendered as plain text. I.e., you can't > include html in templates. I didn't try to include html. It completely ignored the template I've created and sent the html source of the parent domain. Which seems totally random to me. > I see no URI setting in Postorius Settings > Automatic Responses. What > Postorius version is this? Any local mods? It's Postorius Version 1.2.4 installed through the mailman3-web package for ubuntu focal (https://packages.ubuntu.com/focal/mailman3-web) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: Screenshot_20231207_214025.png Replaced multipart/alternative part with first alternative.

2 years, 5 months

[MM3-users] Re: Strange error in uwsgi-error.log

by Derek Lambert

Brian, When I was seeing this, new lists weren't showing in HyperKitty. I was migrating from 2.1, so they were all new lists and was preventing HyperKitty from functioning. I had to drop the constraint to get the lists in. None of them have a description now. Was this working for you in the past? If so, did you do any updates recently? Derek Lambert On 2/6/19, 1:50 PM, "brian(a)emwd.com" <brian(a)emwd.com> wrote: Mark Sapiro wrote: > This looks like <https://urldefense.proofpoint.com/v2/url?u=https-3A__gitlab.com_mailman_hyp…> Thanks Mark. It doesn't seem to impact the functionality of the mailing list in any way and the other lists are fine and producing no errors. Brian _______________________________________________ Mailman-users mailing list -- mailman-users(a)mailman3.org To unsubscribe send an email to mailman-users-leave(a)mailman3.org https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.mailman3.org_mai…

7 years, 3 months

[MM3-users] Re: Sudden increase in "***UNCHECKED***" in email subjects

by Peter Adebahr

On 7/18/20 7:46 PM, Mark Sapiro wrote: > On 7/18/20 9:30 AM, Dave Clements wrote: >> Hi all, >> >> I have just noticed a big jump in the number of emails going out with >> "***UNCHECKED***" added to the subject line. > > > This does not come from Mailman. Some milter or other process in your > MTA or elsewhere in the delivery chain is adding this to the Subject: > Hi Dave, I had experienced the same symptom a while ago. For me, it was amavis doing this. This behaviour could be corrected by adding this line to amavisd.conf: # $undecipherable_subject_tag = '[UNCHECKED] '; # undef disables it $undecipherable_subject_tag = undef; # Hope it helps :) Best regards, Peter

5 years, 9 months

[MM3-users] Re: Problem with redirection when entering alias without a / at the end

by Abhilash Raj

> On Mar 19, 2021, at 4:10 PM, Jens Günther <jens.guenther(a)posteo.de> wrote: > > I did have the first setting, yes. > > The second one no, but activated it now, no change. Can you also share your uwsgi configuration? > > Am 20.03.21 um 00:00 schrieb Mark Sapiro: >> I don't use uwsgi so I can't advise on its configuration, but do you have >> USE_X_FORWARDED_HOST = True >> SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') >> in your Django settings? > _______________________________________________ > 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/ -- thanks, Abhilash Raj (maxking)

5 years, 1 month

[MM3-users] Re: I did something stupid. Can i back out of it?

by William Oliver

On Sat, 2022-02-19 at 17:01 -0800, Mark Sapiro wrote: > On 2/19/22 14:06, William Oliver wrote: > > > > So.. as an aside, it was a bit of a hassle to copy and paste all > > the > > usernames from the "Users" list in Postorius to the "Mass > > subscribe." > > The only way I could see to do it was copy and paste them one at a > > time. > > > Postorius Users -> Members view has a CSV Export button. That exports > a > CSV with all the member addresses. It's actually just a flat list as > it > only has one column. > Thanks! billo

4 years, 2 months

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > If you have content filtering Collapse alternatives = yes, it will become > > multipart/mixed > text/plain <- empty > image/jpeg > > after collapsing alternatives and that will trigger the error. See > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > for a patch (not yet tested) that I think will fix this. I don't think that's the best we can do, though. Especially if Convert HTML to plain is also yes, we want to preserve the HTML part and convert it, don't we? I think a better (or additional) strategy would be to check the selected alternative for blank, and if so, drop it and try again for an appropriate type. Steve

1 year, 3 months

[MM3-users] Re: How to store additional information about lists?

by Stephen J. Turnbull

Mark Sapiro writes: > On 5/29/21 7:31 PM, Stephen J. Turnbull wrote: > > Membership adapter is a Mailman 2 feature that allowed use of an > > external membership database (such as a corporate LDAP system). I > > thought it was ported to Mailman 3 but maybe not. > Actually, it's not quite that simple. Mailman 2.1 defines a > MemberAdaptor class, [...]. > The Mailman 3 analog of this is the IMember interface defined in > mailman/interfaces/member.py and implemented in mailman/model/member.py OK, but for Andi it is "simple" in the sense that he doesn't have an existing MemberAdapter, so the plan is "Implement the IMember interface". Easy to say, maybe not so easy to do. ;-) Steve

4 years, 11 months

[MM3-users] Re: ModuleNotFoundError: No module named 'settings'

by Adrian Wiedemann

Mark Sapiro wrote: > On 5/11/21 6:43 AM, Jeff wrote: > > I found a work around for the problem with the missing settings module. I modified: > > /etc/systemd/system/mailmanweb.service > > to add the PYTHONPATH environmental variable: > > [Service] > > Environment="PYTHONPATH=/etc/mailman3/" > > User=mailman > > Group=mailman > > ExecStart=/usr/local/mailman3/bin/uwsgi --ini /etc/mailman3/uwsgi.ini > > Now it starts up fine: > > That is the appropriate solution. I've updated the doc. That's works for the systemd service, but in case uswgi ist started within the venv (as for test running as stated in the docs), PYHTONPATH need to be exported here as well to work properly: * export PYTHONPATH=/etc/mailman3/ Best regards, Adrian

4 years, 10 months

[MM3-users] Re: Upgrading mailman 3 venv installation

by Morris Jones

On 9/29/2021 11:16 AM, Mark Sapiro wrote: > Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. Thank you! It appears that my installation predates the mailman-web package, as I don't have it installed. But if I understand the docs correctly, it serves to take care of the django-admin commands for migration, static files, js/css compression, etc. So I think I don't need to do anything special (like add mailman-web), except a database migration after the upgrades. Cheers, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

4 years, 7 months

[MM3-users] Re: Fwd: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/search

by Odhiambo Washington

On Fri, Jan 27, 2023 at 9:34 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/27/23 05:53, Odhiambo Washington wrote: > > On Mon, Jan 23, 2023 at 11:48 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> > >> Note that when following > >> https://docs.mailman3.org/en/latest/install/virtualenv.html you create > >> /etc/mailman3/settings.py and it contains > >> ``` > >> from mailman_web.settings.base import * > >> from mailman_web.settings.mailman import * > >> ``` > >> to establish a base set of settings that can be augmented or overridden > >> in /etc/mailman3/settings.py. mailman_web.settings.mailman in turn > contains > >> ``` > >> HAYSTACK_CONNECTIONS = { > >> 'default': { > >> 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', > >> 'PATH': "fulltext_index", > >> ``` > >> which is a relative path for fulltext_index and may need to be set to an > >> absolute path. > >> > > > > Mi Mark, > > > > I have read this page - > > https://docs.mailman3.org/en/latest/install/virtualenv.html and further > - > > > https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-config > > - without clicking any external links. > > I still don't see the HAYSTACK_CONNECTIONS in the settings.py included > on > > that page. > > I am missing something obvious, no? > > > Please reread what I wrote above. HAYSTACK_CONNECTIONS is not in the > suggested settings.py but it is in mailman_web.settings.mailman and is > imported by the suggested settings.py. I have reread what you wrote now and I'm beginning to get the hang of this method. My observation is that it can only be _obvious_ to someone very familiar with Python config to decipher that *additional* settings *that can be augmented or overridden in /etc/mailman3/settings.py* can be obtained from: /PATH-TO/mailman_web/settings/{base|mailman}.py after they have noticed these two lines in the sample settings given in /etc/mailman3/settings.py: from mailman_web.settings.base import *from mailman_web.settings.mailman import * [At first instance, it is not obvious that mailman_web.settings.base and mailman_web.settings.mailman are actually paths in Python - which magically translates to mailman_web/settings/base.py and mailman_web/settings/mailman.py] Granted, I am a slow learner, and perhaps already so mixed up after reading the myriad HOWTOs for installing MM3 that are available online. I am tempted to say there are many like me who are likely to miss "where to obtain" other settings from. For example, my mind all along has been tuned to having a settings_local.py for overriding the settings.py. However, with this particular documentation, it would appear that everything is intended to just go into /etc/mailman3/settings.py. Is it possible to modify the documentation to somehow make it obvious (in a language that a layman can easily understand, that those two "import *" _DO establish a base set of settings that can be augmented or overridden in /etc/mailman3/settings.py_ and that those settings are in what file(s) ? I am not saying @Johannes Rohr <johannes(a)rohr.org> is a layman like me, but I think that is what hit him. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: MM3+Python3.11

by Odhiambo Washington

On Mon, Mar 6, 2023 at 7:10 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 3/6/23 03:38, Odhiambo Washington wrote: > > Has MM3 been tested with Python3.11? > > Yes, but not with uWSGI which is not part of Mailman per se. > Are there any specific tests that are required to be done with respect to uWSGI and mod_wsgi? I could run some of those in my VM. I have switched from uWSGI to mod_wsgi and I don't have any errors - so far. Web UI running without issues in both cases. I believe I do not need to test anything with Gunicorn as that is what the Developers are using all the time :) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 2 months

[MM3-users] Re: See list of subscribers

by Tom Yates

On Wed, 27 Mar 2024, Mark Sapiro wrote: > On 3/27/24 00:38, Tom Yates wrote: >> >> But a random subscriber, who's signed up and authenticated, when she >> visits the list page she sees her subscription, but no option to list the >> other subscribers. >> >> Is she looking in the wrong place? Do I need to open up more settings? Am >> I just being an idiot? > > This is https://gitlab.com/mailman/postorius/-/issues/369 fixed in Postorius > 1.3.9 by https://gitlab.com/mailman/postorius/-/merge_requests/770 Thank you enormously! I'd've looked for a bug myself, but I was by no means sure I was looking in the right place for the user list in the first place. -- Tom Yates - https://www.teaparty.net

2 years, 1 month

[MM3-users] Re: Is there a simple way to remove the footer without having to add a customized template?

by Odhiambo Washington

On Wed, Jun 14, 2023 at 9:30 PM Mark London <mrl(a)psfc.mit.edu> wrote: > I simply want to have no footer for a mailing list. Can I do that > without having to create a customized template? Thanks. > I hope you are good at RTF-Ming :-) https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… Then again, @Mark Sapiro <mark(a)msapiro.net> will tell you the real gospel, or ask you to submit a patch :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 10 months

[MM3-users] Re: Search problem in 3.2.1?

by Mark Sapiro

On 10/22/19 7:51 AM, Mark Dadgar wrote: > Anyone seen this before? This is the result of any search query I run. I installed ElasticSearch as the search engine yesterday and this is the result. It is still indexing (large archives). How did you install ElasticSearch. What ElasticSearch version? This list uses elasticsearch 5.5.3 installed from the .deb as described at <https://www.elastic.co/guide/en/elasticsearch/reference/5.5/deb.html#instal…>. You can't use a later version because there are no python bindings for versions later than 5.x In addition we use the python bindings installed with `pip install elasticsearch5` <https://pypi.org/project>/elasticsearch5/ This version also requires haystack > 2.8.1 which we installed via `pip install -e git+https://github.com/django-haystack/django-haystack.git@master#egg=djang… Finally, we have these patches to the python bindings > --- elasticsearch5_backend.py.orig 2019-05-24 21:26:04.031867202 -0700 > +++ elasticsearch5_backend.py 2019-05-25 08:45:42.521374647 -0700 > @@ -28,6 +28,15 @@ > installation of 'elasticsearch>=5.0.0,<6.0.0'. \ > Please refer to the documentation." > ) > +# We need to override some elasticsearch_backend settings as string type is > +# gone in elasticsearch 5. > +from haystack.backends import elasticsearch_backend > +elasticsearch_backend.DEFAULT_FIELD_MAPPING = { > + "type": "text", "analyzer": "snowball"} > +elasticsearch_backend.FIELD_MAPPINGS["edge_ngram"] = { > + "type": "text", "analyzer": "edgengram_analyzer"} > +elasticsearch_backend.FIELD_MAPPINGS["ngram"] = { > + "type": "text", "analyzer": "ngram_analyzer"} > > > class Elasticsearch5SearchBackend(ElasticsearchSearchBackend): > --- elasticsearch_backend.py.orig 2019-06-16 10:21:42.441334321 -0700 > +++ elasticsearch_backend.py 2019-06-16 10:24:20.802264202 -0700 > @@ -78,8 +78,10 @@ > ) > > # Settings to add an n-gram & edge n-gram analyzer. > + # And, set max_result_window. > DEFAULT_SETTINGS = { > "settings": { > + "max_result_window": "100000", > "analysis": { > "analyzer": { > "ngram_analyzer": { The patch to elasticsearch_backend.py may require an even bigger value for max_result_window. The issue is the monthly Django hyperkitty - update_and_clean_index job runs into <https://stackoverflow.com/questions/41677198/result-window-is-too-large-fro…> > Mailman 3.2.1 from the debian packages in Ubuntu 19.10. > > - Mark > ----- > mark(a)pdc-racing.net | 408-348-2878 > > > Begin forwarded message: > > From: root(a)pdc-racing.net > Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/search > Date: October 22, 2019 at 7:44:49 AM PDT > To: mark(a)pdc-racing.net > > Internal Server Error: /mailman3/hyperkitty/search > > UnboundLocalError at /hyperkitty/search > local variable 'search_exception' referenced before assignment > > Request Method: GET > Request URL: https://mail.pdc-racing.net/mailman3/hyperkitty/search?q=Ken ... > Traceback: > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count > 79. return self.object_list.count() > > File "/usr/lib/python3/dist-packages/haystack/query.py" in count > 522. return len(self) > > File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ > 86. self._result_count = self.query.get_count() > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count > 619. self.run() > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run > 951. results = self.backend.search(final_query, **search_kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper > 33. return func(obj, query_string, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search > 524. _source=True) > > File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped > 84. return func(*args, params=params, **kwargs) > > > During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: I suspect this error is because indexing is still in process. I'm not certain, but I think so. > File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search > 90. request.GET.get('count'), > > File "/usr/lib/python3/dist-packages/django_mailman3/lib/paginator.py" in paginate > 72. objects = paginator.page(page_num) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in page > 57. number = self.validate_number(number) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in validate_number > 46. if number > self.num_pages: > > File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ > 35. res = instance.__dict__[self.name] = self.func(instance) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in num_pages > 91. if self.count == 0 and not self.allow_empty_first_page: > > File "/usr/lib/python3/dist-packages/django/utils/functional.py" in __get__ > 35. res = instance.__dict__[self.name] = self.func(instance) > > File "/usr/lib/python3/dist-packages/django/core/paginator.py" in count > 84. return len(self.object_list) > > File "/usr/lib/python3/dist-packages/haystack/query.py" in __len__ > 86. self._result_count = self.query.get_count() > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in get_count > 619. self.run() > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in run > 951. results = self.backend.search(final_query, **search_kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/__init__.py" in wrapper > 33. return func(obj, query_string, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/haystack/backends/elasticsearch_backend.py" in search > 524. _source=True) > > File "/usr/local/lib/python3.7/dist-packages/elasticsearch/client/utils.py" in _wrapped > 84. return func(*args, params=params, **kwargs) > > > During handling of the above exception (search() got an unexpected keyword argument 'doc_type'), another exception occurred: > > > > File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner > 41. response = get_response(request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 187. response = self.process_exception_by_middleware(e, request) > > File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response > 185. response = wrapped_callback(request, *callback_args, **callback_kwargs) > > File "/usr/lib/python3/dist-packages/hyperkitty/views/search.py" in search > 100. if not isinstance(e, search_exception): > > Exception Type: UnboundLocalError at /hyperkitty/search > Exception Value: local variable 'search_exception' referenced before assignment This is a bug in HyperKitty. We've never encountered it, but the code at <https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/views/search.p…> only considers the whoosh and xapian backends and needs to be updated for elasticsearch. I've reported that at <https://gitlab.com/mailman/hyperkitty/issues/263>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

[MM3-users] Re: Trouble Installing Mailman3

by Henry Hartley

>> -----Original Message----- >> From: Mark Sapiro <mark(a)msapiro.net> >> >> >> The next step in the instructions has me create >> >> /etc/mailman3/mailman.cfg. The first thing in that file is shown as: >> >> >> >> [paths.here] >> >> var_dir: /opt/mailman/mm/var >> >> >> >> Looking in /opt/mailman, there is no mm directory. Should that have >> >> been created, or is that something I need to create myself? >> > >> > You need to create it. I'll update the doc for that too. >> >> Actually, that's wrong. You don't need to create it. The first time you start Mailman core, it will be created. Excellent. Thanks. -- Henry

11 months

[MM3-users] Re: How to subscribe members without sending unsubscribe message

by Flo

On 9/15/25 14:25, Mark Sapiro wrote: > On 9/15/25 14:11, Flo via Mailman-users wrote: >> Hi, >> >> I need to remove subscribed members without sending them an >> unsubscription message. Despite of my research I haven't figured out >> how to do this using the GUI. > > With Postorius, you can do it by first setting the list's Automatic > Responses -> Send goodbye message to No, and then doing the unsubscribe. > > From the command line, you can use the `mailman delmembers` command > which has options to control the sending of the admin notice and the > goodbye message. > Thank you. I don't why I don't find these things in Postorius easily? Flo

7 months, 3 weeks

[MM3-users] Re: integrating mm3 with postfix / lmtp

by Fabian A. Santiago

October 26, 2017 11:07 PM, "Mark Sapiro" <mark(a)msapiro.net> wrote: > On October 26, 2017 7:30:35 PM PDT, "Fabian A. Santiago" <fsantiago(a)garbage-juice.com> wrote: > >> That was it. Perfect. I manually modified my regexp map and it works >> now. Excellent and Thank you. You're the man. Does mm3 ever refresh >> those maps or only as I add new domains / lists? > > Only when you make changes to domains or lists. > > -- > Mark Sapiro <mark(a)msapiro.net> > Sent from my Not_an_iThing with standards compliant, open source software. Mark, I've noticed that even simply restarting the mm3 components those alias maps get rewritten and the problem returns until I can manually edit it. -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

8 years, 6 months

[MM3-users] Re: Stalwart plugin

by Schulz

Thanks, it took some days to evaluate that - and the result is disappointing. While outgoing messages get routed to mailman, incoming messages get stuck in the created virtual users for the lists. Will post _if_ I have better news. Am 10. Juni 2025 um 17:27 schrieb "Mark Sapiro" <mark(a)msapiro.net mailto:mark@msapiro.net?to=%22Mark%20Sapiro%22%20%3Cmark%40msapiro.net%3E >: > > On 6/10/25 07:24, Jörg Schulz via Mailman-users wrote: > > > > > Hi all, > > I'm just reviewing Stalwart as a many-in-one mailing system. Did anybody yet succeed in plugging mailman into stalwart (the incoming bit seems to be difficult)? > > > See https://github.com/ewdurbin/stalwart-mailman > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

8 months, 1 week

[MM3-users] Confusing order of checkboxes in Postorius

by Markus Grandpré

Dear list, dear Mailman3 developers, dear Mark Sapiro, in Postorius under "Mass operations / Mass subscribe" we find the order of the checkboxes confusing: 1. Pre confirm 2. Pre approved 3. Pre Verified 4. Invitation We think it would be easier for us and our mailing list administrators to understand the interaction of these settings if they were displayed in the following order: 1. Pre confirm 2. Pre Verified 3. Pre approved 4. Invitation as in our opinion "Pre confirm" and "Pre Verified" belong together more than "Pre confirm" and "Pre approved". Incidentally, a typing error has crept into the term "Pre Verified". It should read "Pre verified". Yours sincerely, Markus Grandpré -- Markus Grandpré Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung IT-Dienste Forschung, Lehre und Infrastruktur, Tel: ++49 7531 88 4342

1 year, 7 months

[MM3-users] Re: Mailman rewrite the Cc header incorrectly

by Alan So

Mark Sapiro wrote: > I haven't looked at the code to see exactly what's responsible here. I > do note that adding double quotes around a display name is not only > allowed, but is required if the display name contains "specials". So, it looks like that Outlook still consider the part (XYZ) as comment during folding even though it is within the double quotes. It is folded between DEF and (XYZ) quite often in our cases if there are four or more than four email addresses in the Cc header. Since we normally have full name in the format of "Firstname Lastname (Dept)" in our organization, we hit the issue quite easily if users send to a list with more than four addresses in the Cc header.

5 years, 11 months

[MM3-users] Re: Postorius upgrade issue

by Joel Lord

So I tried to do this after upgrading, fortunately only from 1 point release back, and I get "ModuleNotFoundError: No module named 'paintstore'" from the collectstatic. Haven't tried to get past that point, and haven't really had the time to chase this down myself. It seems like that's referring to a requirement from several versions back, but this venv was built clean only 2 months ago so it strikes me as odd. On 2/8/2021 6:18 PM, Mark Sapiro wrote: > I neglected to mention `migrate`. All 4 Django management commands, `collectstatic`, > `compress`, `compilemessages` and `migrate` should be run after any upgrade. > _______________________________________________ > 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/ > -- Joel Lord

5 years, 2 months

[MM3-users] Re: Disabled by bounce

by Danil Smirnov

Hi Mark On Wed, Feb 1, 2023 at 9:28 PM Mark Sapiro <mark(a)msapiro.net> wrote: > Yes and no. If 'Bounce info stale after' is set to 3d and no bounces for > a user are received in a 3 day period, the user's bounce score is not > immediately reset, but it will be reset (to 1) the next time a bounce is > received for the user. I.e., it is effectively the same thing unless you > are looking at the user's bounce score which doesn't change until the > next bounce. > Isn't this a bug? We are now showing users' bounce scores on the Members page and this would be misleading. Is it difficult from internals perspective to have the bounce score reset immediately? BR, Danil Smirnov

3 years, 3 months

[MM3-users] Re: Strange password problem

by Eggert Ehmke

Am Freitag, 22. September 2023, 19:34:41 CEST schrieb Mark Sapiro: > Can you create another superuser with the Django admin createsuperuser > command and does that user's password stick? This got me on the right track. My mailman installation hosts several mailing lists that are assigned to different domains. Somehow I had created a superuser account 'admin' for each domain with different passwords. Because the browser stores the password for each domain separately, each time I log in via a different domain, I got the wrong password. So for now I use the same password for all logins, and that works. But is that a good solution? The other option would be to assign multiple superusers for each domain, but they would still allow to log in via some other domain. Thank you for your help!

2 years, 7 months

[MM3-users] Re: Chinese characters in list name shows question mark (?)

by Franklin Weng

Hi Mark, Thanks for your reply. Mark Sapiro 於 2019/10/24 上午6:10 寫道: > >> Is there any other setting I should look at? > > The list's preferred_language setting (Postorius -> Settings -> List > Identity -> Preferred Language. The list welcome message is encoded in > Mailman's character set for the list's preferred_language. If this is > English (USA), the character set is us-ascii. If it is set to Chinese > (Taiwan), the character set is utf-8, and it should work. However in my settings -> List Identity page I didn't see Preferred Language option. https://nextcloud.slat.org/index.php/s/45tGaE7ALgAFQFK What may be possible wrong that I couldn't see Preferred Language settings in the web interface? Thanks, Franklin

6 years, 6 months

[MM3-users] Re: High memory usage

by Philip Colmer

Thank you for the replies from Mark and Stephen. One of the reasons why Prasanth & I are concerned with this specific system is because the first time memory usage crept up, it got to the point where oomkiller stepped in and, as is usual for that particular mechanism, one of the processes it killed was sshd, thus removing access to the system :(. I know that oomkiller can be tuned to stop it killing processes like sshd but it will, nevertheless, start killing *some* processes if it sees an out of memory situation. So, as Prasanth said, we doubled the memory available and stuck an alarm on it to trigger when usage exceeded 85% for 5 minutes. I've saved a screenshot of the monitored memory usage over the last couple of weeks: https://1drv.ms/u/s!Aq7dn8GDGLdCodsU-pybJBdckxWU1A?e=BJY1UA (It is stored on OneDrive in case you don't recognise the URL format) We changed the server on 4th February to the larger memory size. On 11th Feb, it triggered the alarm and we rebooted the server. Memory usage is starting to climb again, albeit not at the pace that it was previously. What is particularly curious for us is that we have four Mailman 3 servers. Two of them are single domain and two are hosting two domains. This server is one of the servers hosting two domains, but it is also the ONLY one of the four servers exhibiting this memory pattern. By comparison, the memory usage for the other server hosting two domains looks like this: https://1drv.ms/u/s!Aq7dn8GDGLdCodsVyEufkeQqit_cGA?e=ifrJHs The biggest difference we are aware of with the "problematic" server is that some of the list archives are quite large by comparison with our other servers. The largest is 15K messages, then 2K then 1K. The other three servers have lists with relatively small archives by comparison (double or triple digits at worst). Finally, and just FYI, we're using PostgreSQL for the database and Xapian for the indexing engine. Regards Philip On Tue, 15 Feb 2022 at 16:36, Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/15/22 08:11, Stephen Daniel wrote: > > TL;DR: quite likely your system has plenty of memory and is operating > > normally. > ... > > On Tue, Feb 15, 2022 at 5:28 AM Prasanth Nair <prasanth.nair(a)linaro.org> > > wrote: > > > >> Hi, > >> > >> We are having an issue with high memory usage on our Mailman3 server. > >> Initially, our server had 16GB RAM and the memory usage went up from 5% > to > >> 92% within a week. So, we increased the memory capacity to 32GB RAM and > we > >> can see that the memory usage is going up in the same pattern. > >> > >> Any idea why it is happening? or any suggestions? > > > Just for reference, mail.python.org supports 231 MM 2 lists and 182 MM 3 > lists with 16 GB of ram and no swap. > > The server that supports this list and also the www.list.org web site > has 4 GB of ram and no swap. > > -- > 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, 2 months

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Thomas G

Hi, https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… I changed "sender" for this; # Sender try: from_str = header_to_unicode(message['From']) from_name, from_email = parseaddr(from_str) from_name = unidecode.unidecode(from_name).strip() except (UnicodeDecodeError, UnicodeEncodeError): raise (ValueError("Non-ascii sender address", message)) try: sender_address = from_email.encode('ascii').decode("ascii").strip() except (UnicodeDecodeError, UnicodeEncodeError): if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown(a)unknown.com" else: sender_address = "unknown(a)unknown.com" print("Non-ascii sender addre -- Sender address replaced by ", sender_address) I got this output (example): |Non-ascii sender address -- Sender address replaced by stephaneblipblopstlablipblopgmailcom It's not really perfect, I'm working to do something better, but basically it's works. I think that there is a issue in the original code: Because : "" raise ValueError("Non-ascii sender address", message) "" The second part will be never call: if not sender_address: if from_name: sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) if not sender_address: sender_address = "unknown" sender_address = "{}(a)example.com".format(sender_address) else: sender_address = "unknown(a)example.com" If you bypass : "" raise ValueError("Non-ascii sender address", message) "", by a simple print(), you will get an error due to an unassigned variable (sender_address). Le mar. 30 oct. 2018 à 04:10, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/28/18 12:03 PM, Guiseppin Thomas wrote: > > Hi, > > > > I imported some mbox archives in Hyperkitty. > > > > I have lot issues like: > > > > /\Failed adding message <5b0900ab.1c69fb81.70ab.2f87(a)mx.google.com>: > > ('Non-ascii sender address', <email.message.EmailMessage object at > > 0x7f05f1606048>)// > > //Non-ascii sender address from "Stéphane blipblop <stlablipblop at > > gmail.com>" about [HATLAB][It] Re: A débarrasser ! / > > > > It's probably because "Stéphane". > > > The 'Non-ascii sender address' message comes from > > > try: > > from_str = header_to_unicode(message['From']) > > from_name, from_email = parseaddr(from_str) > > from_name = from_name.strip() > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > raise ValueError("Non-ascii sender address", message) > > Possibly the exception is thrown in parseaddr(), but much more likely, > the email address, not the display name contains non-ascii. > > > Some advise to fix it ? > > > All the other messages should have been imported. If you can find and > fix the 'bad' ones in the mbox, you can make a new mbox with just those > and import that. You could also import the entire mbox with fixed > messages. The already added ones won't be re-imported because of > duplicate Message-ID:, but it's extra processing. > > If the actual bad message From: header is > > From: Stéphane blipblop <stlablipblop(a)gmail.com> > > or > > From: Stéphane blipblop <stlablipblop at gmail.com> > > That shouldn't cause the error, so I'g guessing that 'blipblop' is not > the actual value and the actual value in <stlablipblop at gmail.com> has > non-ascii. > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: Footer variables

by Washington Odhiambo

On Mon, Mar 2, 2026 at 3:41 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Washington Odhiambo via Mailman-users writes: > > > How did @Mark Sapiro <mark(a)msapiro.net> add the footer to > > mailman-users(a)mailman3.org? > > Looking more carefully at decorate(), it does fetch the value of > archiver.permalink for the message, and place it in > `d[f"{archiver.name}_url"]`, which should be `d["hyperkitty_url"]`. > > Have you tried using "$hyperkitty_url" instead of "${hyperkitty_url}"? > I have now removed the curly braces. Let me see what follows. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 months

[MM3-users] Re: templates

by Christian

From bounce.log May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 07:59:00 2023 (765) Member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:01:00 2023 (765) Member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:11:01 2023 (765) Member vortexanthony(a)hotmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 1. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score = 5. May 05 08:13:01 2023 (765) Member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org, bounce score 5 >= threshold 5, sending probe. May 05 08:15:01 2023 (765) Probe bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:01 2023 (765) Disabling delivery for juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:15:02 2023 (765) Probe bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:15:02 2023 (765) Disabling delivery for baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org by bounce May 05 08:17:02 2023 (765) Residual bounce received for member juliankrauspolk(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member alaitz.aritza(a)gmail.com on list degrowcali.lists.ccalternatives.org. May 05 08:17:02 2023 (765) Residual bounce received for member baronchadg(a)gmail.com on list degrowcali.lists.ccalternatives.org. -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Friday, May 5, 2023 4:39 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: templates On 5/5/23 15:27, Christian via Mailman-users wrote: > Okay I sent a test message this morning and subscribers are reporting > they did not receive it. The smtp.log shows 'smtp to > degrowcali(a)lists.ccalternatives.org for 25 recips, completed in > 3276.275292634964 seconds' (see below) I alone received it however and > it is listed in the archive. Below is the excerpt from smtp.log. Two > of my 5 lists are exhibiting this behavior, while > 2 other lists are working normally. Please advise. Thank you. That message says Mailman delivered the message for 25 recipients to the outgoing MTA. If only one recipient received it, you first need to check the outgoing MTA's logs to see whether the message was delivered to the recipient's mail servers or not. Those logs should indicate that either the message was delivered to each recipient's first hop mail server or not. If not, there should be a reason why in the logs. If the message was delivered, it could have been rejected by an MTA further down stream in which case a DSN message should be returned, but possibly not for days, or it could have been delivered to the user's spam/bulk/junk/promo/whatever folder or silently discarded. Do your list's do bounce processing? If so, what's in Mailman's bounce.log? -- 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/ XI52IZUTFWKEFTWELYVVG2MHQ53J65DF/ This message sent to csa(a)web-analysts.net

3 years

[MM3-users] Re: remove non members from a list

by Guillermo Hernandez (Oldno7)

On 6/8/21 19:16, Mark Sapiro wrote: > On 8/6/21 9:48 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> It's not functioning. It says: >> >> "AttributeError: 'MemberRoster' object has no attribute 'nonmembers'" > > Sorry, that was a typo on my part. It should be > > >>> for nonmember in m.nonmembers.members: > ... nonmember.unsubscribe() > ... > >>> commit() > > Thanks. Now it's no showing errors (and nothing at all) but apparently it does nothing. The non mebers of the list (the few that remains: I've been deleting one at a time from the web) aparently still are there.. Knowing the correct procedure will ease me to try tomorrow with a clean head. Thanks a lot.

4 years, 9 months

[MM3-users] Re: Mailman3 reinstall fail, need some help

by Yvan ♞

Ok thanks, I'll try on debian forum as I already unsuccessfully tried on yunohost since 6 months. Le 14/03/2022 à 16:23, Mark Sapiro a écrit : > On 3/14/22 08:12, Yvan ♞ wrote: >> Maybe an idea of my problem as I have pgadmin app installed, it could >> be in conflict to create a postgresql db? > > Your original dbug logs seem to show no issue with postgresql. > > I don't think people on this list can be much help for installing the > Debian package on YunoHost. As I said earlier, I would go first to > YunoHost for help and then to Debian if necessary. > > If you want help from us, I recommend installing as documented at > https://docs.mailman3.org/en/latest/install/virtualenv.html >

4 years, 1 month

[MM3-users] Re: where to configure max_days_to_hold on MM3 GUI interface?

by Abhilash Raj

On Sat, Feb 1, 2020, at 5:27 AM, Shashikanth Komandoor wrote: > Hello Mark, > > Thanks for helping me for moving ahead in my project. > > Troubling you again, I would like to put another request at you. > > As per your suggestion, I am trying to configure my list > configuration through REST API for specially the parameter like > max_days_to_hold as it is not available through interface and I am > following the official links of mailman 3 i.e > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html > > But I am getting "name is not defined" sort of errors as below: > > > > > > *>>> dump_json('http://localhost:9001/3.0/lists/ > <http://localhost:9001/3.0/lists/>','ant(a)example.com/config > <http://ant@example.com/config>',dict(display_name='My > List'),'PATCH')Traceback (most recent call last): File "<stdin>", line 1, > in <module>NameError: name 'dump_json' is not defined>>>* > > Actually I am new to REST API but hope this is the only issue that > is preventing me to go ahead. > > Could you please help me by saying how should I handle this so that > I should be able to configure *max_days_to_hold* of a list or multiple ? > dump_json is basically a Python function which sends the request to the URL you add as the first parameter (GET, if any data isn't specified and uses POST if data is specified or explicitly define the PATCH or method like you have above) and prints the json response. You can easily do the same using curl with the right authorization headers, with something like: $ curl -u restadmin:restpass -X PATCH \ http://localhost:8001/3.1/lists/somelist.example.com/config -d display_name='Patched Name' Note that "restadmin:restpass" is the username password that you have set in your mailman.cfg. If you do want to use Python, you can just use a regular PATCH request using requests or standard library urllib3. Finally, dump_json is documented here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.htm… > On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote: > > > > > > But I could see that parameter value configurable on MM2 GUI > > > interface in General Options but I don't see the same on the MM3 GUI > > > interface. > > > > > > There are many core settings not (yet) exposed in Postorius. > > max_days_to_hold. is one of them. It can be set via `mailman shell` or > > via the REST API > > < > > https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re… > > >. > > > > -- > > 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/ > > > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

6 years, 3 months

[MM3-users] Re: mailman-web migrate fails with sqlite3.IntegrityError: UNIQUE constraint failed: account_emailaddress.email

by Stefan Bauer

Dear Mark, thank you for your time. After patching your script according to https://github.com/maxking/docker-mailman/issues/729#issuecomment-2447542238 It fails with /opt/mailman/venv/data# /usr/local/bin/UC_fix /opt/mailman/venv/data/mailman3web.db Traceback (most recent call last): File "/usr/local/bin/UC_fix", line 77, in <module> c.execute("delete from account_emailaddress where email = %s;", sqlite3.OperationalError: near "%": syntax error for reference: 67 for id, emails in d.items(): 68 ems = find(emails) 69 if ems: 70 em1, em2 = ems 71 if em1.lower() == em1: 72 c.execute("delete from account_emailaddress where email = %s;", 73 [em2]) 74 c.execute("""update account_emailaddress set "primary" = 't' 75 where email = %s;""", [em1]) 76 elif em2.lower() == em2: 77 c.execute("delete from account_emailaddress where email = %s;", 78 [em1]) 79 c.execute("""update account_emailaddress set "primary" = 't' 80 where email = %s;""", [em2]) 81 else: 82 print(f'No LC email for {ems}') However the sql connection itself works, and the select also reports addresses: sqlite> select email, user_id from account_emailaddress; ... John.Doe(a)my.domain|85 john.doe(a)my.domain|85 ..... Mike.Doe(a)my.domain|96 mike.doe(a)my.domain|96 .... Is there something wrong on my side? Thank you. Stefan Am Mo., 3. März 2025 um 18:40 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 3/3/25 07:52, Stefan Bauer via Mailman-users wrote: > > > > trying to update mailman3 to lastest version, we fail during > > > > mailman-web migrate with: > > > > Operations to perform: > > Apply all migrations: account, admin, auth, contenttypes, > django_mailman3, > > django_q, hyperkitty, postorius, sessions, sites, socialaccount > > Running migrations: > > Applying account.0006_emailaddress_lower...Traceback (most recent call > > last): > > File > > > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py", > > line 89, in _execute > > return self.cursor.execute(sql, params) > > File > > > "/opt/mailman/venv/lib/python3.10/site-packages/django/db/backends/sqlite3/base.py", > > line 328, in execute > > return super().execute(query, params) > > sqlite3.IntegrityError: UNIQUE constraint failed: > account_emailaddress.email > > > This issue is due to changes in Django allauth to prevent creating > multiple addresses differing only in case. The problem is if you have > such multiple addresses in your account_emailaddress table, this > migration fails. There is a script at > https://www.msapiro.net/scripts/UC_fix that will fix this. You may need > to adjust the shebang and replace psycopg2 with sqlite3. > > See https://github.com/pennersr/django-allauth/issues/3019 perhaps > starting at > > https://github.com/pennersr/django-allauth/issues/3019#issuecomment-1748028… > > > We found a workaround to fake the migration with > > > > migrate --fake > > You should fix the issue with the DB and run the migrations. > > > Could this be some duplicate users with same mail-address? > > This is not related to Mailman users. It is Django users. > > -- > 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 cubewerk(a)gmail.com >

1 year, 1 month

[MM3-users] Re: Which crontab?

by Pierre Abbat

On Friday, November 3, 2017 2:27:03 PM EST Mark Sapiro wrote: > How about "user that installed Mailman" or "user that Mailman's runners > run as"? I installed it as root. From "man useradd" in Linux: -r, --system Create a system account. System users will be created with no aging information in /etc/shadow, and their numeric identifiers are chosen in the SYS_UID_MIN-SYS_UID_MAX range, defined in /etc/login.defs, instead of UID_MIN-UID_MAX (and their GID counterparts for the creation of groups). Note that useradd will not create a home directory for such an user, regardless of the default setting in /etc/login.defs (CREATE_HOME). You have to specify the -m options if you want a home directory for a system account to be created. Pierre -- lo ponse be lo mruli ku po'o cu ga'ezga roda lo ka dinko

8 years, 6 months

[MM3-users] Re: Starting from scratch

by Benjamin Ragheb

On Tue, Apr 10, 2018, at 12:14 AM, Mark Sapiro wrote: > If you are comfortable with 2), I think that's the better option. After > PyCon in May when we release 3.2 and the rest of the suite, you should > be able to install everything with pip and have it work. I'm not sure > what the issues are now with a pip install. Thanks, Mark. It wasn't clear to me by poking around how stable/unstable the master branches were, but if you think they should be stable enough for a hobby server, that's good enough for me. If I get things working and I'm feeling bold enough to contribute back to the documentation, are there guidelines? The Contributor Guide covers the technical stuff... should I just submit a merge request in GitLab? -- Ben

8 years

[MM3-users] Re: mailman start - can't open file

by Mark Dale

Thanks for the pointer Mark. I've edited mailman.cfg as follows and all is well. [paths.local] var_dir: /var/tmp/mailman bin_dir: /usr/local/bin log_dir: $var_dir/logs lock_dir: $var_dir/locks data_dir: $var_dir/data cache_dir: $var_dir/cache etc_dir: $var_dir/etc messages_dir: $var_dir/messages archive_dir: $var_dir/archives template_dir: $var_dir/templates pid_file: $var_dir/master.pid lock_file: $lock_dir/master.lck [mailman] layout: local Best, Mark On 8/2/19 2:03 am, Mark Sapiro wrote: > On 2/6/19 9:58 PM, Mark Dale wrote: >> Hi All, >> >> On a new installation (pip), when starting Mailman it seems it cannot >> find the "master" file. Have I missed a configuration somewhere that >> tells it to look in "/usr/local/bin" rather than "/usr/bin"? > > > See > <http://docs.mailman3.org/en/latest/config-core.html#configuring-filesystem-…>. >

7 years, 3 months

[MM3-users] Re: No option 'postmap_command' in section: 'postfix'

by Odhiambo Washington

On Mon, Jan 30, 2023 at 9:01 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/30/23 09:46, Odhiambo Washington wrote: > > > > So, if I understand this correctly, there is no need for the addition of > > this parameter: > > > > ``` > > configuration: /path/to/postfix-mailman.cfg > > ``` > > to the mta config block in mailman.cfg in a non-docker environment, or > when > > only using hash tables?? > > > Correct. > Great. So, since the creation of that file is prominent in the doco, maybe a note can be added to that effect? Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: Where does sender postorius@ come from?

by Jens Günther

Am 15.06.23 um 00:34 schrieb Mark Sapiro: >> - Then I tried settings_local.py with: >> EMAIL_CONFIRMATION_FROM = 'myaddress(a)something.org' > > > That is the correct place. It should work. Did you restart the container > after making this change? > Mh, unfortunately it does not work. - I changed the file and rebuilt the container. - I also restarted all 3 containers again. - I checked in the container the settings_local.py to verify that the change "arrived" and found it. - It still sends the "reset-password"-email with postorius@$SERVE_FROM_DOMAIN as shown in the screenshot. Is there any other way to test or check it? Any more ideas? Thank you in advance. ___________________________________________ Die Inhaltsfilterung von Mailman hat die folgenden MIME-Teile aus dieser Nachricht entfernt. Content-Type: image/png Name: Bildschirmfoto_2023-06-15_22-55-29.png

2 years, 10 months

[MM3-users] Re: Mailman/Django-allauth integration with Yahoo

by Дилян Палаузов

Hello Mark, thanks for your answer. So I had in the past registered that yahoo address withing mailman. Then I added oauth/openid to yahoo, then gave it a try. I have receieved as resut two email in the yahoo mailbox. One is sent by yahoo, notifying about account activity. The other, which I have not overseen as it was evaluated as spam, contains: You are receiving this email because you or someone else tried to signup for an account using email address: zzz(a)yahoo.com However, an account using that email address already exists. In case you have forgotten about this, please use the password forgotten procedure to recover your account: https://…/accounts/password/reset/ So the text "we have sent you an email for verification” but the email stating ”there is already such an account within mailman” is misleading, especially after the first message is shown to an yahoo-authenticated user. Greetings // Дилян -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: Mailman/Django-allauth integration with Yahoo Date: 06/08/24 03:01:24 On 8/4/24 03:35, Дилян Палаузов wrote: > > Then I get a site, partially in English, partially localized. It is in my domain at address /mm3/accounts/confirm-email/ , and states: > > Messages: Confirmation of email address sent to ...(a)yahoo.com > Menu: Entrance \r\n New registration > > Confirm your email address: > > We have sent an email to you for verification. Follow the link provided to finalize the signup process. If you do not see the verification email in your main inbox, check your spam folder. Please contact us if you do not receive the verification email within a few minutes. I'm not certain, but it looks like you are signing in to a new account and django-allauth is creating the account with the address from yahoo and is asking you to confirm. > I have indeed received an email, which states: > New signin from … Hi, Your Yahoo account … was just used to sign in on …. If you did this, you’re all set. If not, please use this link to stop sharing, and create a new password. Have a great day! Thanks,Yahoo > > So, the /account/confirm-email states I have received an email for verification, but the email sent says no verification is needed, I am all set up. > > Any idea what can I improve? This appears to be a glitch in the new account verification process. In any case, it's a django-allauth issue, not a Mailman issue. Once you have gone through this dance, what happens the next time you sign in via Yahoo. > In addition https://gitlab.com/mailman/mailman-suite/-/blob/master/mailman-suite_projec… suggests adding in settings.py: > > SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com')]}} > > which I have not done. That is, I do not use the “openid” provider, but the “yahoo” provider. Do I have to use the OpenID provider when using Yahoo? I don't think it would matter. -- 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 dpa-mailman(a)aegee.org

1 year, 9 months

[MM3-users] Use WHAT-WG decoding strategy? [was: Another interesting error...]

by Stephen J. Turnbull

Mark Sapiro writes: > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence I'm pretty sure 0x87 is reserved by the later GBK standard (implemented as an encoding in GB18030) as a prefix for extensions. This is a common problem with Chinese and Japanese encodings: junky email clients use "traditional" names denoting encodings with smaller repertoires to denote modern encodings. I wonder if we shouldn't just promote all gb* to gb18030 and all Shift JIS to the most recent version, as in the WHAT-WG web encodings standard. If nobody says "that's really stupid", I'll write up a RFE later this week. I think there's already a module on PyPI we can use to implement. Steve

8 years

[MM3-users] Re: Reset digest number and volume

by Andrew Bernard

HI Mark, I get: >>> commit() Traceback (most recent call last): File "<console>", line 1, in <module> NameError: name 'commit' is not defined Andrew On 26/6/19 11:49 pm, Mark Sapiro wrote: > On 6/26/19 3:08 AM, andrew.bernard(a)gmail.com wrote: >> How to do this? After lots of testing on my pre-release beta testing list, I want the first production digest to be reset toVolume 1, Number 1. > > You can do this in `mailman shell` by setting the list's `volume` and > `next_digest_number` to 1. E.g., > > > $ ./mailman shell -l list(a)example.com > Welcome to the GNU Mailman shell > The variable 'm' is the list(a)example.com mailing list >>>> m.volume = 1 >>>> m.next_digest_number = 1 >>>> commit()

6 years, 10 months

[MM3-users] Re: User settings triggers error

by Mark Dadgar

On Jun 28, 2020, at 4:56 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 6/28/20 4:39 PM, Mark Dadgar wrote: >> >> The patch does not apply cleanly against /usr/lib/python3/dist-packages/hyperkitty/models/email.py >> >> patching file email.py >> patch: **** malformed patch at line 4: import os > > > That probably isn't because of version mismatch. That would give applied > at offset or with fuzz or a reject. malformed patch means the patch file > is not formatted correctly. Here it is again as an attachment. That may > help. That gives a slightly different error: mark@mail:/usr/lib/python3/dist-packages/hyperkitty/models$ sudo patch < /tmp/patch.txt patching file email.py Hunk #1 FAILED at 24. patch: **** malformed patch at line 23: - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 10 months

[MM3-users] Re: sending messages in response to posts from non-members

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > On 2/26/22 04:26, David Bremner wrote: >> >> I'd like to turn off the "bounce messages" sent by mailman to >> non-members. My reasoning is that most such posts are spammers, and >> often use forged return-paths / From's, so I end of sending steady >> stream of backscatter to amazon.com etc... >> >> Is this configurable (without postorius) somehow? > > What exactly do you want? Do you want to discard without notice any > nonmember posts or do you want to hold them but not send a notice of the > hold to the poster? It was the latter, and your suggestion for existing lists seems to have worked. Thanks, David

4 years, 2 months

[MM3-users] Re: cron error - /opt/mailman/venv/bin/mailman-web runjobs daily

by Stephen J. Turnbull

Mark Sapiro writes: > You can't have two accounts in Postorius/Django with the same email > address. But why would you want to? There should be no problem with > a single Django user being subscribed to a list with more than one > role. I for one am uncomfortable having the superuser role being used by an ordinary user account, for several reasons. I'm pretty sure that is what Odhiambo was concerned about. I will have similar concerns about the domain user role when we implement it. The preference for a single email address across roles is harder for me to understand. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

8 months, 2 weeks

[MM3-users] Re: What is result of planned MM3 integrated installation at Pycon?

by Tom Browder

On Sat, Jun 9, 2018 at 16:48 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/9/18 2:19 PM, Tom Browder wrote: > > I may have missed the announcement, but I thought it was hoped to get a > > major leap toward an integrated MM3 installation at the May Pycon. Did > > anything exciting happen toward that goal, or should I just press on with > > the latest release? > > We accomplished a lot. We are still tying up a few loose ends, but the > release should be soon. FWIW, this list is currently running on the > HEADs of the GitLab branches. Thanks, Mark. Will the release be pretty much a one-step affair for us older folks without much energy? -Tom

7 years, 10 months

[MM3-users] Re: Apache+mod_wsgi issue

by Stephen J. Turnbull

Mark Sapiro writes: > You don't need all of those. ^postorius/ and ^mailman3/ are two > different ways to access Postorius, and ^hyperkitty/ and ^archives/ are > two different ways to access HypereKitty. You only need one of each, That's true from "outside", but there are internal links as well. For example, in Postorius top page, the link to HyperKitty is .../archives. I guess it's a good idea to grep the templates to see which URLS are used. > > Now my question is about what could be adding the /mailman3. Is it possible > > that I installed something out of the ordinary? Besides mod_wsgi as Mark suggests and the uwsgi configuration, the only thing I can think of is an Apache rewrite rule. It's not in the Postorius and HyperKitty templates. Steve

3 years, 4 months

[MM3-users] Re: Postorius List members

by Alain D D Williams

On Wed, Nov 13, 2024 at 07:10:04PM -0800, Mark Sapiro wrote: > On 11/13/24 19:00, Alain D D Williams wrote: > > > > Is it possible to add delivery status to the summary where many users are > > shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of > > what is happening to users. > > > There is a merge request in process for this. See > https://gitlab.com/mailman/postorius/-/merge_requests/953 Great I look forwards to that -- although since I have installed via Debian packages there will prolly be some delay :-( Thanks -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 5 months

[MM3-users] Re: hyperkitty.views.mailman The MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header

by Odhiambo Washington

On Wed, Dec 28, 2022 at 8:35 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/27/22 22:00, Odhiambo Washington wrote: > > I worke up to 959 such entries in my mailmanweb.log: > > > > ERROR 2022-12-27 22:49:57,732 82073 hyperkitty.views.mailman The > > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ... > > > > What might have been the cause of this? > > > > Upgrading HyperKitty without upgrading mailman-hyperkitty. HyperKitty>= > 1.3.5 requires mailman-hyperkitty>=1.2.0. (venv) [mailman@gw ~/mm]$ pip list | grep itty HyperKitty 1.3.6 mailman-hyperkitty 1.2.0 Which I think is fine, no? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 4 months

[MM3-users] Re: Hiding the "subscribe without creating an account"

by Ben Sturmfels

> On 13/07/2024 07:17, Mark Sapiro wrote: > >> On 7/10/24 7:36 PM, Ben Sturmfels via Mailman-users wrote: >>> >>> Is there a configuration option that does this, or was it a custom change >>> made in the templates? Was the change made to reduce fake registrations? Did >>> it work? >> >> It was added in Postorius 1.3.9. See the UI section at >> https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-9 >> >> Yes, the change was made in an attempt to reduce fake registrations. Thanks very much for the prompt advice Mark and Matthew! Really appreciate it. I'm currently running Postorius 1.3.8 (Debian Stable/Bookworm), so will look at upgrading and applying the settings you suggested. Regards, Ben

1 year, 9 months

[MM3-users] Re: user mail not accepted

by Christian Stalberg

My apologies. I did not confirm that what I did already sent you was the message received by the user. The mailing list address is ssan(a)lists.naturalintelligence.us and it seems as though this became an alias for this single user christian(a)sewagesludgeactionnetwork.com . > What I wanted to see was not the message sent to the list, but the message received by the one user from the list. If you are saying this message is that, it didn't come from any Mailman list. > > > Return-Path: <christian(a)sewagesludgeactionnetwork.com> > Delivered-To: ces(a)ecovillage.cc > Received: from box.ecovillage.cc ([127.0.0.1]) > by box.ecovillage.cc with LMTP id MDucNBythmCTSwAAMoO61A > for <ces(a)ecovillage.cc>; Mon, 26 Apr 2021 05:07:56 -0700 > X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on > box.ecovillage.cc > X-Spam-Level: > X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, > DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE autolearn=ham > autolearn_force=no > version=3.4.2 > X-Spam-Report: > * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP > * 0.0 HTML_MESSAGE BODY: HTML included in message > * -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature > * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not > necessarily > * valid > * -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from > * author's domain > X-Spam-Score: -1.1 > Received: from authenticated-user (box.ecovillage.cc [45.79.28.18]) > (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 > bits)) > (No client certificate requested) > by box.ecovillage.cc (Postfix) with ESMTPSA id 6EADF3E8CC > for <ssan(a)lists.naturalintelligence.us>; Mon, 26 Apr 2021 05:07:54 > -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; > d=sewagesludgeactionnetwork.com; s=mail; t=1619438876; > bh=1M7F/uIS0bNG6cWjecy/a9QjskrHVwJHkjWRv+ffpM4=; > h=From:To:References:In-Reply-To:Subject:Date:From; > b=jXOswVZgFeHBB+sjIDqVkNBQqIbfZCj9ZUfpVwl10NQEkGaoxckPHNOKT6x9zIqsW > BZ7iZqqi2mWprVQ8LrK48Lp7gvCQ/ipqspMeLt3t+uljzTtryHmV6uJFEAU3hqM33Y > nQqX6Z8la8Ko40F9Ayb4h4e/MOfPdA4nadgf5hZzt/DzPFZvzUbG3V8lWcHuyJNA2y > SQkhbNubQ6iNEEB0SyBjoOjl3g3LVxjxY+9kMGGmX+1PFfW90CpDDShRmKkkscEWaA > NiV0fX6U5LENBBnc6Q9ImLgXuaLdCqlBRBumJBk+eUUr007rpXXVAPck2NvUzGyM2v > kNNGlT68hGzEg== > From: <christian(a)sewagesludgeactionnetwork.com> > To: <ssan(a)lists.naturalintelligence.us> > References: > In-Reply-To: > Subject: How US chemical industry lobbying and cash defeated > regulation in Trump era > Date: Mon, 26 Apr 2021 05:07:37 -0700 > Message-ID: > <020501d73a94$cbe17440$63a45cc0$(a)sewagesludgeactionnetwork.com> > MIME-Version: 1.0 > Content-Type: multipart/alternative; > boundary="----=_NextPart_000_0206_01D73A5A.1F831170" > Thread-Index: Adc6h7I/qzBKx1yOT6aPOuipppacoQACatZAAADW1wA= > Content-Language: en-us > > How US chemical industry lobbying and cash defeated regulation in > Trump era Industry's congressional allies defeated nearly all PFAS > legislation while the Trump EPA killed, watered down or slowalked new > rules > > https://www.theguardian.com/environment/2021/apr/26/us-chemical-compan > ies-lo > bbying-donation-defeated-regulation > > -----Original Message----- From: Mark Sapiro <mark(a)msapiro.net> Sent: Monday, April 26, 2021 5:54 PM To: mailman-users(a)mailman3.org Subject: [MM3-users] Re: user mail not accepted On 4/26/21 5:41 PM, Christian Stalberg via Mailman-users wrote: > No. there was no response received by the user a la "results of your > email commands" > message. Simply the original email sent to the list. I would still like to see the complete raw message as received by the user. That's the only thing that can tell me how it got to that user and provide clues as to why it didn't go to the other list members. -- 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/

5 years

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, As you know, we can edit the individual messages using the message_id_hash. Is there any possibility that we can edit the original message which then updates all of the threads it has (for example, if someone already replied to the original message)? Or do we need to edit each message manually? Kind regards, Prasanth On Wed, 29 Sept 2021 at 15:46, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Many thanks for your help. I have managed to modify some of the messages > after following your instructions. > > Kind regards, > Prasanth > > On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> > wrote: > >> Hi Mark, >> >> Thank you for your help. Let me try this. >> >> Kind regards, >> Prasanth >> >> On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: >> >>> On 9/28/21 6:02 AM, Prasanth Nair wrote: >>> > Hello, >>> > >>> > Does anyone know how to edit an archived email in Mailman3? It is >>> possible >>> > in Mailman2 ( >>> > >>> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >>> ). >>> > Is there any option similar to this in Mailman3? >>> >>> >>> In some sense the process is the same but possibly even simpler in >>> Mailman 3. You need to modify the underlying data which requires >>> appropriate access to the server. >>> >>> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >>> database. You can get the Message-ID hash from the URL to the archived >>> message, e.g. for the message to which I'm replying, the URL is >>> >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >>> access, you can do database queries like >>> ``` >>> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >>> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> ``` >>> and >>> ``` >>> UPDATE hyperkitty_email SET content = '<new content>' WHERE >>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >>> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >>> ``` >>> If the message has attachments, they are in the hyperkitty_attachment >>> table and can be referenced by `email_id` which is the corresponding >>> `id` from the hyperkitty_email entry. >>> >>> You can also do similar things via `django-admin shell`. E.g. >>> ``` >>> $ django-admin shell >>> Python ... >>> (InteractiveConsole) >>> >>> from hyperkitty.models.email import Email >>> >>> x = >>> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >>> >>> print(x[0].content) >>> ``` >>> but this requires some knowledge of HyperKitty's models and Django's ORM. >>> >>> -- >>> 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, 7 months

[MM3-users] Re: troubleshooting hyperkitty

by Morris Jones

On 12/9/2020 9:11 PM, Mark Sapiro wrote: >> path: /opt/mailman/var/logs/archiver.log api_key <--- ?? Ugh ... I must have garbled my email. The files look fine. I don't know where that stray "api_key" came from. > The key in settings_local.py is MAILMAN_ARCHIVER_KEY, not > MAILMAN_ARCHIVER_FROM, a typo in your mail or ?? Yes, typo ... MAILMAN_ARCHIVER_KEY is 'properly_quoted' and unquoted in mailman-hyperkitty.cfg I'm guessing the next thing I need to do is find a way to crank up the logging in mailman and look for occasions where it calls the hyperkitty endpoint and delivers the message. I tried this but it may not be the right syntax: [logging.archiver] level: debug path: /opt/mailman/var/logs/archiver.log Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 4 months

[MM3-users] Re: Cannot Install Web UI

by Odhiambo Washington

On Tue, Oct 28, 2025 at 8:55 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On October 28, 2025 10:33:50 AM PDT, Odhiambo Washington via Mailman-users > <mailman-users(a)mailman3.org> wrote: > >It should be in sites-enabled/ or conf-enabled/. > > > Actually sites-enabled/mailman.conf should be a symlink to sites > available/mailmen.conf. True. But putting a file inside sites-enabled/ or conf-enabled/ still achieves the same result. Apache's a2ensite/a2enmod will create the symlinks in the *-enabled/ subdirs, but putting files in there, with the right extensions still does it. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

6 months, 1 week

[MM3-users] Re: sass error

by Alexander Klotz

Am 19.04.18 um 16:41 schrieb Mark Sapiro: > On 04/19/2018 02:41 AM, Alexander Klotz wrote: >> Hi everybody, >> >> we tried to make a fresh installation out of the current version >> following the readme.md - we encounter the following error trying to do >> so. As mentioned elsewhere, 'sass' has been replaced by 'sassc', >> however, maybe somewhere there is still a reference to it that may have >> been overlooked? The answer to a similar error posted to this list in >> August 2017 unfortunately didn't help either. > > > What do you have in your Django settings for COMPRESS_PRECOMPILERS? > > Do you actually have sass or sassc installed? > Hi Mark, the error was indeed in our local django setting, it still said "sass" on there - sorry and thanks! Regards, Alex

8 years

[MM3-users] Re: migration

by Dave McGuire

On 7/30/21 4:18 PM, Mark Sapiro wrote: >> Ok. I guess first I've got to figure out where the database lives. >> I've not been hacking on mm3, just using it. > > What's in the [database] section of your mailman.cfg? and the DATABASES > definition of your Django local settings. > > The database is managed by some database manager. If it is Postgres or > MySQL/MariaDB, there are actual database servers. If it is the default > SQLite, it's probably Mailman's var/data/mailman.db Ok, I will dig into it in the coming days. (and I will take a lot of notes this time) Thank you for the pointers. I'll come back on this if I need further help figuring it out. As always, I appreciate your time. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 9 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > On 10/23/21 4:23 PM, David Bremner wrote: >>> This particular machine is running debian oldstable, so things are a bit >>> out of date. mailman-core is 3.2.1 and flufl.bounce is 3.0. I'll look >>> into upgrading at least flufl.bounce. >> >> Oh. It's actually 3.0.1. Still not new enough, but 3 years newer. > > > I don't think it's a flufl.bounce issue. I think it's a Mailman 3.2.1 > issue - https://gitlab.com/mailman/mailman/-/issues/622 which is fixed > in Mailman 3.3.0 Oh great, I just upgraded to Mailman 3.3.0, so I'll see what happens. I did notice a bunch (10 or 20?) of subscribers being disabled for being over the bounce threshhold right after the upgrade, I wonder if that is related. d

4 years, 6 months

[MM3-users] Re: Mailman 3, postfix domains, and postgresql cannot authenticate user

by Odhiambo Washington

The nomenclature aside, if you follow the above link, you should have a running MM3 without much ado, seeing as even your version of PostgreSQL is less than 15, where a little nudging is required :) On Thu, Jul 4, 2024 at 12:38 AM Keith Christian via Mailman-users < mailman-users(a)mailman3.org> wrote: > Odhiambo, Yes, trying to. > > Mark, I'll review your suggestions. > > Thanks. > > On Wed, Jul 3, 2024, 12:52 Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 7/3/24 09:22, Keith Christian via Mailman-users wrote: > > > > > > --------------------------------------------------------------------------- > > > First issue:Postfix v3.5.8 on RHEL 8. > > > The below is from journalctl -xe: > > > > > > --------------------------------------------------------------------------- > > > Jul 03 08:12:04 somehost.somedomain postfix/qmgr[947499]: error: open > > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > > directory > > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > > database /opt/mailman3/mm/var/data/postfix_domains.db: No such file or > > > directory > > > Jul 03 08:12:42 somehost.somedomain postfix/smtpd[947510]: error: open > > > database /opt/mailman3/mm/var/data/postfix_lmtp.db: No such file or > > > directory > > > > > > I manually created the var_dir: /opt/mailman3/mm/var directory > > > specified in the mailman.cfg file. > > > How do I find out how to populate the postfix_domains.db files, and > > > the postfix_lmtp.db file? > > > > > > The `mailman aliases` command generates the postfix_domains and > > postfix_lmtp files and calls the configured postmap_command (default > > /usr/sbin/postmap) to create the .db files. `mailman start` also > > generates these files by default. > > > > > > > > > > --------------------------------------------------------------------------- > > > Second issue: Postgresql authentication. > > > PostgreSQL v10.23. > > > > > > --------------------------------------------------------------------------- > > > I have this in the active mailman3.cfg file, where xxxxxxxxxx is the > > > same complex password in the mailman3 config file: > > > url: postgresql://mailman3:xxxxxxxxxx@localhost/mailman3/mailman3 > > > > > > I don't think you should have two /mailman3 at the end > > > > the form is `postgresql://user:password@host:port/database_name` The > > default port is 5432. > > > > -- > > 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 keith1christian(a)gmail.com > > > _______________________________________________ > 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 odhiambo(a)gmail.com > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 10 months

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

9 years

[MM3-users] Re: Auth question

by David Krantz

On Mon, Apr 10, 2017 at 1:06 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > In mailman_hyperkitty.conf, the key isn't quoted. I.e., if in > production.py or wherever, you have set > > MAILMAN_ARCHIVER_KEY = 'arch_secret' > > in mailman_hyperkitty.conf you set > > [general] > ... > api_key: arch_secret > > No quotes around the api_key value. Ok, I'll try that. Thought that I had, but probably not just that combination then. Also: Found a bug in Hyperkitty, or at least in my setup: Private lists are visible in the "By Name" dialog in the archives when not logged in. The actual content is not visible, but the activity statistics is displayed (although there is none as the login for archiving as of yet does not work). Hopefully this will correct itself when the communication mailman3-hyperkitty gets active. cheers // David

9 years

[MM3-users] Re: LTMP to Postfix problem

by Brian Carpenter

On 6/18/20 6:19 PM, Mark Sapiro wrote: > If you have it, look through the mailman.log for entries around the last > time the connections started to be refused. See if there are entries > about the runner exiting. Also, just before you restarted, there will be > several runner caught SIGTERM. Stopping. and runner exiting. messages. > If lmtp runner is among those, it was still running when you restarted. So lmtp runner was NOT running when I restarted mailman core, however I saw no error messages in the mailman.log at the time of the first instance of the connection refused message. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 10 months

[MM3-users] Re: aborted connection

by Sandor Dibuz

On 2/19/22 20:46, Mark Sapiro wrote: > On 2/19/22 05:23, Sandor Dibuz wrote: >> >> Feb 19 14:15:18 localhost mariadbd[28859]: 2022-02-19 14:15:18 22154 >> [Warning] Aborted connection 22154 to db: 'mailman3' user: 'mailman3' >> host: 'localhost' (Got an error reading communication packets) > > You may be correct in your assumption that these are harmless. I would > try to correlate them with access and error logs from the web/wsgi > server to get more information. It's the mailman quarterly cron job: # Every 15 minutes, gate messages from usenet to those lists which have the gateway configured */15 * * * * list if [ -x /usr/bin/mailman ]; then /usr/bin/mailman gatenews; fi And I have no gateway enabled for any of them. Will have to find out what mailman exactly does. And change MariaDB to verbose logging. Sanyi

4 years, 2 months

[MM3-users] Re: Internal Server Errors in mailmanweb.log

by Washington Odhiambo

On Thu, Dec 25, 2025 at 12:07 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/18/25 03:07, Washington Odhiambo via Mailman-users wrote: > > I keep seeing several errors like the below in my mailmanweb.log and not > > sure what the causa is. > > What is your HyperKitty version? If it is 1.3.12 from PyPI and not the > latest from gitlab, See > https://gitlab.com/mailman/hyperkitty/-/issues/529 and > https://gitlab.com/mailman/hyperkitty/-/merge_requests/660 for a patch > to fix this. > It is version 1.3.12. Patch applied. Thank you. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

4 months, 1 week

[MM3-users] Re: MM3 Docker

by Abhilash Raj

On Tue, Jan 8, 2019, at 5:52 AM, Odhiambo Washington wrote: > On Tue, 8 Jan 2019 at 03:29, Mark Sapiro <mark(a)msapiro.net> wrote: > > > On 1/7/19 1:18 AM, Odhiambo Washington wrote: > > > On Sun, 6 Jan 2019 at 23:39, Mark Sapiro <mark(a)msapiro.net> wrote: > > >> > > >> Please help me understand what steps are missing and I will try to > > >> provide the information. > > > > > > > > > Okay. > > > > > > At the installation stage, you say the following: > > > "I already had some things set up in /opt/mailman including a git > > > subdirectory containing clones of the GitLab mailman, mailmanclient, > > > mailman-hyperkitty, hyperkitty, django-mailman3 and > > > postorius projects. On the third server I have added mailman-suite > > > because I use the settings.py from that project as the basis for mine." > > > > > > Please assume that the reader is a newbie to python3 virtualenv and give > > the > > > details of the commands they need to execute to (a) clone all the > > projects > > > needed > > > and (b) create the virtualenv. > > > > > > The next steps are: > > > mkdir /opt/mailman/mm > > > > > > Then you say "I then created a /opt/mailman/mm directory and within that > > a > > > Python 3.6 virtualenv" > > > What happens here is something that needs clarification, because you are > > > specific about "python3.6". > > > I have googled and realized that one has to be specific about the python > > > version they want to use in their virtualenv > > > as shown here -> > > > > > https://stackoverflow.com/questions/45293436/how-to-specify-python-version-… > > > > > > exact command to execute to create the /opt/mailman/mm/venv > > > exact command to execute to activate virtualenv > > > > > > I have added a comment to the page which I hope gives you what you want. > > > > I also added a section on templates instead of referring to a prior > > version of the page. > > > > That makes it better. > However, as a newbie, something is not yet clear: > > "When active in a particular shell, it can be deactivated with the command > > deactivate > or by exiting that shell." > > HI am trying to understand the effect of detaching from a venv. I am > assuming that a virtualenv is a container that is supposed to be always > active for the services within to be accessible. Is that right? So, how do > I ensure it's always running/up, or that does not matter as the scripts > which run the services will always refer to the files? virtualenv is not actually a container that is supposed to be active. It is merely a set of settings that are applied to your SHELL when you are in the virtual environment. It is not supposed to be always active, only when you actually want to run commands in that virtual environment. The services will keep on running after you deactivate your shell and would function like other normal services on your machine. -- thanks, Abhilash Raj (maxking)

7 years, 4 months

[MM3-users] Re: Is there a "global" max_message_size?

by skenny＠scss.tcd.ie

Mark Sapiro wrote: > > Mailman's lmtp runner which implements the server that receives mail via > LMTP uses the aiosmtpd.lmtp.LMTP class to implement the server. This has > a default size limit of 33554432 bytes (32 MB) and that's where the "552 > Error: Too much mail data" comes from. Ah - fantastic! I had tried a fairly crude trawl through the mailman-core container files (not knowing what exactly to look for really), but failed to come up with anything. > There is also the message_size_limit setting in postfix. Presumably > you've changed that because it defaults to 10240000 bytes (about 10 MB). Yes I fortunately did remember to set this to a very high value (way higher than 32MB) during testing. Thanks so much for the explanation Mark, very much appreciated. Stephen

5 years, 10 months

[MM3-users] Re: Moderated Signup with "info" box?

by Brian Carpenter

On 12/7/20 10:13 PM, Mark Sapiro wrote: > On 12/7/20 8:01 AM, Brian Carpenter wrote: >> Keep in mind that Mailman 3's REST API is only accessible locally. So to >> access Mailman 3's REST API from another server is not remotely >> possible. (see what I did there?) > > The REST API is only accessible locally by default. It is certainly > possible to configure the webservice section of mailman.cfg to be able > to access it remotely - if you do this, be sure not to use the default > admin_pass. There is also an authenticating REST proxy project called > lemme (possibly abandoned) at <https://gitlab.com/mailman/lemme>. Thank you for the clarification. I did not know that. Is that made clear in the documentation? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] Re: Sanity check of upgrade procedure

by David Newman

On 10/26/22 6:14 PM, Mark Sapiro wrote: > >> Attempting uninstall: mailman-web >> Found existing installation: mailman-web 0.0.6.dev9+gc606169 >> Uninstalling mailman-web-0.0.6.dev9+gc606169: >> Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 >> ERROR: Could not install packages due to an OSError: [Errno 13] >> Permission denied: 'WHEEL' >> Check the permissions. >> >> The command also said I needed to upgrade pip. Doing that produced a >> similar error. >> >> How to resolve this error? Thanks again. > > Was the venv initially created as the `mailman` user? Maybe > > sudo chown mailman:mailman /path/to/venv > > will fix it. Yup, that was it. Some Django directories were owned by root. The installation ran clean after running 'chown -R mailman:mailman' on those directories. Thanks! dn

3 years, 6 months

[MM3-users] Re: Is there a way of recording bounce messages?

by Andrew Hodgson

Mark Sapiro <mark(a)msapiro.net> wrote: >On 9/21/23 11:28, Andrew Hodgson wrote: >> >> Hmm. I'm on 3.3.8 and there was no attached bounce message in any of the reports. >Can you provide one of the bounce report messages and the corresponding bounce message from the MTA log. I only have the message I would get as the owner of the list that the delivery has been disabled, I don't have the original bounce message. One thing to note is the bounce messages coming in from Gmail are being generated by Office 365 (as that is the outbound smarthost for the Mailman server), so it may be due to the format of those NDRs why we aren't seeing the original bounce messages attached to the email. Thanks. Andrew.

2 years, 7 months

[MM3-users] Re: Weird response to postings after subscriptions and accounts

by Mark Sapiro

On 9/18/19 11:24 PM, Paul Arenson wrote: > > In the case of Mailman 3 much depends on the individual list and its settings, so my conclusion is it is mostly on me. With just a suggestion that you have a SIGN UP blue button to make things less confusing and not necessitating multiple clicking. This is difficult. See my reply to your first message. You will notice that when you click sign-up in either Postorius or HyperKitty, you go to <https://list.tokyoprogressive.org/accounts/signup/> which is neither Postorius nor HyperKitty but Django. So the current process is click sign-up, go to Django and sign up, then go back to Postorius and subscribe. To do this all in one step, Postorius would need to send you to /accounts/signup/?next=/postorius/lists/discuss.list.tokyoprogressive.org/ which it currently does, but there would need to be extra communication between Django and Postorius so that when Django returned to /postorius/lists/discuss.list.tokyoprogressive.org/, Postorius would know to tell Core to subscribe you. However, this is missing a step, because Django sends you an email requesting you to confirm your address, and you don't actually have an account until you confirm. This dance also renders the next=/postorius/lists/discuss.list.tokyoprogressive.org/ ineffective. Presumably Postorius could tell Core to subscribe you anyway even though you haven't confirmed your account, but Postorius doesn't know what address you signed up with. > The main obstacle I found was I had my list settings as NO to "Choose whether to include this list on the list of all lists". Changing this to "Yes" made it a little easier. > > Here are my two tests and conclusion. > > 2) TEST 1 > ________ > Sign up first... > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > ...you will find that if I have said NO on "Choose whether to include this list on the list of all lists” you will find it hard to go back to the subscribe page. Unless you backspace. Or paste the address again. Not ideal > > > QUESTIONS: Am I missing something? By not having my discussion listed, people cannot find it to subscribe. > > Or is NOT LISTED better where I add people manually to subscribe and then tell them to sign up? If you want people to be able to find your list by going to <https://list.tokyoprogressive.org/postorius/> or for that matter, to <https://mailman3.emwd.com/postorius/> or if you think having it there is helpful in any way, set List Identity -> Show list on index page to Yes. Otherwise set it to No. > 3) TEST 2 > ________ > One solution is I could put the list back on the host’s list of lists back and tell people to click on Discuss. > > That is what I did for now. Then it is rather smooth. I could tell my users (especially ones from previous company’s mailing list who want to interact with the hyperkitty site) > > to > CLICK LOGIN > CLICK SIGNIN > then follow all these steps: > > Verify > > Confirm > > Get taken to sign in page > > Click Discuss > > Subscribe > > Click Archives > > Or I could leave it as it is and tell people to backspace until they find the signup page and then subscribe. > > Or tell them to copy and paste https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > > or https://list.tokyoprogressive.org/accounts/signup/ in the same browser window and then subscribe. > > CONCLUSION and SUGGESTION—> WHY NOT HAVE A SEPARATE BLUE BUTTON TO SIGN UP TO AVOID THE CONFUSING clicking twice? See above. > IS THIS THE ANSWER?— > > Tell my users as follows on a WORDPRESS PAGE as follows: > > - - - - - - - - - - - - > Greetings. If you have never signed up before, follow instructions A. If you are coming from the previous dadamail list, follow instructions B > > > INSTRUCTIONS A > Steps 1-3 to get on the mailing list and be able to post from your email account. > Continue to steps 4 and 5 if you want to see the archives and post from that page. (Note to Mark: I have turned the archives off by default to make it more of a no brainer to want to sign up) > > > INSTRUCTIONS B > You are already registered, you will continue to get messages and be able to send to the list. If you want to keep using the same email address you are all set and do not need to do anything. > > If you want to keep using the same address, but also be able to access the archives, follow steps 4 and 5 only. > > If you want to register a new address, follow steps 1-5 below. > > 1) Go here > https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres… > Add your email address at the BOTTOM of the page. Name is optional. > > 2) Then wait for email to reply to come. > > 3) That’s it. You can stop here. However, you can sign up to the archives which makes this list more of a forum to see at a glance old conversations. And you can also post from it. To do so, continue to steps 4 and 5, > > 4) Right on the same page, you can sign up and sign in by clicking > log in and then sign up and then follow the same procedure as above. (Mark, SEE SUGGESTION FOR A BLUE SIGN UP BUTTON). > > 5) Once you have signed up, you can log in to access the archives and web posting. > - - - - - - - - - - - - > > Hope the above long winded post was clear. Feel like I am sseing the lite. > _______________________________________________ > 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/ > -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 7 months

[MM3-users] Re: How to upgrade to 3.10

by Paul Tomblin

On Sat, Mar 7, 2026, at 11:08 PM, Mark Sapiro wrote: > On 3/7/26 17:14, Paul Tomblin via Mailman-users wrote: >> >> I’m not seeing it. > > Are you looking at <https://your.domain/mailman3/domains/> > > Do you have the latest Postorius from GitLab? I missed that step at first, but now I've done it, I see no change. It still says version 1.3.13, and the Edit Domain page still just has Description, Alias Domain, and Web Host. When I was installing it, it said it was this commit: Resolved https://gitlab.com/mailman/postorius to commit 2c0c3aeb905c82ee4d6724897b89def71c02c1ef which does appear to be the latest. Sorry to be taking so much of your time, but I really want to make the footer for my neighborhood association lists as much like the old ones as possible. -- Paul Tomblin

2 months

[MM3-users] Re: Hyperkitty - Non-ascii sender address

by Thomas G

you do > try: > sender_address = from_email.encode('ascii').decode("ascii").strip() > except (UnicodeDecodeError, UnicodeEncodeError): > sender_address = from_email.encode('ascii', errors='replace').decode("ascii").strip() It's perfect, thank ! Le sam. 3 nov. 2018 à 19:11, Mark Sapiro <mark(a)msapiro.net> a écrit : > On 10/31/18 5:57 AM, Thomas G wrote: > > Hi, > > > > > https://gitlab.com/mailman/hyperkitty/blob/master/hyperkitty/lib/incoming.p… > > > > I changed "sender" for this; > > # Sender > > try: > > from_str = header_to_unicode(message['From']) > > from_name, from_email = parseaddr(from_str) > > from_name = unidecode.unidecode(from_name).strip() > > What is unidecode? > > > except (UnicodeDecodeError, UnicodeEncodeError): > > raise (ValueError("Non-ascii sender address", message)) > > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown(a)unknown.com" > > else: > > sender_address = "unknown(a)unknown.com" > > print("Non-ascii sender addre -- Sender address replaced by ", > > sender_address) > > > > I got this output (example): > > |Non-ascii sender address -- Sender address replaced by > > stephaneblipblopstlablipblopgmailcom > > It's not really perfect, I'm working to do something better, but > basically > > it's works. > > > The original code intends to provide some value for the email address > where parseaddr returns a null address. > > You have an address, and you would do better to remove the non-ascii > from the address than to try to make and address out of the sanitized > real name. > > Your issue is parseaddr() returns an email address with non-ascii. > > I would suggest that instead of > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown(a)unknown.com" > > else: > > sender_address = "unknown(a)unknown.com" > > you do > > > try: > > sender_address = > from_email.encode('ascii').decode("ascii").strip() > > except (UnicodeDecodeError, UnicodeEncodeError): > > sender_address = from_email.encode('ascii', > errors='replace').decode("ascii").strip() > > > > > > I think that there is a issue in the original code: > > Because : "" raise ValueError("Non-ascii sender address", message) "" > > > > The second part will be never call: > > It will if there is no exception. > > > if not sender_address: > > if from_name: > > sender_address = re.sub("[^a-z0-9]", "", from_name.lower()) > > if not sender_address: > > sender_address = "unknown" > > sender_address = "{}(a)example.com".format(sender_address) > > else: > > sender_address = "unknown(a)example.com" > > > > If you bypass : "" raise ValueError("Non-ascii sender address", message) > > "", by a simple print(), you will get an error due to an unassigned > > variable (sender_address). > > -- > 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/ >

7 years, 6 months

[MM3-users] Re: Member Issue Discovered

by Victoriano Giralt

El vie, 23-10-2020 a las 08:19 -0700, Mark Sapiro escribió: > > This would be more difficult for Postorius/Hyperkitty because those > users are Django users, but that isn't an issue for Affinity. > All of a sudden, an idea has dawned on me ... Wouldn't it be possible for Postorius/Hyperkitty, both Django applications, to use Mailman core user model as their User model? It is just a setting for Django (AUTH_USER_MODEL). I've used it for some of my applications and works nicely. This would certainly improve users' experience. -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

5 years, 6 months

[MM3-users] Re: clone a list?

by Dave McGuire

On 1/17/22 4:16 PM, Mark Sapiro wrote: >> Hi folks. Is there a way to clone or duplicate a list in MM3, i.e. >> create a list with a different name but other settings etc being >> identical? > > The short answer is not yet. > > Would you also want to clone the list membership? If not, you could > possibly do something directly with the database mailinglist table by > adding a new row with all the column values other than id, list_name and > list_id equal to those of the existing list. No, different membership. No problem, I'm just being lazy about it; I'll just duplicate it and copy the settings over manually. I only have two clones to make so it's really not a big deal. Thanks, -Dave -- Dave McGuire, AK4HZ New Kensington, PA

4 years, 3 months

[MM3-users] Re: DKIM signatures with message footers or subject prefixes

by Stanisław Findeisen

On Fri, Mar 11, 2022 at 10:41:00AM -0800, Mark Sapiro wrote: > Also, your outgoing MTA should DKIM sign the mail on the way out. With that and the above setting, the outgoing message will have only your > valid DKIM signature and no prior Authentication-Results:. Ok, you mean after replacing the From address with the list address, right? I can see no way (or sense) to DKIM sign arbitrary From: addresses. This actually works quite good: the recipient just gets 2 DKIM signatures. The original one is broken, the MTA-generated one (after writing my list address into From) is OK. This is good enough even for ProtonMail (no red warning). What about this list (mailman-users). It looks this one also has From address replacement + conditional DMARC mitigation. And remove_dkim_headers: no. Correct? Thank you

4 years, 1 month

[MM3-users] Re: Hyperkitty list overview error: thread matching query does not exist

by Ken Alker

Mark Sapiro wrote: > On 6/28/23 10:17 PM, Ken Alker wrote: > > Tthere is now an implication that my daily recent_threads_cache job must not have been running, true? Is there some way to check to see if the jobs are running? I did a "crontab -l" and the cron jobs that appear are identical to what was suggested at https://docs.mailman3.org/en/latest/install/virtualenv.html?highlight=period.... > > grep 'CRON.*runjobs' /var/log/syslog > > will tell you if cron is running the various runjobs commands. It is running every morning. Is it at all possible that running it manually did something that running it from CRON would not? I'm not sure why this solved the problem when the CRON job has been running every day.

2 years, 10 months

[MM3-users] Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 4 months

[MM3-users] Re: Mailman 3.2.0 Hyperkitty fulltext index error

by Marvin Gülker

Hi, Am 12. Juli 2018 um 08:14 Uhr -0700 schrieb Mark Sapiro: > This is due the the change from Python 2.7 to Python 3. The existing > search index is not compatible with Python 3 whoosh. Ah, I see. > I fixed this by deleting all the files in the index directory which is > defined as PATH in HAYSTACK_CONNECTIONS in your settings and running > 'django_admin update_index', but just running 'django_admin > rebuild_index' should do it. I simply followed your first suggestion, and it worked. I deleted all files in the index directory (which was "fulltext_index" in the "mailman-suite_project" directory, as we use https://gitlab.com/mailman/mailman-suite/tree/master/mailman-suite_project) and then ran update_index. That took a while, but succeeded. Since then the errors are gone. Thank you! Marvin -- Blog: https://mg.guelker.eu PGP/GPG ID: F1D8799FBCC8BC4F

7 years, 9 months

[MM3-users] Re: Gmail emails bouncing - anybody seen this problem?

by worik

On 14/02/19 1:08 PM, Mark Sapiro wrote: > Presumably this is list mail so your list copy should be the same except > for the few headers related to delivery from Mailman to you. Nope. I cannot send *any* emails to a gmail address. So it is the first "Welcome to the list" email. As far as I can tell there is no solution to the problem, which is why I ask is any one else having this problem? Am I incredibly unlucky or is this a known problem? I have a SPF record. I have tried a new VPS on a different IP address. Worik -- If not me then who? If not now then when? If not here then where? So, here I stand, I can do no other root(a)worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)

7 years, 2 months

[MM3-users] Re: Weird hourly indexing error

by Mark Dadgar

On May 5, 2020, at 4:01 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > As to the patch not working, there is a different patch at > <https://github.com/alexsilva/xapian-haystack/commit/a53523d2d0d13929a0729d4…> > which may work. > > There is one issue with this patch. Namely it calls force_str() in the > section > >> + # https://trac.xapian.org/wiki/FAQ/UniqueIds#Workingroundthetermlengthlimit >> + # Working round the term length limit >> + word = force_str(word) >> + word_length = len(word) > > > but xapian_backend.py imports force_text > <https://github.com/notanumber/xapian-haystack/blob/master/xapian_backend.py…>. > They are actually synonymous > <https://docs.djangoproject.com/en/3.0/ref/utils/#module-django.utils.encodi…>, > but just appliing the patch without changinf force_str to force_text > won't work. The second patch did not work either. Ahh, well. - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 11 months

[MM3-users] Re: mailman3 OWNERS_CAN_ENABLE_PERSONALIZATION option

by Henry S

Thanks Mark. That's exactly what I am looking for. On 3/12/2020 1:09 pm, Mark Sapiro wrote: > On 12/2/20 5:42 PM, Henry S via Mailman-users wrote: >> I am trying to change email "To" field to user's email instead of >> mailing list's email. e.g. "To: <user(a)gmail.com>" instead of "To: >> <mailman-users(a)mailman3.org>" > > In Postorius set Settings -> Alter Messages -> Personalize to Full. > > >> I looked around old mailman configs they mentioned about adding >> >> OWNERS_CAN_ENABLE_PERSONALIZATION option in mm_cfg.py >> >> is this feature still available in mailman3 ? Can I do it via Postorius >> or REST API? > > There is no setting in Mailman 3 to control the ability to set > personalization. It is always available. > >

5 years, 5 months

[MM3-users] Mailman 3 Installation Packaging

by ddw David Wilson

Salutations; I understand that work is in progress to provide a convenient installation tool to facilitate getting the suite of requisite programs installed and working harmoniously with a minimum of hassle? I assume that involves some combination of containers and/or virtual environments to insulate and isolate issues and facilitate portability. In addition, it would entail Mailman 3, Hyperkitty, Posterius and also Django, etc. The database selection of PostgreSQL or other. Other optionals to be configured would be the email utilities such as Postfix, etc Personally, my server of choice would run Centos. I gather Mark Sapiro was working on this as well? *Is there sufficient progress to warrant believing that such a capability might exist in the 2016 August - September time frame as was suggested some time back? Or are there any revised time-frames? Or an approximate estimated road-map?* Best regards. Dave Wilson

9 years, 8 months

[MM3-users] Re: Imported Digest Settings

by Brian Carpenter

On 2/16/21 5:21 PM, Mark Sapiro wrote: > Depends what the issue is. The two most obvious approaches are upgrade > to Mailman 3.3.3 if you aren't already there and switch from plain to > MIME digests, but I would really like to see the full raw source of this > digest messages to try to see if there is some other issue. > > >> What I did: I had the client change the list member's digest setting >> from plain-text to mime. Was that the right instruction to do? > It will probably help, but if this is Mailman 3.3.3, there's still a bug > somewhere that needs to be diagnosed and fixed. Hi Mark, The beginning of my OP stated I was using Mailman 3.3.3. Remember to use your reading glasses old man! -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 2 months

[MM3-users] Re: Is it possible yet to install Mailman 3 for Ubuntu 22.04?

by Eggert Ehmke

I can confirm the virtualenv method. It works well on all Debian derived systems like Ubuntu, and you are independent of the package release cycle of the distribution. My system works on Debian 11, Mailman3, MariaDb, uwsgi, Apache, Postfix. No problems so far. Regards, Eggert Am Freitag, 14. April 2023, 22:30:14 CEST schrieb Mark Sapiro: > On 4/14/23 12:44, Mark London wrote: > > Is it possible yet to install Mailman 3 for Ubuntu 22.04? > > Yes. We recommend following the instructions at > <https://docs.mailman3.org/en/latest/install/virtualenv.html> but there > are also Debian/Ubuntu packages. You can install the mailman3-full > package with apt. This will install Mailman core as well as the > Postorius and HyperKitty web packages, but the versions are several > releases old.

3 years

[MM3-users] Re: Maximum number of recipients Setting

by Stephen J. Turnbull

Mark Sapiro writes: > I understand it's confusing, but it's been that way since the beginning > of Mailman 2.1. The docs at > <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs…> > say "For backward compatibility, the message must have fewer than the > maximum number of explicit recipients." That's just weird. I guess the test is expressed "len(recipients) < maximum_recipients"? It would be easy to change "<" to "<=", but "backward compatibility" (and yes, it would be an annoying and mysterious change if you're using max_recips = 2 to enforce "no CCs" and after an upgrade CCs started sending annoying dupes to your subscribers). I wonder if it would be worth having an explicit backward compatibility setting so that we could change these things going forward. Steve

5 years, 1 month

[MM3-users] Re: config incoming email in my domain cpanel

by Rafael Mora

El jue., 3 ago. 2017 a las 16:07, tlhackque via Mailman-users (< mailman-users(a)mailman3.org>) escribió: > You've said you're working with labbrands.com. > > labbrands.com has address 192.185.51.89 > mail.labbrands.com has address 192.185.51.89 > www.labbrands.com is an alias for labbrands.com. > > telnet proves that Exim is running on that IP address. Either you're > running it, or hostgator is redirecting the SMTP ports. > > You added: > lists.labbrands.com has address 190.145.27.66 > > Presumably that's a different machine. > > So that now needs an MX record, and a firewall routing. I added the MX record on our hostgator hosting like this: [image: image.png] Is it correct??? > And the SPF > records ... and spam and virus filters, and all the other stuff you need > to setup an independent, public-facing smtp server. > > But at least you won't have to relay. > > Good luck. > > On 03-Aug-17 16:55, Rafael Mora wrote: > > El jue., 3 ago. 2017 a las 15:49, tlhackque via Mailman-users (< > > mailman-users(a)mailman3.org>) escribió: > > > >> I think you're confused. > >> > >> You already have mail.labbrands.com set up as the MX record for > >> labbrands.com. And it has an A record with the same address as your > >> webserver. > >> > > I'm working with the hostgator mailserver, we are not running a local > > mailserver. > > > > As suggested I added an A record like this: > > [image: image.png] > > > > Is it correct? is it redirecting to my Ip so I can redirect it to my > > postfix/mm3 server? > > > > > >> So if you're getting e-mail on that domain, there's another e-mail > >> server running on that IP address. You can't have 2 servers on port > >> 25. In that case, as has been noted before, you'll need to setup a > >> relay in that server, not a firewall redirect. Depending on your MTA, > >> you would need to relay to your internal server. And make sure your > >> firewall setup allows your MTA to do this. > >> > >> We can see it's EXIM: > >> > >> telnet mail.labbrands.com 25 > >> Trying 192.185.51.89... > >> Connected to mail.labbrands.com (192.185.51.89). > >> Escape character is '^]'. > >> help > >> 220-gator4137.hostgator.com ESMTP Exim 4.87 #1 Thu, 03 Aug 2017 > 15:47:48 > >> -0500 > >> 220-We do not authorize the use of this system to transport unsolicited, > >> 220 and/or bulk e-mail. > >> 214-Commands supported: > >> 214 AUTH STARTTLS HELO EHLO MAIL RCPT DATA NOOP QUIT RSET HELP > >> quit > >> 221 gator4137.hostgator.com closing connection > >> Connection closed by foreign host. > >> > >> Or, consolidate all your e-mail to one server - which is a lot easier to > >> manage unless you have a really big operation. Postfix is probably the > >> right choice, but requires more setup. > >> > >> Although Mailman3 configuration is not well documented (as you've > >> discovered), you may want to get help from someone with more general > >> network and mail experience. You're now into territory that is, as > >> Simon indicated, not Mailman-specific. > >> > >> On 03-Aug-17 16:28, Rafael Mora wrote: > >>> El jue., 3 ago. 2017 a las 15:26, Mark Sapiro (<mark(a)msapiro.net>) > >> escribió: > >>>> On 08/03/2017 01:22 PM, Rafael Mora wrote: > >>>>> El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) > >>>> escribió: > >>>>>> You need to forward port 25 for SMTP mail delivery and if you want > the > >>>>>> web UI (Postorius and HyperKitty) accessible from the outside, port > 80 > >>>>>> for http and/or port 443 for https > >>>>>> < > >>>>>> > >> > https://www.iana.org/assignments/service-names-port-numbers/service-names-p… > >>>>>>> . > >>>>> I mean for incoming mail redirected from my hostgator hosting, > because > >>>> when > >>>>> I suscribe an email address MM3 sends a confirmation email, so I have > >> to > >>>>> reply to be suscribed to the list. > >>>> As I said, for mail delivery you need to forward port 25 to the > Mailman > >>>> server. > >>>> > >>> Ok so I'll redirect in my zentyal firewall the port 25 to my local > >> centos7 > >>> with postfix and MM3 with IP 192.168.1.42. Thanks Mark. > >>> > >>> > >>>> -- > >>>> 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 > >>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >>>> > >> -- > >> This communication may not represent my employer's views, > >> if any, on the matters discussed. > >> > >> _______________________________________________ > >> Mailman-users mailing list > >> mailman-users(a)mailman3.org > >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >> > > -- > This communication may not represent my employer's views, > if any, on the matters discussed. > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 9 months

[MM3-users] Re: Python error, debian package, again

by Lars Schimmer

On 11/5/19 6:48 PM, Mark Sapiro wrote: > On 11/5/19 7:04 AM, Lars Schimmer wrote: >> >> Abhilash Raj (maxking) mentionend, it maybe a issue with mailman core >> trying to deliver the message to hyperkitty. >> But how can I remove those broken messages, or twitch hyperkitty to >> accept and discard them? > > > Look in Mailman's var/archives/hyperkitty/spool/ directory. This is > where messages that mailman-hyperkitty can't deliver to hyperkitty are > kept for retry. Yeah, there are some in this folder. Can I simply remove those entries from the spool directory? Or do I need to fiddle with any cmdline tool? thank you. MfG, Lars Schimmer -- ------------------------------------------------------------- TU Graz, Institut für ComputerGraphik & WissensVisualisierung Tel: +43 316 873-5405 E-Mail: l.schimmer(a)cgv.tugraz.at Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723

6 years, 6 months

[MM3-users] Re: Sanity check of upgrade procedure

by David Newman

On 10/26/22 3:10 PM, Mark Sapiro wrote: > On 10/26/22 11:08, David Newman wrote: >> >> For these new releases, is that mistune step still needed? > > > No. That is one of the issues fixed in HyperKitty 1.3.6 which now > requires mistune>=2.0.0,<3.0 and will work with those versions. OK, thanks. Before getting to mistune, this command, run as mailman in a venv: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web uwsgi Mailmanclient produced this error: .. Attempting uninstall: mailman-web Found existing installation: mailman-web 0.0.6.dev9+gc606169 Uninstalling mailman-web-0.0.6.dev9+gc606169: Successfully uninstalled mailman-web-0.0.6.dev9+gc606169 ERROR: Could not install packages due to an OSError: [Errno 13] Permission denied: 'WHEEL' Check the permissions. The command also said I needed to upgrade pip. Doing that produced a similar error. How to resolve this error? Thanks again. dn

3 years, 6 months

[MM3-users] Re: Mailman3 breaking DKIM signatures

by Stephen J. Turnbull

Mark Sapiro writes: > On 1/23/25 12:53 AM, Danil Smirnov via Mailman-users wrote: > > Doesn't this parameter fits better? > > > > https://docs.python.org/3/library/email.policy.html#email.policy.EmailPolic… > > That would be better except Mailman uses the legacy > email.message.Message class whose policy is Compat32 and the Compat32 > policy doesn't accept refold_source. I would welcome a patch, especially if (a) tested on a system offering lists to the general public (or some organization large and diverse enough to support the span of the MUAs cat(1), mutt, Thunderbird, and Outlook), and (b) enabling owners at some level to select policy. I don't promise to apply (it's not my call), but I've personally been interested in a number of issues that can probably be addressed via email.policy tweaks. Steve

1 year, 3 months

[MM3-users] Google Summer of Docs

by Terri Oda

On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: >Ralph Seichter writes: > > * Mark Sapiro: > > >> > If you post an issue at ><https://gitlab.com/mailman/mailman/issues>, > > > one of our GSOC aspirants may pick it up. > > > > Done, although I wonder if any GSOC participant would want to write > > documentation instead of code... ;-) > >For their actual, Google-supported, project, Google explicitly >excludes documentation. > They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate. (It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)

7 years, 1 month

[MM3-users] Re: Link in the top-left corner of Hyperkitty

by Seth Seeger

> On May 8, 2020, at 11:13 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > > It should show the display name corresponding to the domain name that > matches the domain in the URL that you go to. If this doesn't seem > correct, perhaps there is some issue with the way you are proxying in > your web server. Here is my proxy entry in Nginx: location / { include uwsgi_params; uwsgi_pass 172.19.199.3:8080; uwsgi_read_timeout 300; } My uwsgi_params file: uwsgi_param QUERY_STRING $query_string; uwsgi_param REQUEST_METHOD $request_method; uwsgi_param CONTENT_TYPE $content_type; uwsgi_param CONTENT_LENGTH $content_length; uwsgi_param REQUEST_URI $request_uri; uwsgi_param PATH_INFO $document_uri; uwsgi_param DOCUMENT_ROOT $document_root; uwsgi_param SERVER_PROTOCOL $server_protocol; uwsgi_param REQUEST_SCHEME $scheme; uwsgi_param HTTPS $https if_not_empty; uwsgi_param REMOTE_ADDR $remote_addr; uwsgi_param REMOTE_PORT $remote_port; uwsgi_param SERVER_PORT $server_port; uwsgi_param SERVER_NAME $server_name; Is there something I’ve missed? I followed a tutorial for this (which is no longer available). Seth

6 years

[MM3-users] Re: 500 Internal Server Error on specific list pages

by Johnny Cison

The Mailman logs contain the following: Jul 30 10:32:11 2020 (26190) REST request handler error: Traceback (most recent call last): File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run self.result = application(self.environ, self.start_response) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper rtn = function(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__ return super().__call__(environ, start_response) File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872) File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419) File "/usr/lib/python3/dist-packages/mailman/rest/lists.py", line 346, in on_get archiver_set = IListArchiverSet(self._mlist) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 135, in __call__ adapter = self.__adapt__(obj) File "/usr/lib/python3/dist-packages/zope/interface/interface.py", line 151, in __adapt__ adapter = hook(self, obj) File "/usr/lib/python3/dist-packages/zope/component/_api.py", line 156, in adapter_hook return sitemanager.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/registry.py", line 348, in queryAdapter return self.adapters.queryAdapter(object, interface, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 353, in queryAdapter return self.adapter_hook(provided, object, name, default) File "/usr/lib/python3/dist-packages/zope/interface/adapter.py", line 363, in adapter_hook result = factory(object) File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 85, in wrapper return function(args[0], config.db.store, *args[1:], **kws) File "/usr/lib/python3/dist-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none() File "/usr/lib/python3/dist-packages/sqlalchemy/orm/query.py", line 2793, in one_or_none "Multiple rows were found for one_or_none()") sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() On Thu, Jul 30, 2020 at 1:46 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 7/29/20 9:55 PM, Johnny Cison wrote: > > I have a new Mailman 3 server set up and am having a strange issue with > > just one particular list. > > > > Accessing the list's Info page URL or it's Archiving Settings page URL > > returns a 500 Internal Server Error, but its other pages work correctly. > > Also, the Info and Archiving pages on the other lists are working > correctly. > > > > When I access the info page for the problem list, I get these errors in > the > > log: > > > > Traceback (most recent call last): > > File > > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", > line > > 41, in inner > > response = get_response(request) > ...> line 103, in call > > raise HTTPError(url, response.status, content, response, None) > > HTTPError: HTTP Error 500: A server error occurred. Please contact the > > administrator. > > > > > > When I access the Archiving page in Settings, I get these: > > > > Traceback (most recent call last): > > File > > "/usr/lib/python2.7/dist-packages/django/core/handlers/exception.py", > line > > 41, in inner > ... > > line 103, in call > > raise HTTPError(url, response.status, content, response, None) > > HTTPError: HTTP Error 500: A server error occurred. Please contact the > > administrator. > > > These messages are from Django's log. What's in Mailman's mailman.log? > > > -- > 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/ >

5 years, 9 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:~# ******************* Making progress... I edited settings file again, replacing the domain name with the IP address () POSTORIUS_TEMPLATE_BASE_URL = 'http://12.34.56.78' (no SSL) The URI in the template table now has this. http://12.34.56.78/mailman3/api/templates/list/MYTESTLIST.MYDOMAIN.COM/list… Now, when Mass subscribing a new member, a Welcome email is sent to the new member with the correct Subject and From, but the message is blank.

2 years

[MM3-users] Re: Mailman shutting down Hyperkitty: Request too large

by Stephen J. Turnbull

Mark Sapiro writes: > Not if we're collapsing alternatives. If we're collapsing a > multipart/alternative part with text/plain and text/html > alternatives to just the first alternative we don't keep the > text/html part. I understand that's what we currently do. But I think that when the MUA provides an empty plain text part and a non-null HTML part, that's a mark of lazy MUA developers, not author intent. I think that it's very likely that the author would prefer the reader get converted HTML rather than a blank. Of course if the list owner wants to inhibit conversion, that's fine. But I would expect that list owners who enable conversion would also want to present a converted alternate rather than the blank plain text. Steve

1 year, 3 months

[MM3-users] Re: Template's encoding setup

by Ugnius S

Mark, You were 100% right for fixing. I was not sure what the language setting were on list creating, but one of the lists was created a day ago and I was doubt about it a little. So I made test: I have checked that default language is lt, and then I created the new list for testing. I had language issues with the HTML as well. Your recipe helped to resolve the issue. :) I fixed all my lists. I have stopped the mailman (just in case), than executed as You had told: $ mailman shell -l test(a)example.com Welcome to the GNU Mailman shell The variable 'm' is the test(a)example.com mailing list >>> m.preferred_language <Language [en] English (USA)> >>> m.preferred_language = 'lt' >>> <Ctrl>+D Thank You very much. This fix made magic. Kind regards Ugnius 2019-09-14, št, 20:20 Mark Sapiro <mark(a)msapiro.net> rašė: > On 9/14/19 4:06 AM, Ugnius S wrote: > > > Yes, I have made several tests. I have set charset: iso-8859-13 > > and default_language: lt in mailman.cfg. > > If you created the list before you set default_language: lt in > mailman.cfg, the list's preferred_language is possibly 'en;' with > character set us-ascii. > > > > (Also I have set LANGUAGE_CODE = 'lt' in the settings_local.py, but I > think > > it is not related to this case.) > > > Yes, LANGUAGE_CODE in settings_local.py is not relevant to this. > > > > I have tried to set utf-8 as well in mailman.cfg as well. And I can > > confirm - in all tested cases > > text characters are correct (in footer as well) if sender sends text > only. > > OK > > > > If sender sends message in HTML (mostly all users send) then no > > matter what the encoding is set in my mailman's > > configuration or iso-8859-13, or utf-8 message body looks correct, but > in > > footer all national characters are replaced with > > question marks " ? ". > > > The addition of the footer is done by mailman/handlers/decorate.py. In > the plain text case the message body is converted to unicode, the > unicode footer is appended to the body and the new body is encoded for > transmission. The encoding is the first of the list's character set, the > incoming message's character set or utf-8 which produces no error. > > > In the case where the incoming message is not a single plain text > message part, the footer is added as a separate MIME part with the > unicode footer encoded in the list's character set with > errors='replace'. This is what produces the '?' characters. I suspect > this happens because the list's preferred_language is 'en' with > character set us-ascii. > > try running Mailman's > > bin/mailman shell -l your_list@domain > > at the prompt enter > > m.preferred_language > > if the response is not > > <Language [lt] Lithuanian> > > do > > m.preferred_language = 'lt' > > and then control-D to exit. > > -- > 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/ >

6 years, 7 months

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

by Onyeibo Oku

Hi Mark, thanks for your inputs. I am making progress. On January 2, 2023 9:15:59 PM GMT+01:00, Mark Sapiro <mark(a)msapiro.net> wrote: >On 1/2/23 11:56, Onyeibo wrote: >> On Mon, 2 Jan 2023 09:57:45 -0800 >> Mark Sapiro <mark(a)msapiro.net> wrote: >>> >>> 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\""} > >That is the expected response if you have no lists yet. So connection to >Mailman's REST API works via curl, so why doesn't it work via >mailmanclient? If Mailman core was running, it should work. I don't know >why it doesn't. Perhaps you have some kind of firewall that's blocking it. > It turns out to be a fault from my settings. Postfix was not happy with the default email for the admin (<root@localhost>) since I had an operational virtual map for users. That connection error disappeared when I added a functioning admin email address. There are other issues, however. (1) Mailman refuses to resolve to a preferred subdomain. If the server's domain is "website.tld", I'd like mailman's homepage to be at "list.website.tld". Mailman insists that I add "website.tld" to the ALLOWED HOSTS, whereas "lists.website.tld" is already there as an ALLOWED HOST (same VPS/IP address nonetheless). The result is that the homepage ends up at "https://website.tld/mailman3/lists" when the desired url is "https://lists.website.tld/mailman3/lists". This is a conflict because the main domain is intended for another service. How do I approach this? (2) See the traceback below: ERROR 2023-01-03 07:40:32,078 27926 django.request Internal Server Error: /mailman3/lists/ Traceback (most recent call last): File "/opt/mailman/venv/lib64/python3.10/site-packages/django/core/handlers/exception.py", line 55, in inner response = get_response(request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/core/handlers/base.py", line 197, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib64/python3.10/site-packages/postorius/views/list.py", line 980, in list_index return render(request, template, File "/opt/mailman/venv/lib64/python3.10/site-packages/django/shortcuts.py", line 24, in render content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/loader.py", line 62, in render_to_string return template.render(context, request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/backends/django.py", line 62, in render return self.template.render(context) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/base.py", line 173, in render with context.bind_template(self): File "/usr/lib64/python3.10/contextlib.py", line 135, in enter return next(self.gen) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/template/context.py", line 254, in bind_template updates.update(processor(self.request)) File "/opt/mailman/venv/lib64/python3.10/site-packages/django_mailman3/context_processors.py", line 32, in common context["site_name"] = get_current_site(request).name File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/shortcuts.py", line 16, in get_current_site return Site.objects.get_current(request) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/models.py", line 59, in get_current return self._get_site_by_id(site_id) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/contrib/sites/models.py", line 30, in _get_site_by_id site = self.get(pk=site_id) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/manager.py", line 85, in manager_method return getattr(self.get_queryset(), name)(*args, **kwargs) File "/opt/mailman/venv/lib64/python3.10/site-packages/django/db/models/query.py", line 650, in get raise self.model.DoesNotExist( django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. It seems a migration is missing. How should I approach this?

3 years, 4 months

[MM3-users] Re: Unknown attribute: max_message_size

by Alexander Klotz

Hi, unfortunately we still have problems configuring a list so that it allows a message size larger than 40 KB. Neither the workaround described here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… (required was already set to false) nor this docker setup by yova https://gitlab.com/mailman/postorius/issues/246 worked. Are there any other options we could try? Thanks! Regards, Alex Klotz (CultureBase editorial staff) Am 28.05.18 um 17:16 schrieb Mark Sapiro: > On 05/28/2018 08:05 AM, Alexander Klotz wrote: >> Hi, >> >> just encountering the same problem in postorious, how are the chances of >> a fix being released soon? > > > It is fixed in the current branch heads. We plan a new release very > soon. There are still a few things we want to get in the release, so > it's not quite ready yet, but we're working on it. >

7 years, 10 months

[MM3-users] Re: 404 on fresh install (Debian11)

by David Newman

On 3/28/23 5:00 PM, comprepair_jimberg--- via Mailman-users wrote: > Can you setup Mailman3 for me? I can't. But I previously provided a pointer to setup instructions using virtualenv, which is MUCH preferable to the older, buggier version packaged with Debian 11. Mark Sapiro also provided a link to a list of providers who help with setup for a fee. If it's any consolation, I practiced with test VMs about 4 or 5 times before attempting a production migration from Mailman 2. Much of my misery was caused by the initial Debian install setting the wrong ownership on some files. For that reason, things got much better when I snapshotted a brand-new Debian 11 VM and rolled back to there each time. I still made mistakes, multiple times, but at least I was no longer fighting with two installations that do things differently. dn

3 years, 1 month

[MM3-users] Re: Don't start nntp runner by default - was: Mailman3 doesn't send Mails to users (Debian12 with Plesk)

by Danil Smirnov

Hi Mark, On Fri, May 24, 2024 at 11:24 PM Mark Sapiro <mark(a)msapiro.net> wrote: > We could default mailman.cfg to contain `start: no` in the runner.nntp > section so people would need to enable it if they wanted it. What do > others think? > I'd vote for disabling it by default and also for moving the Postorius NNTP-related settings from the "Settings - List Identity" page (the last five settings) to a separate page. Users who are born later than my generation are sometimes confused and misinterpret those settings. Once a user set "Newsgroup moderation" to "Moderated" by mistake which implicitly made the mailing list moderated too. Sincerely, Danil Smirnov

1 year, 11 months

[MM3-users] Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 1:04 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 2:52 PM, Odhiambo Washington wrote: > > > > Do I need to install sassc in the base OS or in the virtualenv? > > Have you checked `which sassc` to see if you don't already have it. It > doesn't matter whether it's in the base OS or the virtualenv. Things > running in the virtualenv can still access the base OS, just not vice > versa. > I install sassc, because sass installation always failed - after some upgrade. <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> I remember posting about it in 2020 or 2019 :) root@gw:/usr/home/wash # which sassc /usr/local/bin/sassc -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 11 months

[MM3-users] Re: MM3 not starting afte an upgrade -addendum

by Gelpi Andrea

To solve the problem I had to remove VHOST parameter from config file. I remember that Vhost was mandatory for my configuration when I set it up two month ago. So I don't understand why now I had to remove it to have MM3 working. Il 24/07/20 18:59, Mark Sapiro ha scritto: > On 7/24/20 1:33 AM, Gelpi Andrea wrote: >> >> Is anything changed since two month aggo when I applied some pathces? > > > What exactly are you asking? There have been multiple commits to the > master branches of the Mailman components in the last two months and new > releases of django-mailman3, hyperkitty and postorius in early June. > -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

5 years, 9 months

[MM3-users] Re: Hold messages that have binary attachments

by Quanah Gibson-Mount

--On Wednesday, August 12, 2020 11:29 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 8/12/20 9:37 AM, Quanah Gibson-Mount wrote: >> Is there a way to configure a list automatically put a hold on messages >> that have binary attachments such as jpgs, pngs, etc? > > You can use header matching rules (Header filters) for this: > > E.g., > Header = content-type > Pattern = image/ > Action = Hold > > will hold all messages with attached images > > A pattern like > > ^(?!(text/|multipart/|message/|application/.*signature)) > > will match any message that has an elemental part that isn't text/ or > some kind of signature. Thank you very much! Applied. :) Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 8 months

[MM3-users] Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 7/2/21 18:35, Mark Sapiro wrote: > On 2/6/21 10:44 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> I'm using sqlite as django database and mysql for mailman. > > I'm not certain about this, but having separate databases for Django and > Mailman core may be an issue. Thanks for your reply. I'm aware by this list that some people had problems using mysql in upgrades from previous releases. That was my first thought... But it seems that the problem is not database related. As far as I can see is about some missing properties in the "REST" process from 3.3.2 to 3.3.3 or maybe some template is not well upgraded even I did a "migrate" command. I installed mailman 3 in 24th of last december, with 3.3.2 version and all worked as expected. It's my first upgrade. >

5 years, 3 months

[MM3-users] Re: uncaught bounce messages

by David Bremner

Mark Sapiro <mark(a)msapiro.net> writes: > > See the thread at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > There is an example `mailman shell` session at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that will reenable delivery for members disabled by bounce if you think > the disables were spurious. Thanks very much for the recipe. I had been trying (and failing) to do something similar using the mailmanclient API / rest client. Does anyone happen to have a working example of updating user preferences via mailmanclient? I did call save(), after setting preferences['delivery_status']='enabled', but that seemed to not be enough. If no-one has a working example I can try to reconstruct a more precise reproducer. d P.S. I wonder if it would be worth collecting some of these recipes on the list as examples in the documentation?

4 years, 6 months

[MM3-users] Re: Moving from forum to Mailman 3

by jonathan.mailing.lists＠gmail.com

Mark Sapiro wrote: > > Can you export the posts from the forum in a format that looks like > email messages? Python's standard library mailbox module can be used to > read a set of messages in any of Maildir, mbox, MH, Babyl, or MMDF > format and write them to a mbox format file which can then be imported > into HyperKitty. The requirements are that the exported messages have > headers like an email message. At a minimum, From:, Date: and Subject:. Thanks for this. I’m sure I could turn that basic information (from, date, subject) into an mbox file somehow. What else does Mailman need, eg to work out which messages are in reply to which? Would it be possible to add ex-forum message “emails” like this to an existing mailing list archive? Thank you Jonathan

5 years, 6 months

[MM3-users] Re: Filter who can send on mailman3 list?

by Marcus Granath

Mark Sapiro wrote: > > As Ruth said in her reply at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > in Postorius, go to the Users dropdown and select Non-Members. On that > page there is a form to enter Email Address and Display Name with an Add > nonmember button. Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? Maybe then I need to try contact our mailman server admin, or? Or any other way for me as just an mailman-list admin to add this "Non-Member"?.... ;-)

5 years, 1 month

[MM3-users] Re: To have mailman3 start at boot, trying to configure the systemd mailman3.service unit, but having issues

by SATOH Fumiyasu

On Sun, 09 Jun 2024 06:48:58 +0900, Mark Sapiro wrote: > ``` > #!/bin/bash > unset PYTHONSTARTUP > > exec /opt/mailman/venv/bin/mailman \ > -C "/etc/mailman3/mailman.cfg" \ > $@ > ``` You should use `"$@"` to preserver arguments. For examples: ``` $ sh -c 'for v in $@; do echo "[$v]"; done' sh a 'b *' 'c d' ... $ sh -c 'for v in "$@"; do echo "[$v]"; done' sh a 'b *' 'c d' ... ``` -- -- Name: SATOH Fumiyasu @ OSSTech Corp., Japan (fumiyas @ osstech co jp) -- Business: <https://www.OSSTech.co.jp/> -- Development: <https://GitHub.com/fumiyas/> <https://GitLab.com/fumiyas/> -- PGP Fingerprint: EE58 9CE7 A512 E5D8 1DAD 5627 6709 E8A8 C7DD 5305

1 year, 10 months

[MM3-users] Re: makemigrations --merge error after Debian upgrade

by Odhiambo Washington

On Tue, Oct 1, 2024 at 12:36 PM Chupin Maxime via Mailman-users < mailman-users(a)mailman3.org> wrote: > Mark Sapiro wrote: > > Did you run this as the Mailman user (list in the Debian packages)? > > Thank you, I tried, but the system asked me a Password for this user... I > do not understand. > > ``` > sudo -u list mailman-web makemigrations --merge > Password: > ``` > The user executing `sudo` is yourself so enter your own password. It's not the password for user "list" that is wanted. It's your own login password. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 7 months

[MM3-users] Re: Create a mailman-web admin user

by Roland Giesler

On 2024/07/30 19:13, Mark Sapiro wrote: > On 7/30/24 08:55, Roland Giesler via Mailman-users wrote: >> >> I use Linux LXC containers mostly in Proxmox, so adding another layer >> by using docker or something else to mean seems like another layer of >> complication. >> >> The documentation is obviously good enough for people that know how >> already, but need to look up a detail here or, but for a first time >> mailman user it is a bit of a nightmare. Once I have chewed my way >> through all the traps and tunnels, I intend to do something about >> this. I can't contribute to code here, but I can make it easier for >> the next person coming along. > > > Please see https://wiki.list.org/x/12812344 Point taken, Mark.

1 year, 9 months

[MM3-users] Re: Mailman3 breaking DKIM signatures

by Danil Smirnov

Hi Mark, чт, 23 янв. 2025 г., 03:15 Mark Sapiro <mark(a)msapiro.net>: > > You could try a patch like > ``` > --- a/src/mailman/runners/lmtp.py > +++ b/src/mailman/runners/lmtp.py > @@ -186,7 +186,8 @@ class LMTPHandler: > listnames = set(getUtility(IListManager).names) > # Parse the message data. If there are any defects in the > # message, reject it right away; it's probably spam. > - msg = email.message_from_bytes(envelope.content, Message) > + msg = email.message_from_bytes(envelope.content, Message, > + policy=email.policy.Compat32(max_line_length=0)) > msg.set_unixfrom(envelope.mail_from) > except Exception: > elog.exception('LMTP message parsing') > ``` > This should prevent folding headers, but this is problematic. It may be > that the incoming message contains a folded header and this change will > not fold it in the outgoing message. Doesn't this parameter fits better? https://docs.python.org/3/library/email.policy.html#email.policy.EmailPolic… Danil

1 year, 3 months

[MM3-users] Re: Separating Lists by Domain

by Abhilash Raj

On Thu, Jan 3, 2019, at 8:19 PM, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > > > Is there a way we can get [Postorius updated] where we can > > > separate lists by domain the way Hyperkitty does? Mark Sapiro > > > refers to this in the following post: > > > > > > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > > You can file an issue at > > https://gitlab.com/mailman/postorius/issues > > Is this feature GSoC-able, or too small? It could be a good first issue for a GSoC applicant, too small to be the project itself. > > Steve > _______________________________________________ > 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/ > -- thanks, Abhilash Raj (maxking)

7 years, 4 months

[MM3-users] Re: Updated script for checking and fixing mbox files.

by Odhiambo Washington

On Fri, Jan 20, 2023 at 5:29 AM Mark Sapiro <mark(a)msapiro.net> wrote: > Mailman 2.1 has a cleanarch script for checking mbox files for unescaped > `From `lines in message bodies and optionally fixing them. For some > time, there has been a stand-alone python3 version of this script at > https://www.msapiro.net/scripts/cleanarch3 (mirrored at > https://fog.ccsf.edu/~msapiro/scripts/cleanarch3) I have just updated > this script to check and optionally fix bad Date: headers. > > I have also added it at > > https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/contrib/clea… > for the next release. > At what point does an MM3 List Admin require this script? I am unable to figure that out :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 3 months

[MM3-users] Re: Sad news - Brian Carpenter

by Odhiambo Washington

On Wed, May 12, 2021 at 10:45 PM <smorytko(a)gmail.com> wrote: > > https://www.tributearchive.com/obituaries/21066847/Brian-Keith-Carpenter/wa… > > I mentioned some "unfortunate circumstances" in a recent post. An inquiry > from Mark Sapiro prompted me to do a search and I sadly found this. > > Brian's company managed our list and on 4/22 we became aware that he was > hospitalized with Covid. > I have known Brian for many years mainly from the Mailman lists and he was a great resource. For a while now I have been meaning to check on the HOWTO he was writing for installing Mailm3 on Debian and yesterday I actually wanted to check on it. What a sad turn of events. May his soul rest in peace. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

4 years, 11 months

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

by Manos Pitsidianakis

Στις 2019-09-19 18:52, Mark Sapiro έγραψε: > No. You referred to "shunted" mails. I assumed that mail was winding up > in the shunt queue, but this is apparently not the case. But they are. Not exactly when or why but they show up in queue/shunt and queue/out at times. (maybe because I used mailman unshunt?) > > This should stop the out runner from "spinning" on these messages. Then > you can examine the files with Mailman's 'bin/mailman qfile' command > and > see if you can identify something in the recipients list or other > metadata that might be causing this. I cannot discern anything in the qfiles. It'd take some effort to deanonymise them for posting here. I've had new posts in the list and they get stuck as well.

6 years, 7 months

[MM3-users] Re: Handling of (un)subscribe mails for already (un)subscribed users

by Andreas Barth

Hi Mark, thank you for your help. * Mark Sapiro (mark(a)msapiro.net) [201210 23:26]: > The issue is the code at > <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/subscripti…> > appears to not be executed as in my test at least, the workflow continued. Interessting. Here it ended with (current git version) ==> /var/log/mailman3/mailman.log <== Dec 13 23:27:04 2020 (15015) deque: Traceback (most recent call last): File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/workflow.py", line 69, in __next__ return step() File "/srv/prod.mailman/lib/python3/dist-packages/mailman/app/subscriptions.py", line 227, in _step_sanity_checks MemberRole.member) mailman.interfaces.member.AlreadySubscribedError: t3@$domain is already a MemberRole.member of mailing list t1@$domain This was a "live" run of mailman (however on my testing box). And, however, still no mail. Now I need to think how to continue. Regards, Andi

5 years, 4 months

[MM3-users] Re: anomalous behavior

by Donato Molino

On Saturday 05 October 2024, alle 08:59, Mark Sapiro wrote: > On 10/5/24 04:14, donato(a)molino.it wrote: > > Hi, > > I installed mailman-full on debian 12. > > How? Did you follow > https://docs.mailman3.org/en/latest/install/virtualenv.html or did you > install the Debian packages. If the latter, please see > https://wiki.list.org/x/12812344 Ok you're right, I'll try to contact the debian developers. In any case, I will answer your questions below > > > Everything works perfectly except for the fact that for a single ML the messages are not delivered to the recipients. > > I have three MLs: > > 1) example(a)example.com > > 2) test(a)example.com > > 3) hello(a)example.com > > > > For the n. 2 and 3 are fine, but 1 doesn't deliver. > > The configurations are identical for all 3: > > > > smtp.log:Oct 05 11:37:44 2024 (42769) Peer: ('127.0.0.1', 37912) > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) handling connection > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'LHLO list.example.com' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'MAIL FROM:<subscriber(a)domain.tld> SIZE=7873 BODY=7BIT' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) sender: subscriber(a)domain.tld > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'RCPT TO:<example(a)list.example.com>' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) recip: example(a)list.example.com > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'DATA' > > Oct 05 11:37:44 2024 (42769) ('127.0.0.1', 37912) >> b'QUIT' > > I also enabled all debugging in mailman.cfg. > > But everything is fine > > What's in the MTA log? Does list 1 have any non-digest members with delivery > enabled > `mailman members --regular --nomail enabled example(a)example.com` No all members have regular enabled no digest. MTA log accept the message: (relay=127.0.0.1[127.0.0.1]:8024 - status=sent (250 Ok)) then HyperKitty archived message, then smtp log show the message above but does not send to recipients. > > In addition to the above in smtp.log, I would expect to see entries similar > to the following for your post to this list. me too but nothing. All other list with the same configuration are perfect. I tried also delete an recreate the list but nothing. All the lists are no moderate. in any case thank you for the work you do for the Mailman community. Donato > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 4 recips, completed in 0.31321239471435547 > seconds > Oct 05 11:15:02 2024 (3390806) > <172812689916.3390800.7261628565807094029(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from mailman-users-owner(a)mailman3.org, 5028 bytes > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> smtp to > mailman-users(a)mailman3.org for 334 recips, completed in 52.519867181777954 > seconds > Oct 05 15:22:57 2024 (3390806) > <172812689795.412444.17509223827906057290(a)mail.mailman3.org> post to > mailman-users(a)mailman3.org from donato(a)molino.it, 1683 bytes > ``` > (the delay between 11:15:02 and 15:22:57 above is the time between arrival > and held message approval) > > Do you see things like that? > > -- > 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 donato(a)molino.it

1 year, 7 months

[MM3-users] Re: Hyperkitty Error Curiosity

by Brian Carpenter

On 11/11/20 7:06 PM, Mark Sapiro wrote: > On 11/11/20 2:11 PM, Brian Carpenter wrote: >> This happened again. Is there a way to get HK to deal with such messages automatically? > > How would you like them dealt with? The issue is in mailman-hyperkitty. > When it's attempt to archive the message returns an error, it queues the > message for retry. It is not clear if any of these errors are actually > retryable - for sure some aren't but maybe others like HyperKitty not > responding are - but even if we think retry won't succeed what would you > like done with the message? > Some sort of auto-discard procedure after a number of retries? Is it possible to detect a message with a null characters and automatically discard them? Do such messages make it into the thread table? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 5 months

[MM3-users] KeyError: 'get_requests_count' after an upgrade

by Guillermo Hernandez (Oldno7)

I've just upgrade mailman 3 installation following Mr. Sapiro advice: did a pip install --upgrade django-mailman3 hyperkitty mailman mailmanclient mailman-hyperkitty postorius I did a "python3 manage.py migrate" after, too. And all seemed to run well. All the lists showed in postorius via web, but when I try to accesss into one of them the browser shows an error. In the log you can see: *-*-*-*-*-*-* Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 119, in __getattr__ return self._get(name) File "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", line 86, in _get raise KeyError(key) KeyError: 'get_requests_count' ... (And after all the traceback lines) AttributeError: 'MailingList' object has no attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists seem to be distributing messeages well.. but I cannot acces via web administration (django/postorius) Can anyone point me in the right direction to solve this, please?

5 years, 3 months

[MM3-users] Re: PGP - S/MIME signed messages

by Stephen J. Turnbull

Mark Sapiro writes: > On 7/28/25 13:29, Peter Adebahr via Mailman-users wrote: > > we are receiving a few PGP-signed posts as a S/MIME attachment. Some > > final recipients check these, and as mailman3 does not munge them - the > > original mail is signed, not mailman3's final posts - those get rejected. Besides Mark's suggestions, technically, PGP-signed and S/MIME are two different protocols. If you try to verify one with software expecting the other, it will fail. This seems unlikely (there would be reports of direct mail failing verification), but if Mark's suggestions don't help, you could verify that all the users are on the same page as to what signature protocols are being used. Steve -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

9 months, 1 week

[MM3-users] Re: Triaging message non-receipt

by Eric Abrahamsen

On 07/13/18 12:56 PM, Mark Sapiro wrote: > On July 13, 2018 12:11:13 PM PDT, Eric Abrahamsen <eric(a)ericabrahamsen.net> wrote: > >>All messages are correctly archived in hyperkitty. smtp.log always >>shows >>"for 5 recips", even for the messages that the two users aren't >>getting. >>These two users only ever miss messages sent by the other. >> > .... >> >>Is there any way to get a better sense of where things are going wrong? >>Turn up the logging verbosity? Send test messages? Get more >>diagnostics? > > > Mailman has delivered the messages to the outgoing MTA and can't tell > you any more. Mailman 3 bounce processing is broken. > > Look in the MTA logs for more. Okay, I'll see what postfix has to tell me. I appreciate the tip on bounce processing. Thanks, Eric

7 years, 9 months

[MM3-users] Re: How to Increase outgoing mail volume for Mailman 3

by Mark Dadgar

On Nov 10, 2020, at 1:18 PM, Mark Sapiro <mark(a)msapiro.net> wrote: >> >> The downside to this is that you lose automated bounce processing, of course. > > > You don't lose bounce processing. It just becomes a bit less reliable. > The VERPed envelope sender says exactly what address the message was > sent to. Without this information, Mailman (actually flufl.bounce > <https://fluflbounce.readthedocs.io/en/latest/README.html>) has to parse > the returned bounce message to determine the bouncing address. There are > many MTAs that do not send RFC 1894 compliant DSNs and we have several > heuristic recognizers to try to parse these, but they can fail. Brian specified: verp_personalized_deliveries: no Doesn’t that default back to regular mass delivery, as opposed to individualized VERPed envelopes, which mandates individual deliveries? - Mark ----- mark(a)pdc-racing.net | 408-348-2878

5 years, 5 months

[MM3-users] Re: Time Zone Issue in Postorius

by Henrik Rasmussen

> -----Oprindelig meddelelse----- > Fra: Mark Sapiro <mark(a)msapiro.net> > Sendt: 8. februar 2022 07:48 > Til: mailman-users(a)mailman3.org > Emne: [MM3-users] Re: Time Zone Issue in Postorius > > It should be TIME_ZONE = 'UTC' > > Times passed from Mailman core are naive times, I.e. they don't have > time zone info, but they are in UTC. Thus for Django to get the correct > time with time zone you need USE_TZ = True (without that, Django will > throw an exception about naive times) and the TIME_ZONE to apply is UTC. As https://stackoverflow.com/questions/29311354/how-to-set-the-timezone-in-dja… seems to say otherwise ("You can use TIME_ZONE = 'Europe/Istanbul'"), to make sure, am I right to understand it as for Mailman, Danish time should be stated as "TIME_ZONE = 'UTC+1' " with use of "USE_TZ = True"? /Henrik Rasmussen

4 years, 3 months

Search results for query "sapiro"