Mailman 3 July 2004 - Mailman-Developers

Re: [Mailman-Developers] [Greg Stark <gsstark@mit.edu>] Re:Bounceremoval parameters default values
by J C Lawrence 11 Jul '04

11 Jul '04

On Fri, 2 Jul 2004 10:21:26 -0700 somuchfun <somuchfun(a)atlantismail.com> wrote: > This is not the point here, J.C. Actually, it is very precisely the point. As this message is repetition so I'll likely be ending my participation in this thread with this message. > The important point is the fact that mailman did introduce a new way > of handling bounces without a way to opt-out of this new way. Yup. > Normally every software package that introduces a new way of doing a > certain task (opposed to a complete new functionality) there is an > option to opt-out and continue "the old way" until all proper changes > have been done. I'm sure that Barry et al would have welcomed your patches. I'm also sure that Barry et al would have welcomed funding by you or cPanel to do the appropriate work. Equally I'm sure that Barry et al would have welcomed an email from cPanel mentioning that they don't support plus addressing and could the Mailman README be updated with a more strongly phrased warning? But, none of these things happened. > Take cPanel for example, they have still not gotten around to make the > proper adjustments to their highly complex environment and they are > used hundreds of thousands of times around the world by web hosting > companies. Yup. > Right now people are unsubscribed because of this all over the place > for no apparent reason (from the view of the user). The only way to > not end up in trouble in this environment is to turn off bounce > handling completely in mailman 2.1.5... Or to have not installed/upgraded_to 2.1.5 in the first place. Nobody pointed a gun at their heads. These are free choices, freely made, freely paid for. > ... So looking at this, do you still think it was wise to introduce > VERP bounce probes by default and by force with no choice? Frankly I just don't think it is very important. I see it as a nice-to-have on all scales: "Hey, it would have been nice if the release docs said something a bit more blatant about requiring plus addressing supports in the local MTA. You know, some CAPS or something." "Yeah, you're right that would have been better to put in CAPs or something. But we didn't hide it, it was in the docs." "Oh yeah." "Wanna go get a beer?" "Sure!" -- 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

Major Bug (stop all lists) in mailman 2.0.14
by Silviu Marin-Caea 09 Jul '04

09 Jul '04

