Mailman 3 July 2003 - Mailman-Users

Re: [Mailman-Users] default action on administrative requests
by Hal Huntley 30 Jul '03

30 Jul '03

Richard and Heath, Thank you for pointing me in the right direction. You got me to the correct file and looking at the right places. However, it wasn't at this location in the admindb.py file, but further down. Working with this part of the code: > > radio = RadioButtonArray(id, (_('Defer'), > > _('Approve'), > > _('Reject'), > > _('Discard')), > > values=(mm_cfg.DEFER, > > mm_cfg.SUBSCRIBE, > > mm_cfg.REJECT, > > mm_cfg.DISCARD), > > checked=0).Format() and setting "checked=3", did not do what I wanted. The relevant lines of code appear to be around line 392. Here is where I modified things: == start code segment == # The encompassing sender table stable = Table(border=1) stable.AddRow([Center(Bold(_('From:')).Format() + esender)]) stable.AddCellInfo(stable.GetCurrentRowIndex(), 0, colspan=2) left = Table(border=0) left.AddRow([_('Action to take on all these held messages:')]) left.AddCellInfo(left.GetCurrentRowIndex(), 0, colspan=2) btns = hacky_radio_buttons( 'senderaction-' + qsender, (_('Defer'), _('Accept'), _('Reject'), _('Discard')), (mm_cfg.DEFER, mm_cfg.APPROVE, mm_cfg.REJECT, mm_cfg.DISCARD), (0, 0, 0, 1)) ### modifying line above to see if default action for "discard" is ### set here. Hal 7/30/2003 ### (1, 0, 0, 0)) == end code segment == As you can see, I changed the line "(1, 0, 0, 0))" to be "(0, 0, 0, 1))" and the "discard" radio button was selected as the default on the web page. I realize this changes things for all my lists instead of just the one. For now, that is ok since there are few lists to worry about. I would like to request an enhancement by those who know how to develop that this feature be made available on a per list basis. Thanks again, Hal Huntley SRI International ============================================================== > On Wednesday, July 30, 2003, at 03:06 pm, Heath Raftery wrote: > > > Hi Hal, > > > > On Wednesday, July 30, 2003, at 11:36 AM, Hal Huntley wrote: > >> > >> I have a list that gets more spam than legit email. I would like to > >> have the > >> "Action to take on all these held messages" on the > >> "admindb/<listname>" page > >> to have a default of "discard" instead of "defer". This way I can > >> quickly > >> scan the "baddies" and then "submit all data" once I see they are all > >> spam; > >> no clicking on the "Discard" radio button. > > > > Not a definitive answer, but I've found the following in > > Mailman/Mailman/Cgi/admindb.py: > > > > radio = RadioButtonArray(id, (_('Defer'), > > _('Approve'), > > _('Reject'), > > _('Discard')), > > values=(mm_cfg.DEFER, > > mm_cfg.SUBSCRIBE, > > mm_cfg.REJECT, > > mm_cfg.DISCARD), > > checked=0).Format() > > > > I reckon (but have not confirmed) that you could change the checked=0 > > bit to > > checked=4 for Approve > > checked=2 for Reject > > checked=3 for Discard > > Not quite. The value assigned to the checked parameter is the offset of > the radio button in the array which is initially checked when the form > is rendered; the value is the offset in the preceding list of button > names and their values. So: > > checked=0 means the 'Defer' button would be checked > checked=1 means the 'Approve' button would be checked > checked=2 means the 'Reject' button would be checked > checked=3 means the 'Discard' button would be checked > > > > > (got these values from the HTML source generated in a typical > > Administrative Requests page) > > > > This seems to put a CHECKED flag in the <INPUT> tag, which I'm not > > actually sure is valid HTML. > > It is valid HTML. CHECKED (without any value associated) is a valid > attribute of an INPUT tag of TYPE="radio". It causes that radio button > to be in the "on" state when the form is initially displayed. > > > My reading seems to suggest that a value="Yes" is required instead. If > > that is not visible, then the standard is unclear. One version says > > the user agent should select the first radio button in the group, so > > you may want to try rearranging the order of the buttons in the > > RadioButtonArray above instead. > > > >> Right now, I also wish this behavior for one list only, not as a > >> default for > >> all the lists that I have. > > > > Hmm, dunno about that! > > > > If you hack the code in the admindb.py file then the changes will > affect all lists equally. > > > Hope that helps, tell us how you go! > > Heath

