Mailman 3 March 2002 - Mailman-Developers

2.0.8 - qrunner on solaris
by Rob Ellis 29 Mar '02

29 Mar '02

I'm not sure if this is appropriate here, so apologies in advance if it isn't... We're using Mailman 2.0.8 on a sun ultra with solaris 8, and we were running into two problems with qrunner... The first was a race condition where this code in qrunner - # If the .db file has no corresponding .msg file, we might as well - # remove the .db file, since there's little we can do about it. - if not os.path.exists(root+'.msg'): - syslog('qrunner', 'Unlinking orphaned .db file: %s.db' % root) - os.unlink(root+'.db') was unlinking .db files before their corresponding .msg files were created. We just removed those lines and it seems to be ok -- no orphaned .db files and no more orphaned .msg files. The second problem was that qrunner was crashing on some kinds of bounce messages (?), causing messages to pile up in the queue occasionally. It was generating errors like this: > Traceback (most recent call last): > File "/usr/local/mailman/cron/qrunner", line 277, in ? > kids = main(lock) > File "/usr/local/mailman/cron/qrunner", line 247, in main > keepqueued = dispose_message(mlist, msg, msgdata) > File "/usr/local/mailman/cron/qrunner", line 121, in dispose_message > if BouncerAPI.ScanMessages(mlist, mimemsg): > File "/usr/local/mailman/Mailman/Bouncers/BouncerAPI.py", line 59, in ScanMessages > addrs = func(msg) > File "/usr/local/mailman/Mailman/Bouncers/DSN.py", line 46, in process > if string.lower(msg.gettype()) <> 'multipart/report' or \ > File "/usr/local/lib/python2.1/string.py", line 51, in lower > return s.lower() > AttributeError : 'None' object has no attribute 'lower' The patch below seems to fix the problem (?)... we're now seeing some errors like this: bounce loop detected from: mailer-daemon(a)web.net but at least qrunner keeps running and the queue is getting cleared. - Rob -- Rob Ellis <rob(a)web.ca> System Administrator, Web Networks * --- Mailman/Bouncers/DSN.py 14 Nov 2001 15:57:09 -0000 1.1.1.2 +++ Mailman/Bouncers/DSN.py 7 Mar 2002 16:29:02 -0000 1.2 @@ -43,7 +43,7 @@ def process(msg): - ctype = msg.gettype() + ctype = msg.gettype() or '' param = msg.getparam('report-type') or '' if string.lower(ctype) <> 'multipart/report' or \ string.lower(param) <> 'delivery-status':

2 1

config_list
by Ron Jarrell 29 Mar '02

29 Mar '02

Uh, I think the cutting and pasting was a little too literal here... A segment from a dump of one of my lists... ## Privacy options # # When a message is posted to the list, a series of moderation steps are # take to decide whether the a moderator must first approve the message # or not. This section contains the controls for moderation of both # member and non-member postings. # # Member postings are held for moderation if their moderation # flag is turned on. You can control whether member postings are # moderated by default or not. # # Non-member postings can be automatically <a # href="?VARHELP=privacy/sender/accept_these_nonmembers" >accepted</a>, # <a href="?VARHELP=privacy/sender/hold_these_nonmembers">held for # moderation</a>, <a # href="?VARHELP=privacy/sender/reject_these_nonmembers" >rejected</a> # (bounced), or <a # href="?VARHELP=privacy/sender/discard_these_nonmembers" # >discarded</a>, either individually or as a group. Any posting from a # non-member who is not explicitly accepted, rejected, or discarded, # will have their posting filtered by the <a # href="?VARHELP=privacy/sender/generic_nonmember_action">general # non-member rules</a>. # # In the text boxes below, add one address per line; start the line # with a ^ character to designate a <a href= # "http://www.python.org/doc/current/lib/module-re.html" >Python regular # expression</a>. When entering backslashes, do so as if you were using # Python raw strings (i.e. you generally just use a single backslash). # # Note that non-regexp matches are always done first. # Each list member has a moderation flag which says whether messages # from the list member can be posted directly to the list, or must first # be approved by the list moderator. When the moderation flag is turned # on, list member postings must be approved first. You, the list # administrator can decide whether a specific individual's postings will # be moderated or not. # # When a new member is subscribed, their initial moderation flag takes # its value from this option. Turn this option off to accept member # postings by default. Turn this option on to, by default, moderate # member postings first. You can always manually set an individual # member's moderation bit by using the membership management screens. # # legal values are: # 0 = "No" # 1 = "Yes" default_member_moderation = 1 BTW, am I just missing it, or is config_list the only place you can change default_member_moderation? I didn't see a likely checkbox in the cgi screens...

