Mailman 3 March 2002 - Mailman-Developers

Restrictions on listnames?
by Ellen Spertus 19 Mar '02

19 Mar '02

Are there any restrictions on list names? The only implicit restriction I can see in the source is that they can't contain "@" (for good reason). For my modifications, I'd like to be able to assume a specific character (I don't care which) is a delimiter, not part of a list name. Suggestions? Ellen Spertus

2 1

rejecting messages depending on To:/Cc: content
by Marc MERLIN 18 Mar '02

18 Mar '02

Just to make sure I got this right: If I go to (let's say): http://lists.svlug.org/lists/admin/speakers/privacy/spam I can set values in acceptable_aliases In http://lists.svlug.org/lists/admin/speakers/privacy/sender I can get mailman to auto-reject or discard messages depending on the sender So is there a way to apply the auto-reject or auto-discard on values in the privacy/spam page? (not to worry, if the ansewr is "no", this isn't an official feature request, we gotta stop somewhere :-D) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

1 0

Re: [Mailman-Developers] Modifications to msg
by Dan Mick 18 Mar '02

18 Mar '02

> There is rather tortured logic in the old (and maybe new) documents > justifying the ability to have multiple addresses in the single From: > header. Personally, I've never sent or received one of those, even as a > test message (I'm sure to get one now, having said that ;-)). Geek wedding announcements? :) :) > And remember, too, that some things in RFCs are the way they are because > that's the way they are (and are hard to explain any other way). surely true. And the point about "there sorta must be multiple Received:s" is of course well-taken.

1 0

Re: [Mailman-Developers] Modifications to msg
by Dan Mick 18 Mar '02

18 Mar '02

> RFC 2822 rules on the number of specific headers a message can have. > E.g. it can have many Received: headers, but only one Reply-To: header > (although the latter allows for multiple addresses... go figure). Ease of parsing. No one but humans typically looks at Received:, but dumb MUAs need to use Reply-To:, so complicated tricks for accumulating a list are limited there. (at least that's what I'd guess at for a rationale.)

2 1

minor config issue: web_page_url is stored in list config
by Harald Koch 18 Mar '02

18 Mar '02

I installed Mailman 2.1b1 yesterday. I have an active 2.0.8 config, so I installed 2.1b1 in a different directory, and moved a couple of lists over from one install to the other. Everything worked swimmingly, except for one thing: the URLs on web pages were all pointing back to the old mailman installation. Some poking around led me to the following: The value for 'web_page_url' is stored in each individual list config file (config.db/config.pck), instead of always being read from mm_cfg.py. However, that variable is not exported by "config_list -o", so it took me a while to figure it out. The workaround for me was to add "web_page_url = 'http://www.cfrq.net/mm/' to my list config and ran "config_list -i"; thankfully that worked. Ideally, I would expect that this variable always be built from mm_cfg; it's a property of the mailman install, not a property of an individual list. Comments? -- Harald Koch <chk(a)pobox.com> "It takes a child to raze a village." -Michael T. Fry

3 6

a success! from 2.0.8 to 2.1b1 :)
by Mentor Cana 18 Mar '02

18 Mar '02

I would like to report a succesful upgrade from 2.0.8 to 2.1b1. :) Besides for some small things, the upgrade went fine; per list options and per subscriber options migrated all fine. Obviously, I had to create the default site list, regenerate the aliases file, make sure that qfile/ was empty, go through the mm_cfg.py (which I still have to do more work for fine-tuning), did a backup on few files (in addition to tar-in the entire installation of mailman2.0.8; which does not seem I will need :)), an few other maintenance things. Here are few 'problems': 1. logs/error file logged bunch of errors [see bellow] about corrupt list config files. nevertheless, the lists got upgraded fine. 2. Whatever held messages were in data/ migrated fine. I could approve and reject files on various lists. However, one of the lists (my test-l list) reports an error/bug when clicking on "Tend to pending moderator requests". See bellow for the error. So far I have seen this error on one list. 3. The list archives didn't show until I sent a message to the list, or until I ran the bin/arch <list-name>. I consider these few things not to be substantial problems. :) To MM developers and the support team: EXCELLENT JOB! :) -- Mentor ------------------ Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck.last Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck.last Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck.last Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck Mar 18 18:47:16 2002 (26826) test-l config file was corrupt, trying fallback: /opt/home/mailman/lists/test-l/config.pck.last Mar 18 18:47:17 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck Mar 18 18:47:17 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck.last Mar 18 18:47:17 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck Mar 18 18:47:17 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck.last Mar 18 18:47:18 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck Mar 18 18:47:18 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck.last Mar 18 18:47:18 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck Mar 18 18:47:18 2002 (26826) listowners-l config file was corrupt, trying fallback: /opt/home/mailman/lists/listowners-l/config.pck.last ------------------ ------------------ Mar 18 19:03:10 2002 admin(27321): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(27321): [----- Mailman Version: 2.1b1 -----] admin(27321): [----- Traceback ------] admin(27321): Traceback (most recent call last): admin(27321): File "/opt/home/mailman/scripts/driver", line 82, in run_main admin(27321): main() admin(27321): File "/opt/home/mailman/Mailman/Cgi/admindb.py", line 219, in main admin(27321): show_pending_subs(mlist, form) admin(27321): File "/opt/home/mailman/Mailman/Cgi/admindb.py", line 274, in show_pending_subs admin(27321): time, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) admin(27321): ValueError: unpack tuple of wrong size ------------------