1 0

HTML-Tags ins listaddress :-(
by Christian Schoepplein 30 Jul '03

30 Jul '03

Hiho! If HTML-tags were used in a description for a MM-list, in some cases this tags apear in the listaddress. Example: I have a local list called lh2(a)test.dom. In the webinterface I added the following for the listdescription: <b><center>beschreibung</center></b> If I write a mail to the list everything with the addresses in the header is fine...., only the Reply-to-entry looks strange: Reply-To: "<b><center>beschreibung</center></b>" <lh2(a)test.dom> If I reply to this message, my mailer (mutt) uses this entry in his to-field :-(. I'm using MM 2.1.2 and the reply-to for the list is set to the listaddress. MTA is postfix and my MUA is mutt..., but I think its nor a MUA or MTA butt a MM related problem :-(. I cant prevent the listadmins on my site to use this HTML-tags, they think it looks nicer on the listinfopages..., but also they don't want this HTML-stuff in the messages to their lists... Is there a possibility to filter out this HTML-tags? Thanks and the best regards, Schoeppi -- Christian Schoepplein | Beste Rockband der Welt: http://www.lily-rockt.de mail(a)schoeppi.net | Linux fuer Blinde: http://www.blinux.suse.de

1 0

version 2.1.2 of mailman ... problem
by Nyx Wolfwlaker 30 Jul '03

30 Jul '03

Greetings Everyone, My server just upgraded to version 2.1.2 of mailman and i'm getting ever few days all mylists are bouncing ... according to the server admin this is a bug in Mailman, and that there is no patch out there as yet for this problem. If there is a patch, can you please let me know so I can tell them about it, as I do not wish to have them switch from this services to another, that they have given as an less desirable option. Well take care, Nyx Wolfwalker

2 1

web create interface
by Loriann Higashi 30 Jul '03

30 Jul '03

Hi All, I'm having trouble with the web create interface, in that unless I set the data/aliases and data/aliases.db to be owned by apache:mailman, I'll get an error after I use the web interface to create a list. The list is still created, and the aliases added to the data/aliases file, but the list created email does not send and I get the following returned in my web browser: Bug in Mailman version 2.1.2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/var/mailman/Mailman/Cgi/create.py", line 217, in process_request sys.modules[modname].create(mlist, cgi=1) File "/var/mailman/Mailman/MTA/Postfix.py", line 232, in create _update_maps() File "/var/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (acmd, status, errstr) RuntimeError: command failed: /usr/sbin/postalias /var/mailman/data/aliases (status: 1, Operation not permitted) Everything that I've read, including the archives of this list, says that the owner on this file should be mailman:mailman. Everything seems to work with the creation if I set it to apache:mailman, so I'm wondering if there's anything wrong with doing this. And anyone have an explanation why it doesn't work correctly? I'm using Mailman version 2.1.2, python version 2.2.2, on a system running Red Hat Linux 9. Thanks in advance, -Lori -----~-----~-----~-----~-----~-----~-----~-----~----- Loriann Higashi Coordinator of Student Computing loriann.higashi(a)yale.edu (203) 432.9549

1 0

Question: [Fwd: The results of your email commands]
by Glenn Sieb 30 Jul '03

30 Jul '03

Hi everyone... I just upgraded to 2.1.2 recently, I have Postfix running, and postfix-to-mailman.py ... this used to work in 2.1, and is now broken.. :( WhatdidIdowrongnow? :-/ I did a search for "unprocessed" and "confirm" in the mail archives, but didn't see anything come back that looked like this.. Thanks in advance, as always.. Glenn ---------------------------- Original Message ---------------------------- Subject: The results of your email commands From: listnameremoved-bounces(a)lists.wingfoot.org Date: Wed, July 30, 2003 2:36 pm To: ges at wingfoot.org -------------------------------------------------------------------------- The results of your email command are provided below. Attached is your original message. - Unprocessed: Re: You have been invited to join the ListNameRemoved mailing list listnameremoved-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoot.org said: > Your address "ges(a)wingfoot.org" has been invited to join the ListNameRemoved mailing list at lists.wingfoot.org by the ListNameRemoved mailing list owner. You may accept the invitation by simply replying to this message, keeping the Subject: header intact. > > You can also visit this web page: > > https://www.wingfoot.org/mailman/confirm/ListNameRemoved/cc126fa8ddb6a12a4a… > > > Or you should include the following line -- and only the following line -- in a message to ListNameRemoved-request(a)lists.wingfoot.org: > > confirm cc126fa8ddb6a12a4a745126e20baa27404841b5 > > Note that simply sending a `reply' to this message should work from most mail readers. > > If you want to decline this invitation, please simply disregard this message. If you have any questions, please send them to > ListNameRemoved-owner(a)lists.wingfoot.org. > - Ignored: > --- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess - Done. -- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess Return-Path: <ges(a)wingfoot.org> Received: from localhost (localhost.wingfoot.org [127.0.0.1]) by wingfoot.org (Postfix) with ESMTP id 20BAF15294 for <gardmen-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoot.org>; Wed, 30 Jul 2003 14:36:22 -0400 (EDT) Received: from wingfoot.org ([127.0.0.1]) by localhost (caduceus.wingfoot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 72023-06 for <gardmen-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoot.org>; Wed, 30 Jul 2003 14:36:21 -0400 (EDT) Received: from www.wingfoot.org (localhost.wingfoot.org [127.0.0.1]) by wingfoot.org (Postfix) with SMTP id 281B21528E for <gardmen-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoot.org>; Wed, 30 Jul 2003 14:36:21 -0400 (EDT) Received: from 65.246.246.82 (SquirrelMail authenticated user ges) by www.wingfoot.org with HTTP; Wed, 30 Jul 2003 14:36:21 -0400 (EDT) Message-ID: <2939.65.246.246.82.1059590181.squirrel(a)www.wingfoot.org> In-Reply-To: <mailman.0.1059590165.73019.gardmen(a)lists.wingfoot.org> References: <mailman.0.1059590165.73019.gardmen(a)lists.wingfoot.org> Date: Wed, 30 Jul 2003 14:36:21 -0400 (EDT) Subject: Re: You have been invited to join the GardMen mailing list From: "Glenn Sieb" <ges(a)wingfoot.org> To: gardmen-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoo, t.org(a)wingfoot.org User-Agent: SquirrelMail/1.4.0 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at wingfoot.org gardmen-confirm+cc126fa8ddb6a12a4a745126e20baa27404841b5(a)lists.wingfoot.org said: > Your address "ges(a)wingfoot.org" has been invited to join the GardMen > mailing list at lists.wingfoot.org by the GardMen mailing list owner. > You may accept the invitation by simply replying to this message, > keeping the Subject: header intact. > > You can also visit this web page: > > https://www.wingfoot.org/mailman/confirm/gardmen/cc126fa8ddb6a12a4a745126e2… > > > Or you should include the following line -- and only the following > line -- in a message to gardmen-request(a)lists.wingfoot.org: > > confirm cc126fa8ddb6a12a4a745126e20baa27404841b5 > > Note that simply sending a `reply' to this message should work from > most mail readers. > > If you want to decline this invitation, please simply disregard this > message. If you have any questions, please send them to > gardmen-owner(a)lists.wingfoot.org. > > --- The original portions of this message are the copyright of the author (c)1998-2002 Glenn E. Sieb. ICQ UIN: 300395 IRC Nick: Rainbear "All acts of Love and Pleasure are Her rituals"-Charge of the Goddess

1 0

Getting a mailman (python?) variable into a js variable
by Paul H Byerly 30 Jul '03

30 Jul '03

Hi all, I don't even know if this is possible, and I don't know enough about it to run a Google search that gives me what I need to know. Is there a way, in html, to get the contents of %(subject_html)s into a javascript variable? Paul

1 0

Trouble with @ character in archives
by Kaja P. Christiansen 30 Jul '03

30 Jul '03

In the internal code for (La)TeX system, the control sequences use the @ character as a text character; on TeX related lists there are often examples of such internal code. Unfortunately, the archiver (mailman 2.1.2) converts a 'string1@string2' pattern to an email address. So, if a posting has a line with something like: \put(\strip@pt\@tempdimb,\strip@pt\@tempdimc) this line will appear in the archives as \put(\strip at pt\@tempdimb,\strip at pt\@tempdimc) where 'strip at pt' are links pointing to the listinfo page. See: http://www.tug.org/pipermail/test/2003-July/000000.html Is there a workaround to prevent this behaviour? Kaja

2 1

default action on administrative requests
by Hal Huntley 30 Jul '03

30 Jul '03

I sent this question a while back and had no reply. I didn't see my own message come back to me by way of the mailing list, so I presume it did not get out. I'm using Mailman 2.1.2 with Python 2.1.3 with Solaris 8. I've looked through the FAQ. I've seen a similar question on this list, but the answer was "get Mailman 2.1". I now have 2.1.2, but this issue still eludes me. I have a list that gets more spam than legit email. I would like to have the "Action to take on all these held messages" on the "admindb/<listname>" page to have a default of "discard" instead of "defer". This way I can quickly scan the "baddies" and then "submit all data" once I see they are all spam; no clicking on the "Discard" radio button. I don't want to use the Privacy Options -> Sender Filters option of: Action to take for postings from non-members for which no explicit action is defined. to be "discard". I know that the messages would come to me with the: Should messages from non-members, which are automatically discarded, be forwarded to the list moderator? but I really don't want the messages automatically coming to me; I want the member of my list to receive it if I click "Accept". I've seen reference to a script that will just toss everything that is queued up for a list; I would rather not do this. Right now, I also wish this behavior for one list only, not as a default for all the lists that I have. What file do I need to change to make the default choice be "discard" on the administrative requests page? Pointers to documentation gratefully accepted. Thank you, Hal Huntley SRI International

4 3

Internal server error
by Morten-Christian Bernson 30 Jul '03

30 Jul '03

I have installed Mailman 2.1.1 on a FreeBSD 4.7-RELEASE machine with Apache 1.3.27. It's installed from ports with this line: make MM_USERNAME=mailman MM_USERID=91 MM_GROUPNAME=mailman \ MM_GROUPID=91 CGI_GID=80 install This is a new server, and I moved all the files from the old server which used 2.0.11 over to the correct location before the installation, and it seems it converted the existing lists allright. After the installation it seems everything works, you can mail to the list, get replies, /usr/local/mailman/cgi-bin/admin as the www-user shows correct output, and everything is sweet except it doesn't work from the web. I get internal server error, and the apache error-log shows this: Premature end of script headers: /usr/local/mailman/cgi-bin/admin Mailman has user/group id 91, apache has user/group-id 80. PS: httpd.conf contains these lines, and has been restarted (numerous times): ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" Alias /pipermail/ "/usr/local/mailman/archives/public/" I have been searhcing the mailinglist archives, googling the web and usenet, but I can't seem to understand why this happens. Would appreciate any help resolving this problem... -MortenCB

1 0

moving a list to new server
by Kirk R. Wythers 30 Jul '03

30 Jul '03

I am trying to move a list (archives intact) to a new server. Trouble is that when I call up the listinfo page, the old server name is still intact. But, setting up a new testlist on the new server shows the correct servers name in listinfo/testlist. I tried a grep for the two server names and got: root@lorax:148 grep -r fireweed * | egrep -v 'logs|archives|qfiles' Mailman/mm_cfg.py:DEFAULT_HOST_NAME = 'fireweed.org' Binary file Mailman/mm_cfg.pyc matches Binary file lists/neighborsunited/config.db matches Binary file lists/neighborsunited/config.db.last matches Binary file lists/neighborsunited/config.pck matches Binary file lists/neighborsunited/config.pck.last matches Binary file lists/mailman/config.pck matches Binary file lists/mailman/config.pck.last matches root@lorax:149 more Mailman/mm_cfg.py root@lorax:147 grep -r lorax * | egrep -v 'logs|archives|qfiles' Mailman/Defaults.py:DEFAULT_EMAIL_HOST = 'lorax.forestry.umn.edu' Mailman/Defaults.py:DEFAULT_URL_HOST = 'lorax.forestry.umn.edu' Binary file Mailman/Defaults.pyc matches Binary file lists/testlist/config.pck matches Binary file lists/testlist/config.pck.last matches locks/master-qrunner:/usr/local/mailman/locks/master-qrunner.lorax.forestry.umn.edu.77379 locks/master-qrunner.lorax.forestry.umn.edu.77379:/usr/local/mailman/locks/master-qrunner.lorax.forestry.umn.edu.77379 fireweed is the old sever name (lorax is the new one), so I went ahead and changed mm_cfg.py to the new hostname (I must have copied the old mm_cfg.py file over when I moved the list). However, I'm still getting the old server name in /listinfo/oldlist, therefor I'm figureing that the binary files that are associated with the oldlist-oldservername need to be regenerated. Does anyone know how to do this? Thanks Kirk

1 0