2 2

mm-handler
by Ron Jarrell 29 Mar '02

29 Mar '02

Barry - dgc's mm-handler isn't prepared to handle 2.1; it's using the old structure for aliases. Not surprisingly. However, since it's referenced in the docs as a sendmail solution, it'll probably surprise some people who try it, when things go majorly foobar (even the wrapper script name is wrong.) I've gotten it working in my installation. At some point I'll contribute again my mc file that makes installing it a more "sendmail like" operation then the way dgc does it. I've got it on my production and test servers right now, and it seems to be working cleanly. Here's a diff against cvs. I had to change a couple of paths above and beyond the minimum required to get it 2.1 clean, simply to get it to work on my machine, but otherwise this seems to do it. David might have his own way of fixing it, but I'm happy as is now :-). Index: mm-handler =================================================================== RCS file: /cvsroot/mailman/mailman/contrib/mm-handler,v retrieving revision 1.1 diff -r1.1 mm-handler 1c1 < #!/opt/bin/perl --- > #!/usr/local/bin/perl 5d4 < 7,11c6,17 < ## testlist: "|/opt/pkgs/mailman/mail/wrapper post testlist" < ## testlist-admin: "|/opt/pkgs/mailman/mail/wrapper mailowner testlist" < ## testlist-request: "|/opt/pkgs/mailman/mail/wrapper mailcmd testlist" < ## owner-testlist: testlist-admin < ## testlist-owner: testlist-admin --- > ## > ##testlist: "|/home/mailman/mail/mailman post testlist" > ##testlist-admin: "|/home/mailman/mail/mailman admin testlist" > ##testlist-bounces: "|/home/mailman/mail/mailman bounces testlist" > ##testlist-confirm: "|/home/mailman/mail/mailman confirm testlist" > ##testlist-join: "|/home/mailman/mail/mailman join testlist" > ##testlist-leave: "|/home/mailman/mail/mailman leave testlist" > ##testlist-owner: "|/home/mailman/mail/mailman owner testlist" > ##testlist-request: "|/home/mailman/mail/mailman request testlist" > ##testlist-subscribe: "|/home/mailman/mail/mailman subscribe testlist" > ##testlist-unsubscribe: "|/home/mailman/mail/mailman unsubscribe testlist" > ##owner-testlist: testlist-owner 14,15c20,21 < $MMWRAPPER = "/opt/pkgs/mailman/mail/wrapper"; < $MMLISTDIR = "/var/mailman/lists"; --- > $MMWRAPPER = "/home/mailman/mail/mailman"; > $MMLISTDIR = "/home/mailman/lists"; 122a129,130 > my @validfields = qw(admin bounces confirm join leave owner request > subscribe unsubscribe); 124,132c132,139 < if ($addr =~ /(.*)-admin$/ < || $addr =~ /(.*)-owner$/ < || $addr =~ /^owner-(.*)$/) { < $list = $1; < $cmd = "mailowner"; < } elsif ($addr =~ /(.*)-request$/) { < $list = $1; < $cmd = "mailcmd"; < } else { --- > $addr =~ /(.*)-(.*)$/; > $list = $1; > $cmd = $2; > if ($list eq "owner") { > $list = $cmd; > $cmd = "owner"; > } > if (!grep /^$cmd$/, @validfields) { 190c197 < if (! -f "$MMLISTDIR/$list/config.db") { --- > if (! -f "$MMLISTDIR/$list/config.pck") { 192c199 < if (! -f "$MMLISTDIR/$list/config.db") { --- > if (! -f "$MMLISTDIR/$list/config.pck") {

