Mailman 3 June 2000 - Mailman-Developers

Bug still in current CVS
by Dan Mick 22 Jun '00

22 Jun '00

I had to fix this bug, which was reported in May, before I could use the current CVS: dmick@we-24-30-117-227> diff ListAdmin.py.orig ListAdmin.py 182c182 < enqueue = HandlerAPI.DeliverToList(self, msg, newdata=msgdata) --- > enqueue = HandlerAPI.DeliverToList(self, msg, msgdata) Could someone with putback access clean this up, please?

2 1

Re: [Mailman-Developers] Re: [Mailman-Users] Domain allowed to post to a list.
by J C Lawrence 22 Jun '00

22 Jun '00

On Thu, 22 Jun 2000 10:18:32 +0200 (CEST) Evilio del Rio <edelrio(a)icm.csic.es> wrote: > Now the good news: it is easy to patch Mailman to accept a regular > expression as the "posters" settings (addresses allowed to post to > a restricted list even if they are not members). I have patched > the following file: Oooo. This one should get into the next beta. A whole bunch of people would be very happy to see that. Barry? -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

1 0

including subscribe address in message
by Ryan Fife 22 Jun '00

22 Jun '00

Before I start looking into this I thought I'd check to see if it's already been done/investigated. I would like to include a line that says: You are subscribed as: fife(a)AnwyhereYouGo.com in the body of the message on the way out. I know it will increase the needed processing of messages tremendously, but it would be good for our subscribers as well as the list admin (me!). Our mail server doesn't have anything better to do anyway... -- Ryan Fife fife(a)AnywhereYouGo.com Creators of the world's first online WAP testing tool: http://www.AnywhereYouGo.com/Content.po?name=lab/About

2 1

New beta release needed (+ little patch)
by Bernhard Reiter 22 Jun '00

22 Jun '00

It looks like a new mailman beta or even pre beta release is badly needed. I had to make to many little adjustments to 2.0b2. (Also see my mail to mailman-users in April.) So please release a bug-fix version. I see people going for the CVS version. This creates a lot of work for people who just want to run mailman in a stable way. Here is another little patch so that error messages for external archivers do not get lost. (You have to other chance to get that information.) Regards, Bernhard -- Professional Service around Free Software (intevation.net) The FreeGIS Project (freegis.org) Association for a Free Informational Infrastructure (ffii.org)

3 2

Fwd: Mailman error messages.
by Christopher Kolar 22 Jun '00

22 Jun '00

This was sent to me by someone. No need to reply directly to me, and the person is not on the list. --chris >From: "czh" <tonytsai(a)ec.dayi.com> >To: <ckolar(a)admin.aurora.edu> >Subject: Mailman error messages. >Date: Thu, 22 Jun 2000 14:30:43 +0800 >X-Mailer: Microsoft Outlook Express 5.00.2615.200 > >Hi Ckolar, >I just want to install Mailman into my Slackware, but got the error messages, > ---------------- Begin of error messages ------------- > > >Bug in Mailman version 2.0beta2 > > > > > >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 (innermost last): > File "/home/mailman/scripts/driver", line 64, in run_main > immediate=1) > File "/home/mailman/Mailman/Logging/StampedLogger.py", line 49, in __init__ > Logger.__init__(self, category, nofail, immediate) > File "/home/mailman/Mailman/Logging/Logger.py", line 40, in __init__ > self.__get_f() > File "/home/mailman/Mailman/Logging/Logger.py", line 55, in __get_f > f = self.__fp = open(self.__filename, 'a+', 1) >IOError: [Errno 13] Permission denied: '/home/mailman/logs/error' > > > >---------- > > >Python information: > > > >Variable Value >sys.version 1.5.2 (#1, Jul 17 1999, 22:10:16) [GCC egcs-2.91.66 >19990314/Linux (egcs- >sys.executable /usr/bin/python >sys.prefix /usr >sys.exec_prefix /usr >sys.path /usr >sys.platform linux2 > > >---------- > > >Environment variables: > > > >Variable Value >DOCUMENT_ROOT /usr/local/etc/httpd/htdocs >SERVER_ADDR 203.74.9.7 >HTTP_ACCEPT_ENCODING gzip, deflate, gzip, deflate >SERVER_PORT 443 >PATH_TRANSLATED /usr/local/etc/httpd/htdocs/abcde >ssl_unclean_shutdown 1 >SERVER_PROTOCOL HTTP/1.1 >HTTP_ACCEPT_LANGUAGE zh-tw, zh-tw >GATEWAY_INTERFACE CGI/1.1 >nokeepalive 1 >HTTP_CONNECTION Keep-Alive >HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt) >HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, >application/vnd.ms-powerpoint, application/vnd.ms-excel, >application/msword, */* >REQUEST_URI /mailman/admin/abcde >SERVER_NAME czh.dayi.com >PATH >/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/openwin/bin:/usr/games:/opt/kde/bin:/usr/share/texmf/bin > >QUERY_STRING >SCRIPT_FILENAME /home/mailman/cgi-bin/admin >HTTPS on >PATH_INFO /abcde >HTTP_HOST czh.dayi.com >REQUEST_METHOD GET >SERVER_SIGNATURE Apache/1.3.12 Server at czh.dayi.com Port 443 >SCRIPT_NAME /mailman/admin >SERVER_ADMIN root(a)czh.dayi.com >SERVER_SOFTWARE Apache/1.3.12 (Unix) PHP/4.0.0 mod_ssl/2.6.4 OpenSSL/0.9.5a >PYTHONPATH /home/mailman >REMOTE_ADDR 203.74.9.62 >REMOTE_PORT 64731

1 0

Indexing pipermail archives
by Nigel Metheringham 22 Jun '00

22 Jun '00

I've just been looking at the problem of indexing/searching a large Mailman/pipermail archive. htdig will do the job, but the (htdig) indexes get bloated by the pipermail index pages (which are *very* rarely what you want when searching for something). Indexing can be controlled by meta tags. [See http://info.webcrawler.co m/mak/projects/robots/meta-user.html ]. The pipermail HTML generation is hard coded into the archiver code. As a short term fix, would people be happy with me adding the following meta tags to the pipermail HTML generation:- On top level (ie list of weeks/months etc) and by-date index pages:- <meta name="robots" content="noindex,follow"> [ie do not index the page, follow links down to the articles] On thread/subject/author indexes <meta name="robots" content="noindex,nofollow"> [skip page and linked pages - nofollow is superluous since the indexing robot should realise that the pages are already included but it doesn't hurt much] On article pages <meta name="robots" content="index,nofollow"> [you may disagree with the nofollow, but I think there is no general requirement for the indexer to follow links off the list] Its a hack for now, but will make htdig and other indexing robots behave better. Comments? Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

