Mailman 3 November 2002 - Mailman-Users

Switch to quarterly reminders
by Gary Pupurs Nov. 8, 2002

Nov. 8, 2002

Please consider switching the base code of mailman to send quarterly instead of monthly 'reminders' to subscribers. As an avid subscriber of lists, it's annoying to get these messages every month, when every 3 or 6 months would suffice. Thanks! -g

3 3

Where do they keep the site wide templates?
by Chris Lawson Nov. 8, 2002

Nov. 8, 2002

...as in the ones used to create the page you see when you visit /mailman/listinfo/ ? I'm sorry if this is in the FAQ, but I honestly couldn't find it anywhere. Nor could I find the site-wide list info template. cmkl -- Chris Lawson, Jungle Internet http://www.jungle.ca

1 0

sendmail failing causing Mailman to go haywire
by Richard F. Man Nov. 8, 2002

Nov. 8, 2002

OK, I found out that my problem is not a mail loop, but that when sending out digests, somehow sendmail fails, and cause Mailman to try to resend the digest forever. Mailman is 2.0.9, does anyone know how to get the version of sendmail? Here's the excerpt from Mailman's error log: Nov 08 13:20:05 2002 (21869) Traceback (most recent call last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Sendmail.py", line 86, in process fp.write(msgtext) IOError: [Errno 32] Broken pipe I did a mail -s "test" $(/home/mailman/bin/list_members -d <list>) to send out a test msg to the digest members and that seem to be fine. One potential problem is that for NORMAL posting, one of the list members' company recently mucked up their mail delivery and one would get this back when posting to the list: *************************** From: TZO Mailer [mailto:mailer@tzo.com] Sent: 8. november 2002 15:44 To: <XXXX> Subject: Delivery failure to "'icc-avr(a)imagecraft.com'" <icc-avr(a)imagecraft.com> Delivery was attempted, but failed because: 554 <icc-avr(a)imagecraft.com>: Recipient address rejected: Relay access denied -=-=-=-=-=-=-=-=- Original Message: -=-=-=-=-=-=-=-=- TZForward: <XXXX> Received: from 205.219.84.13 by saf.tzo.com id 2002110806440965687 for <XXXX> Fri, 08 Nov 2002 11:44:09 GMT Received: from dragonsgate.imagecraft.com (209-128-106-110.BAYAREA.NET [209.128.106.110]) by postman.bayarea.net (8.9.3/8.9.3) with ESMTP id DAA52937; Fri, 8 Nov 2002 03:39:55 -0800 (PST) (envelope-from icc-avr-admin(a)imagecraft.com) Received: (from mailman@localhost) by dragonsgate.imagecraft.com (8.11.6/8.11.6/SuSE Linux 0.5) id gA8Ce3f15336; Fri, 8 Nov 2002 04:40:03 -0800 ****** I contacted them and they say they will look into the problem. However, can a normal user's email problem caused problems for digest mailing? Thanks for any advice you may have // richard <http://www.imagecraft.com> <http://www.dragonsgate.net/mailman/listinfo> On-line orders, support, and listservers available on web site. [ For technical support on ImageCraft products, please include all previous replies in your msgs. ]

1 0

installation problem
by Clay Stuckey Nov. 8, 2002

Nov. 8, 2002

I have RedHat 7.3 with all current updates. When I follow the instructions to set up mail man and restart apache, I get the following error: Starting httpd: Syntax error on line 5 of /etc/httpd/conf/httpd-mailman.conf: Invalid command 'ScriptAlias', perhaps mis-spelled or defined by a module not included in the server configuration I have the line "Include conf/httpd-mailman.conp" in my httpd.conf. I stuck it at the top of the script. Any ideas? Sincerely, Clay Stuckey - RHCE, CCNA, MCSE Charleston Housing Authority - MIS Manager

1 0

mailman log cleanup
by Matthews, Michael J (Mike), ALCNS Nov. 8, 2002

Nov. 8, 2002

admin questions A list was mis-configured so that hundreds of messages were held for approval. I removed the messages on disk but admin web page still sees them with no message found. How do I get rid of these references? thanks -- * Michael Matthews * AT&T Labs * mjmatthews(a)att.com

1 0

Re: Admin password problem
by Mark Leisher Nov. 8, 2002

Nov. 8, 2002

Mark> Setup: Solaris 2.8 Python 2.2.2 Mailman 2.0.13 Mozilla 1.1 (Enable Mark> all cookies) Mark> List and site passwords always fail authentication. Any relevant Mark> clues? Answering my own question: Mailman.Crypt.crypt() is returning a different result every time for the same password when Python 2.2.2 is used. Python 1.5.2 works. Haven't tried any other version. ----------------------------------------------------------------------------- Mark Leisher Computing Research Lab But blogging's political bias New Mexico State University is not so much left/right as Box 30001, Dept. 3CRL anti-idiot. Las Cruces, NM 88003 -- Glenn Reynolds

1 0

Upgrading to Version 2.1
by Brian C. Kacmarsky Nov. 8, 2002

Nov. 8, 2002

Hello, I am interested in upgrading our Mailman Software to Version 2.1 and have a few questions on how to do this. Our site (Roger Williams University) currently uses Version 2.0.3. The main reason for our decision to upgrade to Version 2.1 is due to the fact that the footers do not show up on some of the list messages. After review your FAQ I saw the solution was to upgrade to 2.1. I have read the documentation both online and in the tar file regarding updating the version and am a bit confused. Do you have a site or document you can send me that will list the correct steps that I should take in upgrading to version 2.1. Thanks. Brian

1 0

Re: [Mailman-Users] Question about sync_members
by Richard Barrett Nov. 8, 2002

Nov. 8, 2002

Forget what I originally said. below. That AddMember function is not called during execution of sync_members. Indeed, it appears that there is no check in sync_members (or indeed add_members) to prevent a list being subscribed to itself. This is so in MM 2.0.13. and also in 2.1b4. Getting back to your problem. Utils.ValidateEmail is first called at line 194 of sync_members for each email address in the input file. If an incoming mail address is invalid the script should print something like this and exit: Invalid: <faulty email address> You must fix the preceding invalid addresses first. You do not say that you are getting this output which identifies the faulty email address. Utils.ValidateEmail checks each email address as follows: 1. it has a userid and domain part separated by an @ char 2. the userid is not empty 3. the domain has at least one period character in it If you are not getting that error message output from sync_members, the strange thing is that the Errors.MMBadEmailError would then seem to originate when the Utils.ValidateEmail is called a second time in respect of the same datum. This occurs when Utils.ValidateEmail is again called at line 1096 of Mailman/MailList.py as the new members are actually added to the list. The traceback you supplied seems to indicate this is when the error is occurring. If this exception is being reported during this second round of processing it is not immediately obvious to me why this is happening. If your or anybody else can offer a solution I'd like to know what it is. Must be something obvious but I cannot spot it right now. At 19:53 07/11/2002, Jim Tomasello wrote: >Good afternoon. I'm running a new setup of mailman, the version that comes >with Red Hat 8.0. My problem isn't with Mailman per se, but with the >sync_members script that comes with it. > Its better to specify the actual Mailman version number but lets assume that it is 2.0.x >I am trying to load members from a text file. The file has one email >address per line and contains 2,086 emails. When I run the script using >the following command while logged in as root, "./sync_members -n -w=no >-a=no -f members realtor-members", doing the dry run, everything seems >fine. When I remove the -n parameter to run it live, it gets through 2,043 >emails and then generates the following error: > >Traceback (most recent call last): > File "./sync_members", line 257, in ? > main() > File "./sync_members", line 240, in main > welcome, notifyadmin) > File "/var/mailman/Mailman/MailList.py", line 1054, in ApprovedAddMember > raise e, v >Mailman.Errors.MMBadEmailError >Now I've looked at the addresses around the one it appears to be dying on, >and they look fine. I have no idea what this is telling me the problem is. >I've looked in the /var/logs/mailman dir to see if I can find any evidence >of what's going on, to no avail. Anyone out there have any idea where I >should start looking to figure this one out? Any help would be appreciated. > Looking at the MM 2.0.13 code. The only circumstance that I can see where Errors.MMBadEmailError is raised without sync_members printing something like this and exiting: Invalid : <faulty email address>' You must fix the preceding invalid addresses first. is if the maillist's own email address is on the list., i.e. you are trying to subscribe the list to itself.. Could that be the case?? This error is generated at line 970 of $prefix/Mailman/MailList.py in function AddMember.

1 0

Incorrect info in headers
by Eric Trager Nov. 8, 2002

Nov. 8, 2002

Hi all, My site runs a handful of lists using 2.0.13, each administrated by a different individual. Some of the lists are configured to send the monthly password reminders. The problem we are having is that the monthly messages for the different lists and users all end up with the same Return-Path, Sender, and Errors-to headers, which contain the address of the admin for one of the lists (it so happens it's the first list that was created at this site). What this boils down to is once a month, bounce errors for invalid addresses for lists 3, 4, and 7, the ones that send out the monthly reminders, all go to the admin for list 1. An example of this is below. It's a reminder for a test list I set up for myself. --------- Return-Path: <xplor-nih-admin(a)nmr.cit.nih.gov> . . Date: Tue, 05 Nov 2002 12:39:29 -0500 Message-ID: <20021105173929.19467.43040.Mailman(a)argo.cit.nih.gov> Subject: argo.cit.nih.gov mailing list memberships reminder From: mailman-owner(a)cbel.cit.nih.gov To: trager(a)cbel.cit.nih.gov . . Sender: xplor-nih-admin(a)nmr.cit.nih.gov Errors-To: xplor-nih-admin(a)nmr.cit.nih.gov X-BeenThere: xplor-nih(a)nmr.cit.nih.gov X-Mailman-Version: 2.0.13 Precedence: bulk This is a reminder, sent out once a month, about your argo.cit.nih.gov [etc.] ----------- In this case, I'm on list 7, not the xplor-nih-admin list. If my account goes away, the xplor-nih admin will get the bounce error. I've pored through the docs and list archives to figure out how to change this so the mailman-owner address or each list's admin receives the errors, OR to change which list's admin is chosen to receive the errors... but to no avail. I have not been able to figure out how this return address is chosen and used in the mailpasswds process. Any ideas on how to sort this out? TIA. - - - - - Eric Trager

2 1

Changing the digest subject line
by Mark McRitchie Nov. 8, 2002

Nov. 8, 2002

Hi there, I've googled and looked every where else I can think of, and it seems like something simple. How do I change the subject line of digest mailings? I'm using Mailman 2.0.11 on Debian Woody. (Feel free to slap me if I've missed something blatantly obvious) Regards, Mark. Salamis Group of Companies - WWW.SALAMISGROUP.COM This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) be advised that any form of distribution, copying or use of this communication or the information it contains is strictly prohibited and may be unlawful. We apologise if you have received this communication in error. Please return it to the sender immediately, delete this communication from your computer and destroy any copies of it. Any views/opinions expressed in this email are that of the author and may not reflect the views of Salamis (M&I)Ltd.

1 0