From danny@terweij.nl Sat Jun 1 10:47:31 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 1 Jun 2002 11:47:31 +0200 Subject: [Mailman-Developers] Wrong domain choosed when creating a new list (mm2.1b2) References: <009101c2042b$4f7b9840$1e00a8c0@onsnet.org> Message-ID: <01ca01c20951$59609ce0$1e00a8c0@onsnet.org> **Resend** Still no answer, somebody working on it? Or has a answer? ----- Original Message ----- From: "Danny Terweij" Sent: Saturday, May 25, 2002 10:32 PM Hi, These are my mm_cfg settings: DEFAULT_EMAIL_HOST = 'lnx.p-s.nl' DEFAULT_URL_HOST = 'www.p-s.nl' DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' DEFAULT_HOST_NAME = DEFAULT_URL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST VIRTUAL_HOST_OVERVIEW = 0 When i do creating a new list : ./newlist [root@lnx bin]# ./newlist Enter the name of the list: testlist-1 Enter the email of the person running the list: danny@terweij.nl Initial testlist-1 password: [aliases shown] Hit enter to notify testlist-1 owner... When i hit it and check my mailbox of danny@terweij.nl : mailman-admin@www.p-s.nl wrote: The mailing list `testlist-1' has just been created for you. The following is some basic information about your mailing list. It is using DEFAULT_URL_HOST or DEFAULT_HOST_NAME instead of DEFAULT_EMAIL_HOST. (in my case... the lists are not runing on www.p-s.nl, but on www.p-s.nl : 81 redirected internaly to my linux host lnx.p-s.nl) Where can i change this? Danny. From barry@zope.com Sat Jun 1 16:20:39 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 1 Jun 2002 11:20:39 -0400 Subject: [Mailman-Developers] Wrong domain choosed when creating a new list (mm2.1b2) References: <009101c2042b$4f7b9840$1e00a8c0@onsnet.org> <01ca01c20951$59609ce0$1e00a8c0@onsnet.org> Message-ID: <15608.58951.961775.311826@anthem.wooz.org> >>>>> "DT" == Danny Terweij writes: DT> **Resend** DT> Still no answer, somebody working on it? Or has a answer? Sorry, I'll plead for patience here. Lots of stuff on my plate at the moment, both work and home related. -Barry From noreply@sourceforge.net Sat Jun 1 17:08:32 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 01 Jun 2002 09:08:32 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-563328 ] confirmation strings don't work 2.1b2+ Message-ID: Bugs item #563328, was opened at 2002-06-01 16:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563328&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Marc Merlin (marcmerlin) Assigned to: Nobody/Anonymous (nobody) Summary: confirmation strings don't work 2.1b2+ Initial Comment: I'm using a CVS tree tha's up to date I got this mail (because my spamassassin is boucing the mails, and the list mostly gets spams). No big deal, except that the URL tells me the confirmation string is incorrect and even if I re-enter it in the "Otherwise, re-enter your confirmation string." page, it still doesn't work. What can I do to help debug this/provide more info? ----- Forwarded message from web-team-request@svlug.org ----- From: web-team-request@svlug.org To: me@domain X-List-Administrivia: yes Subject: confirm 834fdd960d02e8e77409e82c626b698f96fb434a Your membership in the mailing list web-team has been disabled due to excessive bounces. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. To re-enable your membership, you can simply respond to this message (leaving the Subject: line intact), or visit the confirmation page at http://lists.svlug.org/lists/confirm/web-team/834fdd960d02e8e77409e82c626b698f96 fb434a You can also visit your membership page at http://lists.svlug.org/lists/options/web-team/merlin%40svlug.org (...) ----- End forwarded message ----- ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563328&group_id=103 From totschnig.michael@uqam.ca Sat Jun 1 17:36:43 2002 From: totschnig.michael@uqam.ca (totschnig.michael@uqam.ca) Date: Sat, 01 Jun 2002 12:36:43 -0400 Subject: [Mailman-Developers] hide web interface from users and "Results of your email commands" Message-ID: Hello, I am sorry if my question is not appropriate here, but I am using mailman from CVS, and I imagine things work quite different on Mailman 2.0 and 2.1. I have a list that is a newsletter associated to a web site on another host as the one mailman is running, and we have a form for subscription on the web site, which simply sends an email to list-subscribe@host. Ideally we would like that the process would be the most simple possible for the users, and that she does not see all the details of ours mailman system. The only page from the mailman web interface, I would like to show them is the "Confirm subscription page" when they activate the "confirm cookie" URL. Once they have confirmed, I would like to redirect them immediately to the web site, instead of showing them the confirmation page. Unfortunately this page is not customizable via the admin interface, otherwise I could use a redirect meta tag, as I did succesfully with the main info page for the list. And I would like to suppress the "Results of your email commands" since it is considered redundant by many users, even if they subscribe by email, and for this list they do not send the email themselves, but is originated by a script on the web site. So my two questions are: - Can I suppress the "Results of your email commands" email for this list or alternatively for the whole site? - Is there a way to suppress most parts of the web-interface for a list. Thanks in advance, Michael From noreply@sourceforge.net Sat Jun 1 17:48:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 01 Jun 2002 09:48:51 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11 Message-ID: Bugs item #563336, was opened at 2002-06-02 00:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id=103 From danny@terweij.nl Sun Jun 2 03:28:28 2002 From: danny@terweij.nl (Danny Terweij) Date: Sun, 2 Jun 2002 04:28:28 +0200 Subject: [Mailman-Developers] Re: [Mailman-Users] "Host name this list prefers" References: <000801c209cb$b8f06ad0$0432e7d8@artemis> Message-ID: <006f01c209dd$2ec6d440$1e00a8c0@onsnet.org> steven heeft geschreven: > Hi, > > How do I get the field labelled "Host name this list prefers" on the > admin page "mailing list administration > General Options Section" to correctly handle a sub-domain (aka three > part machine name, e.g. foo.domain.com) so that mail sent from > adminstrative aliases comes from > listname-admin@foo.domain.dom instead of listname-admin@domain.dom ? Hi, I have the same question asked at the dev list ( a few days ago). Here with Mailman 2,1b2 same problem. Danny, From jonc@nc.rr.com Sun Jun 2 05:29:56 2002 From: jonc@nc.rr.com (Jon Carnes) Date: Sun, 2 Jun 2002 00:29:56 -0400 Subject: [Mailman-Developers] Re: [Mailman-Users] "Host name this list prefers" In-Reply-To: <006f01c209dd$2ec6d440$1e00a8c0@onsnet.org> References: <000801c209cb$b8f06ad0$0432e7d8@artemis> <006f01c209dd$2ec6d440$1e00a8c0@onsnet.org> Message-ID: <0a4de2525040262FE5@mail5.nc.rr.com> On Saturday 01 June 2002 10:28 pm, Danny Terweij wrote: > steven heeft geschreven: > > Hi, > > > > How do I get the field labelled "Host name this list prefers" on the > > admin page "mailing list administration > > General Options Section" to correctly handle a sub-domain (aka three > > part machine name, e.g. foo.domain.com) so that mail sent from > > adminstrative aliases comes from > > listname-admin@foo.domain.dom instead of listname-admin@domain.dom ? > > Hi, > > I have the same question asked at the dev list ( a few days ago). > Here with Mailman 2,1b2 same problem. > > Danny, Alas, Mailman simply users the listname here and chops off any included domain name. If you want the Domain name included in the mailing properly, then you will have to use the "generics" tables for Sendmail - or move your MTA over to something that does virtual domains easier. Postfix does Virtual domains quite easily. You might want to look at using that for your MTA instead of Sendmail (though I'm still a die-hard Sendmail fan!). Jon Carnes From marc_news@vasoftware.com Sun Jun 2 07:54:42 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sat, 1 Jun 2002 23:54:42 -0700 Subject: [Mailman-Developers] bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 more text Message-ID: <20020602065442.GA12014@merlins.org> If this works as expected, all the headers below the subject line should end up in the mail body. I've been tracking this bug for a while, apparently mailman's header parsing chokes when you have a header that contains more than 80 (maybe 100?) characters in a row without a space. This breaks horribly when you run spamassassin, due to headers like: X-Spam-Status: No, hits=2.0 required=7.0 tests=SUBJ_ENDS_IN_Q_MARK,TO_LOCALPART_EQ_REAL,X_NOT_PRESENT,RCVD_IN_VADUL,X_RCVD_IN_DUL_FH version=2.21 But it also breaks because outlook has a bug where Message-IDs listed in the References header aren't always separated by spaces. I'm hoping that Barry or someone else can nail this quicker than I can find out which part of mailman may even be responsible for that (I'm still quite busy hacking on exim and spamassassin for sf.net right now) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@vasoftware.com Sun Jun 2 08:14:08 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 00:14:08 -0700 Subject: [Mailman-Developers] bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 more text In-Reply-To: <20020602065442.GA12014@merlins.org> References: <20020602065442.GA12014@merlins.org> Message-ID: <20020602071408.GC12014@merlins.org> On Sat, Jun 01, 2002 at 11:54:42PM -0700, Marc MERLIN wrote: > If this works as expected, all the headers below the subject line should > end up in the mail body. Son of a... When I sent it to my mailman lists, it arrives in my mailbox as: ---------------------------------------------------------------------------- (...) From: Marc MERLIN To: mailman-developers@python.org Message-ID: <20020602065442.GA12014@merlins.org> Mail-Followup-To: mailman-developers@python.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Sysadmin: BOFH X-URL: http://marc.merlins.org/ X-Operating-System: Proudly running Linux 2.4.14-lvm1.0.1rc4-ext3-0.9.15-grsec-1.8.8-servers11/Debian woody X-Mailer: Some Outlooks can't quote properly without this header X-Mailman-Approved-At: Sun, 02 Jun 2002 07:02:13 -0000 Subject: [Test] bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971234567898 112345678911234567892123456789112345678911234567892123456789 more text X-BeenThere: test@list.merlins.org X-Mailman-Version: 2.1b2+ Precedence: bulk List-Help: List-Archive: List-Unsubscribe: , List-Subscribe: , List-Post: List-Id: What could a test list be for? Sender: test-bounces+marc=merlins.org@list.merlins.org Errors-To: test-bounces+marc=merlins.org@list.merlins.org If this works as expected, all the headers below the subject line should end up in the mail body. (...) ---------------------------------------------------------------------------- I don't get it. I just synced my tree, it still does it, and on two different machines. Can you guys try this subject line on your mm 2.1b2 servers? (it works with mailman 2.0) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@vasoftware.com Sun Jun 2 08:16:07 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 00:16:07 -0700 Subject: [Mailman-Developers] bug demonstration In-Reply-To: References: Message-ID: <20020602071607.GD12014@merlins.org> On Sun, Jun 02, 2002 at 12:14:08AM -0700, Marc MERLIN wrote: > 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 > more text > Message-ID: <20020602071408.GC12014@merlins.org> > Mail-Followup-To: mailman-developers@python.org > References: <20020602065442.GA12014@merlins.org> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > In-Reply-To: <20020602065442.GA12014@merlins.org> > User-Agent: Mutt/1.3.28i > X-Sysadmin: BOFH > X-URL: http://marc.merlins.org/ > X-Operating-System: Proudly running Linux > 2.4.14-lvm1.0.1rc4-ext3-0.9.15-grsec-1.8.8-servers11/Debian woody > X-Mailer: Some Outlooks can't quote properly without this header > X-Spam-Status: No, hits=-4.3 required=5.0 > tests=IN_REP_TO,LARGE_HEX,BODY_PYTHON_ZOPE version=2.20 > X-Spam-Level: > X-BeenThere: mailman-developers@python.org > X-Mailman-Version: 2.1b2+ > Precedence: bulk > List-Help: > List-Archive: > List-Unsubscribe: , > > List-Subscribe: , > > List-Post: > List-Id: GNU Mailman developers > Sender: mailman-developers-bounces+mailman-developers-local=merlins.org@python.org > Errors-To: mailman-developers-bounces+mailman-developers-local=merlins.org@python.org > > On Sat, Jun 01, 2002 at 11:54:42PM -0700, Marc MERLIN wrote: > > If this works as expected, all the headers below the subject line should > > end up in the mail body. > > Son of a... Ahah, and now it barfs on python.org too. I don't get this bug, I really don't... Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From ricardo@rixhq.nu Sun Jun 2 11:32:16 2002 From: ricardo@rixhq.nu (Ricardo Kustner) Date: Sun, 02 Jun 2002 12:32:16 +0200 Subject: [Mailman-Developers] bug demonstration References: <20020602071607.GD12014@merlins.org> Message-ID: <3CF9F430.6090406@rixhq.nu> Marc MERLIN wrote: >>>If this works as expected, all the headers below the subject line should >>>end up in the mail body. >>Son of a... > Ahah, and now it barfs on python.org too. > I don't get this bug, I really don't... the bug is probably in the function prefix_subject in Mailman/Handlers/CookHeaders.py I haven't found the *exact* problem though... Ricardo. From danny@terweij.nl Sun Jun 2 11:35:35 2002 From: danny@terweij.nl (Danny Terweij) Date: Sun, 2 Jun 2002 12:35:35 +0200 Subject: [Mailman-Developers] Re: [Mailman-Users] "Host name this list prefers" References: <000801c209cb$b8f06ad0$0432e7d8@artemis> <006f01c209dd$2ec6d440$1e00a8c0@onsnet.org> <0a4de2525040262FE5@mail5.nc.rr.com> Message-ID: <00ad01c20a21$3adf33a0$1e00a8c0@onsnet.org> From: "Jon Carnes" > On Saturday 01 June 2002 10:28 pm, Danny Terweij wrote: > > steven heeft geschreven: > > > listname-admin@foo.domain.dom instead of listname-admin@domain.dom ? > > I have the same question asked at the dev list ( a few days ago). > > Danny, > Alas, Mailman simply users the listname here and chops off any included > domain name. If you want the Domain name included in the mailing properly, > then you will have to use the "generics" tables for Sendmail - or move your > MTA over to something that does virtual domains easier. I do not know if you read my message at the de list, i am not using virtual hosts at my site. I use this at my site : These are my mm_cfg settings: DEFAULT_EMAIL_HOST = 'lnx.p-s.nl' DEFAULT_URL_HOST = 'www.p-s.nl' DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' DEFAULT_HOST_NAME = DEFAULT_URL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST VIRTUAL_HOST_OVERVIEW = 0 Look for the thread : [Mailman-Developers] Wrong domain choosed when creating a new list (mm2.1b2) Danny. From lrosa@mail.hypertrek.info Sun Jun 2 14:48:32 2002 From: lrosa@mail.hypertrek.info (Luigi Rosa) Date: Sun, 02 Jun 2002 15:48:32 +0200 Subject: [Mailman-Developers] 2.1b4 bug or my problem? Message-ID: <5.1.1.2.2.20020602153745.0208b478@mail.venus.it> I just installed 2.1b4 on a fresh Linux installation. Everything is working well except for the URL in the headers and in the web pages. The hostname of the Linux box is mail.hypertrek.info and this is a part of mm_cfg.py: DEFAULT_EMAIL_HOST = 'mail.hypertrek.info' DEFAULT_URL_HOST = 'mail.hypertrek.info' DEFAULT_URL_PATTERN = 'http://%s/mailman/' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_HOST_NAME = DEFAULT_EMAIL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST HOME_PAGE = 'index.html' MAILMAN_SITE_LIST = 'mailman' With this settings, the header of the messages of each list and the mailto URL of the web pages are http://mail/mailman.... With the withlist inbterface I tried to change the web_page_url parameter of each list from 'mail' to 'http://mail.hypertrek.info' and the mailto url werw ok, but the headers of the messages and the URL of teh web pages were http://mail.hypertrek.info/... without mailman The question is: can I set the web_page_url variable to 'http://mail.hypertrek.info/mailman/' or there is another solution for this issue? Thanks. Ciao, luigi From hostmaster@shults.org Sun Jun 2 11:01:31 2002 From: hostmaster@shults.org (steven) Date: Sun, 2 Jun 2002 03:01:31 -0700 Subject: [Mailman-Developers] RE: [Mailman-Users] "Host name this list prefers" In-Reply-To: <0a4de2525040262FE5@mail5.nc.rr.com> Message-ID: <001701c20a1c$7d100880$0432e7d8@artemis> found the problem, it was me. I had DM "(who I masquerade as (null for no masquerading) (see also $=M)" set in sendmail.cf, which was overriding FM (masq-domains.) > -----Original Message----- > From: mailman-users-admin@python.org > [mailto:mailman-users-admin@python.org] On Behalf Of Jon Carnes > Sent: Saturday, June 01, 2002 9:30 PM > To: Danny Terweij; steven; mailman-users@python.org > Cc: mailman-developers@python.org > Subject: Re: [Mailman-Users] "Host name this list prefers" > > > On Saturday 01 June 2002 10:28 pm, Danny Terweij wrote: > > steven heeft geschreven: > > > Hi, > > > > > > How do I get the field labelled "Host name this list > prefers" on the > > > admin page "mailing list administration > > > General Options Section" to correctly handle a sub-domain > (aka three > > > part machine name, e.g. foo.domain.com) so that mail sent from > > > adminstrative aliases comes from > > > listname-admin@foo.domain.dom instead of > listname-admin@domain.dom ? > > > > Hi, > > > > I have the same question asked at the dev list ( a few days ago). > > Here with Mailman 2,1b2 same problem. > > > > Danny, > > Alas, Mailman simply users the listname here and chops off > any included > domain name. If you want the Domain name included in the > mailing properly, > then you will have to use the "generics" tables for Sendmail > - or move your > MTA over to something that does virtual domains easier. > > Postfix does Virtual domains quite easily. You might want to > look at using > that for your MTA instead of Sendmail (though I'm still a > die-hard Sendmail > fan!). > > Jon Carnes > > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users@python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > From pioppo@ferrara.linux.it Sun Jun 2 17:15:48 2002 From: pioppo@ferrara.linux.it (Simone Piunno) Date: Sun, 2 Jun 2002 18:15:48 +0200 Subject: [Mailman-Developers] 2.1b4 bug or my problem? In-Reply-To: <5.1.1.2.2.20020602153745.0208b478@mail.venus.it> References: <5.1.1.2.2.20020602153745.0208b478@mail.venus.it> Message-ID: <20020602161548.GA14137@abulafia.casa> domenica, 02 giugno 2002 alle 15:48:32, Luigi Rosa ha scritto: > I just installed 2.1b4 on a fresh Linux installation. the last CVS is 2.1b2+... where did you find this 2.1b4? :) -- Simone Piunno, FerraraLUG - http://members.ferrara.linux.it/pioppo From marc_news@vasoftware.com Sun Jun 2 22:15:31 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 14:15:31 -0700 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <3CF9F430.6090406@rixhq.nu> References: <20020602071607.GD12014@merlins.org> <3CF9F430.6090406@rixhq.nu> Message-ID: <20020602211531.GC18804@merlins.org> On Sun, Jun 02, 2002 at 12:32:16PM +0200, Ricardo Kustner wrote: > >>>If this works as expected, all the headers below the subject line should > >>>end up in the mail body. > >>Son of a... > >Ahah, and now it barfs on python.org too. > >I don't get this bug, I really don't... > > the bug is probably in the function prefix_subject in > Mailman/Handlers/CookHeaders.py > I haven't found the *exact* problem though... I was suspecting email-x.y.tar.gz myself :-) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From jarrell@vt.edu Sun Jun 2 22:30:30 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Sun, 02 Jun 2002 17:30:30 -0400 Subject: [Mailman-Developers] bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971 234567898112345678911234567892123456789112345678911234567892123456789 more text In-Reply-To: <20020602065442.GA12014@merlins.org> Message-ID: <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> At 11:54 PM 6/1/02 -0700, Marc MERLIN wrote: >If this works as expected, all the headers below the subject line should >end up in the mail body. > >I've been tracking this bug for a while, apparently mailman's header parsing >chokes when you have a header that contains more than 80 (maybe 100?) >characters in a row without a space. Refer to the notes that I posted off and on over the last month, including a sample header that triggers the effect. I finally caught a header *before* it happened by being cc'd on a note that coincidentally triggered it, and posted it, and Barry confirmed he could replicate it. What little time I've had to look at it has left me convinced it's email that's doing it... Unfortunately, while I would normally have been trying to fix this, rather than just report it and wash my hands of it, I've recently been rendered functionally unable to do much of anything at work. Thanks to excellent and far sighted scheduling on the part of the upper brass, my #1 priority is to pack and move my office into storage. In about a month the bid on our new office space should go out, and the most forgiving estimates show us getting a place to sit down again and set up shop possibly as early as christmas... From jarrell@vt.edu Sun Jun 2 22:33:57 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Sun, 02 Jun 2002 17:33:57 -0400 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <20020602071607.GD12014@merlins.org> References: Message-ID: <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> At 12:16 AM 6/2/02 -0700, Marc MERLIN wrote: >Ahah, and now it barfs on python.org too. > >I don't get this bug, I really don't... Yea. It's not simple line length. It also appears to really need a continuation header to trigger; I think it happened after you replied because *now*, thanks to the reformatting that went on on it's way into the pickle, it had continuation lines in it. I still think it's email doing it - the header parser likes to unwrap lines with nl's, and rewrap them later, and I think it's getting confused and kicking out an extra NL. From jarrell@vt.edu Sun Jun 2 22:35:07 2002 From: jarrell@vt.edu (Ron Jarrell) Date: Sun, 02 Jun 2002 17:35:07 -0400 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <3CF9F430.6090406@rixhq.nu> References: <20020602071607.GD12014@merlins.org> Message-ID: <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> At 12:32 PM 6/2/02 +0200, Ricardo Kustner wrote: >Marc MERLIN wrote: > >>>>If this works as expected, all the headers below the subject line should >>>>end up in the mail body. >>>Son of a... >>Ahah, and now it barfs on python.org too. >>I don't get this bug, I really don't... > >the bug is probably in the function prefix_subject in >Mailman/Handlers/CookHeaders.py >I haven't found the *exact* problem though... It's not just subjects that trigger it - I posted a X-Face header two weeks ago that will consistently trigger it, and there are other headers that do it to. It's any header of the right size and shape. From marc_news@vasoftware.com Sun Jun 2 22:44:58 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 14:44:58 -0700 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> References: <20020602065442.GA12014@merlins.org> <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <20020602071607.GD12014@merlins.org> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> Message-ID: <20020602214458.GC29098@merlins.org> On Sun, Jun 02, 2002 at 05:35:07PM -0400, Ron Jarrell wrote: > It's not just subjects that trigger it - I posted a X-Face header two weeks I'm very aware of that, my initial post mentionned the X-Spam header from SA, and reference headers from buggy outlooks that forget to put a space between message-Ids in reference lines On Sun, Jun 02, 2002 at 05:33:57PM -0400, Ron Jarrell wrote: > At 12:16 AM 6/2/02 -0700, Marc MERLIN wrote: > >Ahah, and now it barfs on python.org too. > > > >I don't get this bug, I really don't... > > Yea. It's not simple line length. It also appears to really need a > continuation header to trigger; I think it happened after you replied > because *now*, thanks to the reformatting that went on on it's way into the > pickle, it had continuation lines in it. Mmh, that would make sense. > I still think it's email doing it - the header parser likes to unwrap > lines with nl's, and rewrap them later, and I think it's getting confused > and kicking out an extra NL. Yep. On Sun, Jun 02, 2002 at 05:30:30PM -0400, Ron Jarrell wrote: > Refer to the notes that I posted off and on over the last month, including > a sample header that triggers the effect. Actually I posted one too :-) > I finally caught a header *before* it happened by being cc'd on a note I ended up sending my list mail to an alias saved on disk so that I could see the mail before and after mm. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From barry@zope.com Sun Jun 2 22:48:55 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 2 Jun 2002 17:48:55 -0400 Subject: [Mailman-Developers] bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971 234567898112345678911234567892123456789112345678911234567892123456789 more text References: <20020602065442.GA12014@merlins.org> <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> Message-ID: <15610.37575.971910.283791@anthem.wooz.org> >>>>> "RJ" == Ron Jarrell writes: RJ> What little time I've had to look at it has left me convinced RJ> it's email that's doing it... I suspect this as well. I'm way too busy to spend a lot of time on this right now (I'm closing on a new house tomorrow), but it would be great if someone could checkout the current cvs of the email (mimelib) package and try it with the current cvs of MM2.1. I've got no substantive unchecked in stuff, so if it doesn't work with this combination, then the bug's still lurking in there. -Barry From david@midrange.com Sun Jun 2 23:06:17 2002 From: david@midrange.com (David Gibbs) Date: Sun, 2 Jun 2002 17:06:17 -0500 Subject: [Mailman-Developers] Contributing code? Message-ID: Folks: How does one go about contributing code? I've made some small changes in my cvs sandbox that I think would be useful for the core code. Do I mail them to someone (Barry?) for consideration, post them here, what? The mods I made are fairly simple ... when the admlogin, options, and private templates are loaded, the cursor is automaticly placed in the first form field on the page. I made similar changes in 2.0.11 and my list owners love it. Thanks! david From marc_news@vasoftware.com Sun Jun 2 23:17:38 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 15:17:38 -0700 Subject: [Mailman-Developers] Contributing code? In-Reply-To: References: Message-ID: <20020602221738.GA32064@merlins.org> On Sun, Jun 02, 2002 at 05:06:17PM -0500, David Gibbs wrote: > Folks: > > How does one go about contributing code? > > I've made some small changes in my cvs sandbox that I think would be useful > for the core code. Do I mail them to someone (Barry?) for consideration, > post them here, what? If the diff isn't too big, post it here. If it's big or you are afraid the MUA/MTA is going to damanged it, put it on a web site and post a URL. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From claw@kanga.nu Sun Jun 2 23:34:10 2002 From: claw@kanga.nu (J C Lawrence) Date: Sun, 02 Jun 2002 15:34:10 -0700 Subject: [Mailman-Developers] MimeFilter integration with Mailman Message-ID: <12017.1023057250@kanga.nu> <> A while back I noticed that while we'd been happily recommending MimeFilter for stripping unwanted MIME parts from messages before they got to mailman, nobody had bothered to say how to run it beyond "chuck it in the alias file". Problem: those instructions (generally) won't work. Reason: Mimefilter tries to create files and a temp directory in its CWD, and at least under postfix that means /var/spool/postfix which here is root.root/0755 (and I'm not about to change that). So I spent some time this morning and threw something together a little slicker. Its essentially a wrapper around Mailman's wrapper. What I got seems to work. I don't and won't claim beauty. ---- #!/bin/bash # Syntax: # # mimestrip # # Both arguments will be passed to /var/lib/mailman/mail/wrapper # in the same order, without change. # # All other arguments will be gleefully discarded. # # Author: J C Lawrence # ACTION=$1 TARGET=$2 export PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/sbin:/usr/sbin # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Config (Edit this bit to suit your setup!) # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Safe working directory for mimefilter. We need to do this as # postfix by default will execute this script in /var/spool/postfix and # mimefilter will try and create temp directories and files under there. # Note: Make sure that the value of tmpdir is writeable by the UID or GID # that this script will execute under. tmpdir="/tmp/mimestrip.${$}" # Do you want to save an mbox of the messages before filtering # in $savefile_pre? (0/1) save_pre=1 # Do you want to save an mbox of the messages after filtering # in $savefile_post? (0/1) save_post=1 # File to save pre-filtered messages in savefile_pre="/tmp/mimestrip.prefilter" # File to same post filtered messages in savefile_post="/tmp/mimestrip.postfilter" # Send a copy of every processed message to the list maintainer? (Y/N) copy_maintainer="y" # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # MimeFilter setup (Don't edit from here down) # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # The name of the mailing list this message is intended for. Used # as the return address of the warning issued to the orginal author # if the message is not already clean. export list=${USER} # The address of the mailing list this message is intended for. # Used in the X-Loop field of the warning issued to the original # author if the message is not already clean. export listaddr=${USER}@${DOMAIN} # The administrative (owner) address of the mailing list this # message is inteded for. Used in the return address of the warning # issued to the original author if the message is not already clean. export listreq=${USER}-admin@${DOMAIN} # The email address of the maintainer of the mailing list this # message is inteded for. If it is defined, it is used to send the # maintainer original carbon copies of messages that have been # modified by this filter -- if filter_mime_cc_maintainer is # affermative, of course. export maintainer=${USER}-owner@${DOMAIN} # A boolean flag: if affermative (i.e., if it matches the /y/i Perl # regular expression), the mimefilter script will send carbon copies # of every cleaned (modified) message to the maintainer of the # mailing list the message is intended for. export filter_mime_cc_maintainer=${copy_maintainer} # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Start working # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Build a safe working directory for mimefilter. We need to do this as # postfix by default will execute this script in /var/spool/postfix and # mimefilter will try and create temp directories and files under there, # which will fail on permissions. # Note: Make sure that the value of tmpdir is writeable by the UID or GID # that this script will execute under. rm -rf ${tmpdir} 2> /dev/null mkdir ${tmpdir} cd ${tmpdir} # Working files (over-engineered and IO heavy, but useful during debugging # and tuning of the filter setup) tmpfile="mimestrip.$$" holdfile="mimehold.$$" # DEBUG #pwd > /tmp/mimestrip.pwd #set > /tmp/mimestrip.env # Get the inbound message from stdin and run it thru mimefilter with # copies saved for before and after. The mimestrip.err file should # always be empty. I found it useful for debugging. Nuke freely. # Note: If there's an "X-MimeStrip: No" header (actually anywhere in the # message), then don't run this message thru mimefilter but pass it # straight on to the mailman wrapper. cat > ${holdfile} grep -i "^X-MimeStrip:[ \t]*No" ${holdfile} if [ $? ] then cat ${holdfile} | /usr/bin/mimefilter > ${tmpfile} 2> /tmp/mimestrip.err # If there's nothing left of the message (less than 5 lines), don't # bother sending it forward to Mailman. count=`cat ${tmpfile} | wc -l` if [ $count -gt 5 ] then cat ${tmpfile} | /var/lib/mailman/mail/wrapper ${ACTION} ${TARGET} fi else # We found a header so send it thru unfiltered. cat ${tmpfile} | /var/lib/mailman/mail/wrapper ${ACTION} ${TARGET} fi # Save copies of the before and after messages off to a temp file for # analysis/debugging if [ $save_pre -eq 1 ] then cat ${holdfile} >> /tmp/mimestrip.prefilter echo >>/tmp/mimestrip.prefilter fi if [ $save_post -eq 1 ] then cat ${tmpfile} >> /tmp/mimestrip.postfilter echo >> /tmp/mimestrip.postfilter fi # Clean up rm -rf ${tmpdir} exit 0 ---- Notes: Use in your Mailman alias file as so (for a list called "test"): test: "|/some/path/here/mimestrip post test" More simply just replace the normal /var/lib/mailman/mail/wrapper" with the call to mimestrip. The script is Postfix specific in that it expects the $USER and $DOMAIN in its environment to be respectively set to the LHS and RHS of the address the message was sent to. Hack freely for your MTA of choice if it does something different. Why not use demime which does all sorts of cool things like Yahoo signature removal and getting rid of unnecessary quoted-printable? demime strips all MIME parts, which is fine if that's what you want. However there are certain MIME parts that I specifically want to let thru to my lists (eg message/rfc822), and I rather like some of mimefilter's other features thta demime doesn't share like emailing the original poster with a warning that parts were removed from their message. Yeah, those extra messages are annoying to the posters. They're intended to be and I like that. I don't want posters sending unwanted MIME parts to my lists. Note: You can turn off that feature in Mimefilter's config. I also wanted a way to send MIME messages thru to my lists without doing any MIME stripping. A bypass if you would. Typically I'd use this for valid/valuable list messages which contain useful MIME parts (eg an attached image such as a graph diagramming the message content) that would otherwise be stripped my the mimefilter. In the end I did this via a custom X-header: X-MimeStrip: No. Strong suggestion: Configure your lists to hold messages with that header for moderator approval. This will allow you to catch abuse by too-clever posters. Mailman v2.1 largely removes need for this mimestrip filter. If all you want is mimestripping then Mailman 2.1 should be more than enough. However I want more than that. I want mimefilter's annoying messages to posters of unwanted MIME, I want the bypass, I want the ability to save the before and after filtering messages etc, and I really want the ability to ad-hoc extend the filter with other little toys and trinkets as I go along (eg a quoted-printable flattener will likely be next for me here). Adding in something like SpamAssassin into the mail processing pipe with a custom handling rule (eg silently discard messages with high enough scores before passing them thru mimefilter) would be trivially easy and is left as an exercise for the reader. This is barely if at all tested. Caveat Emptor and all that rot. Yeah, I should put this in the FAQ and I hopefully will after I've run it thru a few more exercises here. Enjoy. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw@kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. From barry@zope.com Mon Jun 3 00:29:29 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 2 Jun 2002 19:29:29 -0400 Subject: [Mailman-Developers] Contributing code? References: <20020602221738.GA32064@merlins.org> Message-ID: <15610.43609.882412.457090@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> If the diff isn't too big, post it here. If it's big or you MM> are afraid the MUA/MTA is going to damanged it, put it on a MM> web site and post a URL. Better yet, post it on the SF patch manager, so it doesn't get lost in my inbox! ;) -Barry From david@midrange.com Mon Jun 3 00:47:34 2002 From: david@midrange.com (David Gibbs) Date: Sun, 02 Jun 2002 18:47:34 -0500 Subject: [Mailman-Developers] Contributing code? In-Reply-To: <15610.43609.882412.457090@anthem.wooz.org> References: <20020602221738.GA32064@merlins.org> Message-ID: <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> At 06:29 PM 6/2/2002, Barry A. Warsaw wrote: >Better yet, post it on the SF patch manager, so it doesn't get lost in >my inbox! ;) Ok. What's the prescribed method of preparing a good diff? cvs diff? david -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | If you can't fly, run; if you can't run, walk; | if you can't walk, crawl. | -mlk From marc_news@vasoftware.com Mon Jun 3 00:52:57 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 16:52:57 -0700 Subject: [Mailman-Developers] Contributing code? In-Reply-To: <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> References: <20020602221738.GA32064@merlins.org> <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> Message-ID: <20020602235257.GE32064@merlins.org> On Sun, Jun 02, 2002 at 06:47:34PM -0500, David Gibbs wrote: > At 06:29 PM 6/2/2002, Barry A. Warsaw wrote: > >Better yet, post it on the SF patch manager, so it doesn't get lost in > >my inbox! ;) > > Ok. What's the prescribed method of preparing a good diff? > > cvs diff? cvs diff -u :-) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@vasoftware.com Mon Jun 3 00:54:37 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 16:54:37 -0700 Subject: [Mailman-Developers] Contributing code? In-Reply-To: <20020602235257.GE32064@merlins.org> References: <20020602221738.GA32064@merlins.org> <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> <20020602235257.GE32064@merlins.org> Message-ID: <20020602235436.GA6048@merlins.org> On Sun, Jun 02, 2002 at 04:52:57PM -0700, Marc MERLIN wrote: > On Sun, Jun 02, 2002 at 06:47:34PM -0500, David Gibbs wrote: > > At 06:29 PM 6/2/2002, Barry A. Warsaw wrote: > > >Better yet, post it on the SF patch manager, so it doesn't get lost in > > >my inbox! ;) > > > > Ok. What's the prescribed method of preparing a good diff? > > > > cvs diff? > > cvs diff -u :-) Mmmh, no, that'd make your patch inversed. Make two dirs: mailman-cvs mailman-yourtree and do a diff -urN mailman-cvs mailman-yourtree > yourpatches.diff Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From david@midrange.com Mon Jun 3 00:58:44 2002 From: david@midrange.com (David Gibbs) Date: Sun, 02 Jun 2002 18:58:44 -0500 Subject: [Mailman-Developers] Contributing code? In-Reply-To: <20020602235436.GA6048@merlins.org> References: <20020602235257.GE32064@merlins.org> <20020602221738.GA32064@merlins.org> <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> <20020602235257.GE32064@merlins.org> Message-ID: <5.1.1.2.2.20020602185644.024b07a0@linux.midrange.com> At 06:54 PM 6/2/2002, Marc MERLIN wrote: > > cvs diff -u :-) >Mmmh, no, that'd make your patch inversed. You sure? I just ran a diff on my patch and it looks right to me... Line I replace has a "-" in front of it, line I replaced it with as a "+" in front. >Make two dirs: >mailman-cvs mailman-yourtree >and do a diff -urN mailman-cvs mailman-yourtree > yourpatches.diff Ech, that's a lot of work when we have a change management system. david >Marc >-- >Microsoft is to operating systems & security .... > .... what McDonalds is to gourmet > cooking > >Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for >PGP key -- | Internet: david@midrange.com | WWW: http://david.fallingrock.net | AIM: MidrangeMan | | If you can't fly, run; if you can't run, walk; | if you can't walk, crawl. | -mlk From marc_news@vasoftware.com Mon Jun 3 01:00:39 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Sun, 2 Jun 2002 17:00:39 -0700 Subject: [Mailman-Developers] Contributing code? In-Reply-To: <5.1.1.2.2.20020602185644.024b07a0@linux.midrange.com> References: <20020602235257.GE32064@merlins.org> <20020602221738.GA32064@merlins.org> <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> <20020602235257.GE32064@merlins.org> <5.1.1.2.2.20020602185644.024b07a0@linux.midrange.com> Message-ID: <20020603000039.GF32064@merlins.org> On Sun, Jun 02, 2002 at 06:58:44PM -0500, David Gibbs wrote: > At 06:54 PM 6/2/2002, Marc MERLIN wrote: > >> cvs diff -u :-) > >Mmmh, no, that'd make your patch inversed. > > You sure? I just ran a diff on my patch and it looks right to me... Never mind, you're right. Too much hacking, not enough sleep. Please ignore me. Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Mon Jun 3 01:03:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 02 Jun 2002 17:03:58 -0700 Subject: [Mailman-Developers] [ mailman-Patches-563686 ] Position cursor in login templates Message-ID: Patches item #563686, was opened at 2002-06-02 19:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Position cursor in login templates Initial Comment: Some of my list owners wanted the cursor to be positioned in the password field for the admin & admindb pages. So I hacked a tiny bit of javascript to position the cursor in the first form field on the admlogin, options, and private templates. All languages. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id=103 From david@midrange.com Mon Jun 3 01:06:02 2002 From: david@midrange.com (David Gibbs) Date: Sun, 2 Jun 2002 19:06:02 -0500 Subject: [Mailman-Developers] Re: Contributing code? References: <20020602221738.GA32064@merlins.org> <15610.43609.882412.457090@anthem.wooz.org> Message-ID: "Barry A. Warsaw" wrote in message news:15610.43609.882412.457090@anthem.wooz.org... > Better yet, post it on the SF patch manager, so it doesn't get lost in > my inbox! ;) Ok, I posted it on sf. It's patch #563686. david From barry@zope.com Mon Jun 3 04:15:17 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 2 Jun 2002 23:15:17 -0400 Subject: [Mailman-Developers] Re: Contributing code? References: <20020602221738.GA32064@merlins.org> <15610.43609.882412.457090@anthem.wooz.org> Message-ID: <15610.57157.291766.422372@anthem.wooz.org> >>>>> "DG" == David Gibbs writes: DG> Ok, I posted it on sf. It's patch #563686. Thanks. Yup, "cvs diff -u" is the preferred mechanism. You'll need to do -N if you're adding new files (but you can also just post the new files themselves). I can grok context diffs (-C 2) but unifieds are much preferred. Thanks, -Barry From barry@zope.com Mon Jun 3 04:16:01 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sun, 2 Jun 2002 23:16:01 -0400 Subject: [Mailman-Developers] Contributing code? References: <20020602235257.GE32064@merlins.org> <20020602221738.GA32064@merlins.org> <5.1.1.2.2.20020602184649.0247dc30@linux.midrange.com> <5.1.1.2.2.20020602185644.024b07a0@linux.midrange.com> <20020603000039.GF32064@merlins.org> Message-ID: <15610.57201.267528.354248@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> Never mind, you're right. Too much hacking, not enough sleep. You've been listening to Nancy too much! :) -Barry From marc_news@vasoftware.com Tue Jun 4 07:11:21 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Mon, 3 Jun 2002 23:11:21 -0700 Subject: [Mailman-Developers] hide web interface from users and "Results of your email commands" In-Reply-To: References: Message-ID: <20020604061121.GL18804@merlins.org> On Sat, Jun 01, 2002 at 12:36:43PM -0400, totschnig.michael@uqam.ca wrote: > - Can I suppress the "Results of your email commands" email for this > list or alternatively for the whole site? > > - Is there a way to suppress most parts of the web-interface for a > list. Yes to both, but not without hacking the code Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From dickson@permanentmail.com Tue Jun 4 20:34:25 2002 From: dickson@permanentmail.com (Paul Dickson) Date: Tue, 4 Jun 2002 12:34:25 -0700 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <20020602214458.GC29098@merlins.org> References: <20020602065442.GA12014@merlins.org> <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <20020602071607.GD12014@merlins.org> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> <20020602214458.GC29098@merlins.org> Message-ID: <20020604123425.745f0d94.dickson@permanentmail.com> On Sun, 2 Jun 2002 14:44:58 -0700, Marc MERLIN wrote: > On Sun, Jun 02, 2002 at 05:35:07PM -0400, Ron Jarrell wrote: > > It's not just subjects that trigger it - I posted a X-Face header two weeks > > I'm very aware of that, my initial post mentionned the X-Spam header from > SA, and reference headers from buggy outlooks that forget to put a space > between message-Ids in reference lines It happened to me today. A message from a Mailman 2.0.11 mailing list, created by Mutt/1.2.5.1i. The References: field had 5 message-ids separated by spaces only, making the line 254 characters long. The next line was a blank line (in which a Status field had been added), pushing the rest of the header info into the body (the mailing list info, which is why my filters could not sort the message). I thought this problem was with my POP3 mailbox server I was using until the test message came through on this list. -Paul From marc_news@vasoftware.com Tue Jun 4 21:50:53 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Tue, 4 Jun 2002 13:50:53 -0700 Subject: [Mailman-Developers] bug demonstration In-Reply-To: <20020604122833.6bc25b20.dickson@permanentmail.com> References: <20020602065442.GA12014@merlins.org> <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <20020602071607.GD12014@merlins.org> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> <20020602214458.GC29098@merlins.org> <20020604122833.6bc25b20.dickson@permanentmail.com> Message-ID: <20020604205052.GC30773@merlins.org> On Tue, Jun 04, 2002 at 12:28:33PM -0700, Paul Dickson wrote: > It happened to me today. A message from a Mailman 2.0.11 mailing list, > created by Mutt/1.2.5.1i. > > The References: field had 5 message-ids separated by spaces only, making > the line 254 characters long. The next line was a blank line (in which a > Status field had been added), pushing the rest of the header info into the > body (the mailing list info, which is why my filters could not sort the > message). > > I thought this problem was with my POP3 mailbox server I was using until > the test message came through on this list. I'm pretty sure the bugs are different. The one I refer to only happens if you have a very long line with no spaces, and it does not happen with mailman 2.0.11 (at least I couldn't get it to happen) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Tue Jun 4 22:08:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 04 Jun 2002 14:08:25 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-564587 ] config_list breaks at filter_mime_types Message-ID: Bugs item #564587, was opened at 2002-06-04 14:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Devin L. Ganger (dlganger) Assigned to: Nobody/Anonymous (nobody) Summary: config_list breaks at filter_mime_types Initial Comment: When running: config_list -o cpunk.conf cpunk-secpro on my list cpunk-secpro@lists.thecabal.org, I get the following error: (bofh:mailman) /home/mailman $ config_list -o cpunk.conf cpunk-secpro Traceback (most recent call last): File "/home/mailman/bin/config_list", line 268, in ? main() File "/home/mailman/bin/config_list", line 261, in main do_output(listname, outfile) File "/home/mailman/bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "/home/mailman/bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: 'list' object has no attribute 'replace' Doing a tail of the cpunk.conf file show the following: (bofh:mailman) /home/mailman $ tail cpunk.conf # matching MIME major type, e.g. image. Blank lines are ignored. # # After stripping message parts, any multipart attachment that is empty # as a result is removed all together. If the outer part's MIME type # matches one of the strip types, or if all of the outer part's subparts # are stripped, then the whole message is discarded. Finally, each # multipart/alternative section will be replaced by just the first # alternative that is non-empty after the specified types have been # removed. filter_mime_types = ---------------------------------------------------------------------- >Comment By: Devin L. Ganger (dlganger) Date: 2002-06-04 14:08 Message: Logged In: YES user_id=478874 This is on Solaris 7, Python 2.2: (bofh:devin) /home/devin $ python -V Python 2.2 (bofh:devin) /home/devin $ uname -a SunOS bofh.thecabal.internal 5.7 Generic_106541-14 sun4m sparc SUNW,SPARCsystem-600 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_id=103 From noreply@sourceforge.net Tue Jun 4 22:06:03 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 04 Jun 2002 14:06:03 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-564587 ] config_list breaks at filter_mime_types Message-ID: Bugs item #564587, was opened at 2002-06-04 14:06 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Devin L. Ganger (dlganger) Assigned to: Nobody/Anonymous (nobody) Summary: config_list breaks at filter_mime_types Initial Comment: When running: config_list -o cpunk.conf cpunk-secpro on my list cpunk-secpro@lists.thecabal.org, I get the following error: (bofh:mailman) /home/mailman $ config_list -o cpunk.conf cpunk-secpro Traceback (most recent call last): File "/home/mailman/bin/config_list", line 268, in ? main() File "/home/mailman/bin/config_list", line 261, in main do_output(listname, outfile) File "/home/mailman/bin/config_list", line 113, in do_output do_list_categories(mlist, k, None, outfp) File "/home/mailman/bin/config_list", line 162, in do_list_categories lines = value.replace('\r', '').split('\n') AttributeError: 'list' object has no attribute 'replace' Doing a tail of the cpunk.conf file show the following: (bofh:mailman) /home/mailman $ tail cpunk.conf # matching MIME major type, e.g. image. Blank lines are ignored. # # After stripping message parts, any multipart attachment that is empty # as a result is removed all together. If the outer part's MIME type # matches one of the strip types, or if all of the outer part's subparts # are stripped, then the whole message is discarded. Finally, each # multipart/alternative section will be replaced by just the first # alternative that is non-empty after the specified types have been # removed. filter_mime_types = ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=564587&group_id=103 From jra@baylink.com Wed Jun 5 00:51:59 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Tue, 4 Jun 2002 19:51:59 -0400 Subject: [Mailman-Developers] Oops... In-Reply-To: <20020604205052.GC30773@merlins.org>; from Marc MERLIN on Tue, Jun 04, 2002 at 01:50:53PM -0700 References: <5.1.0.14.2.20020602172524.00a14c00@lennier.cc.vt.edu> <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <20020602071607.GD12014@merlins.org> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> <20020602214458.GC29098@merlins.org> <20020604122833.6bc25b20.dickson@permanentmail.com> <20020604205052.GC30773@merlins.org> Message-ID: <20020604195159.14301@scfn.thpl.lib.fl.us> Ok; Barry's busy closing on a house. This time, to the list... I'm doing some low-grade hacking on MM CVS from about last week, trying to adapt it for some commercial mailing for a client. (Anyone inclined to maling my ethics without asking first will be happily consigned to /dev/null; I get more spam than you do, unless your first name ends in 'Q'. :-) I've made a modified version of add_members called invite_members, swapping ApprovedAddMember for InviteMember as suggested by Barry. Alas, it seems to be trying to call what I suspect is a mixin from context, something about hostile addresses. It's giving me a traceback; here's the dump: Traceback (most recent call last): File "/appl/mailman2.1/bin/invite_members", line 289, in ? main() File "/appl/mailman2.1/bin/invite_members", line 266, in main addall(mlist, nmembers, 0, send_welcome_msg, s) File "/appl/mailman2.1/bin/invite_members", line 165, in addall except MMHostileAddress: NameError: global name 'MMHostileAddress' is not defined The only changes are the one call in invite_members, which is otherwise identical to add_members except in it's name, and, the following slight code modification at line 675 in MailList.py: text = Utils.maketext( 'invite.txt', {'email' : invitee, 'listname' : listname, 'hostname' : self.host_name, 'confirmurl' : confirmurl, 'requestaddr': requestaddr, 'cookie' : cookie, 'listowner' : self.GetOwnerEmail(), }, mlist=self) if mm_cfg.VERP_CONFIRMATIONS: if mm_cfg.JRA_INVITE_SUBJECT: subj = mm_cfg.JRA_INVITE_SUBJECT else: subj = _( 'You have been invited to join the %(listname)s mailing list') sender = self.GetConfirmEmail(cookie) else: # Do it the old fashioned way subj = 'confirm ' + cookie sender = requestaddr I added: VERP_CONFIRMATIONS=1 JRA_INVITE_SUBJECT='This will be the subject line' to mm_cfg.py. It's probably worth noting that add_members still works fine. Anyone got any ideas what screwy thing I've done wrong here? Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From jra@baylink.com Wed Jun 5 00:54:36 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Tue, 4 Jun 2002 19:54:36 -0400 Subject: [Mailman-Developers] Oops... In-Reply-To: <20020604195159.14301@scfn.thpl.lib.fl.us>; from "Jay R. Ashworth" on Tue, Jun 04, 2002 at 07:51:59PM -0400 References: <5.1.0.14.2.20020602173146.00a152c0@lennier.cc.vt.edu> <20020602071607.GD12014@merlins.org> <5.1.0.14.2.20020602173422.00a15920@lennier.cc.vt.edu> <20020602214458.GC29098@merlins.org> <20020604122833.6bc25b20.dickson@permanentmail.com> <20020604205052.GC30773@merlins.org> <20020604195159.14301@scfn.thpl.lib.fl.us> Message-ID: <20020604195436.64304@scfn.thpl.lib.fl.us> On Tue, Jun 04, 2002 at 07:51:59PM -0400, Jay R. Ashworth wrote: > Ok; Barry's busy closing on a house. This time, to the list... And apologies for not unwiring the References header... Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From barry@zope.com Wed Jun 5 03:48:56 2002 From: barry@zope.com (Barry A. Warsaw) Date: Tue, 4 Jun 2002 22:48:56 -0400 Subject: [Mailman-Developers] Splitting long header lines and the "bug demonstration" Message-ID: <15613.31768.357110.313371@anthem.wooz.org> I know what is causing http://mail.python.org/pipermail-21/mailman-developers/2002-June/012093.html It's the email package, and specifically it's Generator's behavior when splitting long lines, i.e. Generator._split_header(). I actually think that method is terminally broken because it has a ascii bias. I doubt it would even work for long lines of encoded text. The good news is that we have a perfectly fine line splitter that understands encoded headers and does the RFC-correct thing. It's called Header.encode(). The bad news is that Header.encode() isn't parameter aware and making _split_header() call it will cause some messages to not generate idempotently. If your code is expecting the splitting done by _split_header(), your code will break. Interestingly enough, only 4 unit tests fail when I make this change. In particular, it means that a header like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spooge="yummy"; hippos="gargantuan"; marshmallows="gooey" will not get split like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spooge="yummy"; hippos="gargantuan"; marshmallows="gooey" but instead will get split like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spo oge="yummy"; hippos="gargantuan"; marshmallows="gooey" I can obviously fix the test cases, but will this break your code if I make this change? It should fix the nasty Mailman problem. I'm wondering if I need to make some accomodations for _split_header()'s old behavior. -Barry From noreply@sourceforge.net Wed Jun 5 08:42:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 05 Jun 2002 00:42:05 -0700 Subject: [Mailman-Developers] [ mailman-Patches-564747 ] Makes "powered by" icons into links Message-ID: Patches item #564747, was opened at 2002-06-05 07:42 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=564747&group_id=103 Category: Web UI Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: W Isaac Carroll (zaak) Assigned to: Nobody/Anonymous (nobody) Summary: Makes "powered by" icons into links Initial Comment: This makes the Mailman, Python, and GNU icons at the bottom of the web UI pages into links to their respective web sites. There are already links if mm_cfg.IMAGE_LOGOS is false. This patch simply makes the graphical version have the links as well. Patch against version 2.0.9 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=564747&group_id=103 From stephen@xemacs.org Wed Jun 5 09:51:14 2002 From: stephen@xemacs.org (Stephen J. Turnbull) Date: 05 Jun 2002 17:51:14 +0900 Subject: [Mailman-Developers] Splitting long header lines and the "bug demonstration" In-Reply-To: <15613.31768.357110.313371@anthem.wooz.org> References: <15613.31768.357110.313371@anthem.wooz.org> Message-ID: <87it4yaz25.fsf@tleepslib.sk.tsukuba.ac.jp> >>>>> "BAW" == Barry A Warsaw writes: BAW> but instead will get split like X-Foobar-Spoink-Defrobnit: wasnipoop; giraffes="very-long-necked-animals"; spo oge="yummy"; hippos="gargantuan"; marshmallows="gooey" If by "split" you mean RFC 2822 2.2.3 header folding, you can't split "spooge" like that, can you? There's no whitespace between the `o's. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py From noreply@sourceforge.net Wed Jun 5 10:00:17 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 05 Jun 2002 02:00:17 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-474616 ] SECURITY: Pipermail permissions problem Message-ID: Bugs item #474616, was opened at 2001-10-24 22:35 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=474616&group_id=103 Category: Pipermail Group: None Status: Closed Resolution: Wont Fix Priority: 8 Submitted By: H. Peter Anvin (hpa) Assigned to: Nobody/Anonymous (nobody) Summary: SECURITY: Pipermail permissions problem Initial Comment: $mailman_root/archive/private is o+x in the default installation. This allows anyone with local access to the machine to read the archives of private mailing lists, as long as they know the (trivial) structure of the files beneath this directory. I have verified that changing this directory to o-x causes *all* pipermail pages to become inaccessible, so that does not resolve the problem. There presumably needs to be a setgid program involved which can verify that the user is authenticated and give access to the archives if appropriate; then that directory can be made o-x. ---------------------------------------------------------------------- Comment By: Arne Georg Gleditsch (argggh) Date: 2002-06-05 11:00 Message: Logged In: YES user_id=387572 I'm not comfortable with this remaining unfixed. Is there any reason it couldn't be handled by doing --- Mailman/Archiver/Archiver.py 15 Feb 2002 16:28:03 -0000 1.1 +++ Mailman/Archiver/Archiver.py 5 Jun 2002 08:54:18 -0000 @@ -250,8 +250,12 @@ self._internal_name + '.mbox') privmbox = self.archive_directory + '.mbox' if self.archive_private: + os.chmod(privdir, 02770) + os.chmod(privmbox, 02770) breaklink(pubdir) breaklink(pubmbox) else: + os.chmod(privdir, 02775) + os.chmod(privmbox, 02775) makelink(privdir, pubdir) makelink(privmbox, pubmbox) or something? ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-12 00:40 Message: Logged In: YES user_id=12800 I'm not inclined to fix this, since this arrangement is crucial to the web security of private archives. Since Mailman is usually run on mail and/or web servers that have very limited access anyway, I don't consider this an important vulnerability. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=474616&group_id=103 From barry@zope.com Wed Jun 5 13:12:23 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 5 Jun 2002 08:12:23 -0400 Subject: [Mailman-Developers] Splitting long header lines and the "bug demonstration" References: <15613.31768.357110.313371@anthem.wooz.org> <87it4yaz25.fsf@tleepslib.sk.tsukuba.ac.jp> Message-ID: <15614.39.43517.913342@anthem.wooz.org> >>>>> "SJT" == Stephen J Turnbull writes: SJT> If by "split" you mean RFC 2822 2.2.3 header folding, you SJT> can't split "spooge" like that, can you? There's no SJT> whitespace between the `o's. I believe you're right. Besides, that section recommends to fold at the highest syntactic level possible. We'd be okay if the header parts were wrapped in encodings, but they're not. -Barry From jra@baylink.com Wed Jun 5 17:14:39 2002 From: jra@baylink.com (Jay R. Ashworth) Date: Wed, 5 Jun 2002 12:14:39 -0400 Subject: [Mailman-Developers] Problem with invite confirmations in CVS References: <15482.21423.433540.541277@anthem.wooz.org> <20020225115400.33258@scfn.thpl.lib.fl.us> Message-ID: <20020605121439.27497@scfn.thpl.lib.fl.us> Well, I figured out my HostileAddress problem (a typo in CVS) and the problem that was hiding (it's Invite*New*Member, not InviteMember )... and now my confirmation reply is erroring out. The traceback: Jun 05 12:02:33 2002 (1522) Traceback (most recent call last): File "/appl/mailman2.1/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/appl/mailman2.1/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/appl/mailman2.1/Mailman/Queue/CommandRunner.py", line 192, in _dispose res.do_command('confirm', (mo.group('cookie'),)) File "/appl/mailman2.1/Mailman/Queue/CommandRunner.py", line 118, in do_command return handler.process(self, args) File "/appl/mailman2.1/Mailman/Commands/cmd_confirm.py", line 44, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/appl/mailman2.1/Mailman/MailList.py", line 1015, in ProcessConfirmation # Confirmation processing File "/appl/mailman2.1/Mailman/Pending.py", line 97, in confirm db = _load() File "/appl/mailman2.1/Mailman/Pending.py", line 121, in _load return cPickle.load(fp) AttributeError: 'module' object has no attribute 'UserDesc' I'm not sure if this is because InviteNewMember doesn't take the ack argument that ApprovedAddmember does, or if it's something else... I'd like to think that it's *not* the fact that I added a human-readable address to GetConfirmEmail -- which otherwise worked fine -- or that I changed the subject line (which, since I'm using VERPed confirmations, theoretically ought to be acceptable, as well. Any ideas? And, BTW: is there anyway to get the Python traceback to show the damned *values* of the arguments? Am I the only one who's noticed that the current scheme is almost useless? ;-) Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Baylink RFC 2100 The Suncoast Freenet The Things I Think Tampa Bay, Florida http://baylink.pitas.com +1 727 647 1274 "If you don't have a dream; how're you gonna have a dream come true?" -- Captain Sensible, The Damned (from South Pacific's "Happy Talk") From totschnig.michael@uqam.ca Wed Jun 5 20:02:41 2002 From: totschnig.michael@uqam.ca (totschnig.michael@uqam.ca) Date: Wed, 05 Jun 2002 15:02:41 -0400 Subject: [Mailman-Developers] Re: "Results of your email commands" In-Reply-To: <20020604061121.GL18804@merlins.org> (Marc MERLIN's message of "Mon, 3 Jun 2002 23:11:21 -0700") References: <20020604061121.GL18804@merlins.org> Message-ID: <86r8jlsg4u.fsf_-_@cmo.uqam.ca> Marc MERLIN a =E9crit: > On Sat, Jun 01, 2002 at 12:36:43PM -0400, totschnig.michael@uqam.ca wro= te: >> - Can I suppress the "Results of your email commands" email for this >> list or alternatively for the whole site? [...] > Yes to both, but not without hacking the code thank you for your answer. I tried to understand where the Results message is generated. My guess is that I had to uncomment the line =20 res.send_response() in CommandRunner.py, but I am afraid to break something. Our system is in use for some groups, so I'd rather ask before doing any changes that might affect the functionality. Thanks in advance, Michael From noreply@sourceforge.net Wed Jun 5 22:41:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 05 Jun 2002 14:41:49 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565052 ] make install fails Message-ID: Bugs item #565052, was opened at 2002-06-05 21:41 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565052&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Aliet Santiesteban Sifontes (aliet) Assigned to: Nobody/Anonymous (nobody) Summary: make install fails Initial Comment: Hi boy: I've been trying to build a rpm for mailman 2.1 b2 but the make install fails when you define something like this, make install prefix=/var/tmp/var/mailman var_prefix=/var/tmp/var/mailman I thought I was making something wrong so I did it with the sources rather than throught rpm, and I got the same error, this error causes that I can't not build a rpm for this version of mailman, this is the error Compiling: /var/tmp/var/mailman/Mailman/version.pr... Traceback (most recent call last); File "bin/update", line 45, in ? from Mailman import mm_cfg Import error: No module named Mailman make: *** [update] Error 1 I'm building in a Linux RedHat 7.3 ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565052&group_id=103 From noreply@sourceforge.net Thu Jun 6 02:37:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 05 Jun 2002 18:37:41 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses Message-ID: Bugs item #229568, was opened at 2001-01-20 22:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 Category: Pipermail Group: None >Status: Open Resolution: Works For Me Priority: 5 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" is resolved by pipermail as: listname@foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- >Comment By: Aharon Varady (aharon) Date: 2002-06-05 21:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient@phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- [Philly_ambient] tool!

    [Philly_ambient] tool!

    Posted by . . . .. . . . on Mon Jun 3 23:17:02 2002 

    hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina

  • Previous message: [Philly_ambient] Noise Deafinitions and playlist
  • Next message: [Philly_ambient] Do you hear what I hear? (re: noise deaf)
  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
    • --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: aharon@phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient@phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for ; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn@aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for ; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn@aol.com Message-ID: To: philly_ambient@phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin@phobos.serve.com Errors-To: philly_ambient-admin@phobos.serve.com X-BeenThere: philly_ambient@phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient@phobos.serve.com List-Help: List-Post: List-Subscribe: , List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts List-Unsubscribe: , List-Archive: X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient@phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 21:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 From dickson@permanentmail.com Thu Jun 6 10:52:50 2002 From: dickson@permanentmail.com (Paul Dickson) Date: Thu, 6 Jun 2002 02:52:50 -0700 Subject: [Mailman-Developers] Splitting long header lines and the "bug demonstration" In-Reply-To: <15613.31768.357110.313371@anthem.wooz.org> References: <15613.31768.357110.313371@anthem.wooz.org> Message-ID: <20020606025250.0e7671d0.dickson@permanentmail.com> On Tue, 4 Jun 2002 22:48:56 -0400, Barry A. Warsaw wrote: > I know what is causing > > http://mail.python.org/pipermail-21/mailman-developers/2002-June/012093.html > > It's the email package, and specifically it's Generator's behavior > when splitting long lines, i.e. Generator._split_header(). I received two messages today with the same problem, a blank line added after a long References: field. Trouble is both messages were from the Linux-Kernel mailing list which apparently is using majordomo! Apparent software download stream of that is: Postfix SMTPD32 6.06 (a windows server program) fetchmail 5.9.8 sendmail 8.11.6 The headers are apparently intact when processed by Mailman and Majordomo and mailing list info is attached. I'd like to hear from others to compare the Received: fields after the mailing list software is done. While I believe the line splitting is a Mailman problem (the email package mentioned above), the added blank line is coming from somewhere down the processing line. -Paul From noreply@sourceforge.net Thu Jun 6 16:09:03 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 06 Jun 2002 08:09:03 -0700 Subject: [Mailman-Developers] [ mailman-Patches-565346 ] suggested wording change Message-ID: Patches item #565346, was opened at 2002-06-06 11:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=565346&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Glen Foster (gafoster) Assigned to: Nobody/Anonymous (nobody) Summary: suggested wording change Initial Comment: The message: rejection = 'Non-members are not allowed to post messages to this list.' in ${PREFIX}/Mailman/Handlers/Hold.py line 60 is confusing when lists are run by membership-based organizations. It is unclear to non-subscribed posters that the word "members" refers to list members and not members of the organization itself. A suggested rewording is: rejection = 'You must subscribe to this list before you may post.' ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=565346&group_id=103 From noreply@sourceforge.net Thu Jun 6 17:09:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 06 Jun 2002 09:09:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses Message-ID: Bugs item #229568, was opened at 2001-01-20 19:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 Category: Pipermail Group: None Status: Open Resolution: Works For Me Priority: 5 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" is resolved by pipermail as: listname@foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-06-06 09:09 Message: Logged In: NO This comment doesn't directly address the case you report, but it might be related so I thought it worthwhile to submit. I see you are using MM2.0.9. I saw a similar problem with MM2.1b1, which was fixed in MM2.1b2. The problem then was that an address with a name "comment" would be displayed in the archive as the list name, whereas an address with a name comment would be displayed (properly) with the name. Example: "John Doe" jdoe@whereever.com displayed as "John Doe" whereas jdoe@whereever.com displayed as the list name. In your comment, you use an example with a name comment of "John", but in the example you provided there is no name comment field, so perhaps my statements here do apply. ---------------------------------------------------------------------- Comment By: Aharon Varady (aharon) Date: 2002-06-05 18:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient@phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- [Philly_ambient] tool!

      [Philly_ambient] tool!

      Posted by . . . .. . . . on Mon Jun 3 23:17:02 2002 

      hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina

    • Previous message: [Philly_ambient] Noise Deafinitions and playlist
    • Next message: [Philly_ambient] Do you hear what I hear? (re: noise deaf)
    • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
      • --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: aharon@phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient@phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for ; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn@aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for ; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn@aol.com Message-ID: To: philly_ambient@phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin@phobos.serve.com Errors-To: philly_ambient-admin@phobos.serve.com X-BeenThere: philly_ambient@phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient@phobos.serve.com List-Help: List-Post: List-Subscribe: , List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts List-Unsubscribe: , List-Archive: X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient@phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 18:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 From noreply@sourceforge.net Fri Jun 7 09:21:38 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 07 Jun 2002 01:21:38 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565706 ] user wrongly detected Message-ID: Bugs item #565706, was opened at 2002-06-07 08:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Enrico Cherubini (bestkevin) Assigned to: Nobody/Anonymous (nobody) Summary: user wrongly detected Initial Comment: Hi, I'm using mailman 2.0.6 and a user, that is in the mailing list, is not able to write in it after I closed the list to members only. He is member as I can see in the members list, here is what happen: Jun 07 09:31:06 2002 (29505) post to lugvr from ., size=1350, success the poster is identified as '.'....here are headers of an email he sent: From: .::Spark::. If you need any further information you are welcome ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_id=103 From noreply@sourceforge.net Fri Jun 7 09:43:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 07 Jun 2002 01:43:24 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565706 ] user wrongly detected Message-ID: Bugs item #565706, was opened at 2002-06-07 10:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Enrico Cherubini (bestkevin) Assigned to: Nobody/Anonymous (nobody) Summary: user wrongly detected Initial Comment: Hi, I'm using mailman 2.0.6 and a user, that is in the mailing list, is not able to write in it after I closed the list to members only. He is member as I can see in the members list, here is what happen: Jun 07 09:31:06 2002 (29505) post to lugvr from ., size=1350, success the poster is identified as '.'....here are headers of an email he sent: From: .::Spark::. If you need any further information you are welcome ---------------------------------------------------------------------- >Comment By: Simone Piunno (pioppo) Date: 2002-06-07 10:43 Message: Logged In: YES user_id=227443 Ciao Enrico! did you remember me? I was pioppo on #linux-it @ IrcNET :) I think 1st of all you should upgrade to Mailman 2.0.11 and/or to a more recent Python (I guess you are using 1.5.2) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565706&group_id=103 From noreply@sourceforge.net Fri Jun 7 14:16:11 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 07 Jun 2002 06:16:11 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565808 ] Broken options in Hungarian listinfo Message-ID: Bugs item #565808, was opened at 2002-06-07 15:16 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565808&group_id=103 Category: Web/CGI Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: szabolcs szigeti (szigi) Assigned to: Nobody/Anonymous (nobody) Summary: Broken options in Hungarian listinfo Initial Comment: Teh Hungarian template for listinfo is broken, instead of setting options, users are taken to subscription. Similar to bug [ 553033 ] "subscribing via web does not work" This should correct it: *** templates/hu/listinfo.html.orig Fri Jun 7 15:10:36 2002 --- templates/hu/listinfo.html Fri Jun 7 15:08:56 2002 *************** *** 127,133 ****

      ! --- 127,133 ----

      ! ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565808&group_id=103 From rodolfo@pilas.net Fri Jun 7 18:08:44 2002 From: rodolfo@pilas.net (Rodolfo Pilas) Date: 07 Jun 2002 14:08:44 -0300 Subject: [Mailman-Developers] postmap error since upgrade Message-ID: <1023469729.4912.18.camel@julieta> I upgraded to CVS version of 2002 06 03 but the create script shows the following error: Bug in Mailman version 2.1b2+ We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 82, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/lib/mailman/Mailman/Cgi/create.py", line 213, in process_request sys.modules[modname].create(mlist, cgi=1) File "/usr/lib/mailman/Mailman/MTA/Postfix.py", line 225, in create _update_maps() File "/usr/lib/mailman/Mailman/MTA/Postfix.py", line 53, in _update_maps raise RuntimeError, msg % (vcmd, status, errstr) RuntimeError: command failed: /usr/sbin/postmap /var/spool/mailman/data/virtual-mailman (status: 1, Operation not permitt I solve it running from the root shell the postmap virtual-mailman command. The virtual-mailman file is mailman:mailman ownered. Can you tell me how to fix it? Thank you. -- Rodolfo Pilas Quien los puso a estos tipos donde estan, rodolfo@pilas.net Quien los deja seguir en su lugar, http://rodolfo.pilas.net Quien los baja ahora de su altar, Yahoo ID: ysidorito Quien les paga para que hagan lo que haran http://xtralinux.org -=# Apocalipsis Now % Cuarteto de Nos #=- Public GnuPG key: http://www.keyserver.net 1024D/57153363 2001-06-02 key fingerprint = DAAE 3246 3F7D A420 B7A0 48A5 D120 C773 5715 3363 From noreply@sourceforge.net Fri Jun 7 19:02:50 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 07 Jun 2002 11:02:50 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565917 ] mailmanctl bombs after unclean shutdown Message-ID: Bugs item #565917, was opened at 2002-06-07 18:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Dale Stimson (dstimson) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl bombs after unclean shutdown Initial Comment: Environment: Red Hat 7.3, latest errata, Mailman 2.1b2 I see that this problem still exists in the current CVS as of a day or two ago. When mailman restarts after having been shutdown uncleanly (e.g., when rebooting following a crash), it bombs leaving no qrunners active with the following in the log: Jun 04 18:05:13 2002 mailmanctl(1572): Traceback (most recent call last): Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 502, in ? Jun 04 18:05:13 2002 mailmanctl(1572): main() Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 352, in main Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 203, in acquire_lock Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock_1(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 197, in acquire_lock_1 Jun 04 18:05:13 2002 mailmanctl(1572): os.unlink(tempfile) Jun 04 18:05:13 2002 mailmanctl(1572): OSError : [Errno 2] No such file or directory: 'master-qrunner.cupro.opengvs.com.9014' Diagnosis: In file bin/mailmanctl, function acquire_lock_1 is attempting to delete the lock file left over from the last run. It calls function get_lock_data to find the name of the old lock file that is to be deleted. Function get_lock_data (incorrectly) returns the file name with the directory part of the path stripped, thereby causing the delete to fail and the trap to occur. Function get_lock_data should instead return the entire file path, including directories. The patch given below corrects the behavior of get_lock_data. As an aside, it would be nice if acquire_lock_1 was more forgiving if the os.unlink calls fail due to "no such file". I have not submitted a patch for that as I don't know the appropriate python semantics. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_id=103 From noreply@sourceforge.net Fri Jun 7 19:14:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 07 Jun 2002 11:14:24 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-565917 ] mailmanctl bombs after unclean shutdown Message-ID: Bugs item #565917, was opened at 2002-06-07 18:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_id=103 Category: command line scripts Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Dale Stimson (dstimson) Assigned to: Nobody/Anonymous (nobody) Summary: mailmanctl bombs after unclean shutdown Initial Comment: Environment: Red Hat 7.3, latest errata, Mailman 2.1b2 I see that this problem still exists in the current CVS as of a day or two ago. When mailman restarts after having been shutdown uncleanly (e.g., when rebooting following a crash), it bombs leaving no qrunners active with the following in the log: Jun 04 18:05:13 2002 mailmanctl(1572): Traceback (most recent call last): Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 502, in ? Jun 04 18:05:13 2002 mailmanctl(1572): main() Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 352, in main Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 203, in acquire_lock Jun 04 18:05:13 2002 mailmanctl(1572): lock = acquire_lock_1(force) Jun 04 18:05:13 2002 mailmanctl(1572): File "/var/mailman/bin/mailmanctl", line 197, in acquire_lock_1 Jun 04 18:05:13 2002 mailmanctl(1572): os.unlink(tempfile) Jun 04 18:05:13 2002 mailmanctl(1572): OSError : [Errno 2] No such file or directory: 'master-qrunner.cupro.opengvs.com.9014' Diagnosis: In file bin/mailmanctl, function acquire_lock_1 is attempting to delete the lock file left over from the last run. It calls function get_lock_data to find the name of the old lock file that is to be deleted. Function get_lock_data (incorrectly) returns the file name with the directory part of the path stripped, thereby causing the delete to fail and the trap to occur. Function get_lock_data should instead return the entire file path, including directories. The patch given below corrects the behavior of get_lock_data. As an aside, it would be nice if acquire_lock_1 was more forgiving if the os.unlink calls fail due to "no such file". I have not submitted a patch for that as I don't know the appropriate python semantics. ---------------------------------------------------------------------- >Comment By: Dale Stimson (dstimson) Date: 2002-06-07 18:14 Message: Logged In: YES user_id=559033 Please ignore uploaded file sf1.txt (it won't let me delete it), which has cruft in it (the problem report text), as opposed to just the patch). The file with just the patch is sf.txt. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=565917&group_id=103 From noreply@sourceforge.net Sat Jun 8 13:24:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 08 Jun 2002 05:24:48 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566149 ] qrunner high CPU load Message-ID: Bugs item #566149, was opened at 2002-06-08 14:24 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566149&group_id=103 Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: qrunner high CPU load Initial Comment: On my private, low use P60 server qrunner uses about 10 s CPU time and is run every minute. That's 15% overall CPU time or 4 hours/day for a mostly idle task. It would be preferable if mail handling were triggered by incoming mails. That would also deliver them quicker. If there is still need for recurring checking maybe you can make that less resource consuming. Thank you, Bernhard ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566149&group_id=103 From noreply@sourceforge.net Sat Jun 8 13:29:24 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 08 Jun 2002 05:29:24 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566150 ] real names Message-ID: Bugs item #566150, was opened at 2002-06-08 14:29 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: real names Initial Comment: I'd like it if people could enter their real (first, last) name in their subscription. It is nicer to receive mails with ones real name. Thanks, Bernhard ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 From noreply@sourceforge.net Sat Jun 8 22:44:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 08 Jun 2002 14:44:09 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566301 ] umbrella list: unsubscribe key public Message-ID: Bugs item #566301, was opened at 2002-06-08 23:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 Category: security/privacy Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: umbrella list: unsubscribe key public Initial Comment: Mailman offers a feature to set up an "umbrella-list", which is used if a list just has other lists as members. Assume we have an umbrella-list U, which has to members, X and Y - both are also lists. Now, cleverly, the monthly password reminders are not sent to X and Y, but to "X-owner" and "Y-owner" instead, so this information should reach the owners of the subscribed lists (sending a password reminder to X would mean giving each member of the X list the power to unsubscribe X from U etc.). But: If a member of X or Y opens the member options page (http://my.server.net/mailman/options/U/X) and clicks on the "unsubscribe" button, the necessary key is mailed to X (and not to "X-owner"). This is probably not what we want. If the list archive is not private, the password is even available to everyone out there. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 From noreply@sourceforge.net Sat Jun 8 22:44:54 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sat, 08 Jun 2002 14:44:54 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566301 ] umbrella list: unsubscribe key public Message-ID: Bugs item #566301, was opened at 2002-06-08 23:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 Category: security/privacy Group: 2.1 beta Status: Open Resolution: None >Priority: 7 Submitted By: Stefan Divjak (stdivjak) Assigned to: Nobody/Anonymous (nobody) Summary: umbrella list: unsubscribe key public Initial Comment: Mailman offers a feature to set up an "umbrella-list", which is used if a list just has other lists as members. Assume we have an umbrella-list U, which has to members, X and Y - both are also lists. Now, cleverly, the monthly password reminders are not sent to X and Y, but to "X-owner" and "Y-owner" instead, so this information should reach the owners of the subscribed lists (sending a password reminder to X would mean giving each member of the X list the power to unsubscribe X from U etc.). But: If a member of X or Y opens the member options page (http://my.server.net/mailman/options/U/X) and clicks on the "unsubscribe" button, the necessary key is mailed to X (and not to "X-owner"). This is probably not what we want. If the list archive is not private, the password is even available to everyone out there. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566301&group_id=103 From noreply@sourceforge.net Sun Jun 9 15:53:03 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 09 Jun 2002 07:53:03 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566482 ] Mod req notification but nothing shown Message-ID: Bugs item #566482, was opened at 2002-06-09 09:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Alan Schwartz (alansz) Assigned to: Nobody/Anonymous (nobody) Summary: Mod req notification but nothing shown Initial Comment: Running 2.1b2 cvs checkout of June 3 2002. Upgraded a previously 2.0.11 server with several lists. Everything seems to be operating ok mailwise except I'm receiving a daily email from checkdbs on two of the lists directing me to their admindb pages for pending requests. When I visit those urls, there are no pending requests. The lists' request.db's appear to be binary-identical to those of the other mailing lists that don't have any pending requests (that is, empty). I haven't managed to figure out why checkdbs is generating these notices. Help would be appreciated. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 From noreply@sourceforge.net Mon Jun 10 06:09:12 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 09 Jun 2002 22:09:12 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566691 ] check for subscriber fails w/ moderated Message-ID: Bugs item #566691, was opened at 2002-06-10 01:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566691&group_id=103 Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Garvas (jgarvas) Assigned to: Nobody/Anonymous (nobody) Summary: check for subscriber fails w/ moderated Initial Comment: When you run a list that is non-moderated, but you limit posts to the subscribers list, a post by a non-member results in this error: Reason: Post by non-member to a members-only list If you go into "Privacy Options" and change "Must posts be approved by an administrator?" and maintain "Restrict posting privilege to list members" a post by a non-subscriber results in THIS reason: Reason: Post to moderated list Unless I am missing a configuration option, I believe this is a flaw in the order in which mailman is checking posts. Even if a list is moderated, the reason this individual post was rejected should still read Reason: Post by non-member to a members-only list or, a new reason should be made like this: Reason: Post by a non-member to a members-only AND moderated list This may seem like a silly request, but if you run a members only list that happens to be moderated as well, you run into the problem of accidentally approving a post from a non-member when the content of that post was "on topic". Is there a fix for this? Would this classify as a bug? Does anyone know of any other work arounds? When you have a few thousand people on a mailing list, its not really easy to realize on your own that a specific individual isn't a subscriber to the list. Especially when you have multiple individuals help administrate the list itself. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566691&group_id=103 From techgrrl@beeze.com Mon Jun 10 19:13:31 2002 From: techgrrl@beeze.com (Sarah K. Miller) Date: Mon, 10 Jun 2002 11:13:31 -0700 Subject: [Mailman-Developers] List Reply Address Message-ID: <00d501c210aa$86e2cb10$7941a8c0@home.beeze.com> I'm using 2.1b2 and I've started getting complaints about the "reply" = address in the digests. It appears that all digests come from their = respective lists -request address with no "reply-to" address specified. = That means if someone just clicks "reply", their message goes to the = request address instead of to the regular list. Is this intentional = behavior or am I missing a setting somewhere?? -- Sarah Plus =E7a change, plus c'est la m=EAme chose From noreply@sourceforge.net Mon Jun 10 23:13:06 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 10 Jun 2002 15:13:06 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-567096 ] list_members script export Name+Address Message-ID: Feature Requests item #567096, was opened at 2002-06-10 19:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=567096&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Rodolfo Pilas (alkalino) Assigned to: Nobody/Anonymous (nobody) Summary: list_members script export Name+Address Initial Comment: I uses MM 2.1b2+ (from CVS this month -June 2002) The mass subscription (web) option enables me to put one user address form each line with this format: Name Surname and works ok. However the $PREFIX/bin/list_members script do not export with this format, it list name@address.com only. Please, add to list_members a complete user data exportation. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=350103&aid=567096&group_id=103 From noreply@sourceforge.net Tue Jun 11 03:14:56 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 10 Jun 2002 19:14:56 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-229568 ] Pipermail won't resolve author names of aol.com addresses Message-ID: Bugs item #229568, was opened at 2001-01-20 21:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 Category: Pipermail Group: None Status: Open Resolution: Works For Me Priority: 5 Submitted By: Aharon Varady (aharon) Assigned to: Nobody/Anonymous (nobody) Summary: Pipermail won't resolve author names of aol.com addresses Initial Comment: Pipermail does not resolve the "author" of emails sent from aol.com. Instead, Pipermail gives the email address of the listserve. For example: "John" is resolved by pipermail as: listname@foo.com and not as John. This bug only occurs for users of aol.com addresses. ---------------------------------------------------------------------- Comment By: Ava Jarvis (katanalynx) Date: 2002-06-10 21:14 Message: Logged In: YES user_id=561110 This bug -- for version 2.0.11 at least -- seems to occur when 'from' only contains the email address. There's some code in pipermail.py (version 2.0.11), line 177: # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) if self.author == "": self.author = self.email If reply-to is set, then it is always taken as the author's email address. However, some lists set the reply-to field to be, for instance, the list address.... and you can guess what happens next when there is no name comment/author. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2002-06-06 11:09 Message: Logged In: NO This comment doesn't directly address the case you report, but it might be related so I thought it worthwhile to submit. I see you are using MM2.0.9. I saw a similar problem with MM2.1b1, which was fixed in MM2.1b2. The problem then was that an address with a name "comment" would be displayed in the archive as the list name, whereas an address with a name comment would be displayed (properly) with the name. Example: "John Doe" jdoe@whereever.com displayed as "John Doe" whereas jdoe@whereever.com displayed as the list name. In your comment, you use an example with a name comment of "John", but in the example you provided there is no name comment field, so perhaps my statements here do apply. ---------------------------------------------------------------------- Comment By: Aharon Varady (aharon) Date: 2002-06-05 20:37 Message: Logged In: YES user_id=139355 Well, this remains (and has always been) a problem for my lists. I have never had a user posting with an aol.com address that this hasn't been the case with. Currently my solution is to replace the wrong address shown (philly_ambient@phobos.serve.com) with a generic or balnk mark. Here is the html source of a typical email from our pipermail archive, and below it the source email with headers. ------------------------------------------------------------- [Philly_ambient] tool!

        [Philly_ambient] tool!

        Posted by . . . .. . . . on Mon Jun 3 23:17:02 2002 

        hey all
