From turnbull.stephen.fw at u.tsukuba.ac.jp Mon Mar 2 03:12:25 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Mon, 2 Mar 2020 17:12:25 +0900 Subject: [Mailman-Users] The last release from the GNU Mailman project In-Reply-To: References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <2c0aa580-e03e-cca8-2e7b-1423c467b1b6@emwd.com> <24152.61688.525891.15443@turnbull.sk.tsukuba.ac.jp> <24154.4770.669929.292630@turnbull.sk.tsukuba.ac.jp> <32a3d7a40db3f137613c2f915c5f7cb24ba6ac56.camel@domainmail.org> Message-ID: <24156.49129.82313.300186@turnbull.sk.tsukuba.ac.jp> Mark Sapiro writes: > I'd say it depend on the details of how serious the vulnerability is, > how easy it is to exploit and how hard it is to fix. I am not opposed to > Mailman 2.1.30-x security fix releases. Mark speaks for me, although it's been a long time since I've worked on Mailman 2, and never on the release process itself. (A short pause for M-x all-hail-mark.) I'm happy to help where I have competence on anything Mark deems necessary, and possibly stuff he doesn't think rise to the level of justifying a release. Steve From turnbull.stephen.fw at u.tsukuba.ac.jp Mon Mar 2 03:17:28 2020 From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull) Date: Mon, 2 Mar 2020 17:17:28 +0900 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> Message-ID: <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> Jim Popovitch via Mailman-Users writes: > Interestingly enough, here's a roadmap on exactly how to do it: :) Jim, you're not helping. Until there are "I'll do it" hands up, no port to Python 3 that is faithful to current Mailman 2 is viable. Pushing it just serves to annoy those who are currently doing work for Mailman that they care more about. By contrast, your question about security fixes was an entirely appropriate clarification, and #ThankYouForPersisting on that subthread. Steve From raposo at ipb.pt Mon Mar 2 03:35:49 2020 From: raposo at ipb.pt (Eduardo Costa) Date: Mon, 2 Mar 2020 08:35:49 +0000 Subject: [Mailman-Users] MM3 filter content Message-ID: Hello, How do I manage to activate and define the content filters in order to remove attachments at MM3? Best Regards -- ...................................... Eduardo Costa Centro de Comunica??es - Instituto Polit?cnico de Bragan?a raposo at ipb.pt http://www.ipb.pt/~raposo/ ...................................... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3619 bytes Desc: S/MIME Cryptographic Signature URL: From jimpop at domainmail.org Mon Mar 2 11:56:34 2020 From: jimpop at domainmail.org (Jim Popovitch) Date: Mon, 02 Mar 2020 11:56:34 -0500 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> Message-ID: <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> On Mon, 2020-03-02 at 17:17 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > Interestingly enough, here's a roadmap on exactly how to do it: :) > > Jim, you're not helping. Stephen, thank you for taking the time to respond. Although I would have preferred you respond to the questions that I asked, I believe I can now see why you don't want to. Your "Dave Matthews" subthread sent me down a youtube rabbit's hole of Barry's videos and links. TBH, I can see why bringing those to the surface aren't favorable. Barry's roadmap for Python2 -> Python3 seems to counter the narrative that MM2 is ill- advised to be ported to Python3 (btw, that was posted in Jan of this year). > Until there are "I'll do it" hands up, no > port to Python 3 that is faithful to current Mailman 2 is viable. That is a piece of a much bigger puzzle. How are we to attract interest in coding for MM2 when (omg wow) for the past 10+ years key people have been drumming a beat that MM2 is dead. > Pushing it just serves to annoy those who are currently doing work for > Mailman that they care more about. I get that, but others may care more about MM2, you yourself have even somewhat begrudgingly acknowledged this. > By contrast, your question about security fixes was an entirely > appropriate clarification, and #ThankYouForPersisting on that > subthread. #Mailman3MightBeTheNewNewCoke :-) -Jim P. From mark at msapiro.net Mon Mar 2 12:43:44 2020 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 2 Mar 2020 09:43:44 -0800 Subject: [Mailman-Users] MM3 filter content In-Reply-To: References: Message-ID: <2c2c10f5-292c-6b86-4961-8538beaf3bcb@msapiro.net> On 3/2/20 12:35 AM, Eduardo Costa via Mailman-Users wrote: > Hello, > > How do I manage to activate and define the content filters in order to > remove attachments at MM3? The list for questions about Mailman 3 is mailman-users at mailman3.org . That said, the MM 3 settings Filter content, Collapse alternatives and Convert html to plaintext are exposed in Postorius -> Settings -> Alter messages. The other settings: filter_action, filter_extensions, filter_types, pass_extensions and pass_types are not currently exposed in Postorius. They can be set via mailman shell. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Mon Mar 2 13:54:33 2020 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 2 Mar 2020 10:54:33 -0800 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> Message-ID: <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> On 3/2/20 8:56 AM, Jim Popovitch via Mailman-Users wrote: > Barry's roadmap > for Python2 -> Python3 seems to counter the narrative that MM2 is ill- > advised to be ported to Python3 (btw, that was posted in Jan of this > year). The question is what do people want when they say they want Mailman 2 ported to Python 3. If it means, porting to Python 3 and fixing a few things on the way such as adding a real backend database, a concept of "user" and a REST API, it's at least partially done. It's Mailman 3 core. If it means cloning the MM 2.1 web UI and pipermail archiver, that is almost certainly not worth the effort. A compromise is exactly what Brian proposes. Mailman 3 with a new web UI, light weight, not based on Django and easy to install. Mailman 3 was explicitly designed to be separate from a web management UI and Archiver and to allow different implementations of those to integrate easily with core. Postorius and HyperKitty are part of Mailman 3 because we needed something and that is what people were willing to commit to do. We always hoped there would be alternatives, and it seems that now Brian is working on one. There's room for more. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geek at uniserve.com Mon Mar 2 12:08:17 2020 From: geek at uniserve.com (Dave Stevens) Date: Mon, 2 Mar 2020 09:08:17 -0800 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> Message-ID: <20200302090817.0d0f0809@dave-900X1B> On Sat, 29 Feb 2020 10:53:19 -0500 Jim Popovitch via Mailman-Users wrote: > but I have vague recollections that both Barry and Mark have > > said repeatedly that doing so would be substantially anything built on the MM2 > > architecture. assuming that's so I think the "anything built on the MM2 architecture" is perhaps misconceived. I don't need to be told that MM2 is awkward to set up and run but millions of people get and send mail that way every day and it mostly "just works." This very large body of users it what matters most to actually getting work done, not the developers' wishes and preferences - "more effort than they are willing to put into...". I think increasingly as time goes by that the new New Coke analogy is a good fit. D From jimpop at domainmail.org Mon Mar 2 16:55:40 2020 From: jimpop at domainmail.org (Jim Popovitch) Date: Mon, 02 Mar 2020 16:55:40 -0500 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> Message-ID: <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> On Mon, 2020-03-02 at 10:54 -0800, Mark Sapiro wrote: > On 3/2/20 8:56 AM, Jim Popovitch via Mailman-Users wrote: > > > Barry's roadmap > > for Python2 -> Python3 seems to counter the narrative that MM2 is ill- > > advised to be ported to Python3 (btw, that was posted in Jan of this > > year). > > The question is what do people want when they say they want Mailman 2 > ported to Python 3. I believe they want Mailman 2, as it is today, but with a fully supported language that it depends on. Lets be clear, the upgrade from MM2 to MM3 is not the same as a traditional upgrade path, MM3 is a whole new application. It's an application upgrade the same way the Space Shuttle was an upgrade from the Apollo capsules. Different designs, whole new concepts, years of pie-in-the-sky and dry marker dust. While that is important to some, it may not matter to others (and I think that is the situation today). I really want to know who all the "we need a REST interface now!" people are. I'm reminded of that great diagram from years past about "what the customer wanted", "what the developer envisioned", "what the tester tested", etc. It's a great reminder of how quagmires are created. > If it means, porting to Python 3 and fixing a few things on the way such > as adding a real backend database, a concept of "user" and a REST API, > it's at least partially done. It's Mailman 3 core. > > If it means cloning the MM 2.1 web UI and pipermail archiver, that is > almost certainly not worth the effort. There are plenty of people who are still happy with pipermail and some of the other search options (Google, htdig, etc) What benefit does a REST api provide to church groups, and tech lists like nanog or mailop? BTW, I've run some technical discussion lists for 2 decades now, I can recall the number of times someone has said "we need an archive search feature" on 1 hand. > A compromise is exactly what Brian proposes. Mailman 3 with a new web > UI, light weight, not based on Django and easy to install. Mailman 3 was > explicitly designed to be separate from a web management UI and Archiver > and to allow different implementations of those to integrate easily with > core. While I applaud Brian's efforts, I'm not convinced that I would run PHP on a public facing portal, even in 2020. But that's just me, others may feel differently. > Postorius and HyperKitty are part of Mailman 3 because we needed > something and that is what people were willing to commit to do. We > always hoped there would be alternatives, and it seems that now Brian is > working on one. There's room for more. -Jim P. From brian_carpenter at emwd.com Mon Mar 2 17:07:45 2020 From: brian_carpenter at emwd.com (Brian Carpenter) Date: Mon, 2 Mar 2020 17:07:45 -0500 Subject: [Mailman-Users] The last release from the GNU Mailman project In-Reply-To: <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> Message-ID: <097a8d95-16dc-78f8-2911-6d78ca79928d@emwd.com> On 3/2/20 4:55 PM, Jim Popovitch via Mailman-Users wrote: > While I applaud Brian's efforts, I'm not convinced that I would run PHP > on a public facing portal, even in 2020. But that's just me, others may > feel differently. And so it begins. -- 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/ From mark at msapiro.net Mon Mar 2 20:18:50 2020 From: mark at msapiro.net (Mark Sapiro) Date: Mon, 2 Mar 2020 17:18:50 -0800 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> Message-ID: <89a6bfea-b6dc-5a49-3fee-a461d4697042@msapiro.net> On 3/2/20 1:55 PM, Jim Popovitch via Mailman-Users wrote: > > There are plenty of people who are still happy with pipermail and some > of the other search options (Google, htdig, etc) What benefit does a > REST api provide to church groups, and tech lists like nanog or mailop? It provides a stable, documented management interface so people can create their own web UIs to control Mailman 3 in whatever way they want. Granted your end user's aren't going to do this, but the people who want it can, and more easily than by porting Mailman 2.1 to Python 3. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From bernie at fantasyfarm.com Tue Mar 3 05:25:03 2020 From: bernie at fantasyfarm.com (Bernie Cosell) Date: Tue, 03 Mar 2020 05:25:03 -0500 Subject: [Mailman-Users] multiple explicit reply addresses? Message-ID: <5E5E307F.23453.E4A06D5@bernie.fantasyfarm.com> I don't want to break my lists, so I'll ask first..:o) Does mailman do the right thing if I want explicit replies to go to two addresses? It seems very explicit that the explicit reply address is singular.. would making it e1 at x.com, e2 at y.com work? /Bernie\ Bernie Cosell bernie at fantasyfarm.com -- Too many people; too few sheep -- From jimpop at domainmail.org Tue Mar 3 09:47:33 2020 From: jimpop at domainmail.org (Jim Popovitch) Date: Tue, 03 Mar 2020 09:47:33 -0500 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <89a6bfea-b6dc-5a49-3fee-a461d4697042@msapiro.net> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> <89a6bfea-b6dc-5a49-3fee-a461d4697042@msapiro.net> Message-ID: <27cefe3fa65898ac2baf9a974dcbfe44ff60c65b.camel@domainmail.org> On Mon, 2020-03-02 at 17:18 -0800, Mark Sapiro wrote: > On 3/2/20 1:55 PM, Jim Popovitch via Mailman-Users wrote: > > There are plenty of people who are still happy with pipermail and some > > of the other search options (Google, htdig, etc) What benefit does a > > REST api provide to church groups, and tech lists like nanog or mailop? > > It provides a stable, documented management interface so people can > create their own web UIs to control Mailman 3 in whatever way they want. > Granted your end user's aren't going to do this, but the people who want > it can, and more easily than by porting Mailman 2.1 to Python 3. Can you share with me (us) the number and size, along with the industry or operations arena, of those people who are creating their own web UI. I honestly don't believe that there is that much interest for that outside of a handful of entities (Brian, CPanel, Canonical, and LinkedIn?). I feel like if the interest was greater, we'd see more evidence of that in the Gitlab issue tracker and or on the MM3 lists. Convince me that I'm wrong. -Jim P. From mark at msapiro.net Tue Mar 3 11:26:04 2020 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 3 Mar 2020 08:26:04 -0800 Subject: [Mailman-Users] multiple explicit reply addresses? In-Reply-To: <5E5E307F.23453.E4A06D5@bernie.fantasyfarm.com> References: <5E5E307F.23453.E4A06D5@bernie.fantasyfarm.com> Message-ID: On 3/3/20 2:25 AM, Bernie Cosell wrote: > I don't want to break my lists, so I'll ask first..:o) Does mailman do the right > thing if I want explicit replies to go to two addresses? It seems very explicit that > the explicit reply address is singular.. would making it e1 at x.com, e2 at y.com > work? It won't work. The code uses email.utils.parseaddr() which accepts various display-name and address formats, but only one address. 'e1 at x.com, e2 at y.com' will result in only 'e1 at x.com' in the Reply-To:. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From luscheina at yahoo.de Tue Mar 3 11:43:05 2020 From: luscheina at yahoo.de (Christian F Buser) Date: Tue, 3 Mar 2020 17:43:05 +0100 Subject: [Mailman-Users] multiple explicit reply addresses? In-Reply-To: References: <5E5E307F.23453.E4A06D5@bernie.fantasyfarm.com> Message-ID: <4d1d713f-c024-1f04-389b-37a2d6f250ee@yahoo.de> My work-around would then be: Set up an address on my server, say specialrepy at mydomain.dom, which acts as a forwarder to the two addresses e1 at x.com and e1 at y.com Christian Mark Sapiro schrieb am 03.03.20 um 17:26: > On 3/3/20 2:25 AM, Bernie Cosell wrote: >> I don't want to break my lists, so I'll ask first..:o) Does mailman do the right >> thing if I want explicit replies to go to two addresses? It seems very explicit that >> the explicit reply address is singular.. would making it e1 at x.com, e2 at y.com >> work? > It won't work. The code uses email.utils.parseaddr() which accepts > various display-name and address formats, but only one address. > 'e1 at x.com, e2 at y.com' will result in only 'e1 at x.com' in the Reply-To:. > From luscheina at yahoo.de Tue Mar 3 11:43:05 2020 From: luscheina at yahoo.de (Christian F Buser) Date: Tue, 3 Mar 2020 17:43:05 +0100 Subject: [Mailman-Users] multiple explicit reply addresses? In-Reply-To: References: <5E5E307F.23453.E4A06D5@bernie.fantasyfarm.com> Message-ID: <4d1d713f-c024-1f04-389b-37a2d6f250ee@yahoo.de> My work-around would then be: Set up an address on my server, say specialrepy at mydomain.dom, which acts as a forwarder to the two addresses e1 at x.com and e1 at y.com Christian Mark Sapiro schrieb am 03.03.20 um 17:26: > On 3/3/20 2:25 AM, Bernie Cosell wrote: >> I don't want to break my lists, so I'll ask first..:o) Does mailman do the right >> thing if I want explicit replies to go to two addresses? It seems very explicit that >> the explicit reply address is singular.. would making it e1 at x.com, e2 at y.com >> work? > It won't work. The code uses email.utils.parseaddr() which accepts > various display-name and address formats, but only one address. > 'e1 at x.com, e2 at y.com' will result in only 'e1 at x.com' in the Reply-To:. > From mark at msapiro.net Tue Mar 3 12:26:18 2020 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 3 Mar 2020 09:26:18 -0800 Subject: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses) In-Reply-To: <27cefe3fa65898ac2baf9a974dcbfe44ff60c65b.camel@domainmail.org> References: <1bd9ad85-1fbf-97bd-0203-93573ca06ebc.ref@bellsouth.net> <1bd9ad85-1fbf-97bd-0203-93573ca06ebc@bellsouth.net> <2812ac4e-693f-27ca-1344-2e8ed6b63781@msapiro.net> <13721b1b-a0a1-b764-d1d8-f686929a40f4@msapiro.net> <8006602E-7393-407A-B34A-EB8434512A43@billmail.scconsult.com> <24156.49432.426002.299608@turnbull.sk.tsukuba.ac.jp> <88f0f53a741081609b6280a757e4cb8430bf5764.camel@domainmail.org> <6c0da0d0-a6c3-8131-1777-323ac8517446@msapiro.net> <963b4029d28a8bf2f728caf9fa4aa737257d103d.camel@domainmail.org> <89a6bfea-b6dc-5a49-3fee-a461d4697042@msapiro.net> <27cefe3fa65898ac2baf9a974dcbfe44ff60c65b.camel@domainmail.org> Message-ID: <6ed7c2d8-eb89-5197-39f4-e812ec42e239@msapiro.net> On 3/3/20 6:47 AM, Jim Popovitch via Mailman-Users wrote: > > Can you share with me (us) the number and size, along with the industry > or operations arena, of those people who are creating their own web UI. I have no information about that. > I honestly don't believe that there is that much interest for that > outside of a handful of entities (Brian, CPanel, Canonical, and > LinkedIn?). I feel like if the interest was greater, we'd see more > evidence of that in the Gitlab issue tracker and or on the MM3 lists. > Convince me that I'm wrong. By the same reasoning, if there was real interest in porting the Mailman 2.1 code base to Python 3, we'd be seeing that too. I'm not trying to convince you of anything. All I'm saying is what I've said all along and that is that I believe that if you want a smaller, easier to install Python 3 based Mailman, the best way to accomplish that is to build a light weight, non-Django web UI that communicates with Mailman 3 core via the REST API and, for Python at least, the existing mailmanclient bindings. If you believe some other way is better, that's fine. It doesn't matter to me because I'm not doing it. I am willing and available to help anyone such as Brian with implementation of an alternative to Postorius to the extent that I can. There are already alternatives to HyperKitty. There is the 'prototype' archiver which archives messages in maildir format and also the ability to archive to mail-archive.com and MHonArc. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Jason at zx2c4.com Wed Mar 11 21:11:28 2020 From: Jason at zx2c4.com (Jason A. Donenfeld) Date: Wed, 11 Mar 2020 19:11:28 -0600 Subject: [Mailman-Users] rejecting messages with any HTML Message-ID: Hi, I run several mailing lists over at lists.zx2c4.com using mailman 2.1.30rc1. I would like to reject incoming messages that have any HTML parts in them at all. Or, perhaps, I'd like to whitelist a few different mimetypes, and reject incoming messages with parts that don't match. I noticed that mailman has a feature to strip out disallowed mimetypes, and also to reject messages that are empty after such stripping. But I could not find a button to reject the entire message (with a nice reject reply, preferably) based on the presence of a certain mimetype. Am I missing something? I should note that this isn't an unusual desire. Several kernel-orienting lists, such as netdev at vger.kernel.org, will reject your message if it has HTML in any part of it, and send you back an email letting you know what happened. Thanks in advance for your help. Regards, Jason From mark at msapiro.net Thu Mar 12 03:25:03 2020 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 12 Mar 2020 07:25:03 +0000 Subject: [Mailman-Users] rejecting messages with any HTML In-Reply-To: References: Message-ID: On March 12, 2020 1:11:28 AM GMT+00:00, "Jason A. Donenfeld" wrote: >Hi, > >I run several mailing lists over at lists.zx2c4.com using mailman >2.1.30rc1. I would like to reject incoming messages that have any HTML >parts in them at all. Or, perhaps, I'd like to whitelist a few >different mimetypes, and reject incoming messages with parts that >don't match. I noticed that mailman has a feature to strip out >disallowed mimetypes, and also to reject messages that are empty after >such stripping. But I could not find a button to reject the entire >message (with a nice reject reply, preferably) based on the presence >of a certain mimetype. Am I missing something? No. Mailman has no such facility. >I should note that this isn't an unusual desire. Several >kernel-orienting lists, such as netdev at vger.kernel.org, will reject >your message if it has HTML in any part of it, and send you back an >email letting you know what happened. Given that many, if not most, user's MUAs send multipart/alternative "text", this seems to be something that would be problematic for all but lists with highly technical users. -- Mark Sapiro Sent from my Not_an_iThing with standards compliant, open source software. From keld at keldix.com Mon Mar 16 16:20:38 2020 From: keld at keldix.com (keld at keldix.com) Date: Mon, 16 Mar 2020 21:20:38 +0100 Subject: [Mailman-Users] mailman queues Message-ID: <20200316202038.GA26761@www5.open-std.org> I have a problem with removing failing subscription requests eg from a bogus requester. I thought I could remove the request from a queue somewhere but cannot find it. the subscription requests keep recurring, over 1000 in my maillog -postfix I looked in /var/spool/mailman , but no ordinary files in the dirs. running 2.1.9 in a somewhat complex env, mulitiple domains. keld From mark at msapiro.net Tue Mar 17 10:05:03 2020 From: mark at msapiro.net (Mark Sapiro) Date: Tue, 17 Mar 2020 07:05:03 -0700 Subject: [Mailman-Users] mailman queues In-Reply-To: <20200316202038.GA26761@www5.open-std.org> References: <20200316202038.GA26761@www5.open-std.org> Message-ID: On 3/16/20 1:20 PM, keld at keldix.com wrote: > I have a problem with removing failing subscription requests > eg from a bogus requester. I thought I could remove the request > from a queue somewhere but cannot find it. > the subscription requests keep recurring, over 1000 in my maillog -postfix The requests waiting user confirmation are in the file lists/LIST_NAME/pending.pck. Requests waiting moderator action are in the file lists/LIST_NAME/requests.pck. There are scripts at (mirrored at ) which can help with this. In particular, "erase" and "list_requests". Also, the withlist script "discard_subs.py". More recent Mailman has defenses against robotic web subscribes, but none are in 2.1.9. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From chris at dubna.co.uk Wed Mar 18 08:06:30 2020 From: chris at dubna.co.uk (scoutdubna) Date: Wed, 18 Mar 2020 05:06:30 -0700 (MST) Subject: [Mailman-Users] New installation sudo /etc/init.d/mailman start Message-ID: <1584533190931-0.post@n7.nabble.com> I have made a new installation of mailman using https://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze This is on an Ubuntu 18.04 server hosted by IONOS I get all the way through but when I input the start command sudo /etc/init.d/mailman start I get the error sudo: /etc/init.d/mailman: command not found Any ideas please? CHRIS -- Sent from: http://mailman.9.n7.nabble.com/Mailman-Users-f3.html From mailman-admin at uni-konstanz.de Fri Mar 20 10:21:46 2020 From: mailman-admin at uni-konstanz.de (Mailman-admin) Date: Fri, 20 Mar 2020 15:21:46 +0100 Subject: [Mailman-Users] New installation sudo /etc/init.d/mailman start In-Reply-To: <1584533190931-0.post@n7.nabble.com> References: <1584533190931-0.post@n7.nabble.com> Message-ID: <1be94290-05d8-a9e2-01a3-b4d4af7e1b9a@uni-konstanz.de> Hello Am 18.03.20 um 13:06 schrieb scoutdubna: > > I have made a new installation of mailman using > https://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze > > This is on an Ubuntu 18.04 server hosted by IONOS > > I get all the way through but when I input the start command > sudo /etc/init.d/mailman start > I get the error sudo: /etc/init.d/mailman: command not found > > Any ideas please? > Ubuntu 18.04 uses mostly systemd. Try: sudo service mailman start or sudo systemctl start mailman Kind regards, Christian Mack From eddydonovan04 at gmail.com Fri Mar 20 04:37:48 2020 From: eddydonovan04 at gmail.com (eddydonovan) Date: Fri, 20 Mar 2020 01:37:48 -0700 (MST) Subject: [Mailman-Users] Find a smtp server to send out emails In-Reply-To: References: Message-ID: <1584693468990-0.post@n7.nabble.com> You could definitely try other SMTP services like Sendinblue, Pepipost, etc. I have found more at - https://digitalmarketingtipsy.com/email-marketing/best-smtp-services/ and also at https://digitalmarketingtipsy.com/email-marketing/best-smtp-servers/ These posts feature some good SMTP servers that I too use for personal use. -- Sent from: http://mailman.9.n7.nabble.com/Mailman-Users-f3.html From chris at dubna.co.uk Sun Mar 22 09:33:05 2020 From: chris at dubna.co.uk (scoutdubna) Date: Sun, 22 Mar 2020 06:33:05 -0700 (MST) Subject: [Mailman-Users] New installation sudo /etc/init.d/mailman start In-Reply-To: <1be94290-05d8-a9e2-01a3-b4d4af7e1b9a@uni-konstanz.de> References: <1584533190931-0.post@n7.nabble.com> <1be94290-05d8-a9e2-01a3-b4d4af7e1b9a@uni-konstanz.de> Message-ID: <1584883985320-0.post@n7.nabble.com> Christian Mack Thanks for your reply. Blooming obvious now you have pointed it out. I had to do one or two more things to get the web interface to work eg implement cgi but now at least that part is working. Thanks again. CHRIS -- Sent from: http://mailman.9.n7.nabble.com/Mailman-Users-f3.html