Mailman 3 March 2001 - Mailman-Developers

Mailman + DB
by Chris Ryan 12 Mar '01

12 Mar '01

A week or so ago I sent a mail, entitled 'Mailman + PostgeSQL'. Since I have been doing my research on Mailman and getting an idea for how things work in a big picture kind of way. From the many suggestions of people who responded and of my own OOP background making the changes to have Mailman access a data source in an abstracted manner would seem to be the best solution. This email is directed to those who either develop Mailman or have interest in the changes I'm proposing. My motives for making these changes are to allow Mailman to access data from a database, PostgreSQL in my case. This is step one for me and my development needs. With the desire to contribute said changes back to the project in a meaningful way. With that in mind I'm suggesting the development of a standard data containment method that would encapsulate the data. Then data source containers can be developed and deployed for any storage method that some could use such as PostgreSQL, ZopeDB, flat file, etc. I will be working on this definition, hopefully with your input, and develop the first instance using the current storage method. Once that has been done and Mailman modified to use it then future data sources should be easy to add. Outlining the basic encapsulation I will use names that are easy to recognize but will not necessarily be the names used. The encapsulation will actually be a collection of classes so as to make the flow easier to maintain and understand. --------- class List: # does the initialization __init__(self,listname): # these two are for compatibility of the current flat file method # and can be left to perform no action for those sources that don't # need them Load(self): Save(self): # one of each for each attribute # most of these will return the values that are expected # as Mailman is today get<Attribute>(self): set<Attribute>(self,value): # Members/DigestMembers will be handled a little differently # as to create a more uniform and clean interface as they # will return a Members class getMembers(self): # Other data will most likely be encapsulated as Members # such as postings_responses, request_responses and # admin_responses, bounce_info and any other attributes # that are 'complex' class Members: # in my current thinking with the encapsulation it would # make sense to place both members and digest_members # within this one class providing methods to break out # each one as need. # each one of these would return the email keys (lc value of address) # the email key values hence forth will be referred to as userid # ??? why does Mailman care about case of the email addresses ??? getMembers(self): # return a list of _all_ list members getRegularMembers(self): # return a list of all regular list members getDigestMembers(self): # return a list of all digest members # other methods of use getMemberAddress(self,userid): # return the case preserved email of userid getMemberOption(self,userid,option): # returns 0,1 false,true setMemberOption(self,userid,option,state): # set/unset the option getMemberPassword(self,userid): # Returns the users password . . . # and so on # there would be respective classes for the other 'complex' attributes as stated above # in List ----------- The classes with the definition and implementations would could be defined under as such: Mailman/datasources/flatfile.py, Mailman/datasources/postgresql.py and then using a config option the respective file could be loaded with each of the classes into the namespace allowing easy installation of new datasources for use. This doesn't really handle the conversion from one source to another but makes it easy for users to select the kind of source they would like to use. I believe this to be a solid method for adding the functionality desired. I would like to know if people think that this is a good idea or not. Have I missed anything in my concept? Chris Ryan chris(a)greatbridge.com

3 2

Using Mailman as a broadcast list manager
by Jay R. Ashworth 08 Mar '01

08 Mar '01

That's what I'm doing for a client, and before you ask, yes, it's opt-in, and no, you can't have the addresses. :-) My problem is that I haven't had nearly enough time (or warning) on the fact that they only want about 5,000 mails to go out per day to their 55,000+ name list... and I'm not sure which module to put the throttle into. It *looks* like it ought to go in SMTPdirect, but I'm worried about locking issues. And, of course, I'd want it to be a list parameter, though that's not essential for this particular site.Is there anyone on the list who's already done this, or failing that, has a snap answer for this one? I'm headed off to search the archives... but I do have multiple windows on my laptop. :-) Damned fine looking system, BTW: only one 'bug' I've seen so far: The doco says the site password will work anywhere... but it doesn't seem to work as the "old password" for changing a list password, and I can't find anywhere *else* to do that either. Am I missing something, or is that really a bug? I'm gonna check Jitterbug for that, too, during my search. Cheers, -- jra -- Jay R. Ashworth jra(a)baylink.com Member of the Technical Staff Baylink The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 804 5015

1 0

mailman and qmail-inject
by Jason R. Mastaler 08 Mar '01

08 Mar '01

