[Mailman-Users] Re: Archive Issue

On 9/17/20 4:49 PM, Dennis Putnam wrote: >   > I'll give that a try tomorrow. In the meantime I discovered something > that may or may not be relevant. Apparently the last saved archive was > in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to > resolve the DMARC problem. I am bett

[Mailman-Users] Re: Archive Issue

On 9/17/2020 5:34 PM, Mark Sapiro wrote: > On 9/17/20 11:50 AM, Dennis Putnam wrote: >> Hit a bug page. Note this is the production server running 2.1.15 but >> the test server running 2.1.34 got the same thing. This is the error log: >> >> Sep 17 12:37:13 2020 admin(24458): >>

[Mailman-Users] Re: mailman v2.x

On 9/17/2020 3:59 PM, Phil Stracchino wrote: ... The writing has been on the wall for Python2 for nearly ten years. The EOL date has already been extended five years. It's time to let it go. The big concern du jour in science community is: can you take your scripts from 10 years ago and r

[Mailman-Users] Re: Archive Issue

On 9/17/20 11:50 AM, Dennis Putnam wrote: > Hit a bug page. Note this is the production server running 2.1.15 but > the test server running 2.1.34 got the same thing. This is the error log: > > Sep 17 12:37:13 2020 admin(24458): > > admin(24458): [-

[Mailman-Users] Re: mailman v2.x

On 2020-09-17 14:34, Christian F Buser via Mailman-Users wrote: > Of course I do not want do move anyone away from Mailman. If Phil absolutely > wants to retire Python 2 on his machine(s), And that is precisely my motivation. The writing has been on the wall for Python2 for nearly ten years. Th

[Mailman-Users] Re: mailman v2.x

On 2020-09-17 13:59, Christian F Buser wrote: > I am in no way a programmer - but as I understand it, Python 2 can live > alongside Python 3 without any problems. Oh, indeed, it totally can. And right now, it does, on two of my three Linux boxes. I've managed to get Python2 completely off the

[Mailman-Users] Re: Archive Issue

On 9/17/2020 2:13 PM, Dennis Putnam wrote: I know. That is what Mark is trying to help me fix. Public contains all the archives rather than private so creating a symlink will destroy the archives. ??? Can't you move it? Dima -- Mailman-Users

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 14:56 -0400, Brian Carpenter wrote: > On 9/17/20 2:27 PM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-09-17 at 14:15 -0400, Brian Carpenter wrote: > > Absolutely not. I'm intrigued by the idea of mailman-core (1/3 of mm3) > > with a lightweight web-based GUI in fr

[Mailman-Users] Re: Archive Issue

On 9/17/2020 2:57 PM, Dmitri Maziuk wrote: > On 9/17/2020 1:50 PM, Dennis Putnam wrote: > >> admin(24458): OSError: [Errno 21] Is a directory: >> '/var/lib/mailman/archives/public/rushtalk' > > ICBW but files in public/ should be symlinks to subdirs in private/ > i.e. public/rushtalk should be a sy

[Mailman-Users] Re: Archive Issue

On 9/17/2020 1:50 PM, Dennis Putnam wrote: admin(24458): OSError: [Errno 21] Is a directory: '/var/lib/mailman/archives/public/rushtalk' ICBW but files in public/ should be symlinks to subdirs in private/ i.e. public/rushtalk should be a symlink to private/rushtalk and not a directory. Dima

[Mailman-Users] Re: mailman v2.x

On 9/17/20 2:27 PM, Jim Popovitch via Mailman-Users wrote: On Thu, 2020-09-17 at 14:15 -0400, Brian Carpenter wrote: Absolutely not. I'm intrigued by the idea of mailman-core (1/3 of mm3) with a lightweight web-based GUI in front of it. But, to date, that doesn't exist. I also don't see the nee

[Mailman-Users] Re: Archive Issue

On 9/17/2020 1:06 PM, Mark Sapiro wrote: > OK. First make a backup of /var/lib/mailman/archives/public/ just in > case, although it appears that > /var/lib/mailman/archives/private/rushtalk is more up to date. Then go > to the web admin UI for both the mailman and rushtalk lists and set > Archiving

[Mailman-Users] Re: mailman v2.x

Hello Brian Carpenter. On Thu, 17 Sep 2020 14:20:06 -0400, you wrote: > I am sure Christian also meant to include me in their list of other > choices: https://harmonylists.com. At least I still offer Mailman 3 > howbeit as a SaaS provider and not encourage a fellow mailman user on > a mailman u

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 14:15 -0400, Brian Carpenter wrote: > On 9/17/20 1:45 PM, Jim Popovitch via Mailman-Users wrote: > > That's kind of my point. mm2 works for me and my use, I'd much rather > > prefer to keep it working than to rip it out and replace it, including > > installed and maintaining a

[Mailman-Users] Re: mailman v2.x

On 9/17/20 1:59 PM, Christian F Buser via Mailman-Users wrote: I am in no way a programmer - but as I understand it, Python 2 can live alongside Python 3 without any problems. The EOL declaration for Python 2 does NOT mean that Python 2 will stop working on the date the publishers announced. T

[Mailman-Users] Re: mailman v2.x

On 9/17/20 1:45 PM, Jim Popovitch via Mailman-Users wrote: That's kind of my point. mm2 works for me and my use, I'd much rather prefer to keep it working than to rip it out and replace it, including installed and maintaining a database, a framework, a new setup of custom admin scripts unique to

[Mailman-Users] Re: mailman v2.x

Hello Phil Stracchino. On Thu, 17 Sep 2020 12:37:08 -0400, you wrote: > .. Except for the part where it requires me to keep Python 2 installed > beyond its second, extended, we absolutely mean it this time, no more > extensions, declared EOL. > > It's not that I need anything Mailman 2 doesn't do

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 09:07 -0700, Mark Sapiro wrote: > On 9/17/20 8:04 AM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > > > Forward to where? > > > > Oh the irony of you asking that question. :) If we go back a year, > > there were STARK warn