a friend can get me some free tickets to see TOOL on monday
august 12 at 
sovereign bank arena in trenton. i know mondays suck, but oh
well. is anyone 
here into going?  if so, contact me privately.  i know it's
not ambient, but 
neither is some of what we discuss here :)
let me know asap, please

gina

      • Previous message: [Philly_ambient] Noise Deafinitions and playlist
      • Next message: [Philly_ambient] Do you hear what I hear? (re: noise deaf)
      • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
        • --------------------------------------------------------------------- Here is the original email with headers: --------------------------------------------------------------- >From - Tue Jun 04 01:16:56 2002 X-UIDL: m;n!!9'f!!a2E"!3;D"! X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: Delivered-To: aharon@phobos.serve.com Received: from phobos.serve.com (localhost.localdomain [127.0.0.1]) by phobos.serve.com (Postfix) with ESMTP id 6BC4D52D2B; Mon, 3 Jun 2002 23:17:06 -0400 (EDT) Delivered-To: philly_ambient@phobos.serve.com Received: from imo-r06.mx.aol.com (imo-r06.mx.aol.com [152.163.225.102]) by phobos.serve.com (Postfix) with ESMTP id 6F82F52D1D for ; Mon, 3 Jun 2002 23:16:46 -0400 (EDT) Received: from Mistsojorn@aol.com by imo-r06.mx.aol.com (mail_out_v32.5.) id p.d4.184e63f9 (17378) for ; Mon, 3 Jun 2002 23:14:35 -0400 (EDT) From: Mistsojorn@aol.com Message-ID: To: philly_ambient@phobos.serve.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 4.0 for Mac - Post-GM sub 66 Subject: [Philly_ambient] tool! Sender: philly_ambient-admin@phobos.serve.com Errors-To: philly_ambient-admin@phobos.serve.com X-BeenThere: philly_ambient@phobos.serve.com X-Mailman-Version: 2.0.9 Precedence: bulk Reply-To: philly_ambient@phobos.serve.com List-Help: List-Post: List-Subscribe: , List-Id: a discussion list relevant to Philadelphia Ambient and Experimental Psychedelic Music Enthusiasts List-Unsubscribe: , List-Archive: X-Original-Date: Mon, 3 Jun 2002 23:14:35 EDT Date: Mon, 3 Jun 2002 23:14:35 EDT X-UIDL: m;n!!9'f!!a2E"!3;D"! hey all a friend can get me some free tickets to see TOOL on monday august 12 at sovereign bank arena in trenton. i know mondays suck, but oh well. is anyone here into going? if so, contact me privately. i know it's not ambient, but neither is some of what we discuss here :) let me know asap, please gina _______________________________________________ Philly_ambient mailing list Philly_ambient@phobos.serve.com Subscribe, Unsubscribe, Edit Options at: http://phobos.serve.com/mailman/listinfo/philly_ambient a PAC(MaN) List http://simpletone.com -------------------------------------------------------------------- I don't know why pipermail would treat my aol subscribers different either. But it is. Aharon ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-04-28 20:11 Message: Logged In: YES user_id=12800 Bizarre. I've never seen this, and I can't see any reason why Pipermail would treat aol.com addresses any different. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=229568&group_id=103 From lrosa@mail.hypertrek.info Tue Jun 11 05:23:52 2002 From: lrosa@mail.hypertrek.info (Luigi Rosa) Date: Tue, 11 Jun 2002 06:23:52 +0200 Subject: [Mailman-Developers] Strange Reply-To in 2.1b2 Message-ID: <32150827484.20020611062352@mail.hypertrek.info> Hello mailman-developers, with 2.1b2 often (but not always, I am not yet able to say exactly when) the Reply-To field of a message posted in reply of another has this value: Reply-To: Luigi Rosa , staff@mail.hypertrek.info where the first mail is the personal mail of the person who replied and the second is the address of the list. Is this a bug or a feature? Thanks. -- Best regards, Luigi mailto:lrosa@mail.hypertrek.info From noreply@sourceforge.net Tue Jun 11 05:50:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 10 Jun 2002 21:50:05 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566691 ] check for subscriber fails w/ moderated Message-ID: Bugs item #566691, was opened at 2002-06-10 01:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566691&group_id=103 Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Garvas (jgarvas) Assigned to: Nobody/Anonymous (nobody) Summary: check for subscriber fails w/ moderated Initial Comment: When you run a list that is non-moderated, but you limit posts to the subscribers list, a post by a non-member results in this error: Reason: Post by non-member to a members-only list If you go into "Privacy Options" and change "Must posts be approved by an administrator?" and maintain "Restrict posting privilege to list members" a post by a non-subscriber results in THIS reason: Reason: Post to moderated list Unless I am missing a configuration option, I believe this is a flaw in the order in which mailman is checking posts. Even if a list is moderated, the reason this individual post was rejected should still read Reason: Post by non-member to a members-only list or, a new reason should be made like this: Reason: Post by a non-member to a members-only AND moderated list This may seem like a silly request, but if you run a members only list that happens to be moderated as well, you run into the problem of accidentally approving a post from a non-member when the content of that post was "on topic". Is there a fix for this? Would this classify as a bug? Does anyone know of any other work arounds? When you have a few thousand people on a mailing list, its not really easy to realize on your own that a specific individual isn't a subscriber to the list. Especially when you have multiple individuals help administrate the list itself. ---------------------------------------------------------------------- >Comment By: Jeff Garvas (jgarvas) Date: 2002-06-11 00:50 Message: Logged In: YES user_id=560554 I've been experimenting with Mailman/Handlers/Hold.py (playing with python for the first time ever) and after spending some time trying to figure out how to compile it, I came up with a simple idea. I moved the code that checks if the list is moderated to immediately after the code that checks if the list is "subscriber only" and the post is coming from a subscriber or not. The result: Exactly what I want. However, I don't know if I've managed to miss something obvious by doing this. Have I possibly broken an aspect of Mailman and I'm not realizing it? With this modification to Hold.py a post from a non- subscriber to a moderated (and subscriber only) list ends up in the administrative queue with a reason of "Post by non- member to member-only list" instead of a moderated list bounce. This seems like the logical and proper way for this to operate. Can someone tell me if this appears to be a safe and proper solution? If so, I think it should be rolled into the current version. I generated a patch file with diff -C 2, attached here, but possibly not created properly. Beware when running it! :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566691&group_id=103 From noreply@sourceforge.net Tue Jun 11 08:13:57 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 11 Jun 2002 00:13:57 -0700 Subject: [Mailman-Developers] [ mailman-Patches-567288 ] 'rejection-notice' breaks METAFMT_ASCII Message-ID: Patches item #567288, was opened at 2002-06-11 09:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Maximillian Dornseif (mdornseif) Assigned to: Nobody/Anonymous (nobody) Summary: 'rejection-notice' breaks METAFMT_ASCII Initial Comment: The variable 'rejection-notice' will not work well with METADATA_FORMAT = METAFMT_ASCII or HOLD_MESSAGES_AS_PICKLES = 0. Renaming to 'rejection_notice' helps. I guess this change breaks kompatibility with old queues. In case SF.net upload breaks: http://c0re.jp/c0de/misc/mailman-2.1b2-rejection-notice.patch Index: ./Mailman/Cgi/admindb.py - text = Utils.wrap(msgdata.get('rejection-notice', + text = Utils.wrap(msgdata.get('rejection_notice', Index: ./Mailman/Handlers/Hold.py - msgdata['rejection-notice'] = Utils.wrap(exc.rejection_notice(mlist)) + msgdata['rejection_notice'] = Utils.wrap(exc.rejection_notice(mlist)) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 From noreply@sourceforge.net Tue Jun 11 14:28:27 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 11 Jun 2002 06:28:27 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566482 ] Mod req notification but nothing shown Message-ID: Bugs item #566482, was opened at 2002-06-09 14:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Alan Schwartz (alansz) Assigned to: Nobody/Anonymous (nobody) Summary: Mod req notification but nothing shown Initial Comment: Running 2.1b2 cvs checkout of June 3 2002. Upgraded a previously 2.0.11 server with several lists. Everything seems to be operating ok mailwise except I'm receiving a daily email from checkdbs on two of the lists directing me to their admindb pages for pending requests. When I visit those urls, there are no pending requests. The lists' request.db's appear to be binary-identical to those of the other mailing lists that don't have any pending requests (that is, empty). I haven't managed to figure out why checkdbs is generating these notices. Help would be appreciated. ---------------------------------------------------------------------- Comment By: Michael Totschnig (totschnig) Date: 2002-06-11 13:28 Message: Logged In: YES user_id=318184 I see these phantom request notifcations too, and I have spotted a pattern that might help debug them. I did not see them every morning, but only once in a while. It seems that they are triggered by subscriptions to the lists. Every time someone has confirmed his subscription during the preceding 24 hours, I get these notification requests and the number of requests mentioned in the notification is identical to the number of subscription confirmations. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 From noreply@sourceforge.net Tue Jun 11 16:38:08 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 11 Jun 2002 08:38:08 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566482 ] Mod req notification but nothing shown Message-ID: Bugs item #566482, was opened at 2002-06-09 09:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 Category: None Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Alan Schwartz (alansz) Assigned to: Nobody/Anonymous (nobody) Summary: Mod req notification but nothing shown Initial Comment: Running 2.1b2 cvs checkout of June 3 2002. Upgraded a previously 2.0.11 server with several lists. Everything seems to be operating ok mailwise except I'm receiving a daily email from checkdbs on two of the lists directing me to their admindb pages for pending requests. When I visit those urls, there are no pending requests. The lists' request.db's appear to be binary-identical to those of the other mailing lists that don't have any pending requests (that is, empty). I haven't managed to figure out why checkdbs is generating these notices. Help would be appreciated. ---------------------------------------------------------------------- >Comment By: Alan Schwartz (alansz) Date: 2002-06-11 10:38 Message: Logged In: YES user_id=559669 However, I got a new one yesterday for a list that doesn't allow subscription requests at all. It has 13 members. I had emailed a message to the list the day before, and there were a 3 bounces (setting bounce score to 1.0 for each). But no subscribe requests or unsubscribe requests. Maybe it's all tied into the bounce/confirm processing, though? ---------------------------------------------------------------------- Comment By: Michael Totschnig (totschnig) Date: 2002-06-11 08:28 Message: Logged In: YES user_id=318184 I see these phantom request notifcations too, and I have spotted a pattern that might help debug them. I did not see them every morning, but only once in a while. It seems that they are triggered by subscriptions to the lists. Every time someone has confirmed his subscription during the preceding 24 hours, I get these notification requests and the number of requests mentioned in the notification is identical to the number of subscription confirmations. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=566482&group_id=103 From noreply@sourceforge.net Tue Jun 11 18:15:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 11 Jun 2002 10:15:41 -0700 Subject: [Mailman-Developers] [ mailman-Patches-567488 ] possible fix for Hold.py check order Message-ID: Patches item #567488, was opened at 2002-06-11 13:15 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567488&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Garvas (jgarvas) Assigned to: Nobody/Anonymous (nobody) Summary: possible fix for Hold.py check order Initial Comment: I don't like the way Mailman checks posts in Hold.py -- I posted to mailman-users and created a bug, but this was probably too low of a priority for anyone to notice it. Basically I want to know if a user posting to a list is a subscriber (even if the list is moderated) when the list is in "subscriber only" mode. I went into Hold.py, knowing almost nothing about Python, and basically took the if block that checks for moderated status and moved it below the if block that checks for subscriber status. I created this patch by putting my version of Hold.py in the root of the directory you get when you un-tar mailman, then I ran: diff -C 2 Mailman/Handlers/Hold.py Hold.py This might not be the proper way to make the patch file, but I've never done it before. I would like some input/feedback on if this is safe. I can't fathom this breaking anything, but others obviously know this code much better than I do -- I just learned how to compile my python script last night ;) -Jeff ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567488&group_id=103 From bob@nleaudio.com Wed Jun 12 04:17:25 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Tue, 11 Jun 2002 23:17:25 -0400 Subject: [Mailman-Developers] Mail forwarding loop Message-ID: <3D06BD45.708BDE1C@nleaudio.com> Hi Gang, I've noticed that perhaps once or twice a month, I get a "Mail forwarding loop" error in my postfix log from a 2.0.x mailman install. The sender gets the bounce, yet the message still seems to get delivered to the list, and distributed, so it's not a show-stopper; just a minor inconvenience. Has anyone else seen this? Could this be a Postfix thing? Bob From noreply@sourceforge.net Wed Jun 12 05:44:48 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 11 Jun 2002 21:44:48 -0700 Subject: [Mailman-Developers] [ mailman-Patches-567834 ] Fix for options wording Message-ID: Patches item #567834, was opened at 2002-06-12 00:44 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567834&group_id=103 Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Jon Parise (parise) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for options wording Initial Comment: On the subscriber's options screen in Mailman 2.1b2+, this text existis: "Conceal yourself from subscriber list? When someone views the list membership, your email address is normally shown (in an obscured fashion to thwart spam harvesters). If you do not want your email address to show up on this membership roster, select No for this option." It sounds like that "No" should be changed to a "Yes" for the statements to agree and make sense. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567834&group_id=103 From marc_news@vasoftware.com Wed Jun 12 08:08:57 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Wed, 12 Jun 2002 00:08:57 -0700 Subject: [Mailman-Developers] 1 SA-Exim moderator request(s) waiting Message-ID: <20020612070856.GF21363@merlins.org> So I get this every day, but the page tells me there are no pending requests. Any ideas? moremagic:/var/local/mailman/lists/sa-exim# l total 28 drwxrwsr-x 2 root mailman 4096 Jun 12 00:05 ./ drwxrwsr-x 22 root mailman 4096 May 7 21:44 ../ -rw-rw---- 1 www-data mailman 5541 Jun 12 00:05 config.pck -rw-rw---- 1 mailman mailman 5543 Jun 11 17:00 config.pck.last -rw-rw-r-- 1 www-data mailman 29 Jun 12 00:05 request.db moremagic:/var/local/mailman/lists/sa-exim# ~mailman/bin/dumpdb request.db {'version': (0, 1)} moremagic:/var/local/mailman/lists/sa-exim# ----- Forwarded message from sa-exim-bounces@merlins.org ----- Received: from localhost ([127.0.0.1]:35607 helo=moremagic.merlins.org) by mail2.merlins.org with esmtp (Exim 4.04 #161 (Debian)) id 17HvYT-0007vO-00 for <@merlins.org>; Tue, 11 Jun 2002 17:00:05 -0700 Received: from localhost ([127.0.0.1]:55275 helo=moremagic.merlins.org) by mail2.merlins.org with esmtp (Exim 4.04 #161 (Debian)) id 17HvYR-0000qb-00 for ; Tue, 11 Jun 2002 17:00:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: 1 SA-Exim moderator request(s) waiting From: sa-exim-xxxxxxx@merlins.org To: sa-exim-xxxxx@merlins.org Message-ID: Date: Tue, 11 Jun 2002 17:00:02 -0700 Precedence: bulk X-BeenThere: sa-exim@lists.merlins.org X-Mailman-Version: 2.1b2+ X-List-Administrivia: yes List-Id: Discussions on the SpamAssassin in exim at SMTP time Sender: sa-exim-bounces@xxxlins.org Errors-To: sa-exim-bounces@xxxxxxxxxlins.org Content-Length: 266 Lines: 9 The SA-Exim@xxxxxxxerlins.org mailing list has 1 request(s) waiting for your consideration at: http://lists.merlins.org/lists/admindb/sa-exim Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. ----- End forwarded message ----- -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From marc_news@vasoftware.com Wed Jun 12 08:17:22 2002 From: marc_news@vasoftware.com (Marc MERLIN) Date: Wed, 12 Jun 2002 00:17:22 -0700 Subject: [Mailman-Developers] 1 SA-Exim moderator request(s) waiting In-Reply-To: <200206120714.g5C7EiOl003764@utopia.West.Sun.COM> References: <200206120714.g5C7EiOl003764@utopia.West.Sun.COM> Message-ID: <20020612071722.GG21363@merlins.org> On Wed, Jun 12, 2002 at 12:13:43AM -0700, Dan Mick wrote: > isn't it ~mailman/data/pending.pck? You're right, but I can't find any reference to my sa-exim list moremagic:/var/local/mailman/data# ~mailman/bin/dumpdb pending.pck { '056e5cd9a29d674cfce6b9c98cfe24aed0a166c9': ('H', 80), '3504c03abd43c53e7a31f30cb2fe0e2bfb4e648f': ( 'E', 'zark', 'stephane.duchadeau@alcatel.fr'), 'e2e830fe8936dc9e419f38eab8caa1ed2c192d68': ( 'E', 'zark', 'gwenaelle.habasque@alcatel.fr'), 'evictions': { '056e5cd9a29d674cfce6b9c98cfe24aed0a166c9': 1023972680.6694781, '3504c03abd43c53e7a31f30cb2fe0e2bfb4e648f': 1023955695.506128, 'e2e830fe8936dc9e419f38eab8caa1ed2c192d68': 1023955633.799271}, 'version': 1} -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key From noreply@sourceforge.net Wed Jun 12 13:31:51 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 12 Jun 2002 05:31:51 -0700 Subject: [Mailman-Developers] [ mailman-Patches-567288 ] 'rejection-notice' breaks METAFMT_ASCII Message-ID: Patches item #567288, was opened at 2002-06-11 09:13 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None >Priority: 7 Submitted By: Maximillian Dornseif (mdornseif) Assigned to: Nobody/Anonymous (nobody) Summary: 'rejection-notice' breaks METAFMT_ASCII Initial Comment: The variable 'rejection-notice' will not work well with METADATA_FORMAT = METAFMT_ASCII or HOLD_MESSAGES_AS_PICKLES = 0. Renaming to 'rejection_notice' helps. I guess this change breaks kompatibility with old queues. In case SF.net upload breaks: http://c0re.jp/c0de/misc/mailman-2.1b2-rejection-notice.patch Index: ./Mailman/Cgi/admindb.py - text = Utils.wrap(msgdata.get('rejection-notice', + text = Utils.wrap(msgdata.get('rejection_notice', Index: ./Mailman/Handlers/Hold.py - msgdata['rejection-notice'] = Utils.wrap(exc.rejection_notice(mlist)) + msgdata['rejection_notice'] = Utils.wrap(exc.rejection_notice(mlist)) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=567288&group_id=103 From barry@zope.com Wed Jun 12 14:56:14 2002 From: barry@zope.com (Barry A. Warsaw) Date: Wed, 12 Jun 2002 09:56:14 -0400 Subject: [Mailman-Developers] 1 SA-Exim moderator request(s) waiting References: <20020612070856.GF21363@merlins.org> Message-ID: <15623.21246.904567.249026@anthem.wooz.org> >>>>> "MM" == Marc MERLIN writes: MM> So I get this every day, but the page tells me there are no MM> pending requests. I've seen this on my MM2.1 system too. I'm sure it's a bug, but I still don't have time to fix it. That should change as soon as I've got the network up in the new house. DSL-rocks-as-long-as-it-works-ly y'rs, -Barry From smontgom@bcgsc.bc.ca Tue Jun 11 20:07:41 2002 From: smontgom@bcgsc.bc.ca (Stephen Montgomery) Date: Tue, 11 Jun 2002 12:07:41 -0700 Subject: [Mailman-Developers] Searchable Archives Message-ID: <3D064A7D.BABB75E5@bcgsc.bc.ca> Hi, I was wondering if mailman offers the opportunity for keyword searchable archives. How do I go about implementing it? With my list I'm envisioning getting tired of answering the same questions and would like users to be able to search the archives easily. Cheers, Stephen -- Stephen Montgomery Graduate Student, Bioinformatics Genome Science Centre Vancouver, BC Canada Tel 604-877-6000 ext. 2543 From noreply@sourceforge.net Wed Jun 12 17:09:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 12 Jun 2002 09:09:55 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-568086 ] Crash when accessing list page Message-ID: Bugs item #568086, was opened at 2002-06-12 16:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Garey Mills (gareytm) Assigned to: Nobody/Anonymous (nobody) Summary: Crash when accessing list page Initial Comment: Install goes well, though I have to run 'check_perms -f' because directories are not 02775. After creating 'mailman' list, however, when I try to access list page I get an error that says that the email.Iterators module does not exist. I can see it in 'pythonlib/email', though permissions are 600. The list URL is http://www.lib.berkeley.edu/mailman/listinfo/mailman ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 From noreply@sourceforge.net Wed Jun 12 17:45:09 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 12 Jun 2002 09:45:09 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-568086 ] Crash when accessing list page Message-ID: Bugs item #568086, was opened at 2002-06-12 16:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Garey Mills (gareytm) Assigned to: Nobody/Anonymous (nobody) Summary: Crash when accessing list page Initial Comment: Install goes well, though I have to run 'check_perms -f' because directories are not 02775. After creating 'mailman' list, however, when I try to access list page I get an error that says that the email.Iterators module does not exist. I can see it in 'pythonlib/email', though permissions are 600. The list URL is http://www.lib.berkeley.edu/mailman/listinfo/mailman ---------------------------------------------------------------------- >Comment By: Garey Mills (gareytm) Date: 2002-06-12 16:45 Message: Logged In: YES user_id=555793 I have gotten things to work by setting perms on all '*.py*' files in pythonlib and its subdirectories. Perhaps these permissions could have been checked with 'check_perms' ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 From noreply@sourceforge.net Wed Jun 12 17:45:58 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 12 Jun 2002 09:45:58 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-568086 ] Crash when accessing list page Message-ID: Bugs item #568086, was opened at 2002-06-12 16:09 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 Category: configuring/installing Group: 2.1 beta >Status: Closed Resolution: None Priority: 5 Submitted By: Garey Mills (gareytm) Assigned to: Nobody/Anonymous (nobody) Summary: Crash when accessing list page Initial Comment: Install goes well, though I have to run 'check_perms -f' because directories are not 02775. After creating 'mailman' list, however, when I try to access list page I get an error that says that the email.Iterators module does not exist. I can see it in 'pythonlib/email', though permissions are 600. The list URL is http://www.lib.berkeley.edu/mailman/listinfo/mailman ---------------------------------------------------------------------- Comment By: Garey Mills (gareytm) Date: 2002-06-12 16:45 Message: Logged In: YES user_id=555793 I have gotten things to work by setting perms on all '*.py*' files in pythonlib and its subdirectories. Perhaps these permissions could have been checked with 'check_perms' ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568086&group_id=103 From noreply@sourceforge.net Wed Jun 12 22:48:05 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 12 Jun 2002 14:48:05 -0700 Subject: [Mailman-Developers] [ mailman-Patches-534577 ] Add SpamAssassin filter to mail pipeline Message-ID: Patches item #534577, was opened at 2002-03-25 08:17 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 Category: list administration Group: Mailman 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: James Henstridge (jhenstridge) Assigned to: Nobody/Anonymous (nobody) Summary: Add SpamAssassin filter to mail pipeline Initial Comment: This filter adds support for discarding or holding spam sent to the mailing list. It contacts a spamd daemon (from SpamAssassin -- http://spamassassin.taint.org) to score the message. If the score is above a certain threshold (default 10), the message is discarded and an entry is written to the vette log. If the score is above another lower threshold (default 5), the message is held for moderation. The SpamAssassin.py file should be installed in Mailman/Handlers/. The LIST_PIPELINE variable in Mailman/Handlers/HandlerAPI.py should be modified to include a 'SpamAssassin' item (I put it just after the existing 'SpamDetect' item). To change the defaults, the following can be added to the mm_cfg.py file: SPAMASSASSIN_HOST = 'host:port' # how to contact SA SPAMASSASSIN_DISCARD_SCORE = 10 SPAMASSASSIN_HOLD_SCORE = 5 If you don't want to discard messages, then DISCARD_SCORE can be set to something very high (1000 should do it). It looks the MM2.1 filter APIs have changed a bit, so this filter will need some modifications to work with that version. When I get round to upgrading, I might look into updating it. ---------------------------------------------------------------------- Comment By: Sean Reifschneider (jafo) Date: 2002-06-12 21:48 Message: Logged In: YES user_id=81797 FYI: I've been running the 2002-05-14 version of this patch with spamassassin 2.20 for the last day on our main mailman box and it seems to be working great. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-05-14 06:04 Message: Logged In: YES user_id=146903 This version is essentially the same as the previous version, but adds compatibility with python > 1.5.2, which doesn't like you passing two arguments to socket.connect(). ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-04-27 06:17 Message: Logged In: YES user_id=146903 Just attached my updated version of the patch. This version requires SpamAssassin 2.20 (for the extra commands that the spamd daemon understands). It now displays a list of which rules were triggered for held messages, and can give messages from list members a bonus (defaults to 2), so that they are less likely to get held as spam. ---------------------------------------------------------------------- Comment By: James Henstridge (jhenstridge) Date: 2002-03-26 01:21 Message: Logged In: YES user_id=146903 There is a fairly easy optimisation for this filter that I missed when writing it. It calls str() on the message object twice. It would be quicker to call str() on the message once. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=534577&group_id=103 From cerdil@ttnet.net.tr Wed Jun 12 19:09:58 2002 From: cerdil@ttnet.net.tr (CAGAN ERDIL) Date: Wed, 12 Jun 2002 21:09:58 +0300 Subject: [Mailman-Developers] mailman installation request Message-ID: <002801c2123c$611f1580$6401a8c0@caan> Hello, This is a very well written software, but we fall short in = Python.Is there any mailman installation provided in this = community, or could anybody install it for a fee. Thank you. Shawn Erdil. www.e-zbanner.com From philb@philb.us Thu Jun 13 00:43:27 2002 From: philb@philb.us (Phil Barnett) Date: Wed, 12 Jun 2002 19:43:27 -0400 Subject: [Mailman-Developers] Searchable Archives In-Reply-To: <3D064A7D.BABB75E5@bcgsc.bc.ca> References: <3D064A7D.BABB75E5@bcgsc.bc.ca> Message-ID: <200206121943.27570.philb@philb.us> On Tuesday 11 June 2002 03:07 pm, Stephen Montgomery wrote: > I was wondering if mailman offers the opportunity for keyword > searchable archives. How do I go about implementing it? > With my list I'm envisioning getting tired of answering the same > questions and would like users to be able to search the archives easily. I use HT://Dig for that exact purpose. From jon@csh.rit.edu Thu Jun 13 06:12:13 2002 From: jon@csh.rit.edu (Jon Parise) Date: Thu, 13 Jun 2002 01:12:13 -0400 Subject: [Mailman-Developers] cron/disabled error Message-ID: <20020613051213.GA24318@csh.rit.edu> ---------------------- multipart/mixed attachment I've been getting the attached error for a couple of weeks (just now getting the time to investigate it). I started occuring after my last cvs upgrade to Mailman 2.1b2+. Any hints on where to start looking to resolve the problem? -- Jon Parise (jon@csh.rit.edu) . Information Technology (2001) http://www.csh.rit.edu/~jon/ : Computer Science House Member ---------------------- multipart/mixed attachment An embedded message was scrubbed... From: mailman@vlad.horde.org (Cron Daemon) Subject: Cron /usr/local/bin/python -S /usr/local/mailman/cron/disabled Date: Thu, 6 Jun 2002 09:00:04 -0700 (PDT) Size: 1016 Url: http://mail.python.org/pipermail-21/mailman-developers/attachments/d0da74b1/attachment.txt ---------------------- multipart/mixed attachment-- From noreply@sourceforge.net Thu Jun 13 11:21:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 13 Jun 2002 03:21:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-568456 ] base64 messages not decoded in archives Message-ID: Bugs item #568456, was opened at 2002-06-13 10:21 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568456&group_id=103 Category: Pipermail Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Geer (beroul) Assigned to: Nobody/Anonymous (nobody) Summary: base64 messages not decoded in archives Initial Comment: It appears that messages in base-64 encoding are not decoded in pipermail archives with Mailman 2.0.8. For example: http://lists.southspace.net/pipermail/esf-uk-coordinators/2002-June/000009.html In some cases I can tell people to switch to 8-bit or quoted-printable encoding, but some people are using web-based email services that don't give them any choice. The result is that their messages are shown as garbage in the archives. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=568456&group_id=103 From R.Barrett@ftel.co.uk Thu Jun 13 16:05:31 2002 From: R.Barrett@ftel.co.uk (Richard Barrett) Date: Thu, 13 Jun 2002 16:05:31 +0100 Subject: [Mailman-Developers] Searchable Archives In-Reply-To: <3D064A7D.BABB75E5@bcgsc.bc.ca> Message-ID: <5.1.0.14.2.20020613160350.0401ced8@pop.ftel.co.uk> At 12:07 11/06/2002 -0700, Stephen Montgomery wrote: >Hi, > I was wondering if mailman offers the opportunity for keyword >searchable archives. How do I go about implementing it? >With my list I'm envisioning getting tired of answering the same >questions and would like users to be able to search the archives easily. > >Cheers, >Stephen The following patches integrate the htdig (http://www.htdig.org/) search engine with Mailman. http://sourceforge.net/tracker/index.php?func=detail&aid=444879&group_id=103&atid=300103 http://sourceforge.net/tracker/index.php?func=detail&aid=444884&group_id=103&atid=300103 Also see http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.011.htp From bob@nleaudio.com Fri Jun 14 06:10:09 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Fri, 14 Jun 2002 01:10:09 -0400 Subject: [Mailman-Developers] Mail forwarding loops - discovered! References: <20020614043101.1799.81965.Mailman@mail.python.org> Message-ID: <3D097AB1.415EC0BB@nleaudio.com> Hello all, I have been recently seeing a bunch of "Mail forwarding Loop" messages in my Postfix mail log. After pouring over this stuff for several hours, I think I found the problem... Microsoft! Seriously, here's the scoop: a user sends a message to the list, which gets properly distributed. Sometime later (I've seen a few hours to a few days), the exact message that went out of the list mysteriously comes back to the list, with the same FROM: (usually the list's admin address), and the same TO: address (the list posting address). Postfix catches the loop, as it sees it's "Delivered-To" line in there, and bounces the message back to the sender, which sometimes is the real sender, other times is the list bounce address. The sender gets the bounce, and thinks their message didn't go out, when it really did. I've seen at least three different mail servers that have caused this: a roadrunner server, xt1.xtlab.com, and some other one in Australia. The common thread is that they are all running Microsoft mail server software. One of the messages had a header line that indicated it came from some webmail server, so it's possible that the webmail server software itself is somehow buggered up, and sends out these messages when the user does something. If it is user interaction, that would explain the random delay I saw (up to 2 days on one message). Here's a sample header, with some comments: >From DRSpoelhof@cs.com Thu Jun 13 22:09:44 2002 Return-Path: Delivered-To: cscmsgs@nlenet.net <--- my separate test mailbox to collect this message Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by list.nlenet.net (Postfix) with ESMTP id 65DA9128 for ; Thu, 13 Jun 2002 22:09:44 -0400 (EDT) Received: from mail pickup service by mail8.nc.rr.com with Microsoft SMTPSVC; Thu, 13 Jun 2002 21:58:19 -0400 <--- HERE'S THE REMAILED MESSAGE GOING OUT! Received: from ncmx01.mgw.rr.com ([24.93.67.251]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.757.75); <-- Here's where the original message got delivered Wed, 12 Jun 2002 08:01:15 -0400 <--- NOTICE THE DATE CHANGE! Received: from list.nlenet.net (list.nlenet.net [208.178.159.75]) by ncmx01.mgw.rr.com (8.12.2/8.12.2) with ESMTP id g5CC1FbC010819; Wed, 12 Jun 2002 08:01:15 -0400 (EDT) Received: from list.nlenet.net (localhost.localdomain [127.0.0.1]) by list.nlenet.net (Postfix) with ESMTP id 0368EFE; Wed, 12 Jun 2002 08:01:11 -0400 (EDT) Delivered-To: csc@nlenet.net Received: from imo-r07.mx.aol.com (imo-r07.mx.aol.com [152.163.225.103]) by list.nlenet.net (Postfix) with ESMTP id 60E2EF8 for ; Wed, 12 Jun 2002 08:00:56 -0400 (EDT) Received: from DRSpoelhof@cs.com by imo-r07.mx.aol.com (mail_out_v32.5.) id 7.cb.23799993 (657) for ; Wed, 12 Jun 2002 08:00:50 -0400 (EDT) From: DRSpoelhof@cs.com Message-ID: Subject: Re: [CSC] surge protection To: csc@lists.churchsoundcheck.com My solution (for now) was to insert procmail into the picture, scan the message for the "Delivered-To" the list address header, and if present, dump the message to the bit-bucket. Otherwise, the message gets passed on to Mailman. But the mail server software needs to be fixed! I'm sure others out there are going to see this same thing happening. I've seen it on a few different servers of my own, so I know it's not just one specific machine. Bob From chuqui@plaidworks.com Fri Jun 14 06:00:26 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Thu, 13 Jun 2002 22:00:26 -0700 Subject: [Mailman-Developers] Mail forwarding loops - discovered! In-Reply-To: <3D097AB1.415EC0BB@nleaudio.com> Message-ID: On 6/13/02 10:10 PM, "Bob Puff@NLE" wrote: > But the mail > server software needs to be fixed! Thanks, Bob. I needed the laugh. Yes, that server software is broken. When I run into them, I blackhole them so they can't annoy my servers any more. Soemtimes it gets their attention. Amazingly often, it doesn't seem to. -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ Stress is when you wake up screaming and you realize you haven't fallen asleep yet. From bob@nleaudio.com Fri Jun 14 06:19:07 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Fri, 14 Jun 2002 01:19:07 -0400 Subject: [Mailman-Developers] Mail forwarding loops - discovered! References: Message-ID: <3D097CCB.3A30C5F0@nleaudio.com> I'd do the same, if I could figure out --which- user it was! But there's a handful of roadrunner users, and I don't want to nuke them all... Plus, there is a server of which I have no users that match the domain name or mx host. I guess that's where having the TO: be set to each person's address would really help! Bob From chuqui@plaidworks.com Fri Jun 14 06:10:23 2002 From: chuqui@plaidworks.com (Chuq Von Rospach) Date: Thu, 13 Jun 2002 22:10:23 -0700 Subject: [Mailman-Developers] Mail forwarding loops - discovered! In-Reply-To: <3D097CCB.3A30C5F0@nleaudio.com> Message-ID: On 6/13/02 10:19 PM, "Bob Puff@NLE" wrote: > I'd do the same, if I could figure out --which- user it was! Watch your monthly password notices and see which ones come back from there. As I understand what's going on here, the SMTPSVC server is returning an error message to you. Or attempting to. Sort of. The way it does it is simply redirect the message back. There are a couple of other servers that do other similarly bad things. I've been working with one server vendor for a while to fix some bugs in their bounce returns. I'm just waiting for them to release the fixed version of their server before I can say anything (and then I'll go whack on the other, since I only realize there were two vendors doing this, and it's only certain buggy releases of their server) -- Chuq Von Rospach, Architech chuqui@plaidworks.com -- http://www.chuqui.com/ The Cliff's Notes Cliff's Notes on Hamlet: And they all died happily ever after From dmick@utopia.West.Sun.COM Tue Jun 18 17:15:23 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Tue, 18 Jun 2002 09:15:23 -0700 Subject: [Mailman-Developers] Bug in CVS Message-ID: <3D0F5C9B.2050807@utopia.west.sun.com> Bouncer.py refers to BYUNKNOWN instead of UNKNOWN. Here's the fix: Index: Bouncer.py =================================================================== RCS file: /cvsroot/mailman/mailman/Mailman/Bouncer.py,v retrieving revision 2.30 diff -u -r2.30 Bouncer.py --- Bouncer.py 28 May 2002 03:02:23 -0000 2.30 +++ Bouncer.py 18 Jun 2002 16:14:38 -0000 @@ -216,7 +216,7 @@ {MemberAdaptor.BYBOUNCE: 'BYBOUNCE', MemberAdaptor.BYUSER: 'BYUSER', MemberAdaptor.BYADMIN: 'BYADMIN', - MemberAdaptor.BYUNKNOWN: 'BYUNKNOWN'}.get( + MemberAdaptor.UNKNOWN: 'UNKNOWN'}.get( reason, 'invalid value')) return # Send the next notification From noreply@sourceforge.net Wed Jun 19 08:28:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 19 Jun 2002 00:28:33 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-571004 ] member_posting_only does not work Message-ID: Bugs item #571004, was opened at 2002-06-19 07:28 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571004&group_id=103 Category: security/privacy Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Josef Grosch (jgrosch) Assigned to: Nobody/Anonymous (nobody) Summary: member_posting_only does not work Initial Comment: Version 2.0.11 on FreeBSD 4.6 Mailman allows people who are not on the list are allowed to post. member_posting_only is set yes but non members are still posting. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571004&group_id=103 From wheakory@isu.edu Wed Jun 19 16:45:49 2002 From: wheakory@isu.edu (Kory Wheatley) Date: Wed, 19 Jun 2002 09:45:49 -0600 Subject: [Mailman-Developers] Finding restrcit post to members options Message-ID: <3D10A72D.2080700@isu.edu> In Mailman is there a command line utility I can use to find out all the mailing lists that have the "Restrict post to members only" set as yes or 1? I've current installed Mailman 2.0.11 on Red Hat Linux 7.2 . -- ######################################### Kory Wheatley Academic Computing Analyst Sr. Phone 282-3874 ######################################### Everything must point to him. From noreply@sourceforge.net Wed Jun 19 17:55:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 19 Jun 2002 09:55:18 -0700 Subject: [Mailman-Developers] [ mailman-Patches-510415 ] Improve MIME header handling Message-ID: Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 From noreply@sourceforge.net Wed Jun 19 19:17:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 19 Jun 2002 11:17:01 -0700 Subject: [Mailman-Developers] [ mailman-Patches-510415 ] Improve MIME header handling Message-ID: Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- >Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 20:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 From noreply@sourceforge.net Wed Jun 19 23:21:18 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 19 Jun 2002 15:21:18 -0700 Subject: [Mailman-Developers] [ mailman-Patches-510415 ] Improve MIME header handling Message-ID: Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-20 00:21 Message: Logged In: YES user_id=105527 Ok, I could have had a look at the patch header more closely, sorry. Thanks for your answer though, I wasn't aware of 2.14 being existent at all, since 2.0.9 seems to be the latest version being officially avilable... Anyway, my problem with german Umlauts being screwed up was solved by running arch manually, somehow the Umlauts seems to be only messed up when the archiver is run automatically... And rather than backporting (especially now, since my special problem was solved so easily ;) I would love to see a newer version of mailman being released officially... Thanks again for you answer! ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 20:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 From noreply@sourceforge.net Thu Jun 20 14:08:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 20 Jun 2002 06:08:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-571634 ] Date: header field handling Message-ID: Bugs item #571634, was opened at 2002-06-20 15:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571634&group_id=103 Category: mail delivery Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Date: header field handling Initial Comment: I got this traceback in my error log (using latest CVS, 2.1b2+): Jun 20 14:58:21 2002 (1991) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/ArchRunner.py", line 54, in _dispose elif abs(now - mktime_tz(tup)) > \ File "/usr/src/build/87651-i386/install/usr/lib/python2.2/rfc822.py", line 955, in mktime_tz t = time.mktime(data[:8] + (0,)) ValueError: year out of range The offending mail was moved to the qfiles/shunt/ directory. A quick dump_db on the .pck file showed this Date: field in the header: Date: Tue, 18 Jun 0102 05:12:09 +0500 The offending mail was a spam mail, so I've deleted the .db and .pck file. But reporting it anyway. :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571634&group_id=103 From noreply@sourceforge.net Thu Jun 20 14:19:21 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 20 Jun 2002 06:19:21 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-571636 ] Traceback in error log - bounce handling Message-ID: Bugs item #571636, was opened at 2002-06-20 15:19 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571636&group_id=103 Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback in error log - bounce handling Initial Comment: I got this traceback in my error log: Jun 20 14:58:56 2002 (1992) Traceback (most recent call last): File "/home/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/BounceRunner.py", line 71, in _dispose addrs = BouncerAPI.ScanMessages(mlist, msg) File "/home/mailman/Mailman/Bouncers/BouncerAPI.py", line 60, in ScanMessages addrs = sys.modules[modname].process(msg) File "/home/mailman/Mailman/Bouncers/Microsoft.py", line 35, in process body = StringIO(subpart.get_payload()) TypeError: expected read buffer, list found The following had probably happened: 1. A spam mail was sent to one of our lists. 2. The list tried to send a "waiting for moderator approval" mail to the sender of the spam mail. 3. The "waiting for moderator approval" mail bounced (because the sender address was, of course, invalid). The bounce in (3) gave me the traceback and was moved to qfiles/shunt/. PCK file is attached to this bug report. Let me know if you need the DB file too... :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=571636&group_id=103 From Javier@cips.nokia.COM Thu Jun 20 18:12:53 2002 From: Javier@cips.nokia.COM (Javier Henderson) Date: Thu, 20 Jun 2002 10:12:53 -0700 Subject: [Mailman-Developers] Tuple of the wrong size Message-ID: <20020620171253.GG35829@argentum.cips.nokia.com> I moved a list from a 2.0beta6 installation to 2.1a4, it all looks good except the admindb page, it produces the following: Bug in Mailman version 2.1a4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/export/homec/mailman/scripts/driver", line 86, in run_main main() File "../Mailman/Cgi/admindb.py", line 214, in main show_pending_subs(mlist, form) File "../Mailman/Cgi/admindb.py", line 262, in show_pending_subs time, addr, fullname, passwd, digest, lang = mlist.GetRecord(id) ValueError: unpack tuple of wrong size Any ideas? -jav From spertus@mills.edu Thu Jun 20 22:23:10 2002 From: spertus@mills.edu (spertus@mills.edu) Date: Thu, 20 Jun 2002 14:23:10 -0700 (PDT) Subject: [Mailman-Developers] Mailman 2.1b2 and qmail Message-ID: <1024608190.3d1247be52d6a@webmail.mills.edu> Has anyone gotten Mailman 2.1b2 to work with qmail via contrib/qmail-to-mailman.py? There seems to be a problem. qmail-to-mailman.py includes: if os.path.exists(local): os.execv(MailmanHome + "/mail/mailman", (MailmanHome + "/mail/mailman", type, local)) In my configuration, this is an attempt to exec /usr/local/mailman/mail/mailman, which doesn't exist. Perhaps it should be: if os.path.exists(local): os.execv(MailmanHome + "/scripts/mailman", (MailmanHome + "/scripts/mailman", type, local)) ^^^^^^^^^^ I made this change and no longer get a FileNotFound error but still haven't gotten the system to work. Ellen From spertus@mills.edu Fri Jun 21 04:19:46 2002 From: spertus@mills.edu (Ellen Spertus) Date: Thu, 20 Jun 2002 20:19:46 -0700 Subject: [Mailman-Developers] Mailman 2.1b2 and qmail In-Reply-To: <1024608190.3d1247be52d6a@webmail.mills.edu> Message-ID: <5.1.0.14.0.20020620201721.03e3ac60@ella.mills.edu> At 02:23 PM 6/20/2002 -0700, spertus@mills.edu wrote: >There seems to be a problem. qmail-to-mailman.py >includes: > > if os.path.exists(local): > os.execv(MailmanHome + "/mail/mailman", > (MailmanHome + "/mail/mailman", type, local)) > >In my configuration, this is an attempt to exec >/usr/local/mailman/mail/mailman, >which doesn't exist. Perhaps it should be: > > if os.path.exists(local): > os.execv(MailmanHome + "/scripts/mailman", > (MailmanHome + "/scripts/mailman", type, local)) > ^^^^^^^^^^ That was a silly hypothesis. /usr/local/mailman/scripts/mailman is the script that turns mailman on or off. qmail-to-mailman.py was correct. The problem was that mail/mailman never got created from mailman-2.1b2/src/mail-wrapper.c, which I'll now try to understand. >Has anyone gotten Mailman 2.1b2 to work with qmail via >contrib/qmail-to-mailman.py? My original question still stands. Ellen From spertus@mills.edu Fri Jun 21 04:42:54 2002 From: spertus@mills.edu (Ellen Spertus) Date: Thu, 20 Jun 2002 20:42:54 -0700 Subject: [Mailman-Developers] Mailman 2.1b2 and qmail In-Reply-To: <5.1.0.14.0.20020620201721.03e3ac60@ella.mills.edu> References: <1024608190.3d1247be52d6a@webmail.mills.edu> Message-ID: <5.1.0.14.0.20020620203424.03e3ac60@ella.mills.edu> At 08:19 PM 6/20/2002 -0700, Ellen Spertus wrote: > The problem was that mail/mailman never got created from mailman-2.1b2/src/mail-wrapper.c, which I'll now try to understand. The problem was that /usr/local/src/mailman-2.1b2/src/Makefile was placing the mailman executable (created from mail-wrapper.c) into /usr/local/bin/mail/ instead of into /usr/local/mailman/mail/. The relevant lines from the Makefile are: prefix= /usr/local/mailman exec_prefix= /usr/local/bin MAIL_PROGS= mailman MAILDIR= $(exec_prefix)/mail for f in $(MAIL_PROGS); \ do \ $(INSTALL_PROGRAM) $$f $(MAILDIR); \ chmod g+s $(MAILDIR)/$$f; \ done Because I did not set exec_prefix in configure, it defaulted to /usr/local/bin. I'll need someone wiser than me to tell me whether this was a bug or a feature and how to permanently fix the problem. (For now, I'll just copy the file from the directory in which it is placed to the directory in which it was sought.) Soliloquizing, Ellen From noreply@sourceforge.net Fri Jun 21 22:34:33 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 21 Jun 2002 14:34:33 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-572312 ] bin/update fails on bogus import Message-ID: Bugs item #572312, was opened at 2002-06-21 14:34 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=572312&group_id=103 Category: configuring/installing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Larry A. Price (swirly) Assigned to: Nobody/Anonymous (nobody) Summary: bin/update fails on bogus import Initial Comment: Traceback (most recent call last): File "bin/update", line 47, in ? from Mailman import MailList File "/var/lib/mailman/Mailman/MailList.py", line 40, in ? from email.Utils import getaddresses, formataddr, parseaddr ImportError: cannot import name formataddr make: *** [update] Error 1 there is no function formataddr in /usr/lib/python2.2/email/Utils.py formataddr is called only within the code to generate the admin_notif for new subscriptions. My solution was 40c40 < from email.Utils import getaddresses, formataddr, parseaddr --- > from email.Utils import getaddresses, parseaddr 865c865 < "member" : formataddr((name, email)), --- > "member" : "%s <%s>" % (name, email), ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=572312&group_id=103 From laprice@efn.org Fri Jun 21 23:18:02 2002 From: laprice@efn.org (Larry Price) Date: Fri, 21 Jun 2002 15:18:02 -0700 (PDT) Subject: [Mailman-Developers] make install import failures Message-ID: after the second failed to import error which failed with this error File "/var/lib/mailman/Mailman/Message.py", line 26, in ? from email.Charset import Charset ImportError: No module named Charset I figured it would be best to make sure that I had the correct library and versions. I'm using python2.2.1 on debian woody and am wondering if I'm experiencing version whip or what. http://www.efn.org/~laprice ( Community, Cooperation, Consensus http://www.opn.org ( Openness to serendipity, make mistakes http://www.efn.org/~laprice/poems ( but learn from them.(carpe fructus ludi) From robla@robla.net Fri Jun 21 05:47:29 2002 From: robla@robla.net (Rob Lanphier) Date: Thu, 20 Jun 2002 21:47:29 -0700 (PDT) Subject: [Mailman-Developers] New dev considering adding RSS support Message-ID: Hi all, I'm a longtime mailman user, but new to mailman development. A while back, I submitted a feature request for RSS: https://sourceforge.net/tracker/index.php?func=detail&aid=534234&group_id=103&atid=350103 In response, I received the question: "care to submit a patch?" I'm in a good place to work on something like this now. However, I thought I'd send this mail out there first, in case there's any advice/recommendations for how to do this. In particular, I've been skimming the code in Mailman/Archiver, and I notice there's a TODO note regarding the template strings needing to be broken out. Since I'll probably be doing something similar, I'll need to either add to the mess, or help allievate it. Is the template breakout something I should do while I'm in there, or should I let someone who's more familiar handle that? Thoughts? Rob From dmick@utopia.West.Sun.COM Sat Jun 22 21:33:02 2002 From: dmick@utopia.West.Sun.COM (Dan Mick) Date: Sat, 22 Jun 2002 13:33:02 -0700 Subject: [Mailman-Developers] make install import failures References: Message-ID: <3D14DEFE.15DEC48B@utopia.west.sun.com> The version of email you need to use is contained in the mailman tree. paths.py contains the gunge to get pythonlib on your searchpath for all the installed mailman binaries. Larry Price wrote: > > after the second failed to import error > which failed with this error > File "/var/lib/mailman/Mailman/Message.py", line 26, in ? > from email.Charset import Charset > ImportError: No module named Charset > > I figured it would be best to make sure that I had the correct library > and versions. > > I'm using python2.2.1 on debian woody > > and am wondering if I'm experiencing version whip or what. > http://www.efn.org/~laprice ( Community, Cooperation, Consensus > http://www.opn.org ( Openness to serendipity, make mistakes > http://www.efn.org/~laprice/poems ( but learn from them.(carpe fructus ludi) > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman-21/listinfo/mailman-developers From noreply@sourceforge.net Sun Jun 23 19:02:47 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Sun, 23 Jun 2002 11:02:47 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-572822 ] real_name attribute not changed Message-ID: Bugs item #572822, was opened at 2002-06-23 14:02 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Christine Charity (ccharity) Assigned to: Nobody/Anonymous (nobody) Summary: real_name attribute not changed Initial Comment: When trying to change the name of a mailing list from MAILINGLISTNAME to mailinglistname (lowercase) the following error is returned: real_name attribute not changed! It must differ from the list's name by case only. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=572822&group_id=103 From jcrey@uma.es Mon Jun 24 12:13:51 2002 From: jcrey@uma.es (Juan Carlos Rey Anaya) Date: Mon, 24 Jun 2002 13:13:51 +0200 Subject: [Mailman-Developers] Re: Tuple of the wrong size References: Message-ID: <3D16FEEF.2277BC48@uma.es> > Javier Henderson wrote: > Traceback (most recent call last): > File "/export/homec/mailman/scripts/driver", line 86, in run_main > main() > File "../Mailman/Cgi/admindb.py", line 214, in main > show_pending_subs(mlist, form) > File "../Mailman/Cgi/admindb.py", line 262, in show_pending_subs > time, addr, fullname, passwd, digest, lang =3D mlist.GetRecord(id) > ValueError: unpack tuple of wrong size > = > Any ideas? You somehow have old style requests in some of your lists. The only way to jump over this is patching you code. (I have had to do it too :-( ) Enclose 'time, addr, fullname, passwd, digest, lang =3D mlist.GetRecord(id)' inside try - except statements like this. try: time, addr, fullname, passwd, digest, lang =3D mlist.GetRecord(id) except ValueError: time, addr, passwd, digest =3D mlist.GetRecord(id) fullname =3D "" lang =3D mlist.preferred_language So it doesn't crash. Do it when this bug arise :-( Cheers. -- = ___ / F \ [[[]]]] ( O O ) #----------------0000--(_)--0000---------------# | Juan Carlos Rey Anaya (jcrey@uma.es) | | Servicio Central de inform=E1tica | | Universidad de M=E1laga - Espa=F1a | #----------------------------------------------# From noreply@sourceforge.net Mon Jun 24 12:23:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 04:23:55 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-573071 ] nonmembers can post after upgrading Message-ID: Bugs item #573071, was opened at 2002-06-24 13:23 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=573071&group_id=103 Category: security/privacy Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: nonmembers can post after upgrading Initial Comment: After upgrading to current CVS (2.1b2+), nonmembers are now allowed to post to a list that used to be members-only (in MM 2.0.11). The member_posting_only config variable is not propagated to the generic_nonmember_action variable when upgrading. This caused me a lot of trouble... :) The fix is probably trivial, but my lack of python experience prevents me from submitting a patch... ;) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=573071&group_id=103 From dom@earth.li Mon Jun 24 12:42:58 2002 From: dom@earth.li (Dominic Hargreaves) Date: Mon, 24 Jun 2002 12:42:58 +0100 Subject: [Mailman-Developers] Re: [Mailman-Users] Python problems, mm 2.1b2, rh71 Message-ID: <20020624124258.D1414@tirian.magd.ox.ac.uk> [posted to mailman-developers separately because I'm subscribed with a different address] On Mon, Jun 24, 2002 at 01:55:57AM +0100, Dominic Hargreaves wrote: > Hi, > > I'm having some problems upgrading from mailman 2.0.11 to 2.1b2. > > The setup is redhat 7.1 with the python2 package (python2-2.0-3) installed > from powertools. Someone has pointed out to me by private mail that I need python 2.1 [0] to run mailman 2.1, so it was a mistake on my part not to have read the requirements carefully enough. However, it's worth pointing out that the configure script complained when I tried to run it with python 1.5.2, but not when I ran it with 2.0. Should this be fixed? Cheers, Dom. [0] I said 2.2 in the mail to mailman-users. Need more coffee. From noreply@sourceforge.net Tue Jun 25 00:47:42 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 16:47:42 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-573394 ] separate auto-disable and "nomail" flags Message-ID: Feature Requests item #573394, was opened at 2002-06-24 16:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Stein (gstein) Assigned to: Nobody/Anonymous (nobody) Summary: separate auto-disable and "nomail" flags Initial Comment: Currently, Mailman will disable email to accounts (say, because they bounced too many times) by setting the "nomail" option. *However*, that option is also used by users. As a result, I have no way to determine which subscriptions are old/invalid, and which correspond to actual users. It would be nice to record disabling as a separate field... say, as the date the account was disabled. Then, I could periodically find all accounts which were disabled more than a year ago and simply delete them. Thus, users who temporarily disable mail delivery will not accidentally have their subscriptions purged :-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 From noreply@sourceforge.net Tue Jun 25 00:52:25 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 16:52:25 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-573394 ] separate auto-disable and "nomail" flags Message-ID: Feature Requests item #573394, was opened at 2002-06-24 23:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Stein (gstein) Assigned to: Nobody/Anonymous (nobody) Summary: separate auto-disable and "nomail" flags Initial Comment: Currently, Mailman will disable email to accounts (say, because they bounced too many times) by setting the "nomail" option. *However*, that option is also used by users. As a result, I have no way to determine which subscriptions are old/invalid, and which correspond to actual users. It would be nice to record disabling as a separate field... say, as the date the account was disabled. Then, I could periodically find all accounts which were disabled more than a year ago and simply delete them. Thus, users who temporarily disable mail delivery will not accidentally have their subscriptions purged :-) ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-06-24 23:52 Message: Logged In: YES user_id=10725 MM 2.1 adds a "reason" enumeration to the disabled flag, so at least the 'bounce' vs. 'user' or 'administrator' distinction is obvious. The date of the event is also available in the log files. Not that that's as useful as what you suggest, but it's partway there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 From noreply@sourceforge.net Tue Jun 25 02:50:53 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 18:50:53 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-573394 ] separate auto-disable and "nomail" flags Message-ID: Feature Requests item #573394, was opened at 2002-06-24 16:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Stein (gstein) Assigned to: Nobody/Anonymous (nobody) >Summary: separate auto-disable and "nomail" flags Initial Comment: Currently, Mailman will disable email to accounts (say, because they bounced too many times) by setting the "nomail" option. *However*, that option is also used by users. As a result, I have no way to determine which subscriptions are old/invalid, and which correspond to actual users. It would be nice to record disabling as a separate field... say, as the date the account was disabled. Then, I could periodically find all accounts which were disabled more than a year ago and simply delete them. Thus, users who temporarily disable mail delivery will not accidentally have their subscriptions purged :-) ---------------------------------------------------------------------- >Comment By: Greg Stein (gstein) Date: 2002-06-24 18:50 Message: Logged In: YES user_id=6501 Yes, that is a definite improvement. Note that logs get rotated, so you might not know "when" a particular transition occurred. For my particular problem, I'd be happy with the current 2.1 behavior, and would be even happier with the change date added, too. thx! ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-06-24 16:52 Message: Logged In: YES user_id=10725 MM 2.1 adds a "reason" enumeration to the disabled flag, so at least the 'bounce' vs. 'user' or 'administrator' distinction is obvious. The date of the event is also available in the log files. Not that that's as useful as what you suggest, but it's partway there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 From bob@nleaudio.com Tue Jun 25 06:37:49 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Tue, 25 Jun 2002 01:37:49 -0400 Subject: [Mailman-Developers] Bug in the latest 2.1 CVS Message-ID: <3D1801AD.A56A522D@nleaudio.com> Here's something I just got when installing a brand new 2.1b fresh from CVS tonight: Jun 25 01:17:51 2002 (21415) Uncaught runner exception: isinstance() arg 2 must be a class or type Jun 25 01:17:51 2002 (21415) Traceback (most recent call last): File "/home/mm21/mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/home/mm21/mailman/Mailman/Queue/Runner.py", line 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mm21/mailman/Mailman/Queue/IncomingRunner.py", line 129, in _dispo se status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/home/mm21/mailman/Mailman/Queue/IncomingRunner.py", line 152, in _dopip eline sys.modules[modname].process(mlist, msg, msgdata) File "/home/mm21/mailman/Mailman/Handlers/Hold.py", line 141, in process if mlist.administrivia and Utils.is_administrivia(msg): File "/home/mm21/mailman/Mailman/Utils.py", line 492, in is_administrivia for line in email.Iterators.body_line_iterator(msg): File "/home/mm21/mailman/pythonlib/email/_compat22.py", line 41, in body_line_ iterator if isinstance(payload, StringTypes): TypeError: isinstance() arg 2 must be a class or type This happened when I sent the first message to the first list. BOb From noreply@sourceforge.net Tue Jun 25 06:54:49 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 22:54:49 -0700 Subject: [Mailman-Developers] [ mailman-Patches-573503 ] message-id munge error in ToUsenet.py Message-ID: Patches item #573503, was opened at 2002-06-25 06:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573503&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: message-id munge error in ToUsenet.py Initial Comment: # Our Message-ID format is msgid = msg.get('message-id') hackmsgid = 1 if msgid: mo = re.search( msgid, r'[^@]+)@(?P[^>]+)>') in the re.search, the parameters are the wrong way around. The consequence is that a new message-id is assigned to each message and threading is easily broken. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573503&group_id=103 From noreply@sourceforge.net Tue Jun 25 06:59:15 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 22:59:15 -0700 Subject: [Mailman-Developers] [ mailman-Patches-573505 ] usenet threading improvements Message-ID: Patches item #573505, was opened at 2002-06-25 06:59 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: usenet threading improvements Initial Comment: Basically message-id munging for all messages. Might be better as an option? This helps with threading in usenet gating, as what happens is this: someone sends a mail with message- id foo@bar.com gating replaces the message-id with mailman.123.456.list@list.com list member replies via mail, "in-reply-to" header is set to the foo@bar.com now when the message is gated it can't thread because in-reply-to: (which is translated into references:) is wrong. Solution is to munge all message-ids. Doesn't really do any harm AFAICT. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573505&group_id=103 From noreply@sourceforge.net Tue Jun 25 07:03:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 23:03:13 -0700 Subject: [Mailman-Developers] [ mailman-Patches-573508 ] ToUsenet: subject prefix stripping Message-ID: Patches item #573508, was opened at 2002-06-25 07:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573508&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: ToUsenet: subject prefix stripping Initial Comment: For some inexplicable reason ToUsenet is trying to -add- the subject prefix. Now this doesn't work generally anyway (consider a plain post - this won't do it). Typically, the subject prefix is the list- name, which just replicates information we already have (as we already know which newsgroup we are looking at). Anyway, arguments aside, I've fixed up ToUsenet.py to go the other way and remove subjects. (I would have made this an option, but my Python is non-existent). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573508&group_id=103 From noreply@sourceforge.net Tue Jun 25 07:16:28 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Mon, 24 Jun 2002 23:16:28 -0700 Subject: [Mailman-Developers] [ mailman-Patches-573509 ] ToUsenet: subject prefix stripping Message-ID: Patches item #573509, was opened at 2002-06-25 07:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573509&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: ToUsenet: subject prefix stripping Initial Comment: For some inexplicable reason ToUsenet is trying to -add- the subject prefix. Now this doesn't work generally anyway (consider a plain post - this won't do it). Typically, the subject prefix is the list- name, which just replicates information we already have (as we already know which newsgroup we are looking at). Anyway, arguments aside, I've fixed up ToUsenet.py to go the other way and remove subjects. (I would have made this an option, but my Python is non-existent). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573509&group_id=103 From noreply@sourceforge.net Tue Jun 25 11:32:13 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Tue, 25 Jun 2002 03:32:13 -0700 Subject: [Mailman-Developers] [ mailman-Feature Requests-573394 ] separate auto-disable and "nomail" flags Message-ID: Feature Requests item #573394, was opened at 2002-06-25 01:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Stein (gstein) Assigned to: Nobody/Anonymous (nobody) Summary: separate auto-disable and "nomail" flags Initial Comment: Currently, Mailman will disable email to accounts (say, because they bounced too many times) by setting the "nomail" option. *However*, that option is also used by users. As a result, I have no way to determine which subscriptions are old/invalid, and which correspond to actual users. It would be nice to record disabling as a separate field... say, as the date the account was disabled. Then, I could periodically find all accounts which were disabled more than a year ago and simply delete them. Thus, users who temporarily disable mail delivery will not accidentally have their subscriptions purged :-) ---------------------------------------------------------------------- Comment By: Jesús Cea Avión (jcea) Date: 2002-06-25 12:32 Message: Logged In: YES user_id=97460 Good. You've read my mind :-). This feature is a "must have" :-). ---------------------------------------------------------------------- Comment By: Greg Stein (gstein) Date: 2002-06-25 03:50 Message: Logged In: YES user_id=6501 Yes, that is a definite improvement. Note that logs get rotated, so you might not know "when" a particular transition occurred. For my particular problem, I'd be happy with the current 2.1 behavior, and would be even happier with the change date added, too. thx! ---------------------------------------------------------------------- Comment By: Dan Mick (dmick) Date: 2002-06-25 01:52 Message: Logged In: YES user_id=10725 MM 2.1 adds a "reason" enumeration to the disabled flag, so at least the 'bounce' vs. 'user' or 'administrator' distinction is obvious. The date of the event is also available in the log files. Not that that's as useful as what you suggest, but it's partway there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=573394&group_id=103 From tollef@add.no Wed Jun 26 13:45:44 2002 From: tollef@add.no (Tollef Fog Heen) Date: 26 Jun 2002 14:45:44 +0200 Subject: [Mailman-Developers] Error in Deliverer.py, b2 Message-ID: <87adpijjif.fsf@arabella.raw.no> line 110 in Deliverer.py should read: 'password' : self.getMemberPassword(user), and not access the password hash directly. This is needed in order to use other MemberAdaptors. -- Tollef Fog Heen ,''`. UNIX is user friendly, it's just picky about who its friends are : :' : `. `' `- From bob@nleaudio.com Wed Jun 26 17:03:40 2002 From: bob@nleaudio.com (Bob Puff@NLE) Date: Wed, 26 Jun 2002 12:03:40 -0400 Subject: [Mailman-Developers] Fix for the last error I reported Message-ID: <3D19E5DC.EDB78361@nleaudio.com> Hey Gang, I finally found a fix for the last show-stopper I reported: > File "/home/mm21/mailman/pythonlib/email/_compat22.py", line 41, in body_line_iterator > if isinstance(payload, StringTypes): > TypeError: isinstance() arg 2 must be a class or type It seems that while: > admin(22824): [----- Python Information -----] > admin(22824): sys.version = 2.2b1 (#2, Oct 29 2001, 16:07:36) > [GCC 2.95.3 19991030 (prerelease)] I copied _compat21.py over top _compat22.py, and it now works. So, it seems that _compat22.py isn't really compatible with the 2.2 beta 1 release of Python. Bob From noreply@sourceforge.net Wed Jun 26 20:58:22 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Wed, 26 Jun 2002 12:58:22 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-574240 ] web ui confirm button placement Message-ID: Bugs item #574240, was opened at 2002-06-26 14:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=574240&group_id=103 Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Christopher Kolar (ckolar) Assigned to: Nobody/Anonymous (nobody) Summary: web ui confirm button placement Initial Comment: Hi. Running 2.1b2 I just did a test subscription via email. When I clicked on the link to confirm the confirmation page came up properly. I am a bit bugged by the UI though. The Confirm button was way off to the left -- right under all of the user informaiton on the screen was the "dismiss and discard" button (or whatever it was labeled). After checking the info on the screen I very nearly hit the button because I could not see the real confirm burron and the discard button, being placed right under the info, seemed to instinctively be a good place for a confirm button. I would change the UI to at least get both of them in the center. Cheers, --chris ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=574240&group_id=103 From fil@rezo.net Thu Jun 27 09:49:10 2002 From: fil@rezo.net (Fil) Date: Thu, 27 Jun 2002 10:49:10 +0200 Subject: [Mailman-Developers] problems with iso... encoding Message-ID: <20020627084910.GB18806@rezo.net> Hi Mailman-devs, I don"t understand why, since I upgraded Mailman to the current cvs 2.1b2+ (from a former 2.1b1) the accents encoding are all dead ; it seems that a creepy ^M (higlighted below) puts it wrong. It might be because I had diffidulty installing the email package (_compat22.py would yield a complaint : I had to do a 'cp _compat21.py _compat22.py to install)... I have Python 2.1.2 ----- Forwarded message from Fil ----- Subject: [Test] =?iso-8859-1?Q?probl=E8mes_d'accents_je_te?=^M =?iso-8859-1?B?c3RlIDog4CDpIOcg6A==?= ? ----- End forwarded message ----- Help will be appreciated. From noreply@sourceforge.net Fri Jun 28 05:01:55 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 27 Jun 2002 21:01:55 -0700 Subject: [Mailman-Developers] [ mailman-Patches-510415 ] Improve MIME header handling Message-ID: Patches item #510415, was opened at 2002-01-29 18:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 Category: Pipermail >Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-06-28 00:01 Message: Logged In: YES user_id=12800 k-fish, Martin was actually referring to the revision of one of the files in the Mailman 2.1 distribution. MM2.1 is in beta testing now and will officially support internationalization. The MM2.0.x does not. I'm closing this patch since as Martin says, it's already applied! ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:21 Message: Logged In: YES user_id=105527 Ok, I could have had a look at the patch header more closely, sorry. Thanks for your answer though, I wasn't aware of 2.14 being existent at all, since 2.0.9 seems to be the latest version being officially avilable... Anyway, my problem with german Umlauts being screwed up was solved by running arch manually, somehow the Umlauts seems to be only messed up when the archiver is run automatically... And rather than backporting (especially now, since my special problem was solved so easily ;) I would love to see a newer version of mailman being released officially... Thanks again for you answer! ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 14:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 12:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 00:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 From noreply@sourceforge.net Fri Jun 28 05:04:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 27 Jun 2002 21:04:02 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566150 ] real names Message-ID: Bugs item #566150, was opened at 2002-06-08 07:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 Category: None Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: real names Initial Comment: I'd like it if people could enter their real (first, last) name in their subscription. It is nicer to receive mails with ones real name. Thanks, Bernhard ---------------------------------------------------------------------- Comment By: Kyle Rhorer (rhorer) Date: 2002-06-27 23:04 Message: Logged In: YES user_id=569903 It is not just nice, it's downright useful. The listadmins of large lists sometimes need to know if a particular person is subscribed, but may only know the person's name. If John Smith is subscribed as bizzyboy938@yahoo.com (a ficticious address for the purpose of illustration), the admin won't be able to determine whether Mr. Smith is subscribed or not. It would also be nice if the admin could sort on either real name or email address, but I certainly wouldn't want to see addition of the real name feature held up waiting for the sort capability. Thanks, Kyle ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 From noreply@sourceforge.net Fri Jun 28 05:25:01 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 27 Jun 2002 21:25:01 -0700 Subject: [Mailman-Developers] [ mailman-Bugs-566150 ] real names Message-ID: Bugs item #566150, was opened at 2002-06-08 08:29 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 Category: None Group: 2.0.x >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Bernhard Kuemel (darsie) Assigned to: Nobody/Anonymous (nobody) Summary: real names Initial Comment: I'd like it if people could enter their real (first, last) name in their subscription. It is nicer to receive mails with ones real name. Thanks, Bernhard ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-06-28 00:25 Message: Logged In: YES user_id=12800 Closing this as it's already supported in Mailman 2.1 (currently in beta testing). It won't be supported in the MM2.0.x series. ---------------------------------------------------------------------- Comment By: Kyle Rhorer (rhorer) Date: 2002-06-28 00:04 Message: Logged In: YES user_id=569903 It is not just nice, it's downright useful. The listadmins of large lists sometimes need to know if a particular person is subscribed, but may only know the person's name. If John Smith is subscribed as bizzyboy938@yahoo.com (a ficticious address for the purpose of illustration), the admin won't be able to determine whether Mr. Smith is subscribed or not. It would also be nice if the admin could sort on either real name or email address, but I certainly wouldn't want to see addition of the real name feature held up waiting for the sort capability. Thanks, Kyle ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=566150&group_id=103 From noreply@sourceforge.net Fri Jun 28 07:51:02 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Thu, 27 Jun 2002 23:51:02 -0700 Subject: [Mailman-Developers] [ mailman-Patches-574976 ] Reply-To option, Author Name & Archives Message-ID: Patches item #574976, was opened at 2002-06-28 01:51 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 Category: Pipermail Group: None Status: Open Resolution: None Priority: 5 Submitted By: Susan Dridi (sdridi) Assigned to: Nobody/Anonymous (nobody) Summary: Reply-To option, Author Name & Archives Initial Comment: If the option to Reply-To the list is set, and if the "From:" field in the list.mbox file is in the format of "Poster Name" or else Poster Name then Poster Name is displayed as the Author. If the "From:" field is in the format of someone@example.com (AOL does this) then the Author is the list e-mail address. The e-mail address in the archived post is always the list e-mail address. So, it's often difficult to tell who actually posted something. Here is the patch, which just rearranges lines that were already in the code: *** pipermail.py.dist Fri Jun 1 15:30:16 2001 --- pipermail.py Mon Jun 24 12:22:46 2002 *************** *** 176,189 **** # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') ! e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) - - if self.author == "": - self.author = self.email # Save the In-Reply-To:, References:, and Message-ID: lines # --- 176,188 ---- # Figure out the e-mail address and poster's name self.author, self.email = message.getaddr('From') ! if self.author == "": ! self.author = self.email ! e = message.getheader('Reply-To') if e is not None: self.email = e self.email = strip_separators(self.email) self.author = strip_separators(self.author) # Save the In-Reply-To:, References:, and Message-ID: lines # ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=574976&group_id=103 From noreply@sourceforge.net Fri Jun 28 14:26:41 2002 From: noreply@sourceforge.net (noreply@sourceforge.net) Date: Fri, 28 Jun 2002 06:26:41 -0700 Subject: [Mailman-Developers] [ mailman-Patches-510415 ] Improve MIME header handling Message-ID: Patches item #510415, was opened at 2002-01-30 00:19 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Closed Resolution: Accepted Priority: 5 Submitted By: Martin v. Löwis (loewis) Assigned to: Nobody/Anonymous (nobody) Summary: Improve MIME header handling Initial Comment: This patch fixes a number of problems for non-English archives. In particular: - it normalizes the encoding name (converting to lower-case, splitting of potential \r characters, and splitting off potential quotes) - if the article and the header encoding differ, it tries to preserve the decoded header as a Unicode string, instead of immediately falling back to the MIME-encoded one (if the encoding is not known to Python it will still fall back) - if a Unicode string needs to be formatted, it uses character references for all non-ASCII characters. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-28 15:26 Message: Logged In: YES user_id=105527 Thanks, now this is clear. I'll try the beta ASAP :-) ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-06-28 06:01 Message: Logged In: YES user_id=12800 k-fish, Martin was actually referring to the revision of one of the files in the Mailman 2.1 distribution. MM2.1 is in beta testing now and will officially support internationalization. The MM2.0.x does not. I'm closing this patch since as Martin says, it's already applied! ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-20 00:21 Message: Logged In: YES user_id=105527 Ok, I could have had a look at the patch header more closely, sorry. Thanks for your answer though, I wasn't aware of 2.14 being existent at all, since 2.0.9 seems to be the latest version being officially avilable... Anyway, my problem with german Umlauts being screwed up was solved by running arch manually, somehow the Umlauts seems to be only messed up when the archiver is run automatically... And rather than backporting (especially now, since my special problem was solved so easily ;) I would love to see a newer version of mailman being released officially... Thanks again for you answer! ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-06-19 20:17 Message: Logged In: YES user_id=21627 The patch applies to version 2.13 of HyperArch.py, just as the patch header says. It was current for the mailman CVS at the time of its creation. It has been applied to the mailman CVS by now (as 2.14), so it is now useless. Feel free to back-port it to mailman 2.0.8 if you want. ---------------------------------------------------------------------- Comment By: Karsten Dambekalns (k-fish) Date: 2002-06-19 18:55 Message: Logged In: YES user_id=105527 I tried to apply this patch to mailman 2.0.8 and 2.0.9, and both times the patch didn't apply cleanly. In fact 6 out of 10 hunks failed here. Any hints on that? For which version was the patch created? ---------------------------------------------------------------------- Comment By: Martin v. Löwis (loewis) Date: 2002-04-02 07:40 Message: Logged In: YES user_id=21627 The second version of this patch expects and ignores LookupError from unicode(), and it decodes the subjects from the next and previous articles. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=510415&group_id=103 From danny@terweij.nl Fri Jun 28 19:34:26 2002 From: danny@terweij.nl (Danny Terweij) Date: Fri, 28 Jun 2002 20:34:26 +0200 Subject: [Mailman-Developers] article.html (MM2.1b2) References: <1025215422.19168.7.camel@enterprise.tj.sc.gov.br><00cd01c21e2f$ecc62520$1e00a8c0@onsnet.org><15643.41082.318520.783924@anthem.wooz.org><00f001c21e36$7b3a97e0$1e00a8c0@onsnet.org><15643.51607.182066.428033@anthem.wooz.org><021601c21ea6$3893a600$1e00a8c0@onsnet.org> <15644.27912.234620.214644@anthem.wooz.org> Message-ID: <02f301c21ed2$6ebde7a0$1e00a8c0@onsnet.org> Hi, I have found a problem in the article.html from the templates. When a table is used (), then it is ignoring to parse the %(xxx)s commands. Instead of parsing them, it just shows the %(command)s on the web page. Danny Terweij. From barry@zope.com Sat Jun 29 00:36:11 2002 From: barry@zope.com (Barry A. Warsaw) Date: Fri, 28 Jun 2002 19:36:11 -0400 Subject: [Mailman-Developers] Splitting long header lines and the "bug demonstration" References: <15613.31768.357110.313371@anthem.wooz.org> Message-ID: <15644.62187.931912.926933@anthem.wooz.org> Earlier this month (seems like years ago ;), I said: BAW> I know what is causing BAW> BAW> http://mail.python.org/pipermail-21/mailman-developers/2002-June/012093.html BAW> It's the email package, and specifically it's Generator's BAW> behavior when splitting long lines, BAW> i.e. Generator._split_header(). BAW> I actually think that method is terminally broken because it BAW> has a ascii bias. I doubt it would even work for long lines BAW> of encoded text. BAW> The good news is that we have a perfectly fine line splitter BAW> that understands encoded headers and does the RFC-correct BAW> thing. It's called Header.encode(). BAW> The bad news is that Header.encode() isn't parameter aware BAW> and making _split_header() call it will cause some messages BAW> to not generate idempotently. If your code is expecting the BAW> splitting done by _split_header(), your code will break. BAW> Interestingly enough, only 4 unit tests fail when I make this BAW> change. I've worked on resurrecting Generator._split_header() into Header.encode() when the charset is None or 'us-ascii'. Basically in that case, we'll split on the highest syntactic boundary we know about, which means either semicolons or spaces. I don't handle other syntax in other types of structured headers. Even this might not be completely correct since Header (still) doesn't know about parameters. In the long term, it probably makes sense to move parameter parsing from the Message class to the Header class, use that for syntactic splitting, and change Message to use Header instances. But that's more work than I have time for now. It may make sense to use the "ascii splitter" on other types of character sets, but I'm not going to think about that right now. :) Last time, Steve Turnbull commented: SJT> If by "split" you mean RFC 2822 2.2.3 header folding, you SJT> can't split "spooge" like that, can you? There's no SJT> whitespace between the `o's. And now, if a line has no semicolons or spaces, it doesn't get split. This could cause us to violate RFC 2822's hard maximum of 998 characters in a line, but I'm not going to worry about this. Some day we might want a verification stage, or raise an exception, etc. I think I have updated test cases to cover all this, but I haven't yet tested it in MM2.1, so I may find that I'm missing something. Finally, some of the Japanese test cases broke. Since there's no way for me to know whether they're still correct, I simply changed the tests. But I'd appreciate it if someone with Japanese and RFC 2047 expertise could take a closer look. Commits going into cvs momentarily. -Barry From danny@terweij.nl Sat Jun 29 15:28:51 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 16:28:51 +0200 Subject: [Mailman-Developers] shunt / unshunt Message-ID: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> Hi, What are the files in the shunt dir? When i do bin/unshunt then there is somthing happen, it sends a mail out and the shunt dir is growing. Danny Terweij MM21b2 From barry@zope.com Sat Jun 29 16:03:44 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 29 Jun 2002 11:03:44 -0400 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> Message-ID: <15645.52304.512014.854946@anthem.wooz.org> >>>>> "DT" == Danny Terweij writes: DT> What are the files in the shunt dir? When i do bin/unshunt DT> then there is somthing happen, it sends a mail out and the DT> shunt dir is growing. You need to tail your logs/error file. Messages get sent to shunt when there's a bug in Mailman so there should be a traceback in the error log. The idea is that you fix the bug, then run bin/unshunt to complete delivery of those messages. It doesn't do any good to unshunt a message while the bug still exists. -Barry From danny@terweij.nl Sat Jun 29 15:41:41 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 16:41:41 +0200 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> <15645.52304.512014.854946@anthem.wooz.org> Message-ID: <013701c21f7b$158b89e0$1e00a8c0@onsnet.org> From: "Barry A. Warsaw" > You need to tail your logs/error file. Messages get sent to shunt > when there's a bug in Mailman so there should be a traceback in the > error log. > > The idea is that you fix the bug, then run bin/unshunt to > complete delivery of those messages. It doesn't do any good to > unshunt a message while the bug still exists. Hmm, I did the following: Translation of /nl/mailman.po Not all translations are translated, i did want to see the already created translations.. I ran msgfmt and copy messages.mo to mailman.mo Created the new language at Defaults.py (bottom). At the mailing list admin links (Test list), set default language to Dutch, and set the users language to Dutch. Then when sending a message to the list it is not processed. it sits then in the shunt dir. Lets take a look at the error file: Jun 29 16:43:30 2002 (17486) Uncaught runner exception: nl Jun 29 16:43:30 2002 (17486) 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 154, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 183, in _dispose msg = res.make_response() File "/usr/local/mailman/Mailman/Queue/CommandRunner.py", line 143, in make_response _charset=Utils.GetCharSet(self.mlist.preferred_language)) File "/usr/local/mailman/Mailman/Utils.py", line 649, in GetCharSet return mm_cfg.LC_DESCRIPTIONS[lang][1] KeyError: nl From barry@zope.com Sat Jun 29 16:15:48 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 29 Jun 2002 11:15:48 -0400 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> <15645.52304.512014.854946@anthem.wooz.org> <013701c21f7b$158b89e0$1e00a8c0@onsnet.org> Message-ID: <15645.53028.599177.274487@anthem.wooz.org> Did you "bin/mailmanctl restart"? You always need to do that after hacking mm_cfg.py (or Defaults.py, which you should avoid ;). -Barry From danny@terweij.nl Sat Jun 29 15:48:45 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 16:48:45 +0200 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org><15645.52304.512014.854946@anthem.wooz.org><013701c21f7b$158b89e0$1e00a8c0@onsnet.org> <15645.53028.599177.274487@anthem.wooz.org> Message-ID: <013f01c21f7c$11db84c0$1e00a8c0@onsnet.org> From: "Barry A. Warsaw" > Did you "bin/mailmanctl restart"? You always need to do that after > hacking mm_cfg.py (or Defaults.py, which you should avoid ;). I did not :-) But i did 15 mins ago a mailmanctl stop :) It was running for 44 days. Can i copy the whole Defaults.py to mm_cfg.py? en then edit my modifications in there? I am waiting before i start the qrunner again :) Danny. From barry@zope.com Sat Jun 29 16:25:08 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 29 Jun 2002 11:25:08 -0400 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> <15645.52304.512014.854946@anthem.wooz.org> <013701c21f7b$158b89e0$1e00a8c0@onsnet.org> <15645.53028.599177.274487@anthem.wooz.org> <013f01c21f7c$11db84c0$1e00a8c0@onsnet.org> Message-ID: <15645.53588.800111.564542@anthem.wooz.org> >>>>> "DT" == Danny Terweij writes: >> Did you "bin/mailmanctl restart"? You always need to do that >> after hacking mm_cfg.py (or Defaults.py, which you should avoid >> ;). DT> I did not :-) But i did 15 mins ago a mailmanctl stop :) It DT> was running for 44 days. That's a good sigh. :) DT> Can i copy the whole Defaults.py to mm_cfg.py? en then edit my DT> modifications in there? I am waiting before i start the DT> qrunner again :) No need. Just put in mm_cfg.py customizations that override Defaults.py. The MM installation process will overwrite Defaults.py but never mm_cfg.py. Your add_language() change is questionable though, because that /is/ something that's been added to Defaults.py{.in} already (in cvs). -Barry From danny@terweij.nl Sat Jun 29 16:03:14 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 17:03:14 +0200 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org><15645.52304.512014.854946@anthem.wooz.org><013701c21f7b$158b89e0$1e00a8c0@onsnet.org><15645.53028.599177.274487@anthem.wooz.org><013f01c21f7c$11db84c0$1e00a8c0@onsnet.org> <15645.53588.800111.564542@anthem.wooz.org> Message-ID: <014b01c21f7e$180953c0$1e00a8c0@onsnet.org> From: "Barry A. Warsaw" > DT> Can i copy the whole Defaults.py to mm_cfg.py? en then edit my > DT> modifications in there? I am waiting before i start the > DT> qrunner again :) > No need. Just put in mm_cfg.py customizations that override > Defaults.py. The MM installation process will overwrite Defaults.py > but never mm_cfg.py. I am aware of it, but do not remember witch settings are default. Thats why i asked for copy the whole Defaults.py to mm_cfg.py :) Also thats why i am afraid of if i install the mailman-cvs to the current installation for overwriting the Defaults.py. If i knew better and before, then i added all the modifications to mm-cfg.py :) So i did the last changes to this file. > Your add_language() change is questionable though, because that /is/ > something that's been added to Defaults.py{.in} already (in cvs). I did now added the add_language() to the mm_cfg.py for nl (dutch). I am ready to start mailman :) lets see for error to the error file, if any :) Danny. From barry@zope.com Sat Jun 29 16:37:57 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 29 Jun 2002 11:37:57 -0400 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> <15645.52304.512014.854946@anthem.wooz.org> <013701c21f7b$158b89e0$1e00a8c0@onsnet.org> <15645.53028.599177.274487@anthem.wooz.org> <013f01c21f7c$11db84c0$1e00a8c0@onsnet.org> <15645.53588.800111.564542@anthem.wooz.org> <014b01c21f7e$180953c0$1e00a8c0@onsnet.org> Message-ID: <15645.54357.553689.375220@anthem.wooz.org> Cool. BTW, I just checked out some (simple) Dutch templates. Looks good to me. -Barry From danny@terweij.nl Sat Jun 29 16:07:46 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 17:07:46 +0200 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org><15645.52304.512014.854946@anthem.wooz.org><013701c21f7b$158b89e0$1e00a8c0@onsnet.org><15645.53028.599177.274487@anthem.wooz.org><013f01c21f7c$11db84c0$1e00a8c0@onsnet.org><15645.53588.800111.564542@anthem.wooz.org> <014b01c21f7e$180953c0$1e00a8c0@onsnet.org> Message-ID: <015101c21f7e$ba201400$1e00a8c0@onsnet.org> From: "Danny Terweij" > I am ready to start mailman :) lets see for error to the error file, if any > :) [root@lnx bin]# ./mailmanctl start Traceback (most recent call last): File "./mailmanctl", line 101, in ? from Mailman import mm_cfg File "/usr/local/mailman/Mailman/mm_cfg.py", line 69, in ? add_language('nl', _('Nederlands'), 'us-ascii') NameError: name '_' is not defined [root@lnx bin]# I am going to remove the add_language line from mm_cfg.py and add it again to Defaults.py. Lets see what then is happen.. Danny. From danny@terweij.nl Sat Jun 29 16:15:50 2002 From: danny@terweij.nl (Danny Terweij) Date: Sat, 29 Jun 2002 17:15:50 +0200 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org><15645.52304.512014.854946@anthem.wooz.org><013701c21f7b$158b89e0$1e00a8c0@onsnet.org><15645.53028.599177.274487@anthem.wooz.org><013f01c21f7c$11db84c0$1e00a8c0@onsnet.org><15645.53588.800111.564542@anthem.wooz.org><014b01c21f7e$180953c0$1e00a8c0@onsnet.org> <015101c21f7e$ba201400$1e00a8c0@onsnet.org> Message-ID: <017201c21f7f$da9c9e00$1e00a8c0@onsnet.org> From: "Danny Terweij" > > I am ready to start mailman :) lets see for error to the error file, if > any > > :) > > [root@lnx bin]# ./mailmanctl start > Traceback (most recent call last): > File "./mailmanctl", line 101, in ? > from Mailman import mm_cfg > File "/usr/local/mailman/Mailman/mm_cfg.py", line 69, in ? > add_language('nl', _('Nederlands'), 'us-ascii') > NameError: name '_' is not defined > [root@lnx bin]# > > I am going to remove the add_language line from mm_cfg.py and add it again > to Defaults.py. > > Lets see what then is happen.. Now the master qrunner is running. Lets post a message to the list... And it works. Lets do some unshunting... shunt directory is empty now. Lets check the already made translations... This is working. Wow, this is gonna be cool, i now know how to handle it. But the add_language to the mm_cfg.py does not work. Danny. From barry@zope.com Sat Jun 29 17:16:45 2002 From: barry@zope.com (Barry A. Warsaw) Date: Sat, 29 Jun 2002 12:16:45 -0400 Subject: [Mailman-Developers] shunt / unshunt References: <012a01c21f79$4aa004a0$1e00a8c0@onsnet.org> <15645.52304.512014.854946@anthem.wooz.org> <013701c21f7b$158b89e0$1e00a8c0@onsnet.org> <15645.53028.599177.274487@anthem.wooz.org> <013f01c21f7c$11db84c0$1e00a8c0@onsnet.org> <15645.53588.800111.564542@anthem.wooz.org> <014b01c21f7e$180953c0$1e00a8c0@onsnet.org> <015101c21f7e$ba201400$1e00a8c0@onsnet.org> <017201c21f7f$da9c9e00$1e00a8c0@onsnet.org> Message-ID: <15645.56685.300165.829194@anthem.wooz.org> >>>>> "DT" == Danny Terweij writes: DT> Wow, this is gonna be cool, i now know how to handle it. DT> But the add_language to the mm_cfg.py does not work. You must need to add from Mailman.i18n import _ Or do a cvs update. :) -Barry From barry@wooz.org Sun Jun 30 16:37:54 2002 From: barry@wooz.org (Barry A. Warsaw) Date: Sun, 30 Jun 2002 11:37:54 -0400 Subject: [Mailman-Developers] Bug in CVS References: <3D0F5C9B.2050807@utopia.west.sun.com> Message-ID: <15647.9682.385270.791748@anthem.wooz.org> >>>>> "DM" == Dan Mick writes: DM> Bouncer.py refers to BYUNKNOWN instead of UNKNOWN. Here's the DM> fix: Thanks guys, applied. -Barry From kristoffer@linpro.no Tue Jun 25 17:04:33 2002 From: kristoffer@linpro.no (Kristoffer Gleditsch) Date: Tue, 25 Jun 2002 18:04:33 +0200 Subject: [Mailman-Developers] Making the anonymize option really anonymize Message-ID: ---------------------- multipart/mixed attachment Hi, We have a setup where we need the anonymizing feature "Hide the sender of a message ..." to actually anonymize the messages going through the list. Both in the archive and in the mails it sent out, it left headers that (normally) make it pretty easy to track the sender. This patch against Mailman/Handlers/Cleanse.py from version 2.0.11 should remove most of those. It strips the recieved-headers, generates a new Message-ID and sets the envelope-from address to the list admin. ---------------------- multipart/mixed attachment Index: Mailman/Handlers/Cleanse.py =================================================================== RCS file: /linpro/local/CVSROOT/mailman-limacute/Mailman/Handlers/Cleanse.py,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- Mailman/Handlers/Cleanse.py 15 Feb 2002 16:28:03 -0000 1.1 +++ Mailman/Handlers/Cleanse.py 18 Jun 2002 20:33:34 -0000 1.2 @@ -16,6 +16,7 @@ """Cleanse certain headers from all messages.""" +from Mailman import Utils def process(mlist, msg, msgdata): # Always remove this header from any outgoing messages. Be sure to do @@ -27,8 +28,12 @@ if mlist.anonymous_list: del msg['reply-to'] del msg['sender'] + del msg['received'] + del msg['message-id'] + msg.unixfrom = "From " + mlist.GetAdminEmail() + "\n" msg['From'] = mlist.GetAdminEmail() msg['Reply-To'] = mlist.GetListEmail() + msg['Message-ID'] = Utils.make_msgid(idstring='Mailman') # # Some headers can be used to fish for membership del msg['return-receipt-to'] ---------------------- multipart/mixed attachment Regards, -- Kristoffer. ---------------------- multipart/mixed attachment--