Mailman 3 April 2001 - Mailman-Developers

mailman qrunner error
by Kory Wheatley April 10, 2001

April 10, 2001

I'm recieving this message below every single minute and nothing has changed on our system, which of course is not allowing mail to be received to the mailing list. Our system is (RED HAT 7.0 Mailman 2.0.3 and the right Python Version). (I manage over a 100 lists for our universtity so this is very critical). The web server will not bring up any of the mailman pages. I receive the following error "We have found a Bug mailman 2.0.3". I have been running this version of Mailman ever since it was released and have not had one problem. In the error logfile file "qrunner" it says Could not acquire qrunner lock I shutdown sendmail and the web server and restarted both, but still have the problem. I just thought that would be worth trying. I also have no lock files so no processes are hanging. I ran check_perms and all permissions were set correctly There are also no messages in the "qfiles" directory. Any solution would be helpful and I would really appreciate it. Thank you ahead of time. ----- The following addresses had permanent fatal errors ----- "|/home/mailman/mail/wrapper post ccaus" (expanded from: <ccaus(a)mm.isu.edu>) ----- Transcript of session follows ----- Traceback (innermost last): File "/home/mailman/scripts/post", line 33, in ? from Mailman import MailList File "/home/mailman/Mailman/MailList.py", line 30, in ? import socket ImportError: /usr/lib/libcrypto.so.0: undefined symbol: i2d_X509_EXTENSION 554 "|/home/mailman/mail/wrapper post ccaus"... unknown mailer error 1 Reporting-MTA: dns; mm.isu.edu Received-From-MTA: DNS; ux5-250.isu.edu Arrival-Date: Tue, 10 Apr 2001 08:29:14 -0600 Final-Recipient: RFC822; <ccaus(a)mm.isu.edu> X-Actual-Recipient: RFC822; |/home/mailman/mail/wrapper post ccaus(a)mm.isu.edu Action: failed Status: 5.0.0 Last-Attempt-Date: Tue, 10 Apr 2001 08:29:14 -0600 Subject: test 2 Date: Tue, 10 Apr 2001 08:28:55 -0600 From: Kory Wheatley <wheakory(a)isu.edu> To: ccaus(a)mm.isu.edu -- ######################################### -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

2 1

Re: [Mailman-Developers] Re: Patch: Optionally Suppressing List Headers - v2
by Nigel Metheringham April 9, 2001

April 9, 2001

darrell(a)grumblesmurf.net said: > I say make it optional, but strongly discourage turning it off. I come in fairly strongly on the not having this as a standard (or distributed) option - I want people to fix their broken MUAs rather than break MLMs to fit. Those using a sane MTA (OK, I mean exim), can simply set the outgoing transport to strip the headers. Nigel. -- [ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ] [ - Comments in this message are my own and not ITO opinion/policy - ]

1 0

Re: [Mailman-Developers] Remote scripting with XML-RPC
by J C Lawrence April 8, 2001

April 8, 2001

On Sun, 8 Apr 2001 02:00:12 -0400 Jay R Ashworth <jra(a)baylink.com> wrote: > On Sat, Apr 07, 2001 at 08:59:43PM -0400, Eric Kidd wrote: >> An XML-RPC server is basically a glorified CGI script with a >> structured input/output format. Handy, but not really anything >> new. > Oh, yeah. On the server side, I guess that's true. It's the > client side API that makes it cool. While setting up client key authentication under SSL is not hard, its also something not well documented or familiar to (most) SysAdms. Its fiddly, easy to get wrong, and tends to be frustrating before you reach the "Aha!" point, and that doesn't even count the PKI problem. -- 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

Remote scripting with XML-RPC
by Eric Kidd April 8, 2001

April 8, 2001

