Mailman off-track after upgrading to 11.3

English Network/Internet
#1

Mailman seems to work (the Web interface actually, I could add a subscriber as admin), but when someone tries to subsribe alone, I get this error :

admin(17420): ----- Mailman Version: 2.1.11 -----]
admin(17420): ----- Traceback ------]
admin(17420): Traceback (most recent call last):
admin(17420): File “/usr/lib/mailman/scripts/driver”, line 101, in run_main
admin(17420): main()
admin(17420): File “/usr/lib/mailman/Mailman/Cgi/subscribe.py”, line 96, in main
admin(17420): process_form(mlist, doc, cgidata, language)
admin(17420): File “/usr/lib/mailman/Mailman/Cgi/subscribe.py”, line 176, in process_form
admin(17420): mlist.AddMember(userdesc, remote)
admin(17420): File “/usr/lib/mailman/Mailman/MailList.py”, line 916, in AddMember
admin(17420): raise Errors.MMSubscribeNeedsConfirmation
admin(17420): TypeError: exceptions must be old-style classes or derived from BaseException, not str
admin(17420): ----- Python Information -----]
admin(17420): sys.version = 2.6.5 (r265:79063, Jul 5 2010, 11:47:21)

This looks like an incompatibility between mailman’s version and Python’s.
Anyone know where to find mailman 2.1.12+ rpm?

Sending an email to a list outputs " Command output: Failure to
exec script. WANTED gid 67, GOT gid 65533."

which rather looks like a Postfix issue. I tried default_privs = mailman in main.cf, but no effect (probably the Python problem anyway).

I’ve read many pages on the Web and am still stuck… Help!:slight_smile:

#2

Hi there,

sorry if i cant provide much help, but the error seems to be in mailman as far as i read the error

admin(17420): raise Errors.MMSubscribeNeedsConfirmation
admin(17420): TypeError: exceptions must be old-style classes or derived from BaseException, not str

seems like mailman expectet a different type for the raise.
Maybe you should fill in an mailman bug report.

Just an idea :slight_smile:

#3

Yep, my version of mailman uses deprecated Python exceptions. Since I find no rpm, I’m affraid I’ll have to install an upper version by hand.

#4

Yes, seems so,
but after i read some of the notes on the mailman homepage, i think it wont be that heavy

#5

I can’t manage to install ;configure does not work.

#6

how does it fail?

#7

Sorry, I shouldn’t have posted in a hurry. Actually, it is not installed/available!

#8

Well,
i think you should provide a bit more information on what you actually do, or try to do.

If the configure fails the software is if course not installed.
If you tell me what the last messages were, i maybe can help.

#9

Configure is just not recognized as a valid command.

#10

If you trying to confuse me, it works :slight_smile:

so you downloaded Downloading Mailman than you switched to the directory there is after you unpacked the source. Then you tried to read the README or INSTALL? And if nothing at all you just tried an ./configure or an make?

#11

Yup (sorry for being confuse, I’m trying to work and look out at guys installing a new kitchen at the same time – bad idea).

I followed http://www.list.org/mailman-install/index.html until:

./configure

-bash: ./configure: No such file or directory

#12

OK, here I am back from holydays. I got an older version of mailman (2.1.13) with a proper configure script, which runs apparently fine.

Then I run make and make install (which output some errors) and mailman does not work (sounds logical).

Looks like a file’s missing on my system. :frowning:

#13

Ok, got the file from a neighboring directory. Almost seems to work fine (web interface: OK; my test email to a list has not showed up yet).