1 0

Modifications to msg
by Ellen Spertus 18 Mar '02

18 Mar '02

I've been making some modifications to Mailman to support dynamic sublists (http://javamlm.mills.edu). I'm still rather new with Python and have a question about modifying fields (dictionary elements) of the msg data structure. Specifically, I added the following code to change the message's "To" field at the end of CookHeaders.py: 1 if msgdata.get('dlist'): 2 threadID = msgdata['thread_id'] 3 syslog('info', "threadID = %d", threadID) 4 to_line = '%s-%d@%s' % (mlist.real_name.lower(), threadID, mlist.host_name) 5 syslog('info', "to_line = %s", to_line) 6 del msg['To'] 7 msg['To'] = to_line 8 syslog('info', "Set msg['To'] to '%s'", msg['To']) This correctly changes the "To" field of the message from etest-new@hostname to etest-<threadID>@hostname, as shown by the log: Mar 18 13:29:55 2002 (4600) threadID = 19 Mar 18 13:29:55 2002 (4600) to_line = etest-19(a)javamlm.mills.edu Mar 18 13:29:55 2002 (4600) Set msg['To'] to 'etest-19(a)javamlm.mills.edu' Similarly, the resulting email message that is sent has the new 'To' field. The problem is I don't see why line 6 above is necessary. When I comment it out, however, I get the incongruous logfile entry: Mar 18 13:36:04 2002 (4640) threadID = 20 Mar 18 13:36:04 2002 (4640) to_line = etest-20(a)javamlm.mills.edu Mar 18 13:36:04 2002 (4640) Set msg['To'] to 'etest-new(a)javamlm.mills.edu' as though line 7 had never been executed. The final email message contains two "To" headers, one with "etest-new" and one with "etest-<threadID>". It's not clear to me why the original value is preserved instead of overwritten. Could someone let me know what I'm missing about dictionaries or the email class? Thank you. Ellen Spertus

2 4

Problem with mailman 2.0.8 upgrade to Mailman 2.1b1
by Kory Wheatley 18 Mar '02

18 Mar '02

Mailman 2.08 was working fine and I decided to upgrade to mailman 2.1b1 and the web interface is fine and it sends out the welcome messages fine. I regenerated the alias file to the new format. I changed the wrapper to mailman in the /etc/smrsh directory. The problem is when I send a message to the list I receive the following error. The original message was received at Mon, 18 Mar 2002 11:41:56 -0500 from ux9-205.isu.edu [134.50.205.114] ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/mailman post korybest" (reason: 2) (expanded from: <korybest(a)kwlinux.isu.edu>) ----- Transcript of session follows ----- Failure to exec script. WANTED gid 501, GOT gid 12. (Reconfigure to take 12?) 554 5.3.0 unknown mailer error 2 Reporting-MTA: dns; kwlinux.isu.edu Received-From-MTA: DNS; ux9-205.isu.edu Arrival-Date: Mon, 18 Mar 2002 11:41:56 -0500 Final-Recipient: RFC822; korybest(a)kwlinux.isu.edu X-Actual-Recipient: X-Unix; |/home/mailman/mail/mailman post korybest Action: failed Status: 5.0.0 Diagnostic-Code: X-Unix; 2 Last-Attempt-Date: Mon, 18 Mar 2002 11:41:56 -0500 I have always used the 501 GID has the group id, I did not specify a different GID in the upgrade when I did the configure, (all I specified was ./configure --prefix=/home/mailman).. How can I reconfigure without losing my lists or starting over. -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

2 1

erroneous format specification: sync_members
by mss＠mawhrin.net 18 Mar '02

18 Mar '02

A small patch to fix it. -- Misha Index: sync_members =================================================================== RCS file: /cvsroot/mailman/mailman/bin/sync_members,v retrieving revision 2.6 diff -u -b -r2.6 sync_members --- sync_members 23 Feb 2002 06:34:14 -0000 2.6 +++ sync_members 18 Mar 2002 23:40:28 -0000 @@ -182,7 +182,7 @@ addr = filemembers[i].strip() if addr == '' or addr[:1] == '#': del filemembers[i] - print _('Ignore : %30(addr)s') + print _('Ignore : %(addr)30s') # first filter out any invalid addresses filemembers = email.Utils.getaddresses(filemembers)

2 1

Re: [Mailman-Developers] Modifications to msg
by Ellen Spertus 18 Mar '02

18 Mar '02

At 02:05 PM 3/18/2002 -0800, Dan Mick wrote: >Question one: which version of mailman? The "message" class >changes drastically from 2.0.x to 2.1.x. Sorry to leave that out. I'm using Mailman 2.1a3 and Python 2.2c1. Ellen

1 0