[Mailman-Users] Candidate Mailman 2.0.13 patch

As some of you have noticed, Mailman 2.0.12 has some compatibility problems with Python 1.5.2. In order to correct this, and a few other minor problems, I want to soon release a version 2.0.13. This time, however I'd like to enlist your help. ;) I have uploaded a candidate patch for 2.0.12 ->

Re: [Mailman-Users] Error during 1st install

> > <<< Failure to exec script. WANTED gid 12, GOT gid 501. (Reconfigure to take > 501?) > So, add apache to group 12 or whatever group you need to do. Or recompile, gee!! -- TJW :Head tech, designer, bum:P Mud :http://dreamless.wolfstream.net telnet :telnet://dreamless.wolfstrea

[Mailman-Users] HELP CONFIGURE

When i have unpack the tar.gz file into /home/mailman/  i run configure (./configure) but its Doesn't work,. Please Help What happen :   [mailman@develop mailman-2.0.12]$ ./configureloading cache ./config.cachechecking for --with-python... nochecking for python... /usr/bin/pythonchecking Pyt

RE: [Mailman-Users] Mailman don't send subscription confirmation email

Ive been having trouble with that also, among other things. when you create a list via $prefix/bin/newlist it runs you thru a little questionaire. what is the list's name, who is the admin? it then tells you to add this the your /etc/aliases file. ###-- Mailman List Aliases ## te

[Mailman-Users] mailman memory error

Folks, I have set up a new Mailman server with the HTDig patches. It all works fine on a small list. I can send email and I see it in the archives etc. When I brought over a list from my other Mailman system and when I run /bin/arch I get the following error. 2001-November *** malloc[311]: err

[Mailman-Users] Mailman don't send subscription confirmation email

Hi... I been install Mailman 2.0.11-1 downloaded from RedHat rpm's database, on a RedHat 7.1 server with sendmail and iPop3 (Imap), I made test sending and reciving mails trought shell's users and it works, but when I tried to subscribe to Mailman list, the server doesn't send me any mail for con

Re: [Mailman-Users] Error during 1st install

Thanks all I needed to do was set up reverse lookup and it works now but now when sending mail to my news group I get this back from the mail server: <<< Failure to exec script. WANTED gid 12, GOT gid 501. (Reconfigure to take 501?) I know the FAQ says to recompile with the --cgi-gid and som

Re: [Mailman-Users] Changing how footer is written when non text messages are sent to list

On Tue, 23 Jul 2002 12:41:51 -0400 Shannon M Anderson <[EMAIL PROTECTED]> wrote: > First off Thanks Bob Weissman [[EMAIL PROTECTED]] for the answer to > my first question. (Why footer is not showing up in outbound mail). > Now we use Mailman to send emails out from our Cold fusion servers for >

[Mailman-Users] strip out and archive attachments?

Hey folks, I've got a problem that I can't quite seem to work out. On the lists that we're hosting (RH 7.2 w/Postfix as the MTA), we've been seeing an increasing number of attachments, and we'd like to start stripping all attachments -- especially the ones that are most likely virii :) But -- an

Re: [Mailman-Users] Re: [Mailman-Developers] Mailman 2.0.12 error

I believe I was the first to report the problem last week, and I felt a certain relief as other reported it since - I had already been through the fire. Alas, it bit me again yesterday and one client was fuming this morning because a time-sensitive message didn't get delivered. I started pulling

[Mailman-Users] Re: [Mailman-Developers] Mailman 2.0.12 error

> "KW" == Kory Wheatley <[EMAIL PROTECTED]> writes: KW> This is very critical I get this fixed, I'm running 150 KW> production mailing lists, here's my problem. Apply the following patch. Mailman 2.0.12 had compatibility issues with Python 1.5.2. Later today I will post a candidat

[Mailman-Users] Mailman 2.0.12 error

This is very critical I get this fixed, I'm running 150 production mailing lists, here's my problem. I keep receiving this below error when messages are sent to my lists. I'm running Red Hat 7.2 mailman 2.0.12. Does anyone know the solution? If I take them out of the qfiles directory and the

[Mailman-Users] Re: Mailman-Users digest, Vol 1 #2125 - 9 msgs

  [EMAIL PROTECTED] wrote: Send Mailman-Users mailing list submissions to[EMAIL PROTECTED]To subscribe or unsubscribe via the World Wide Web, visithttp://mail.python.org/mailman/listinfo/mailman-usersor, via email, send a message with subject or body 'help' to[EMAIL PROTECTED]You can reach the p

[Mailman-Users] Mailman modifications

Mailman users: I would like to use Mailman for our lists, but to do so, I will require one modification. I am wondering 1) if the change will be difficult to make, and 2) if anyone else has done it. What we need is the addition of first and last name records for all of our members. We already

[Mailman-Users] Changing how footer is written when non text messages are sent to list

First off Thanks Bob Weissman [[EMAIL PROTECTED]] for the answer to my first question. (Why footer is not showing up in outbound mail).   Now we use Mailman to send emails out from our Cold fusion servers for different clients that want a automated list system and it works very well for this

[Mailman-Users] opening holes by changing permissions?

I was having problems adding a list in Mailman 2.1beta via the web interface, it was giving me an error regarding permissions to the mailman/data/aliases.db file. This is the error I got: ... File "/var/mailman/Mailman/MTA/Postfix.py", line 46, in _update_maps raise RuntimeError, msg % (acmd, st

[Mailman-Users] Warning: Unrecognized character set: utf-8

The other day I started getting this error message emailed to me from MailMan after a few people posted messages to the system:   Warning: Unrecognized character set: utf-8   The Subject on the email is: Cron /usr/bin/python -S /home/mailman/cron/qrunner   Anyone kno

[Mailman-Users] Debug message - how to switch off

Hello all, we switched to Mailman 2.1b2 recently because we need multi language support. Now every mail message to the listname-request address seems to issue a sort of debug message coming from the listname-bounce address in addition to listname-request's replies, like this: The resu