Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On 2/17/20 2:27 AM, Dennis Putnam wrote: > It turns out that the only version available for RHEL 7 is 2.1.12. > However, the mailman documentation indicates that also has DMARC > mitigation. What documentation? I assume Red Hat's. In any case, what you will have, as others have said, is 2.1.12 with who knows what later features and fixes backported by Red Hat to make what they call 2.1.12-xx.yy, and if you run into trouble, we (this list) my not be able to help. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On 2/17/2020 11:24 AM, Lindsay Haisley (linode) wrote: This is common practice for all major distributions. The only way to keep up with upstream versions is to install from same from the git-go. This has its own pitfalls, but I do this for Mailman and have never had a problem. I'm still hoping to some day get a round tuit for trying to fit MM2 in a docker container. You know exactly what codebase you have from the git-go, and if the new one does not cut it, the good old container is still there to fall back to. The clue is strong with docker people. D -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On Feb 17, 2020, at 10:45 AM, Phil Stracchino wrote: > >> On 2020-02-17 10:56, Bill Cole wrote: >> RedHat has a policy of nailing down nominal versions of software with >> each major RHEL release and then backporting whatever fixes they deem >> important into their packages over the life of the major release, adding >> their own subordinate versioning. > An unfortunate side effect of this is that it makes it very difficult to > support some software on Red Hat because you don't know for sure what > codebase you're actually running, except that it's probably neither fish > nor fowl nor good red meat. This is common practice for all major distributions. The only way to keep up with upstream versions is to install from same from the git-go. This has its own pitfalls, but I do this for Mailman and have never had a problem. Sent from my iPhone -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On 2020-02-17 10:56, Bill Cole wrote: > RedHat has a policy of nailing down nominal versions of software with > each major RHEL release and then backporting whatever fixes they deem > important into their packages over the life of the major release, adding > their own subordinate versioning. I know from working on the > SpamAssassin security team that RH is particularly attentive to security > issues and other major bugfixes. An unfortunate side effect of this is that it makes it very difficult to support some software on Red Hat because you don't know for sure what codebase you're actually running, except that it's probably neither fish nor fowl nor good red meat. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On 17 Feb 2020, at 5:27, Dennis Putnam wrote: On 2/16/2020 11:45 PM, Stephen J. Turnbull wrote: Dennis Putnam writes: Since migrating to mailman 3 on the latest RHEL is going to take some time, I need an interim solution to DMARC mitigation. I understand version 2.1.18 Why 2.1.18? Do you have that already installed? It's already pretty old, and many of the fixes still being made are security-related. It turns out that the only version available for RHEL 7 is 2.1.12. However, the mailman documentation indicates that also has DMARC mitigation. Anyway, I am giving it a try. Seems silly that RHEL repositories are so far behind the curve. RedHat has a policy of nailing down nominal versions of software with each major RHEL release and then backporting whatever fixes they deem important into their packages over the life of the major release, adding their own subordinate versioning. I know from working on the SpamAssassin security team that RH is particularly attentive to security issues and other major bugfixes. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not For Hire (currently) -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman 2.1.18 for RHEL 5
On 2/16/2020 11:45 PM, Stephen J. Turnbull wrote: > Dennis Putnam writes: > > > Since migrating to mailman 3 on the latest RHEL is going to take some > > time, I need an interim solution to DMARC mitigation. I understand > > version 2.1.18 > > Why 2.1.18? Do you have that already installed? It's already pretty > old, and many of the fixes still being made are security-related. It turns out that the only version available for RHEL 7 is 2.1.12. However, the mailman documentation indicates that also has DMARC mitigation. Anyway, I am giving it a try. Seems silly that RHEL repositories are so far behind the curve. > > > will do what I need, at least until I can finish the > > migration. However, I have been unable to find a repository or rpm > > for that version for RHEL 5. Can someone help me out with that? > > The Red Hat or Fedora lists would be a much better place to ask. > We're not likely to know, and we can't provide much support except > generic comments since we're generally not using packaged versions of > Mailman, even for testing. We just don't have the time. > > Steve signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mailman 2.1.18 for RHEL 5
Dennis Putnam writes: > Since migrating to mailman 3 on the latest RHEL is going to take some > time, I need an interim solution to DMARC mitigation. I understand > version 2.1.18 Why 2.1.18? Do you have that already installed? It's already pretty old, and many of the fixes still being made are security-related. > will do what I need, at least until I can finish the > migration. However, I have been unable to find a repository or rpm > for that version for RHEL 5. Can someone help me out with that? The Red Hat or Fedora lists would be a much better place to ask. We're not likely to know, and we can't provide much support except generic comments since we're generally not using packaged versions of Mailman, even for testing. We just don't have the time. Steve -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mailman 2.1.18 for RHEL 5
Since migrating to mailman 3 on the latest RHEL is going to take some time, I need an interim solution to DMARC mitigation. I understand version 2.1.18 will do what I need, at least until I can finish the migration. However, I have been unable to find a repository or rpm for that version for RHEL 5. Can someone help me out with that? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