Upon receiving a message like bellow (and similar messages) that are virus social engineering without the viral payload, mailman, specifically qrunner, chokes for good, and does not deliver any message that follows, on any list. There's the relevant excerpt from error log bellow. I still have the .msg and .db files that, if moved to /var/lib/mailman/qfiles, can reproduce the error, always. They're here: ftp://ftp.genesys.ro/upload/mailman-error System is SUSE Openexchange Server 8, but it happened on SUSE LINUX 8.0 Professional too, which used mailman 2.0.x. From zoltank67(a)hotmail.com Thu Jun 24 22:42:00 2004 Return-Path: <zoltank67(a)hotmail.com> Delivered-To: networking-request(a)genesys.ro Received: from mail.genesys.ro (localhost [127.0.0.1]) by mail.genesys.ro (Postfix) with ESMTP id 373B96BA85 for <networking-request(a)genesys.ro>; Thu, 24 Jun 2004 22:42:00 +0300 (EEST) Received: by mail.genesys.ro (Postfix, from userid 65534) id 24F906E21E; Thu, 24 Jun 2004 22:42:00 +0300 (EEST) Received: from hotmail.com (bay8-f8.bay8.hotmail.com [64.4.27.8]) by mail.genesys.ro (Postfix) with ESMTP id D1D926E21A for <networking-request(a)genesys.ro>; Thu, 24 Jun 2004 22:41:58 +0300 (EEST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 24 Jun 2004 12:41:55 -0700 Received: from 80.97.222.9 by by8fd.bay8.hotmail.msn.com with HTTP; Thu, 24 Jun 2004 19:41:55 GMT X-Originating-IP: [80.97.222.9] X-Originating-Email: [zoltank67(a)hotmail.com] X-Sender: zoltank67(a)hotmail.com From: "Keresztes Zoltan" <zoltank67(a)hotmail.com> To: networking-request(a)genesys.ro Date: Thu, 24 Jun 2004 22:41:55 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: <BAY8-F8Y9IuXZ2y2Fko000034a2(a)hotmail.com> X-OriginalArrivalTime: 24 Jun 2004 19:41:55.0660 (UTC) FILETIME=[4E4338C0:01C45A23] X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on mail.genesys.ro X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=BAYES_01,FROM_ENDS_IN_NUMS autolearn=no version=2.63 X-BitDefender-Scanner: Clean, Agent: BitDefender POSTFIX 1.5.7 on mail confirm 641541 _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus Jun 25 13:18:55 2004 qrunner(9964): Traceback (most recent call last): Jun 25 13:18:55 2004 qrunner(9964): File "/usr/lib/mailman/cron/qrunner", line 283, in ? Jun 25 13:18:55 2004 qrunner(9964): kids = main(lock) Jun 25 13:18:55 2004 qrunner(9964): File "/usr/lib/mailman/cron/qrunner", line 253, in main Jun 25 13:18:55 2004 qrunner(9964): keepqueued = dispose_message(mlist, msg , msgdata) Jun 25 13:18:55 2004 qrunner(9964): File "/usr/lib/mailman/cron/qrunner", line 157, in dispose_message Jun 25 13:18:55 2004 qrunner(9964): mlist.ParseMailCommands(msg) Jun 25 13:18:55 2004 qrunner(9964): File "/usr/lib/mailman/Mailman/MailCommand Handler.py", line 163, in ParseMailCommands Jun 25 13:18:55 2004 qrunner(9964): splitsubj = string.split(subject) Jun 25 13:18:55 2004 qrunner(9964): File "/usr/lib/python2.2/string.py", line 117, in split Jun 25 13:18:55 2004 qrunner(9964): return s.split(sep, maxsplit) Jun 25 13:18:55 2004 qrunner(9964): AttributeError : 'NoneType' object has no a ttribute 'split'

1 0

Bug error in Send filter option
by Kory Wheatley 08 Jul '04

08 Jul '04

