Mailman 3 November 2000 - Mailman-Developers

Re: [Mailman-Developers] Mailman with sendmail = performance bottleneck
by J C Lawrence 22 Nov '00

22 Nov '00

On Tue, 21 Nov 2000 18:04:07 -0600 Bob Tanner <tanner(a)real-time.com> wrote: > I have to say I am very disappointed at mailman's performance with > sendmail. Especially qrunner and how it works. This is not a sendmail problem. Questionably it is a Mailman problem in that qrunner as currently architected is not terribly scalable. > I am running sendmail with 10 queues, but it looks like mailman > only understands and utilizes 1 queue. It also looks like qrunner > is single threaded AND multiple instances cannot be running at the > same time. True. > This lends itself to a very slow delivery system. Only if your MTA is configured to make it so. Example: Delivering 100 messages (1K members with 10 RCPT_TOs per message) via qrunner to Exim or Postfix takes just under 2 seconds here. Admittedly this is a fast machine. Additionally the local MTA is configured to not do name lookups on local deliveries, and, of course, I'm running a cacheing name server locally. > What sucks is qrunner just tries to deliver each message one at a > time. If message 5 takes forever on the rcpt to: command (for > example), no other messages deliveries are attempted because > qrunner sits on message 5 until it times out. Translation: You are doing name lookups on messages delivered via SMTP from the localhost. There's not much reason for this. Turn it off. > Will mailman support multiple "qfiles" directories in the future? Not for v2.0. After, yes. No designs are finalised. -- J C Lawrence claw(a)kanga.nu ---------(*) : http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

1 0

Re: [Mailman-Developers] Future of pipermail?
by Jeremy Hylton 21 Nov '00

21 Nov '00

>>>>> "BAW" == Barry A Warsaw <barry(a)digicool.com> writes: >>>>> "GE" == Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: GE> What are the current plans about the html archiver in mailman? GE> The major shortcomings of pipermail I see are: | - doesn't decode MIME | - doesn't handle mixed charsets | - no search engine | - somewhat convoluted code. The last is the killer, because it makes the first three that much harder to accomplish. I tried some refactoring for the 2.0 release, but I'm not convinced there is much worth saving. BAW> Anyway, yes, we'd like to rewrite the archiver from the ground BAW> up, but nobody's working on that yet. I suspect either Jeremy BAW> or I will tackle it at some point. It's not near the top of my priorities at the moment, but I would like to work on a new archiver. Perhaps we should start sketching some design issues in Barry's Mailman wiki. I would also like to see separation of the presentation part of the archive from the code, so that it is easier to customize the presentation. Jeremy

4 7

Re: [Mailman-Developers] Re: Future of pipermail?
by Dan Mick 21 Nov '00

21 Nov '00

> Except that WebDAV isn't really new and it is a ratified standard that > basically everyone is adopting! Ah, well, new is in the timespan of the beholder. To me, Web-based anything is "relatively new".... > (but, yes, I should have included the acronym in the first place!) > > The key with WebDAV is that use therein means that you can point WebDAV > enabled Mailman at Zope, IBM's websphere, Apache+mod_dav, or any of the other > WebDAV enabled HTTP servers out there and it should "just work" (assuming they > did the implementation right). There is nothing proprietary about the > solution and choosing it as a foundation for archival/management of > messages/attachments opens doors (instead of closing doors). Yeah, I understand the point. But understand that virtually everyone claims ubiquity long before they actually have it, too... I'll research some more about the web servers I use.

1 0

Re: [Mailman-Developers] Re: Future of pipermail?
by Bill Bumgarner 21 Nov '00

21 Nov '00

