[Mailman-Users] Anything to look out for in a 2.1.9 to 2.1.14-1upgrade?

[Steve Burling]

On 1/16/12 12:09 PM, "Mark Sapiro" <mark at msapiro.net> wrote:

> You can fix this by removing the email directory from
> /usr/lib/mailman/pythonlib so that Mailman will use the Python 2.6
> email package instead of Mailman's which is not compatible, but this
> won't fix all the Mailman 2.1.9/Python 2.6.x incompatibilities.

Would doing this also break mail delivery, since the contents of
/usr/lib64/python2.4/email (on the mail delivery machine) look very
different than the contents of /usr/lib64/python2.6/email on the web server?

At this point, the question is academic, though, see below.

> However, I have other questions.
> 
> Is RedHat distributing Mailman 2.1.9 with Python 2.6.6? If so, this is
> bad, and see <http://wiki.list.org/x/OIDD>. If not, perhaps there is a
> RedHat RPM you can use to upgrade.
> 
> OTOH, from the paths I see in the traceback above (prefix =
> /opt/mailman), it seems your current Mailman may have been installed
> from source rather than a RedHat RPM. If this is the case, just
> configure Mailman 2.1.14-1 with the same options you used for 2.1.9,
> stop mailman, make install and start mailman and you should be OK.

This is, indeed, an installation from source. I've been reading the list
long enough that I've never actually used a Red Hat packaged version of
mailman.

Red Hat is delivering mailman 2.1.12-17 with Red Hat 6.

What we think is the most straight-forward fix for this, with the least
likelihood of breaking mail delivery, is to run a limited httpd on the mail
delivery machine as http://lists.our.domain, and add a re-write rule to our
main web server to redirect references to http://www.our.domain/mailman/ to
http://lists.our.domain/mailman/ instead.

Does that seem like a reasonable approach?