[Mailman-Users] Re: Archive Issue

On 9/17/20 9:39 AM, Dennis Putnam wrote: > On 9/17/2020 12:29 PM, Mark Sapiro wrote: >> On 9/17/20 9:06 AM, Dennis Putnam wrote: >> >> Before doing anything, show me the results of >> ls -la /var/lib/mailman/archives/public/ > # ls -la /var/lib/mailman/archives/public/ > total 44 > drwxrwsr-x.   4

[Mailman-Users] Re: mailman v2.x

On 2020-09-17 12:07, Mark Sapiro wrote: > If Mailman 2.1 meets their needs now, why won't it continue to do so as > it is? (Aside: I still sometimes use Adobe Reader 9 for Linux on my > desktop even though it has been unsupported and unavailable from Adobe > for years.) Weighing in on this questi

[Mailman-Users] Re: mailman v2.x

On 9/17/2020 9:24 AM, Brian Carpenter wrote: FYI, here is a decent comparison of Django vs Flask: https://hackr.io/blog/flask-vs-django In the article, this was said: "Django is suited for bigger projects that need a lot of functionality. For simpler projects, the features might be an overdo

[Mailman-Users] Re: Archive Issue

On 9/17/2020 12:29 PM, Mark Sapiro wrote: > On 9/17/20 9:06 AM, Dennis Putnam wrote: > > Before doing anything, show me the results of > ls -la /var/lib/mailman/archives/public/ # ls -la /var/lib/mailman/archives/public/ total 44 drwxrwsr-x.   4 root mailman    37 Jul 31  2019 . drwxrwsr-x.   4 roo

[Mailman-Users] Re: Archive Issue

On 9/17/20 9:06 AM, Dennis Putnam wrote: > There are no sym links. Private looks like just place holders as there > is no data there nor any archives. It looks like everything is in > public. The ownership is root:mailman and the group has R/O permissions. > Only root has write. I'm assuming that

[Mailman-Users] Re: mailman v2.x

