[Mailman-Users] Mailman Update...

Mark Sapiro msapiro at value.net
Wed Jan 17 01:22:09 CET 2007


maillists wrote:
>
>I am about to do an update from Mailman 2.1.1 to 2.1.9
>
>This is on an older RedHat 9 box. 
>My Python version is 2.2.2 
>I believe that Mailman is installed via RPM. 

I don't think it is as bad as Brad indicates in his reply. I think
running configure with "--prefix=/var/mailman" will get you close on
older RedHat. You'll probably also need --with-cgi-gid and
--with-mail-gid (see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.016.htp>).

A more serious issue is Mailman 2.1.9 requires Python 2.3. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq05.008.htp>
which contains a link to a post containing a work around.


>when I run "rpm qa |grep mailman" I get the following:
>mailman-2.1.1-5
>
>My mailman "home" directory is /var/mailman


The --prefix above takes care of that.


>I also have files in /var/log/mailman, /var/spool/mailman/


These are set in mm_cfg.py which will not be overwritten by 'make
install'


>I basically have some questions and need moral support before I do
>this...
>
>I have lots of files in: 
>/var/mailman/qfiles/shunt/ ans also /var/mailman/qfiles/bad/
>What should I do with these?
>Were these old email messages that were never delivered?


You don't need to do anything, but probably 'old' files should just be
deleted. The messages in shunt/ were messages that encountered some
error in processing and were shunted. There were messages in Mailman's
'error' log for each one, but these have been probably logrotated into
oblivion.

The messages in bad/ are messages which were 'preserved' by content
filtering's filter_action.


>(I did have a problem with one of my lists not sending mail...)


That may be the source of the shunted messages.


>I downloaded the tarball of 2.1.9. the UPGRADE file said that the
>"upgrade" script would automatically run. Does this mean tht I should
>just do the ./configure thing as if this is a new install?  Does this
>take care of everything? 


Assuming you get the right options to configure, 'make install' will
take care of everything.


>Finally is there anything that I should watch out for, or does anybody
>see if I might be heading for disaster?


See above regarding Python incompatability.

-- 
Mark Sapiro <msapiro at value.net>       The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan



More information about the Mailman-Users mailing list