Mailman 3 January 2004 - Mailman-Users

mailman-2.1.4
by Camelia Botez 01 Jan '04

01 Jan '04

I try to install mailman-2.1.4 using python-2.2.2. Everything goes well and check_perms doesn't report problems. But when I try to creat a test list by running newlist command ( and give all the asked details) I get error message: ./newlist Enter the name of the list: test Enter the email of the person running the list: camelia@wicc Initial test password: Traceback (most recent call last): File "./newlist", line 219, in ? main() File "./newlist", line 151, in main mlist = MailList.MailList() File "/export/mailman/Mailman/MailList.py", line 101, in __init__ self.InitTempVars(name) File "/export/mailman/Mailman/MailList.py", line 249, in InitTempVars withlogging = mm_cfg.LIST_LOCK_DEBUGGING) File "/export/mailman/Mailman/LockFile.py", line 192, in __init__ self.__tmpfname = '%s.%s.%d.%d' % ( AttributeError: 'module' object has no attribute 'gethostname' Exception exceptions.AttributeError: "LockFile instance has no attribute '_LockFile__owned'" in ignored How can I fix this ? Thank you camelia.botez(a)weizmann.ac.il Camelia Botez System Administrator Weizmann Institute of Science - Computing Center E-mail camelia.botez(a)weizmann.ac.il Phone 972-8-9344964 Fax 972-8-9344106 or 972-8-9344102

1 0

trying to install mailman-2.1.4
by camelia 01 Jan '04

01 Jan '04

I try to install mailman-2.1.4 using python-2.2.2. Everything goes well and check_perms doesn't report problems. But when I try to creat a test list by running newlist command ( and give all the asked details) I get error message: ./newlist Enter the name of the list: test Enter the email of the person running the list: camelia@wicc Initial test password: Traceback (most recent call last): File "./newlist", line 219, in ? main() File "./newlist", line 151, in main mlist = MailList.MailList() File "/export/mailman/Mailman/MailList.py", line 101, in __init__ self.InitTempVars(name) File "/export/mailman/Mailman/MailList.py", line 249, in InitTempVars withlogging = mm_cfg.LIST_LOCK_DEBUGGING) File "/export/mailman/Mailman/LockFile.py", line 192, in __init__ self.__tmpfname = '%s.%s.%d.%d' % ( AttributeError: 'module' object has no attribute 'gethostname' Exception exceptions.AttributeError: "LockFile instance has no attribute '_LockFile__owned'" in ignored How can I fix this ? Thank you camelia.botez(a)weizmann.ac.il

1 0

New Mailman User
by April Cox 31 Dec '03

31 Dec '03

Hi there! I was hoping someone out there could help me. I'm a new user of mailman and am creating a list for a professional organization. It's an outgoing-bound list only, specifically I'll be using it to send out meeting announcements and reminders. I was able to set it up to not allow members or non-members to post to the list. But I was unable to prevent it from allowing people to respond to the email they receive from me. Right now it goes to the list - which I don't want. I set the option to REPLY-TO an explicit address and entered my email address, so that when people have questions about the meeting or announcement, I can respond to them, and it doesn't post to the list. But it doesn't work. It's still being sent to the group. I could remove the listname from being in the FROM field, but if I do that, then my own name is the one that the message comes from, which is not my intention either, since it is a message for the group sent by the association - not me personally. Can anyone tell me what I'm doing wrong? The version of mailman that I'm using is: version 2.1.2. Thank you in advance for your help. Happy New Year! April

2 1

Re: [Mailman-Users] RELEASED Mailman 2.1.4
by Ricardo Kleemann 31 Dec '03

31 Dec '03

Thanks Ed. One thing I hadn't noticed in my first mailman installation and which I did notice with the SUSE rpm's installation is the use of files /etc/mailman.cgi-gid and /etc/mailman.mail-gid. Does that setup work right out of the box? Basically it allows to dynamically set the proper gid without having to rebuild mailman with the specific gid settings. That is really nice. I'm hoping I can build mailman-2.1.4 from the tarball and it will consult those files for gid configuration? Ricardo ----- Original Message Follows ----- > > On Wed, Dec 31, 2003 at 04:04:37PM -0800, Ricardo Kleemann > > wrote: > > I have a question... I currently run mailman as > > installed via RPM (under SUSE 9.0). How can I upgrade > > via the tarball? I mean the rpm puts files into specific > > locations (such as both /usr/lib/mailman and > > /var/lib/mailman) and I wanted to make sure that when I > > upgrade, the files go into the same locations where they > > are currently. How can I specify the locations? > > Three options. > 1. Since this is a security fix, SuSe should either > backport the security patch into the version they've > released, or upgrade to 2.1.4. You can post to a > SuSe-specific list to find out what they plan on doing, or > you could contact the package maintainer. 2. Grab the > source RPM from SuSe's distribution. Install it, and then > study the spec file to see what they've done and what > patches they've applied. Merge the new source changes > with theirs, or replace their source with the one from > sourceforge. Rebuild the source rpm and have a good look > at the rpm it produced to see if the files look like > they'll go in the right locations. You'll also need to > study any config changes and see if they're still > applicable. 3. Remove the SuSe RPM. Install the > sourceforge package and then migrate your lists over. > Forget about ever upgrading from SuSe. > > You really have to decide if you're going to trust your > distributor - SuSe in this case - or go to the original > package maintainer for your updates. You shouldn't mix > and match. > > I run Red Hat Enterprise Linux and simply go with a stock > mailman package and watch for the updates myself. Red Hat > doesn't even package mailman any more, but I went this > route with an older Red Hat Linux when Red Hat still was > shipping it. > > .../Ed > > p.s. In the future, please snip your replies to the > relevant pieces. > > -- > Ed Wilts, Mounds View, MN, USA > mailto:ewilts@ewilts.org