Hello! I run several Mailman-based mailing lists. And along the way, I've come to really love Mailman. Many thanks to everyone who has worked on it; it's definitely the best list manager I've ever seen. But--for better of for worse--I've decided to tamper with near perfection. :-) Here's what I'm up to: * I want to be able to control Mailman remotely, using scripts. For example, I want to be able to change list preferences, access the approval queue, and generally do anything I could do through the web. * Ideally, I'd like to be able to write these scripts in any popular language. * I don't especially want to fake FORM POSTs and parse the HTML response. This would work, but it's more work than I'd like to get into on the client side. So I've decided to add XML-RPC support to my local copy of Mailman. XML-RPC is a protocol that allows you to make CGI-like "function calls" over HTTP using specially-formatted XML documents. You can read all about XML-RPC here: http://www.xmlrpc.com/ http://www.xmlrpc.com/spec http://www.linuxdoc.org/HOWTO/XML-RPC-HOWTO/index.html The HOWTO contains example clients and servers in many different languages. Fredrik Lundh wrote an excellent implementation of XML-RPC for Python. His code is used in Zope, the RedHat Network and some forthcoming stuff from Eazel: http://www.pythonware.com/products/xmlrpc/index.htm But why use XML-RPC? 1) XML-RPC is really simple. It doesn't get into Schemas, namespaces, alternate encodings, or anything else especially fancy. Fredrik's implemention is less than a 1,000 lines long, which isn't bad for an RPC protocol. I'm not smart enough to cope anything more complicated. :-) 2) XML-RPC is widely supported, with bindings for Python, Perl, Java, C, C++, Tcl, KDE, Zope, AppleScript, Microsoft .NET, Ruby, Rebol, Delphi, and some languages I'd never even heard of. 3) XML-RPC supports complex data-types: arrays, dictionaries, byte arrays, etc. 4) Many XML-RPC implementations support Unicode, including Python, Perl, Java, C and C++. This would allow me to handle international data gracefully. 5) XML-RPC servers can support introspection, allowing a client to discover APIs over the network. This makes it easy to generate documentation, create wrapper classes, and so on, without needing to cope with IDL. For more information on XML-RPC introspection, see: http://xmlrpc-c.sourceforge.net/hacks.php OK, yes, I'm probably crazy. But it seems like a fun hack. So if anybody else is interested in XML-RPC for Mailman, please let me know. And if anybody can tell me why I'm nuts, please let me know that, too. :-) Cheers, Eric -- XML-RPC HOWTO: http://www.linuxdoc.org/HOWTO/XML-RPC-HOWTO/index.html XML-RPC for C and C++: http://xmlrpc-c.sourceforge.net/ xmlrpc-c-devel list: http://xmlrpc-c.sourceforge.net/lists.php

4 10

specific templates
by Adriaan Peeters April 7, 2001

April 7, 2001

Hey all, I sent this to the mailman-users list, but they couldn't give me a complete answer. Does anyone know how to change the automated subcribe confirmation email ? It is possible to add a text via the administrative interface, but is't not possible to change the mail completely. I would like to change the welcome e-mail completely, perhaps even make html mails from it. I tried to copy templates/subscribeack.txt to lists/listname/subscribeack.txt and change something in that file, but it didn't work :( I think it's not a very big deal to change the code to check first if a specific subscribeack.txt exists, then include it, and if not, include the default one. But unfortunately I don't know enough Python to submit a patch :( Is there a way to accomplish this at this moment, or are there any patches out there ? Regards and thanks, Adriaan Peeters

4 5

Re: Patch: Optionally Suppressing List Headers - v2
by ps＠psncc.at April 6, 2001

April 6, 2001