On 9/17/20 8:04 AM, Jim Popovitch via Mailman-Users wrote: > On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: >> >> Forward to where? > > Oh the irony of you asking that question. :) If we go back a year, > there were STARK warnings about the EOL of mm2. Blatant EOL warnings. > To me, a "p

[Mailman-Users] Re: Archive Issue

On 9/17/2020 11:40 AM, Mark Sapiro wrote: > > What makes you think messages aren't being archived? Because when I look at it via the web, the emails I sent as a test are not there. There is no September 2020 link and the date on the mbox file is old (Feb 2020). > > Is your archive public? If so, is

[Mailman-Users] Re: Archive Issue

On 9/17/20 7:56 AM, Dennis Putnam wrote: > On 9/17/2020 10:43 AM, Mark Sapiro wrote: >> >> Is ArchRunner running? Are there entries in /var/spool/mailman/archive/? > Looks like it: What makes you think messages aren't being archived? Is your archive public? If so, is /var/lib/mailman/archives/p

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > On 9/17/20 7:36 AM, Jim Popovitch via Mailman-Users wrote: > > Here's my POV, if mm2 can (and it appears to me that it > > can somewhat easily) be fixed to use py3 then all the installed bases of > > mm2 don't have to learn/deal/secure/test/ma

[Mailman-Users] Re: mailman v2.x

On 9/17/20 10:36 AM, Jim Popovitch via Mailman-Users wrote: Would it though? Is that conjecture or based on available data that can be analyzed? Here's my POV, if mm2 can (and it appears to me that it can somewhat easily) be fixed to use py3 then all the installed bases of mm2 don't have to lea

[Mailman-Users] Re: Archive Issue