1 0

Re: [Mailman-Users] RELEASED Mailman 2.1.4
by Ricardo Kleemann 31 Dec '03

31 Dec '03

Hi, Thanks for the update! I have a question... I currently run mailman as installed via RPM (under SUSE 9.0). How can I upgrade via the tarball? I mean the rpm puts files into specific locations (such as both /usr/lib/mailman and /var/lib/mailman) and I wanted to make sure that when I upgrade, the files go into the same locations where they are currently. How can I specify the locations? Thanks Ricardo ----- Original Message Follows ----- > > > I have released Mailman 2.1.4, a bug fix release that also > contains support for four new languages: Catalan, Croatian > , Romanian, and Slovenian. This release also contains a > fix for a cross-site scripting vulnerability in the > 'admin' cgi script (see CAN-2003-0965). There is also an > expanded ability to filter message headers, nominally to > provide better support when Mailman is used in conjunction > with upstream spam and virus filters. > > The full source tarball has been made available from the > usual sites. Sorry, there is no patch available yet, but > you should be able to install Mailman 2.1.4 over your > existing 2.1.x installation. See > > > http://sourceforge.net/project/showfiles.php?group_id=103 > > for links to the downloadable files. After installing, be > sure you restart your Mailman daemon by doing a > "mailmanctl restart". > > IMPORTANT: You will want to re-run configure before doing > a make install. > > See also: > > http://www.list.org > http://mailman.sf.net > http://www.gnu.org/software/mailman > > Enjoy, and have a Happy New Year. > -Barry > > -------------------- snip snip -------------------- > 2.1.4 (31-Dec-2003) > > - Close some cross-site scripting vulnerabilities in > the admin pages > (CAN-2003-0965). > > - New languages: Catalan, Croatian, Romanian, > Slovenian. > > - New mm_cfg.py/Defaults.py variable PUBLIC_MBOX which > allows the site > administrator to disable public access to all the > raw list mbox files > (this is not a per-list configuration). > > - Expanded header filter rules under Privacy -> Spam > Filters. Now you can > specify regular expression matches against any > header, with specific > actions tied to those matches. > > - Rework the SMTP error handling in SMTPDirect.py to > avoid scoring bounces > for all recipients when a permanent error code is > returned by the mail > server (e.g. because of content restrictions). > > - Promoted SYNC_AFTER_WRITE to a Default.py/mm_cfg.py > variable and > make it control syncing on the config.pck file. > Also, we always flush > and sync message files. > > - Reduce archive bloat by not storing the HTML body of > Article objects in > the Pipermail database. A new script bin/rb-archfix > was added to clean > up older archives. > > - Proper RFC quoting for List-ID descriptions. > > - PKGDIR can be passed to the make command in order to > specify a different > directory to unpack the distutils packages in misc. > (SF bug 784700). > > - Improved logging of the origin of subscription > requests. > > - Bugs and patches: 832748 (unsubscribe_policy ignored > for unsub button on > member login page), 846681 (bounce disabled cookie > was always out of > date), 835870 (check VIRTUAL_HOST_OVERVIEW on > through the web list > creation), 835036 (global address change when the > new address is already > a member of one of the lists), 833384 (incorrect > admin password on a > hold message confirmation attachment would discard > the message), 835012 > (fix permission on empty archive index), 816410 > (confirmation page > consistency), 834486 (catch empty charsets in the > scrubber), 777444 (set > the process's supplemental groups if possible), > 860135 (ignore > DiscardMessage exceptions during digest scrubbing), > 828811 (reduce > process size for list and admin overviews), > 864674/864676 (problems > accessing private archives and rosters with admin > password), 865661 > (Tokio Kikuchi's i18n patches), 862906 (unicode > prefix leak in admindb), > 841445 (setting new_member_options via config_list), > n/a (fixed email > command 'set delivery') > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users(a)python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: ricardo(a)americasnet.com > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/ricardo%40americasnet.…

2 1