Mailman 3 April 2002 - Mailman-Developers

Re: [Mailman-Developers] pipermail replacement
by J C Lawrence 11 Apr '02

11 Apr '02

On Mon, 8 Apr 2002 03:33:53 +0000 Eric Hanson <eric(a)aquameta.com> wrote: > There have been several mentions of the need for a mailing list with a > web interface, something that allows mailing list functionality and a > web interface that allows posting, user accounts, threading etc. I've > been thinking about such a thing using the XML server 4suite server > (4suite.org) and mailman, essentially replacing pipermail. You might like to look at what I've done under MHonArc and PHP here at Kanga.Nu. I specifically don't handle accounts, but I do handle posting, MIME, and the rest. http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.004.htp -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Ok, this is weird...
by Ron Jarrell 11 Apr '02

11 Apr '02

Mar 26 21:56:41 2002 (558) Uncaught runner exception: Continuation line seen before first header Mar 26 21:56:41 2002 (558) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 111, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 134, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/Tagger.py", line 47, in process matchlines.extend(scanbody(msg, mlist.topics_bodylines_limit)) File "/home/mailman/Mailman/Handlers/Tagger.py", line 101, in scanbody msg = email.message_from_string(EMPTYSTRING.join(lines)) File "/home/mailman/pythonlib/email/__init__.py", line 36, in message_from_string return _Parser(_class).parsestr(s) File "/home/mailman/pythonlib/email/Parser.py", line 45, in parsestr return self.parse(StringIO(text)) File "/home/mailman/pythonlib/email/Parser.py", line 40, in parse self._parseheaders(root, fp) File "/home/mailman/pythonlib/email/Parser.py", line 69, in _parseheaders raise Errors.HeaderParseError( HeaderParseError: Continuation line seen before first header Now, I'd believe there was something wrong with the header (although mm ought to catch this more elegantly), except the user had just sent it to list1@myserver,list2@myserver, and it made it to *list2*, it just won't go through to list1. I unshunted it, and it failed again the same way. So how in heck did it get to list2? Barry, I saved the copy I got (I'm on both lists), and the shunt files, if you want them; there's nothing private in the message.

2 14

New bug...
by Ron Jarrell 11 Apr '02

11 Apr '02

Ok, here's the top of a message I got yesterday evening. Please note, this is *not* the header. This is everything from the first blank line in the note after the header, until the next blank line in the note. <5.1.0.14.2.20020410133754.02508db0(a)lennier.cc.vt.edu><1877.131.187.110.224.1018464240.squirrel(a)www.dnaco.net> <3CB48A42.2B3B5698(a)elfie.org> Subject: Re: [VTSFFC-L] What the bands want... Date: Wed, 10 Apr 2002 15:11:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-BeenThere: vtsffc-l(a)lists.vtsffc.org X-Mailman-Version: 2.1b1 Precedence: bulk Reply-To: vtsffc-l(a)lists.vtsffc.org List-Id: VTSFFC Mailing List <vtsffc-l.lists.vtsffc.org> List-Post: <mailto:vtsffc-l@lists.vtsffc.org> List-Subscribe: <http://lists.vtsffc.org/mailman/listinfo/vtsffc-l>, <mailto:vtsffc-l-request@lists.vtsffc.org?subject=subscribe> List-Unsubscribe: <http://lists.vtsffc.org/mailman/listinfo/vtsffc-l>, <mailto:vtsffc-l-request@lists.vtsffc.org?subject=unsubscribe> List-Archive: http://lists.vtsffc.org/mailman/private/vtsffc-l/ List-Help: <mailto:vtsffc-l-request@lists.vtsffc.org?subject=help> Sender: vtsffc-l-bounces+jarrell=vt.edu(a)lists.vtsffc.org Errors-To: vtsffc-l-bounces+jarrell=vt.edu(a)lists.vtsffc.org Looks like a header, huh? But mailman put it in the *note* body. The header itself has *no* mailman headers in it. Also no subject in the real header, although it did have a *second* date and a from. Note the first couple of lines - I suspect that this might be related to the continuation header bug I've been running into - although topics are off now, and this is a different symptoms.. Before they just wouldn't post until I turned topics back off, but looked fine.

1 0

Buglet in list_members (and others?)
by Chuq Von Rospach 10 Apr '02

10 Apr '02

Oh, this is so obscure I'm embarrassed. % list_members typo_a_list_name > foo % % cat foo No such list "typo_a_list_name" List_members returns errors to STDOUT, not STDERR. -- Chuq Von Rospach, Architech chuqui(a)plaidworks.com -- http://www.chuqui.com/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet.

2 1

os.unlink error with mm 2.0.9
by Marc MERLIN 10 Apr '02

10 Apr '02

