From barry at python.org Sat Feb 1 12:10:13 2003 From: barry at python.org (Barry A. Warsaw) Date: Sat Feb 1 12:10:43 2003 Subject: [Mailman-Developers] PyCon, Sprints, and IRC (was Re: [Mailman-Users] IRC) References: <3E3BC42E.3070404@attbi.com> Message-ID: <15931.65397.179142.150480@gargle.gargle.HOWL> >>>>> "JL" == Jim LaSalle writes: JL> Is there an IRC for users of this mail list? irc.freenode.net #mailman But I haven't had much time to hang out there lately. :( BTW, is anybody planning on coming to PyCon? http://www.python.org/pycon/ If there is enough interest and participation, I'd be willing to chair a Mailman sprint. I can think of several topics that might be useful to sprint on: - documentation - bug fix day - improving the archiver (adding searching, or webmail) - Mailman 3.0 sprints (member mgt, backing database) - improve admindb interface I'm of course open to other suggestions. Anybody interested and planning on attending? -Barry From jarrell at vt.edu Sat Feb 1 15:01:48 2003 From: jarrell at vt.edu (Ron Jarrell) Date: Sat Feb 1 15:07:12 2003 Subject: [Mailman-Developers] I hate the 1st of the month. Message-ID: <5.1.0.14.2.20030201145755.064badb0@lennier.cc.vt.edu> Just venting. I'm in my monthly "God, I *hate* the password reminder scheme" phase. I get over it in a few days. But for the next 48 hours or so I'm dealing with a stream of people who reply to mailman-owner with a "please take me off the list" note, leaving me to send back endless streams of form letters along the lines of "Look, Jane, you ignorant slut, read the damn note and unsubscribe your own damn self, I don't even know which *list* you're on!" (Let's see how many saturday night live fans are in the audience :-)) Yes, I know I have the tools to pretty straightforwardly find the list and kill them from the command line, but that presumes it's a list I manage myself. In between these bouts, I like the feature. From chuqui at plaidworks.com Sat Feb 1 13:19:00 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Sat Feb 1 16:19:26 2003 Subject: [Mailman-Developers] I hate the 1st of the month. In-Reply-To: <5.1.0.14.2.20030201145755.064badb0@lennier.cc.vt.edu> Message-ID: On Saturday, February 1, 2003, at 12:01 PM, Ron Jarrell wrote: > > Just venting. I'm in my monthly "God, I *hate* the password reminder > scheme" phase. I get over it in a few days. But for the next 48 > hours or so I'm dealing with a stream of people who reply to > mailman-owner with a "please take me off the list" note, leaving me to > send back endless streams of form letters along the lines of So change the note to say "if you want to unsubscribe, follow the instructions in this letter. do not respond to it, any responses will be ignored". then ignore them. problem solved. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ He doesn't have ulcers, but he's a carrier. From dgc at uchicago.edu Sat Feb 1 18:15:17 2003 From: dgc at uchicago.edu (David Champion) Date: Sat Feb 1 19:15:48 2003 Subject: [Mailman-Developers] Re: I hate the 1st of the month. In-Reply-To: <5.1.0.14.2.20030201145755.064badb0@lennier.cc.vt.edu> References: <5.1.0.14.2.20030201145755.064badb0@lennier.cc.vt.edu> Message-ID: <20030202001517.GU7855@dust.uchicago.edu> * On 2003.02.01, in <5.1.0.14.2.20030201145755.064badb0@lennier.cc.vt.edu>, * "Ron Jarrell" wrote: > > Just venting. I'm in my monthly "God, I *hate* the password reminder > scheme" phase. I get over it in a few days. But for the next 48 hours > or so I'm dealing with a stream of people who reply to mailman-owner > with a "please take me off the list" note, leaving me to send back > endless streams of form letters along the lines of "Look, Jane, you > ignorant slut, read the damn note and unsubscribe your own damn self, > I don't even know which *list* you're on!" I used to hate the first of the month. We used to get several thousand bounces and several dozen "take me off" messages each month around the 1-3. Then I wrote an autoresponder and attached it to mailman-ignore@listhost.uchicago.edu, and rewrote the monthly reminder to send reminders from that address. (It also no longer send passwords, just list names and contact addresses/URLs.) Mailman-ignore@ does mail loop protection, and returns boilerplate to the effect that we told you we'd ignore replies, and we are. It reiterates directions for common problems, with a little more detail than the instructions in the password reminder, and describes some things such as unsub/resub for changing your address. At the bottom, it tells people to contact mailman-owner@listhost... directly if they're still unsatisfied. We get perhaps 5-10 responses each month now, and by and large they're reasonable requests, not people who simply failed to read the directions. It's saved me $thousands in medical charges not covered by my plan, not to mention legal fees. -- -D. "Jobs are created when... Americans have more money... dgc@uchicago.edu and the best way to make sure Americans have that money is not to tax it.... More jobs mean more taxpayers and higher revenues to our government." - G.W. Bush From jon at csh.rit.edu Sun Feb 2 21:14:22 2003 From: jon at csh.rit.edu (Jon Parise) Date: Sun Feb 2 21:14:26 2003 Subject: [Mailman-Developers] mailpasswds and SuppressPasswordReminder Message-ID: <20030203021421.GB18267@csh.rit.edu> It looks like the "massive rewrite" that occured between revisions 2.5 and 2.5 of cron/mailpasswds removed the SuppressPasswordReminder check. Attached is a totally untested patch provided simply to suggest a possible fix. -- Jon Parise (jon@csh.rit.edu) :: http://www.csh.rit.edu/~jon/ -------------- next part -------------- Index: mailpasswds =================================================================== RCS file: /cvsroot/mailman/mailman/cron/mailpasswds,v retrieving revision 2.14 diff -u -r2.14 mailpasswds --- mailpasswds 2 Jan 2003 05:40:57 -0000 2.14 +++ mailpasswds 3 Feb 2003 02:12:47 -0000 @@ -136,6 +136,10 @@ for mlist in byhost[host]: listaddr = mlist.GetListEmail() for member in mlist.getMembers(): + # The user may have disabled password reminders for this list + if mlist.getMemberOption(member, + mm_cfg.SuppressPasswordReminder): + continue # Group by the lower-cased address, since Mailman always # treates person@dom.ain the same as PERSON@dom.ain. password = mlist.getMemberPassword(member) From chuqui at plaidworks.com Sun Feb 2 21:19:08 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Mon Feb 3 00:19:24 2003 Subject: [Mailman-Developers] mailpasswd still broken. Message-ID: <052BABB7-3737-11D7-AC25-0003934516A8@plaidworks.com> got further, but still broken.. grump. Traceback (most recent call last): File "/usr/local/mailman/cron/mailpasswds", line 216, in ? main() File "/usr/local/mailman/cron/mailpasswds", line 200, in main text, poplang) File "/usr/local/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) LookupError: unknown encoding off to do more debugging... -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Someday, we'll look back on this, laugh nervously and change the subject. From mch at cix.compulink.co.uk Mon Feb 3 13:00:00 2003 From: mch at cix.compulink.co.uk (Mike Holderness) Date: Mon Feb 3 08:00:34 2003 Subject: [Mailman-Developers] Oddness with handle-opts.html and subscribe.html Message-ID: In-Reply-To: I'm using MailMan 2.0.6 - upgrading isn't under my control since I don't run the server. The results pages handle-opts.html and subscribe.html seem to be returning **** &quot; Mike [1] if I see a pattern I'll provide a test case. From bryanf at samurai.com Mon Feb 3 10:24:04 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Mon Feb 3 10:24:26 2003 Subject: [Mailman-Developers] Mailman 2.1.1 ETA? Message-ID: <87C52D36-378B-11D7-A0E1-000393013B04@samurai.com> Howdy, Is there an ETA on 2.1.1? It's hard to justify using sources from CVS in production, and it's becoming a bit annoying trying to remember all the patches to apply when a new fix comes along. :) Thanks, Bryan From barry at python.org Mon Feb 3 11:05:02 2003 From: barry at python.org (Barry A. Warsaw) Date: Mon Feb 3 11:05:34 2003 Subject: [Mailman-Developers] Mailman 2.1.1 ETA? References: <87C52D36-378B-11D7-A0E1-000393013B04@samurai.com> Message-ID: <15934.37678.632527.29833@gargle.gargle.HOWL> >>>>> "BF" == Bryan Fullerton writes: BF> Is there an ETA on 2.1.1? It's hard to justify using sources BF> from CVS in production, and it's becoming a bit annoying BF> trying to remember all the patches to apply when a new fix BF> comes along. :) Unfortunately no. Due to recent changes in my work situation, I'm only able to work on Mailman in my spare time these days. I find it's nearly impossible just to keep up on the lists. But I am working hard on trying to get the most critical fixes into cvs so I can spin a 2.1.1 release as soon as possible. -Barry From bryanf at samurai.com Mon Feb 3 11:15:52 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Mon Feb 3 11:16:15 2003 Subject: [Mailman-Developers] Mailman 2.1.1 ETA? In-Reply-To: <15934.37678.632527.29833@gargle.gargle.HOWL> Message-ID: On Monday, February 3, 2003, at 11:05 AM, Barry A. Warsaw wrote: > Unfortunately no. Due to recent changes in my work situation, I'm > only able to work on Mailman in my spare time these days. Ah, that sucks. > I find it's nearly impossible just to keep up on the lists. Yeah, release of 2.1 has generated a lot of traffic, especially on the -users list. But people seem to be stepping up to answer questions instead of waiting for you, which is great (except if they're giving wrong answers ;). > But I am working hard > on trying to get the most critical fixes into cvs so I can spin a > 2.1.1 release as soon as possible. Okie. My time is also somewhat limited, what with my first child having arrived two months early on Jan 26th, but if I can help with the process somehow let me know. Thanks, Bryan From marc at perkel.com Mon Feb 3 08:33:58 2003 From: marc at perkel.com (Marc Perkel) Date: Mon Feb 3 11:34:25 2003 Subject: [Mailman-Developers] Just a thought about documentation Message-ID: <3E3E99F6.4050307@perkel.com> One problem with developers writing their own documentation is that the developer never experienced learning the program. One of the problems with almost all free software is that the documentation could be a lot better. There are also many schools out there that have courses for people who want to become technical writers. People who's job it will someday be to do software documentation. So it occurs to me that if technical writing colleges hooked up with free software projects and assigned documenting free software - such as Mailnan to students - that it would be beneficial for both worlds. My two centz .... From barry at python.org Mon Feb 3 11:43:00 2003 From: barry at python.org (Barry A. Warsaw) Date: Mon Feb 3 11:43:31 2003 Subject: [Mailman-Developers] Just a thought about documentation References: <3E3E99F6.4050307@perkel.com> Message-ID: <15934.39956.158539.675965@gargle.gargle.HOWL> >>>>> "MP" == Marc Perkel writes: MP> One problem with developers writing their own documentation is MP> that the developer never experienced learning the program. One MP> of the problems with almost all free software is that the MP> documentation could be a lot better. True! MP> There are also many schools out there that have courses for MP> people who want to become technical writers. People who's job MP> it will someday be to do software documentation. So it occurs MP> to me that if technical writing colleges hooked up with free MP> software projects and assigned documenting free software - MP> such as Mailnan to students - that it would be beneficial for MP> both worlds. Wow, Marc, that's an excellent idea. Do you have any contacts and/or could you facilitate this? -Barry From marc at perkel.com Mon Feb 3 09:36:50 2003 From: marc at perkel.com (Marc Perkel) Date: Mon Feb 3 12:36:56 2003 Subject: [Mailman-Developers] Just a thought about documentation In-Reply-To: <15934.39956.158539.675965@gargle.gargle.HOWL> References: <3E3E99F6.4050307@perkel.com> <15934.39956.158539.675965@gargle.gargle.HOWL> Message-ID: <3E3EA8B2.4080608@perkel.com> I'm glad you like the idea Barry. No - I don't have any contacts. But someone else might have contacts. My idea in creating documentation is that the student or perhaps a small group of student would work with developers who would make sure that the new information was accurate. Also - as part of the project the sudents would find end users - maybe a Linux users group and give them the docs and software and watch them learn and configure Mailman from the documentation and record their voice comments so as to learn what is confusing about the documentation. After completing the course - the fact that they did this software documentation project becomes part of their job resume and might create an ongoing relationship between the student and the developers. And free software would greatly benefit. Barry A. Warsaw wrote: >>>>>>"MP" == Marc Perkel writes: >>>>>> >>>>>> > > MP> One problem with developers writing their own documentation is > MP> that the developer never experienced learning the program. One > MP> of the problems with almost all free software is that the > MP> documentation could be a lot better. > >True! > > MP> There are also many schools out there that have courses for > MP> people who want to become technical writers. People who's job > MP> it will someday be to do software documentation. So it occurs > MP> to me that if technical writing colleges hooked up with free > MP> software projects and assigned documenting free software - > MP> such as Mailnan to students - that it would be beneficial for > MP> both worlds. > >Wow, Marc, that's an excellent idea. Do you have any contacts and/or >could you facilitate this? > >-Barry > >_______________________________________________ >Mailman-Developers mailing list >Mailman-Developers@python.org >http://mail.python.org/mailman/listinfo/mailman-developers > > From barry at python.org Mon Feb 3 12:49:04 2003 From: barry at python.org (Barry A. Warsaw) Date: Mon Feb 3 12:49:35 2003 Subject: [Mailman-Developers] Mailman 2.1.1 ETA? References: <15934.37678.632527.29833@gargle.gargle.HOWL> Message-ID: <15934.43920.123457.930075@gargle.gargle.HOWL> >>>>> "BF" == Bryan Fullerton writes: >> Unfortunately no. Due to recent changes in my work situation, >> I'm only able to work on Mailman in my spare time these days. BF> Ah, that sucks. Only if you don't have an adversarial relationship with your pillow: http://mail.python.org/pipermail/python-list/2001-August/058073.html >> I find it's nearly impossible just to keep up on the lists. BF> Yeah, release of 2.1 has generated a lot of traffic, BF> especially on the -users list. But people seem to be stepping BF> up to answer questions instead of waiting for you, which is BF> great (except if they're giving wrong answers ;). So far, I think the quality of answers has been excellent -- and most appreciated! >> But I am working hard on trying to get the most critical fixes >> into cvs so I can spin a 2.1.1 release as soon as possible. BF> Okie. My time is also somewhat limited, what with my first BF> child having arrived two months early on Jan 26th, but if I BF> can help with the process somehow let me know. Hey, congratulations! What would help a lot is scanning mailman-users and mailman-developers and making sure than any real bugs reported are in the SF trackers. Also that bugs and patches are assigned to the proper group, and that some triage is done on them to assign priorities. I'd like to get to the point where anything over priority 7 has to get fixed in 2.1.1, and then just attack them one by one. Any help you can provide here would be greatly appreciated. The more I can focus on the really critical stuff, the quicker I can get 2.1.1 out. -Barry From jon at csh.rit.edu Mon Feb 3 22:35:30 2003 From: jon at csh.rit.edu (Jon Parise) Date: Mon Feb 3 22:35:39 2003 Subject: [Mailman-Developers] mailpasswds and SuppressPasswordReminder In-Reply-To: <20030203021421.GB18267@csh.rit.edu> References: <20030203021421.GB18267@csh.rit.edu> Message-ID: <20030204033530.GA28578@csh.rit.edu> On Sun, Feb 02, 2003 at 09:14:22PM -0500, Jon Parise wrote: > It looks like the "massive rewrite" that occured between revisions 2.5 > and 2.5 of cron/mailpasswds removed the SuppressPasswordReminder > check. > > Attached is a totally untested patch provided simply to suggest a > possible fix. Just a note that I was able to verify that the following patch does indeed fix the problem. I'll submit a SourceForge patch so this doesn't get lost. > Index: mailpasswds > =================================================================== > RCS file: /cvsroot/mailman/mailman/cron/mailpasswds,v > retrieving revision 2.14 > diff -u -r2.14 mailpasswds > --- mailpasswds 2 Jan 2003 05:40:57 -0000 2.14 > +++ mailpasswds 3 Feb 2003 02:12:47 -0000 > @@ -136,6 +136,10 @@ > for mlist in byhost[host]: > listaddr = mlist.GetListEmail() > for member in mlist.getMembers(): > + # The user may have disabled password reminders for this list > + if mlist.getMemberOption(member, > + mm_cfg.SuppressPasswordReminder): > + continue > # Group by the lower-cased address, since Mailman always > # treates person@dom.ain the same as PERSON@dom.ain. > password = mlist.getMemberPassword(member) -- Jon Parise (jon@csh.rit.edu) :: http://www.csh.rit.edu/~jon/ From barry at python.org Mon Feb 3 23:36:36 2003 From: barry at python.org (Barry A. Warsaw) Date: Mon Feb 3 23:37:06 2003 Subject: [Mailman-Developers] mailpasswds and SuppressPasswordReminder References: <20030203021421.GB18267@csh.rit.edu> Message-ID: <15935.17236.821725.6217@gargle.gargle.HOWL> >>>>> "JP" == Jon Parise writes: JP> It looks like the "massive rewrite" that occured between JP> revisions 2.5 and 2.5 of cron/mailpasswds removed the JP> SuppressPasswordReminder check. JP> Attached is a totally untested patch provided simply to JP> suggest a possible fix. Seems good to me, and I've applied it to cvs. Thanks! -Barry From jarrell at vt.edu Tue Feb 4 09:24:51 2003 From: jarrell at vt.edu (Ron Jarrell) Date: Tue Feb 4 09:25:55 2003 Subject: [Mailman-Developers] bugs postings? Message-ID: <5.1.0.14.2.20030204092247.04127920@lennier.cc.vt.edu> Did the posting of bugs to the list break, or did I just miss a thread where it was announced it would stop? I haven't seen any since the 19th (which includes the one I put in recently about incorrect padding errors coming out of ToDigest->Scrubber->Message->Utils->base64, which is stacking up mail in my shunt). From barry at python.org Tue Feb 4 09:31:10 2003 From: barry at python.org (Barry A. Warsaw) Date: Tue Feb 4 09:31:41 2003 Subject: [Mailman-Developers] bugs postings? References: <5.1.0.14.2.20030204092247.04127920@lennier.cc.vt.edu> Message-ID: <15935.52910.5212.640079@gargle.gargle.HOWL> >>>>> "RJ" == Ron Jarrell writes: RJ> Did the posting of bugs to the list break, or did I just miss RJ> a thread where it was announced it would stop? I haven't seen RJ> any since the 19th (which includes the one I put in recently RJ> about incorrect padding errors coming out of RJ> ToDigest->Scrubber->Message->Utils->base64, which is stacking RJ> up mail in my shunt). Hey Ron, I think you missed the announcement. All SF tracker postings are now going to mailman-coders@python.org http://mail.python.org/mailman/listinfo/mailman-coders Cheers, -Barry From jarrell at vt.edu Tue Feb 4 10:25:52 2003 From: jarrell at vt.edu (Ron Jarrell) Date: Tue Feb 4 10:27:38 2003 Subject: [Mailman-Developers] bugs postings? In-Reply-To: <15935.52910.5212.640079@gargle.gargle.HOWL> References: <5.1.0.14.2.20030204092247.04127920@lennier.cc.vt.edu> Message-ID: <5.1.0.14.2.20030204102427.06313750@lennier.cc.vt.edu> At 09:31 AM 2/4/03 -0500, Barry A. Warsaw wrote: >>>>>> "RJ" == Ron Jarrell writes: > > RJ> Did the posting of bugs to the list break, or did I just miss > RJ> a thread where it was announced it would stop? I haven't seen > RJ> any since the 19th (which includes the one I put in recently > RJ> about incorrect padding errors coming out of > RJ> ToDigest->Scrubber->Message->Utils->base64, which is stacking > RJ> up mail in my shunt). > >Hey Ron, I think you missed the announcement. All SF tracker postings >are now going to mailman-coders@python.org > > http://mail.python.org/mailman/listinfo/mailman-coders Figures... Been up to *here* (picture hand waving forlornly somewhere up above my head) with "emergency" projects that used to be cancelled projects getting in the way of the critical projects that stepped all over the important projects, and been skimming, rather than reading... From barry at python.org Wed Feb 5 11:06:57 2003 From: barry at python.org (Barry A. Warsaw) Date: Wed Feb 5 11:07:29 2003 Subject: [Mailman-Developers] Attention Mailman Hosting Sites Message-ID: <15937.13985.60266.13096@gargle.gargle.HOWL> A long while ago, I offered to put up a page listing sites that offered commercial Mailman list hosting services. Sadly, I don't have the time to maintain this or even put it together. However, there is a MoinMoin page (think: Wiki) listing general Python hosting services, of which Mailman is included. I encourage all Mailman hosting facilities to add entries to the page: http://www.python.org/cgi-bin/moinmoin/PythonHosting There is currently only one Mailman hosting site listed. The MoinMoin is on the honor system, and you don't need a password to add content to it. If you do add an entry, be sure to include the word "Mailman" so the page is easy to search. Cheers, -Barry From dan.mick at sun.com Wed Feb 5 20:28:57 2003 From: dan.mick at sun.com (Dan Mick) Date: Wed Feb 5 23:30:24 2003 Subject: [Mailman-Developers] New unicode-related error with CVS Message-ID: <3E41E489.8050909@sun.com> Updated to CVS today, and now I'm seeing these; anyone else? Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, in process send_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, in send_digests send_i18n_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, in send_i18n_digests addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in lheader h = make_header(decode_header(s), **kws) File "/export/home/mailman/pythonlib/email/Header.py", line 123, in make_header h.append(s, charset) File "/export/home/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) SHUNTING: 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 From tkikuchi at is.kochi-u.ac.jp Thu Feb 6 14:38:11 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 00:38:27 2003 Subject: [Mailman-Developers] New unicode-related error with CVS References: <3E41E489.8050909@sun.com> Message-ID: <3E41F4C3.1040903@is.kochi-u.ac.jp> Dan Mick wrote: > Updated to CVS today, and now I'm seeing these; anyone else? No, but it's ToDigest.py again... > > addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) > File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in > lheader > h = make_header(decode_header(s), **kws) Does this person set his name in non-ascii character and your list is configured english (us-ascii) ? I think I have to update my patch. https://sourceforge.net/tracker/?func=detail&aid=674401&group_id=103&atid=300103 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From tkikuchi at is.kochi-u.ac.jp Thu Feb 6 14:50:03 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 00:50:16 2003 Subject: [Mailman-Developers] New unicode-related error with CVS References: <3E41E489.8050909@sun.com> <3E41F4C3.1040903@is.kochi-u.ac.jp> Message-ID: <3E41F78B.70501@is.kochi-u.ac.jp> Dan, > > I think I have to update my patch. > https://sourceforge.net/tracker/?func=detail&aid=674401&group_id=103&atid=300103 > > There actually are two patches, original and revised. I think the original one will get you better result. https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=40608&aid=674401 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From Daniel.Buchmann at bibsys.no Thu Feb 6 10:47:17 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Thu Feb 6 04:50:26 2003 Subject: [Mailman-Developers] checkdbs UnicodeError Message-ID: <1044524838.3202.8.camel@fornax.bibsys.no> I was the puzzled receiver of these words this morning: Traceback (most recent call last): File "/home/mailman/cron/checkdbs", line 136, in ? main() File "/home/mailman/cron/checkdbs", line 80, in main text += '\n' + pending_requests(mlist) File "/home/mailman/cron/checkdbs", line 123, in pending_requests text = NL.join(pending) UnicodeError: ASCII decoding error: ordinal not in range(128) Anyone else seen this and know how to fix it? Couldn't find anything about this in the SF bug tracker... I'm using the Release_2_1-maint CVS branch. -Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030206/c8b5c5e4/attachment.bin From tkikuchi at is.kochi-u.ac.jp Thu Feb 6 19:25:41 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 05:25:59 2003 Subject: [Mailman-Developers] checkdbs UnicodeError References: <1044524838.3202.8.camel@fornax.bibsys.no> Message-ID: <3E423825.2060209@is.kochi-u.ac.jp> Hi, Try this patch. It's a coincidence that I am working on it. Index: checkdbs =================================================================== RCS file: /cvsroot/mailman/mailman/cron/checkdbs,v retrieving revision 2.17 diff -u -r2.17 checkdbs --- checkdbs 28 Oct 2002 03:43:42 -0000 2.17 +++ checkdbs 6 Feb 2003 10:21:27 -0000 @@ -92,6 +92,7 @@ def pending_requests(mlist): + lcset = Utils.GetCharSet(mlist.preferred_language) # Must return a byte string pending = [] first = 1 @@ -101,6 +102,8 @@ first = 0 when, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) if fullname: + if _isunicode(fullname): + fullname = fullname.encode(lcset, 'replace') fullname = ' (%s)' % fullname pending.append(' %s%s %s' % (addr, fullname, time.ctime(when))) first = 1 ======= Daniel Buchmann wrote: > I was the puzzled receiver of these words this morning: > > Traceback (most recent call last): > File "/home/mailman/cron/checkdbs", line 136, in ? > main() > File "/home/mailman/cron/checkdbs", line 80, in main > text += '\n' + pending_requests(mlist) > File "/home/mailman/cron/checkdbs", line 123, in pending_requests > text = NL.join(pending) > UnicodeError: ASCII decoding error: ordinal not in range(128) > > > Anyone else seen this and know how to fix it? > Couldn't find anything about this in the SF bug tracker... > > I'm using the Release_2_1-maint CVS branch. > > > -Daniel > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From Daniel.Buchmann at bibsys.no Thu Feb 6 11:33:46 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Thu Feb 6 05:37:17 2003 Subject: [Mailman-Developers] checkdbs UnicodeError In-Reply-To: <3E423825.2060209@is.kochi-u.ac.jp> References: <1044524838.3202.8.camel@fornax.bibsys.no> <3E423825.2060209@is.kochi-u.ac.jp> Message-ID: <1044527630.3201.18.camel@fornax.bibsys.no> The patch solved the problem. Thanks! :) Over to something else: Is there anyone out there that has written a script to flush (discard) the entire request db for a specified list? I need it badly.. ;) On Thu, 2003-02-06 at 11:25, Tokio Kikuchi wrote: > Hi, > > Try this patch. It's a coincidence that I am working on it. > > Index: checkdbs > =================================================================== > RCS file: /cvsroot/mailman/mailman/cron/checkdbs,v > retrieving revision 2.17 > diff -u -r2.17 checkdbs > --- checkdbs 28 Oct 2002 03:43:42 -0000 2.17 > +++ checkdbs 6 Feb 2003 10:21:27 -0000 > @@ -92,6 +92,7 @@ > > > > def pending_requests(mlist): > + lcset = Utils.GetCharSet(mlist.preferred_language) > # Must return a byte string > pending = [] > first = 1 > @@ -101,6 +102,8 @@ > first = 0 > when, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) > if fullname: > + if _isunicode(fullname): > + fullname = fullname.encode(lcset, 'replace') > fullname = ' (%s)' % fullname > pending.append(' %s%s %s' % (addr, fullname, time.ctime(when))) > first = 1 > > ======= > > Daniel Buchmann wrote: > > I was the puzzled receiver of these words this morning: > > > > Traceback (most recent call last): > > File "/home/mailman/cron/checkdbs", line 136, in ? > > main() > > File "/home/mailman/cron/checkdbs", line 80, in main > > text += '\n' + pending_requests(mlist) > > File "/home/mailman/cron/checkdbs", line 123, in pending_requests > > text = NL.join(pending) > > UnicodeError: ASCII decoding error: ordinal not in range(128) > > > > > > Anyone else seen this and know how to fix it? > > Couldn't find anything about this in the SF bug tracker... > > > > I'm using the Release_2_1-maint CVS branch. > > > > > > -Daniel > > > > -- > Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp > http://weather.is.kochi-u.ac.jp/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030206/fc397b88/attachment.bin From tkikuchi at is.kochi-u.ac.jp Thu Feb 6 19:47:59 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 05:48:15 2003 Subject: [Mailman-Developers] checkdbs UnicodeError References: <1044524838.3202.8.camel@fornax.bibsys.no> <3E423825.2060209@is.kochi-u.ac.jp> <1044527630.3201.18.camel@fornax.bibsys.no> Message-ID: <3E423D5F.4070202@is.kochi-u.ac.jp> Daniel Buchmann wrote: > The patch solved the problem. Thanks! :) You're welcome. > > Over to something else: > Is there anyone out there that has written a script to flush (discard) > the entire request db for a specified list? > I need it badly.. ;) It's me again. ;^) https://sourceforge.net/tracker/?func=detail&aid=636412&group_id=103&atid=300103 Ooops, not for one list but entire lists. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From greg at gregsteele.net Mon Feb 3 10:43:49 2003 From: greg at gregsteele.net (greg steele) Date: Thu Feb 6 08:56:27 2003 Subject: [Mailman-Developers] archive html In-Reply-To: <3E3EA8B2.4080608@perkel.com> References: <3E3E99F6.4050307@perkel.com> <15934.39956.158539.675965@gargle.gargle.HOWL> <3E3EA8B2.4080608@perkel.com> Message-ID: <3E3EAA55.3070204@gregsteele.net> ok... I did google and couldn't find any info about this.... Can I edit/re-write the archive pages to match the look/feel of the rest of my site? anyone? bueller? g From killesreiter at physik.uni-freiburg.de Sun Feb 2 03:20:41 2003 From: killesreiter at physik.uni-freiburg.de (Gerhard Killesreiter) Date: Thu Feb 6 08:59:21 2003 Subject: [Mailman-Developers] Re: [Bug] guess_type() got an unexpected keyword argument 'strict' In-Reply-To: <4alm0z2zon.fsf@helios.physik.uni-freiburg.de> References: <4alm0z2zon.fsf@helios.physik.uni-freiburg.de> Message-ID: <4afzr72zk6.fsf@helios.physik.uni-freiburg.de> Gerhard Killesreiter writes: > I decided to move my lists to 2.1 this night. + I decided to be brave and use cvs if this wasn't obvious. Cheers, Gerhard -- > Ach! War es Mark Twain, der gesagt hat, da? nur ein Leben reicht > nicht, um Deutsch lernen zu k?nnen? Woher wu?te *der* eigentlich von der Rechtschreibreform? (Holger Kunadt zu Jo?o Luiz in desd) From killesreiter at physik.uni-freiburg.de Sun Feb 2 03:18:00 2003 From: killesreiter at physik.uni-freiburg.de (Gerhard Killesreiter) Date: Thu Feb 6 08:59:22 2003 Subject: [Mailman-Developers] [Bug] guess_type() got an unexpected keyword argument 'strict' Message-ID: <4alm0z2zon.fsf@helios.physik.uni-freiburg.de> Hi there! Please Cc me on responses I am not on the list. Sorry for not using the bug tracker, but somehow it does not like my ancient version of nutscrape. I decided to move my lists to 2.1 this night. Everything went more or less smooth, but when I wanted to visit the archive of my test-list, I got the error below. I /think/ that it might be due to the recent change in private.py: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/Mailman/Cgi/private.py.diff?r1=2.16&r2=2.17 Cheers, Gerhard Traceback (most recent call last): File "/home/vdst.net/mailman/scripts/driver", line 87, in run_main main() File "/home/vdst.net/mailman/Mailman/Cgi/private.py", line 136, in main ctype, enc = mimetypes.guess_type(path, strict=0) TypeError: guess_type() got an unexpected keyword argument 'strict' sys.version 2.1.1 (#1, Nov 18 2001, 12:16:29) [GCC 2.95.4 20010319 (prerelease)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 DOCUMENT_ROOT /var/www/doma.in/htdocs SERVER_ADDR 217.115.157.198 REMOTE_HOST helios.physik.uni-freiburg.de SERVER_PORT 80 PATH_TRANSLATED /var/www/doma.in/htdocs/test/ REMOTE_ADDR 132.230.78.135 UNIQUE_ID Pjx3CNlzjV8AAAPpO2s HTTP_ACCEPT_LANGUAGE en PHPRC /etc= GATEWAY_INTERFACE CGI/1.1 SERVER_NAME www.doma.in SCRIPT_FILENAME /home/doma.in/mailman/cgi-bin/private HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* REQUEST_URI /mailman/private/test/ QUERY_STRING SERVER_PROTOCOL HTTP/1.0 PATH_INFO /test/ HTTP_HOST list.doma.in REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.26 Ben-SSL/1.48 Server at www.doma.in Port 80 SCRIPT_NAME /mailman/private SERVER_ADMIN root@ds217-115-141-95.dedicated.hosteurope.de SERVER_SOFTWARE Apache/1.3.26 Ben-SSL/1.48 (Unix) mod_gzip/1.3.19.1a PHP/4.2.1 HTTP_USER_AGENT Mozilla (X11; I; Linux 2.0.32 i586) PYTHONPATH /home/doma.in/mailman -- Dipl.-Phys. Gerhard Killesreiter Man soll nciht so tun, als wenn es "neutrale" oder "objektive" Wissenschaften gibt. (Stephan Peters aka Kang0815 in dssv) From nicolas at marchildon.net Thu Feb 6 02:30:33 2003 From: nicolas at marchildon.net (Nicolas Marchildon) Date: Thu Feb 6 09:00:31 2003 Subject: [Mailman-Developers] PGP whitelist to skip moderation Message-ID: <1044516634.23564.69.camel@cortex.marchildon.net> I'm currently the admin of a few Mailman lists. There used to be lots of spam and viruses, so we added Spamassassin to our procmail configuration, which dumps flagged messages to a designed file. Obviously, it does not catch everything, such as messages *totally* unrelated with the list subject comming from lost people, or some viruses/worms. So we decided to moderate the lists. Even subscribers see their posts moderated, because some worms spread by sending messages with a forged sender, which would get through anyway. The traffic of "real" messages is currently below 10 messages per day, so it's quite manageable. However, even though there are 4 moderadors, it can take many hours for a message to get moderated. We would like to be able to let known people post to the list without having their message delivery delayed by the moderation. My proposal is to have Mailman manage a whitelist consisting of PGP keys. Messages signed with a "white" key would skip moderation. Subscribers willing to use this feature would only have to submit their key to a specific PGP key server. When a message that is signed but whose PGP key is not in the whitelist comes in, it would be dropped in the moderation queue. When the moderator looks at the list of messages, he would be given an extra option: "Add key 0x00000000 to whitelist". When submitting the form with this option selected, Mailman would fetch the key from its configured keyserver, and add it to its whitelist. That way, the next message signed with that key would not get moderated. If you change your key (new identity, or because it has expired), you simply have to submit it to the keyserver, and only your "first" message would be moderated. Note that the moderator does not have to verify your new key, his job is only to make sure the content of your mail is appropriate. It's up the each subscriber to get your key, verify it, possibly sign it, and verify the messages you send. Most key servers also have a web interface for adding, updating and searching for keys. A simple link to this web interface from the list info page would be a good-enough integration, in my opinion. I have searched the archives for discussions of PGP and Mailman, and found an interesting post[1] from Phil Stracchino, who describes an "Accept signed posts only" option, but which lacked a good description of how keys would get to the whitelist. My proposal does not allow spammers to automatically add their key and then post their crap, because a first signed message has to be approved by the moderator, who will discover the spam, and reject the message without adding the key to the whitelist. I also found two[2] patches[3] for adding PGP support to Mailman, but only adding *encryption* support, not simple signatures. However, because those two patches have already integrated GnuPG into Mailman, it would be a good base for going further by implementing my idea. I don't know Mailman's code a lot, but I have hacked it a bit recently to add the "approved" header for posting to usenet, and made the same Message-Id appear in both regular mail and usenet deliveries. I am willing to spend some time implementing the feature I described, and I was even contacted by an other person offering help. I found two messages stating we should wait until 2.1 is released, which seems to be done now. I'd like to know the status of the PGP support, mainly to figure out which of the two patches to build on. Is anybody planning to apply an existing patch for adding PGP support? As for those that might ask "why bother implementing this if 95% of the planet don't know what PGP is?" I answer that I know enough people on the list I administer that know how to use PGP, and would actually be very happy if that was implemented :) Thanks for your help, Nicolas Marchildon [1]http://www.mail-archive.com/mailman-developers@python.org/msg05055.html [2] https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645297&group_id=103 [3] http://www.nah6.com/products/secure-list/ -- OpenPGP public key: http://nicolas.marchildon.net/pubkey.txt Key fingerprint: 5E84 1089 0036 BB63 6997 232C 8FFB 777D 39D4 B2D4 Jabber ID: nicolas@marchildon.net http://www.jabber.org What have you done for freedom today? http://www.gnu.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030206/efb50dc1/attachment.bin From mrbill at mrbill.net Thu Feb 6 09:45:04 2003 From: mrbill at mrbill.net (Bill Bradford) Date: Thu Feb 6 10:45:08 2003 Subject: [Mailman-Developers] Weirdness with 2.1 Message-ID: <20030206154504.GQ907@mrbill.net> 2.1 works fine for me, *except* When I go to http://mysite/mailman/admindb/, it asks for the list password. I give it, get the "held for moderation/approval" queue of messages, pick my choices on each, and hit submit. I then get the password auth page again, have to do it over, and hit submit *again*, then it "takes" and processes the messages per my admin choices. I can duplicate this at will using either Mozilla, IE5/6 for Windows, Chimera or Safari on the Mac, so its not a cookies problem, at least not on the client side.. Bill -- bill bradford mrbill@mrbill.net austin, texas From bryanf at samurai.com Thu Feb 6 11:03:38 2003 From: bryanf at samurai.com (Bryan Fullerton) Date: Thu Feb 6 11:03:41 2003 Subject: [Mailman-Developers] Weirdness with 2.1 In-Reply-To: <20030206154504.GQ907@mrbill.net> Message-ID: <8E14A429-39EC-11D7-9178-0003936377F0@samurai.com> On Thursday, February 6, 2003, at 10:45 AM, Bill Bradford wrote: > 2.1 works fine for me, *except* > > When I go to http://mysite/mailman/admindb/, it asks for the > list password. I give it, get the "held for moderation/approval" queue > of messages, pick my choices on each, and hit submit. > > I then get the password auth page again, have to do it over, and hit > submit *again*, then it "takes" and processes the messages per my > admin choices. Are you running Mailman 2.1 and 2.0 lists in the same URI space? If so, you're hitting bug #664466, which is fixed in CVS (and the bug closed, so you won't see it if you browse open bugs in SourceForge). http://sourceforge.net/tracker/ index.php?func=detail&aid=664466&group_id=103&atid=100103 Thanks, Bryan From dgc at uchicago.edu Thu Feb 6 12:18:44 2003 From: dgc at uchicago.edu (David Champion) Date: Thu Feb 6 13:23:01 2003 Subject: [Mailman-Developers] Re: checkdbs UnicodeError In-Reply-To: <1044527630.3201.18.camel@fornax.bibsys.no> References: <1044524838.3202.8.camel@fornax.bibsys.no> <3E423825.2060209@is.kochi-u.ac.jp> <1044527630.3201.18.camel@fornax.bibsys.no> Message-ID: <20030206181844.GW7855@dust.uchicago.edu> * On 2003.02.06, in <1044527630.3201.18.camel@fornax.bibsys.no>, * "Daniel Buchmann" wrote: > The patch solved the problem. Thanks! :) > > Over to something else: > Is there anyone out there that has written a script to flush (discard) > the entire request db for a specified list? > I need it badly.. ;) This might work for you. It will accept, reject, or discard all current post requests for one or more lists. You can give a reason. The reason enters the vette log, and is relayed to the poster if you're rejecting. I recommend that you try it on a test list or something, or save the backup of your config.db, or whatever. This is for an old version of Mailman and might not work as well for you as for me. http://home.uchicago.edu/~dgc/sw/mailman/bulk-vette.py server$ bulk-vette.py usage: /opt/bin/bulk-vette.py [-a | --accept] [-r | --reject] [-d | --discard] [-c "why" | --comment="why"] list [list ...] -- -D. "Jobs are created when... Americans have more money... dgc@uchicago.edu and the best way to make sure Americans have that money is not to tax it.... More jobs mean more taxpayers and higher revenues to our government." - G.W. Bush From dan.mick at sun.com Thu Feb 6 10:40:40 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Feb 6 13:42:08 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS Message-ID: <3E42AC28.1040304@sun.com> Sent this last night; haven't seen it on the list yet Updated to CVS today, and now I'm seeing these; anyone else? This seems to be stopping all traffic to the list Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, in process send_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, in send_digests send_i18n_digests(mlist, mboxfp) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, in send_i18n_digests addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in lheader h = make_header(decode_header(s), **kws) File "/export/home/mailman/pythonlib/email/Header.py", line 123, in make_header h.append(s, charset) File "/export/home/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range(128) Feb 05 20:17:15 2003 (4633) SHUNTING: 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 From dan.mick at sun.com Thu Feb 6 12:37:24 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Feb 6 15:38:52 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS In-Reply-To: <3E42AC28.1040304@sun.com> References: <3E42AC28.1040304@sun.com> Message-ID: <3E42C784.9030706@sun.com> One of my users has 8bit characters in his "username" string (the 'comment' part of his From address); that's causing this problem. The Unicode stuff doesn't like that. This hacks around the problem for now (just discarding those characters when manipulating the address). It's not a fix, but it let mail flow for me until a better one comes along. *** Header.py Mon Oct 14 09:50:57 2002 --- /export/home/mailman/pythonlib/email/Header.py Thu Feb 6 12:15:55 2003 *************** *** 183,189 **** def __unicode__(self): """Helper for the built-in unicode function.""" # charset item is a Charset instance so we need to stringify it. ! uchunks = [unicode(s, str(charset)) for s, charset in self._chunks] return u''.join(uchunks) # Rich comparison operators for equality only. BAW: does it make sense to --- 183,189 ---- def __unicode__(self): """Helper for the built-in unicode function.""" # charset item is a Charset instance so we need to stringify it. ! uchunks = [unicode(s, str(charset), 'ignore') for s, charset in self._chunks] return u''.join(uchunks) # Rich comparison operators for equality only. BAW: does it make sense to *************** *** 227,233 **** # Possibly raise UnicodeError if the byte string can't be # converted to a unicode with the input codec of the charset. incodec = charset.input_codec or 'us-ascii' ! ustr = unicode(s, incodec) # Now make sure that the unicode could be converted back to a # byte string with the output codec, which may be different # than the iput coded. Still, use the original byte string. --- 227,233 ---- # Possibly raise UnicodeError if the byte string can't be # converted to a unicode with the input codec of the charset. incodec = charset.input_codec or 'us-ascii' ! ustr = unicode(s, incodec, 'ignore') # Now make sure that the unicode could be converted back to a # byte string with the output codec, which may be different # than the iput coded. Still, use the original byte string. Dan Mick wrote: > Sent this last night; haven't seen it on the list yet > > Updated to CVS today, and now I'm seeing these; anyone else? > This seems to be stopping all traffic to the list > > > Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding > error: ordinal not in range(128) > Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): > File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in > _oneloop > self._onefile(msg, msgdata) > File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in > _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, > in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, > in _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, in > process > send_digests(mlist, mboxfp) > File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, in > send_digests > send_i18n_digests(mlist, mboxfp) > File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, in > send_i18n_digests > addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) > File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, in > lheader > h = make_header(decode_header(s), **kws) > File "/export/home/mailman/pythonlib/email/Header.py", line 123, in > make_header > h.append(s, charset) > File "/export/home/mailman/pythonlib/email/Header.py", line 230, in > append > ustr = unicode(s, incodec) > UnicodeError: ASCII decoding error: ordinal not in range(128) > > Feb 05 20:17:15 2003 (4633) SHUNTING: > 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers From bryanf at samurai.com Thu Feb 6 15:56:05 2003 From: bryanf at samurai.com (bryanf@samurai.com) Date: Thu Feb 6 15:56:38 2003 Subject: [Mailman-Developers] Weirdness with 2.1 In-Reply-To: <20030206181109.GF907@mrbill.net> References: <20030206154504.GQ907@mrbill.net> <8E14A429-39EC-11D7-9178-0003936377F0@samurai.com> <20030206181109.GF907@mrbill.net> Message-ID: <54182.142.76.1.62.1044564965.squirrel@mailbox.samurai.com> > I may have figured it out. Might want to add, to the 2.1 upgrade > instructions, that people need to go to all the computers they use, and > clear the cookies. I had MM2.0 list admin cookies on all of > the systems I use, which was causing the same/similar problem, > even though all the lists were upgraded to 2.1. Yeah, same problem, 2.0.x cookies make 2.1.0 barf. Kinda moot to change the docs for the next release, though - 2.1.1 will have the bug fix that's in CVS now, so this'll no longer be a problem. Bryan From tkikuchi at is.kochi-u.ac.jp Fri Feb 7 09:37:12 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 19:37:18 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS References: <3E42AC28.1040304@sun.com> <3E42C784.9030706@sun.com> Message-ID: <3E42FFB8.9000309@is.kochi-u.ac.jp> Dan, It is not a good idea to hack email package. The error raised should be treated in higher coding level. Please try patch #674401, most recent one (ToDigest.py.diff2.txt). https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=41727&aid=674401 Dan Mick wrote: > One of my users has 8bit characters in his "username" string (the > 'comment' part of his > From address); that's causing this problem. The Unicode stuff doesn't > like that. > > This hacks around the problem for now (just discarding those characters > when manipulating > the address). It's not a fix, but it let mail flow for me until a > better one > comes along. > > > *** Header.py Mon Oct 14 09:50:57 2002 > --- /export/home/mailman/pythonlib/email/Header.py Thu Feb 6 > 12:15:55 2003 > *************** > *** 183,189 **** > def __unicode__(self): > """Helper for the built-in unicode function.""" > # charset item is a Charset instance so we need to stringify it. > ! uchunks = [unicode(s, str(charset)) for s, charset in > self._chunks] > return u''.join(uchunks) > > # Rich comparison operators for equality only. BAW: does it make > sense to > --- 183,189 ---- > def __unicode__(self): > """Helper for the built-in unicode function.""" > # charset item is a Charset instance so we need to stringify it. > ! uchunks = [unicode(s, str(charset), 'ignore') for s, charset > in self._chunks] > return u''.join(uchunks) > > # Rich comparison operators for equality only. BAW: does it make > sense to > *************** > *** 227,233 **** > # Possibly raise UnicodeError if the byte string can't be > # converted to a unicode with the input codec of the > charset. > incodec = charset.input_codec or 'us-ascii' > ! ustr = unicode(s, incodec) > # Now make sure that the unicode could be converted > back to a > # byte string with the output codec, which may be > different > # than the iput coded. Still, use the original byte > string. > --- 227,233 ---- > # Possibly raise UnicodeError if the byte string can't be > # converted to a unicode with the input codec of the > charset. > incodec = charset.input_codec or 'us-ascii' > ! ustr = unicode(s, incodec, 'ignore') > # Now make sure that the unicode could be converted > back to a > # byte string with the output codec, which may be > different > # than the iput coded. Still, use the original byte > string. > > Dan Mick wrote: > >> Sent this last night; haven't seen it on the list yet >> >> Updated to CVS today, and now I'm seeing these; anyone else? >> This seems to be stopping all traffic to the list >> >> >> Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding >> error: ordinal not in range(128) >> Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): >> File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >> 130, in _dispose >> more = self._dopipeline(mlist, msg, msgdata, pipeline) >> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >> 153, in _dopipeline >> sys.modules[modname].process(mlist, msg, msgdata) >> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, >> in process >> send_digests(mlist, mboxfp) >> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, >> in send_digests >> send_i18n_digests(mlist, mboxfp) >> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, >> in send_i18n_digests >> addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) >> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, >> in lheader >> h = make_header(decode_header(s), **kws) >> File "/export/home/mailman/pythonlib/email/Header.py", line 123, in >> make_header >> h.append(s, charset) >> File "/export/home/mailman/pythonlib/email/Header.py", line 230, in >> append >> ustr = unicode(s, incodec) >> UnicodeError: ASCII decoding error: ordinal not in range(128) >> >> Feb 05 20:17:15 2003 (4633) SHUNTING: >> 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 >> >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers@python.org >> http://mail.python.org/mailman/listinfo/mailman-developers > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > > -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From dan.mick at sun.com Thu Feb 6 17:55:45 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Feb 6 20:56:48 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS In-Reply-To: <3E42FFB8.9000309@is.kochi-u.ac.jp> References: <3E42AC28.1040304@sun.com> <3E42C784.9030706@sun.com> <3E42FFB8.9000309@is.kochi-u.ac.jp> Message-ID: <3E431221.2040905@sun.com> Tokio Kikuchi wrote: > Dan, > > It is not a good idea to hack email package. The error raised should be > treated in higher coding level. heh. Desperate men have fewer options open to them. ;) > Please try patch #674401, most recent one > (ToDigest.py.diff2.txt). > https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=41727&aid=674401 I'll have a look. Thanks. > Dan Mick wrote: > >> One of my users has 8bit characters in his "username" string (the >> 'comment' part of his >> From address); that's causing this problem. The Unicode stuff >> doesn't like that. >> >> This hacks around the problem for now (just discarding those >> characters when manipulating >> the address). It's not a fix, but it let mail flow for me until a >> better one >> comes along. >> >> >> *** Header.py Mon Oct 14 09:50:57 2002 >> --- /export/home/mailman/pythonlib/email/Header.py Thu Feb 6 >> 12:15:55 2003 >> *************** >> *** 183,189 **** >> def __unicode__(self): >> """Helper for the built-in unicode function.""" >> # charset item is a Charset instance so we need to stringify >> it. >> ! uchunks = [unicode(s, str(charset)) for s, charset in >> self._chunks] >> return u''.join(uchunks) >> >> # Rich comparison operators for equality only. BAW: does it >> make sense to >> --- 183,189 ---- >> def __unicode__(self): >> """Helper for the built-in unicode function.""" >> # charset item is a Charset instance so we need to stringify >> it. >> ! uchunks = [unicode(s, str(charset), 'ignore') for s, charset >> in self._chunks] >> return u''.join(uchunks) >> >> # Rich comparison operators for equality only. BAW: does it >> make sense to >> *************** >> *** 227,233 **** >> # Possibly raise UnicodeError if the byte string >> can't be >> # converted to a unicode with the input codec of the >> charset. >> incodec = charset.input_codec or 'us-ascii' >> ! ustr = unicode(s, incodec) >> # Now make sure that the unicode could be converted >> back to a >> # byte string with the output codec, which may be >> different >> # than the iput coded. Still, use the original byte >> string. >> --- 227,233 ---- >> # Possibly raise UnicodeError if the byte string >> can't be >> # converted to a unicode with the input codec of the >> charset. >> incodec = charset.input_codec or 'us-ascii' >> ! ustr = unicode(s, incodec, 'ignore') >> # Now make sure that the unicode could be converted >> back to a >> # byte string with the output codec, which may be >> different >> # than the iput coded. Still, use the original byte >> string. >> >> Dan Mick wrote: >> >>> Sent this last night; haven't seen it on the list yet >>> >>> Updated to CVS today, and now I'm seeing these; anyone else? >>> This seems to be stopping all traffic to the list >>> >>> >>> Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding >>> error: ordinal not in range(128) >>> Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): >>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in >>> _oneloop >>> self._onefile(msg, msgdata) >>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in >>> _onefile >>> keepqueued = self._dispose(mlist, msg, msgdata) >>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>> 130, in _dispose >>> more = self._dopipeline(mlist, msg, msgdata, pipeline) >>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>> 153, in _dopipeline >>> sys.modules[modname].process(mlist, msg, msgdata) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, >>> in process >>> send_digests(mlist, mboxfp) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, >>> in send_digests >>> send_i18n_digests(mlist, mboxfp) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, >>> in send_i18n_digests >>> addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, >>> in lheader >>> h = make_header(decode_header(s), **kws) >>> File "/export/home/mailman/pythonlib/email/Header.py", line 123, in >>> make_header >>> h.append(s, charset) >>> File "/export/home/mailman/pythonlib/email/Header.py", line 230, in >>> append >>> ustr = unicode(s, incodec) >>> UnicodeError: ASCII decoding error: ordinal not in range(128) >>> >>> Feb 05 20:17:15 2003 (4633) SHUNTING: >>> 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 >>> >>> >>> _______________________________________________ >>> Mailman-Developers mailing list >>> Mailman-Developers@python.org >>> http://mail.python.org/mailman/listinfo/mailman-developers >> >> >> >> >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers@python.org >> http://mail.python.org/mailman/listinfo/mailman-developers >> >> > > From greg at gregsteele.net Thu Feb 6 19:15:31 2003 From: greg at gregsteele.net (greg steele) Date: Thu Feb 6 21:15:40 2003 Subject: [Mailman-Developers] archive html Message-ID: <3E4316C3.2080507@gregsteele.net> ok... I did google and couldn't find any info about this.... Can I edit/re-write the archive pages to match the look/feel of the rest of my site? anyone? bueller? g From dan.mick at sun.com Thu Feb 6 18:55:55 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Feb 6 21:56:52 2003 Subject: [Mailman-Developers] archive html In-Reply-To: <3E4316C3.2080507@gregsteele.net> References: <3E4316C3.2080507@gregsteele.net> Message-ID: <3E43203B.5000809@sun.com> greg steele wrote: > ok... I did google and couldn't find any info about this.... > > Can I edit/re-write the archive pages to match the look/feel of the rest > of my site? > > anyone? bueller? a casual look at templates/en, and noting that there are a wad of files that begin wtih 'arch', leads me to believe the answer is yes. Noting this comment from the code, in Mailman/Utils.py, leads me to believe that it could be list-specific, domain-specific, site-specific, or global, too: # When looking for a template in a specific language, there are 4 places # that are searched, in this order: # # 1. the list-specific language directory # lists// # # 2. the domain-specific language directory # templates// # # 3. the site-wide language directory # templates/site/ # # 4. the global default language directory # templates/ # # The first match found stops the search. In this way, you can specialize # templates at the desired level, or, if you use only the default # templates, you don't need to change anything. You should never modify # files in the templates/ subdirectory, since Mailman will # overwrite these when you upgrade. That's what the templates/site # language directories are for. # # A further complication is that the language to search for is determined # by both the `lang' and `mlist' arguments. The search order there is # that if lang is given, then the 4 locations above are searched, # substituting lang for . If no match is found, and mlist is # given, then the 4 locations are searched using the list's preferred # language. After that, the server default language is used for # . If that still doesn't yield a template, then the standard # distribution's English language template is used as an ultimate # fallback. If that's missing you've got big problems. ;) From dan.mick at sun.com Thu Feb 6 19:08:48 2003 From: dan.mick at sun.com (Dan Mick) Date: Thu Feb 6 22:10:23 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS In-Reply-To: <3E42FFB8.9000309@is.kochi-u.ac.jp> References: <3E42AC28.1040304@sun.com> <3E42C784.9030706@sun.com> <3E42FFB8.9000309@is.kochi-u.ac.jp> Message-ID: <3E432340.2010801@sun.com> Tokio: I haven't tried it yet, but I guess I don't understand how this is going to help. The problem is that unicode() inside Header.__unicode__() fails, because the input string has 8-bit characters in it; your patch still calls __unicode__() outside a try/except. Tokio Kikuchi wrote: > Dan, > > It is not a good idea to hack email package. The error raised should be > treated in higher coding level. Please try patch #674401, most recent one > (ToDigest.py.diff2.txt). > https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=41727&aid=674401 > > > Dan Mick wrote: > >> One of my users has 8bit characters in his "username" string (the >> 'comment' part of his >> From address); that's causing this problem. The Unicode stuff >> doesn't like that. >> >> This hacks around the problem for now (just discarding those >> characters when manipulating >> the address). It's not a fix, but it let mail flow for me until a >> better one >> comes along. >> >> >> *** Header.py Mon Oct 14 09:50:57 2002 >> --- /export/home/mailman/pythonlib/email/Header.py Thu Feb 6 >> 12:15:55 2003 >> *************** >> *** 183,189 **** >> def __unicode__(self): >> """Helper for the built-in unicode function.""" >> # charset item is a Charset instance so we need to stringify >> it. >> ! uchunks = [unicode(s, str(charset)) for s, charset in >> self._chunks] >> return u''.join(uchunks) >> >> # Rich comparison operators for equality only. BAW: does it >> make sense to >> --- 183,189 ---- >> def __unicode__(self): >> """Helper for the built-in unicode function.""" >> # charset item is a Charset instance so we need to stringify >> it. >> ! uchunks = [unicode(s, str(charset), 'ignore') for s, charset >> in self._chunks] >> return u''.join(uchunks) >> >> # Rich comparison operators for equality only. BAW: does it >> make sense to >> *************** >> *** 227,233 **** >> # Possibly raise UnicodeError if the byte string >> can't be >> # converted to a unicode with the input codec of the >> charset. >> incodec = charset.input_codec or 'us-ascii' >> ! ustr = unicode(s, incodec) >> # Now make sure that the unicode could be converted >> back to a >> # byte string with the output codec, which may be >> different >> # than the iput coded. Still, use the original byte >> string. >> --- 227,233 ---- >> # Possibly raise UnicodeError if the byte string >> can't be >> # converted to a unicode with the input codec of the >> charset. >> incodec = charset.input_codec or 'us-ascii' >> ! ustr = unicode(s, incodec, 'ignore') >> # Now make sure that the unicode could be converted >> back to a >> # byte string with the output codec, which may be >> different >> # than the iput coded. Still, use the original byte >> string. >> >> Dan Mick wrote: >> >>> Sent this last night; haven't seen it on the list yet >>> >>> Updated to CVS today, and now I'm seeing these; anyone else? >>> This seems to be stopping all traffic to the list >>> >>> >>> Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII decoding >>> error: ordinal not in range(128) >>> Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): >>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in >>> _oneloop >>> self._onefile(msg, msgdata) >>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in >>> _onefile >>> keepqueued = self._dispose(mlist, msg, msgdata) >>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>> 130, in _dispose >>> more = self._dopipeline(mlist, msg, msgdata, pipeline) >>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>> 153, in _dopipeline >>> sys.modules[modname].process(mlist, msg, msgdata) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, >>> in process >>> send_digests(mlist, mboxfp) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 120, >>> in send_digests >>> send_i18n_digests(mlist, mboxfp) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 213, >>> in send_i18n_digests >>> addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) >>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 372, >>> in lheader >>> h = make_header(decode_header(s), **kws) >>> File "/export/home/mailman/pythonlib/email/Header.py", line 123, in >>> make_header >>> h.append(s, charset) >>> File "/export/home/mailman/pythonlib/email/Header.py", line 230, in >>> append >>> ustr = unicode(s, incodec) >>> UnicodeError: ASCII decoding error: ordinal not in range(128) >>> >>> Feb 05 20:17:15 2003 (4633) SHUNTING: >>> 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 >>> >>> >>> _______________________________________________ >>> Mailman-Developers mailing list >>> Mailman-Developers@python.org >>> http://mail.python.org/mailman/listinfo/mailman-developers >> >> >> >> >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers@python.org >> http://mail.python.org/mailman/listinfo/mailman-developers >> >> > > From tkikuchi at is.kochi-u.ac.jp Fri Feb 7 12:26:25 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 6 22:26:32 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS References: <3E42AC28.1040304@sun.com> <3E42C784.9030706@sun.com> <3E42FFB8.9000309@is.kochi-u.ac.jp> <3E432340.2010801@sun.com> Message-ID: <3E432761.1090401@is.kochi-u.ac.jp> Sorry, Dan. I have just updated the patch. I uploaded an intermediate version. https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=41736&aid=674401 Dan Mick wrote: > Tokio: > > I haven't tried it yet, but I guess I don't understand how this is going > to help. > The problem is that unicode() inside Header.__unicode__() fails, because > the input > string has 8-bit characters in it; your patch still calls __unicode__() > outside > a try/except. > > Tokio Kikuchi wrote: > >> Dan, >> >> It is not a good idea to hack email package. The error raised should be >> treated in higher coding level. Please try patch #674401, most recent one >> (ToDigest.py.diff2.txt). >> https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=41727&aid=674401 >> >> >> Dan Mick wrote: >> >>> One of my users has 8bit characters in his "username" string (the >>> 'comment' part of his >>> From address); that's causing this problem. The Unicode stuff >>> doesn't like that. >>> >>> This hacks around the problem for now (just discarding those >>> characters when manipulating >>> the address). It's not a fix, but it let mail flow for me until a >>> better one >>> comes along. >>> >>> >>> *** Header.py Mon Oct 14 09:50:57 2002 >>> --- /export/home/mailman/pythonlib/email/Header.py Thu Feb 6 >>> 12:15:55 2003 >>> *************** >>> *** 183,189 **** >>> def __unicode__(self): >>> """Helper for the built-in unicode function.""" >>> # charset item is a Charset instance so we need to >>> stringify it. >>> ! uchunks = [unicode(s, str(charset)) for s, charset in >>> self._chunks] >>> return u''.join(uchunks) >>> >>> # Rich comparison operators for equality only. BAW: does it >>> make sense to >>> --- 183,189 ---- >>> def __unicode__(self): >>> """Helper for the built-in unicode function.""" >>> # charset item is a Charset instance so we need to >>> stringify it. >>> ! uchunks = [unicode(s, str(charset), 'ignore') for s, >>> charset in self._chunks] >>> return u''.join(uchunks) >>> >>> # Rich comparison operators for equality only. BAW: does it >>> make sense to >>> *************** >>> *** 227,233 **** >>> # Possibly raise UnicodeError if the byte string >>> can't be >>> # converted to a unicode with the input codec of >>> the charset. >>> incodec = charset.input_codec or 'us-ascii' >>> ! ustr = unicode(s, incodec) >>> # Now make sure that the unicode could be converted >>> back to a >>> # byte string with the output codec, which may be >>> different >>> # than the iput coded. Still, use the original >>> byte string. >>> --- 227,233 ---- >>> # Possibly raise UnicodeError if the byte string >>> can't be >>> # converted to a unicode with the input codec of >>> the charset. >>> incodec = charset.input_codec or 'us-ascii' >>> ! ustr = unicode(s, incodec, 'ignore') >>> # Now make sure that the unicode could be converted >>> back to a >>> # byte string with the output codec, which may be >>> different >>> # than the iput coded. Still, use the original >>> byte string. >>> >>> Dan Mick wrote: >>> >>>> Sent this last night; haven't seen it on the list yet >>>> >>>> Updated to CVS today, and now I'm seeing these; anyone else? >>>> This seems to be stopping all traffic to the list >>>> >>>> >>>> Feb 05 20:17:15 2003 (4633) Uncaught runner exception: ASCII >>>> decoding error: ordinal not in range(128) >>>> Feb 05 20:17:15 2003 (4633) Traceback (most recent call last): >>>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 105, in >>>> _oneloop >>>> self._onefile(msg, msgdata) >>>> File "/export/home/mailman/Mailman/Queue/Runner.py", line 155, in >>>> _onefile >>>> keepqueued = self._dispose(mlist, msg, msgdata) >>>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>>> 130, in _dispose >>>> more = self._dopipeline(mlist, msg, msgdata, pipeline) >>>> File "/export/home/mailman/Mailman/Queue/IncomingRunner.py", line >>>> 153, in _dopipeline >>>> sys.modules[modname].process(mlist, msg, msgdata) >>>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line 79, >>>> in process >>>> send_digests(mlist, mboxfp) >>>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line >>>> 120, in send_digests >>>> send_i18n_digests(mlist, mboxfp) >>>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line >>>> 213, in send_i18n_digests >>>> addresses = getaddresses([lheader(msg.get('from', ''), lcset)]) >>>> File "/export/home/mailman/Mailman/Handlers/ToDigest.py", line >>>> 372, in lheader >>>> h = make_header(decode_header(s), **kws) >>>> File "/export/home/mailman/pythonlib/email/Header.py", line 123, >>>> in make_header >>>> h.append(s, charset) >>>> File "/export/home/mailman/pythonlib/email/Header.py", line 230, >>>> in append >>>> ustr = unicode(s, incodec) >>>> UnicodeError: ASCII decoding error: ordinal not in range(128) >>>> >>>> Feb 05 20:17:15 2003 (4633) SHUNTING: >>>> 1044504218.645468+31ecfd687a04619284497495da50c740cbddf364 >>>> >>>> >>>> _______________________________________________ >>>> Mailman-Developers mailing list >>>> Mailman-Developers@python.org >>>> http://mail.python.org/mailman/listinfo/mailman-developers >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Mailman-Developers mailing list >>> Mailman-Developers@python.org >>> http://mail.python.org/mailman/listinfo/mailman-developers >>> >>> >> >> > > > From barry at python.org Thu Feb 6 23:47:10 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Feb 6 23:47:38 2003 Subject: [Mailman-Developers] Try 2: URGENT BREAKAGE: New unicode-related error with CVS References: <3E42AC28.1040304@sun.com> <3E42C784.9030706@sun.com> <3E42FFB8.9000309@is.kochi-u.ac.jp> <3E432340.2010801@sun.com> <3E432761.1090401@is.kochi-u.ac.jp> Message-ID: <15939.14926.565394.548404@gargle.gargle.HOWL> TK> I have just updated the patch. Applied! Thanks, it seems to have fixed the problems we were having on python.org. -Barry From marilyn at deliberate.com Fri Feb 7 10:21:53 2003 From: marilyn at deliberate.com (Marilyn Davis) Date: Fri Feb 7 13:43:06 2003 Subject: [Mailman-Developers] Patching question Message-ID: Hi Mailmen and Mailwomen, If I fix up a patch for 2.1 so that eVote works with it, some administrators will want it and some won't. What happens when new Mailman patches come along for 2.1+? Will I have to make a new patch for each patch? Please forgive my ignorance. Marilyn From pioppo at ferrara.linux.it Fri Feb 7 20:26:08 2003 From: pioppo at ferrara.linux.it (Simone Piunno) Date: Fri Feb 7 14:28:00 2003 Subject: [Mailman-Developers] archive html In-Reply-To: <3E4316C3.2080507@gregsteele.net> References: <3E4316C3.2080507@gregsteele.net> Message-ID: <20030207192608.GC3087@ferrara.linux.it> On Thu, Feb 06, 2003 at 07:15:31PM -0700, greg steele wrote: > ok... I did google and couldn't find any info about this.... > > Can I edit/re-write the archive pages to match the look/feel of the rest > of my site? > > anyone? bueller? look in templates/en/arch*.html -- Simone Piunno -- http://members.ferrara.linux.it/pioppo .------- Adde parvum parvo magnus acervus erit -------. Ferrara Linux Users Group - http://www.ferrara.linux.it Deep Space 6, IPv6 on Linux - http://www.deepspace6.net GNU Mailman, Mailing List Manager - http://www.list.org `-------------------------------------------------------' From david at midrange.com Fri Feb 7 13:55:29 2003 From: david at midrange.com (David Gibbs) Date: Fri Feb 7 15:03:09 2003 Subject: [Mailman-Developers] Messages going through as attachments Message-ID: I recently updated to the latest CVS (based on Tokio Kikuchi's advice) to fix some digest issues ... most things are working fine, but some messages are coming through as attachments instead of plain text. Any ideas why this would be? Thanks! david From david at midrange.com Fri Feb 7 14:46:46 2003 From: david at midrange.com (David Gibbs) Date: Fri Feb 7 15:52:18 2003 Subject: [Mailman-Developers] Subject's being mangled Message-ID: Folks: I've noticed some odd behavior in the latest CVS that I updated to ... the subject line is being treated as if it's blank. Here's an example of a message that was processed by one of my lists ... > Content-Type: text/plain; charset="US-ASCII" > X-Content-Filtered-By: Mailman/MimeDel 2.1+ > Subject: > Re: V4R4 to V5R1 upgrade [was Re: Off-topic, and not sorry one iota] > X-BeenThere: midrange-l@midrange.com > X-Mailman-Version: 2.1+ > Precedence: list Notice that the subject is on a seperate line. This list does NOT have a prefix configured. Any ideas? Thanks! david From tkikuchi at is.kochi-u.ac.jp Sat Feb 8 06:28:59 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Fri Feb 7 16:29:14 2003 Subject: [Mailman-Developers] Subject's being mangled References: Message-ID: <3E44251B.3020007@is.kochi-u.ac.jp> David Gibbs wrote: >>X-Content-Filtered-By: Mailman/MimeDel 2.1+ >>Subject: >>Re: V4R4 to V5R1 upgrade [was Re: Off-topic, and not sorry one iota] > Notice that the subject is on a seperate line. > > This list does NOT have a prefix configured. Make sure your prefix is blank. Invisible space may cause this effect, I suspect. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From david at midrange.com Fri Feb 7 15:35:40 2003 From: david at midrange.com (David Gibbs) Date: Fri Feb 7 16:36:33 2003 Subject: [Mailman-Developers] Subject's being mangled In-Reply-To: <3E44251B.3020007@is.kochi-u.ac.jp> References: <3E44251B.3020007@is.kochi-u.ac.jp> Message-ID: <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> Tokio Kikuchi said: >> Notice that the subject is on a seperate line. >> This list does NOT have a prefix configured. > Make sure your prefix is blank. Invisible space may cause this > effect, I suspect. It happens on lists with subject prefixes also. david -- "Who said I couldn't have it all?" -B Gates From lists at konfido.de Fri Feb 7 22:40:44 2003 From: lists at konfido.de (Matthias Juchem) Date: Fri Feb 7 16:40:54 2003 Subject: [Mailman-Developers] qmail-to-mailman.py broken when using --with-var-prefix Message-ID: Hi. I have just added a tested patch (against 2.1.0) to the SF Mailman project. Problem: When using --with-var-prefix with configure, contrib/qmail-to-mailman.py gets broken because it does not know about the concept of a second directory. Fix: Instroduce new variable for var-prefix directory. There are 2 attachment. The older one is wrong, but I couldn't delete it. Regards, Matthias From tkikuchi at is.kochi-u.ac.jp Sat Feb 8 15:28:16 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sat Feb 8 01:28:45 2003 Subject: [Mailman-Developers] Subject's being mangled References: <3E44251B.3020007@is.kochi-u.ac.jp> <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> Message-ID: <3E44A380.3050308@is.kochi-u.ac.jp> David Gibbs wrote: > Tokio Kikuchi said: > >>>Notice that the subject is on a seperate line. >>>This list does NOT have a prefix configured. >> >>Make sure your prefix is blank. Invisible space may cause this >>effect, I suspect. Sorry but how about putting a space in your blank prefix. (effect is reverse, now I suppose) > > > It happens on lists with subject prefixes also. Hmm, could you show me an example? -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From david at midrange.com Sat Feb 8 07:20:21 2003 From: david at midrange.com (David Gibbs) Date: Sat Feb 8 08:21:12 2003 Subject: [Mailman-Developers] Subject's being mangled In-Reply-To: <3E44A380.3050308@is.kochi-u.ac.jp> References: <3E44251B.3020007@is.kochi-u.ac.jp> <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> Message-ID: <5.2.0.9.2.20030208071910.032a8708@linux.midrange.com> >>It happens on lists with subject prefixes also. >Hmm, could you show me an example? Here's one ... >Sensitivity: >To: interlug@midrange.com >X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 >Message-ID: >From: "Jennifer Alten" >Date: Fri, 7 Feb 2003 10:06:50 -0600 >X-MIMETrack: Serialize by Router on Notes1/xxxxxxx(Release 5.0.11 |July 24, > 2002) at 02/07/2003 10:07:27 AM >MIME-Version: 1.0 >Content-type: text/plain; charset=us-ascii >X-MailScanner: Found to be clean >Subject: [Interlug] > Get COMMON's web banner... and "March 9-13 in Indy" materials >X-BeenThere: interlug@midrange.com >X-Mailman-Version: 2.1+ >Precedence: list >Reply-To: interlug@midrange.com >List-Id: >List-Unsubscribe: , > >List-Archive: >List-Post: >List-Help: >List-Subscribe: , > >Sender: interlug-bounces@midrange.com >Errors-To: interlug-bounces@midrange.com -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | We're not in the middle of nowhere... | we're on the outskirts of everywhere! | - DMRoth (adapted) From tkikuchi at is.kochi-u.ac.jp Sun Feb 9 08:41:50 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sat Feb 8 18:42:07 2003 Subject: [Mailman-Developers] Subject's being mangled References: <3E44251B.3020007@is.kochi-u.ac.jp> <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> <5.2.0.9.2.20030208071910.032a8708@linux.midrange.com> Message-ID: <3E4595BE.4020304@is.kochi-u.ac.jp> >>> It happens on lists with subject prefixes also. >> >> Hmm, could you show me an example? > > Here's one ... > >> Subject: [Interlug] >> Get COMMON's web banner... and "March 9-13 in Indy" materials This makes no problem, I believe. Try putting a white space or deleting for no-subject_prefix case. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From barry at python.org Sat Feb 8 20:39:14 2003 From: barry at python.org (Barry A. Warsaw) Date: Sat Feb 8 20:39:38 2003 Subject: [Mailman-Developers] RELEASED Mailman 2.1.1 Message-ID: <15941.45378.536004.128513@gargle.gargle.HOWL> I've released Mailman 2.1.1 which includes many bug fixes and language updates. This release includes a fix for the cross-site scripting vulnerability, a fix for the cookie problem, any many other bugs. I recommend that all Mailman 2.1 users upgrade to this release. As usual, I've made both a full source tarball and a patch file available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarballs. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=97760 Note that applying the patch does /not/ completely update the language support. If you go the patch route, you will want to cd into the messages directory and run "make catalogs" before installing. This will only work if your OS has the necessary language tools installed. You don't need to do this if your lists are all English-only. If you have a problem, please download and install the full release. It is safe to install this over version 2.1. You can simply run configure the way you did for 2.1, then do a make install. Be sure you restart your mailman daemon by doing a "mailmanctl restart" after installing. See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.1.1 (08-Feb-2003) Lots of bug fixes and language updates. Also: - Closed a cross-site scripting vulnerability in the user options page. - Restore the ability to control which headers show up in messages included in plaintext and MIME digests. See the variables PLAIN_DIGEST_KEEP_HEADERS and MIME_DIGEST_KEEP_HEADERS in Defaults.py. - Messages included in the plaintext digests are now sent through the scrubber to remove (and archive) attachments. Otherwise, attachments would screw up plaintext digests. MIME digests include the attachments inline. From mrbill at mrbill.net Sat Feb 8 21:35:52 2003 From: mrbill at mrbill.net (Bill Bradford) Date: Sat Feb 8 22:43:50 2003 Subject: [Mailman-Developers] RELEASED Mailman 2.1.1 In-Reply-To: <15941.45378.536004.128513@gargle.gargle.HOWL> References: <15941.45378.536004.128513@gargle.gargle.HOWL> Message-ID: <20030209033552.GV316@mrbill.net> On Sat, Feb 08, 2003 at 08:39:14PM -0500, Barry A. Warsaw wrote: > If you have a problem, please download and install the full release. > It is safe to install this over version 2.1. You can simply run > configure the way you did for 2.1, then do a make install. Be sure > you restart your mailman daemon by doing a "mailmanctl restart" after > installing. I completely shut down postfix and mailman. Compiled 2.1.1, then did a make install. Now: mailman@ohno:~/bin> ./mailmanctl start Site list is missing: mailman Suggestions? I just broke some high-traffic lists. 8-( Bill -- bill bradford mrbill@mrbill.net austin, texas From mrbill at mrbill.net Sat Feb 8 21:45:17 2003 From: mrbill at mrbill.net (Bill Bradford) Date: Sat Feb 8 22:45:19 2003 Subject: [Mailman-Developers] RELEASED Mailman 2.1.1 In-Reply-To: <20030209033552.GV316@mrbill.net> References: <15941.45378.536004.128513@gargle.gargle.HOWL> <20030209033552.GV316@mrbill.net> Message-ID: <20030209034517.GW316@mrbill.net> > mailman@ohno:~/bin> ./mailmanctl start > Site list is missing: mailman > Suggestions? I just broke some high-traffic lists. 8-( Nevermind, I'm an idiot, and didnt read INSTALL thoroughly. Bill -- bill bradford mrbill@mrbill.net austin, texas From barry at python.org Sun Feb 9 00:08:55 2003 From: barry at python.org (Barry A. Warsaw) Date: Sun Feb 9 00:09:27 2003 Subject: [Mailman-Developers] RELEASED Mailman 2.1.1 References: <15941.45378.536004.128513@gargle.gargle.HOWL> <20030209033552.GV316@mrbill.net> Message-ID: <15941.57959.635188.401701@gargle.gargle.HOWL> >>>>> "BB" == Bill Bradford writes: | mailman@ohno:~/bin> ./mailmanctl start | Site list is missing: mailman bin/newlist mailman -Barry From tkikuchi at is.kochi-u.ac.jp Sun Feb 9 15:45:26 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sun Feb 9 01:45:45 2003 Subject: [Mailman-Developers] Subject's being mangled References: <3E44251B.3020007@is.kochi-u.ac.jp> <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> <5.2.0.9.2.20030208071910.032a8708@linux.midrange.com> <3E4595BE.4020304@is.kochi-u.ac.jp> Message-ID: <3E45F906.4050502@is.kochi-u.ac.jp> David, Try this patch. Tokio --- CookHeaders.py.orig Sun Feb 9 15:13:27 2003 +++ CookHeaders.py Sat Feb 8 15:06:46 2003 @@ -219,6 +219,8 @@ # tracked (e.g. internally crafted, delivered to a single user such as the # list admin). prefix = mlist.subject_prefix + if not prefix: + return subject = msg.get('subject', '') # Try to figure out what the continuation_ws is for the header if isinstance(subject, Header): From jarrell at vt.edu Sun Feb 9 09:40:26 2003 From: jarrell at vt.edu (Ron Jarrell) Date: Sun Feb 9 09:40:46 2003 Subject: [Mailman-Developers] RELEASED Mailman 2.1.1 In-Reply-To: <15941.57959.635188.401701@gargle.gargle.HOWL> References: <15941.45378.536004.128513@gargle.gargle.HOWL> <20030209033552.GV316@mrbill.net> Message-ID: <5.1.0.14.2.20030209093916.00abd180@lennier.cc.vt.edu> Hey, Barry, shouldn't Versions.py have gotten updated to say 2.1.1? cvs still says 2.1+, so it's not triggering update to run for 2.1 users. From david at midrange.com Sun Feb 9 09:43:57 2003 From: david at midrange.com (David Gibbs) Date: Sun Feb 9 10:52:00 2003 Subject: [Mailman-Developers] Subject's being mangled In-Reply-To: <3E45F906.4050502@is.kochi-u.ac.jp> References: <3E44251B.3020007@is.kochi-u.ac.jp> <12101.208.248.38.130.1044653740.squirrel@webmail.midrange.com> <5.2.0.9.2.20030208071910.032a8708@linux.midrange.com> <3E4595BE.4020304@is.kochi-u.ac.jp> Message-ID: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> Tokio: Didn't help ... it seems to have something to do with the length of the subject line. A long subject gets wrapped around to the next line of the message. david At 12:45 AM 2/9/2003, Tokio Kikuchi wrote: >David, > >Try this patch. > >Tokio > >--- CookHeaders.py.orig Sun Feb 9 15:13:27 2003 >+++ CookHeaders.py Sat Feb 8 15:06:46 2003 >@@ -219,6 +219,8 @@ > # tracked (e.g. internally crafted, delivered to a single user such > as the > # list admin). > prefix = mlist.subject_prefix >+ if not prefix: >+ return > subject = msg.get('subject', '') > # Try to figure out what the continuation_ws is for the header > if isinstance(subject, Header): -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | We're not in the middle of nowhere... | we're on the outskirts of everywhere! | - DMRoth (adapted) From david at midrange.com Sun Feb 9 11:38:03 2003 From: david at midrange.com (David Gibbs) Date: Sun Feb 9 12:38:45 2003 Subject: [Mailman-Developers] Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) In-Reply-To: <773FBBA7-3C54-11D7-A702-0003935622A2@terc.edu> References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> Message-ID: <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> At 11:32 AM 2/9/2003, Robby Griffin wrote: >>Didn't help ... it seems to have something to do with the length of the >>subject line. A long subject gets wrapped around to the next line of the >>message. >Hmm. Yes, it does. Perhaps you should have a look at RFC2822, section >2.2.3, and then try to identify a specific problem with subject wrapping. I have no problem with the subject getting wrapped ... however I do have a problem with the WAY the subject is getting wrapped. In the examples I posted, the messages entire subject was getting wrapped to another line ... it was not getting wrapped when the text exceeded a specific length. This has the affect of making most mail client software (that I'm using, Eudora and Squirrelmail) showing a blank subject or just the subject prefix. david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | We're not in the middle of nowhere... | we're on the outskirts of everywhere! | - DMRoth (adapted) From danny at terweij.nl Sun Feb 9 21:33:56 2003 From: danny at terweij.nl (Danny Terweij) Date: Sun Feb 9 15:34:13 2003 Subject: [Mailman-Developers] Message Encoding traceback fault 2.1.x Message-ID: <028201c2d07a$91982510$1e00a8c0@onsnet.org> Hi, with version 2.1+ and 2.1.1, I have some message encoding problems. This messages are stuck in /qfiles/shunt/ Logfile: Feb 09 19:34:15 2003 (2229) Uncaught runner exception: unknown encoding Feb 09 19:34:15 2003 (2229) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 75, in process prefix_subject(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in prefix_subject h.append(s, c) File "/usr/local/mailman/pythonlib/email/Header.py", line 243, in append s = s.encode(outcodec) LookupError: unknown encoding And this are only from a few users and always the same users! Other users doing fine.. The message is just a normal message from outlook express in HTML format (stationery's).. I dont get it why it goes in a shunt dir. After unshunting the message goes away with a subject line "NONE" So there is something changed between 2.1 and 2.1+ . Please change it back :) Danny Terweij From marilyn at deliberate.com Sun Feb 9 17:54:45 2003 From: marilyn at deliberate.com (Marilyn Davis) Date: Sun Feb 9 20:54:49 2003 Subject: [Mailman-Developers] Message-ID: nomail on asdfjkl; From marilyn at deliberate.com Sun Feb 9 18:01:52 2003 From: marilyn at deliberate.com (Marilyn Davis) Date: Sun Feb 9 21:01:54 2003 Subject: [Mailman-Developers] In-Reply-To: Message-ID: Geeso, don't you catch dummies like me? I'm sorry. Too tired. Packing to do. Marilyn From matthew.davis at dogpound.vnet.net Sun Feb 9 21:11:32 2003 From: matthew.davis at dogpound.vnet.net (Matthew Davis) Date: Sun Feb 9 21:11:02 2003 Subject: [Mailman-Developers] In-Reply-To: ; from marilyn@deliberate.com on Sun, Feb 09, 2003 at 05:54:45PM -0800 References: Message-ID: <20030209211132.A18014@dogpound.vnet.net> From a domain like that, I'd say that was no accident. (da do tish!) * Marilyn Davis (marilyn@deliberate.com) wrote: > nomail on asdfjkl; -- Matthew Davis http://dogpound.vnet.net/ What was sliced bread the greatest thing since? From tkikuchi at is.kochi-u.ac.jp Mon Feb 10 11:53:09 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sun Feb 9 21:55:25 2003 Subject: [Mailman-Developers] Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> Message-ID: <3E471415.4000001@is.kochi-u.ac.jp> > I have no problem with the subject getting wrapped ... however I do have > a problem with the WAY the subject is getting wrapped. > > In the examples I posted, the messages entire subject was getting > wrapped to another line ... it was not getting wrapped when the text > exceeded a specific length. This has the affect of making most mail > client software (that I'm using, Eudora and Squirrelmail) showing a > blank subject or just the subject prefix. MUA developers should take care the RFC. In RFC-2822, subject = "Subject:" unstructured CRLF unstructured = *([FWS] utext) [FWS] ..., any CRLF that appears in FWS is semantically "invisible." So, any MUA which treat the folding CR/LF as a meaningful line separation is not RFC compliant. I know it's weired but will take a lot of hacking because this is caused by email package on which mailman relies. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From david at midrange.com Sun Feb 9 22:36:34 2003 From: david at midrange.com (David Gibbs) Date: Sun Feb 9 23:38:42 2003 Subject: [Mailman-Developers] Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) In-Reply-To: <3E471415.4000001@is.kochi-u.ac.jp> References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> Message-ID: <5.2.0.9.2.20030209223501.00b1ac10@linux.midrange.com> At 08:53 PM 2/9/2003, Tokio Kikuchi wrote: >MUA developers should take care the RFC. In RFC-2822, >So, any MUA which treat the folding CR/LF as a meaningful line >separation is not RFC compliant. >I know it's weired but will take a lot of hacking because this is >caused by email package on which mailman relies. Well, this has never been a problem with mailman before ... so when it starts being a problem, I tend to blame the software that changed last ... and my mail client hasn't changed for a long time, and Mailman has changed recently. david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | We're not in the middle of nowhere... | we're on the outskirts of everywhere! | - DMRoth (adapted) From matthew.davis at dogpound.vnet.net Mon Feb 10 09:25:54 2003 From: matthew.davis at dogpound.vnet.net (Matthew Davis) Date: Mon Feb 10 09:25:19 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Solved! (Selective no archive message option) In-Reply-To: ; from je_mmd@kronos.honk.org on Mon, Feb 10, 2003 at 12:35:47AM -0500 References: Message-ID: <20030210092554.A20593@dogpound.vnet.net> * Jon Earle (je_mmd@kronos.honk.org) wrote: > http://kronos.honk.org/~jearle/files/mailman-noarchive.patch > > It's built for v2.1, but applies (with a few offset hunks) against 2.1.1). > > What this does is allow you to approve a message that has been held for > moderation (msg exceeds size limit for example) so it can be delivered, > but preventing it from being archived if the noarchive checkbox is > checked, thus saving disk space. This would be good for others to have. Submit a patch on sourceforge (http://sf.net/projects/mailman) -- Matthew Davis http://dogpound.vnet.net/ ... Clinton Economics: If 1+2=3 then 4+5=6. From doggabow at jackloren.com Mon Feb 10 06:04:32 2003 From: doggabow at jackloren.com (J. Alden Gillespy) Date: Mon Feb 10 10:35:33 2003 Subject: [Mailman-Developers] Mailman 2.1.1 bugs Message-ID: <200302101104.h1AB4Y48026963@smtp-server1.tampabay.rr.com> My provider, Hostmatix.com, claims "The mailman version 2.1.1 is having some bugs as our admin has confirmed it. We are waiting for the developers to provide us with the debugged version.". Any idea as to 1) what this problem is, and 2) if and when it will be fixed? I am in need of the "ban list" feature in MM 2.1.1, but these bugs that Hostmatix is having are hindering my list's functionality. J. Alden Gillespy (aka Dogga) Microsoft Beta Tester: - Office 11 - Content Management Server (CMS) 2002 - Systems Management Server (SMS) 2003 From je_mmd at kronos.honk.org Sun Feb 9 18:20:11 2003 From: je_mmd at kronos.honk.org (Jon Earle) Date: Mon Feb 10 10:36:05 2003 Subject: [Mailman-Developers] Puzzled; Selective no-archive patch. Message-ID: Working on a patch to MM 2.1 (easily patches 2.1.1 too), that will selectively not archive messages but am having trouble getting them to not go into the archive. Link to patch is here: http://kronos.honk.org/~jearle/files/noarchive.patch Essentially, I run a list where the members like to email pics and other funnies to each other. This is fine with me, but I'd rather they not go into the archive for obvious reasons. I made a change to the moderation screen to add a checkbox to not archive the particular message, or in the message list screen, to not archive all of them. Obviously, the approval of the moderator would be required to make the noarchive option work. I think I've got the various pieces in place in the admin screen, and I have the message metadata including a 'noarchive' entry. I then theorized that my next step would be to fiddle with Handlers/ToArchive.py (part of the qrunner?). I thought that by adding a check for the 'noarchive' entry in msgdata nr the top of the process method would do the trick, but no. Did a slight mod to Approve.py and still no luck. Not sure what do now and would appreciate any advice given. I've worked with C for a few years, learned Perl last Nov and this is my first foray into Python. Cheers! Jon --- Jon Earle SAVE FARSCAPE http://www.savefarscape.com/ From je_mmd at kronos.honk.org Mon Feb 10 00:35:47 2003 From: je_mmd at kronos.honk.org (Jon Earle) Date: Mon Feb 10 10:36:07 2003 Subject: [Mailman-Developers] Solved! (Selective no archive message option) Message-ID: I've fixed my own problem. I noticed a syntax error in Handlers/Approve.py. I figured it was the msg.get syntax, so I copied the format from a few lines above. No luck. After seriously scratching my head for a while, I noticed that the indentation in python blocks was done with spaces. I'd used tabs. Changed tabs to spaces and voila! I now have a working feature! You can grab the patch if you like from: http://kronos.honk.org/~jearle/files/mailman-noarchive.patch It's built for v2.1, but applies (with a few offset hunks) against 2.1.1). What this does is allow you to approve a message that has been held for moderation (msg exceeds size limit for example) so it can be delivered, but preventing it from being archived if the noarchive checkbox is checked, thus saving disk space. Cheers! Jon --- Jon Earle SAVE FARSCAPE http://www.savefarscape.com/ From m.zieger at zmi.at Mon Feb 10 03:30:40 2003 From: m.zieger at zmi.at (Michael Zieger) Date: Mon Feb 10 10:36:14 2003 Subject: [Mailman-Developers] Mailman 2.0.6 Message-ID: <200302100330.40055@zmi.at> Hi there, just a short question to Mailman 2.0.6 (rpm from SuSE7.3): I installed everything and created a list. After adding members, I sent an e-mail via kmail to the list. But the arriving e-mail does not contain any "list-id" headers. According to documentation, it should be there, but no, it's not. Do you know what could be the problem? BTW, looks like a great piece of software. I try with just one list now and if it's good, I'll implement it for my customers. thanks, michael -- // Michael Zieger, BSc.Ing. --- Zieger Michael EDV-L?sungen // http://www.zmi.at Tel: 0676/4156531 Linux 2.4.21 From ogi at fmi.uni-sofia.bg Mon Feb 10 15:52:49 2003 From: ogi at fmi.uni-sofia.bg (Ognyan Kulev) Date: Mon Feb 10 10:36:31 2003 Subject: [Mailman-Developers] Adding windows-1251 encoding Message-ID: <3E47AEB1.9090407@fmi.uni-sofia.bg> Hi, When a mail is sent with windows-1251 encoding something like the output of bug 649007[1] is written in the error log. After a short investigation I found that it should be possible to add windows-1251 encoding, because in Python 2.1 it is there (as 'cp1251'). I wasn't able to do it though. How can I add support for windows-1251 in Mailman 2.1.1 using python 2.1? [1] http://sourceforge.net/tracker/?func=detail&atid=100103&aid=649007&group_id=103 Regards -- Ognyan Kulev , "\"Programmer\"" From r.barrett at openinfo.demon.co.uk Fri Feb 7 08:21:15 2003 From: r.barrett at openinfo.demon.co.uk (Richard Barrett) Date: Mon Feb 10 10:36:39 2003 Subject: [Mailman-Developers] premature closure? (was Weirdness with 2.1) Message-ID: <5.1.1.6.0.20030207081914.03bceaf8@pop.ftel.co.uk> At 16:03 06/02/2003, Bryan Fullerton wrote: >On Thursday, February 6, 2003, at 10:45 AM, Bill Bradford wrote: > >>2.1 works fine for me, *except* >> >>When I go to http://mysite/mailman/admindb/, it asks for the >>list password. I give it, get the "held for moderation/approval" queue >>of messages, pick my choices on each, and hit submit. >> >>I then get the password auth page again, have to do it over, and hit >>submit *again*, then it "takes" and processes the messages per my >>admin choices. > >Are you running Mailman 2.1 and 2.0 lists in the same URI space? If so, >you're hitting bug #664466, which is fixed in CVS (and the bug closed, >so you won't see it if you browse open bugs in SourceForge). > >http://sourceforge.net/tracker/index.php?func=detail&aid=664466&group_id=103&atid=100103 > >Thanks, > >Bryan Am I alone in thinking that closing a bug report should only be done when the numbered release is made that incorporates the fix. Closing the bug when the fix goes into the CVS version only "hides" the existence of fixes for known bugs in the current production (numbered) release. It means that in trying to consider what might be applicable to the latest numbered release effectively all bug fixes, both open and closed have to checked. I would have thought that pending would be a better category for bugs whose fixes are in the CVS but not in the numbered release, with re-categorisation as closed when the fix appears in a numbered release. From r.barrett at openinfo.demon.co.uk Sat Feb 8 00:37:27 2003 From: r.barrett at openinfo.demon.co.uk (Richard Barrett) Date: Mon Feb 10 10:36:42 2003 Subject: [Mailman-Developers] Patching question In-Reply-To: Message-ID: <5.1.1.6.0.20030207221104.00ab0dc0@pop3.demon.co.uk> At 18:21 07/02/2003, Marilyn Davis wrote: >Hi Mailmen and Mailwomen, > >If I fix up a patch for 2.1 so that eVote works with it, some >administrators will want it and some won't. > >What happens when new Mailman patches come along for 2.1+? Will >I have to make a new patch for each patch? > >Please forgive my ignorance. > >Marilyn I have some enhancement patches for MM that have yet to be adopted for inclusion in the main development line; may never be. If it will help I'll describe how I've been doing things although the real Mailman developers may have a different take on things Thus far I have maintained my patches as follows: 1. When a new numbered or beta release of MM comes out I try applying my patches for the previous numbered release. 2. If it applies without complaint and tests out as working I just add a comment to the sourceforge page for the patch telling people that patch file name abc works with MM version x.y.z 3, If the patch will not apply without complaint or it fails my testing I fix things and generate a new version of the patch. I then upload the revised patch + a comment to the sourceforge page for the patch. Fixing things can include creating a whole new precursor patch if it is to correct a bug in the Mailman numbered release code that I've just tripped over rather than a defect in the code my patch adds. I normally generate the patches by doing a recursive diff between a directory structure of either the vanilla MM release or that + any necessary precursor patches applied, and the directory structure of the MM release plus my changes. I guess I could use RCS/CVS branches for some of this but thus far I haven't got my head round solving the problem that way. My current worst case is a patch #444884 which requires three precursor patches. #444879 which is an enhancement patch and #668685, which fixes a new bug that appeared in MM 2.1. Patch #44879 in turn depends on patch #661138 which fixes different issues that also appeared in MM 2.1 final. The patch generation sequence goes like this: diff -r -u -P mailman-2.1/ mailman-2.1-driver/ > driver-2.1-0.1.patch diff -r -u -P mailman-2.1/ mailman-2.1-tfix/ > templates-2.1-0.1.patch diff -r -u -P mailman-2.1-tfix/ mailman-2.1-index/ > indexing-2.1-0.1.patch diff -r -u -P mailman-2.1-index/ mailman-2.1-htdig/ > htdig-2.1-0.3.patch and the patch application sequence goes like this: zcat distributions/mailman-2.1.tgz | tar xf - mv mailman-2.1 mailman-2.1-run cd mailman-2.1-run/ patch -p1 < ../patches/current/driver-2.1-0.1.patch patch -p1 < ../patches/current/templates-2.1-0.1.patch patch -p1 < ../patches/current/indexing-2.1-0.1.patch patch -p1 < ../patches/current/htdig-2.1-0.3.patch The reason I've done things this way is I want to separate patches that add discrete chunks of enhancement from fixes to generic problems I've identified in baseline MM while developing the enhancements. This way I'm in with a shout of persuading Barry Warsaw to add the bug fixes to the Mailman CVS at some point, even if he won't accept the enhancements so readily. Hopefully, and over time, my patches to fix MM bugs go away even if I'm left with the maintenance of the enhancement patch(es). That's better than polluting my enhancement patches with general bug fix stuff and then having to rip that out if its fixed in a new numbered release. In the case of the example, I split my original work into a fairly generic patch #444879 and a more specialised one #444884. Again this was with the hope that the more generic patch had a better chance of making it into the CVS ahead of the more specialised stuff. I do not even attempt to publish patches for MM CVS; its too much like trying to shoot skeet with a rifle. As far as I'm concerned the sort of adventurous people that run from the CVS have to make do with patches for the most recent numbered (or beta) release and do their own manual fixing of rejected patch elements After fumbling around at the start, I adopted a patch file naming convention (see example) where the first number group is the version of Mailman the patch applies to and the second number group is the evolution/version number of the patch applicable to that MM version; adrift in sourceforge's repository is htdig-2.0.8-0.1.patch and htdig-2.0.13-0.4.patch, as well as the most recent htdig-2.1-0.3.patch. Its a bit of a chore maintaining patches for MM across new releases but I do it because I need the changes for my own use and the discipline of having to keep up to date and publish for other users is good for my soul. In practice it means I can build my MM server systems from cold almost automatically to the patch state I want them to run at (the patch application lines above come out of the script that does this). I've been trying to get out revised patches after just a few days of a new numbered or beta release hitting the stree, but not always with success. I do not know of any way of avoiding conflicts with other patches that people might want to apply to same version of MM as my patches. I make it clear if my patches have necessary precursors and aim for no problems/warnings when running the patch command. I take the view that if people are mixing and matching a lot of different patches and this leads to patch command warnings or errors, then the person concerned has to contribute to their own salvation; although I'm willing to advise or help. How big a problem this is depends on how pervasive your changes are; so far I seem to have been fairly lucky on this score. Sorry to rattle on at such length when you probably have all of this scoped out. Still, if its saves you some work along the way ... I had put your post to mailman-users to one side as a reminder to investigate eVote further. If the MM 2.1 version is likely to be available in the near future, it will suit me better than having to regress my test system to MM 2.0.13 in order to try out eVote. Best of luck. From rmg at terc.edu Sun Feb 9 12:32:30 2003 From: rmg at terc.edu (Robby Griffin) Date: Mon Feb 10 10:36:49 2003 Subject: [Mailman-Developers] Subject's being mangled In-Reply-To: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> Message-ID: <773FBBA7-3C54-11D7-A702-0003935622A2@terc.edu> On Sunday, Feb 9, 2003, at 10:43 US/Eastern, David Gibbs wrote: > Didn't help ... it seems to have something to do with the length of > the subject line. A long subject gets wrapped around to the next line > of the message. Hmm. Yes, it does. Perhaps you should have a look at RFC2822, section 2.2.3, and then try to identify a specific problem with subject wrapping. --Robby From sakalis at cti.gr Sat Feb 8 21:29:01 2003 From: sakalis at cti.gr (Giorgos Sakalis) Date: Mon Feb 10 10:37:03 2003 Subject: [Mailman-Developers] error at make install Message-ID: <3E455A7D.50703@cti.gr> I am trying to instal mailman 2.1 on an SGI O2. When I execute make install i get this error Creating language directory /usr/local/mailman/sv mkdir /usr/local/mailman/sv Cannot create directory "/usr/local/mailman/messages/de": File exists Cannot create /usr/local/mailman/messages/de/#inst.170827# - Not a directory *** Error code 2 (bu21) *** Error code 1 (bu21) Any ideas? From stone at hkust.se Tue Feb 11 04:07:02 2003 From: stone at hkust.se (Magnus Stenman) Date: Mon Feb 10 22:07:08 2003 Subject: [Mailman-Developers] stylesheet support (patch) Message-ID: <20030211030702.GA9904@hkust.se> I've patched my mailman 2.1.1 to accept an optional stylesheet config option. I modified the english templates with the stylesheet placeholder, and included a sample style sheet. Feel free to include it. patch attached below; in your mailman source dir, apply with patch -p1 < stylesheets.diff /magnus -- Magnus Stenman mailto:stone@hkust.se http://www.stenman.org Get it up, keep it up. Linux -- Viagra for your PC -------------- next part -------------- A non-text attachment was scrubbed... Name: stylesheets.diff.gz Type: application/x-gzip Size: 1809 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030211/ba0f2449/stylesheets.diff.bin From stone at hkust.se Tue Feb 11 04:35:39 2003 From: stone at hkust.se (Magnus Stenman) Date: Mon Feb 10 22:35:43 2003 Subject: [Mailman-Developers] stylesheet support (patch) In-Reply-To: <20030211030702.GA9904@hkust.se> References: <20030211030702.GA9904@hkust.se> Message-ID: <20030211033539.GA11103@hkust.se> Best way to find a bug is to send the code to a mailing list... The login page did not display the style sheet properly, revised patch follows. /magnus On Tue, Feb 11, 2003 at 04:07:02AM +0100, Magnus Stenman wrote: > I've patched my mailman 2.1.1 to accept an optional > stylesheet config option. -- Magnus Stenman mailto:stone@hkust.se http://www.stenman.org Get it up, keep it up. Linux -- Viagra for your PC -------------- next part -------------- A non-text attachment was scrubbed... Name: stylesheets.diff.gz Type: application/x-gzip Size: 2088 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030211/a6d61235/stylesheets.diff.bin From matthew.davis at dogpound.vnet.net Mon Feb 10 23:15:01 2003 From: matthew.davis at dogpound.vnet.net (Matthew Davis) Date: Mon Feb 10 23:14:18 2003 Subject: [Mailman-Developers] Mailman 2.0.6 In-Reply-To: <200302100330.40055@zmi.at>; from m.zieger@zmi.at on Mon, Feb 10, 2003 at 03:30:40AM +0100 References: <200302100330.40055@zmi.at> Message-ID: <20030210231501.C23686@dogpound.vnet.net> * Michael Zieger (m.zieger@zmi.at) wrote: > just a short question to Mailman 2.0.6 (rpm from SuSE7.3): As good as RPM's are, and how they make life a lot easier on a lot of software, mailman is a peice of software that works better installed from source. There's too much system dependent information that mailman relies on (mail gid & gid for cgi's to run for example). > I installed everything and created a list. After adding members, I sent > an e-mail via kmail to the list. But the arriving e-mail does not > contain any "list-id" headers. According to documentation, it should be > there, but no, it's not. Do you know what could be the problem? I can't answer this, I don't have a mailman 2.0.6 installation, but my guess in the version number lies the problem. > BTW, looks like a great piece of software. I try with just one list now > and if it's good, I'll implement it for my customers. I'd suggest implementing mailman 2.1.1 for your customers. It's a LOT nicer, a lot slicker, a lot cleaner, a lot more customizable, a lot more everything than <2.1. Good luck! And come back with any other questions, sorry I couldn't answer your list-id question, but since your this early in your experience, i'd be smarter to jump in with mailman 2.1.1 instead of 2.0.6. -- Matthew Davis http://dogpound.vnet.net/ Use your MasterCard to pay your Visa bill. From ogi at fmi.uni-sofia.bg Tue Feb 11 13:15:44 2003 From: ogi at fmi.uni-sofia.bg (Ognyan Kulev) Date: Tue Feb 11 06:15:58 2003 Subject: [Mailman-Developers] Re: Adding windows-1251 encoding In-Reply-To: <3E47AEB1.9090407@fmi.uni-sofia.bg> References: <3E47AEB1.9090407@fmi.uni-sofia.bg> Message-ID: <3E48DB60.9000505@fmi.uni-sofia.bg> Ognyan Kulev wrote: > When a mail is sent with windows-1251 encoding something like the output > of bug 649007[1] is written in the error log. I found a solution: In /usr/lib/python2.1/encodings/aliases.py (this is Debian) windows_1251 is added as an alias for cp1251. Keep up the good work! Regards -- Ognyan Kulev , "\"Programmer\"" From narnett at mccmedia.com Sat Feb 8 12:01:26 2003 From: narnett at mccmedia.com (Nick Arnett) Date: Tue Feb 11 14:55:28 2003 Subject: [Mailman-Developers] Odd message body "/root/8e8Ta4: Permission denied" (2.1b2) Message-ID: One of my list moderators accidentally approved a bit of spam to a list. The message that went to the subscribers contained nothing other than the line "/root/8e8Ta4: Permission denied" and the footer. In the Mailman error log, the entry for that message is "Feb 07 10:14:24 2003 (11930) HTML->text/plain error: 65280". So I'm assuming that conversion from HTML to text failed. And I suppose that this sort of thing just basically shouldn't go to the list. This happened with Mailman 2.1b2 on Redhat 7.0. I'm in the process of switching over to 2.1 on a new machine running RH 8.0, so I sent it to my test list there... which promptly kicked it back to me with a "Content filtered message notification." Thus, no real problem, I believe, but I offer this because it's slightly worrisome to see anything with "/root" showing up in a message that goes to the whole list. Nick -- Nick Arnett Phone/fax: (408) 904-7198 narnett@mccmedia.com From david at midrange.com Tue Feb 11 14:00:52 2003 From: david at midrange.com (David Gibbs) Date: Tue Feb 11 15:00:57 2003 Subject: [Mailman-Developers] Re: Odd message body "/root/8e8Ta4: Permission denied" (2.1b2) References: Message-ID: "Nick Arnett" wrote in message news:PHEDLIMPMIAGAEPEFBGCKEGLFHAA.narnett@mccmedia.com... > One of my list moderators accidentally approved a bit of spam to a list. > The message that went to the subscribers contained nothing other than the > line "/root/8e8Ta4: Permission denied" and the footer. Redhat & lynx, right? I've been meaning to put an FAQ entry up (as Barry asked me to, sorry). It has to do with the user that lynx runs under. Take a look at http://www.mail-archive.com/mailman-users@python.org/msg14584.html for more info. david From david at midrange.com Tue Feb 11 15:37:45 2003 From: david at midrange.com (David Gibbs) Date: Tue Feb 11 16:37:50 2003 Subject: [Mailman-Developers] Re: Subject's being mangled References: Message-ID: "David Gibbs" wrote in message news:b2165s$209$1@main.gmane.org... > I've noticed some odd behavior in the latest CVS that I updated to ... the > subject line is being treated as if it's blank. I have been able to determine a bit more information about the messages that are having the subjects mangled. 1. It only happens on messages that have very long subjects 2. When it happens, the entire subject is being put on a line by itself AFTER the subject header 3. The subject is being prefixed, on the next line, with a tab character. Here's an example: X-MailScanner: Found to be clean Subject: [Interlug] [tab]Get COMMON's web banner... and "March 9-13 in Indy" materials X-BeenThere: interlug@midrange.com (I replaced the actual tab character with [tab], in case it isn't obvious). Note: The *SAME* thing happened on a thread with the subject "Odd message body "/root/8e8Ta4: Permission denied" (2.1b2)" started by Nick Arnett in this mailing list. Does this help at all? david From rmg at terc.edu Tue Feb 11 17:42:50 2003 From: rmg at terc.edu (Robby Griffin) Date: Tue Feb 11 17:49:16 2003 Subject: [Mailman-Developers] Re: Subject's being mangled In-Reply-To: Message-ID: <266C4652-3E12-11D7-B928-00039383CAAE@terc.edu> On Tuesday, February 11, 2003, at 04:37 PM, David Gibbs wrote: > 3. The subject is being prefixed, on the next line, with a tab > character. Ah, this sounds like wrong behavior on Mailman's part. The next line of a wrapped subject should be prefixed with nothing, i.e., it should begin simply with whatever whitespace character followed the wrap point in the original subject line. Usually a single space. To use a tab means that an RFC-compliant MUA will display the unfolded subject with a tab (instead of the original amount of whitespace) at the wrap point. Apple Mail and Lotus Notes do this. That still doesn't excuse your MUA's decision to just drop the wrapped text on the floor. Please consider reporting any such bugs to their authors as well. --Robby From rmg at terc.edu Tue Feb 11 18:00:14 2003 From: rmg at terc.edu (Robby Griffin) Date: Tue Feb 11 18:06:39 2003 Subject: [Mailman-Developers] Re: Subject's being mangled In-Reply-To: <266C4652-3E12-11D7-B928-00039383CAAE@terc.edu> Message-ID: <94EEC4AA-3E14-11D7-B928-00039383CAAE@terc.edu> On Tuesday, February 11, 2003, at 05:42 PM, Robby Griffin wrote: > Ah, this sounds like wrong behavior on Mailman's part. The next line > of a wrapped subject should be prefixed with nothing, i.e., it should > begin simply with whatever whitespace character followed the wrap > point in the original subject line. Usually a single space. But wait, there's more. Mailman's wrapping the line _after_ a whitespace character instead of before. If you look closely, you'll see there's a space dangling at the end of the first line of the subject. Adding the tab on the next line makes the resulting header valid, but does actually add a tab to the content of the subject. --Robby From david at midrange.com Tue Feb 11 17:19:29 2003 From: david at midrange.com (David Gibbs) Date: Tue Feb 11 18:19:33 2003 Subject: [Mailman-Developers] Re: Re: Subject's being mangled References: <266C4652-3E12-11D7-B928-00039383CAAE@terc.edu> <94EEC4AA-3E14-11D7-B928-00039383CAAE@terc.edu> Message-ID: "Robby Griffin" wrote in message news:94EEC4AA-3E14-11D7-B928-00039383CAAE@terc.edu... > But wait, there's more. Mailman's wrapping the line _after_ a > whitespace character instead of before. If you look closely, you'll see > there's a space dangling at the end of the first line of the subject. > Adding the tab on the next line makes the resulting header valid, but > does actually add a tab to the content of the subject. I think the real issue is this: Why is Mailman reformatting the subject line in the first place? If the subject is too long to fit in a certian amount of space, then it's fine ... but there is *NO* space problem in the examples I have referenced. david From tanner at real-time.com Tue Feb 11 23:16:38 2003 From: tanner at real-time.com (Bob Tanner) Date: Wed Feb 12 00:11:46 2003 Subject: [Mailman-Developers] CORRUPT ARCHIVE FOR LIST: Redux Message-ID: <200302112316.38369.tanner@real-time.com> Getting the following error from mailman: Feb 11 21:50:35 2003 qrunner(2157): Traceback (innermost last): Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/Archiver.py", line 222, in ArchiveMail Feb 11 21:50:35 2003 qrunner(2157): h.close() Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/pipermail.py", line 306, in close Feb 11 21:50:35 2003 qrunner(2157): self.write_TOC() Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/HyperArch.py", line 896, in write_TOC Feb 11 21:50:35 2003 qrunner(2157): self.sortarchives() Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/HyperArch.py", line 834, in sortarchives Feb 11 21:50:35 2003 qrunner(2157): self.archives.sort(sf) Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/HyperArch.py", line 825, in sf Feb 11 21:50:35 2003 qrunner(2157): al=s.volNameToDate(a) Feb 11 21:50:35 2003 qrunner(2157): File "/var/mailman/Mailman/Archiver/HyperArch.py", line 820, in volNameToDate Feb 11 21:50:35 2003 qrunner(2157): return time.mktime((year,month,1,0,0,0,0,1,-1)) Feb 11 21:50:35 2003 qrunner(2157): OverflowError: mktime argument out of range Feb 11 21:50:35 2003 (2157) CORRUPT ARCHIVE FOR LIST: the-list mailman-2.0.13-1 python-1.5.2-38 Redhat-7.3 Linux Followed the thread here: http://www.mail-archive.com/mailman-users@python.org/msg13602.html Tried to rebuild the archives, but still get the error message. Any other ideas? -- Bob Tanner | Phone : (952)943-8700 http://www.mn-linux.org, Minnesota, Linux | Fax : (952)943-8500 http://www.linuxjustworks.com | Linux Just Works! Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 From r.barrett at openinfo.demon.co.uk Wed Feb 12 08:18:10 2003 From: r.barrett at openinfo.demon.co.uk (Richard Barrett) Date: Wed Feb 12 03:19:23 2003 Subject: [Mailman-Developers] CORRUPT ARCHIVE FOR LIST: Redux In-Reply-To: <200302112316.38369.tanner@real-time.com> Message-ID: <5.1.1.6.0.20030212075718.03bf88d8@pop3.demon.co.uk> At 05:16 12/02/2003, Bob Tanner wrote: >Getting the following error from mailman: > >Feb 11 21:50:35 2003 qrunner(2157): Traceback (innermost last): >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/Archiver.py", line 222, in ArchiveMail >Feb 11 21:50:35 2003 qrunner(2157): h.close() >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/pipermail.py", line 306, in close >Feb 11 21:50:35 2003 qrunner(2157): self.write_TOC() >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/HyperArch.py", line 896, in write_TOC >Feb 11 21:50:35 2003 qrunner(2157): self.sortarchives() >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/HyperArch.py", line 834, in sortarchives >Feb 11 21:50:35 2003 qrunner(2157): self.archives.sort(sf) >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/HyperArch.py", line 825, in sf >Feb 11 21:50:35 2003 qrunner(2157): al=s.volNameToDate(a) >Feb 11 21:50:35 2003 qrunner(2157): File >"/var/mailman/Mailman/Archiver/HyperArch.py", line 820, in volNameToDate >Feb 11 21:50:35 2003 qrunner(2157): return >time.mktime((year,month,1,0,0,0,0,1,-1)) >Feb 11 21:50:35 2003 qrunner(2157): OverflowError: mktime argument out of >range >Feb 11 21:50:35 2003 (2157) CORRUPT ARCHIVE FOR LIST: the-list The reported error is that the time.mktime function is being called with a year value outside the range 1970 to 2038, that is outside the epoch known by the C functions for date handling on the platform. The question of why this date has cropped up is more difficult to determine. I would suspect that within the list's UNIX .mbox file, from which you are trying to rebuild the archive, is an email with a date on the From line preceding it which is out of range. To quote from the Python mailbox module documentation ",,, a classic Unix-style mailbox, where all messages are contained in a single file and separated by 'From '(a.k.a. 'From_') lines." I would try grepping the mbox file ($prefix/archives/private/.mbox/.mbox) and checking for problematic dates: grep "^From " .mbox | less If you find a From line with a problem date then use a text editor to change it. If my guess is correct,you still have the question of how this came about to answer. >mailman-2.0.13-1 >python-1.5.2-38 >Redhat-7.3 Linux > >Followed the thread here: > >http://www.mail-archive.com/mailman-users@python.org/msg13602.html > >Tried to rebuild the archives, but still get the error message. > >Any other ideas? > > >-- >Bob Tanner | Phone : (952)943-8700 >http://www.mn-linux.org, Minnesota, Linux | Fax : (952)943-8500 >http://www.linuxjustworks.com | Linux Just Works! >Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288 From chk at pobox.com Wed Feb 12 10:17:42 2003 From: chk at pobox.com (Harald Koch) Date: Wed Feb 12 10:41:55 2003 Subject: [Mailman-Developers] Re: CORRUPT ARCHIVE FOR LIST: Redux Message-ID: <12979.1045063062@persephone.cfrq.net> I have the same problem :-) In message <5.1.1.6.0.20030212075718.03bf88d8@pop3.demon.co.uk>, Richard Barrett writes: > > The reported error is that the time.mktime function is being called with a > year value outside the range 1970 to 2038, that is outside the epoch known > by the C functions for date handling on the platform. > > The question of why this date has cropped up is more difficult to determine. Yup. This happens irregularly for me, but once a "corrupt" message is in the archive.mbox file it is repeatable. I've looked at the message causing the problem (both in the queue files and in the archive .mbox file) and *I* can't see a poorly formatted date. Granted, my eyes aren't what they used to be. My error log and shunted qfiles are available at , if any developers want a test case for this bug (which is related to #610265). -- Harald Koch http://blog.cfrq.net/chk/ There is no problem, no matter how large or small, that cannot be solved by a suitable amount of high explosives. - Leo Graf, USS LaFarge, 2298 From tkikuchi at is.kochi-u.ac.jp Thu Feb 13 16:51:58 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 13 02:52:09 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Cc: to cc: weirdness References: <20030210173154.A29957@smartmonkey.org> Message-ID: <3E4B4E9E.1070308@is.kochi-u.ac.jp> Hi, I think this patch will work. https://sourceforge.net/tracker/index.php?func=detail&aid=685788&group_id=103&atid=300103 Cc-ing mailman-developers. Erik S.E. Walum wrote: > We've recently upgraded to Mailman2.1 and have noticed that Mailman is > now changing our Cc: headers and doing some RFC 2822 non-compliant > business with them. The original header might be: > > Cc: someuser@dom.ain, otheruser@dom.ain, lastuser@dom.ain > > when the message comes through to the list, the header has been altered > to: > > cc: someuser@dom.ain > cc: otheruser@dom.ain > cc: lastuser@dom.ain > > Can anyone help me out? -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From mentor at alb-net.com Fri Feb 14 12:36:25 2003 From: mentor at alb-net.com (Mentor Cana) Date: Fri Feb 14 12:36:29 2003 Subject: [Mailman-Developers] https vs. http Message-ID: With mailman 2.1, if I used https for secure access to access the admin site, example: https://www.alb-net.com/mailman/admin/ Clicking on one of the lists brings you do that list's login page, and the "https" stays "https" However, in 2.1.1, the "https" changes into "http". Was this an intentional modification of behavior between 2.1 and 2.1.1? How else can I ensure that all the sessions stay withing "https" if I access the admin page via "https". thanks, Mentor From lists at konfido.de Fri Feb 14 23:35:17 2003 From: lists at konfido.de (Matthias Juchem) Date: Fri Feb 14 17:35:23 2003 Subject: [Mailman-Developers] 'Charset "CHARSET"' warning when doing make catalogs Message-ID: (Repost to mailman-developers@python.org because I got no answer on mailman-users@python.org) Hi there. I just wanted to do a upgrade to 2.1.1. The release notes tell me to do a 'make catalogs' in messages/. This step is repeated for each language: ---snip--- msgfmt -o lt/LC_MESSAGES/mailman.mo lt/LC_MESSAGES/mailman.po Merging new template file with existing translations mv nl/LC_MESSAGES/mailman.po nl/LC_MESSAGES/mailman.po.old && msgmerge -o nl/LC_MESSAGES/mailman.po nl/LC_MESSAGES/mailman.po.old mailman.pot mailman.pot: warning: Charset "CHARSET" is not a portable encoding name. Message conversion to user's charset might not work. ............................................................................ ................................................ done. ---snip--- Can I safely ignore the warning? Regards, Matthias From pioppo at ferrara.linux.it Sat Feb 15 14:09:55 2003 From: pioppo at ferrara.linux.it (Simone Piunno) Date: Sat Feb 15 08:12:14 2003 Subject: [Mailman-Developers] 'Charset "CHARSET"' warning when doing make catalogs In-Reply-To: References: Message-ID: <20030215130955.GA3908@ferrara.linux.it> On Fri, Feb 14, 2003 at 11:35:17PM +0100, Matthias Juchem wrote: > msgfmt -o lt/LC_MESSAGES/mailman.mo lt/LC_MESSAGES/mailman.po > Merging new template file with existing translations > mv nl/LC_MESSAGES/mailman.po nl/LC_MESSAGES/mailman.po.old && msgmerge -o > nl/LC_MESSAGES/mailman.po nl/LC_MESSAGES/mailman.po.old mailman.pot > mailman.pot: warning: Charset "CHARSET" is not a portable encoding name. > Can I safely ignore the warning? in my experience yes, it works anyway, because mailman.pot is written in plain ascii. The original xgettext does the same but I think it should grow a command line option to declare the used charset (maybe defaulting to ascii). A possible patch: --- bin/pygettext.py 2003-02-15 13:46:49.000000000 +0100 +++ bin/pygettext.py.new 2003-02-15 14:05:03.000000000 +0100 @@ -175,7 +175,7 @@ "Last-Translator: FULL NAME \\n" "Language-Team: LANGUAGE \\n" "MIME-Version: 1.0\\n" -"Content-Type: text/plain; charset=CHARSET\\n" +"Content-Type: text/plain; charset=%(charset)s\\n" "Content-Transfer-Encoding: ENCODING\\n" "Generated-By: pygettext.py %(version)s\\n" @@ -336,7 +336,11 @@ timestamp = time.ctime(time.time()) # The time stamp in the header doesn't have the same format as # that # generated by xgettext... - print >> fp, pot_header % {'time': timestamp, 'version': __version__} + print >> fp, pot_header % { + 'time': timestamp, + 'charset': options.charset, + 'version': __version__ + } # Sort the entries. First sort each particular entry's keys, # then # sort all the entries by their first item. reverse = {} @@ -423,6 +427,7 @@ excludefilename = '' docstrings = 0 nodocstrings = {} + charset = 'US-ASCII' options = Options() locations = {'gnu' : options.GNU, @@ -435,6 +440,8 @@ usage(0) elif opt in ('-a', '--extract-all'): options.extractall = 1 + elif opt in ('--charset'): + options.charset = arg elif opt in ('-d', '--default-domain'): options.outfile = arg + '.pot' elif opt in ('-E', '--escape'): -- Simone Piunno -- http://members.ferrara.linux.it/pioppo .------- Adde parvum parvo magnus acervus erit -------. Ferrara Linux Users Group - http://www.ferrara.linux.it Deep Space 6, IPv6 on Linux - http://www.deepspace6.net GNU Mailman, Mailing List Manager - http://www.list.org `-------------------------------------------------------' From tkikuchi at is.kochi-u.ac.jp Sun Feb 16 17:10:41 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sun Feb 16 03:11:24 2003 Subject: [Mailman-Developers] Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> <3E471415.4000001@is.kochi-u.ac.jp> Message-ID: <3E4F4781.9080703@is.kochi-u.ac.jp> Hi, I've uploaded a patch for pythonlib/email/Header.py https://sourceforge.net/tracker/?func=detail&atid=384680&aid=687338&group_id=25568 patching in the install dir would be OK because the installer doesn't seem to overwrite it in the next make install of mailman. Tokio Kikuchi wrote: > >> I have no problem with the subject getting wrapped ... however I do >> have a problem with the WAY the subject is getting wrapped. >> >> In the examples I posted, the messages entire subject was getting >> wrapped to another line ... it was not getting wrapped when the text >> exceeded a specific length. This has the affect of making most mail >> client software (that I'm using, Eudora and Squirrelmail) showing a >> blank subject or just the subject prefix. > > > MUA developers should take care the RFC. In RFC-2822, > > subject = "Subject:" unstructured CRLF > unstructured = *([FWS] utext) [FWS] > ..., any CRLF that appears in FWS is semantically "invisible." > > So, any MUA which treat the folding CR/LF as a meaningful line > separation is not RFC compliant. > > I know it's weired but will take a lot of hacking because this is > caused by email package on which mailman relies. > -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From david at midrange.com Sun Feb 16 07:31:15 2003 From: david at midrange.com (David Gibbs) Date: Sun Feb 16 08:31:28 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> Message-ID: "Tokio Kikuchi" wrote in message news:3E4F4781.9080703@is.kochi-u.ac.jp... > I've uploaded a patch for pythonlib/email/Header.py > https://sourceforge.net/tracker/?func=detail&atid=384680&aid=687338&group_id =25568 > patching in the install dir would be OK because the installer > doesn't seem to overwrite it in the next make install of mailman. Ah, that didn't seem to help ... in fact, it seems to have made it somewhat worse. Here's what I would get BEFORE the patch ... ---------------------- From: David Gibbs Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Found to be clean Subject: [testlist] RE: FTP from QNTC prepends "?" to file name X-BeenThere: testlist@midrange.com X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Test List List-Id: Test List ---------------------- ... and here's what I get AFTER the patch ... ---------------------- From: David Gibbs Subject: [testlist] RE: FTP from QNTC prepends "?" to file name Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-MailScanner: Found to be clean X-BeenThere: testlist@midrange.com X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Test List List-Id: Test List ---------------------- As you can see, the list prefix is now put on the next line as well. david From david at midrange.com Sun Feb 16 07:56:43 2003 From: david at midrange.com (David Gibbs) Date: Sun Feb 16 08:56:49 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp><3E4F4781.9080703@is.kochi-u.ac.jp> Message-ID: Ack, this also happened ... ==> error <== Feb 16 07:55:49 2003 (12529) Uncaught runner exception: string index out of range Feb 16 07:55:49 2003 (12529) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 71, in process g.flatten(msg, unixfrom=1) File "/usr/local/mailman/pythonlib/email/Generator.py", line 100, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 135, in _write self._write_headers(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 165, in _write_headers text = '%s: %s' % (h, v) File "/usr/local/mailman/pythonlib/email/Header.py", line 183, in __str__ return self.encode() File "/usr/local/mailman/pythonlib/email/Header.py", line 480, in encode return self._encode_chunks(newchunks) File "/usr/local/mailman/pythonlib/email/Header.py", line 447, in _encode_chunks if len(chunks) >0 and chunks[-1][-1] in ' \t': IndexError: string index out of range "David Gibbs" wrote in message news:b2o3mm$mur$1@main.gmane.org... > "Tokio Kikuchi" wrote in message > news:3E4F4781.9080703@is.kochi-u.ac.jp... > > I've uploaded a patch for pythonlib/email/Header.py > > > https://sourceforge.net/tracker/?func=detail&atid=384680&aid=687338&group_id > =25568 > > patching in the install dir would be OK because the installer > > doesn't seem to overwrite it in the next make install of mailman. > > Ah, that didn't seem to help ... in fact, it seems to have made it somewhat > worse. > > Here's what I would get BEFORE the patch ... > > ---------------------- > From: David Gibbs > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii"; format=flowed > X-MailScanner: Found to be clean > Subject: [testlist] > RE: FTP from QNTC prepends "?" to file name > X-BeenThere: testlist@midrange.com > X-Mailman-Version: 2.1.1 > Precedence: list > Reply-To: Test List > List-Id: Test List > ---------------------- > > ... and here's what I get AFTER the patch ... > > ---------------------- > From: David Gibbs > Subject: > [testlist] RE: FTP from QNTC prepends "?" > to file name > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii"; format=flowed > X-MailScanner: Found to be clean > X-BeenThere: testlist@midrange.com > X-Mailman-Version: 2.1.1 > Precedence: list > Reply-To: Test List > List-Id: Test List > ---------------------- > > As you can see, the list prefix is now put on the next line as well. > > david From tkikuchi at is.kochi-u.ac.jp Mon Feb 17 08:44:07 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sun Feb 16 18:44:18 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of this subject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> Message-ID: <3E502247.2030503@is.kochi-u.ac.jp> How about applying this patch also https://sourceforge.net/tracker/?func=detail&atid=300103&aid=601117&group_id=103 David Gibbs wrote: > "Tokio Kikuchi" wrote in message > news:3E4F4781.9080703@is.kochi-u.ac.jp... > >>I've uploaded a patch for pythonlib/email/Header.py >> > > https://sourceforge.net/tracker/?func=detail&atid=384680&aid=687338&group_id > =25568 > >>patching in the install dir would be OK because the installer >>doesn't seem to overwrite it in the next make install of mailman. > > > Ah, that didn't seem to help ... in fact, it seems to have made it somewhat > worse. > > Here's what I would get BEFORE the patch ... > > ---------------------- > From: David Gibbs > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii"; format=flowed > X-MailScanner: Found to be clean > Subject: [testlist] > RE: FTP from QNTC prepends "?" to file name > X-BeenThere: testlist@midrange.com > X-Mailman-Version: 2.1.1 > Precedence: list > Reply-To: Test List > List-Id: Test List > ---------------------- > > ... and here's what I get AFTER the patch ... > > ---------------------- > From: David Gibbs > Subject: > [testlist] RE: FTP from QNTC prepends "?" > to file name > Mime-Version: 1.0 > Content-Type: text/plain; charset="us-ascii"; format=flowed > X-MailScanner: Found to be clean > X-BeenThere: testlist@midrange.com > X-Mailman-Version: 2.1.1 > Precedence: list > Reply-To: Test List > List-Id: Test List > ---------------------- > > As you can see, the list prefix is now put on the next line as well. > > david > From terri at zone12.com Mon Feb 17 14:37:57 2003 From: terri at zone12.com (Terri Oda) Date: Mon Feb 17 14:32:58 2003 Subject: [Mailman-Developers] Aliases with extra information Message-ID: <20030217193756.GA1028@ostraya.zone12.com> In 2.0, the mailman aliases used to include a little blob about who created the list and when it was made: ## tartparty mailing list ## created: 13-May-2002 terri But the new one doesn't do the second comment line... is there any reason for the change? It's hardly essential, but I found it handy to have that little bit of extra info auto-generated by mailman so my fellow sysadmins would just cut-and-paste it in. I'll probably just patch it in myself. I have to say, it's great that with an entire upgrade, that's the only little detail that irked me. :) Wish I could say that about all my upgrades! Terri From tkikuchi at is.kochi-u.ac.jp Tue Feb 18 16:20:50 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue Feb 18 02:21:25 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp><3E4F4781.9080703@is.kochi-u.ac.jp> Message-ID: <3E51DED2.1080301@is.kochi-u.ac.jp> David, Will you please send me the offending subject line. As to the other case, the problem you stated did not reproduce. > Subject: > [testlist] RE: FTP from QNTC prepends "?" > to file name Tokio David Gibbs wrote: > Ack, this also happened ... > > ==> error <== > Feb 16 07:55:49 2003 (12529) Uncaught runner exception: string index out of > range > Feb 16 07:55:49 2003 (12529) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop > self._onefile(msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in > _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in > _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 71, in > process > g.flatten(msg, unixfrom=1) > File "/usr/local/mailman/pythonlib/email/Generator.py", line 100, in > flatten > self._write(msg) > File "/usr/local/mailman/pythonlib/email/Generator.py", line 135, in > _write > self._write_headers(msg) > File "/usr/local/mailman/pythonlib/email/Generator.py", line 165, in > _write_headers > text = '%s: %s' % (h, v) > File "/usr/local/mailman/pythonlib/email/Header.py", line 183, in __str__ > return self.encode() > File "/usr/local/mailman/pythonlib/email/Header.py", line 480, in encode > return self._encode_chunks(newchunks) > File "/usr/local/mailman/pythonlib/email/Header.py", line 447, in > _encode_chunks > if len(chunks) >0 and chunks[-1][-1] in ' \t': > IndexError: string index out of range > "David Gibbs" wrote in message > news:b2o3mm$mur$1@main.gmane.org... > From danny at terweij.nl Tue Feb 18 12:25:58 2003 From: danny at terweij.nl (Danny Terweij) Date: Tue Feb 18 06:24:50 2003 Subject: [Mailman-Developers] Message Encoding traceback fault 2.1.x References: <028201c2d07a$91982510$1e00a8c0@onsnet.org> Message-ID: <037b01c2d740$8287eca0$1e00a8c0@onsnet.org> From: "Danny Terweij" > with version 2.1+ and 2.1.1, I have some message encoding problems. This > messages are stuck in /qfiles/shunt/ > Logfile: > Feb 09 19:34:15 2003 (2229) Uncaught runner exception: unknown encoding > Feb 09 19:34:15 2003 (2229) Traceback (most recent call last): > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop > self._onefile(msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in > _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in > _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 75, in > process > prefix_subject(mlist, msg, msgdata) > File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in > prefix_subject > h.append(s, c) > File "/usr/local/mailman/pythonlib/email/Header.py", line 243, in append > s = s.encode(outcodec) > LookupError: unknown encoding > And this are only from a few users and always the same users! Other users > doing fine.. > The message is just a normal message from outlook express in HTML format > (stationery's).. > I dont get it why it goes in a shunt dir. > After unshunting the message goes away with a subject line "NONE" ** Checked it now and it has no subject line after unshunting. just [list-name] > So there is something changed between 2.1 and 2.1+ . > Please change it back :) Still same error on current CVS 2.1.1+ is someone working on it? If someone wants the pickled shunted message and the error log then i send it to you . I added mailman/bin/unshunt at cronjob every minute to push the messages. I hope someone will respond to this and hopefully comes with a bugfix Danny Terweij From tkikuchi at is.kochi-u.ac.jp Tue Feb 18 21:31:10 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Tue Feb 18 07:31:17 2003 Subject: [Mailman-Developers] Message Encoding traceback fault 2.1.x References: <028201c2d07a$91982510$1e00a8c0@onsnet.org> <037b01c2d740$8287eca0$1e00a8c0@onsnet.org> Message-ID: <3E52278E.3000607@is.kochi-u.ac.jp> Hi, >> prefix_subject(mlist, msg, msgdata) >> File "/usr/local/mailman/Mailman/Handlers/CookHeaders.py", line 262, in >>prefix_subject >> h.append(s, c) >> File "/usr/local/mailman/pythonlib/email/Header.py", line 243, in append >> s = s.encode(outcodec) >>LookupError: unknown encoding Looks like the subject charset was unknown to python. What version are you using ? There was someone reporting on windows charset. > > I added mailman/bin/unshunt at cronjob every minute to push the messages. > I hope someone will respond to this and hopefully comes with a bugfix I think it is not a good idea because unshunted messages may come back again to shunt directory. You should fix the bug before unshunt (or somehow edit the message... I don't know how). -- Tokio From danny at terweij.nl Tue Feb 18 17:16:54 2003 From: danny at terweij.nl (Danny Terweij) Date: Tue Feb 18 11:16:00 2003 Subject: [Mailman-Developers] Message Encoding traceback fault 2.1.x References: <028201c2d07a$91982510$1e00a8c0@onsnet.org> <037b01c2d740$8287eca0$1e00a8c0@onsnet.org> <3E52278E.3000607@is.kochi-u.ac.jp> Message-ID: <03c401c2d769$274a8bd0$1e00a8c0@onsnet.org> From: "Tokio Kikuchi" To: "Danny Terweij" > >>LookupError: unknown encoding > Looks like the subject charset was unknown to python. > What version are you using ? There was someone reporting on > windows charset. Okay, i have: # python2 -V Python 2.1.1 On an RH 7.2 (nice, Mailman 2.1.1 and Python 2.1.1 :) ) > > I added mailman/bin/unshunt at cronjob every minute to push the messages. > > I hope someone will respond to this and hopefully comes with a bugfix > > I think it is not a good idea because unshunted messages may come back > again to shunt directory. You should fix the bug before unshunt (or > somehow edit the message... I don't know how). Well, the mesages arnt comming back :) they just go way now :) without subjectline. Lets update to latest python. i hope i can replace it without any problems... Thanx From barry at python.org Thu Feb 20 10:55:52 2003 From: barry at python.org (barry@python.org) Date: Thu Feb 20 10:56:01 2003 Subject: [Mailman-Developers] Alternative MemberAdaptors Message-ID: <15956.64136.366613.284548@gargle.gargle.HOWL> This message is primary for those of you writing or using alternative MemberAdaptor implementations (e.g. SQL). Yesterday I checked in a working implementation of a member adaptor based on BerkeleyDB. It seems to greatly improve the memory footprint for really huge lists, at the cost of greater administrative overhead (because you have to know how to setup and manage BerkeleyDBs), and potentially slower performance (I haven't benchmarked it; this is just based on my experience with BerkeleyDB in general). I've found a few things during this experience that point to things we ought to improve. I don't have a lot of time right now, but I wanted to put this out there to start the discussion. I'll quickly mention a few things. - I wanted to hook into the BDB transaction (txn) machinery, and I found a convenient hook. I overloaded MailList.Lock() to include a txn begin, MailList.Save() to do a txn commit, and MailList.Unlock() to do a txn abort. This seems to work well as long as aborting after committing is harmless (it is in BDB). I'd like to get feedback from the SQL folks (or other MemberAdaptor developers) on whether we need more explicit transaction support or whether the basically necessary hooks are already there. - To make this work, however, I found I had to change the order of when the extend.py hook gets run. Specifically, I needed it to run /before/ the list is locked in MailList.__init__(), otherwise locking contructors don't hook into the machinery. I want to commit this change but I don't want to break other MemberAdaptors or extend.py hooks. - We really need to optimize the MemberAdaptor API and the implementations that use them. Especially methods that return lists, e.g. getMembers() and friends. Right now, everything has to return a list, but I could do much better by returning iterators, because I can load my iterator up with a BDB cursor. This has the advantage of not requiring the entire member database to be loaded into memory just to iterate over it. Unfortunately, too much of the rest of the code assumes these methods return lists, and while I started to go down the iterator path, I backed out of it because of the complexity. There are other optimizations that would require a bit more thought. E.g. the admin's Membership List page seems to require that the entire member database be iterated over to chunkify and bucketize. Fixing this probably requires both changes to the u/i and changes to the interface. It also makes life more difficult for OldStyleMemberships, although BDBMemberAdaptor can probably be fairly easily elaborated. I'd like to hear from other member adaptor implementations on their thoughts here. - I'd love for any BerkeleyDB experts to review the BDBMemberAdaptor code, especially in some of the choices I've made for creating and opening the environment. I had a lot of practical problems with this part of the code, especially in getting multiple processes to cooperate reasonably. Any BerkeleyDB experts out there? (I'm fairly happy with the schemas, at least for the current MemberAdaptor API). - I'm leaning heavily toward having this stuff in Mailman 2.2 and /not/ porting it to 2.1.x. Too many changes for a micro release, although it makes project management more complicated, especially in merging fixes back into the 2.1.x maintenance branch. Sigh. Okay, I'm out of time for today. Any feedback will be appreciated, even if I can't respond immediately. Also, the BerkeleyDB based member adaptor seems to work, but should be considered experimental. See the BDBMemberAdaptor.py comments for how to hook this up to a mailing list. There is currently no migration tool from classic member adaptors to BDBMemberAdaptors, although I intend to write such a beast and run a few of my personal lists on the code to flesh things out. Enjoy, -Barry From chuqui at plaidworks.com Thu Feb 20 09:30:36 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Feb 20 12:30:42 2003 Subject: [Mailman-Developers] 2.1 traceback. Message-ID: <05B0E9E9-44F9-11D7-AD38-0003934516A8@plaidworks.com> Every so often I get a report of a posting sent to one of my lists that dissappears. I got two yesterday. Thanks to some detective work, I found one -- it got shunted because of a traceback: Feb 19 23:44:31 2003 (24496) Uncaught runner exception: sequence expected, NoneT ype found Feb 19 23:44:31 2003 (24496) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispos e self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 139, in process deliveryfunc(mlist, msg, msgdata, envsender, refused, conn) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 277, in verpdel iver d = {'bounces': bmailbox, TypeError: sequence expected, NoneType found This is someone that's able to post normally, so it's not a messed up mailer or anything. Anyone else seeing this? -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From chuqui at plaidworks.com Thu Feb 20 09:33:40 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Feb 20 12:33:44 2003 Subject: [Mailman-Developers] another traceback Message-ID: <73375654-44F9-11D7-AD38-0003934516A8@plaidworks.com> going through my error log, I see another, unrelated traceback. I have no idea what caused this one yet..... Feb 19 23:35:28 2003 (24496) Uncaught runner exception: please run connect() first Feb 19 23:35:28 2003 (24496) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 149, in process conn.quit() File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 79, in quit self.__conn.quit() File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From barry at python.org Thu Feb 20 12:36:41 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Feb 20 12:39:02 2003 Subject: [Mailman-Developers] 2.1 traceback. References: <05B0E9E9-44F9-11D7-AD38-0003934516A8@plaidworks.com> Message-ID: <15957.4649.628913.450499@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> This is someone that's able to post normally, so it's not a CVR> messed up mailer or anything. Anyone else seeing this? This is caused by a VERP delivery to an unqualified address, e.g. if a -request message comes in with a "From: aperson" header, the response can't be usefully VERPified. This should be fixed in 2.1.1 by discarding the outgoing message and logging an entry to logs/smtp. -Barry From chuqui at plaidworks.com Thu Feb 20 09:42:10 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Feb 20 12:42:19 2003 Subject: [Mailman-Developers] 2.1 traceback. In-Reply-To: <15957.4649.628913.450499@gargle.gargle.HOWL> Message-ID: On Thursday, February 20, 2003, at 09:36 AM, Barry A. Warsaw wrote: > >>>>>> "CVR" == Chuq Von Rospach writes: > > CVR> This is someone that's able to post normally, so it's not a > CVR> messed up mailer or anything. Anyone else seeing this? > > This is caused by a VERP delivery to an unqualified address, e.g. if a > -request message comes in with a "From: aperson" header, the response > can't be usefully VERPified. This should be fixed in 2.1.1 by > discarding the outgoing message and logging an entry to logs/smtp. > ah, okay. Except in this case, I believe the address was qualified. hang on, I'll go look. Here's the header of the message that died. Note this guy normally can post to the list... From bep@pinskyfamily.org Wed Feb 19 23:34:58 2003 Return-Path: Received: from spike-internal.pinskyfamily.org (spike.pinskyfamily.org [216.27.185.46]) by plaidworks.com (8.12.6/8.12.2) with ESMTP id h1K7YuSE028110; Wed, 19 Feb 2003 23:34:56 -0800 (PST) Received: from pinskyfamily.org (dhcp-172-16-77-97.pinskyfamily.org [172.16.77.97]) (authenticated bits=0) by spike-internal.pinskyfamily.org (8.12.7/8.12.7) with ESMTP id h1K7VlRs015996 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 19 Feb 2003 23:31:57 -0800 (PST) Message-ID: <3E548463.8000008@pinskyfamily.org> Date: Wed, 19 Feb 2003 23:31:47 -0800 From: Bruce Pinsky Reply-To: bep@pinskyfamily.org Organization: Pinsky Family User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuq Von Rospach CC: Sharks@plaidworks.com Subject: Re: Talk Radio: Talk to the Chuqster! References: <16CDE8D8-44A3-11D7-AD38-0003934516A8@plaidworks.com> In-Reply-To: <16CDE8D8-44A3-11D7-AD38-0003934516A8@plaidworks.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Status: R -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ But when that last guitar's been packed away You know that I still want to play So just make sure you got it all set to go Before you come for my piano From barry at python.org Thu Feb 20 13:24:10 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Feb 20 13:24:43 2003 Subject: [Mailman-Developers] another traceback References: <73375654-44F9-11D7-AD38-0003934516A8@plaidworks.com> Message-ID: <15957.7498.41915.828142@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> going through my error log, I see another, unrelated CVR> traceback. I have no idea what caused this one yet..... That's one's strange for sure. Does it happen just once? Are there any other error log entries before that that might be related? Any logs in your smtpd that might correlate? -Barry From terri at zone12.com Thu Feb 20 14:58:10 2003 From: terri at zone12.com (Terri Oda) Date: Thu Feb 20 14:52:45 2003 Subject: [Mailman-Developers] Documentation for 2.1 Message-ID: <20030220195810.GD936@ostraya.zone12.com> I've spent the past few days fighting with outdated Zope documentation and I got to thinking... has Mailman got updated docs for 2.1, or are people learning Mailman for the first time now suffering from the same "but that option doesn't exist in this version!" problems I'm having with Zope docs? A quick look at list.org only turned up 2.0 documentation last updated a few years ago, although at least the FAQ looks more recent. Are newer docs in the works, or are we waiting for volunteers? Because if it's the latter, I've got some time right now that's not being spent fighting with Zope, and I don't mind volunteering to write some up-to-date stuff for 2.1. I'm more of a coder than a writer, normally, but I've been doing a fair bit of writing lately and I've had to explain Mailman stuff to my list admins and users enough times that I should be good at this by now. :) I'd really hate for anyone to get the sort of negative impression of Mailman that I've gotten of Zope thanks to the documentation. So if none of this is already happening... where would be best to start? I'd guess the user guide would be the first step, since I know as an admin I'd like to be able to point my users at a guide. :) Terri PS - If anyone wants to point me to more up-to-date Zope docs, I'd be much obliged. :) From barry at python.org Thu Feb 20 15:21:30 2003 From: barry at python.org (Barry A. Warsaw) Date: Thu Feb 20 15:22:00 2003 Subject: [Mailman-Developers] Documentation for 2.1 References: <20030220195810.GD936@ostraya.zone12.com> Message-ID: <15957.14538.385723.403318@gargle.gargle.HOWL> >>>>> "TO" == Terri Oda writes: TO> I don't mind volunteering to write some up-to-date stuff for TO> 2.1. Fame and fortune awaits you Terri! A while back, I made a push towards writing the admin documentation, and the incomplete results can be found in CVS, under docs/mailman-admin.tex. That's in LaTeX using Python's mkhowto template. I'd like this to be the standard for Mailman's documentation because it's free, I already have the tool chain to build it, and I actually know it (as opposed to something like DocBook ;). You should be able to get all the mkhowto tools by either grabbing the Python 2.2.2 source distro, or downloading the LaTeX version of the Python documentation: http://www.python.org/doc/current/download.html I get it by checking out the Python cvs. My vision is that there be three separate documents, one for users, one for admins, and one for site admins. The former would describe such things as subscribing and unsubscribing, viewing the archives, editing user options, getting explicit password reminders, choosing languages and digest modes, etc. I agree that this is the most important document to write -- even though I didn't start with it -- because there are many more users in the world than list or site admins. The second document would describe everything an admin needs to know to run their lists, including email commands, approving posts and subscriptions, etc. This is the one I've started on. This is the second most important document. The third is for the site admin and should cover such issues as installation, integration, editing mm_cfg.py, etc. Lots of this material should be available in the various READMEs.y If you want to tackle the user guide, that would be wonderful. Definitely look at Chris Kolar's existing stuff, although I suspect lots of updates for 2.1 are necessary. Start by copying mailman-admin.tex and whacking out the text you don't need. Tell me what I can do to help. -Barry From chuqui at plaidworks.com Thu Feb 20 12:29:56 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Feb 20 15:30:08 2003 Subject: [Mailman-Developers] another traceback In-Reply-To: <15957.7498.41915.828142@gargle.gargle.HOWL> Message-ID: <134A29A9-4512-11D7-AD38-0003934516A8@plaidworks.com> On Thursday, February 20, 2003, at 10:24 AM, Barry A. Warsaw wrote: > >>>>>> "CVR" == Chuq Von Rospach writes: > > CVR> going through my error log, I see another, unrelated > CVR> traceback. I have no idea what caused this one yet..... > > That's one's strange for sure. Does it happen just once? Just happened again. Seems like my incoming SMTP goes away for some reason, and then mailman doesn't handle it quite right. *** ../../logs//post *** Feb 20 12:13:12 2003 (24496) post to sharks from xxx@rcn.com, size=2769, success *** ../../logs//bounce *** Feb 20 12:14:43 2003 (24493) sharks: xxx@pmfc.com already scored a bounce for today Feb 20 12:15:43 2003 (24493) sharks: xxx@ix.netcom.com already scored a bounce for today *** ../../logs//smtp *** Feb 20 12:17:01 2003 (24496) All recipients refused: (61, 'Connection refused') Feb 20 12:17:02 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:02 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:02 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:05 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:05 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:05 2003 (24496) All recipients refused: please run connect() first Feb 20 12:17:05 2003 (24496) All recipients refused: please run connect() first *** ../../logs//error *** Feb 20 12:17:05 2003 (24496) Uncaught runner exception: please run connect() first Feb 20 12:17:05 2003 (24496) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 149, in process conn.quit() File "/usr/local/mailman/Mailman/Handlers/SMTPDirect.py", line 79, in quit self.__conn.quit() File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 671, in quit self.docmd("quit") File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 352, in docmd self.putcmd(cmd,args) File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 308, in putcmd self.send(str) File "/BinaryCache/python/python-3.root~193/usr/lib/python2.2/smtplib.py", line 300, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Feb 20 12:17:05 2003 (24496) SHUNTING: 1045772208.148375+f793e73e6ea24d4fd7e4ae681fb86ebe3143f667 Hmm. Looks like I had a wave of spam come in,a nd I set the # of daemons on the listener port too low, so it stopped accepting connections, and if that happens in the middle of a batch (I have SMTP_MAX_SESSIONS_PER_CONNECTION = 2 set), mailman doesn't handle it right. if it fails opening a connection, it seems to be okay. RE-opening a connection seems to be this problem. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From RossBoylan at stanfordalumni.org Thu Feb 20 21:49:25 2003 From: RossBoylan at stanfordalumni.org (Ross Boylan) Date: Fri Feb 21 00:49:34 2003 Subject: [Mailman-Developers] Using mailman via an ISP Message-ID: <20030221054925.GE5567@wheat.boylan.org> Because I don't have access to an always connected server I can control, I've pursued the slightly eccentric strategy of trying to use mailman via a dial-up ISP. This ISP allows me to receive mail at rbrobot+xxxx@earthlink.net for arbitrary xxx, and I've hooked up exim on my Linux system to process it appropriately from there. Obviously, the web interface is usable only by me in this setup. I'm writing for several reasons: 1. I've done this by modifying mailman to put an arbitary prefix before the list name. If I ever get that working adequately, would there be interest in incorporating it into the main mailman? I will not be offended if the answer is "No, too esoteric." But I thought I'd ask as long as I'm doing it. 2. If anyone has any advice along the lines of don't abuse mailman to do this, use x instead, I'm all ears. Even better would be sites that would host some fairly low volume non-profit lists for free :) (One reason I'm looking into this is that I've been using topica, but their registration process has become increasingly intrusive.) 3. I have a number of specific questions about the code. a) Originally I found a few methods in MailList.py centered on getListAddress; I thought a change here would be enough. It's since become clear it's not, and judging by the number of uses of internal_name there may be a lot of code to change. I did not want to change internal_name directly because I was hoping to keep the undecorated name for some purposes (e.g., directory names on disk, program's own use, some identification). Seeing all the uses, I'm considering changing the code at internal_name() rather than trying to track down all the uses. Comments? b) I added DEFAULT_EMAIL_PREFIX to mm_config, with a default of an empty string. Is that an appropriate name for the variable? c) How do I make the prefix show up in the through the web pages, and how do I categorize it onto one of those pages? d) Am I going to get into trouble declaring the list to be in a domain different from the one I'm running on? (That is, I've told the list its DEFAULT_EMAIL_HOST is earthlink.net, though my local machine is in my own made up domain). e) Way down the line I might worry about eliminating references to the web site, since it's only usable by me. Short-term I just plan to put a welcome message saying "Don't try to use this over the web; it won't work." Is there any magic shortcut fixing that up? FYI I've also noted that the VERP regexps need to be massaged to compensate for the extra "+" in the email address. There is probably a clever way of quoting the prefix and incorporating it into the regexps automatically, but for now I did it manually. From dgc at uchicago.edu Fri Feb 21 12:25:37 2003 From: dgc at uchicago.edu (David Champion) Date: Fri Feb 21 13:26:03 2003 Subject: [Mailman-Developers] feature idea Message-ID: <20030221182537.GR15901@dust.uchicago.edu> Forgive me if this is already in there and I haven't noticed, but occasionally there's a situation where I think it would be useful for Mailman to support an address that would expand to all addresses currently listed as mailing list administrators. (It wouldn't be obligatory; you could just disable or overload that address if you don't want to support it, or there could be a config option.) Today I got a message at mailman-owner saying "we will be switching to EM for the new year, please send me information on the new listserve." Often I can figure out which of our 1600 lists something like this is for, but today I can't. It would be handy if mailman-owner could write to a list-owners address and ask if anyone recognizes the concept at work and knows what list they're looking for. Just an idea for the indefinite future. -- -D. dgc@uchicago.edu NSIT University of Chicago "The whole thrust of the text adventure was one picture was worth a thousand words and we would rather give you the thousand words." - Dave Lebling, Implementor From matthew.davis at dogpound.vnet.net Fri Feb 21 20:28:36 2003 From: matthew.davis at dogpound.vnet.net (Matthew Davis) Date: Fri Feb 21 20:26:57 2003 Subject: [Mailman-Developers] another traceback In-Reply-To: <134A29A9-4512-11D7-AD38-0003934516A8@plaidworks.com>; from chuqui@plaidworks.com on Thu, Feb 20, 2003 at 12:29:56PM -0800 References: <15957.7498.41915.828142@gargle.gargle.HOWL> <134A29A9-4512-11D7-AD38-0003934516A8@plaidworks.com> Message-ID: <20030221202836.A27950@dogpound.vnet.net> * Chuq Von Rospach (chuqui@plaidworks.com) wrote: > raise SMTPServerDisconnected('please run connect() first') > SMTPServerDisconnected: please run connect() first > > Feb 20 12:17:05 2003 (24496) SHUNTING: > 1045772208.148375+f793e73e6ea24d4fd7e4ae681fb86ebe3143f667 > > > Hmm. Looks like I had a wave of spam come in,a nd I set the # of > daemons on the listener port too low, so it stopped accepting > connections, and if that happens in the middle of a batch (I have > SMTP_MAX_SESSIONS_PER_CONNECTION = 2 set), mailman doesn't handle it > right. > > if it fails opening a connection, it seems to be okay. RE-opening a > connection seems to be this problem. I've encountered this error with local addresses. When mailman is communicating to the MTA and comes to an address that's invalid, the MTA closes the connection, but mailman trys to keep talking to the connection. At least that's what it appears to be on my end. -- Matthew Davis http://dogpound.vnet.net/ APATHY ERROR: Don't bother striking any key. From barry at python.org Fri Feb 21 20:58:29 2003 From: barry at python.org (Barry A. Warsaw) Date: Fri Feb 21 20:59:28 2003 Subject: [Mailman-Developers] EFF Mailing List Query Message-ID: <15958.55621.663963.264582@gargle.gargle.HOWL> FYI, >From the latest EFF mailer... -Barry -------------------- snip snip -------------------- * Mailing List Headaches? Contact us. EFF believes that delivery of legitimate e-mail needs to be carefully protected as a fundamental part of any solution to the spam problem. Unfortunately, we've lately learned that more and more opt-in mailing lists are being mislabeled as spam and wrongly blocked. EFF is looking for people who administer opt-in e-mail mailing lists and have had difficulty because their messages have been mislabeled as spam, causing delivery to fail. Our hope is to connect the folks facing this problem so that they can work together to find a global solution that both respects the Internet as a place of free speech (and e-mail as a vital organizing tool) while protecting Internet users and sysadmins from the problems that *real* spam causes. Contact mailinglistsheadaches@eff.org. From david at midrange.com Sat Feb 22 10:41:31 2003 From: david at midrange.com (David Gibbs) Date: Sat Feb 22 11:42:30 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of thissubject to see how it wraps) In-Reply-To: <3E51DED2.1080301@is.kochi-u.ac.jp> References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> <3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> Message-ID: <5.2.0.9.2.20030222103858.03337c58@linux.midrange.com> At 01:20 AM 2/18/2003, Tokio Kikuchi wrote: >Will you please send me the offending subject line. >As to the other case, the problem you stated did not reproduce. Tokio: Sorry it took so long to get back to you on this ... work got kind of hectic ... And example of a subject line that caused the problem is: "RE: FTP from QNTC prepends "?" to file name" I have a test list that exhibits this behavior every time setup on my system ... if you would like, I can subscribe you to that list so you can see the behavior yourself. david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | We're not in the middle of nowhere... | we're on the outskirts of everywhere! | - DMRoth (adapted) From tkikuchi at is.kochi-u.ac.jp Mon Feb 24 11:01:41 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Sun Feb 23 21:01:58 2003 Subject: [Mailman-Developers] Re: Subject's being mangled (I'm extendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> <3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> <5.2.0.9.2.20030222103858.03337c58@linux.midrange.com> Message-ID: <3E597D05.4000407@is.kochi-u.ac.jp> Hi, David Gibbs wrote: > At 01:20 AM 2/18/2003, Tokio Kikuchi wrote: > >> Will you please send me the offending subject line. >> As to the other case, the problem you stated did not reproduce. > > > Tokio: > > Sorry it took so long to get back to you on this ... work got kind of > hectic ... > > And example of a subject line that caused the problem is: "RE: FTP from > QNTC prepends "?" to file name" > Use of Latin-1 character in english list is a different matter. If the subscribers use these character in your list, then see http://mail.python.org/pipermail/mailman-users/2003-February/026558.html Tokio From barry at python.org Sun Feb 23 21:24:07 2003 From: barry at python.org (Barry A. Warsaw) Date: Sun Feb 23 21:24:31 2003 Subject: [Mailman-Developers] 2.1 traceback. References: <15957.4649.628913.450499@gargle.gargle.HOWL> Message-ID: <15961.33351.244094.853200@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: >> header, the response can't be usefully VERPified. This should >> be fixed in 2.1.1 by discarding the outgoing message and >> logging an entry to logs/smtp. CVR> ah, okay. Except in this case, I believe the address was CVR> qualified. CVR> hang on, I'll go look. Next time this happens, check the .db file (use bin/dumpdb). Specifically look at the "recips" key to see if there's an unqualified address (maybe it's coming from somewhere else). -Barry From barry at python.org Sun Feb 23 21:25:44 2003 From: barry at python.org (Barry A. Warsaw) Date: Sun Feb 23 21:26:05 2003 Subject: [Mailman-Developers] another traceback References: <15957.7498.41915.828142@gargle.gargle.HOWL> <134A29A9-4512-11D7-AD38-0003934516A8@plaidworks.com> Message-ID: <15961.33448.240713.874766@gargle.gargle.HOWL> CVR> Hmm. Looks like I had a wave of spam come in,a nd I set the # CVR> of daemons on the listener port too low, so it stopped CVR> accepting connections, and if that happens in the middle of a CVR> batch (I have SMTP_MAX_SESSIONS_PER_CONNECTION = 2 set), CVR> mailman doesn't handle it right. CVR> if it fails opening a connection, it seems to be CVR> okay. RE-opening a connection seems to be this problem. This looks like a bit of a pain to fix. Fortunately, once you fix your smtpd and you unshunt the messages, they'll get delivered as normal. Please submit a bug report on this though... -Barry From chuqui at plaidworks.com Tue Feb 25 07:38:24 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Tue Feb 25 10:39:11 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification Message-ID: <2D4D89E4-48D7-11D7-B4B5-0003934516A8@plaidworks.com> this is a bug in the bounce processing for Mailman 2.1 Begin forwarded message: > From: mailman@plaidworks.com > Date: Tue Feb 25, 2003 12:58:07 AM US/Pacific > To: sharks-owner@plaidworks.com > Subject: Bounce action notification > > This is a Mailman mailing list bounce action notice: > > List: sharks > Member: xxxx@hotmail.com > Action: Subscription disabled. > Reason: Excessive or fatal bounces. > > > > The triggering bounce notice is attached below. > > Questions? Contact the Mailman site administrator at > mailman@plaidworks.com. > > From: postmaster@mail.hotmail.com > Date: Tue Feb 25, 2003 12:50:14 AM US/Pacific > To: sharks-bounces+xxxx=hotmail.com@plaidworks.com > Subject: Delivery Status Notification (Delay) > > > This is an automatically generated Delivery Status Notification. > > THIS IS A WARNING MESSAGE ONLY. > > YOU DO NOT NEED TO RESEND YOUR MESSAGE. > > Delivery to the following recipients has been delayed. > > xxxx@hotmail.com > > > > Reporting-MTA: dns;mc10-s16.bay6.hotmail.com > Received-From-MTA: dns;mc10-f40.bay6.hotmail.com > Arrival-Date: Mon, 24 Feb 2003 12:49:41 -0800 > > Original-Recipient: > Final-Recipient: rfc822;xxxx@hotmail.com > Action: delayed > Status: 4.4.7 > Will-Retry-Until: Tue, 25 Feb 2003 12:49:41 -0800 -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ He doesn't have ulcers, but he's a carrier. From barry at python.org Tue Feb 25 10:49:47 2003 From: barry at python.org (Barry A. Warsaw) Date: Tue Feb 25 10:50:12 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification References: <2D4D89E4-48D7-11D7-B4B5-0003934516A8@plaidworks.com> Message-ID: <15963.37019.391315.508233@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> this is a bug in the bounce processing for Mailman 2.1 What's the bug? That we're registering a hard bounce score for warning messages? That's a feature. :) We "Precedence: list" on all our outgoing messages. MTAs that send delay warnings to such messages are broken. -Barry From chuqui at plaidworks.com Tue Feb 25 08:13:19 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Tue Feb 25 11:13:37 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <15963.37019.391315.508233@gargle.gargle.HOWL> Message-ID: <0DAD4E2E-48DC-11D7-B4B5-0003934516A8@plaidworks.com> you go tell hotmail to fix itself, Barry. Seems to me, since it's fairly easy to parse the "this is a warning message" stuff, we ought to. shrug. I guess. On Tuesday, February 25, 2003, at 07:49 AM, Barry A. Warsaw wrote: > >>>>>> "CVR" == Chuq Von Rospach writes: > > CVR> this is a bug in the bounce processing for Mailman 2.1 > > What's the bug? That we're registering a hard bounce score for > warning messages? That's a feature. :) > > We "Precedence: list" on all our outgoing messages. MTAs that send > delay warnings to such messages are broken. > > -Barry > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ No! No! Dead girl, OFF the table! -- Shrek From Daniel.Buchmann at bibsys.no Tue Feb 25 17:18:32 2003 From: Daniel.Buchmann at bibsys.no (Daniel Buchmann) Date: Tue Feb 25 11:19:25 2003 Subject: [Mailman-Developers] Hold-for-approval in MM 2.1 Message-ID: <1046189913.2728.6.camel@fornax.bibsys.no> Is there a way of specifying a list of addresses that is ALWAYS able to post to a list without their post being held for approval? How? Where? Adding email addresses to the "accept_these_nonmembers" is not enough, because other filters take precedence... Is there a way of rearranging filter appliance? How? Where? (Wasn't there a pipeline somewhere..? ;) -Daniel, tired of discarding spam and approving messages sent from addresses listed in accept_these_nonmembers... ;) -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: This is a digitally signed message part Url : http://mail.python.org/pipermail/mailman-developers/attachments/20030225/6944c68d/attachment.bin From dan.mick at sun.com Tue Feb 25 15:40:53 2003 From: dan.mick at sun.com (Dan Mick) Date: Tue Feb 25 18:43:02 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <0DAD4E2E-48DC-11D7-B4B5-0003934516A8@plaidworks.com> References: <0DAD4E2E-48DC-11D7-B4B5-0003934516A8@plaidworks.com> Message-ID: <3E5BFF05.1090108@sun.com> Chuq Von Rospach wrote: > you go tell hotmail to fix itself, Barry. ...or tell your users to drop that piece of crap. yes yes, I know, millions on the Internet, elitist attitude, yadda yadda. > Seems to me, since it's fairly > easy to parse the "this is a warning message" stuff, we ought to. It is? I've seen a *lot* of those sorts of messages. Every two-bit MTA admin in the world seems to want to customize his own. From chuqui at plaidworks.com Tue Feb 25 16:03:10 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Tue Feb 25 19:05:06 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <3E5BFF05.1090108@sun.com> Message-ID: On Tuesday, February 25, 2003, at 03:40 PM, Dan Mick wrote: > Chuq Von Rospach wrote: >> you go tell hotmail to fix itself, Barry. > > ...or tell your users to drop that piece of crap. > > yes yes, I know, millions on the Internet, elitist attitude, yadda > yadda. nah, it's even simpler: if I take a "me or him" attitude, chances are, they'll choose "him". Not a fight I want to take (I'm already having too much fun with AOL, as my blog will show. sigh. grump. I have better things to do), and not a fight I feel I can win. hotmail is a 500 pound gorilla. I leave tilting at windmills to the youngsters out there, and prefer quiet co-existance. >> Seems to me, since it's fairly easy to parse the "this is a warning >> message" stuff, we ought to. > > It is? > > I've seen a *lot* of those sorts of messages. Every two-bit MTA admin > in the world seems to want to customize his own. > In the bounce system I've been writing, I'm up to about 99.46% resolution, including throwing out of soft bounces like this (having recently whacked 3 million or so bounces down to 20,000, I think I've got a pretty good test sample, too). and half of what I can't process are @$#@%W%% first class bombosities. so yes, it's fairly easy. I doubt mailman can get QUITE to the level of processing I am, because I'm able to do some stuff you might not be able to get away with, but the answer to the general question is "i've already done it". -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ He doesn't have ulcers, but he's a carrier. From barry at python.org Tue Feb 25 22:19:38 2003 From: barry at python.org (Barry A. Warsaw) Date: Tue Feb 25 22:20:00 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification References: <15963.37019.391315.508233@gargle.gargle.HOWL> <0DAD4E2E-48DC-11D7-B4B5-0003934516A8@plaidworks.com> Message-ID: <15964.12874.197346.923262@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> you go tell hotmail to fix itself, Barry. Seems to me, since CVR> it's fairly easy to parse the "this is a warning message" CVR> stuff, we ought to. Dang, I forgot to read chapter 800 of the ISP handbook, "How to be a Friendly Gorilla". ;) Actually, this particular message appears to be a DSN, so it would be fairly trivial to ignore delayed actions. See line 48 of Mailman/Bouncers/DSN.py, and the commentary preceding that block. The patch might look something like the attached (untested). So the debate would be whether the current behavior is best, and if not whether this should be configurable. I tend to come down on the side of "yes", and "no". -Barry -------------------- snip snip -------------------- Index: DSN.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Bouncers/DSN.py,v retrieving revision 2.7 diff -u -r2.7 DSN.py --- DSN.py 2 Dec 2002 14:21:58 -0000 2.7 +++ DSN.py 26 Feb 2003 03:18:45 -0000 @@ -1,17 +1,17 @@ -# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software Foundation, Inc. +# Copyright (C) 1998-2003 by the Free Software Foundation, Inc. # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. -# +# # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. -# +# # You should have received a copy of the GNU General Public License -# along with this program; if not, write to the Free Software +# along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. """Parse RFC 1894 (i.e. DSN) bounce formats.""" @@ -20,6 +20,8 @@ from email.Utils import parseaddr from cStringIO import StringIO +from Mailman.BouncerAPI import Stop + def check(msg): @@ -39,13 +41,10 @@ # that for other purposes :( # # Also grok out Action so we can do something with that too. - action = msgblock.get('action', '') - # BAW: Should we treat delayed bounces the same? Yes, because if - # the transient problem clears up, they should get unbounced. The - # other problem is what to do about a DSN that has both delayed - # and failed actions in multiple header blocks? We're not - # architected to handle that. ;/ - if action.lower() not in ('failed', 'failure', 'delayed'): + action = msgblock.get('action', '').lower() + if action == 'delayed': + return Stop + if action not in ('failed', 'failure'): # Some non-permanent failure, so ignore this block continue params = [] From barry at python.org Tue Feb 25 22:25:03 2003 From: barry at python.org (Barry A. Warsaw) Date: Tue Feb 25 22:25:23 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification References: <3E5BFF05.1090108@sun.com> Message-ID: <15964.13199.139267.763351@gargle.gargle.HOWL> >>>>> "CVR" == Chuq Von Rospach writes: CVR> so yes, it's fairly easy. I doubt mailman can get QUITE to CVR> the level of processing I am, because I'm able to do some CVR> stuff you might not be able to get away with, but the answer CVR> to the general question is "i've already done it". Of course, Mailman can verp which takes the guesswork out of bounce processing. Even so, anything you can contribute to improve the non-verp bounce detection stuff would be appreciated. -Barry From chuqui at plaidworks.com Tue Feb 25 19:55:14 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Tue Feb 25 22:55:30 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <15964.13199.139267.763351@gargle.gargle.HOWL> Message-ID: <1CB29654-493E-11D7-86B5-0003934516A8@plaidworks.com> On Tuesday, February 25, 2003, at 07:25 PM, Barry A. Warsaw wrote: > Of course, Mailman can verp which takes the guesswork out of bounce > processing. Even so, anything you can contribute to improve the > non-verp bounce detection stuff would be appreciated. > that code's unfortunately not available. But on a more general basis, I found a couple of techniques really helped me here, against all but the most obnoxious bounce returns (i.e. first class): First, I now embed the user's email in the header in an X header, in two ways. One as the address, but also as a hashed string (MD5 hash, et al). I also use the hash in things like the unsubscribe links instead of the email address, because I've found the email address can cause issues of encoding on the way back, so you aren't always sure what to look for. the hash doesn't cause encoding issues. then when stuff comes back, in most cases, the X- headers come back as part of the bounce, almost as reliable as VERP. And if I can't find that, I try to find the unsubscribe/info strings in the message or footer, and see if I can find the hash. if I do, I have an easy match. Nice thing about the hash it can't be deconstructed, and it also doesn't get cloaked by privacy things, so even if you run into sites trying to do "useful" stuff with email addresses, you can still get usable information. the only place it fails is where people mailbot stuff and don't maintain any state from the original message (and those are relatively few, at least on a site/organizational level), and first class servers, but they're hopeless anyway. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Very funny, Scotty. Now beam my clothes down here, will you? From RossBoylan at stanfordalumni.org Wed Feb 26 12:53:21 2003 From: RossBoylan at stanfordalumni.org (Ross Boylan) Date: Wed Feb 26 15:55:30 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <15964.13199.139267.763351@gargle.gargle.HOWL> References: <3E5BFF05.1090108@sun.com> <15964.13199.139267.763351@gargle.gargle.HOWL> Message-ID: <20030226205321.GB6804@wheat.boylan.org> On Tue, Feb 25, 2003 at 10:25:03PM -0500, Barry A. Warsaw wrote: > > >>>>> "CVR" == Chuq Von Rospach writes: > > CVR> so yes, it's fairly easy. I doubt mailman can get QUITE to > CVR> the level of processing I am, because I'm able to do some > CVR> stuff you might not be able to get away with, but the answer > CVR> to the general question is "i've already done it". > > Of course, Mailman can verp which takes the guesswork out of bounce > processing. Even so, anything you can contribute to improve the > non-verp bounce detection stuff would be appreciated. > > -Barry > I thought VERP dealt with figuring out who a message was meant for, and that the problem here was distinguishing a warning message from a failure. Aren't those two separate issues? From tkikuchi at is.kochi-u.ac.jp Thu Feb 27 15:07:07 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 27 02:07:20 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman eating whitespaces in subject References: <20030227001727.GB17928@suse.de> Message-ID: <3E5DAB0B.8060900@is.kochi-u.ac.jp> I am Cc-ing this reply to mailman-developers because of update in pointers. Try these patch. /pythonlib/email/Header.py patch. Description; https://sourceforge.net/tracker/?func=detail&aid=687338&group_id=25568&atid=384680 Latest patch; https://sourceforge.net/tracker/download.php?group_id=25568&atid=384680&file_id=43598&aid=687338 Additionally, this patch for /Mailman/Handlers/CookHeaders.py for better prefixing subject (use number or not). Description; https://sourceforge.net/tracker/?func=detail&aid=601117&group_id=103&atid=300103 Latest patch for Mailman-2.1.1; https://sourceforge.net/tracker/download.php?group_id=103&atid=300103&file_id=43603&aid=601117 You should also check if your MUA is compliant to RFC-2822/2047. (Hmm, you are using Mutt/1.5.3i ...) Tokio Mads Martin Joergensen wrote: > Hey together, > > I found a weird bug in mailman-2.1.1. It seems mailman is removing > whitespaces from the subject line if the subject contains 8-bit > characters like ? ? or similar. > > Just try sending a mail to a testlist running mailman-2.1.1 with the > subject "Emne tekst p? email til flug listerne" and reply a couple of > times. It's eating spaces randomly. > > Subjects like "? ? ? and subject whitespaces" will also demonstrate it. > From ahu at ds9a.nl Sat Feb 22 15:28:35 2003 From: ahu at ds9a.nl (bert hubert) Date: Thu Feb 27 09:25:58 2003 Subject: [Mailman-Developers] [patch] INSTALL file contains errors in 2.1.1 Message-ID: <20030222142835.GA5057@outpost.ds9a.nl> These problems confused me somewhat: --- INSTALL.~ Sat Feb 22 15:17:19 2003 +++ INSTALL Sat Feb 22 15:19:27 2003 @@ -67,6 +67,9 @@ already in use, choose something else unique and see the --with-groupname below. + Make sure the 'mailman' user is in group 'mailman'! Otherwise + permission problems will ensue. + - Create an installation directory (called $prefix in the documentation that follows). All of the Mailman files will be installed under $prefix. Run "configure --help" for ways to @@ -337,6 +340,17 @@ % su - mailman % crontab crontab.in + - Create a "site-wide" mailing list. This is the one that + password reminders will appear to come from. Usually this + should be the "mailman" mailing list, but if you need to change + this, be sure to change the MAILMAN_SITE_LIST variable in + mm_cfg.py (see below). + + % bin/newlist mailman + + Follow the prompts, and see the README file for more + information. + - Start the Mailman qrunner daemon, by executing the following from the $prefix directory: @@ -388,18 +402,8 @@ add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) - - Create a "site-wide" mailing list. This is the one that - password reminders will appear to come from. Usually this - should be the "mailman" mailing list, but if you need to change - this, be sure to change the MAILMAN_SITE_LIST variable in - mm_cfg.py (see below). - - % bin/newlist mailman - - Follow the prompts, and see the README file for more - information. - - You should then subscribe yourself to the mailman list. + - You should then subscribe yourself to the mailman list created above. 5. Customize Mailman -- http://www.PowerDNS.com Open source, database driven DNS Software http://lartc.org Linux Advanced Routing & Traffic Control HOWTO http://netherlabs.nl Consulting From akuchlin at mems-exchange.org Mon Feb 10 20:10:54 2003 From: akuchlin at mems-exchange.org (Andrew Kuchling) Date: Thu Feb 27 09:26:07 2003 Subject: [Mailman-Developers] ng-arch: New list for discussing a better archiver Message-ID: I've started a mailing list, ng-arch, for design and development of a better mail archiving system. To subscribe go to: http://www.amk.ca/mailman/listinfo/ng-arch It would be nice if this new archiver's implementation can be suitable for inclusion with Mailman 2.2 (and can be implemented in time), but if that's not possible it might be a standalone project. --amk (www.amk.ca) BASSANIO: The world is still deceived with ornament. -- _The Merchant of Venice_, III, ii From esew at smartmonkey.org Fri Feb 14 14:12:51 2003 From: esew at smartmonkey.org (Erik S.E. Walum) Date: Thu Feb 27 09:26:20 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Cc: to cc: weirdness In-Reply-To: <3E4B4E9E.1070308@is.kochi-u.ac.jp>; from tkikuchi@is.kochi-u.ac.jp on Thu, Feb 13, 2003 at 04:51:58PM +0900 References: <20030210173154.A29957@smartmonkey.org> <3E4B4E9E.1070308@is.kochi-u.ac.jp> Message-ID: <20030214141251.B21536@smartmonkey.org> That worked! Thanks a lot for the help. Tokio Kikuchi uttered: > Hi, > > I think this patch will work. > https://sourceforge.net/tracker/index.php?func=detail&aid=685788&group_id=103&atid=300103 > > Cc-ing mailman-developers. > > Erik S.E. Walum wrote: > > We've recently upgraded to Mailman2.1 and have noticed that Mailman is > > now changing our Cc: headers and doing some RFC 2822 non-compliant > > business with them. The original header might be: > > > > Cc: someuser@dom.ain, otheruser@dom.ain, lastuser@dom.ain > > > > when the message comes through to the list, the header has been altered > > to: > > > > cc: someuser@dom.ain > > cc: otheruser@dom.ain > > cc: lastuser@dom.ain > > > > Can anyone help me out? > > > -- > Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp > http://weather.is.kochi-u.ac.jp/ > -- Erik Walum personal work 503.780.7492 From hchs at ns.sympatico.ca Fri Feb 14 21:09:11 2003 From: hchs at ns.sympatico.ca (Cody Harris) Date: Thu Feb 27 09:26:48 2003 Subject: [Mailman-Developers] Mailman Alternatives Message-ID: <5.2.0.9.0.20030214210649.009e8810@pop1.ns.sympatico.ca> Does anyone know of a site that would give out Mailman? I like the looks of mailman and how it works, but i have a win32 box. If not, are there any other Win32 compatible mailing list software like Mailman? Thanks alot! Check out http://vectec.net for all your hosting needs From JKeilholz at news-record.com Wed Feb 19 22:25:51 2003 From: JKeilholz at news-record.com (JKeilholz@news-record.com) Date: Thu Feb 27 09:28:01 2003 Subject: [Mailman-Developers] subscriber file Message-ID: <4AC40FD41A6F934DB6D739C27EF4A3D2026E47C9@NRMAIL.office.news-record.com> Hello All! I am trying to track down the file that contains the list of all subscribers. If some one can email me what name the file should have, I can track it down through SSH. Thanks! Have A Great Day! Joe Keilholz Online Technology Coordinator News & Record Interactive (336) 373-3488 http://www.gotriad.com http://www.news-record.com http://www.triadstyle.com From mailmanlist at haxial.com Tue Feb 11 02:58:04 2003 From: mailmanlist at haxial.com (Haxial) Date: Thu Feb 27 09:29:19 2003 Subject: [Mailman-Developers] HTML in digests Message-ID: <200302110258.h1B2w0v08377@mail021.syd.optusnet.com.au> Hello Fantastic work on Mailman, love it! But I think I found a bug. When Mailman collects emails to put them into a digest, it doesn't properly handle multipart MIME emails that contain both HTML and plain text. This means that when someone uses MS Outlook or another email program that sends multipart HTML + plain text, all the HTML crap is included in the digest email, which makes reading the digest a real chore. When forming the digest, Mailman should strip out any HTML parts, and leave only the plain text parts. Here are the relevant lines from an example of an email that had multipart HTML and plain text: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C2D148.1EA670B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 From simar at rodriguezmanuel.com.ar Wed Feb 19 14:52:23 2003 From: simar at rodriguezmanuel.com.ar (Manuel "SiMaR" Rodriguez) Date: Thu Feb 27 09:29:23 2003 Subject: [Mailman-Developers] API Mailman Message-ID: <04b601c2d83f$a8de37b0$7801a8c0@mmugar> Hi i am a new developer in Mailman. I need know if exist a function to retrive a admin password like.... oldpw = mlist.getMemberPassword(address) Thanks! PS: Sorry For my bad english SiMaR simar@rodriguezmanuel.com.ar --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 01/27/2003 From simar at rodriguezmanuel.com.ar Wed Feb 19 15:07:20 2003 From: simar at rodriguezmanuel.com.ar (Manuel "SiMaR" Rodriguez) Date: Thu Feb 27 09:29:28 2003 Subject: [Mailman-Developers] Admin Password & Unsubscribe Command Message-ID: <04ce01c2d841$bfbf89f0$7801a8c0@mmugar> Why i can't unsubscribe members ?? like in previous version ( 2.0.13 ) In previous version i send a mail to list-request@domain.com whith the follow command i the subject unsubscribe adminpassword address@domain2.com i try in this version unsubscribe adminpassword address=address@domain2.com and don't work PS: Sorry for my bad english SiMaR simar@rodriguezmanuel.com.ar --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 01/27/2003 From simar at rodriguezmanuel.com.ar Wed Feb 19 23:05:48 2003 From: simar at rodriguezmanuel.com.ar (Manuel "SiMaR" Rodriguez) Date: Thu Feb 27 09:29:36 2003 Subject: [Mailman-Developers] Unsubscribe & Admin Password Message-ID: <0b9c01c2d884$9726a490$7801a8c0@mmugar> I fix!! i modify de cmd_unsubscribe.py and this work ok now. I can unsubscribe members with de admin password SiMaR --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 01/27/2003 From Tony.Oger at devoteam.com Thu Feb 20 15:22:07 2003 From: Tony.Oger at devoteam.com (Tony.Oger@devoteam.com) Date: Thu Feb 27 09:29:53 2003 Subject: [Mailman-Developers] Mail Architecture Issue Message-ID: Hi and thanx to help me if you can. Here is my architecture Relay SMTP Architecture. | INTERNET | | ------------------------------------| FW |---- | | ------- | | LVS | | ------- | | | --------------- | | | | --------- --------- |-------------- | Relay | | Relay | | | SMTP | | SMTP | ------------ --------- --------- | Lotus | | internal | | mail | ------------ The LVS is a load-balancer that load-balance incoming ou outgoing SMTP traffic between each SMTP Relay Real Servers. system on both Relay SMTP : Exim 4 under linux There are routers and directors configured on those MX Relay Servers to relay Mail to my internal Mail Server (back office where are all the mailboxes) for all the domains it owns. (Winnt + Lotus Domino) I would like to install a Mailing List software because the one in Lotus Domino isn't very clean and easy to use. What i would like to do is to install for example mailman config which can dialog with the Domino LDAP Server to get all users list in the domains. My Problem is that i do not know where to install the mailman framework. Actually, it would be a bad idea to install it on SMTP Relay Server, i think, because, the database containing users list must be shared between those Servers and all configuration files need to be install as the software (as the aliases files) on each server. (Bad idea regarding administration). Do you have any architecture issue ? My intention was to create the mailing list in an other domain or sub-domains and on my relay smtp server just add a director to relay message to @ml.domain.com to another internal server running exim or postfix and mailman. In this case only one linux server has to be installed, and message addressed to the mailing lists will be forwarded to this mail server. What do you think of this architecture and your ideas to prevent isntalling mailman on each smtp relay server and as i cannot install it on the internal mail server which runs lotus ? Thanx Tony From mailman at strangelight.com Thu Feb 20 20:55:28 2003 From: mailman at strangelight.com (dancerboy) Date: Thu Feb 27 09:30:04 2003 Subject: [Mailman-Developers] experienced newbie here... Message-ID: Hello all! I've just been contracted to modify a specific mailman installation so that email addresses cannot be harvested by spammers. Rather than go and do the mods completely on my own, I decided it would make more sense to coordinate my efforts with the larger open-source developer community. About me: I've been writing code since I was 8 years old. I've done a *lot* of development in Perl; significant amounts in C++, Java, JavaScript, and PHP; and smaller amounts in quite a few other languages (Pascal, DCL, assembler, VB, etc.). I pick up computer languages *very* quickly, so I don't think I'll have any trouble learning enough Python to get this job done. However, I'm entirely new to this open-source collaboration thing -- I have only the vaguest idea of how to use CVS, for example -- so I hope someone can point me to the information I'll need so as not to make a complete ass of myself :) I noticed in the TODO list there was one item about creating a form interface to discourage email harvesting. Is there a more detailed spec for this project available? or has it not been nailed down any more than what's listed on the TODO page? I'm not sure if this will satisfy my client's requirements, but it seems to be a good place to start. -jason From simon at uow.edu.au Sat Feb 22 18:30:42 2003 From: simon at uow.edu.au (Simon Coggins) Date: Thu Feb 27 09:30:19 2003 Subject: [Mailman-Developers] Scrubber decode bug Message-ID: <20030222073042.GC3295@uow.edu.au> Hi, I've submitted a bug #691039 about a problem with a decode error in base64 and Scrubber.py. I've also supplied a patch #691055 that i think will fix the problem. Can someone tell me if the patch looks sane enough.. or make a new patch for it :) -- Simon Coggins (SAGE-AU Member) Email: simon@uow.edu.au Network and System Management Officer Phone: +61-2-4221-3775 Information Technology Systems (ITS) Mobile: 0408 115861 University of Wollongong, 2522, Australia Fax: +61-2-4229-1985 From rpao at paonet.org Wed Feb 26 14:19:10 2003 From: rpao at paonet.org (Roger C. Pao) Date: Thu Feb 27 09:30:31 2003 Subject: [Mailman-Developers] Feature request: Display "Your name" in Subscriber list Message-ID: <3E5D3D5E.6000403@paonet.org> I think it would be useful to be able to display the optional "Your name" in the Subscriber list together with the e-mail address. My list members use Traditional Chinese names which they know. The corresponding e-mail addresses, however, are a mystery to most members (including myself). Make it an option for those list managers who do not wish it displayed. The subscriber can always hide himself from the list, so it won't affect them either way. rp03 From mmj at suse.de Thu Feb 27 09:59:17 2003 From: mmj at suse.de (Mads Martin Joergensen) Date: Thu Feb 27 09:30:37 2003 Subject: [Mailman-Developers] Re: [Mailman-Users] Mailman eating whitespaces in subject In-Reply-To: <3E5DAB0B.8060900@is.kochi-u.ac.jp> References: <20030227001727.GB17928@suse.de> <3E5DAB0B.8060900@is.kochi-u.ac.jp> Message-ID: <20030227085917.GB18747@suse.de> * Tokio Kikuchi [Feb 27. 2003 07:07]: > I am Cc-ing this reply to mailman-developers because of update in pointers. > > Try these patch. Thanks. [snip URLs] > You should also check if your MUA is compliant to RFC-2822/2047. > (Hmm, you are using Mutt/1.5.3i ...) Mutt is compliant. -- Mads Martin Joergensen, http://mmj.dk "Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort?" -- A. P. J. From mikel at vintners.net Sun Feb 16 10:32:18 2003 From: mikel at vintners.net (Mike Lempriere) Date: Thu Feb 27 09:31:01 2003 Subject: [Mailman-Developers] Option to supress "msg has implicit dest" behaviour? Message-ID: <200302161832.h1GIWHB8001672@mail.vintners.net> I would really like to see an option to disable the "message has implicit destination" behaviour. Here's why: I run several lists for each of several Internet domains. I do this by having each list having a specific name which includes the domain, eg.: domain1-members domain2-members My sendmail virtusertable then has an entry to redirect "members" to the list: members@domain1.org members-domain1@vintners.net members@domain2.org members-domain2@vintners.net Thus, the list members need not include the redundant domain name in the list name: members@domain1.org works, as well as: members-domain1@domain1.org (Perhaps there's a better way to achieve this configuration, where mailman is serving multiple domains -- please feel free to point me in the right direction.) In majordomo this configuration worked just fine as it wasn't smart enough to care. mailman on the other hand, does a better job protecting its lists, and rightly disallows implicit addressing. For some lists I run, this is desirable behaviour. However, as described above, I'm willing to accept the tradeoff of not doing this checking in order to allow aliasing for some other lists. So, my feature request would be to add a checkbox on a config. page that allows control of this checking. Thanks for listening! -- Mike Lempriere; http://vintners.net/~mikel/ WA State resident: junk email prohibited by law: RCW19.190 & RCW19.86 From mal at lemburg.com Thu Feb 27 11:33:12 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 27 09:31:05 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <1CB29654-493E-11D7-86B5-0003934516A8@plaidworks.com> References: <1CB29654-493E-11D7-86B5-0003934516A8@plaidworks.com> Message-ID: <3E5DE968.8040908@lemburg.com> Chuq Von Rospach wrote: > > On Tuesday, February 25, 2003, at 07:25 PM, Barry A. Warsaw wrote: > >> Of course, Mailman can verp which takes the guesswork out of bounce >> processing. Even so, anything you can contribute to improve the >> non-verp bounce detection stuff would be appreciated. >> > > that code's unfortunately not available. > > But on a more general basis, I found a couple of techniques really > helped me here, against all but the most obnoxious bounce returns (i.e. > first class): > > First, I now embed the user's email in the header in an X header, in two > ways. One as the address, but also as a hashed string (MD5 hash, et al). > I also use the hash in things like the unsubscribe links instead of the > email address, because I've found the email address can cause issues of > encoding on the way back, so you aren't always sure what to look for. > the hash doesn't cause encoding issues. The hash idea sounds interesting, but how do you manage to convert the hash back to an email address ? I guess some simple email address mangling trick would give you the same effect, e.g. base64 encoding: >>> print 'mm(' + base64.encodestring('mal@lemburg.com') + ')' mm(bWFsQGxlbWJ1cmcuY29t) These kind of encodings could even be used in URLs and survive text->HTML->text conversion. -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Feb 27 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 33 days left EuroPython 2003, Charleroi, Belgium: 117 days left From K.Hansen at biostat.ku.dk Thu Feb 27 15:30:52 2003 From: K.Hansen at biostat.ku.dk (Kasper Daniel Hansen) Date: Thu Feb 27 09:31:09 2003 Subject: [Mailman-Developers] public archives and email adresses Message-ID: <200302271530.52927.K.Hansen@biostat.ku.dk> Hi I've recently created a mailing list with mailman and are quite satisfied. However I have one simple question/request: If I have public archives and a member of the list has a signature in their email reader, this signature is included in the archive. But - at least in my list - it is quite common for signatures to include the posters email adress which therefore are being made accesible on a public webpage. Is it possible to strip messages of the signature before they are being archived? If so - how? /Kasper From mal at lemburg.com Thu Feb 27 15:38:37 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 27 09:39:17 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <3E5DE968.8040908@lemburg.com> References: <1CB29654-493E-11D7-86B5-0003934516A8@plaidworks.com> <3E5DE968.8040908@lemburg.com> Message-ID: <3E5E22ED.5020900@lemburg.com> M.-A. Lemburg wrote: > I guess some simple email address mangling trick would give you > the same effect, e.g. base64 encoding: > > >>> print 'mm(' + base64.encodestring('mal@lemburg.com') + ')' > mm(bWFsQGxlbWJ1cmcuY29t) > > These kind of encodings could even be used in URLs and survive > text->HTML->text conversion. Here's some code and an example: import base64, re def encode_email_address(address, note=''): encoded = base64.encodestring(address + ' ' + note)[:-1] encoded = encoded.replace('=', '-') encoded = encoded.replace('+', '.') encoded = encoded.replace('/', '_') return 'mm(%s)' % encoded def decode_email_address_part(mangled_address): mangled_address = mangled_address.replace('-', '=') mangled_address = mangled_address.replace('.', '+') mangled_address = mangled_address.replace('_', '/') decoded = base64.decodestring(mangled_address) return decoded.split() message = """ From: postmaster@lemburg.com Date: Tue Feb 25, 2003 12:58:07 AM US/Pacific To: list-bounce@lists.egenix.com Subject: Bounce action notification The following message bounced. From: mailman@lemburg.com To: info@egenix.com ... _______________________________________________ %s %s """ % (encode_email_address('mailman@lemburg.com', 'sender'), encode_email_address('info@egenix.com', 'rcpt')) print 'Message:' print message print parser = re.compile('mm\(([0-9a-zA-Z-._]+)\)') def find_email_addresses(message, start=0, end=None): l = [] if end is None: end = len(message) while start < end: m = parser.search(message, start, end) if m is not None: address, note = decode_email_address_part(m.group(1)) l.append((note, address)) start = m.end() else: break return l addrs = find_email_addresses(message) print 'Found these email address in message:' for addr in addrs: print ' ', addr -- lemburg/tmp> python mangle_email_address.py Message: From: postmaster@lemburg.com Date: Tue Feb 25, 2003 12:58:07 AM US/Pacific To: list-bounce@lists.egenix.com Subject: Bounce action notification The following message bounced. From: mailman@lemburg.com To: info@egenix.com ... _______________________________________________ mm(bWFpbG1hbkBsZW1idXJnLmNvbSBzZW5kZXI-) mm(aW5mb0BlZ2VuaXguY29tIHJjcHQ-) Found these email address in message: ('sender', 'mailman@lemburg.com') ('rcpt', 'info@egenix.com') -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Feb 27 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 33 days left EuroPython 2003, Charleroi, Belgium: 117 days left From K.Hansen at biostat.ku.dk Thu Feb 27 15:48:20 2003 From: K.Hansen at biostat.ku.dk (Kasper Daniel Hansen) Date: Thu Feb 27 09:39:36 2003 Subject: [Mailman-Developers] experienced newbie here... In-Reply-To: References: Message-ID: <200302271548.20433.K.Hansen@biostat.ku.dk> On Fredag den 21. februar 2003 05:55, dancerboy wrote: > Hello all! > > I've just been contracted to modify a specific mailman installation > so that email addresses cannot be harvested by spammers. Rather than > go and do the mods completely on my own, I decided it would make more > sense to coordinate my efforts with the larger open-source developer > community. > > About me: I've been writing code since I was 8 years old. I've done > a *lot* of development in Perl; significant amounts in C++, Java, > JavaScript, and PHP; and smaller amounts in quite a few other > languages (Pascal, DCL, assembler, VB, etc.). I pick up computer > languages *very* quickly, so I don't think I'll have any trouble > learning enough Python to get this job done. However, I'm entirely > new to this open-source collaboration thing -- I have only the > vaguest idea of how to use CVS, for example -- so I hope someone can > point me to the information I'll need so as not to make a complete > ass of myself :) > > I noticed in the TODO list there was one item about creating a form > interface to discourage email harvesting. Is there a more detailed > spec for this project available? or has it not been nailed down any > more than what's listed on the TODO page? I'm not sure if this will > satisfy my client's requirements, but it seems to be a good place to > start. I'm a mailman newbie myself but please note that it is currently possible to prohibit email harvesting using the privacy options. If you in addition make the archive private (see my recent post) this ought to be good enough. Note that this is possible using the webinterface availible to the lists administrator (or using the comman line). If these options does not seem to be availible - are you sure you're running the newest version? /Kasper From chuqui at plaidworks.com Thu Feb 27 07:23:15 2003 From: chuqui at plaidworks.com (Chuq Von Rospach) Date: Thu Feb 27 10:23:32 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <3E5DE968.8040908@lemburg.com> Message-ID: <6475163C-4A67-11D7-A0F1-0003934516A8@plaidworks.com> On Thursday, February 27, 2003, at 02:33 AM, M.-A. Lemburg wrote: > The hash idea sounds interesting, but how do you manage to convert > the hash back to an email address ? you don't. Since I use a one-way hash (for various security reasons), you store the hash in the record with the email address, and then compare hashes. same general concept as an encrypted password. One reason you do that is so that people can't script your CGIs to extract your subscription list programmatically, since the hash gives them no hook to hack your cgis with. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.plaidworks.com/chuqui/blog/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From david at midrange.com Thu Feb 27 09:24:54 2003 From: david at midrange.com (David Gibbs) Date: Thu Feb 27 10:26:57 2003 Subject: [Mailman-Developers] Re: Re: Subject's being mangled (I'mextendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> <5.2.0.9.2.20030222103858.03337c58@linux.midrange.com> <3E597D05.4000407@is.kochi-u.ac.jp> Message-ID: "Tokio Kikuchi" wrote in message news:3E597D05.4000407@is.kochi-u.ac.jp... > Use of Latin-1 character in english list is a different matter. > If the subscribers use these character in your list, then see > http://mail.python.org/pipermail/mailman-users/2003-February/026558.html I don't think that the character set relates to how the subject is being wrapped ... look at this thread ... there are a bunch of TAB characters in the text that (IMHO) shouldn't be there. david From mal at lemburg.com Thu Feb 27 18:03:13 2003 From: mal at lemburg.com (M.-A. Lemburg) Date: Thu Feb 27 12:03:57 2003 Subject: [Mailman-Developers] Fwd: Bounce action notification In-Reply-To: <6475163C-4A67-11D7-A0F1-0003934516A8@plaidworks.com> References: <6475163C-4A67-11D7-A0F1-0003934516A8@plaidworks.com> Message-ID: <3E5E44D1.6060305@lemburg.com> Chuq Von Rospach wrote: > > On Thursday, February 27, 2003, at 02:33 AM, M.-A. Lemburg wrote: > >> The hash idea sounds interesting, but how do you manage to convert >> the hash back to an email address ? > > you don't. Since I use a one-way hash (for various security reasons), > you store the hash in the record with the email address, and then > compare hashes. same general concept as an encrypted password. Ah, ok. > One reason you do that is so that people can't script your CGIs to > extract your subscription list programmatically, since the hash gives > them no hook to hack your cgis with. So you have a third notion for identifying members... the hash address; in addition to LCE and KEY. Sounds like the data storage scheme needs an update :-) -- Marc-Andre Lemburg eGenix.com Professional Python Software directly from the Source (#1, Feb 27 2003) >>> Python/Zope Products & Consulting ... http://www.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ Python UK 2003, Oxford: 33 days left EuroPython 2003, Charleroi, Belgium: 117 days left From RossBoylan at stanfordalumni.org Thu Feb 27 11:44:46 2003 From: RossBoylan at stanfordalumni.org (Ross Boylan) Date: Thu Feb 27 14:46:29 2003 Subject: [Mailman-Developers] ng-arch: New list for discussing a better archiver In-Reply-To: References: Message-ID: <20030227194446.GC5806@wheat.boylan.org> On Mon, Feb 10, 2003 at 03:10:51PM -0500, Andrew Kuchling wrote: > I've started a mailing list, ng-arch, for design and development of a > better mail archiving system. To subscribe go to: > > http://www.amk.ca/mailman/listinfo/ng-arch > > It would be nice if this new archiver's implementation can be suitable > for inclusion with Mailman 2.2 (and can be implemented in time), but > if that's not possible it might be a standalone project. I've seen some discussion of integration with Zope or at least use of ZODB. I'm currently working away at a Zope product that has certain mailing list elements. The use of Zope would provide things like indexing and searching pretty directly. Are you thinking of moving in this direction, or can anyone comment on plans in this area? I know it would be a pretty big project to do a complete conversion. For example, the ZMailman project, as far as I can tell, contemplates only using Zope to generate HTML forms, but not to manage the underlying data of lists, users, and messages. From tkikuchi at is.kochi-u.ac.jp Fri Feb 28 09:02:16 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 27 19:02:30 2003 Subject: [Mailman-Developers] Re: Re: Subject's being mangled (I'mextendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com><5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com><3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> <5.2.0.9.2.20030222103858.03337c58@linux.midrange.com> <3E597D05.4000407@is.kochi-u.ac.jp> Message-ID: <3E5EA708.5040108@is.kochi-u.ac.jp> Have you tried my latest patch ? You should make sure that patched version is properly installed and restart mailmanctl. Tokio David Gibbs wrote: > "Tokio Kikuchi" wrote in message > news:3E597D05.4000407@is.kochi-u.ac.jp... > >>Use of Latin-1 character in english list is a different matter. >>If the subscribers use these character in your list, then see >>http://mail.python.org/pipermail/mailman-users/2003-February/026558.html > > > I don't think that the character set relates to how the subject is being > wrapped ... look at this thread ... there are a bunch of TAB characters in > the text that (IMHO) shouldn't be there. > > david From tkikuchi at is.kochi-u.ac.jp Fri Feb 28 09:24:24 2003 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu Feb 27 19:24:37 2003 Subject: [Mailman-Developers] Re: Re: Subject's being mangled (I'mextendeding the length of thissubject to see how it wraps) References: <5.2.0.9.2.20030209093300.036ec770@linux.midrange.com> <5.2.0.9.2.20030209113453.036d5e30@linux.midrange.com> <3E471415.4000001@is.kochi-u.ac.jp> <3E4F4781.9080703@is.kochi-u.ac.jp> <5.2.0.9.2.20030222103858.03337c58@linux.midrange.com> <3E597D05.4000407@is.kochi-u.ac.jp> <5.2.1.0.2.20030227181030.0379fa50@linux.midrange.com> Message-ID: <3E5EAC38.8030003@is.kochi-u.ac.jp> http://mail.python.org/pipermail/mailman-developers/2003-February/014854.html You could have searched the archive. David Gibbs wrote: > I'm sorry, I've lost track of patches. > > Things are crazy around here ... got code freeze at work in about 2 > weeks and we just found a major problem :( > > Can you refresh my memory? > > Thanks! > > david > > At 06:02 PM 2/27/2003, you wrote: > >> Have you tried my latest patch ? >> You should make sure that patched version is properly installed >> and restart mailmanctl. >> >> Tokio >> >> David Gibbs wrote: >> >>> "Tokio Kikuchi" wrote in message >>> news:3E597D05.4000407@is.kochi-u.ac.jp... >>> >>>> Use of Latin-1 character in english list is a different matter. >>>> If the subscribers use these character in your list, then see >>>> http://mail.python.org/pipermail/mailman-users/2003-February/026558.html >>>> >>> >>> >>> I don't think that the character set relates to how the subject is being >>> wrapped ... look at this thread ... there are a bunch of TAB >>> characters in >>> the text that (IMHO) shouldn't be there. >>> david >> >> >> >> >> >> _______________________________________________ >> Mailman-Developers mailing list >> Mailman-Developers@python.org >> http://mail.python.org/mailman/listinfo/mailman-developers > > > -- > | Internet: david@midrange.com > | WWW: http://david.fallingrock.net > | AIM: MidrangeMan > | > | We're not in the middle of nowhere... > | we're on the outskirts of everywhere! > | - DMRoth (adapted) > > From charlie at begeistert.org Fri Feb 28 13:54:02 2003 From: charlie at begeistert.org (Charlie Clark) Date: Fri Feb 28 07:53:13 2003 Subject: [Mailman-Developers] re: bounce action notification In-Reply-To: References: Message-ID: <20030228135402.1485.4@.1046426236.fake> On 2003-02-26 at 18:00:06 [+0100], mailman-developers-request@python.org wrote: > > Chuq Von Rospach wrote: > > you go tell hotmail to fix itself, Barry. > > ...or tell your users to drop that piece of crap. > > yes yes, I know, millions on the Internet, elitist attitude, yadda yadda. Actually it's worse than that it's counterproductive and that for two reasons: criticising the what a user uses is implied criticism of the user and this is not very friendly and as Chuq has pointed out may cause them to leave; more importantly, however, the big mail services are interested in having as good a relationship with list-servers as well. They like bounces as much as we do so they are really happy the fewer they get. Talking to the admins can be surprisingly helpful. I've got a list with a huge bias towards hotmail and will be talking to them about working together as well as possible. I'll post any useful response. Charlie From syed at mimos.my Fri Feb 28 03:36:11 2003 From: syed at mimos.my (syed) Date: Tue Mar 18 09:10:45 2003 Subject: [Mailman-Developers] installation path Message-ID: <3E5ED814.1A27698A@mimos.my> Hi! >From the documentation, the default installation path is /home/mailman. It is practical we install mailman in /home/mailman or we should install it at other location? (e.g /var/www/html) Or do you have special installation path to install mailman. I'm asking this silly question because i'm quiet confuse when other software(actually i'm trying to setup savannah) always asking me where is mailman cgi-bin path? Thanks, newbie -- Syed Ahmad Shazali Syed Abdullah Researcher, Open Source Development MIMOS Berhad, Malaysia http://opensource.mimos.my http://asiaosc.org