Greetings, I've been looking to move my lists over to Mailman, but I run qmail and understand there are some "issues" with this combination. If I'm not mistaken, mailman injects outgoing messages via SMTP on localhost. This method is problematic on qmail systems, because it circumvents `qmail-inject' which is responsible for adding appropriate information to the message header before it gets sent to the outgoing queue. The end result is that Mailman messages sent from a qmail server lack certain important headers such as "Date:" and "Message-ID:". Has anyone addressed or made plans to address this issue? -- ____________________________________________________________ My 'jason-dated-*' e-mail address is valid, but expirable. It will expire in 7 day(s) from the date of this message. For more information see <http://jason.mastaler.com/tms/>. ____________________________________________________________

1 0

Idea as for the non-arching issue
by Steffen Bardolatzi 08 Mar '01

08 Mar '01

Unfortunately, I can´t prove it but this might be the reason for non-archiving issues: For the last times I posted with "steffen(a)asta.uni-wuppertal.de" which is basically the same as "steffen(a)wflin3.asta.uni-wuppertal.de" with one difference: - I am subscribed with "steffen(a)wflin3.asta.uni-wuppertal.de" - asta.uni-wuppertal.de is allowed, too - there is no DNS-entry for asta.uni-wuppertal.de (we can't change it) Apart from these details the recent message with "...wflin3..." in it *has* been archived. If the archiving code has not been changed from 2.01 up to 2.02: does it is possible that *non*-Subscribers are not archived (different in Beta 6)? If this was true there was an important issue to us because we *have to* archive non-members messages archiving an external Mailinglist for internal use (filtering Bcc messages). Any ideas about that?! Thanks in advance, Steffen

1 0

Any ideas what happened here?
by Phil Barnett 08 Mar '01

08 Mar '01

I tracked down process 25798 and it was a mailman qrunner process... Mar 6 03:41:39 taz2 kernel: Unable to handle kernel paging request at virtual address 0000a014 Mar 6 03:41:39 taz2 kernel: current->tss.cr3 = 1b247000, %cr3 = 1b247000 Mar 6 03:41:39 taz2 kernel: *pde = 00000000 Mar 6 03:41:39 taz2 kernel: Oops: 0000 Mar 6 03:41:39 taz2 kernel: CPU: 0 Mar 6 03:41:39 taz2 kernel: EIP: 0010:[try_to_free_buffers+18/132] Mar 6 03:41:39 taz2 kernel: EFLAGS: 00010202 Mar 6 03:41:39 taz2 kernel: eax: 0000a000 ebx: c06ce720 ecx: 00000013 edx: 0003efe0 Mar 6 03:41:39 taz2 kernel: esi: 0000a000 edi: 0000a000 ebp: c06ce720 esp: d5c11ec0 Mar 6 03:41:39 taz2 kernel: ds: 0018 es: 0018 ss: 0018 Mar 6 03:41:39 taz2 kernel: Process python (pid: 25798, process nr: 167, stackpage=d5c11000) Mar 6 03:41:39 taz2 kernel: Stack: 00000013 00000000 c011d7ce c06ce720 00000002 00000006 00000013 c0122542 Mar 6 03:41:39 taz2 kernel: 00000006 00000013 00000001 00000013 00000013 c0122670 00000013 d5c10000 Mar 6 03:41:39 taz2 kernel: 00000000 c0122ec0 00000013 00000000 00000000 00000000 00000000 c011d49b Mar 6 03:41:39 taz2 kernel: Call Trace: [shrink_mmap+238/324] [do_try_to_free_pages+38/120] [try_to_free_pages+40/52] [ __get_free_pages+180/1020] [merge_segments+327/364] [do_generic_file_read+1136/1500] [generic_file_read+99/124] Mar 6 03:41:39 taz2 kernel: [file_read_actor+0/80] [sys_read+174/196] [system_call+52/56] Mar 6 03:41:39 taz2 kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 0f 6a 00 e8 6c 01 Mar 6 03:42:09 taz2 proftpd[25807]: harbour-project.org (195.151.104.115[195.151.104.115]) - FTP session closed. Mar 7 09:53:29 taz2 syslogd 1.3-3: restart. -- Phil Barnett mailto:midnight@the-oasis.net WWW http://www.the-oasis.net/ FTP Site ftp://ftp.the-oasis.net

2 2

best wy to upgrade from Mailman 2.0b6 to 2.02?
by Steffen Bardolatzi 08 Mar '01

08 Mar '01

There are some archiv related issues - unfortunatley not archived for some reasons - with upgrading from V2.0b6 to V2.0x final [last attempt with 2.01]. First of all what´s running: - Linux 2.2.x - Python 1.52 (1.6 or 2.0 compiled additionally but did not work with currently passwords i.e. I was not able to login as mailman-owner nor listowner - using a make install) - there are running some inportant liste --> I can´t afford *any* loss of e-mails and archived messages [for this reason I always make a backup] - qmail as MTA I. Upgrading to 2.0 with mailman 2.0.x --> see above, mail delivery seems to work: - passwords are not recognized, it is no way to reset them to default values --> how does it is possible to upgrade to Python 2.0 *without* leaving *all* passwords? ==> I´ll stick with Mailman 2.0x for I have to keep the current list + datebases, if there was a password converter there was not problem ==> sticking with Python 1.52 for now --> II II. Upgrade to mailman 2.0x: - first make install, then - passwords still work - mail delivery is fine - archives *only* work with *some* already configured lists, e.g. "testliste" does *not* archive - newly created lists does not archive *at all* - I couldn´t figure out wrongly set permissions So what might be the best way to upgrade to 2.02 final with using the old datebase and passwords without any loss of data? Thanks in advance, Steffen

1 0

MM 2.0.2: AttributeError: MMAlreadyMember
by Mentor Cana 07 Mar '01

07 Mar '01

Here is the error I get when attempting to approve subscription Request on "confirm+approval" list. thanks, Mentor --- Mar 07 17:07:00 2001 admin(15231): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(15231): [----- Mailman Version: 2.0.2 -----] admin(15231): [----- Traceback ------] admin(15231): Traceback (most recent call last): admin(15231): File "/opt/home/mailman/scripts/driver", line 96, in run_main admin(15231): main() admin(15231): File "/opt/home/mailman/Mailman/Cgi/admindb.py", line 88, in main admin(15231): HandleRequests(mlist, doc, cgidata) admin(15231): File "/opt/home/mailman/Mailman/Cgi/admindb.py", line 271, in HandleRequests admin(15231): preserve, forward, forwardaddr) admin(15231): File "/opt/home/mailman/Mailman/ListAdmin.py", line 133, in HandleRequest admin(15231): status = self.__handlesubscription(data, value, comment) admin(15231): File "/opt/home/mailman/Mailman/ListAdmin.py", line 331, in __handlesubscription admin(15231): except Errors.MMAlreadyMember: admin(15231): AttributeError: MMAlreadyMember ....

2 1

Feature request
by Kurt Seifried 07 Mar '01

07 Mar '01

Have you guys looked at GnuPG/X.509 encryption, i.e. someone sends a message to the list, and instead of just blonking it out to all members it checks a table for email address and GnuPG key/X.509 cert, and if found encrypts the email to that user with their key. It would be a nice optional feature. Kurt Seifried, seifried(a)securityportal.com Securityportal - your focal point for security on the 'net

2 1

Making mailman RPM friendly
by Wari Wahab 07 Mar '01

07 Mar '01

Hi there, tried to build an RPM of mailman and I found that it's not easy to do so with a plain vannila spec file.. Here I include a patch that allows easy creation of RPMs which you might want to include it in you next release, but then again, you might not coz I believe it's an ugly hack ;) and it's also not fhs compliant.. diff -u -r mailman-2.0/Mailman/Archiver/Makefile.in mailman-2.0rc3/Mailman/Archiver/Makefile.in --- mailman-2.0/Mailman/Archiver/Makefile.in Tue Mar 21 14:25:10 2000 +++ mailman-2.0rc3/Mailman/Archiver/Makefile.in Fri Nov 24 16:40:12 2000 @@ -59,7 +59,7 @@ install: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done finish: diff -u -r mailman-2.0/Mailman/Bouncers/Makefile.in mailman-2.0rc3/Mailman/Bouncers/Makefile.in --- mailman-2.0/Mailman/Bouncers/Makefile.in Tue Mar 21 14:25:35 2000 +++ mailman-2.0rc3/Mailman/Bouncers/Makefile.in Fri Nov 24 16:41:45 2000 @@ -57,7 +57,7 @@ install: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done finish: diff -u -r mailman-2.0/Mailman/Cgi/Makefile.in mailman-2.0rc3/Mailman/Cgi/Makefile.in --- mailman-2.0/Mailman/Cgi/Makefile.in Tue Mar 21 14:25:43 2000 +++ mailman-2.0rc3/Mailman/Cgi/Makefile.in Fri Nov 24 16:42:19 2000 @@ -59,7 +59,7 @@ install: for f in $(CGI_MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(CGIDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(CGIDIR); \ done finish: diff -u -r mailman-2.0/Mailman/Handlers/Makefile.in mailman-2.0rc3/Mailman/Handlers/Makefile.in --- mailman-2.0/Mailman/Handlers/Makefile.in Tue Mar 21 14:25:51 2000 +++ mailman-2.0rc3/Mailman/Handlers/Makefile.in Fri Nov 24 16:42:40 2000 @@ -57,7 +57,7 @@ install: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done finish: diff -u -r mailman-2.0/Mailman/Logging/Makefile.in mailman-2.0rc3/Mailman/Logging/Makefile.in --- mailman-2.0/Mailman/Logging/Makefile.in Sat Jun 3 06:13:10 2000 +++ mailman-2.0rc3/Mailman/Logging/Makefile.in Fri Nov 24 16:42:53 2000 @@ -57,7 +57,7 @@ install: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done finish: diff -u -r mailman-2.0/Mailman/Makefile.in mailman-2.0rc3/Mailman/Makefile.in --- mailman-2.0/Mailman/Makefile.in Tue Mar 21 14:24:59 2000 +++ mailman-2.0rc3/Mailman/Makefile.in Fri Nov 24 16:41:25 2000 @@ -64,12 +64,12 @@ install-here: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done - $(INSTALL) -m $(FILEMODE) mm_cfg.py.dist $(PACKAGEDIR) - if [ ! -f $(PACKAGEDIR)/mm_cfg.py ]; \ + $(INSTALL) -m $(FILEMODE) mm_cfg.py.dist $(DESTDIR)$(PACKAGEDIR) + if [ ! -f $(DESTDIR)$(PACKAGEDIR)/mm_cfg.py ]; \ then \ - $(INSTALL) -m $(FILEMODE) mm_cfg.py.dist $(PACKAGEDIR)/mm_cfg.py; \ + $(INSTALL) -m $(FILEMODE) mm_cfg.py.dist $(DESTDIR)$(PACKAGEDIR)/mm_cfg.py; \ fi install: install-here diff -u -r mailman-2.0/Mailman/pythonlib/Makefile.in mailman-2.0rc3/Mailman/pythonlib/Makefile.in --- mailman-2.0/Mailman/pythonlib/Makefile.in Tue Mar 21 14:26:05 2000 +++ mailman-2.0rc3/Mailman/pythonlib/Makefile.in Fri Nov 24 16:43:05 2000 @@ -58,7 +58,7 @@ install: for f in $(MODULES); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(PACKAGEDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(PACKAGEDIR); \ done finish: diff -u -r mailman-2.0/Makefile.in mailman-2.0rc3/Makefile.in --- mailman-2.0/Makefile.in Fri Sep 22 16:06:19 2000 +++ mailman-2.0rc3/Makefile.in Fri Nov 24 17:01:48 2000 @@ -82,7 +82,7 @@ @echo "Creating architecture independent directories..." @for d in $(VAR_DIRS); \ do \ - dir=$(var_prefix)/$$d; \ + dir=$(DESTDIR)$(var_prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ ./mkinstalldirs $$dir; \ @@ -91,10 +91,10 @@ else true; \ fi; \ done - chmod o-r $(var_prefix)/archives/private + chmod o-r $(DESTDIR)$(var_prefix)/archives/private @for d in $(ARCH_INDEP_DIRS); \ do \ - dir=$(prefix)/$$d; \ + dir=$(DESTDIR)$(prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ ./mkinstalldirs $$dir; \ @@ -106,7 +106,7 @@ @echo "Creating architecture dependent directories..." @for d in $(ARCH_DEP_DIRS); \ do \ - dir=$(exec_prefix)/$$d; \ + dir=$(DESTDIR)$(exec_prefix)/$$d; \ if test ! -d $$dir; then \ echo "Creating directory hierarchy $$dir"; \ ./mkinstalldirs $$dir; \ @@ -119,7 +119,7 @@ do \ (cd $$d; $(MAKE) install); \ done - $(PYTHON) -c 'from compileall import *; compile_dir("$(prefix)/Mailman")' + $(PYTHON) -c 'from compileall import *; compile_dir("$(DESTDIR)$(prefix)/Mailman")' update: @(cd $(prefix) ; bin/update) | tee ./update.log diff -u -r mailman-2.0/bin/Makefile.in mailman-2.0rc3/bin/Makefile.in --- mailman-2.0/bin/Makefile.in Fri May 5 06:51:31 2000 +++ mailman-2.0rc3/bin/Makefile.in Fri Nov 24 16:45:36 2000 @@ -62,7 +62,7 @@ install: for f in $(SCRIPTS); \ do \ - $(INSTALL) -m $(EXEMODE) $$f $(SCRIPTSDIR); \ + $(INSTALL) -m $(EXEMODE) $$f $(DESTDIR)$(SCRIPTSDIR); \ done finish: diff -u -r mailman-2.0/cron/Makefile.in mailman-2.0rc3/cron/Makefile.in --- mailman-2.0/cron/Makefile.in Wed Nov 1 10:32:05 2000 +++ mailman-2.0rc3/cron/Makefile.in Fri Nov 24 16:45:57 2000 @@ -59,7 +59,7 @@ install: for f in $(SCRIPTS); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(CRONDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(CRONDIR); \ done finish: diff -u -r mailman-2.0/filters/Makefile.in mailman-2.0rc3/filters/Makefile.in --- mailman-2.0/filters/Makefile.in Fri Sep 22 16:00:01 2000 +++ mailman-2.0rc3/filters/Makefile.in Fri Nov 24 16:46:18 2000 @@ -59,7 +59,7 @@ install: for f in $(FILTERS); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(FILTERSDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(FILTERSDIR); \ done finish: diff -u -r mailman-2.0/misc/Makefile.in mailman-2.0rc3/misc/Makefile.in --- mailman-2.0/misc/Makefile.in Fri Sep 22 15:58:52 2000 +++ mailman-2.0rc3/misc/Makefile.in Fri Nov 24 16:47:20 2000 @@ -61,14 +61,14 @@ all: install: - $(INSTALL) -m $(FILEMODE) Cookie.py $(PACKAGEDIR) - $(INSTALL) -m $(FILEMODE) $(ICONS) $(ICONDIR) + $(INSTALL) -m $(FILEMODE) Cookie.py $(DESTDIR)$(PACKAGEDIR) + $(INSTALL) -m $(FILEMODE) $(ICONS) $(DESTDIR)$(ICONDIR) for d in $(PATHSDIRS); \ do \ - dir=$(prefix)/$$d; \ + dir=$(DESTDIR)$(prefix)/$$d; \ $(INSTALL) -m $(FILEMODE) paths.py $$dir; \ done - $(INSTALL) -m $(DATAMODE) pending_subscriptions.db $(DATADIR) + $(INSTALL) -m $(DATAMODE) pending_subscriptions.db $(DESTDIR)$(DATADIR) finish: diff -u -r mailman-2.0/scripts/Makefile.in mailman-2.0rc3/scripts/Makefile.in --- mailman-2.0/scripts/Makefile.in Tue Mar 21 14:26:37 2000 +++ mailman-2.0rc3/scripts/Makefile.in Fri Nov 24 16:47:35 2000 @@ -58,7 +58,7 @@ install: for f in $(SCRIPTS); \ do \ - $(INSTALL) -m $(FILEMODE) $$f $(SCRIPTSDIR); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(SCRIPTSDIR); \ done finish: diff -u -r mailman-2.0/src/Makefile.in mailman-2.0rc3/src/Makefile.in --- mailman-2.0/src/Makefile.in Sun Aug 6 13:03:00 2000 +++ mailman-2.0rc3/src/Makefile.in Fri Nov 24 16:49:16 2000 @@ -111,18 +111,18 @@ install: all for f in $(CGI_PROGS); \ do \ - exe=$(CGIDIR)/$$f$(CGIEXT); \ + exe=$(DESTDIR)$(CGIDIR)/$$f$(CGIEXT); \ $(INSTALL_PROGRAM) $$f $$exe; \ chmod g+s $$exe; \ done for f in $(MAIL_PROGS); \ do \ - $(INSTALL_PROGRAM) $$f $(MAILDIR); \ - chmod g+s $(MAILDIR)/$$f; \ + $(INSTALL_PROGRAM) $$f $(DESTDIR)$(MAILDIR); \ + chmod g+s $(DESTDIR)$(MAILDIR)/$$f; \ done # @for f in $(ALIAS_PROGS); \ # do \ -# $(INSTALL_PROGRAM) $$f $(bindir) ; \ +# $(INSTALL_PROGRAM) $$f $(DESTDIR)$(bindir) ; \ # done finish: diff -u -r mailman-2.0/templates/Makefile.in mailman-2.0rc3/templates/Makefile.in --- mailman-2.0/templates/Makefile.in Tue Mar 21 14:26:46 2000 +++ mailman-2.0rc3/templates/Makefile.in Fri Nov 24 16:49:53 2000 @@ -59,8 +59,8 @@ install: for f in $(TEMPLATES); \ do \ - mv -f $(TEMPLATEDIR)/$$f $(TEMPLATEDIR)/$$f.prev || $(TRUE); \ - $(INSTALL) -m $(FILEMODE) $$f $(TEMPLATEDIR); \ + mv -f $(DESTDIR)$(TEMPLATEDIR)/$$f $(DESTDIR)$(TEMPLATEDIR)/$$f.prev || $(TRUE); \ + $(INSTALL) -m $(FILEMODE) $$f $(DESTDIR)$(TEMPLATEDIR); \ done finish: Summary: The GNU Mailing List Management System Name: mailman Version: 2.0.2 Release: 1 Copyright: GPL Group: System Environment/Mailing List Managers Source: http://www.list.org/mailman-2.0.2.tgz URL: http://www.list.org Patch0: mailman-rpm.diff BuildRoot: /var/tmp/%{name}-root Packager: Wari Wahab<wari(a)celestix.com> Requires: python %description Mailman is software to help manage electronic mail discussion lists, much like Majordomo or Smartmail. Mailman gives each mailing list a unique web page and allows users to subscribe, unsubscribe, and change their account options over the web. Even the list manager can administer his or her list entirely via the web. Mailman has most of the features that people want in a mailing list management system, including built-in archiving, mail-to-news gateways, spam filters, bounce detection, digest delivery, and so on. %prep %setup -q %patch0 -p1 find . -type d -exec chmod 755 {} \; %build /usr/sbin/groupadd -g 88 mailman /usr/sbin/useradd -d /var/mailman -g mailman -u 88 mailman chgrp mailman /var/mailman chmod a+rx,g+ws /var/mailman export CFLAGS="$RPM_OPT_FLAGS"; CFLAGS="$RPM_OPT_FLAGS" ./configure --prefix=/var/mailman --with-mail-gid=mailman make CFLAGS="$RPM_OPT_FLAGS" %install rm -rf $RPM_BUILD_ROOT mkdir -p $RPM_BUILD_ROOT/var/mailman chgrp mailman $RPM_BUILD_ROOT/var/mailman chmod a+rx,g+ws $RPM_BUILD_ROOT/var/mailman make DESTDIR=$RPM_BUILD_ROOT install %pre /usr/sbin/groupadd -g 88 mailman /usr/sbin/useradd -d /var/mailman -g mailman -u 88 mailman %post su mailman -c '/usr/bin/crontab /var/mailman/cron/crontab.in' %clean rm -rf $RPM_BUILD_ROOT /usr/sbin/userdel mailman %files %dir /var/mailman /var/mailman/* %changelog * Wed Mar 07 2001 Wari Wahab <wari(a)celestix.com> - Modified for the latest mailman 2.0.2 * Wed Dec 20 2000 Wari Wahab <wari(a)celestix.com> - Initial RPM of mailman

1 0

Re: [Mailman-Developers] Fresh install of i18n Mailman
by Ralph Corderoy 07 Mar '01

07 Mar '01

Hi, > I have tried to make a fresh install from CVS. > I get one error that says: > > Compiling /home/mailman/Mailman/versions.py ... > Traceback (most recent call last): > File "bin/update", line 31, in ? > from Mailman import Utils > File "/home/mailman/Mailman/Utils.py", line 37, in ? > from mimelib.MsgReader import MsgReader > ImportError: No module named mimelib.MsgReader > > Has anybody experimented this?. Or did I forget how to install Mailman? Have you fetched Barry's new mimelib module? This is a FAQ these days; I think the docs in CVS might mention it's required. Ralph.

4 4