On 9/17/2020 10:43 AM, Mark Sapiro wrote: > > Is ArchRunner running? Are there entries in /var/spool/mailman/archive/? Looks like it: ● mailman.service - GNU Mailing List Manager    Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled; vendor preset: disabled)    Active: active (runni

[Mailman-Users] Re: mailman v2.x

On 9/17/20 7:36 AM, Jim Popovitch via Mailman-Users wrote: > Here's my POV, if mm2 can (and it appears to me that it > can somewhat easily) be fixed to use py3 then all the installed bases of > mm2 don't have to learn/deal/secure/test/manage/deal with a REST API > and/or Flask, etc. Or they can j

[Mailman-Users] Re: Archive Issue

On 9/17/20 7:24 AM, Dennis Putnam wrote: > On 9/17/2020 9:59 AM, Mark Sapiro wrote: >> On 9/17/20 6:49 AM, Dennis Putnam wrote: >>> For some reason, messages are not being archived. I see no error in the >>> logs and check_perms says no problems found. Any suggestions on how to >>> get archive work

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 07:13 -0700, Mark Sapiro wrote: > On 9/17/20 6:54 AM, Matthew Pounsett wrote: > > If someone was going to undertake a rewrite of Postorius, using a different > > web development framework (e.g. Flask, but pretty much anything that isn't > > Django) would at least remove one ma

[Mailman-Users] Re: mailman v2.x

On 9/17/20 9:54 AM, Matthew Pounsett wrote: If someone was going to undertake a rewrite of Postorius, using a different web development framework (e.g. Flask, but pretty much anything that isn't Django) would at least remove one major moving part from the install process. We went with Laravel (

[Mailman-Users] Re: mailman v2.x

On 9/17/20 7:20 AM, Matthew Pounsett wrote: > > Yep. Sorry, that wasn't meant to sound like criticism ... And it wasn't taken as such. I'm only trying to reinforce the idea that there are opportunities for making a different MM 3 web UI that would be less complex to install, and working on that

[Mailman-Users] Re: Archive Issue

On 9/17/2020 9:59 AM, Mark Sapiro wrote: > On 9/17/20 6:49 AM, Dennis Putnam wrote: >> For some reason, messages are not being archived. I see no error in the >> logs and check_perms says no problems found. Any suggestions on how to >> get archive working? Thanks. > > Is /var/lib/mailman/archives/p

[Mailman-Users] Re: mailman v2.x

On Thu, 17 Sep 2020 at 10:14, Mark Sapiro wrote: > On 9/17/20 6:54 AM, Matthew Pounsett wrote: > > > > If someone was going to undertake a rewrite of Postorius, using a > different > > web development framework (e.g. Flask, but pretty much anything that > isn't > > Django) would at least remove o

[Mailman-Users] Re: mailman v2.x

On 9/17/20 6:54 AM, Matthew Pounsett wrote: > > If someone was going to undertake a rewrite of Postorius, using a different > web development framework (e.g. Flask, but pretty much anything that isn't > Django) would at least remove one major moving part from the install > process. I have said m

[Mailman-Users] Re: Archive Issue

On 9/17/20 6:49 AM, Dennis Putnam wrote: > For some reason, messages are not being archived. I see no error in the > logs and check_perms says no problems found. Any suggestions on how to > get archive working? Thanks. Is /var/lib/mailman/archives/private/.mbox/.mbox being updated? Are any logs

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

On 9/17/2020 9:46 AM, Mark Sapiro wrote: > On 9/17/20 1:47 AM, Dennis Putnam wrote: >> That worked perfectly. Thanks. This is the configure command I used: >> >> *./configure --prefix=/usr/lib/mailman --with-username=mailman >> --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman

[Mailman-Users] Re: mailman v2.x

On Thu, 17 Sep 2020 at 07:22, Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > Replacing Postorius with a Mailman 2 lookalike would probabaly be a > nearly complete rewrite. Of course you can reuse the HTML and perhaps > the page-generating code, but all of the "business logi

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

On 9/17/20 6:44 AM, Dennis Putnam wrote: > > I didn't have it quite right. I got this postfix error: > ... > I assumed, for lack of anything better, '*--with-mail-gid=mailman'*.  > Obviously I should have used '*--with-mail-gid=nobody*'. The > documentation was lacking on what that parameter shou

[Mailman-Users] Archive Issue

For some reason, messages are not being archived. I see no error in the logs and check_perms says no problems found. Any suggestions on how to get archive working? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users ma

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

On 9/17/20 1:47 AM, Dennis Putnam wrote: > > That worked perfectly. Thanks. This is the configure command I used: > > *./configure --prefix=/usr/lib/mailman --with-username=mailman > --with-groupname=mailman --with-cgi-gid=apache --with-mail-gid=mailman > --with-pid-dir=/var/run/mailman/ --with-c

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

On 9/17/2020 4:47 AM, Dennis Putnam wrote: > On 9/16/2020 4:33 PM, Mark Sapiro wrote: >> I have created a work in progress FAQ at >> . This contains an updated patch that >> applies cleanly to the head of the lp:mailman branch and also patches >> configure so the `

[Mailman-Users] Re: mailman v2.x

Cleaned up the @s. Jonathan M writes: > What would be fun is a “Mailman 2 lookalike” Python 3 user > interface for Mailman 3, complete with Times New Roman and Courier. The archiver part would be relatively easy to do; Pipermail is probably fairly easy to disentangle from Mailman 2. I can't s

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 18:47 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > On Thu, 2020-09-17 at 02:34 +0900, Stephen J. Turnbull wrote: > > > > You don't need to have a title, an @mailman email address, or a commit > bit > > > to do any of that. > > > > > >

[Mailman-Users] Re: mailman v2.x

Jim Popovitch via Mailman-Users writes: > On Thu, 2020-09-17 at 02:34 +0900, Stephen J. Turnbull wrote: > > You don't need to have a title, an @mailman email address, or a commit bit > > to do any of that. > > > > You just do it. > > Exactly! But that is not really what this convo is all

[Mailman-Users] Re: Manual Update on Centos 7 (RH)

On 9/16/2020 4:33 PM, Mark Sapiro wrote: > I have created a work in progress FAQ at > . This contains an updated patch that > applies cleanly to the head of the lp:mailman branch and also patches > configure so the `autoconf` step is not required. It also contains