I recieve this below error when I setup the non-member messages to be discarded when no action is taken in the send filters option. Any Solution to this? Bug in Mailman version 2.1.5 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 (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/admin.py", line 175, in main change_options(mlist, category, subcat, cgidata, doc) File "/home/mailman/Mailman/Cgi/admin.py", line 1296, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/home/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/home/mailman/Mailman/Gui/GUIBase.py", line 158, in handleForm doc.addError( File "/home/mailman/Mailman/htmlformat.py", line 340, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ------------------------------------------------------------------------ Python information: Variable Value sys.version 2.1.3 (#1, Apr 9 2002, 22:27:11) [GCC 2.96 20000731 (Red Hat Linux 7.1 2.96-98)] sys.executable /usr/local/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 ------------------------------------------------------------------------ Environment variables: Variable Value DOCUMENT_ROOT /var/www/mailman SERVER_ADDR 134.50.250.14 HTTP_ACCEPT_ENCODING gzip,deflate CONTENT_LENGTH 10956 CONTENT_TYPE application/x-www-form-urlencoded PATH_TRANSLATED /var/www/mailman/irh/privacy/sender REMOTE_ADDR 134.50.249.22 SERVER_SOFTWARE Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_ssl/2.8.12 OpenSSL/0.9.6b DAV/1.0.3 PHP/4.1.2 mod_perl/1.26 GATEWAY_INTERFACE CGI/1.1 HTTP_COOKIE mailman+admin=280200000069c256ed40732800000033303035313436383336313330616362353433663334386633353436343835626139343036666136; childts+admin=280200000069f756ed40732800000063653036323334393331303563313233646639616231336137626234373830306134663937616466; irh+admin=280200000069d072ed40732800000066616661663263616337383662653834323236333066393861346135613833383637616233663930 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 REMOTE_PORT 1806 SERVER_PORT 80 HTTP_CONNECTION keep-alive HTTP_USER_AGENT Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.8 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 REQUEST_URI /mailman/admin/irh/privacy/sender QUERY_STRING SERVER_PROTOCOL HTTP/1.1 HTTP_KEEP_ALIVE 300 HTTP_HOST mm.isu.edu REQUEST_METHOD POST SERVER_SIGNATURE Apache/1.3.27 Server at mm.isu.edu Port 80 SCRIPT_NAME /mailman/admin SERVER_ADMIN wheakory(a)isu.edu SCRIPT_FILENAME /home/mailman/cgi-bin/admin PYTHONPATH /home/mailman PATH_INFO /irh/privacy/sender HTTP_REFERER http://mm.isu.edu/mailman/admin/irh/privacy/sender SERVER_NAME mm.isu.edu -- Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him.

1 0

skinning mailman pages...
by Chuq Von Rospach 06 Jul '04

06 Jul '04

someone please tell me I'm not crazy. I remember a set of patches that could be added to mailman that allowed defining header/footer for mailman without having to hack everything -- and now, I can't find them. Can someone point them out to me? Or suggest ways to add a site look/feel to mailman without hacking everything? I've been using mod_layout to do this, but I'm looking for other options for future uses...

2 1

Various strange permission errors
by Jim Ramsay 06 Jul '04

06 Jul '04

I'm running Mailman 2.1.5, as installed by the Gentoo ebuild, and have a couple questions about some strange permission errors I'm getting: 1 - For some reason the permissions on the /usr/local/mailman/archives/private is drwxr-xr-x, but the /usr/local/mailman/cgi-bin/create is only rwxr-sr-x, so the 'create' web script can't ever create anything in that directory. So, should the permissions on the archive directory be 775, or should the 'create' script be suid? 2 - It looks like nothing poperly sets the permissions on data/aliases(.db) or data/virtual-mailman(.db). I did this by hand, but maybe someone else should do that. 3 - After I 'fixed' the first error here by temporarily setting the permissions on the 'create' script to suid, and after fixing the permissions on the postfix alias files by hand, and creating a list, check_perms says that there is a problem - the archive directories should be mode 02775. Why aren't they? None of these are big problems, and I have work-arounds for all, but they are weird. That is all. -- Jim Ramsay "Me fail English? That's unpossible!"

1 0

Using bouncer engine as standalone
by om＠onlinehome.de 06 Jul '04

06 Jul '04

Hi there, Mailman has rather impressive bouncer code part and I would like to use it for my CRM process to identify bounces. Can one run the bouncer code as a standalone engine, and what would be the right way to do it? Is it a wise thing to do? Basically there is a file with all email bounce messages from my customers and as the result I would need a list of all bounced emails addresses. Bouncer.py needs a mailing list as one of its parameteres. Is it trivial to change the code so that it functions just as a filter for a single file? I do not know that much of Python, so it would take too much time for me to see if it doable in a reasonable time. Should you suggest it is doable, I would spend some time playing around with Python and Mailman code. Best regards, Egor

2 1

Re: Re: [Mailman-Developers] Using bouncer engine as standalone
by om＠onlinehome.de 06 Jul '04

06 Jul '04

Bryan Bradsby <Bryan.Bradsby(a)capnet.state.tx.us> schrieb am 06.07.2004, 16:39:13: > Challenge Response sux. > > Friends don't let friends do C/R. > > Just say no to C/R. > > Just my opinion. > > Thank you, > -bryan bradsby > ======================================================================== > > On Tue, 6 Jul 2004 om(a)onlinehome.de wrote: > > > > > Hi there, > > > > Mailman has rather impressive bouncer code part and I would like to use > > it for my CRM process to identify bounces. ... Thank you for your prompt reaction, Bryan. Could you please elaborate a little bit more on how Challenge Response is connected with using Mailman bouncer code to identify bounces in my inbox? Rgrds, Egor

1 0

JTABLE + JDBC
by Sreenivas Ganji 05 Jul '04

05 Jul '04

Hi all, I have a problem in JTable. I wrote a simple application which contains JTextArea and JButtons and JTable. It is workling like.... We can issue a sql query in TextArea, once click on fetch button, it will displaying records in Jtable, but if records are more, I implemented a button called Next(JButton). My requirement is if records are more than 25, then it should be display only first 25 records, if click on next button, we can get next 25 records, it should be goes until all records (each time only 25 records). Please let me know, how to fetch and display only few records in JTable from whole recordset. Please............., if any body knows & have ideas, please share with me. Regards, Srini.

2 1

why treat action: delayed in DSN as an unrecognized bounce?
by Brian J. Murrell 04 Jul '04

04 Jul '04

I am using MM 2.1.4 and have been getting some "Uncaught bounce notification" messages from it. The MTA is Postfix (a 2.1.0 snapshot as of 20040209) and it is the local MTA (i.e. on the same machine and in the same administrative domain as MM) that is generating the bounces, complete with DSNs. The issue seems to be that the Action: in the DSN is "delayed". These delivery notifications are the "we have been trying for 4 hours and have not been successful but will try for 5 days before giving up" kind of notifications. Looking into the DSN handling code for MM, I see that in DSN.py, the check() method returns "Stop" if action == 'delayed'. The caller (BouncerAPI.py:ScanMessages()) then returns an empty list if the callee returns Stop, which triggers the "unknown bounce" processing. Why is delayed not handled more gracefully than treating it as an unknown bounce type? Or am I totally missing something here? Thanx, b.

2 6

Re: [Mailman-Developers] [Greg Stark <gsstark@mit.edu>] Re:Bounceremoval parameters default values
by Bob Puff＠NLE 02 Jul '04

02 Jul '04

Unless I am missing something here, why don't you just enable verp in your MTA? Postfix, Sendmail, Exim, and Qmail all support it. What's the big deal? Bob Somuchfun wrote: > This is not the point here, J.C. > The important point is the fact that mailman did introduce a new way of > handling bounces without a way to opt-out of this new way. Normally every > software package that introduces a new way of doing a certain task (opposed > to a complete new functionality) there is an option to opt-out and continue > "the old way" until all proper changes have been done. > Take cPanel for example, they have still not gotten around to make the > proper adjustments to their highly complex environment and they are used > hundreds of thousands of times around the world by web hosting companies. > Right now people are unsubscribed because of this all over the place for no > apparent reason (from the view of the user). The only way to not end up in > trouble in this environment is to turn off bounce handling completely in > mailman 2.1.5 > So looking at this, do you still think it was wise to introduce VERP bounce > probes by default and by force with no choice? > > ---------------------------------------- > MANA TANGATA > > >>-----Original Message----- >>From: J C Lawrence [mailto:claw@kanga.nu] >>Sent: Thursday, July 01, 2004 5:58 PM >>To: John W. Baxter >>Cc: mailman-developers(a)python.org >>Subject: Re: [Mailman-Developers] [Greg Stark >><gsstark(a)mit.edu>] Re:Bounceremoval parameters default values >> >>On Thu, 01 Jul 2004 17:48:21 -0700 >>John W Baxter <jwblist(a)olympus.net> wrote: >> >>>On 7/1/2004 9:57, "J C Lawrence" <claw(a)kanga.nu> wrote: >> >>>>They can of course always gain that same time and more by >> >>simply not >> >>>>upgrading. >> >>>Which is decidedly NOT encouraged by this snippet from Barry's 2.1.5 >>>announcement: >> >>> This version also contains a fix for an exploit that >> >>could allow 3rd >> >>> parties to retrieve member passwords. It is thus highly >> >>recommended >> >>> that all existing sites upgrade to the latest version. >> >>Yup, of such hard choices are upgrades made. >> >>Of course Mailman passwords are also not the most significant >>things in >>the computing universe. >> >>-- >>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. >> >>_______________________________________________ >>Mailman-Developers mailing list >>Mailman-Developers(a)python.org >>http://mail.python.org/mailman/listinfo/mailman-developers >>Unsubscribe: >>http://mail.python.org/mailman/options/mailman-developers/somu >>chfun%40atlantismail.com >> > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/bob%40nleaudio.com >

2 2