Except that WebDAV isn't really new and it is a ratified standard that basically everyone is adopting! (but, yes, I should have included the acronym in the first place!) The key with WebDAV is that use therein means that you can point WebDAV enabled Mailman at Zope, IBM's websphere, Apache+mod_dav, or any of the other WebDAV enabled HTTP servers out there and it should "just work" (assuming they did the implementation right). There is nothing proprietary about the solution and choosing it as a foundation for archival/management of messages/attachments opens doors (instead of closing doors). b.bum From: Dan Mick <Dan.Mick(a)west.sun.com> Date: 2000-11-21 13:00:30 -0800 To: bbum(a)codefab.com Subject: Re: [Mailman-Developers] Re: Future of pipermail? CC: Chuq Von Rospach <chuqui(a)plaidworks.com>, mailman-developers(a)python.org X-Accept-Language: en X-Mailer: Mozilla 4.75 [en] (Win98; U) WebDAV: stands for "Web-based Distributed Authoring and Versioning", which sort of neatly sums up what Bill was saying about its capabilities. (It's new to me, too. There seem to be two new web-database "environments" a week these days.)

1 0

Re: [Mailman-Developers] how to limit posting to a domain?
by J C Lawrence 19 Nov '00

19 Nov '00

On Sun, 19 Nov 2000 11:25:07 -0500 Ken Kyler <ken(a)kyler.com> wrote: > Is it safe to assume the reverse will be true? That whole domains > can be prohibited from posting? You can write mailman filters that will hold such posts for moderation, but Malman does not have the ability to ignore such. That said, this is likely trivial to do at either the MTA level, or as a pre-filter before the Mailman scripts: Just check the envelope and don't apss it through if it doesn't match. -- J C Lawrence claw(a)kanga.nu ---------(*) : http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

1 0

Re: [Mailman-Developers] how to limit posting to a domain?
by J C Lawrence 19 Nov '00

19 Nov '00

On 19 Nov 2000 13:35:19 +0200 Antti Siiskonen <Antti.Siiskonen(a)tut.fi> wrote: > Is there a way to allow posting only for those within a certain > domain? Not currently, and not for v2.0. This is commonly requested, especially by corporates. I'd expect to see it in v2.1. -- J C Lawrence claw(a)kanga.nu ---------(*) : http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

2 1

Re: [Mailman-Users] Bug in 2.0rc2 adding newlist
by Greg Connor 19 Nov '00

19 Nov '00

Phil Barnett wrote: > > Running 2.0rc2. > > I was trying to add a list with bin/newlist and got this: > ... > File "/home/mailman/Mailman/Utils.py", line 568, in mkdir > os.mkdir(dir, mode) > OSError: [Errno 2] No such file or directory: > '/home/mailman/archives/private/bin/newlist.mbox' > I got this too. Looks like a buglet in 2.0rc2. However, I noticed that running bin/newlist foo fails, but just running bin/newlist and then typing the new listname when prompted, works. When you put the name on the command line, it looks like it picks up "bin/newlist" as the name instead. -- Greg Connor <gconnor(a)nekodojo.org>

2 1

how to limit posting to a domain?
by Antti Siiskonen 19 Nov '00

19 Nov '00

Is there a way to allow posting only for those within a certain domain? It seems to me that .. 'Addresses of members accepted for posting to this list without implicit approval requirement.' .. does not take regexps. Is there a way around this or is this feature just missing from Mailman? -- //Antti

1 0

Re: [Mailman-Users] interface mailman list passwords python cgi
by J C Lawrence 18 Nov '00

18 Nov '00

On Sat, 18 Nov 2000 08:53:06 +0000 Andy Heath <andyheath2(a)lineone.net> wrote: > I need to write some cgi applications with python that interface > to mailman 1.0 email id's and passwords - access only to list > members, that sort of thing. Study ~bin/withlist. > I'd appreciate advice on how to go about this. I find some > "config.db" files which obviously is some sort of database > containing the info. Is there some easy way I can get into this > info ? config.db is a python pickle -- essentially a streamed python structure. -- J C Lawrence claw(a)kanga.nu ---------(*) : http://www.kanga.nu/~claw/ --=| A man is as sane as he is dangerous to his environment |=--

1 0

interface mailman list passwords python cgi
by Andy Heath 18 Nov '00

18 Nov '00

I don't know whether I should send this to mailman users or developers so apologies if not appropriate. I need to write some cgi applications with python that interface to mailman 1.0 email id's and passwords - access only to list members, that sort of thing. I'd appreciate advice on how to go about this. I find some "config.db" files which obviously is some sort of database containing the info. Is there some easy way I can get into this info ? Later I will need to move the solution to working with mailman 2.0 All advice welcome Andy -- ------------------------------------------------------------ Andy Heath Home:+44 (0)114 2885738 a.k.heath(a)shu.ac.uk

1 0