This happened twice on sf.net about 12H after the upgrade to 2.0.9 Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): Traceback (most recent call las t): Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): File "/var/local/mailman/cron /qrunner", line 282, in ? Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): kids = main(lock) Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): File "/var/local/mailman/cron /qrunner", line 204, in main Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): os.unlink(root+'.msg') Apr 09 02:28:06 2002 usw-sf-list1 qrunner(9416): OSError : [Errno 2] No such fi le or directory: '/var/local/mailman/qfiles/c0cd07c04a0599fb40d2251f364aa2d187fc af43.msg.msg' Note the ".msg.msg" (I am not claiming it's new to 2.0.9, I have to admit that my old error log file was getting too big for me to read it) There are also fun ones like: Apr 09 08:48:47 2002 usw-sf-list1 (517) Exception while calculating message head er: unsupported format character '^M' (0xd) at index 87 or Apr 09 06:35:04 2002 usw-sf-list1 (17060) NNTP gateway improperly configured: no newsgroup, no NNTP host (there aren't new mind you, and I think Barry said that mm2.1 was better about telling you which list these errors happened in) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 7

more deprecation
by Ron Jarrell 10 Apr '02

10 Apr '02

Apr 10 11:10:32 2002 admin(5085): /home/mailman/Mailman/MailList.py:839: Depreca tionWarning: Use email.Utils.formataddr() instead {"listname" : self.real_name, Apr 10 11:13:46 2002 qrunner(2873): /home/mailman/Mailman/Handlers/CookHeaders.p y:109: DeprecationWarning: Use email.Utils.formataddr() instead [email.Utils.dump_address_pair(pair) for pair in d.values()])

1 0

Blocking few features for listadmin
by sunny 10 Apr '02

10 Apr '02

I am running mailman ver 2.08 on Solaris 8 with multiple listadmins the problem some listadmin's are changing The list admin's email address and also "Maximum length in Kb of a message body" to 0 which is choking the servers. Can i customize the mailman so that these fileds will not be available for the list admin to change. Regards DK __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/

1 1

Pre-list filtering?
by Bill Bradford 10 Apr '02

10 Apr '02

Any suggestions on filtering messages *before* they get to the list? I've got a list that doesent allow directly replies back to the list, so I want to block all messages with a subject starting "Re:", "RE:", etc. Getting real tired of moderating/deleting 40-50 posts/day. 8-( The only way I can think to do this would be by changing the list submission alias to point to a "fake user", who would have a .procmailrc to dump the appropriate messages, then re-inject the messages back into mailman. However, this seems very hackish. Suggestions? Bill -- Bill Bradford mrbill(a)mrbill.net Austin, TX

1 0

todigest.py
by Ron Jarrell 10 Apr '02

10 Apr '02

Interesting... Started up the latest cvs before going home last night (yes, I let it run for a while before abandoning it :-)) When I came home my terminal window had a stream of these on it.. Looks like python was dropping the errors to stdout. /home/mailman/Mailman/Handlers/ToDigest.py:172: DeprecationWarning: add_payload() is deprecated, use attach() instead. mimemsg.add_payload(masthead) /home/mailman/Mailman/Handlers/ToDigest.py:262: DeprecationWarning: add_payload() is deprecated, use attach() instead. mimemsg.add_payload(tocpart) /home/mailman/Mailman/Handlers/ToDigest.py:272: DeprecationWarning: add_payload() is deprecated, use attach() instead. mimemsg.add_payload(mimedigest) /home/mailman/Mailman/Handlers/ToDigest.py:276: DeprecationWarning: add_payload() is deprecated, use attach() instead. mimedigest.add_payload(msg) /home/mailman/Mailman/Handlers/ToDigest.py:291: DeprecationWarning: add_payload() is deprecated, use attach() instead. mimemsg.add_payload(footer) /home/mailman/Mailman/Handlers/ToDigest.py:339: DeprecationWarning: add_payload() is deprecated, use attach() instead. rfc1153msg.add_payload(plainmsg.getvalue())

2 1

2.1b1 bug still in topic processor...
by Ron Jarrell 09 Apr '02

09 Apr '02

Barry, the topic processor bug is still there... I did some more testing with the latest (ok, last nights) cvs. Turned topics back on one the list they were on before (the one I sent you the shunt pickles from) and let it run all night. Sure enough, caught a message that was otherwise fine, but died. Turned topics back off and deleted the topics I had, and unshunted it, and it went back in fine. return self.parse(StringIO(text)) File "/home/mailman/pythonlib/email/Parser.py", line 40, in parse self._parseheaders(root, fp) File "/home/mailman/pythonlib/email/Parser.py", line 69, in _parseheaders raise Errors.HeaderParseError( HeaderParseError: Continuation line seen before first header

1 0