Bug 1045783 - mailman crashes when moderating a message
Summary: mailman crashes when moderating a message
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mailman
Version: 6.6
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Pavel Šimerda (pavlix)
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-21 23:41 UTC by John Byrd
Modified: 2016-07-20 10:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-20 10:09:31 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description John Byrd 2013-12-21 23:41:54 UTC
Description of problem:

Using RHEL 6.5, if you install and operate a moderated mailing list via the Web interface using mailman, mailman will crash when the moderator selects and approves a message for the mailing list.

Call stack on crash will look like the following:

> admin(20706): Traceback (most recent call last):
> admin(20706):   File "/usr/lib/mailman/scripts/driver", line 112, in
> run_main
> admin(20706):     main()
> admin(20706):   File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 165,
> in main
> admin(20706):     process_form(mlist, doc, cgidata)
> admin(20706):   File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 716,
> in process_form
> admin(20706):     forward, forwardaddr)
> admin(20706):   File "/usr/lib/mailman/Mailman/ListAdmin.py", line 167, in
> HandleRequest
> admin(20706):     forward, addr)
> admin(20706):   File "/usr/lib/mailman/Mailman/ListAdmin.py", line 254, in
> __handlepost
> admin(20706):     g(msg, 1)
> admin(20706): AttributeError: Generator instance has no __call__ method

Version-Release number of selected component (if applicable):

mailman.x86_64, 3:2.1.12-18.el6 

Mark Sapiro points out on the mailman mailing list that there is an incompatibility between Python 2.6 and mailman 2.1.12.  He also references 
a patch that causes this problem to go away:

https://mail.python.org/pipermail/mailman-users/2013-December/075829.html

Mailman appears to work correctly upon install, but you can't actually moderate any messages with the current RHEL6 version shipping.

Comment 9 Pavel Šimerda (pavlix) 2016-07-20 10:09:31 UTC
(In reply to John Byrd from comment #0)
> Description of problem:
> 
> Using RHEL 6.5, if you install and operate a moderated mailing list via the
> Web interface using mailman, mailman will crash when the moderator selects
> and approves a message for the mailing list.
> 
> Call stack on crash will look like the following:
> 
> > admin(20706): Traceback (most recent call last):
> > admin(20706):   File "/usr/lib/mailman/scripts/driver", line 112, in
> > run_main
> > admin(20706):     main()
> > admin(20706):   File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 165,
> > in main
> > admin(20706):     process_form(mlist, doc, cgidata)
> > admin(20706):   File "/usr/lib/mailman/Mailman/Cgi/admindb.py", line 716,
> > in process_form
> > admin(20706):     forward, forwardaddr)
> > admin(20706):   File "/usr/lib/mailman/Mailman/ListAdmin.py", line 167, in
> > HandleRequest
> > admin(20706):     forward, addr)
> > admin(20706):   File "/usr/lib/mailman/Mailman/ListAdmin.py", line 254, in
> > __handlepost
> > admin(20706):     g(msg, 1)
> > admin(20706): AttributeError: Generator instance has no __call__ method
> 
> Version-Release number of selected component (if applicable):
> 
> mailman.x86_64, 3:2.1.12-18.el6 
> 
> Mark Sapiro points out on the mailman mailing list that there is an
> incompatibility between Python 2.6 and mailman 2.1.12.  He also references 
> a patch that causes this problem to go away:
> 
> https://mail.python.org/pipermail/mailman-users/2013-December/075829.html
> 
> Mailman appears to work correctly upon install, but you can't actually
> moderate any messages with the current RHEL6 version shipping.

This patch has apparently been already applied. I'm looking at the source file in mailman-2.1.12-25.el6.x86_64. Please reopen or file a new bug report if you still have issues with the latest version.

Comment 10 Ian Collier 2016-07-20 10:20:33 UTC
Correct, it was patched for bug 765807 which appears to be a duplicate of this one.


Note You need to log in before you can comment on or make changes to this bug.