[Mailman-Users] installation difficulties

[Richard Barrett]

At 23:26 11/11/2002, Emil Volcheck wrote:
>Hello, Mailman Users,
>
>I'm working with my website administrator to resolve some difficulties
>with our Mailman installation.  We're using RH Linux with Postfix MTA.
>The installation passes the check scripts for permissions and database
>consistency.  The web pages display fine.  But we can't send any mail
>to any list.
>
>Question: do the aliases for individual lists as well as the
>"mailman" and "mailman-owner" have to be in /etc/aliases or
>/etc/aliases.db or does it suffice to put them in the MySQL (?)
>databases used by Postfix?
>
>The problem I'm encountering is that a posting to the list results
>in error code 1:
>
>---
>...Command died with status 1:
>     "/home/mailman/scripts/post concerns"
>---
>(The name of the list is "concerns".)
>
>Also, I'm seeing the following error from qrunner in the
>error log repeatedly:
>
>---
>Nov 11 09:23:01 2002 qrunner(15283): Traceback (innermost last):
>Nov 11 09:23:01 2002 qrunner(15283):   File
>"/home/mailman/cron/qrunner", line 283, in ?
>Nov 11 09:23:01 2002 qrunner(15283):      kids = main(lock)
>Nov 11 09:23:01 2002 qrunner(15283):   File
>"/home/mailman/cron/qrunner", line 253, in main
>Nov 11 09:23:01 2002 qrunner(15283):      keepqueued =
>dispose_message(mlist, msg, msgdata)
>Nov 11 09:23:01 2002 qrunner(15283):   File
>"/home/mailman/cron/qrunner", line 157, in dispose_message
>Nov 11 09:23:01 2002 qrunner(15283):      mlist.ParseMailCommands(msg)
>Nov 11 09:23:01 2002 qrunner(15283):   File
>"/home/mailman/Mailman/MailCommandHandler.py", line 123, in
>ParseMailCommands
>Nov 11 09:23:01 2002 qrunner(15283):      precedence =
>msg.get('precedence', '').lower()
>Nov 11 09:23:01 2002 qrunner(15283): AttributeError :  'string' object
>has no attribute 'lower'
>---

You do not say which version of Mailman and Python you are running. This 
problem arose because some Python 2.x specific code constructs (not 
compatible with Python 1.5.2 and 1.6)  crept into some updates to MM 2.0.x.

You should be able to resolve the problem by either upgrading to MM 2.0.13 
(which removed the offending constructs) or/and upgrading to Python 2.1.3 
or 2.2.2.

You should upgrade to MM 2.0.13 even if you do not want to upgrade your Python.

>I'd appreciate any pointers or suggestions.
>
>Thanks in advance,
>
>--Emil
>
>Emil Volcheck
>volcheck at acm.org