1 0

Re: [Mailman-Users] Domain allowed to post to a list.
by Evilio del Rio 22 Jun '00

22 Jun '00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 20 Jun 2000, Fergus Donohue wrote: > > Hi, > > Could someone give me some info on the following? I want to allow all > users in a particular mail domain to post to a list - I've searched the > archives and found the answer "add @domain.tld to the field Addresses of > members accepted for posting to this list without implicit approval > requirement." I've tried this and also some regular expression > variations on it and can't get it to work. I also tried the same in > "Addresses always held for Approval" (making the list open and add a > regex to hold anything not in domain @domain.tld). Again no luck! Can > someone give me an example of how they're doing this? > > Thanks, > > Fergus Donohue. > [Note: I have already sent a message similar to this one but I had no reply.] Hi Fergus, Some days ago I was searching for the same feature. AFAIK, this is not possible with the current stable distribution (I haven't tried with the developement one). Now the good news: it is easy to patch Mailman to accept a regular expression as the "posters" settings (addresses allowed to post to a restricted list even if they are not members). I have patched the following file: /home/mailman/Mailman/Handlers/Hold.py (/home/mailman is where I installed it) The result of the "diff" between the patched file vs. the original one are (you can use patch if you want to try): 32a33 > import re 120c121,123 < posters = Utils.List2Dict(map(string.lower, mlist.posters)) - --- > isposter = 0 > for poster in mlist.posters: > isposter = isposter or re.compile(poster, re.I).match(sender) 122c125 < not Utils.FindMatchingAddresses(sender, posters): - --- > not isposter: Then, you must set the "posters" settings to something like that: .+(a)my.domain.com If you do it via Web it's on the "Privacy Options", under the label "Addresses of members accepted for posting (...) in addition to allowing posting by list members" or if you use /home/mailman/bin/config_list, you must set the following in the input config file: posters = ['.+(a)my.doma.in'] I would like to know if this is works for you. I would also like to hear some comments about this patch because I am a begginer in python and I do not know quite well if this is the correct place to implement this feature. I propose that this or a similar feature must be included in the standard Mailman distribution (that's why I send this message to the developers list) HTH, ________________________________________________________________ Evilio Jose del Rio Silvan Institut de Ciencies del Mar edelrio(a)icm.csic.es http://members.es.tripod.de/Evilio/ "He tingut una idea" - Joan Gamper, 27 de novembre de 1899 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.1 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE5UcviBYZlGm2iEEIRAme1AJ47QhAOgebJe+sEItgyYoF4zRDz/wCfZOUt EzKh2jX5gWMcSzNlCzlOqxY= =JUaF -----END PGP SIGNATURE-----

1 0

test
by Dan Mick 21 Jun '00

21 Jun '00

1 0

Another bug in current CVS
by Dan Mick 21 Jun '00

21 Jun '00

scripts/mailowner calls HandlerAPI.DeliverToUser; in doing so, it must set msg.recips, but doesn't. Here's a patch. *** mailowner.orig Wed Jun 21 15:13:54 2000 --- mailowner Wed Jun 21 15:14:19 2000 *************** *** 76,81 **** --- 76,82 ---- msgdata = {'recips' : recips, 'toadmin': 1, } + msg.recips = recips enqueue = HandlerAPI.DeliverToUser(mlist, msg, msgdata) if enqueue: msg.Enqueue(mlist, newdata=msgdata) What's going on? How am I running into all this stuff? I thought others were running the current CVS?

1 0

Errors with current CVS
by Dan Mick 21 Jun '00

21 Jun '00

Also getting errors like this: Jun 21 14:49:09 2000 post(10558): Traceback (innermost last): post(10558): File "/export/home/mailman/scripts/mailowner", line 89, in ? post(10558): main() post(10558): File "/export/home/mailman/scripts/mailowner", line 79, in main post(10558): enqueue = HandlerAPI.DeliverToUser(mlist, msg, msgdata) post(10558): File "/export/home/mailman/Mailman/Handlers/HandlerAPI.py", line 146, in DeliverToUser post(10558): msgdata = {'pipeline' : pipeline, post(10558): AttributeError : recips still trying to track down.

1 0