1 1

cgi create error
by Ron Jarrell 29 Mar '02

29 Mar '02

Didn't "ko" need to get added to the LC_DESCRIPTIONS dictionary in Defaults? Traceback (most recent call last): File "/home/mailman/scripts/driver", line 82, in run_main main() File "/home/mailman/Mailman/Cgi/create.py", line 60, in main request_creation(doc) File "/home/mailman/Mailman/Cgi/create.py", line 375, in request_creation [_(Utils.GetLanguageDescr(L)) for L in langs], File "/home/mailman/Mailman/Utils.py", line 647, in GetLanguageDescr return mm_cfg.LC_DESCRIPTIONS[lang][0] KeyError: ko

1 0

traceback (still due to the BounceRunner)
by Fil 29 Mar '02

29 Mar '02

Hello, I've sent yesterday one of these "big bounce list" message, and the BounceRunner is still processing bounces, 100% CPU for hours... Not a problem if the new locking scheme worked, but, unfortunately, it doesn't when the qfiles/bounces/ directory is full : the BounceRunner doesn't know how to pause from time to time. >From what I see it needs about 5-6 seconds (on a 50000 subscribers' list) to process and register one bounce. So it really shouldn't process more than 4 in a row (ie in a minute) if we want the lockfile to be released before 30 secs. However that would mean processing 4 bounces per minute. If you have 50 000 bounces, that's 12 500 minutes... not good. I don't know what to suggest, except maybe to make a BounceRunner preprocessor that doesn't read or write the list files, but just extracts the bounce information and gets rid fast of the bounce files. Then for the "real" BounceRunner to process the bounce information already computed would be very fast. Traceback (most recent call last): File "/var/local/mailman/Mailman/MailCommandHandler.py", line 273, in +ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/var/local/mailman/Mailman/MailCommandHandler.py", line 727, in +ProcessConfirmCmd results = self.ProcessConfirmation(args[0], msg) File "/var/local/mailman/Mailman/MailList.py", line 967, in +ProcessConfirmation data = Pending.confirm(cookie) File "/var/local/mailman/Mailman/Pending.py", line 94, in confirm lock.lock(timeout=30) File "/var/local/mailman/Mailman/LockFile.py", line 292, in lock raise TimeOutError TimeOutError -- Fil

1 0

2.0.6 error
by Bob Puff＠NLE 28 Mar '02

28 Mar '02

Hi Barry and gang, Just noticed this error from one of my 2.0.6 machines: Mar 10 15:22:24 2002 admin(20550): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(20550): [----- Mailman Version: 2.0.6 -----] admin(20550): [----- Traceback ------] admin(20550): Traceback (most recent call last): admin(20550): File "/home/csc/mailman/scripts/driver", line 96, in run_main admin(20550): main() admin(20550): File "../Mailman/Cgi/private.py", line 160, in main admin(20550): cookie='archive') admin(20550): File "/home/csc/mailman/Mailman/SecurityManager.py", line 66, in WebAuthenticate admin(20550): self.ConfirmUserPassword(user, password) admin(20550): File "/home/csc/mailman/Mailman/SecurityManager.py", line 141, i n ConfirmUserPassword admin(20550): if self.ValidAdminPassword(pw): admin(20550): File "/home/csc/mailman/Mailman/SecurityManager.py", line 45, in ValidAdminPassword admin(20550): if Utils.CheckSiteAdminPassword(pw): admin(20550): File "/home/csc/mailman/Mailman/Utils.py", line 413, in CheckSit eAdminPassword admin(20550): return Crypt.crypt(pw1, salt) == pw2 admin(20550): TypeError: argument 1 must be string without null bytes, not str Any ideas? Was this fixed in subsequent patches? Bob