Hi everybody, Having read the replies for my previous patch so far, I have produced version 2 of it. I would also like to note that the functionality applies to both regular and digest messages anyway, so one of the comments from my last posts should be treated as nonsense. Due to this, I have now moved the configurabale option to the "general" options page, and I have properly (?) changed the versions.py file to upgrade mailing lists for the new attribute on-the-fly (I didn't know of the functionality, although I thought it would be hidden somewhere - Barrys mail has pointed me in the right direction). However, this required to increase the DATA_FILE_VERSION in Mailman/Version.py as well (something I was not THAT comfortable with). It also includes a configurable default value for the new attribute as well. I would really like to hear comments on the proposed functionality as well as on the patch's quality (which [indirectly, though] seems to have been the focus of most, if not all, of the replies to my last posting). peter Here is the patch: diff -ur mailman-2.0.2-org/Mailman/Defaults.py.in mailman-2.0.2-patched/Mailman/Defaults.py.in --- mailman-2.0.2-org/Mailman/Defaults.py.in Thu Nov 16 05:23:52 2000 +++ mailman-2.0.2-patched/Mailman/Defaults.py.in Thu Apr 5 07:02:20 2001 @@ -366,6 +366,11 @@ 'subject', 'to', 'cc', 'reply-to', 'organization'] +##### +# Add list header, ie. List-Help, etc. to outgoing non-digest +# messages +##### +DEFAULT_ADDLISTINFO = 1 ##### diff -ur mailman-2.0.2-org/Mailman/Handlers/CookHeaders.py mailman-2.0.2-patched/Mailman/Handlers/CookHeaders.py --- mailman-2.0.2-org/Mailman/Handlers/CookHeaders.py Thu Nov 16 05:35:09 2000 +++ mailman-2.0.2-patched/Mailman/Handlers/CookHeaders.py Wed Apr 4 23:13:39 2001 @@ -124,14 +124,15 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded. The adding of 2 is for the colon-space # separator. - if len(h) + 2 + len(v) > 78: - v = string.join(string.split(v, ', '), ',\n\t') - msg[h] = v + if mlist.addlistinfo: + if len(h) + 2 + len(v) > 78: + v = string.join(string.split(v, ', '), ',\n\t') + msg[h] = v # # Always delete List-Archive header, but only add it back if the list is # actually archiving del msg['List-Archive'] - if mlist.archive: + if mlist.archive and mlist.addlistinfo: value = '<%s>' % urlparse.urljoin(mlist.web_page_url, mlist.GetBaseArchiveURL()) msg['List-Archive'] = value diff -ur mailman-2.0.2-org/Mailman/MailList.py mailman-2.0.2-patched/Mailman/MailList.py --- mailman-2.0.2-org/Mailman/MailList.py Thu Nov 16 05:33:27 2000 +++ mailman-2.0.2-patched/Mailman/MailList.py Thu Apr 5 07:31:07 2001 @@ -345,6 +345,8 @@ self.msg_header = mm_cfg.DEFAULT_MSG_HEADER self.msg_footer = mm_cfg.DEFAULT_MSG_FOOTER + self.addlistinfo = mm_cfg.DEFAULT_ADDLISTINFO + def GetConfigInfo(self): config_info = {} config_info['digest'] = Digester.GetConfigInfo(self) @@ -544,6 +546,10 @@ ('max_message_size', mm_cfg.Number, 7, 0, 'Maximum length in Kb of a message body. Use 0 for no limit.'), + + ('addlistinfo', mm_cfg.Toggle, ('No', 'Yes'), 1, + 'Add mailing list information headers to outgoing messages ' + '(regular AND digests)?'), ('host_name', mm_cfg.Host, WIDTH, 0, 'Host name this list prefers.', diff -ur mailman-2.0.2-org/Mailman/Version.py mailman-2.0.2-patched/Mailman/Version.py --- mailman-2.0.2-org/Mailman/Version.py Sat Mar 3 07:19:15 2001 +++ mailman-2.0.2-patched/Mailman/Version.py Thu Apr 5 07:39:08 2001 @@ -36,7 +36,7 @@ (REL_LEVEL << 4) | (REL_SERIAL << 0)) # config.db schema version number -DATA_FILE_VERSION = 21 +DATA_FILE_VERSION = 22 # qfile/*.db schema version number QFILE_SCHEMA_VERSION = 2 diff -ur mailman-2.0.2-org/Mailman/versions.py mailman-2.0.2-patched/Mailman/versions.py --- mailman-2.0.2-org/Mailman/versions.py Wed Jun 14 07:09:58 2000 +++ mailman-2.0.2-patched/Mailman/versions.py Thu Apr 5 06:59:08 2001 @@ -189,6 +189,7 @@ add_only_if_missing('postings_responses', {}, l) add_only_if_missing('admin_responses', {}, l) add_only_if_missing('reply_goes_to_list', '', l) + add_only_if_missing('addlistinfo', mm_cfg.DEFAULT_ADDLISTINFO, l)

5 4

Re: [Mailman-Developers] Re: Patch: Optionally Suppressing List Headers - v2
by Darrell Fuhriman April 6, 2001

April 6, 2001

chuq von rospach <chuqui(a)plaidworks.com> writes: > These are standards. I think any patch to remove them ought to be > rejected, the documentation ought to explicitly discourge people from > removing them, and the source code ought to have a note in it > recommending against removing them. We want to encourage adoption of > the standard, not removal of the header lines. I agree with everything but the first clause (and I was the one that wrote the patch to implement it.) The RFC specifically says that the headers are optional (paragraph 2 section 1 of the RFC.), and I personally believe in giving people options where available. Just because it's probably a bad idea doesn't mean we should be restrictive on things are not mandated. This is already what's done with the optional Reply-To header, for example. If I wanted software that told me that I had to do it the software's (or the software author's) way and no other, I would just use ezmlm. I don't like software that second guesses my decisions, and I see no compelling reason to be second guessing others' decisions here. I say make it optional, but strongly discourage turning it off. Darrell

1 0

Cross-posting?
by Dale Newfield April 6, 2001

April 6, 2001

I've installed Mailman at a site that has quite a number of mailing lists. we're trying to figure out a more disjoint re-design of the lists to reduce the problem of cross-posting, but I thought I'd at least ask if anyone's attempted to address this from w/in mailman. If there were a database of message ids, along with information listing which mailing lists those've gone to, wouldn't it be possible to only send messages once to people subscribed to both lists? It's a great piece of software, BTW, and a hack I recently installed to unify passwords across lists (so it looks like a user has only one password instead of one per list) helps out, too. -Dale Newfield webmaster(a)wunderland.com

1 0

WWW.LIST.ORG
by Christine Hall April 6, 2001

April 6, 2001

1 0

Patch: Optionally Suppressing List Headers
by ps＠psncc.at April 5, 2001

April 5, 2001

Hi everybody, I just produced the patch included below. It allows to configure not to add the List-* header lines to outgoing non-digest messages. I needed this to hide the HTTP URLs for the webinterface, as Mailman is used "just" as the mailing list backend and the webinterface is to be used by the administrators only. A similar thing should probably be done for the digest case. The patch should apply cleanly to 2.0.2 and 2.0.3. Note that the patch adds a new attribute to the MailList object. This usually breaks existing mailing lists. You can fix the situation by creating a file <tempfile> with just the line mlist.addlistinfo = 1 and using <mailman-path>/bin/config_list -i <tempfile> <listname> (at least this worked for me) NOTE 1: Use this patch at your own risk. NOTE 2: This is my first Mailman patch (and the first time I ever touched python) so I may have overlooked some details. Does anybody like this feature? peter diff -ur mailman-2.0.2-org/Mailman/Handlers/CookHeaders.py mailman-2.0.2-patched/Mailman/Handlers/CookHeaders.py --- mailman-2.0.2-org/Mailman/Handlers/CookHeaders.py Thu Nov 16 05:35:09 2000 +++ mailman-2.0.2-patched/Mailman/Handlers/CookHeaders.py Wed Apr 4 22:19:24 2001 @@ -124,14 +124,15 @@ # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded. The adding of 2 is for the colon-space # separator. - if len(h) + 2 + len(v) > 78: - v = string.join(string.split(v, ', '), ',\n\t') - msg[h] = v + if mlist.addlistinfo: + if len(h) + 2 + len(v) > 78: + v = string.join(string.split(v, ', '), ',\n\t') + msg[h] = v # # Always delete List-Archive header, but only add it back if the list is # actually archiving del msg['List-Archive'] - if mlist.archive: + if mlist.archive and mlist.addlistinfo: value = '<%s>' % urlparse.urljoin(mlist.web_page_url, mlist.GetBaseArchiveURL()) msg['List-Archive'] = value diff -ur mailman-2.0.2-org/Mailman/MailList.py mailman-2.0.2-patched/Mailman/MailList.py --- mailman-2.0.2-org/Mailman/MailList.py Thu Nov 16 05:33:27 2000 +++ mailman-2.0.2-patched/Mailman/MailList.py Wed Apr 4 21:53:54 2001 @@ -345,6 +345,8 @@ self.msg_header = mm_cfg.DEFAULT_MSG_HEADER self.msg_footer = mm_cfg.DEFAULT_MSG_FOOTER + self.addlistinfo = 1 + def GetConfigInfo(self): config_info = {} config_info['digest'] = Digester.GetConfigInfo(self) @@ -770,6 +772,9 @@ "Text appended to the bottom of every immediately-delivery" " message. " + Utils.maketext('headfoot.html', raw=1)), + + ('addlistinfo', mm_cfg.Toggle, ('No', 'Yes'), 1, + 'Add mailing list information headers to outgoing messages?'), ] config_info['bounce'] = Bouncer.GetConfigInfo(self)

3 11