1 0

"search for member with RE" box at top instead of bottom
by Dan Mick 28 Mar '02

28 Mar '02

I don't know why the first time I tried this, it seemed hard, but it's easy, and I like this a *lot* better: Index: Mailman/Cgi/admin.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Cgi/admin.py,v retrieving revision 2.66 diff -u -r2.66 admin.py --- Mailman/Cgi/admin.py 25 Mar 2002 23:48:12 -0000 2.66 +++ Mailman/Cgi/admin.py 25 Mar 2002 23:58:14 -0000 @@ -492,12 +492,8 @@ subcat = Utils.GetPathPieces()[-1] if subcat not in ('list', 'add', 'remove'): subcat = 'list' - # Add member category specific tables - form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) - form.AddItem(Center(submit_button('setmemberopts_btn'))) # In "list" subcategory, we can also search for members if subcat == 'list': - form.AddItem('<hr>\n') table = Table(width='100%') table.AddRow([Center(Header(2, _('Additional Member Tasks')))]) table.AddCellInfo(table.GetCurrentRowIndex(), 0, colspan=2, @@ -525,6 +521,10 @@ mlist.default_member_moderation), SubmitButton('allmodbit_btn', _('Set'))]) form.AddItem(table) + # Add member category specific tables + form.AddItem('<hr>\n') + form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) + form.AddItem(Center(submit_button('setmemberopts_btn'))) elif category == 'passwords': form.AddItem(Center(password_inputs(mlist))) form.AddItem(Center(submit_button()))

5 9

Re: [Mailman-Developers] "search for member with RE" box at top instead of bottom
by Dan Mick 28 Mar '02

28 Mar '02

> I think the help and big button are important. *We* don't need it, > but one thing mailman has so far been excellant for is handing > to only vaugely computer competant people to handle their own lists. > I have several lists run by folks for whom the height of technology is > using a web browser. They cope quite nicely. But I think we're getting > away from that, and they're coping less nicely. I've already gotten a > plaintive cry of "where did all my users go?" to the new membership > page, followed, after a short explanation of "Ok, explain again everything > after "regular expression"? Why do a put an asterisk after the period?" Novices have *no business* using anything but substring searches... so they don't have to know about . or *. But yes, a "search" button and a help link are good to have regardless.

1 0

lower : traceback
by Fil 28 Mar '02

28 Mar '02

While processing bounces, I suspect: ==> logs/error <== Mar 28 18:22:51 2002 (15837) Uncaught runner exception: 'None' object has no attribute 'lower' Mar 28 18:22:51 2002 (15837) Traceback (most recent call last): File "/var/local/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/var/local/mailman/Mailman/Queue/Runner.py", line 155, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/local/mailman/Mailman/Queue/BounceRunner.py", line 119, in _dispose mlist.registerBounce(addr, msg) File "/var/local/mailman/Mailman/Bouncer.py", line 96, in registerBounce if not self.isMember(member): File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 79, in isMember cpaddr, where = self.__get_cp_member(member) File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 62, in __get_cp_member lcmember = member.lower() AttributeError: 'None' object has no attribute 'lower' -- Fil

1 0

2.1b1: new_member_options and web GUI
by Harald Koch 27 Mar '02

27 Mar '02

I could not reset the "Filter out duplicate messages to list members (if possible)" flag in "new_member_options" from the web UI; the setting didn't take. I can change it with config_list, and that change is then reflected in the web GUI. By playing with the flags, I discovered that the problem is this; I cannot clear *all* of the flags. As long as one is set, the setting takes. Looks like a piece of code somewhere is treating "0" as a special case, but I haven't found it yet. -- Harald Koch <chk(a)pobox.com> "It takes a child to raze a village." -Michael T. Fry

3 2