From ambrose_christopher at yahoo.com Mon Jan 1 04:01:47 2007 From: ambrose_christopher at yahoo.com (AMBROSE CHRISTOPHER) Date: Sun, 31 Dec 2006 19:01:47 -0800 (PST) Subject: [Mailman-Users] Mailman-Users Digest, Vol 34, Issue 70 In-Reply-To: Message-ID: <288117.28696.qm@web50914.mail.yahoo.com> no offense but i thought you guys used just so you could have as a teaching tool ,I never even considered possibility that was what you actually preffered to use. some of the new stuff show you examples of 1ooo ways to do and with the new discs and redundancy in them, you can look at completely in every respect before even making a decision. But you get 1 100th the problems. tough to teach from that. like having a harley and buying a honda.you suddenly find yourself riding rather then fixing. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From brad at shub-internet.org Mon Jan 1 07:12:25 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 1 Jan 2007 00:12:25 -0600 Subject: [Mailman-Users] Mailman-Users Digest, Vol 34, Issue 70 In-Reply-To: <288117.28696.qm@web50914.mail.yahoo.com> References: <288117.28696.qm@web50914.mail.yahoo.com> Message-ID: At 7:01 PM -0800 12/31/06, AMBROSE CHRISTOPHER wrote: > no offense but i thought you guys used just so you could have as a > teaching tool ,I never even considered possibility that was what > you actually preffered to use. I'm confused. What are you talking about? > some of the new stuff show you examples of 1ooo ways to do and > with the new discs and redundancy in them, you can look at > completely in every respect before even making a decision. But > you get 1 100th the problems. tough to teach from that. like > having a harley and buying a honda.you suddenly find yourself > riding rather then fixing. I'm sorry, I'm not understanding anything that you're saying. Are you sure that this is the list where you intended to post this material? -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. From emmexx at tiscalinet.it Mon Jan 1 23:31:22 2007 From: emmexx at tiscalinet.it (emmexx) Date: Mon, 01 Jan 2007 23:31:22 +0100 Subject: [Mailman-Users] Moderator subscribing by email Message-ID: <45998BBA.2090806@tiscalinet.it> I'm starting to write a program that my club needs to keep in sync a database and the subscribers of a couple of mailing list. I know there are the users web pages, the -request or -subscribe addresses or the administration panel but I would like to automate the process. It would be great if a list moderator or administrator could subscribe or unsubscribe somebody by email. I mean: - the moderator sends a message to listname-request containing his (moderator) password and the address to subscribe. - the address gets suscribed with no need to confirm. I found nothing of this kind in the faq and in the archives of this mailing list. I can't access the server, so I can't patch/add/modify any server file or configuration. thank you maxx From dragon at crimson-dragon.com Tue Jan 2 07:41:35 2007 From: dragon at crimson-dragon.com (Dragon) Date: Mon, 01 Jan 2007 22:41:35 -0800 Subject: [Mailman-Users] Moderator subscribing by email In-Reply-To: <45998BBA.2090806@tiscalinet.it> References: <45998BBA.2090806@tiscalinet.it> Message-ID: <7.0.1.0.2.20070101223902.07119a20@crimson-dragon.com> emmexx did speak thusly: >I can't access the server, so I can't patch/add/modify any server file >or configuration. ---------------- End original message. --------------------- Everything you said above that is essentially moot unless you can find somebody who can do so. What you wish to do requires code modifications, you are pretty much out of luck as there is no standard configuration that will allow you to do what you wish. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From batkins at tlcdelivers.com Tue Jan 2 21:08:12 2007 From: batkins at tlcdelivers.com (Brian Atkins) Date: Tue, 02 Jan 2007 15:08:12 -0500 Subject: [Mailman-Users] The incredible disapearing post? Message-ID: <459ABBAC.8020306@tlcdelivers.com> Greetings, all! I have a mailing list set up for company-wide emails to which any member can post (in other words, a plain vanilla list). However, I have one user that has been attempting to post to the list but his emails are disappearing. I can see the message hitting the server and being passed off to mailman, but I can not find anything in the mailman logs to indicate that it was ever received. His account is identical to everyone else, but he 'appears' to be the only member that has this issue. I have removed and recreated his account several times, but there has been no change. Any ideas on where to look? MAIL.LOG: --------- Jan 2 09:19:27 mail sendmail[13025]: l02EJNaC013025: from=, size=1791, class=0, nrcpts=1, msgid=<001801c72e79$02aa6370$163b0a0a at MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=[10.10.57.184] Jan 2 09:21:04 mail sendmail[13363]: l02EJNaC013025: to="|/usr/local/mailman/mail/mailman post COMPANY", ctladdr= (8/0), delay=00:01:37, xdelay=00:00:02, mailer=prog, pri=121791, dsn=2.0.0, stat=Sent Here is another user sending the same post (text-wise) to the same list: MAIL.LOG: --------- Jan 2 11:44:05 mail sendmail[13136]: l02Gi16Y013136: from=, size=5831, class=0, nrcpts=1, msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=[10.10.59.56] Jan 2 11:45:04 mail sendmail[13368]: l02Gi16Y013136: to="|/usr/local/mailman/mail/mailman post COMPANY", ctladdr= (8/0), delay=00:00:59, xdelay=00:00:00, mailer=prog, pri=125831, dsn=2.0.0, stat=Sent Jan 2 11:45:09 mail sendmail[13419]: l02Gj9dq013419: from=, size=6793, class=-30, nrcpts=53, msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] Jan 2 11:46:36 mail sendmail[13419]: l02Gj9dr013419: from=, size=6793, class=-30, nrcpts=149, msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1] -- Brian "An adventure is never an adventure when it's happening. Challenging experiences need time to ferment, and an adventure is simply physical and emotional discomfort recollected in tranquility." -- Tim Cahill From ptomblin at xcski.com Tue Jan 2 21:34:13 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 2 Jan 2007 15:34:13 -0500 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <459ABBAC.8020306@tlcdelivers.com> References: <459ABBAC.8020306@tlcdelivers.com> Message-ID: <20070102203413.GA29171@allhats.xcski.com> Quoting Brian Atkins (batkins at tlcdelivers.com): > can post (in other words, a plain vanilla list). However, I have one > user that has been attempting to post to the list but his emails are > disappearing. > > I can see the message hitting the server and being passed off to > mailman, but I can not find anything in the mailman logs to indicate > that it was ever received. His account is identical to everyone else, > but he 'appears' to be the only member that has this issue. I have > removed and recreated his account several times, but there has been no > change. > > Any ideas on where to look? > Look on the admindb page to see if they're being held for some reason. -- Paul Tomblin http://blog.xcski.com/ If men are from Mars and women are from Venus, there's going to be one big-ass fight over where to set the thermostat. -- Jim Rosenberg From dragon at crimson-dragon.com Tue Jan 2 22:02:58 2007 From: dragon at crimson-dragon.com (Dragon) Date: Tue, 02 Jan 2007 13:02:58 -0800 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <459ABBAC.8020306@tlcdelivers.com> References: <459ABBAC.8020306@tlcdelivers.com> Message-ID: <7.0.1.0.2.20070102125640.0685e4e8@crimson-dragon.com> Brian Atkins sent the message below at 12:08 1/2/2007: >Greetings, all! > >I have a mailing list set up for company-wide emails to which any member >can post (in other words, a plain vanilla list). However, I have one >user that has been attempting to post to the list but his emails are >disappearing. > >I can see the message hitting the server and being passed off to >mailman, but I can not find anything in the mailman logs to indicate >that it was ever received. His account is identical to everyone else, >but he 'appears' to be the only member that has this issue. I have >removed and recreated his account several times, but there has been no >change. > >Any ideas on where to look? > >MAIL.LOG: >--------- >Jan 2 09:19:27 mail sendmail[13025]: l02EJNaC013025: >from=, size=1791, class=0, nrcpts=1, >msgid=<001801c72e79$02aa6370$163b0a0a at MYDOMAIN.com>, proto=ESMTP, >daemon=MTA, relay=[10.10.57.184] > >Jan 2 09:21:04 mail sendmail[13363]: l02EJNaC013025: >to="|/usr/local/mailman/mail/mailman post COMPANY", >ctladdr= (8/0), delay=00:01:37, xdelay=00:00:02, >mailer=prog, pri=121791, dsn=2.0.0, stat=Sent > >Here is another user sending the same post (text-wise) to the same list: >MAIL.LOG: >--------- >Jan 2 11:44:05 mail sendmail[13136]: l02Gi16Y013136: >from=, size=5831, class=0, nrcpts=1, >msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, >daemon=MTA, relay=[10.10.59.56] > >Jan 2 11:45:04 mail sendmail[13368]: l02Gi16Y013136: >to="|/usr/local/mailman/mail/mailman post COMPANY", >ctladdr= (8/0), delay=00:00:59, xdelay=00:00:00, >mailer=prog, pri=125831, dsn=2.0.0, stat=Sent > >Jan 2 11:45:09 mail sendmail[13419]: l02Gj9dq013419: >from=, size=6793, class=-30, nrcpts=53, >msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, >daemon=MTA, relay=localhost [127.0.0.1] > >Jan 2 11:46:36 mail sendmail[13419]: l02Gj9dr013419: >from=, size=6793, class=-30, nrcpts=149, >msgid=<200701021644.l02Gi16Y013136 at MYDOMAIN.com>, proto=ESMTP, >daemon=MTA, relay=localhost [127.0.0.1] ---------------- End original message. --------------------- It appears that something is happening to either discard or shunt that user's posts prior to them being handed off to mailman's outgoing queue. The message is being handed off from the SMTP server to mailman but something is happening after that occurs. Have you looked in mailman's vette and error logs? If the message was discarded, it should appear in the vette log. If mailman had a problem processing the message, there should be an entry in the error log. If you have archiving enabled, is the message hitting the archive? Is the person who is having difficulty using an MUA that is the same or different from what others use? Are you doing any sort of content filtering or scrubbing? It could be that after scrubbing of the mail message there are no valid parts left to send. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From batkins at tlcdelivers.com Tue Jan 2 21:55:43 2007 From: batkins at tlcdelivers.com (Brian Atkins) Date: Tue, 02 Jan 2007 15:55:43 -0500 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <20070102203413.GA29171@allhats.xcski.com> References: <459ABBAC.8020306@tlcdelivers.com> <20070102203413.GA29171@allhats.xcski.com> Message-ID: <459AC6CF.6060405@tlcdelivers.com> I guess I forgot to add that info to my previous post. No, it's not getting hung up in the admindb. I was able to get one message from him to go through this afternoon by unchecking 'log on to the server before sending' in Outlook. Hmmm... I can't imagine why that would have prevented him from sending through mailman. I decided to look there after I noticed that the message he was sending had a message ID of "@AD-DOMAIN.DOMAIN.COM" and the other user was "@mail.DOMAIN.COM". Weird. Any idea why that would have caused an issue with Mailman? Brian Paul Tomblin wrote: > Quoting Brian Atkins (batkins at tlcdelivers.com): >> can post (in other words, a plain vanilla list). However, I have one >> user that has been attempting to post to the list but his emails are >> disappearing. >> >> I can see the message hitting the server and being passed off to >> mailman, but I can not find anything in the mailman logs to indicate >> that it was ever received. His account is identical to everyone else, >> but he 'appears' to be the only member that has this issue. I have >> removed and recreated his account several times, but there has been no >> change. >> >> Any ideas on where to look? >> > > Look on the admindb page to see if they're being held for some reason. > From ptomblin at xcski.com Tue Jan 2 22:20:15 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 2 Jan 2007 16:20:15 -0500 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <459AC6CF.6060405@tlcdelivers.com> References: <459ABBAC.8020306@tlcdelivers.com> <20070102203413.GA29171@allhats.xcski.com> <459AC6CF.6060405@tlcdelivers.com> Message-ID: <20070102212015.GA3081@allhats.xcski.com> Quoting Brian Atkins (batkins at tlcdelivers.com): > I was able to get one message from him to go through this afternoon by > unchecking 'log on to the server before sending' in Outlook. > > Hmmm... I can't imagine why that would have prevented him from sending > through mailman. I decided to look there after I noticed that the > message he was sending had a message ID of "@AD-DOMAIN.DOMAIN.COM" and > the other user was "@mail.DOMAIN.COM". If it's changing the Message-ID, it might be changing the From address as well. Is your mailing list set to reject mail from non-members? If so, it's possible that Outlook is changing his From to something other than what he subscribed as. Is there anything in the vette log? -- Paul Tomblin http://blog.xcski.com/ Quality Control, n.: The process of testing one out of every 1,000 units coming off a production line to make sure that at least one out of 100 works. From batkins at tlcdelivers.com Tue Jan 2 22:30:35 2007 From: batkins at tlcdelivers.com (Brian Atkins) Date: Tue, 02 Jan 2007 16:30:35 -0500 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <20070102212015.GA3081@allhats.xcski.com> References: <459ABBAC.8020306@tlcdelivers.com> <20070102203413.GA29171@allhats.xcski.com> <459AC6CF.6060405@tlcdelivers.com> <20070102212015.GA3081@allhats.xcski.com> Message-ID: <459ACEFB.3070602@tlcdelivers.com> Nothing in vette or other logs. It is set to hold non-members, but I also have a rule in place to accept any sender on our domain, just in case the new employees aren't updated as frequently as need be. accept_these_non-members: ^.*@DOMAIN\.com Brian Paul Tomblin wrote: > If it's changing the Message-ID, it might be changing the From address as > well. Is your mailing list set to reject mail from non-members? If so, > it's possible that Outlook is changing his From to something other than > what he subscribed as. Is there anything in the vette log? > From batkins at tlcdelivers.com Tue Jan 2 22:37:26 2007 From: batkins at tlcdelivers.com (Brian Atkins) Date: Tue, 02 Jan 2007 16:37:26 -0500 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <7.0.1.0.2.20070102125640.0685e4e8@crimson-dragon.com> References: <459ABBAC.8020306@tlcdelivers.com> <7.0.1.0.2.20070102125640.0685e4e8@crimson-dragon.com> Message-ID: <459AD096.6080600@tlcdelivers.com> Dragon wrote: > It appears that something is happening to either discard or shunt that > user's posts prior to them being handed off to mailman's outgoing queue. > The message is being handed off from the SMTP server to mailman but > something is happening after that occurs. > > Have you looked in mailman's vette and error logs? If the message was > discarded, it should appear in the vette log. If mailman had a problem > processing the message, there should be an entry in the error log. No log entires. > If you have archiving enabled, is the message hitting the archive? Yes, it is enabled. No, it's not getting there. > Is the person who is having difficulty using an MUA that is the same or > different from what others use? Same. Everyone pretty much uses Outlook, 'cept those of us in the know. > Are you doing any sort of content filtering or scrubbing? It could be > that after scrubbing of the mail message there are no valid parts left > to send. No filtering is enabled. From vancleef at lostwells.net Tue Jan 2 22:47:47 2007 From: vancleef at lostwells.net (Hank van Cleef) Date: Tue, 2 Jan 2007 14:47:47 -0700 (MST) Subject: [Mailman-Users] Options page bombing out on a security violation Message-ID: <200701022147.l02LlmBI002907@bronze.lostwells.net> I'm attaching a user's description of something about 20 of my users are reporting on a fresh install of Mailman 2.1.9 I've edited the user identity, and am including configuration info following the forwarded mail. I'm baffled, because I cannot get this problem to happen from any of the systems at my site, and some users (unfortunately, all of the computer-literate types who might be able to help) aren't getting it either. > > I too am suffering from the > > "High security alert!!! > You are not permitted to download the file "user at userdomain.com". > > URL = http://bronze.lostwells.net/mailman/options/mercedes/user at userdomain.com" > > when trying to switch off the mail > > path followed is as follows:- > > > > 1, http://www.lostwells.net/mailman/listinfo/mercedes > > 2, click on "unsubscribe or edit options" button > > 3, http://bronze.lostwells.net/mailman/options/mercedes > > 4, sign in with normal login details, the page refreshes with all the > parameters viewable > > 5, disable mail delivery and click "submit my changes" > > 6, High Security message at the url > http://bronze.lostwells.net/mailman/options/mercedes/user at userdomain.com > > =================================================== Configuration details: Solaris 9 on Sun Ultra 10 Python 2.5 Mailman 2.1.9 Since I am taking over hosting for a list that was running on a Mailman 2.1.4 installation, I built a local 2.1.4 tree, created the list, then copied the old site config.pck over the newly-created one. Then built 2.1.9 and upgraded the 2.1.4 tree. # cd /usr/local/mailman # ./bin/check_perms No problems found Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From ptomblin at xcski.com Tue Jan 2 22:52:32 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 2 Jan 2007 16:52:32 -0500 Subject: [Mailman-Users] Options page bombing out on a security violation In-Reply-To: <200701022147.l02LlmBI002907@bronze.lostwells.net> References: <200701022147.l02LlmBI002907@bronze.lostwells.net> Message-ID: <20070102215232.GA8644@allhats.xcski.com> Quoting Hank van Cleef (vancleef at lostwells.net): > I'm attaching a user's description of something about 20 of my users are > reporting on a fresh install of Mailman 2.1.9 I've edited the user > identity, and am including configuration info following the forwarded > mail. I'm baffled, because I cannot get this problem to happen from > any of the systems at my site, and some users (unfortunately, all of > the computer-literate types who might be able to help) aren't getting it > either. > > > > > I too am suffering from the > > > > "High security alert!!! > > You are not permitted to download the file "user at userdomain.com". > > > > URL = http://bronze.lostwells.net/mailman/options/mercedes/user at userdomain.com" > > > > when trying to switch off the mail This looks like some stupid "security" feature on their browser that is supposed to prevent them from downloading something dangerous. I bet all 20 of them have installed the same anti-virus or anti-phishing software, or "upgraded" to IE 7. Tell them to use Firefox. -- Paul Tomblin http://blog.xcski.com/ Knuth is definitely the bastard something from hell. I just admire him from a distance, it's safer. -- Peter da Silva From msapiro at value.net Tue Jan 2 23:12:22 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 14:12:22 -0800 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <459AD096.6080600@tlcdelivers.com> Message-ID: Brian Atkins wrote: >Dragon wrote: > >> It appears that something is happening to either discard or shunt that >> user's posts prior to them being handed off to mailman's outgoing queue. >> The message is being handed off from the SMTP server to mailman but >> something is happening after that occurs. It looks that way to me too. >> Have you looked in mailman's vette and error logs? If the message was >> discarded, it should appear in the vette log. If mailman had a problem >> processing the message, there should be an entry in the error log. > >No log entires. It appears from the mail log that the message is delivered to the wrapper for posting to the list, and thus should get to the in queue (qfiles/in/), yet it doesn't get as far in the pipeline as ToArchive. If it is held, it should be in the admindb interface as a held message. If it is rejected, a reject message will be sent to the poster, but this doesn't appear to be in the mail log. If it is discarded for any reason, the discard should be logged in the vette log. If something goes seriously wrong, the exception should be logged in the error log. Is there anything in any of Mailman's queues? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dragon at crimson-dragon.com Tue Jan 2 23:12:32 2007 From: dragon at crimson-dragon.com (Dragon) Date: Tue, 02 Jan 2007 14:12:32 -0800 Subject: [Mailman-Users] The incredible disapearing post? In-Reply-To: <459ACEFB.3070602@tlcdelivers.com> References: <459ABBAC.8020306@tlcdelivers.com> <20070102203413.GA29171@allhats.xcski.com> <459AC6CF.6060405@tlcdelivers.com> <20070102212015.GA3081@allhats.xcski.com> <459ACEFB.3070602@tlcdelivers.com> Message-ID: <7.0.1.0.2.20070102140616.06879580@crimson-dragon.com> Brian Atkins sent the message below at 13:30 1/2/2007: >Nothing in vette or other logs. It is set to hold non-members, but I >also have a rule in place to accept any sender on our domain, just in >case the new employees aren't updated as frequently as need be. > >accept_these_non-members: ^.*@DOMAIN\.com ---------------- End original message. --------------------- Based on your previous post and the fact that the e-mail addresses show have host parts as well as the TLD, you would probably want to try a revised RE like this: ^.*@DOMAIN\.com|^.*@.*\.DOMAIN\.com This change allows any e-mail address that has a host part to pass as well as any from the TLD without a host part. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From cdaily at gmail.com Wed Jan 3 01:27:20 2007 From: cdaily at gmail.com (Camden Daily) Date: Tue, 2 Jan 2007 18:27:20 -0600 Subject: [Mailman-Users] Error during upgrade/migration Message-ID: <16264e070701021627t442d02dewb802d150737cc30a@mail.gmail.com> Hello all. I just took over a job where I have to admin a mailman server that died over the weekend. I have all the files, so I thought I'd just roll a new server and upgrade to the latest version. I'm going from version 2.1.4 to 2.1.9. After installing mailman from yum on Fedora 5, I added DEFAULT_EMAIL_HOST, DEFAULT_URL_HOST to mm_cfg.py, and set the VAR_PREFIX to point to a folder containing my old data, lists, archive, and spam folders. I ran check_perms -f, which set all the old list data to the correct mailman group. However, I can't seem to see the lists in my mailman setup anywhere. If I run list_lists, I get no results. If I create a new list, it shows up in the same place as my old list data, so I think it's pointing to the right place, but it's just not finding the old lists. I read about the move_list command, which seems to be deprecated. I tried doing withlist -l -r list-name, as well, but I would always get back the following error: Importing fix_url... Running fix_url.fix_url()... Loading list list-name (locked) Unknown list: list-name Traceback (most recent call last): File "/usr/lib/mailman/bin/withlist", line 297, in ? main() File "/usr/lib/mailman/bin/withlist", line 275, in main r = do_list(listname, args, func) File "/usr/lib/mailman/bin/withlist", line 201, in do_list return func(m, *args) File "/usr/lib/mailman/bin/fix_url.py", line 81, in fix_url mlist.web_page_url = web_page_url AttributeError: 'NoneType' object has no attribute 'web_page_url' Been pretty stuck at this point for awhile now. Any guidance would be appreciated. From msapiro at value.net Wed Jan 3 02:11:01 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 17:11:01 -0800 Subject: [Mailman-Users] Error during upgrade/migration In-Reply-To: <16264e070701021627t442d02dewb802d150737cc30a@mail.gmail.com> Message-ID: Camden Daily wrote: > >If I create a >new list, it shows up in the same place as my old list data, so I >think it's pointing to the right place, but it's just not finding the >old lists. Are you saying that you create a new list and it creates a directory at path/to/lists/new_list_name/ containing amomg other files, a config.pck file, and that you have some path/to/lists/old_list_name/ directories with config.pck files, and the new_list_name is listed by bin/list_lists, but the old_list_name is not? >I read about the move_list command, which seems to be deprecated. I >tried doing withlist -l -r list-name, as well, but I would always get >back the following error: Presumably you actually ran withlist -l -r fix_url list-name >Importing fix_url... >Running fix_url.fix_url()... >Loading list list-name (locked) >Unknown list: list-name withlist doesn't find the list 'list-name' >Traceback (most recent call last): > File "/usr/lib/mailman/bin/withlist", line 297, in ? > main() > File "/usr/lib/mailman/bin/withlist", line 275, in main > r = do_list(listname, args, func) > File "/usr/lib/mailman/bin/withlist", line 201, in do_list > return func(m, *args) > File "/usr/lib/mailman/bin/fix_url.py", line 81, in fix_url > mlist.web_page_url = web_page_url >AttributeError: 'NoneType' object has no attribute 'web_page_url' The above is really a bug in withlist in that it tries to run the callable script (fix_url in this case) even though it failed to load the list. All of the above say there is not a lists/list-name/config.pck file in the place mailman is looking for it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 3 02:28:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 17:28:12 -0800 Subject: [Mailman-Users] removing members with non-standard characters In-Reply-To: <45955713.9070808@ncmail.net> Message-ID: Anne Ramey wrote: >> >The list_members -i | remove_members pipe is what worked for me. Thanks for clarifying. BTW, this pipe is one of the techniques suggested in . Since you didn't seem to see it there, I have updated the FAQ to try to emphasize that this is the method of choice. Please take a look at the FAQ and see if it looks better to you. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From raygeeknyc at gmail.com Wed Jan 3 02:36:15 2007 From: raygeeknyc at gmail.com (Raymond Blum) Date: Tue, 2 Jan 2007 20:36:15 -0500 Subject: [Mailman-Users] preserving original lists' subject prefix Message-ID: Hi all I have a situation where I need to preserve the "history" or chain of subscriptions that a message has passed through on its way to the recipients. For example if user1 subscribes to list1 and list1 is subscribed to list2, I wish messages sent to list2 to have something like this in the subject [List1] [List2] here is a message for you It looks like mailman is removing [List2], leaving me with [List1] ... as the subject. If empty out the subject prefix for List1, then neither appears. Is there a way to do this? I was surprised to see that Mailman was rewriting the subject, rather than just prefacing it. Thanks ---Raymond From msapiro at value.net Wed Jan 3 02:57:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 17:57:26 -0800 Subject: [Mailman-Users] preserving original lists' subject prefix In-Reply-To: Message-ID: Raymond Blum wrote: > I have a situation where I need to preserve the "history" or chain of >subscriptions that a message has passed through on its way to the >recipients. For example if user1 subscribes to list1 and list1 is >subscribed to list2, I wish messages sent to list2 to have something like >this in the subject > >[List1] [List2] here is a message for you > >It looks like mailman is removing [List2], leaving me with [List1] ... as >the subject. If empty out the subject prefix for List1, then neither >appears. It should work as you expect. What mailman version is this? What is the value of subject_prefix for each of the lists? What is the setting in Defaults.py-mm_cfg.py for OLD_STYLE_PREFIXING? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cdaily at gmail.com Wed Jan 3 03:50:35 2007 From: cdaily at gmail.com (Camden Daily) Date: Tue, 2 Jan 2007 20:50:35 -0600 Subject: [Mailman-Users] Error during upgrade/migration In-Reply-To: References: <16264e070701021627t442d02dewb802d150737cc30a@mail.gmail.com> Message-ID: <16264e070701021850g330c51b6j85592c20c71fbd33@mail.gmail.com> > Are you saying that you create a new list and it creates a directory at > path/to/lists/new_list_name/ containing amomg other files, a > config.pck file, and that you have some path/to/lists/old_list_name/ > directories with config.pck files, and the new_list_name is listed by > bin/list_lists, but the old_list_name is not? exactly. > Presumably you actually ran > > withlist -l -r fix_url list-name Yes, I ran it with the fix_url argument. Sorry I left that out of my post. > All of the above say there is not a lists/list-name/config.pck file in > the place mailman is looking for it. They all seem to be there just fine... mailman just doesn't want to read them. Is there something special that I need to do since they're from an old version? Each lists/list-name folder has config.pck, config.pck.last, and request.db in it. Some also have a digest.mbox file. Thanks for the reply! From msapiro at value.net Wed Jan 3 04:28:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 19:28:26 -0800 Subject: [Mailman-Users] Error during upgrade/migration In-Reply-To: <16264e070701021850g330c51b6j85592c20c71fbd33@mail.gmail.com> Message-ID: Camden Daily wrote: > >> All of the above say there is not a lists/list-name/config.pck file in >> the place mailman is looking for it. > >They all seem to be there just fine... mailman just doesn't want to >read them. Is there something special that I need to do since they're >from an old version? Each lists/list-name folder has config.pck, >config.pck.last, and request.db in it. Some also have a digest.mbox >file. No, there is nothing special to do for the 'old version'. Mailman will take care of updating the data automatically when it successfully accesses the lists. If the list data files are in the same lists/ directory as new lists that work, perhaps it is an ownership/permissions issue. is the group and permissions of the lists/list-name/ directory and contents the same as those of a list that is found? BTW, the requests.db changed to requests.pck in 2.1.5. After the lists are actually working and a requests.pck has been created, you can remove the requests.db. There will also be a pending.pck when things are working. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spyropolymiadis at kromestudios.com Wed Jan 3 04:47:43 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Wed, 03 Jan 2007 14:17:43 +1030 Subject: [Mailman-Users] Incorrect links after list creation Message-ID: <459B275F.7070909@kromestudios.com> Im using v2.1.9 on my debian system - and one thing that is bugging me now - only because I cant find the solution, is that after i create a new list, and it comes to the summary page saying "You can now: visit the info page, admin page, or create another list" the first 2 links are missing a / in the URL looking at the source - its is displayed as thus: Visit the list's info page Visit the list's admin page Create another list as you can see, the parts in caps is missing a / after the mailman bit and before the info/admin bit... but the create new list link is fine.. (note: ive just written it in caps to make it stand out better) Where would I go to fix this? Cheers Spyro This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. From msapiro at value.net Wed Jan 3 05:15:52 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 20:15:52 -0800 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: <459B275F.7070909@kromestudios.com> Message-ID: Spyro Polymiadis wrote: >Im using v2.1.9 on my debian system - and one thing that is bugging me >now - only because I cant find the solution, is that after i create a >new list, and it comes to the summary page saying "You can now: visit >the info page, admin page, or create another list" the first 2 links are >missing a / in the URL The list's web_page_url attribute is missing a trailing slash because DEFAULT_URL_PATTERN in mm_cfg.py is missing a trailing slash. It looks like DEFAULT_URL_PATTERN is set to 'http://%s/cgi-bin/mailman' and it should be 'http://%s/cgi-bin/mailman/'. Fix DEFAULT_URL_PATTERN in mm_cfg.py and see for info on running fix_url to fix the existing lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spyropolymiadis at kromestudios.com Wed Jan 3 05:22:16 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Wed, 03 Jan 2007 14:52:16 +1030 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: References: Message-ID: <459B2F78.9090400@kromestudios.com> Mark Sapiro wrote: > Spyro Polymiadis wrote: > > >> Im using v2.1.9 on my debian system - and one thing that is bugging me >> now - only because I cant find the solution, is that after i create a >> new list, and it comes to the summary page saying "You can now: visit >> the info page, admin page, or create another list" the first 2 links are >> missing a / in the URL >> > > > The list's web_page_url attribute is missing a trailing slash because > DEFAULT_URL_PATTERN in mm_cfg.py is missing a trailing slash. It looks > like DEFAULT_URL_PATTERN is set to 'http://%s/cgi-bin/mailman' and it > should be 'http://%s/cgi-bin/mailman/'. > > Fix DEFAULT_URL_PATTERN in mm_cfg.py and see > > for info on running fix_url to fix the existing lists. > > Would I have to do the fix_url thing? As all other links to do with the lists work fine - its just these 2 links that are incorrect You are right though - that attribute was missing the trailing slash - but it doesnt seem to have affected anything else though... Cheers Spyro This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. From msapiro at value.net Wed Jan 3 05:33:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 2 Jan 2007 20:33:47 -0800 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: <459B2F78.9090400@kromestudios.com> Message-ID: Spyro Polymiadis wrote: > >Would I have to do the fix_url thing? As all other links to do with the >lists work fine - its just these 2 links that are incorrect Check for example the links on the upper portion of the list's 'admin' interface pages. These are only some of the many links that should be wrong if web_page_url is wrong. >You are right though - that attribute was missing the trailing slash - >but it doesnt seem to have affected anything else though... If it truly doesn't affect other links, I don't understand why. There are many links that are obtained via the list's GetScriptURL method which is how the incorrect links you mentioned are obtained. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spyropolymiadis at kromestudios.com Wed Jan 3 05:47:21 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Wed, 03 Jan 2007 15:17:21 +1030 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: References: Message-ID: <459B3558.6020602@kromestudios.com> Mark Sapiro wrote: > Spyro Polymiadis wrote: > >> Would I have to do the fix_url thing? As all other links to do with the >> lists work fine - its just these 2 links that are incorrect >> > > > Check for example the links on the upper portion of the list's 'admin' > interface pages. These are only some of the many links that should be > wrong if web_page_url is wrong. > > > mmmm nah they are all fine... - i havent seen any errant links any where now... And those 2 links are fixed now :~ go figure.... >> You are right though - that attribute was missing the trailing slash - >> but it doesnt seem to have affected anything else though... >> > > > If it truly doesn't affect other links, I don't understand why. There > are many links that are obtained via the list's GetScriptURL method > which is how the incorrect links you mentioned are obtained. > > seriously - it hasnt changed anything other than those 2 links... This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. From forsythe at chem.iupui.edu Wed Jan 3 14:06:41 2007 From: forsythe at chem.iupui.edu (Kelsey Forsythe) Date: Wed, 3 Jan 2007 08:06:41 -0500 Subject: [Mailman-Users] migrating mailman lists Message-ID: Hello, I've recently moved to a new server. It is an Xserve G5 running 10.4.3 OSX. I'd like to migrate the mailman lists from the old server (Xserve G4). Does anyone have experience migrating lists? If so, please let me know what procedure you followed. Thanks, Kelsey From ptomblin at xcski.com Wed Jan 3 14:52:48 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Wed, 3 Jan 2007 08:52:48 -0500 Subject: [Mailman-Users] migrating mailman lists In-Reply-To: References: Message-ID: <20070103135248.GA25837@allhats.xcski.com> Quoting Kelsey Forsythe (forsythe at chem.iupui.edu): > I've recently moved to a new server. It is an Xserve G5 running > 10.4.3 OSX. > I'd like to migrate the mailman lists from the old server (Xserve G4). > > Does anyone have experience migrating lists? > If so, please let me know what procedure you followed. If you have command line access to both servers, it's dead easy. I've done it twice. Here is the procedure I followed. Note that your file paths may differ because OS X does strange things: 1. Copied all of /var/lib/mailman/lists/ from the old server to the new one. 2. Fixed the permissions with "chown -R list.list /var/lib/mailman/lists/" 3. Fixed the urls for the new one with "withlist -l -r fix_url [listname]" for each list. (Only necessary if the new server has a different domain name than the old one - one time I was moving from xcski.com to list.xcski.com and the other time I was keeping the same list.xcski.com url.) 4. Copied all /var/lib/mailman/archives/private/*mbox/*mbox to the new server. 5. Fixed the permissions with "chown -R list.list /var/lib/mailman/archives/private" 6. Regenerated the archives using "/var/lib/mailman/bin/arch [listname]" for each list. Note that if your archives are big, this process can consume all the memory in your system and then some, so you may have to split the mbox files up and regenerate the list archives in peices or use the "--start" and "--end" options to arch. -- Paul Tomblin http://blog.xcski.com/ We'll burn that bridge when we come to it. From raygeeknyc at gmail.com Wed Jan 3 16:54:40 2007 From: raygeeknyc at gmail.com (Raymond Blum) Date: Wed, 3 Jan 2007 10:54:40 -0500 Subject: [Mailman-Users] preserving original lists' subject prefix In-Reply-To: References: Message-ID: Hi Mark I'm glad that to hear that it should be doing the sensible thing. The subject prefix for each list is [list1] and [list2] It's mailman version 2.1.5 Unfortunately I am a list owner but not a sys admin for the machine running mailman so I don't have any access to check the mailman installation for the .py file, is there a way to get that info from mailman? Thanks, ---Raymond On 1/2/07, Mark Sapiro wrote: > > Raymond Blum wrote: > > > I have a situation where I need to preserve the "history" or chain of > >subscriptions that a message has passed through on its way to the > >recipients. For example if user1 subscribes to list1 and list1 is > >subscribed to list2, I wish messages sent to list2 to have something like > >this in the subject > > > >[List1] [List2] here is a message for you > > > >It looks like mailman is removing [List2], leaving me with [List1] ... as > >the subject. If empty out the subject prefix for List1, then neither > >appears. > > > It should work as you expect. > > What mailman version is this? > > What is the value of subject_prefix for each of the lists? > > What is the setting in Defaults.py-mm_cfg.py for OLD_STYLE_PREFIXING? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Wow, as busy as I am I took to the time to write this. I must really like you! From msapiro at value.net Wed Jan 3 17:45:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 08:45:49 -0800 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: <459B3558.6020602@kromestudios.com> Message-ID: Spyro Polymiadis wrote: > >mmmm nah they are all fine... - i havent seen any errant links any where >now... >And those 2 links are fixed now :~ go figure.... You are correct. The create script set the list's web_page_url attribute using the web host and DEFAULT_URL_PATTERN. Thus it had no trailing slash and those two links on the create response page were missing the slash. But, the next time the list is loaded, some attributes are 'sanity checked', and this process adds the missing trailing slash to web_page_url, and it is correct from then on. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jerry at sandiego.edu Wed Jan 3 17:51:47 2007 From: jerry at sandiego.edu (Jerold Stratton) Date: Wed, 3 Jan 2007 08:51:47 -0800 Subject: [Mailman-Users] migrating mailman lists In-Reply-To: References: Message-ID: On Jan 3, 2007, at 5:06 AM, Kelsey Forsythe wrote: > I've recently moved to a new server. It is an Xserve G5 running > 10.4.3 OSX. > I'd like to migrate the mailman lists from the old server (Xserve G4). > > Does anyone have experience migrating lists? > If so, please let me know what procedure you followed. My experience was similar to Paul's: dead easy. My steps were slightly different; and I had been running the new Xserve with some test lists before copying the files over. These are my notes for the final switchover: on old lists mailmanctl stop on old list server, copy files to personal workstation: sudo rsync -a --delete -e ssh /home/mailman/lists user at workstation:Desktop/lists/ --progress sudo rsync -a --delete -e ssh /home/mailman/data user at workstation:Desktop/lists/ --progress sudo rsync -a --delete -e ssh /home/mailman/archives user at workstation:Desktop/lists/ --progress shutdown old lists hardware on new lists: --copy from personal workstation to staging area sudo rsync -a --delete -e ssh user at workstation:Desktop/lists/lists / var/mailman/new --progress sudo rsync -a --delete -e ssh user at workstation:Desktop/lists/data / var/mailman/new --progress sudo rsync -a --delete -e ssh user at workstation:Desktop/lists/ archives /var/mailman/new --progress --fix staging area cd /var/mailman/new rm -r lists/mailman rm data/adm.pw data/aliases data/aliases.db data/master-qrunner.pid data/sitelist.cfg sudo chown -R mailman:mailman /var/mailman/new --fix symbolic links in public directory cd /var/mailman/new/archives/public sudo ~/bin/fixlinks * --move from staging area to live sudo scp -pr /var/mailman/lists /var/mailman/data /var/mailman/ archives /Users/cole/mailmanvar sudo mv /var/mailman/new/lists/* /var/mailman/lists sudo mv /var/mailman/new/data/* /var/mailman/data sudo mv /var/mailman/new/archives/* /var/mailman/archives --add alias lines to /var/mailman/data/aliases --note that I had kept a list of lists in FileMaker, along with the necessary aliases for each --this is what I copied cd sudo scp -p user at workstation:Desktop/lists/list_aliases . sudo vi /var/mailman/data/aliases :r list_aliases :wq sudo /usr/sbin/postalias /var/mailman/data/aliases --update data files sudo /usr/share/mailman/bin/update sudo bin/withlist -l -a -r fix_url -- -v --add IP address (change from test-ip to live-ip) sudo changeip - test-ip live-ip sudo networksetup -setmanual "Built-in Ethernet 1" live-ip netmask gateway sudo networksetup -getinfo "Built-in Ethernet 1" stop and start postfix from server admin? The fixlinks script referenced above, because after the copy the public alias links didn't work, as they were pointing to the wrong directory: === #!/usr/bin/perl $privatebase = "/var/mailman/archives/private"; while ($item = shift) { $reallink = "$privatebase/$item"; print "Changing $item to $reallink\n"; unlink($item); symlink($reallink, $item); } === Jerry jerry at sandiego.edu http://home.sandiego.edu/~jerry/ Maher 190/x8773 -- "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at and repair."--Douglas Adams (Mostly Harmless) From msapiro at value.net Wed Jan 3 20:11:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 11:11:54 -0800 Subject: [Mailman-Users] FW: Problems with spam In-Reply-To: <5B153C49A5F0AB4EAE9D57E0DD7D894420EFF7@caster.nwk-campus.rutgers.edu> Message-ID: Lenore Pearson wrote: > >I am in charge of the 'stud_affrs_roundtable at email.rutgers.edu' list >serv on the Rutgers Newark campus. I am receiving spam on the list >serve and it is not being approved by me. Please contact me and let me >know what actions can be taken to stop the spam and whether or not I >need to change the email server address to alleviate the situation. > >I look forward to hearing from you as soon as possible, as this matter >is very urgent. The >'stud_affrs_roundtable at email.rutgers.edu' listserv contacts high level >administrators within Rutgers University and they will not trust the >server if they are constantly bombarded with spam. While this is in some ways a security issue, it will be better if any follow-ups are addressed to mailman-users at python.org and not to mailman-security at python.org. First of all, what kind of list is this? Is it a discussion list where all members are allowed to post or an announcement list where only one or a few people post? If the latter, see for suggestions on configuring such a list and for a further discussion on 'spoof proofing'. If it is a discussion list, make sure only list members are allowed to post. On the web admin interface, Privacy options...->Sender filters->generic_nonmember_action should be discard or possibly reject or hold, but not accept. In any case, it is best if your own email server administrators at Rutgers install some spam filtering ahead of Mailman so the spam doesn't reach Mailman in the first place. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 3 22:14:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 13:14:02 -0800 Subject: [Mailman-Users] preserving original lists' subject prefix In-Reply-To: Message-ID: Raymond Blum wrote: > The >subject prefix for each list is >[list1] and [list2] >It's mailman version 2.1.5 >Unfortunately I am a list owner but not a sys admin for the machine running >mailman so I don't have any access to check the mailman installation for the >.py file, is there a way to get that info from mailman? The OLD_STYLE_PREFIXING setting was new in 2.1.6, so it doesnt't apply in your case. I am unable to explain or understand what might be happening in your case unless the machine is running some package version of Mailman which is modified from the base 2.1.5. I even ran a test on a 2.1.5 installation and it worked as I expected with both prefixes in the subject and both list's footers added to the post. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From manlio_perillo at libero.it Wed Jan 3 22:08:28 2007 From: manlio_perillo at libero.it (Manlio Perillo) Date: Wed, 03 Jan 2007 22:08:28 +0100 Subject: [Mailman-Users] using mailman for newsletter Message-ID: <459C1B4C.8060701@libero.it> Hi. Is it possible to use Mailman for sending newsletter (where each user should receive a personalized version of the email, using a template)? Thanks Manlio Perillo From msapiro at value.net Wed Jan 3 22:37:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 13:37:54 -0800 Subject: [Mailman-Users] using mailman for newsletter In-Reply-To: <459C1B4C.8060701@libero.it> Message-ID: Manlio Perillo wrote: > >Is it possible to use Mailman for sending newsletter (where each user >should receive a personalized version of the email, using a template)? It is possible to 'fully personalize' a Mailman list which will put the recipient's address in the To: header of the message sent to that recipient and which allows some personal information to be inserted in the list's msg_header and msg_footer, but Mailman doesn't support substituting information into a template or otherwise personalizing the actual message body. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From manlio_perillo at libero.it Wed Jan 3 22:47:25 2007 From: manlio_perillo at libero.it (Manlio Perillo) Date: Wed, 03 Jan 2007 22:47:25 +0100 Subject: [Mailman-Users] using mailman for newsletter In-Reply-To: References: Message-ID: <459C246D.8000409@libero.it> Mark Sapiro ha scritto: > Manlio Perillo wrote: >> Is it possible to use Mailman for sending newsletter (where each user >> should receive a personalized version of the email, using a template)? > > > It is possible to 'fully personalize' a Mailman list which will put the > recipient's address in the To: header of the message sent to that > recipient and which allows some personal information to be inserted in > the list's msg_header and msg_footer, What params can be specified with msg_header and footer? Regards Manlio Perillo From msapiro at value.net Wed Jan 3 23:08:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 14:08:57 -0800 Subject: [Mailman-Users] using mailman for newsletter In-Reply-To: <459C246D.8000409@libero.it> Message-ID: Manlio Perillo wrote: > >What params can be specified with msg_header and footer? >From the help for msg_header: Text prepended to the top of every immediately-delivery message. This text can include Python format strings which are resolved against list attributes. The list of substitutions allowed are: * real_name - The "pretty" name of the list; usually the list name with capitalization. * list_name - The name by which the list is identified in URLs, where case is significant. * host_name - The fully qualified domain name that the list server runs on. * web_page_url - The base URL for Mailman. This can be appended with, e.g. listinfo/%(list_name)s to yield the listinfo page for the mailing list. * description - The brief description of the mailing list. * info - The full description of the mailing list. * cgiext - The extension added to CGI scripts. When personalization is enabled for this list, additional substitution variables are allowed in your headers and footers: * user_address - The address of the user, coerced to lower case. * user_delivered_to - The case-preserved address that the user is subscribed with. * user_password - The user's password. * user_name - The user's full name. * user_optionsurl - The url to the user's option page. The same substitutions apply to msg_footer. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jmwhitco at samford.edu Wed Jan 3 23:33:06 2007 From: jmwhitco at samford.edu (Whitcomb, Jeff) Date: Wed, 3 Jan 2007 16:33:06 -0600 Subject: [Mailman-Users] (no subject) Message-ID: <821AB4E5068CAB43A2539D4DD81F38E303CD3D2B@SAMFORDMAIL.ad.samford.edu> When someone sends an email with a read receipt request to a list that I own, I get a lot of uncaught bounce notifications (I have attached one for reference). I am wondering if there is any way I can stop getting all these Read Receipt messages when people send an email to a Mailman list, without turning off bounce processing all together. I tried just filtering them in Outlook, but you can't filter on an attachment name. I do currently have all of the bounce notifications going to a folder, but would like to either stop getting these particular ones, or be able to further filter them into another folder. I am on Mailman v. 2.1.6 and Exchange 2003 with Outlook 2003. Any help would be appreciated. Thanks, Jeff Whitcomb, MCP Technology Services Manager Cumberland School of Law - Samford University 205-726-4662 From spyropolymiadis at kromestudios.com Thu Jan 4 00:17:52 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Thu, 04 Jan 2007 09:47:52 +1030 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: References: Message-ID: <459C39A0.8020605@kromestudios.com> Mark Sapiro wrote: > You are correct. > The create script set the list's web_page_url attribute using the web > host and DEFAULT_URL_PATTERN. Thus it had no trailing slash and those > two links on the create response page were missing the slash. > > But, the next time the list is loaded, some attributes are 'sanity > checked', and this process adds the missing trailing slash to > web_page_url, and it is correct from then on Ah ok - so in actual fact all the links theoretically should have been missing that slash - but the "sanity check" added them in.... is there a way to get the sanity checker to "auto fix" those 2 links as well for the future? if someone forgets the slash again? - other than that - everything else seems to work fine still ;) Cheers Spyro This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. From msapiro at value.net Thu Jan 4 01:13:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 16:13:49 -0800 Subject: [Mailman-Users] Incorrect links after list creation In-Reply-To: <459C39A0.8020605@kromestudios.com> Message-ID: Spyro Polymiadis wrote: > >Ah ok - so in actual fact all the links theoretically should have been >missing that slash - but the "sanity check" added them in.... is there a >way to get the sanity checker to "auto fix" those 2 links as well for >the future? if someone forgets the slash again? - other than that - >everything else seems to work fine still ;) Basically what happens is the web list create script sets the list's web_page_url attribute by interpolating the web host name into DEFAULT_URL_PATTERN, and it does no checking of the result for a trailing slash. Thus, the links that it creates for its results page are missing a slash if DEFAULT_URL_PATTERN has no trailing slash. Then, the MailList module, adds the trailing slash to the list's web_page_url attribute the next time the list is accessed so the absence of the trailing slash in DEFAULT_URL_PATTERN ultimately causes no harm, but it does cause the two links on the list create results page to be wrong. If you want the two links on the create results page to be correct in the absence of the trailing slash in DEFAULT_URL_PATTERN, you have to add the same "make sure that web_page_url ends in a slash" code that's in Mailman/MailList.py to Mailman/Cgi/create.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 4 01:37:44 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 16:37:44 -0800 Subject: [Mailman-Users] Read Receipt uncaught bounces was: (no subject) In-Reply-To: <821AB4E5068CAB43A2539D4DD81F38E303CD3D2B@SAMFORDMAIL.ad.samford.edu> Message-ID: Whitcomb, Jeff wrote: > >When someone sends an email with a read receipt request to a list that I >own, I get a lot of uncaught bounce notifications (I have attached one >for reference). And the list's content filtering removed it. >I am wondering if there is any way I can stop getting >all these Read Receipt messages when people send an email to a Mailman >list, without turning off bounce processing all together. This is just one more reason why "Read Receipts" are bad. If possible, train your users not to request receipts for list mail. What do they think they are going to get anyway? It would be fairly simple to implement header_filter_rules for your list (admin->Privacy options->Spam filters->header_filter_rules) that would reject any post that asked for a receipt. You could also not send unrecognized bounces to the list owner. Automated bounce processing will still be done, but unrecognized bounces will be discarded. See admin->Bounce processing->bounce_unrecognized_goes_to_list_owner. >I tried just >filtering them in Outlook, but you can't filter on an attachment name. >I do currently have all of the bounce notifications going to a folder, >but would like to either stop getting these particular ones, or be able >to further filter them into another folder. What happens is at least some of your list subscribers (via their MUAs) are returning receipts to the envelope sender. This may or may not be correct. I don't know how these things are supposed to work. In an OOB Mailman, you can't differentiate these 'unrecognized bounces' from any other unrecognized bounces I think your best solution if you have access to the Mailman installation and you don't want to train the users is to implement a custom handler (see ) to remove all headers that request receipts or acknowledgements from the list posts. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From tkikuchi at is.kochi-u.ac.jp Thu Jan 4 01:51:12 2007 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu, 04 Jan 2007 09:51:12 +0900 Subject: [Mailman-Users] Read Receipt uncaught bounces was: (no subject) In-Reply-To: References: Message-ID: <459C4F80.2030700@is.kochi-u.ac.jp> Mark Sapiro wrote: > Whitcomb, Jeff wrote: >> I am wondering if there is any way I can stop getting >> all these Read Receipt messages when people send an email to a Mailman >> list, without turning off bounce processing all together. > > > This is just one more reason why "Read Receipts" are bad. > What exactly is the header name? We already strip these headers by Mailman/Handlers/Cleanse.py: # Some headers can be used to fish for membership del msg['return-receipt-to'] del msg['disposition-notification-to'] del msg['x-confirm-reading-to'] It should not be difficult to add one or more in the next release. -- Tokio Kikuchi, tkikuchi at is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From msapiro at value.net Thu Jan 4 01:54:15 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 3 Jan 2007 16:54:15 -0800 Subject: [Mailman-Users] Read Receipt uncaught bounces was: (no subject) In-Reply-To: Message-ID: Mark Sapiro wrote: > >I think your best solution if you have access to the Mailman >installation and you don't want to train the users is to implement a >custom handler (see >) >to remove all headers that request receipts or acknowledgements from >the list posts. I just looked at the existing Mailman/Handlers/Cleanse.py handler with the thought of creating an example of a custom handler to remove receipt requests, and I was reminded that we already try to remove any headers that request this. This is what we currently do. # Some headers can be used to fish for membership del msg['return-receipt-to'] del msg['disposition-notification-to'] del msg['x-confirm-reading-to'] # Pegasus mail uses this one... sigh del msg['x-pmrqc'] So the question is, what header(s) are your users using to request receipts that aren't among those above? Tell us what they are, and we will remove them effective with Mailman 2.1.10. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jmwhitco at samford.edu Thu Jan 4 14:57:15 2007 From: jmwhitco at samford.edu (Whitcomb, Jeff) Date: Thu, 4 Jan 2007 07:57:15 -0600 Subject: [Mailman-Users] Question about Sender Filters Message-ID: <821AB4E5068CAB43A2539D4DD81F38E303CD3D53@SAMFORDMAIL.ad.samford.edu> I have a non-member filter set under "accept these nonmembers" to ^.*@ >. This accepts all messages from my domain, then I have a reject message set in "nonmember rejection notice". I got an email this morning from a company who is getting bombarded with these rejection messages because one of their addresses is being spoofed and directed at my list. I am curious if I put this company's domain name (in the same format as above) in to the "discard these members" field, will it get processed since it does not meet the "accept these nonmembers" filter, or will anything in filters subsequent to the accept filter be ignored? I hope I explained this well enough and will try to clarify if needs be. Thanks, Jeff Whitcomb, MCP Technology Services Manager Cumberland School of Law - Samford University 205-726-4662 From pdbogen at gmail.com Thu Jan 4 16:24:35 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 4 Jan 2007 09:24:35 -0600 Subject: [Mailman-Users] Question about Sender Filters In-Reply-To: <821AB4E5068CAB43A2539D4DD81F38E303CD3D53@SAMFORDMAIL.ad.samford.edu> References: <821AB4E5068CAB43A2539D4DD81F38E303CD3D53@SAMFORDMAIL.ad.samford.edu> Message-ID: <6fbe3da00701040724p3279f165n36af97281abff497@mail.gmail.com> On 1/4/07, Whitcomb, Jeff wrote: > and directed at my list. I am curious if I put this company's domain > name (in the same format as above) in to the "discard these members" > field, will it get processed since it does not meet the "accept these > nonmembers" filter, or will anything in filters subsequent to the accept > filter be ignored? Assuming you're talking about discard_these_NONmembers, then yes, adding the pattern in question to that filter will take effect if the address isn't matched by other filters. (The filters are applied in some order that I'm feeling too lazy to discover, right now.) -- - Patrick Bogen From msapiro at value.net Thu Jan 4 16:46:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 4 Jan 2007 07:46:35 -0800 Subject: [Mailman-Users] Question about Sender Filters In-Reply-To: <6fbe3da00701040724p3279f165n36af97281abff497@mail.gmail.com> Message-ID: Patrick Bogen wrote: > >Assuming you're talking about discard_these_NONmembers, then yes, >adding the pattern in question to that filter will take effect if the >address isn't matched by other filters. (The filters are applied in >some order that I'm feeling too lazy to discover, right now.) The filters/actions are tested in the order they appear on the web page (accept, hold, reject, discard). The first one that matches is the action taken. If none of the four match, then the generic action is taken. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 4 19:00:53 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 4 Jan 2007 10:00:53 -0800 Subject: [Mailman-Users] OS X Permissions Help. In-Reply-To: <329E796A-7F41-4B32-8472-B5FE51BFF431@citadel97.com> Message-ID: Chris Florio wrote: > >As the instructions said, I configured using: > >sudo ./configure --prefix=/Applications/mailman --with-cgi-gid=www -- >with-mail-gid=mailman > > >Using the instructions from the list I found, I am getting this error >posting to a list I created: > >.. > >The Postfix program > >: Command died with status 2: > "/Applications/mailman/mail/mailman post alumni". Command >output: Group > mismatch error. Mailman expected the mail wrapper script to be >executed as > group "mailman", but the system's mail server executed the mail >script as > group "www". Try tweaking the mail server to run the script as >group > "mailman", or re-run configure, providing the command line option > `--with-mail-gid=www'. > > >.. > >So, I tried again using: > >sudo ./configure --prefix=/Applications/mailman --with-cgi-gid=www -- >with-mail-gid=www > >And then I get this error: > > The Postfix program > >: Command died with status 2: > "/Applications/mailman/mail/mailman post alumni". Command >output: Group > mismatch error. Mailman expected the mail wrapper script to be >executed as > group "www", but the system's mail server executed the mail >script as group > "mailman". Try tweaking the mail server to run the script as >group "www", > or re-run configure, providing the command line option > `--with-mail-gid=mailman'. I suspect you made another change, either directly or indirectly in the group ownership of the aliases file from which Postfix gets its Mailman aliases. Postfix will run the pipe to the Mailman mail wrapper as the user/group that owns the aliases* files from which the pipe alias came. If Mailman's Postfix integration (MTA = 'Postfix') is in use, the aliases will be in Mailman's data/aliases and data/aliases.db and these file will be group owned by 'mailman'. Thus, the first configuration is correct as long as the aliases* files are owned by the 'mailman' group which they need to be for the Postfix integration to work. Also see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 4 19:16:22 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 4 Jan 2007 10:16:22 -0800 Subject: [Mailman-Users] BoundaryError: No terminating boundary and notrailing empty line In-Reply-To: <4591B7FE.8020003@enabled.com> Message-ID: Noah wrote: > >any clues why mailman keeps dumping the following error trace in >/usr/local/mailman/logs/error ? Happens about every hour or so or >sometimes minutes apart. > > >--- snip --- > >Dec 26 08:27:28 2006 (75889) Ignoring unparseable message: >1166121349.6141329+c811d30798575d4ca57b9a0552a1d394a95c8ff1 >Dec 26 08:27:28 2006 (75889) Uncaught runner exception: No terminating >boundary and no trailing empty line The 'ignoring' message and the associated exception and traceback occur because a 'defective' message has been sent to a Mailman address (a list posting address or a list -request, -bounces, etc address) and has been queued in the appropriate queue. When the appropriate runner attempts to dequeue the message for processing, the dequeueing mechanism attempts to parse the message into a Python email Message object and gets the exception because the message has an unparseable MIME structure. Such messages are almost certainly unwanted spam in any case. This is what we say about it in the code # It's possible to get here if the message was stored in the # pickle in plain text, and the metadata had a _parsemsg key # that was true, /and/ if the message had some bogosity in # it. It's almost always going to be spam or bounced spam. # There's not much we can do (and we didn't even get the # metadata, so just log the exception and continue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 4 19:26:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 4 Jan 2007 10:26:12 -0800 Subject: [Mailman-Users] list names and virtual domains In-Reply-To: <45938D8E.5070001@gmx.net> Message-ID: ubw at gmx wrote: > >on a machine running many different virtual hosts, each time that a new >list is created with mailman, mailman adds to the list name the full >virtual domain name. > >I mean: if I create a list called > TEST at myhost.org >in mailman it becomes > TEST_MYHOST.ORG at myhost.org > >and I feel that this situation is quite odd. I am guessing this is a cPanel Mailman. This is the technique that cPanel and perhaps others use to allow lists of the same name in different virtual domains. See -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From james.king at familycampers.com Thu Jan 4 19:10:25 2007 From: james.king at familycampers.com (james.king at familycampers.com) Date: Thu, 4 Jan 2007 13:10:25 -0500 Subject: [Mailman-Users] Messages Not being Distributed Message-ID: <380-22007144181025948@M2W026.mail2web.com> I have 2 Lists setup under the MailMan software offered by HostForWeb.Com Account. One have 36 Email Accounts in the Group. Randomly, some messages other members send to the address does not get distributed. But I can look in the Archive and the message shows there. Is there someway to Re-Issue the Email or Resend it? I have 3 addresses on the system, and know I am not getting them in either accounts. Appreciate the help or guidance on how to fix this Problem. James King -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . From msapiro at value.net Thu Jan 4 21:11:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 4 Jan 2007 12:11:57 -0800 Subject: [Mailman-Users] Messages Not being Distributed In-Reply-To: <380-22007144181025948@M2W026.mail2web.com> Message-ID: james.king at familycampers.com wrote: >I have 2 Lists setup under the MailMan software offered by HostForWeb.Com >Account. One have 36 Email Accounts in the Group. Randomly, some messages >other members send to the address does not get distributed. But I can look >in the Archive and the message shows there. Are you saying you have missing emails with one of the two lists, and no missing emails with the other list? >Is there someway to Re-Issue >the Email or Resend it? I have 3 addresses on the system, and know I am not >getting them in either accounts. There may or may not be a way to reprocess a message depending on why it is missing. If it wasn't sent at all due to a Mailman processing error, it was probably put in Mailman's shunt queue and possibly can be reprocessed if the underlying problem is fixed. OTOH, if it was sent by Mailman, but not delivered for other reasons, Mailman can't resend it. To diagnose this problem further, you need access to the Mailman and MTA logs on the server. Depending on what kind of hosting you have with HostForWeb.Com, this may be something that you can do or something you would have to take up with HostForWeb.Com. Also, judging from the HostForWeb.Com web site, cPanel may be involved which adds another layer of indirection. See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jesse.solidot at gmail.com Fri Jan 5 17:18:28 2007 From: jesse.solidot at gmail.com (Jesse Lee) Date: Sat, 6 Jan 2007 00:18:28 +0800 Subject: [Mailman-Users] Mailman Backup In-Reply-To: <657728f60701050811j1e2c35a1wfcd0134ccc0e416@mail.gmail.com> References: <657728f60701050811j1e2c35a1wfcd0134ccc0e416@mail.gmail.com> Message-ID: <657728f60701050818g57b76191mbedf1d845bf94397@mail.gmail.com> Hello, I need to transfer mailman to another server, But not sure how to make a complete backup of mailman. I've searched web and read some articles, but still confused. Anyone can give a clear method of mailman backup? Step by step is great. Thanks in advance. (Sorry for my English.) Jesse From msapiro at value.net Fri Jan 5 19:04:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 5 Jan 2007 10:04:39 -0800 Subject: [Mailman-Users] Mailman Backup In-Reply-To: <657728f60701050818g57b76191mbedf1d845bf94397@mail.gmail.com> Message-ID: Jesse Lee wrote: > >I need to transfer mailman to another server, But not sure how to make a >complete backup of mailman. >I've searched web and read some articles, but still confused. Anyone can >give a clear method of mailman backup? Step by step is great. See and the posts to whih it refers. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at python.org Fri Jan 5 22:34:47 2007 From: barry at python.org (Barry Warsaw) Date: Fri, 5 Jan 2007 16:34:47 -0500 Subject: [Mailman-Users] Mailman on Mac OS X Server 10.3: Outgoing messagesstuck in qrunner/in folder In-Reply-To: References: <3F10FCB6-8E67-4A63-87C7-86132D86016E@cprp.ca> <3B65E2E1-CC0F-40F5-87F1-708CD5FF0A1A@cprp.ca> Message-ID: <95660757-86C7-41B3-8094-8345ED71B430@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Dec 16, 2006, at 1:05 PM, Brad Knowles wrote: > Now, how much you might want to take from this and incorporate into > the pages at list.org/gnu.org, I would say that would be up to you. > If there are any other changes you'd like made to the listinfo > pages, you're welcome to let me know and I'll be glad to make those > for you -- if you like. Brad, sorry for the delay in responding. Thanks for all the updates here. As far as what I'll add to the static web pages, well, probably not much. I really want to move more content into the wiki and less in the static pages, so as that happens I'll definitely keep this info in mind. Thanks! - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRZ7Ee3EjvBPtnXfVAQJjjwP/VI7BIUbFwqbf8AyRUyXc20vnEJJUc1kB 1oHBPIrJhjr2AuyNpxQpD4RwwIWdd7ENNnzIqv1/3cP04wXZOSufevfKFZhPDMOd 5GNkGA5VZ58xAcyMkVlvd7n7jThKSHsSXwPdBSa4M3kj/z2o2F37tdEqDXzCRE5g eAmJC44xszo= =O0k8 -----END PGP SIGNATURE----- From fcusack at fcusack.com Sat Jan 6 18:16:40 2007 From: fcusack at fcusack.com (Frank Cusack) Date: Sat, 06 Jan 2007 09:16:40 -0800 Subject: [Mailman-Users] Mailman 2.1.[56] installation problem w/ KoreanCodecs Message-ID: <0E6019A140464809258A0EE7@sucksless.local> Hi, found this message back from 2005/11/28: > "make install" dies with > (cd ./$p ; umask 02 ; PYTHONPATH=/home/mailman/2.1.5/pythonlib > /usr/local/bin/python setup.py --quiet install --install-lib > /home/mailman/2.1.5/pythonlib --install-purelib > /home/mailman/2.1.5/pythonlib --install-data > /home/mailman/2.1.5/pythonlib); \ > done > /usr/local/lib/python2.4/distutils/dist.py:222: UserWarning: 'licence' > distribution option is deprecated; use 'license' > warnings.warn(msg) > src/hangul.c:33: error: syntax error before numeric constant > src/hangul.c:34: error: syntax error before numeric constant > error: command 'gcc' failed with exit status 1 > *** Error code 1 > > This happens with either 2.1.5 or 2.1.6, various versions of > Python as well. It's on Solaris 10 with Sun's bundled gcc > (/usr/sfw/bin/gcc). > > Rather furstrating. Is there an easy way to just skip these > codecs i have no use for? I came across the same problem with mailman 2.1.9 and thought I'd share my solution. This is due to a bug in Solaris 10 headers. includes which pollutes the macro "namespace" (if you will) with definitions for x86 registers, like GS and SS. This is only on Solaris/x86; Solaris/sparc doesn't have this error. Before running configure, I do this: # work around solaris bug # http://forum.java.sun.com/thread.jspa?threadID=5074551 gtar zxf misc/KoreanCodecs-2.0.5.tar.gz perl -i -pe 's/GS, N/MYGS, N/; s/CODE.GS./CODE(MYGS)/; s/SS, N/MYSS, N/; s/CODE.SS./CODE(MYSS)/;' \ KoreanCodecs-2.0.5/src/hangul.c gtar zcf misc/KoreanCodecs-2.0.5.tar.gz KoreanCodecs-2.0.5 The tarball has to be unpacked and repacked because 'make' unpacks it. If you unpack it and patch it, without repacking it, 'make' will overwrite your changes when it unpacks it again. -frank From fcusack at fcusack.com Sun Jan 7 03:07:56 2007 From: fcusack at fcusack.com (Frank Cusack) Date: Sat, 06 Jan 2007 18:07:56 -0800 Subject: [Mailman-Users] Defaults.py doco bug Message-ID: # If you set MTA='Postfix', then you also want to set the following variable, # depending on whether you're using virtual domains in Postfix, and which # style of virtual domain you're using. Set this flag to false if you're not # using virtual domains in Postfix, ... Actually it has to be an empty list, not false (or False). I wondered if that was wrong since false wasn't capitalized, but I decided it must be a typo and tried False. Which of course doesn't work. -frank From msapiro at value.net Sun Jan 7 03:45:45 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 6 Jan 2007 18:45:45 -0800 Subject: [Mailman-Users] Defaults.py doco bug In-Reply-To: Message-ID: Frank Cusack wrote: ># style of virtual domain you're using. Set this flag to false if you're >not ># using virtual domains in Postfix, ... > >Actually it has to be an empty list, not false (or False). Thanks for the report. I have changed it in Subversion to say "Set this to the empty list ..." -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From williamstdd at yahoo.com Sun Jan 7 06:27:24 2007 From: williamstdd at yahoo.com (Todd Williams) Date: Sat, 6 Jan 2007 21:27:24 -0800 (PST) Subject: [Mailman-Users] -request "who" message not returning list members Message-ID: <800054.12466.qm@web34815.mail.mud.yahoo.com> When I send a "who " mail message to list-request at ... I only recieve back one or two member names and not the entire list. I have six lists (all hosted by my ISP) five are "production" lists and one is test. The test (only six people) gives me the entire list, but the "production" lists (~100 people each) do not. Is there some setting I am missing? Todd __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From williamstdd at yahoo.com Sun Jan 7 08:37:23 2007 From: williamstdd at yahoo.com (Todd Williams) Date: Sat, 6 Jan 2007 23:37:23 -0800 (PST) Subject: [Mailman-Users] -request "who" message not returning list members Message-ID: <558714.24852.qm@web34808.mail.mud.yahoo.com> Never mind I finally found a reference in one of Mr Shapiro's posts... The Hide Address check box. I would have never figured that one out. Sorry for the clutter. Todd Todd Williams wrote: When I send a "who " mail message to list-request at ... I only recieve back one or two member names and not the entire list. I have six lists (all hosted by my ISP) five are "production" lists and one is test. The test (only six people) gives me the entire list, but the "production" lists (~100 people each) do not. Is there some setting I am missing? Todd __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From manuel at escapade.ch Sun Jan 7 10:27:44 2007 From: manuel at escapade.ch (Manuel Goepfert) Date: Sun, 7 Jan 2007 10:27:44 +0100 Subject: [Mailman-Users] Delete messages too big Message-ID: <00eb01c7323e$16eed320$6310a8c0@newgauche> Hello, I'm currently trying to find a way to automatically delete messages that are oversized. The max since of messages is defined and I get the approbation e-mail stating that the message is too big. I want to remove this message and directly erase the mail sent to the list without going to the admin page and delete myself the message. Is there a way to do so ? Thanks for your help Manuel From msapiro at value.net Sun Jan 7 19:01:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 7 Jan 2007 10:01:02 -0800 Subject: [Mailman-Users] Delete messages too big In-Reply-To: <00eb01c7323e$16eed320$6310a8c0@newgauche> Message-ID: Manuel Goepfert wrote: > >The max since of messages is defined and I get the approbation e-mail >stating that the message is too big. >I want to remove this message and directly erase the mail sent to the list >without going to the admin page and delete myself the message. > >Is there a way to do so ? Only by modifying Mailman/Handlers/Hold.py or creating a custom handler . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From manuel at escapade.ch Sun Jan 7 19:06:31 2007 From: manuel at escapade.ch (Manuel Goepfert) Date: Sun, 7 Jan 2007 19:06:31 +0100 Subject: [Mailman-Users] Delete messages too big In-Reply-To: Message-ID: <000001c73286$8fa30320$6310a8c0@newgauche> Mark Sapiro wrote: >>I want to remove this message and directly erase the mail sent to the >>list without going to the admin page and delete myself the message. >> >>Is there a way to do so ? >Only by modifying Mailman/Handlers/Hold.py or creating a custom handler . Thanks Mark, I will have a look at that one. Manuel From fcusack at fcusack.com Mon Jan 8 01:14:45 2007 From: fcusack at fcusack.com (Frank Cusack) Date: Sun, 07 Jan 2007 16:14:45 -0800 Subject: [Mailman-Users] mhonarc and non-world-readable archives problem Message-ID: I've built mailman-2.1.9 with the mhonarc patch (http://www.openinfo.co.uk/mm/patches/mhonarc/index.html) and it works great. I am running on Solaris 10 with python 2.5. The problem I have is that the list archives are not created world-readable. [root at mailman:/var/mailman/archives/public]# ls -l total 1 lrwxrwxrwx 1 webservd mailman 34 Jan 7 15:32 test -> /var/mailman/archives/private/test [root at mailman:/var/mailman/archives/public]# ls -l test/ total 21 drwxrwsr-x 2 mailman mailman 9 Jan 7 15:35 2007-January -rw-rw-r-- 1 mailman mailman 1537 Jan 7 15:35 2007-January.txt drwxrws--- 2 mailman mailman 3 Jan 7 15:35 htdig -rw-rw-r-- 1 webservd mailman 2640 Jan 7 15:35 index.html -rw-rw---- 1 mailman mailman 566 Jan 7 15:35 pipermail.pck [root at mailman:/var/mailman/archives/public]# ls -l test//2007-January total 38 -rw-rw---- 1 mailman mailman 6851 Jan 7 15:35 .mhonarc.db -rw-rw---- 1 mailman mailman 1177 Jan 7 15:35 author.html -rw-rw---- 1 mailman mailman 1191 Jan 7 15:35 date.html lrwxrwxrwx 1 mailman mailman 11 Jan 7 15:35 index.html -> thread.html -rw-rw---- 1 mailman mailman 2402 Jan 7 15:35 msg00000.html -rw-rw---- 1 mailman mailman 1205 Jan 7 15:35 subject.html -rw-rw---- 1 mailman mailman 1145 Jan 7 15:35 thread.html [root at mailman:/var/mailman/archives/public]# In mm_cfg.py, I have MAILMAN_GROUP = 'mailman'. Now, if I set that to www then would that make these files be created with group www? Just wondering, because that doesn't actually help me. My webserver (thttpd) requires that files be world-readable in order to serve them, regardless of whether the web server actually has access permission. Also just wondering, why is public/test a symlink to ../private/test? The mailing list (and the archives) are not private. So how can I make the archives be created world-readable? thanks -frank From msapiro at value.net Mon Jan 8 02:25:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 7 Jan 2007 17:25:49 -0800 Subject: [Mailman-Users] mhonarc and non-world-readable archives problem In-Reply-To: Message-ID: Frank Cusack wrote: >I've built mailman-2.1.9 with the mhonarc patch >(http://www.openinfo.co.uk/mm/patches/mhonarc/index.html) and it works >great. I am running on Solaris 10 with python 2.5. > >The problem I have is that the list archives are not created world-readable. > >[root at mailman:/var/mailman/archives/public]# ls -l >total 1 >lrwxrwxrwx 1 webservd mailman 34 Jan 7 15:32 test -> >/var/mailman/archives/private/test >[root at mailman:/var/mailman/archives/public]# ls -l test/ >total 21 >drwxrwsr-x 2 mailman mailman 9 Jan 7 15:35 2007-January >-rw-rw-r-- 1 mailman mailman 1537 Jan 7 15:35 2007-January.txt >drwxrws--- 2 mailman mailman 3 Jan 7 15:35 htdig >-rw-rw-r-- 1 webservd mailman 2640 Jan 7 15:35 index.html >-rw-rw---- 1 mailman mailman 566 Jan 7 15:35 pipermail.pck >[root at mailman:/var/mailman/archives/public]# ls -l test//2007-January >total 38 >-rw-rw---- 1 mailman mailman 6851 Jan 7 15:35 .mhonarc.db >-rw-rw---- 1 mailman mailman 1177 Jan 7 15:35 author.html >-rw-rw---- 1 mailman mailman 1191 Jan 7 15:35 date.html >lrwxrwxrwx 1 mailman mailman 11 Jan 7 15:35 index.html -> >thread.html >-rw-rw---- 1 mailman mailman 2402 Jan 7 15:35 msg00000.html >-rw-rw---- 1 mailman mailman 1205 Jan 7 15:35 subject.html >-rw-rw---- 1 mailman mailman 1145 Jan 7 15:35 thread.html >[root at mailman:/var/mailman/archives/public]# > >In mm_cfg.py, I have MAILMAN_GROUP = 'mailman'. Now, if I set that >to www then would that make these files be created with group www? >Just wondering, because that doesn't actually help me. Don't do it. It will break almost everything. See . That said, these files in general are created by ArchRunner and are created in the group in which ArchRunner runs which is normally the group of the user that ran 'bin/mailmanctl start'. >My webserver >(thttpd) requires that files be world-readable in order to serve >them, regardless of whether the web server actually has access permission. >Also just wondering, why is public/test a symlink to ../private/test? >The mailing list (and the archives) are not private. The archives are always created/stored in archives/private. This is at least in part so archives can be changed back and forth between private and public simply by creating/deleting the symlink. The files themselves are normally world readable. I don't know why the .html files in your monthly directories are not world readable. They should be. Perhaps it has something to do with the MHonArc patch. Also, is msg00000.html an archived message? Normally these are named NNNNNN.html, not msgNNNNN.html. >So how can I make the archives be created world-readable? I'm guessing this has something to do with the MHonArc patch you installed, but I really don't know. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fcusack at fcusack.com Mon Jan 8 03:27:43 2007 From: fcusack at fcusack.com (Frank Cusack) Date: Sun, 07 Jan 2007 18:27:43 -0800 Subject: [Mailman-Users] mhonarc and non-world-readable archives problem In-Reply-To: References: Message-ID: <6BB411DB53074877246120C1@sucksless.local> On January 7, 2007 5:25:49 PM -0800 Mark Sapiro wrote: > Frank Cusack wrote: > >> I've built mailman-2.1.9 with the mhonarc patch >> (http://www.openinfo.co.uk/mm/patches/mhonarc/index.html) and it works >> great. I am running on Solaris 10 with python 2.5. >> >> The problem I have is that the list archives are not created >> world-readable. ... >> So how can I make the archives be created world-readable? > > > I'm guessing this has something to do with the MHonArc patch you > installed, but I really don't know. I looked over the patch and didn't see any umask changes. Maybe it was another patch that did something. Anyway ... I changed the MHONARC_ARCHIVER_PATH option to include '-umask 002' and it works. That's good enough for me. -frank From bsaxvik at sunrice.com.au Mon Jan 8 13:33:55 2007 From: bsaxvik at sunrice.com.au (Saxvik, Ben) Date: Mon, 8 Jan 2007 23:33:55 +1100 Subject: [Mailman-Users] Mailman Virtual Domains Message-ID: Hi, I want to use virtual domains on my mailman server. Though the problem I'm having at the moment is that any email sent out from the second virtual domain the resulting address matches that of the server itself and not the individual list (domain). For example the mailman server's FQDN is "listserv.testdomain.com.au" and the new virtual domain that has been added to this server is "listserv.anotherdomain.com.au". So any email sent out from "listserv.anotherdomain.com.au" the domain name gets replaced with "listserv.testdomain.com.au". I currently using sendmail as my MTA and I'm using mailman 2.1.9. Any assistance is appreciated. Many Thanks, Ben From msapiro at value.net Mon Jan 8 17:45:32 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 08:45:32 -0800 Subject: [Mailman-Users] mhonarc and non-world-readable archives problem In-Reply-To: <6BB411DB53074877246120C1@sucksless.local> Message-ID: Frank Cusack wrote: > >I looked over the patch and didn't see any umask changes. Maybe >it was another patch that did something. Anyway ... I changed >the MHONARC_ARCHIVER_PATH option to include '-umask 002' and >it works. That's good enough for me. So it seems that with the patch installed and MHonArc archiving enabled, it is MhonArc and not Mailman that creates the problem files. Thus your solution seems appropriate, or perhaps there is a way to configure the default permissions on these files within MHonArc. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 8 17:50:15 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 08:50:15 -0800 Subject: [Mailman-Users] Mailman Virtual Domains In-Reply-To: Message-ID: Saxvik, Ben wrote: > >For example the mailman server's FQDN is "listserv.testdomain.com.au" and the new virtual domain that has been added to this server is "listserv.anotherdomain.com.au". So any email sent out from "listserv.anotherdomain.com.au" the domain name gets replaced with "listserv.testdomain.com.au". > Does this happen with all mail sent from the second domain or just mail from Mailman. If the latter, see the list's host_name attribute on the General Options page and also searcg the FAQ wizard for fix_url. If it happens with all mail, it is a sendmail/host configuration issue, not Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pilsl at goldfisch.at Mon Jan 8 18:43:52 2007 From: pilsl at goldfisch.at (peter pilsl) Date: Mon, 08 Jan 2007 18:43:52 +0100 Subject: [Mailman-Users] delete moderator requests on the server? Message-ID: <45A282D8.8030900@goldfisch.at> I run plenty of lists on my server and on many of them the moderator-requests are piling up over time. Mostly when there is a spam-flood or when I'm on vacation or cause the people that moderate the list dont do their job. Is there a way to delete the moderator-requests with a command on the server instead of going to the moderator-request-page for each list? I found the heldmsg- files in mailman/data but deleting them does not change the fact that I still receive emails that "300 mylonelylist moderator request(s) waiting". Where can I set this for a certain list? Or how can I update the internal counter with the real number of moderator-requests? I could then delete the heldmsg- mails depending on date and simply remove all old requests at least. thnx peter From msapiro at value.net Mon Jan 8 19:17:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 10:17:39 -0800 Subject: [Mailman-Users] delete moderator requests on the server? In-Reply-To: <45A282D8.8030900@goldfisch.at> Message-ID: peter pilsl wrote: > >Is there a way to delete the moderator-requests with a command on the server >instead of going to the moderator-request-page for each list? See and . >I found the heldmsg- files in mailman/data but deleting them does not change the >fact that I still receive emails that "300 mylonelylist moderator request(s) >waiting". That's because simply removing the files doesn't update the list's request.pck (or request.db prior to 2.1.5) file. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From post at rgrs.com Mon Jan 8 20:19:47 2007 From: post at rgrs.com (Jay Rogers) Date: Mon, 08 Jan 2007 14:19:47 -0500 Subject: [Mailman-Users] Archived html messages Message-ID: When viewing the archive through the web interface for an archived HTML message, the HTML MIME attachment is separated ("scrubbed") to a separate webpage. A link is provided to view that webpage but the HTML content, tags and all, has been modified to display as plain text. This is not very useful. How does one change/configure Mailman to get these archived HTML attachments to display as expected? -- Jay From ken at control.com Mon Jan 8 20:42:38 2007 From: ken at control.com (Ken Crater) Date: Mon, 8 Jan 2007 14:42:38 -0500 Subject: [Mailman-Users] a corrupt pickle Message-ID: Hi all, We're using Mailman 2.1 (in fact, our control.com site was the impetus for v. 2.1) and appear to have suffered a severe problem in connection with a system crash over the weekend. Attempting to access our more important email list via the web interface results in the following traceback: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 87, in run_main main() File "/var/mailman/Mailman/Cgi/admin.py", line 70, in main admin_overview(_('No such list %(safelistname)s')) File "/var/mailman/Mailman/Cgi/admin.py", line 228, in admin_overview mlist = MailList.MailList(name, lock=0) File "/var/mailman/Mailman/MailList.py", line 101, in __init__ self.Load() File "/var/mailman/Mailman/MailList.py", line 588, in Load raise Errors.MMCorruptListDatabaseError, e MMCorruptListDatabaseError: [Errno 2] No such file or directory: '/var/mailman/lists/automation/config.db.last' Further troubleshooting using (attempting to use) dumpdb and check_db indicates that BOTH config.pck and config.pck.last (the above error message referring to config.db.last seems to be incorrect, since this version uses pickles) are experiencing EOFErrors. Actually, dumpdb and check_db in this version crash against these target files, but I brought the list files into a new version of Mailman and both files appear empty there. And, wouldn't you know it, this led us to discover that our hosting site has not been backing up the /var/mailman directory, so we don't have backups. Are there any tools or techniques for data recovery in such circumstances? The files appear to still contain data -- in fact, I've been frantically using a text editor to extract the 1000 or so email addresses as a last-resort, but probably won't be able to capture individual settings with this approach. I can't imagine why both files are corrupted, but they both produce the same result (a compare shows that they are slightly different). Our formerly-active list is down now, so any help will be GREATLY appreciated! Thanks in advance, Ken Crater Control.com ken at control.com From liquid at nationalcomfortinstitute.com Mon Jan 8 22:29:38 2007 From: liquid at nationalcomfortinstitute.com (liquid at nationalcomfortinstitute.com) Date: Mon, 8 Jan 2007 16:29:38 -0500 Subject: [Mailman-Users] Sender Name in message Message-ID: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> I'm running Mailman 2.1.5 I've looked through the archives and have yet to find an answer to this. I'm running an anonymous discussion list. The list is setup so replies are by directed back to the list. I would like to be able to add the senders/posters name (the (optional) name that is in the system) to the header, message or footer. I want it this way to dummy proof the list by forcing a signature. Any way this can be done? Jeff From chandler at chapman.edu Mon Jan 8 22:13:50 2007 From: chandler at chapman.edu (Jay Chandler) Date: Mon, 08 Jan 2007 13:13:50 -0800 Subject: [Mailman-Users] Configuration Question Message-ID: <45A2B40E.1020105@chapman.edu> Greetings. I'm a bit new to Mailman, as I've yet to actually install it on anything. We currently have a majordomo server that's aging, and I'd prefer to replace it with Mailman for a number of reasons. Is there any reason I can't run Mailman on our outbound SMTP server, or would I want to locate it somewhere else? I'd like to avoid giving it its own dedicated box if at all possible, but I also don't want it to complicate the sending of generic mail, either in terms of hostnames or in overhead. FreeBSD 6.1 and Postfix are the relevant pieces. Thanks very much in advance. -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler at chapman.edu Today's Excuse: I'm sorry a pentium won't do, you need an SGI to connect with us. From ashley at pcraft.com Mon Jan 8 22:43:41 2007 From: ashley at pcraft.com (Ashley M. Kirchner) Date: Mon, 08 Jan 2007 14:43:41 -0700 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> References: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> Message-ID: <45A2BB0D.4030806@pcraft.com> liquid at nationalcomfortinstitute.com wrote: > I'm running Mailman 2.1.5 > > I've looked through the archives and have yet to find an answer to this. > > I'm running an anonymous discussion list. The list is setup so replies > are by directed back to the list. > > I would like to be able to add the senders/posters name (the > (optional) name that is in the system) to the header, message or footer. > > I want it this way to dummy proof the list by forcing a signature. > > Any way this can be done? > > > Jeff > You might want to read FAQ 3.15 as a start. It tells you how to enable personalization on an installation, and how to set it up per list. Once enabled, you can click on any of the 'about' links when you're browsing the admin site for your list and it gives you pointers on how to add personalized messages to the message. Do keep in mind that you're taking a performance hit with personalization. So be careful with that. -- W | It's not a bug - it's an undocumented feature. +-------------------------------------------------------------------- Ashley M. Kirchner . 303.442.6410 x130 IT Director / SysAdmin / Websmith . 800.441.3873 x130 Photo Craft Imaging . 3550 Arapahoe Ave. #6 http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A. From liquid at nationalcomfortinstitute.com Mon Jan 8 23:34:52 2007 From: liquid at nationalcomfortinstitute.com (liquid at nationalcomfortinstitute.com) Date: Mon, 8 Jan 2007 17:34:52 -0500 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <45A2BB0D.4030806@pcraft.com> References: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> <45A2BB0D.4030806@pcraft.com> Message-ID: <20070108173452.5ptpxs8g0w44oow8@webmail.nationalcomfortinstitute.com> I have personalization turn on but I didn't think it had a variable for the poster/senders name (not that I found). Am I missing some thing? I know it has the TO: username variable. But thats not what I'm looking for. Jeff Quoting "Ashley M. Kirchner" : > liquid at nationalcomfortinstitute.com wrote: >> I'm running Mailman 2.1.5 >> >> I've looked through the archives and have yet to find an answer to this. >> >> I'm running an anonymous discussion list. The list is setup so >> replies are by directed back to the list. >> >> I would like to be able to add the senders/posters name (the >> (optional) name that is in the system) to the header, message or >> footer. >> >> I want it this way to dummy proof the list by forcing a signature. >> >> Any way this can be done? >> >> >> Jeff >> > You might want to read FAQ 3.15 as a start. It tells you how to > enable personalization on an installation, and how to set it up per > list. Once enabled, you can click on any of the 'about' links when > you're browsing the admin site for your list and it gives you pointers > on how to add personalized messages to the message. > > Do keep in mind that you're taking a performance hit with > personalization. So be careful with that. > > -- > W | It's not a bug - it's an undocumented feature. > +-------------------------------------------------------------------- > Ashley M. Kirchner . 303.442.6410 x130 > IT Director / SysAdmin / Websmith . 800.441.3873 x130 > Photo Craft Imaging . 3550 Arapahoe Ave. #6 > http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A. From ashley at pcraft.com Mon Jan 8 23:55:59 2007 From: ashley at pcraft.com (Ashley M. Kirchner) Date: Mon, 08 Jan 2007 15:55:59 -0700 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <20070108173452.5ptpxs8g0w44oow8@webmail.nationalcomfortinstitute.com> References: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> <45A2BB0D.4030806@pcraft.com> <20070108173452.5ptpxs8g0w44oow8@webmail.nationalcomfortinstitute.com> Message-ID: <45A2CBFF.30104@pcraft.com> liquid at nationalcomfortinstitute.com wrote: > I have personalization turn on but I didn't think it had a variable > for the poster/senders name (not that I found). Am I missing some > thing? I know it has the TO: username variable. But thats not what I'm > looking for. Log in to your admin site, go under the 'Non-digest options' and enable the personalize option. Then click the 'Details for msg header' link in the next box below that personalization option. Read the instructions. From aman.singer at gmail.com Tue Jan 9 00:07:17 2007 From: aman.singer at gmail.com (Aman Singer) Date: Mon, 8 Jan 2007 18:07:17 -0500 Subject: [Mailman-Users] Problem posting to Mailman list from Gmail and other addresses. Message-ID: <45a2ce16.1459fa42.42c3.fffff100@mx.google.com> Hi, all. I find that I'm not able to post to a specific Mailman list running Mailman 2.1B2. If I post from an address at Utoronto.ca, using a rogers.com SMTP server, everything is fine. If I post from a Gmail address using the Gmail SMTP server, I get headers in the message body and messages with no subject. I think this might be a problem with the Gmail implementation of Domain Keys, but am not sure. I am receiving and sending with Outlook 2003, but the choice of mail client sending doesn't seem to matter to the result. Below, I have a message sent from the utoronto.ca address and another sent from the gmail.com address. Both messages contain the same subject and body text, both were sent from the same client and computer, both were sent to the same list, and both were received from that list on the same computer and client, so the only variable I can think of is the SMTP server used to send them. Would anyone know why this is happening? Aman Message from utoronto.ca address, this message arrived properly. The headers and body are separated from each other and the rest of this message by blank lines. Otherwise, they are unaltered. Headers Delivered-To: aman.singer at gmail.com Received: by 10.78.194.14 with SMTP id r14cs332128huf; Mon, 8 Jan 2007 14:38:58 -0800 (PST) Received: by 10.67.91.6 with SMTP id t6mr18712268ugl.1168295938259; Mon, 08 Jan 2007 14:38:58 -0800 (PST) Return-Path: Received: from llla207-a.servidoresdns.net (llla207-a.servidoresdns.net [217.76.128.98]) by mx.google.com with ESMTP id i39si40279072ugd.2007.01.08.14.38.53; Mon, 08 Jan 2007 14:38:58 -0800 (PST) Received-SPF: neutral (google.com: 217.76.128.98 is neither permitted nor denied by best guess record for domain of msp_mailing-bounces at codefactory.es) Received: from llla207-a.servidoresdns.net (localhost.localdomain [127.0.0.1]) by llla207-a.servidoresdns.net (Postfix) with ESMTP id D0A212A5EE5; Mon, 8 Jan 2007 23:38:52 +0100 (CET) X-Original-To: codefactory.es.msp_mailing at llla207-a.servidoresdns.net Delivered-To: codefactory.es.msp_mailing at llla207-a.servidoresdns.net Received: from llsa730-a01.servidoresdns.net (llsa730-a01.servidoresdns.net [82.223.190.24]) by llla207-a.servidoresdns.net (Postfix) with ESMTP id 45C702A3828 for ; Mon, 8 Jan 2007 23:38:51 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-01.servidoresdns.net (Postfix) with ESMTP id 29D7335067 for ; Mon, 8 Jan 2007 23:38:51 +0100 (CET) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by smtp-01.servidoresdns.net (Postfix) with SMTP id 78B9335236 for ; Mon, 8 Jan 2007 23:38:47 +0100 (CET) Received: (qmail 71508 invoked from network); 8 Jan 2007 22:38:45 -0000 Received: from unknown (HELO appdesk) (facable at rogers.com@64.229.169.146 with login) by smtp102.rog.mail.re2.yahoo.com with SMTP; 8 Jan 2007 22:38:45 -0000 X-YMail-OSG: O.8d490VM1l7s8LGGrb4dW_w3M7j204TaSYLYviBZ4.tLf0BtT_UfXujwmGU020sOg-- From: "Aman Singer" To: Date: Mon, 8 Jan 2007 17:40:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcczdfOHXLydKqITQraUGi8f0BOPRg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-Id: <20070108223847.78B9335236 at smtp-01.servidoresdns.net> X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=1.704 tagged_above=0.01 required=5 tests=MSGID_FROM_MTA_ID X-Spam-Score: 1.704 X-Spam-Tests: InternalSpamCheck X-Spam-Level: * Subject: [Mobile Speak Pocket] Test X-BeenThere: msp_mailing at codefactory.es X-Mailman-Version: 2.1b2 Precedence: bulk Sender: msp_mailing-bounces at codefactory.es Errors-To: msp_mailing-bounces at codefactory.es Body Testing 123. This is a test of the Mailman list. [Note: If you wish to post your reply to the list, use the "Reply All", rather than the "Reply", option of your email client.] _______________________________________________ msp_mailing list msp_mailing at codefactory.es http://list.codefactory.es/mailman/listinfo/codefactory.es.msp_mailing Message from gmail.com address, this message arrived with part of the header in the body of the message. That is, it arrived badly. The headers and body are separated from each other and the rest of this message by blank lines. Otherwise, they are unaltered. Headers Delivered-To: aman.singer at gmail.com Received: by 10.78.194.14 with SMTP id r14cs332746huf; Mon, 8 Jan 2007 14:50:02 -0800 (PST) Received: by 10.67.91.6 with SMTP id t6mr18721597ugl.1168296599969; Mon, 08 Jan 2007 14:49:59 -0800 (PST) Return-Path: Received: from llla207-a.servidoresdns.net (llla207-a.servidoresdns.net [217.76.128.98]) by mx.google.com with ESMTP id u1si27989941uge.2007.01.08.14.49.55; Mon, 08 Jan 2007 14:49:59 -0800 (PST) Received-SPF: neutral (google.com: 217.76.128.98 is neither permitted nor denied by best guess record for domain of msp_mailing-bounces at codefactory.es) DomainKey-Status: bad format Received: from llla207-a.servidoresdns.net (localhost.localdomain [127.0.0.1]) by llla207-a.servidoresdns.net (Postfix) with ESMTP id BD83A2A5ED5; Mon, 8 Jan 2007 23:49:54 +0100 (CET) X-Original-To: codefactory.es.msp_mailing at llla207-a.servidoresdns.net Delivered-To: codefactory.es.msp_mailing at llla207-a.servidoresdns.net Received: from llsa730-a01.servidoresdns.net (llsa730-a01.servidoresdns.net [82.223.190.24]) by llla207-a.servidoresdns.net (Postfix) with ESMTP id 2607C2953AD for ; Mon, 8 Jan 2007 23:49:53 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp-01.servidoresdns.net (Postfix) with ESMTP id 082A7352EE for ; Mon, 8 Jan 2007 23:49:53 +0100 (CET) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.239]) by smtp-01.servidoresdns.net (Postfix) with ESMTP id 6DC0B35362 for ; Mon, 8 Jan 2007 23:49:49 +0100 (CET) Received: by nz-out-0506.google.com with SMTP id z6so2315842nzd for ; Mon, 08 Jan 2007 14:49:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; Message-Id: <20070108224954.BD83A2A5ED5 at llla207-a.servidoresdns.net> Date: Mon, 8 Jan 2007 23:49:54 +0100 (CET) From: msp_mailing-bounces at codefactory.es To: undisclosed-recipients:; Body h=received:from:to:subject:date:mime-version:content-type:content-transfer-e ncoding:x-mailer:thread-index:x-mimeole:message-id; b=AOMwVoy14SDxt+7bDsRLIs+8jijdH406+iCOFHjsjDJPFswngLkUj2cDRsdTouLEt4JvlSn9bj G063TFNbGvDAOjOa+L69lJqHZD1M7sflW42hSe66YUZReLbNmYX4SWn8Tvi1hFhg7jBb77bNqyfL z2iDbdnvAlG46ARa21cYA= Received: by 10.35.57.5 with SMTP id j5mr49813476pyk.1168296587810; Mon, 08 Jan 2007 14:49:47 -0800 (PST) Received: from appdesk ( [64.229.169.146]) by mx.google.com with ESMTP id a79sm38675295pye.2007.01.08.14.49.46; Mon, 08 Jan 2007 14:49:47 -0800 (PST) From: "Aman Singer" To: Date: Mon, 8 Jan 2007 17:51:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: Acczd4cIlaI/0xIeSkiPufyyHZ394g== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: <45a2ca8b.556027e6.7a3c.ffffe7f1 at mx.google.com> X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.024 tagged_above=0.01 required=5 tests=RCVD_BY_IP X-Spam-Score: 0.024 X-Spam-Tests: InternalSpamCheck X-Spam-Level: Subject: [Mobile Speak Pocket] Test X-BeenThere: msp_mailing at codefactory.es X-Mailman-Version: 2.1b2 Precedence: bulk Sender: msp_mailing-bounces at codefactory.es Errors-To: msp_mailing-bounces at codefactory.es Testing 123. This is a test of the Mailman list. [Note: If you wish to post your reply to the list, use the "Reply All", rather than the "Reply", option of your email client.] _______________________________________________ msp_mailing list msp_mailing at codefactory.es http://list.codefactory.es/mailman/listinfo/codefactory.es.msp_mailing From msapiro at value.net Tue Jan 9 00:07:50 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 15:07:50 -0800 Subject: [Mailman-Users] Archived html messages In-Reply-To: Message-ID: Jay Rogers wrote: > >How does one change/configure Mailman to get these >archived HTML attachments to display as expected? Set ARCHIVE_HTML_SANITIZER = 3 in mm_cfg.py, but first read the comments about this setting in Defaults.py, and perhaps also google 'xss' and read some of the relevant hits. Basically, doing this allows anyone who can post to a list to place malicious HTML on your web site. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Mon Jan 8 23:43:28 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 8 Jan 2007 16:43:28 -0600 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> References: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> Message-ID: At 4:29 PM -0500 1/8/07, liquid at nationalcomfortinstitute.com wrote: > I'm running an anonymous discussion list. The list is setup so replies > are by directed back to the list. > > I would like to be able to add the senders/posters name (the > (optional) name that is in the system) to the header, message or footer. If the list is anonymous, then doing this kind of thing would eliminate the anonymity, and therefore presumably violate the basic purpose of the list. Otherwise, don't run it as an anonymous list. -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. From brad at shub-internet.org Mon Jan 8 23:44:28 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 8 Jan 2007 16:44:28 -0600 Subject: [Mailman-Users] Configuration Question In-Reply-To: <45A2B40E.1020105@chapman.edu> References: <45A2B40E.1020105@chapman.edu> Message-ID: At 1:13 PM -0800 1/8/07, Jay Chandler wrote: > Is there any reason I can't run Mailman on our outbound SMTP server, or > would I want to locate it somewhere else? I'd like to avoid giving it > its own dedicated box if at all possible, but I also don't want it to > complicate the sending of generic mail, either in terms of hostnames or > in overhead. Well, a lot will depend on your specific mail server and mailing list configuration, but I certainly don't see any reason why you can't run them both on the same machine. I think that this is the most typical type of installation, anyway. -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. From brad at shub-internet.org Tue Jan 9 00:06:12 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 8 Jan 2007 17:06:12 -0600 Subject: [Mailman-Users] Archived html messages In-Reply-To: References: Message-ID: At 2:19 PM -0500 1/8/07, Jay Rogers wrote: > How does one change/configure Mailman to get these > archived HTML attachments to display as expected? That sounds like a web server MIME type issue, in that the web server is not telling the web client the appropriate information regarding the actual type of content of the file, and the web client is then displaying that information in a manner that doesn't make a whole lot of sense. If so, then this would not be a Mailman-related issue, and I don't think we can help you. You would need to use the documentation, FAQs, support mailing lists, etc... that are appropriate for your web server. See also FAQ 4.46. -- Brad Knowles, Trend Micro has announced that they will cancel the stop.mail-abuse.org mail forwarding service as of 15 November 2006. If you have an old e-mail account for me at this domain, please make sure you correct that with the current address. From msapiro at value.net Tue Jan 9 00:20:20 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 15:20:20 -0800 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <45A2CBFF.30104@pcraft.com> Message-ID: Ashley M. Kirchner wrote: >liquid at nationalcomfortinstitute.com wrote: >> I have personalization turn on but I didn't think it had a variable >> for the poster/senders name (not that I found). Am I missing some >> thing? I know it has the TO: username variable. But thats not what I'm >> looking for. > > Log in to your admin site, go under the 'Non-digest options' and >enable the personalize option. Then click the 'Details for msg header' >link in the next box below that personalization option. Read the >instructions. All of the personalization substitutions are for the RECIPIENT, not the SENDER. But, as Brad points out in another reply, If you want the post to identify the poster, why is the list anonymous? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ashley at pcraft.com Tue Jan 9 00:23:41 2007 From: ashley at pcraft.com (Ashley M. Kirchner) Date: Mon, 08 Jan 2007 16:23:41 -0700 Subject: [Mailman-Users] Sender Name in message In-Reply-To: References: Message-ID: <45A2D27D.1000607@pcraft.com> Mark Sapiro wrote: > All of the personalization substitutions are for the RECIPIENT, not the > SENDER. > Ah yes, I did overlook that part. My bad. From msapiro at value.net Tue Jan 9 00:36:04 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 15:36:04 -0800 Subject: [Mailman-Users] a corrupt pickle In-Reply-To: Message-ID: Ken Crater wrote: > >Attempting to access our more important email list via the web interface >results in the following traceback: > >Traceback (most recent call last): > File "/var/mailman/scripts/driver", line 87, in run_main > main() > File "/var/mailman/Mailman/Cgi/admin.py", line 70, in main > admin_overview(_('No such list %(safelistname)s')) > File "/var/mailman/Mailman/Cgi/admin.py", line 228, in admin_overview > mlist = MailList.MailList(name, lock=0) > File "/var/mailman/Mailman/MailList.py", line 101, in __init__ > self.Load() > File "/var/mailman/Mailman/MailList.py", line 588, in Load > raise Errors.MMCorruptListDatabaseError, e >MMCorruptListDatabaseError: [Errno 2] No such file or directory: >'/var/mailman/lists/automation/config.db.last' > >Further troubleshooting using (attempting to use) dumpdb and check_db >indicates that BOTH config.pck and config.pck.last (the above error message >referring to config.db.last seems to be incorrect, since this version uses >pickles) are experiencing EOFErrors. The MailList Load() method tries 4 files in the order config.pck, config.pck.last, config.db and config.db.last. It tries the config.db files because it may be migrating data from a 2.0.x version. When none of them work, the error message refers to the last one tried. Note that this is why you should remove any config.db* files after migrating to 2.1. In a situation such as this, if a config.db were still there, it would be used with its possibly years old data. >Actually, dumpdb and check_db in this >version crash against these target files, but I brought the list files into >a new version of Mailman and both files appear empty there. > >And, wouldn't you know it, this led us to discover that our hosting site has >not been backing up the /var/mailman directory, so we don't have backups. :-( >Are there any tools or techniques for data recovery in such circumstances? Unfortunately, not any good ones. strings may help or your text editor method. Also, email addresses should be grouped by regular vs. digest which may help. >The files appear to still contain data -- in fact, I've been frantically >using a text editor to extract the 1000 or so email addresses as a >last-resort, but probably won't be able to capture individual settings with >this approach. > >I can't imagine why both files are corrupted, but they both produce the same >result (a compare shows that they are slightly different). Normally, if the config.pck is corrupt, we should fall back to the config.pck.last which should be OK. It is difficult to see how the logic could result in both files being corrupt, but strange things happen in a crash. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at python.org Tue Jan 9 00:58:17 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 8 Jan 2007 18:58:17 -0500 Subject: [Mailman-Users] a corrupt pickle In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 8, 2007, at 6:36 PM, Mark Sapiro wrote: > Normally, if the config.pck is corrupt, we should fall back to the > config.pck.last which should be OK. It is difficult to see how the > logic could result in both files being corrupt, but strange things > happen in a crash. That sucks Ken! BTW, what version were you running? I don't remember the details but around about 2.1.3->2.1.4 time frame, we promoted SYNC_AFTER_WRITE to a full fledged mm_cfg.py variable, but we left it set to No by default. This variable forces an fsync when the config.pck file is written, which in turn ensures that the data is flushed to your hard drive (assuming your OS doesn't lie). Note that this is set to No by default because while being much more secure about your data, it's a performance killer. If both files are corrupt, you can thank your hardware. What probably happened is that a subsequent load of config.pck returned valid data but it was corrupted on the disk. Maybe the good data was pulled from the disk buffers -- who knows? But then when Mailman tried to write the new config.pck file, the old config.pck file was already hosed and that ended up in config.pck.last. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRaLannEjvBPtnXfVAQIdtwP/R9/5RQa44Azgx83s9/+QrZKDrOtiyroj rxWGAwMt+l90nJ5YZCQfnwMc4JTjfT2wsLluUXhfJvrpEqV3mHoXZJP/X6iOyurb O0miIQMEb+80pIh9xDECgrrF86qBmmJmnbGyhXEe/qW7uEuDswO3IQPmXThV8+wR mO/S6dRvU1k= =JFWy -----END PGP SIGNATURE----- From msapiro at value.net Tue Jan 9 01:15:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 8 Jan 2007 16:15:57 -0800 Subject: [Mailman-Users] Problem posting to Mailman list from Gmail andother addresses. In-Reply-To: <45a2ce16.1459fa42.42c3.fffff100@mx.google.com> Message-ID: Aman Singer wrote: > I find that I'm not able to post to a specific Mailman list running >Mailman 2.1B2. Over 4 years old. Current release is 2.1.9. Is there some reason why you can't upgrade? >If I post from an address at Utoronto.ca, using a rogers.com >SMTP server, everything is fine. If I post from a Gmail address using the >Gmail SMTP server, I get headers in the message body and messages with no >subject. I think this might be a problem with the Gmail implementation of >Domain Keys, but am not sure. I am receiving and sending with Outlook 2003, >but the choice of mail client sending doesn't seem to matter to the result. How about the choice of mail client reading the resultant post? >Below, I have a message sent from the utoronto.ca address and another sent >from the gmail.com address. Both messages contain the same subject and body >text, both were sent from the same client and computer, both were sent to >the same list, and both were received from that list on the same computer >and client, so the only variable I can think of is the SMTP server used to >send them. Would anyone know why this is happening? First message snipped. >Message from gmail.com address, this message arrived with part of the header >in the body of the message. That is, it arrived badly. The headers and body >are separated from each other and the rest of this message by blank lines. >Otherwise, they are unaltered. >Headers > >DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; > s=beta; d=gmail.com; The next 4 headers have been inserted along with blank lines in the middle of the DomainKey-Signature: header. This is presumably because something inserted a blank line at this point terminating the headers. >Message-Id: <20070108224954.BD83A2A5ED5 at llla207-a.servidoresdns.net> >Date: Mon, 8 Jan 2007 23:49:54 +0100 (CET) >From: msp_mailing-bounces at codefactory.es >To: undisclosed-recipients:; > >Body > > >h=received:from:to:subject:date:mime-version:content-type:content-transfer-e >ncoding:x-mailer:thread-index:x-mimeole:message-id; > > >b=AOMwVoy14SDxt+7bDsRLIs+8jijdH406+iCOFHjsjDJPFswngLkUj2cDRsdTouLEt4JvlSn9bj >G063TFNbGvDAOjOa+L69lJqHZD1M7sflW42hSe66YUZReLbNmYX4SWn8Tvi1hFhg7jBb77bNqyfL >z2iDbdnvAlG46ARa21cYA= It is difficult to tell from the 'folding' and 'refolding' what the original acrtually looked like. >X-BeenThere: msp_mailing at codefactory.es >X-Mailman-Version: 2.1b2 >Precedence: bulk >Sender: msp_mailing-bounces at codefactory.es >Errors-To: msp_mailing-bounces at codefactory.es The above 5 headers were inserted by Mailman immediately before SMTP delivery. At this point, The headers above had not yet been munged. Thus, my best guess is that it is some MTA between Mailman and you that is corrupting the DomainKey-Signature: header. Judging from the headers >Received-SPF: neutral (google.com: 217.76.128.98 is neither permitted nor denied by best guess record for domain of msp_mailing-bounces at codefactory.es) >DomainKey-Status: bad format >Received: from llla207-a.servidoresdns.net (localhost.localdomain [127.0.0.1]) > by llla207-a.servidoresdns.net (Postfix) with ESMTP > id BD83A2A5ED5; Mon, 8 Jan 2007 23:49:54 +0100 (CET) and the fact that the added Date: and Message-ID: headers are >Message-Id: <20070108224954.BD83A2A5ED5 at llla207-a.servidoresdns.net> >Date: Mon, 8 Jan 2007 23:49:54 +0100 (CET) (same timestamp and messade-id host name) I think the Postfix at llla207-a.servidoresdns.net may be responsible for munging the DomainKey-Signature:, or it may just be the first MTA that detected it, and llsa730-a01.servidoresdns.net may have done it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ken at control.com Tue Jan 9 03:58:48 2007 From: ken at control.com (Ken Crater) Date: Mon, 8 Jan 2007 21:58:48 -0500 Subject: [Mailman-Users] a corrupt pickle In-Reply-To: Message-ID: <00a501c7339a$15ddb520$6701a8c0@unakite> Thanks, Barry and Mark, I'm resigned to my fate. Just as additional info on the circumstances: - The system crash seems to have been caused by disk errors on an alleged RAID array (still working on that problem), so that may account for the file corruption. - We were running Mailman 2.1, so the SYNC_AFTER_WRITE option was not available anyway. So, the combination of buffering and disk errors, along with an ill-timed crash (are they *ever* well-timed?) was likely the culprit. None of which would have been so bad had we been more careful about policing our backup policies. Lots of lessons on this one... Best Regards, Ken From webmaster at web-analysts.net Tue Jan 9 15:23:08 2007 From: webmaster at web-analysts.net (Webmaster) Date: Tue, 9 Jan 2007 09:23:08 -0500 Subject: [Mailman-Users] logs no longer working References: <00a501c7339a$15ddb520$6701a8c0@unakite> Message-ID: <1c4001c733f9$b1abfb60$0200a8c0@D4QCJ541> I recently upgraded mailman to 2.1.9 and everything seems to be working fine except somehow all mailman logging has ceased. I am running fedora core 5. my permissions on /var/log are drwxrwsr-x 2 mailman mailman 4096 Jan 7 04:04 mailman and in /var/log/mailman are -rw-rw-r-- 1 mailman mailman 0 Jan 7 04:04 qrunner I have restarted the service with no difference. suggestions anyone? thank you in advance! From zbyszek at szalbot.homedns.org Tue Jan 9 15:14:30 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 15:14:30 +0100 (CET) Subject: [Mailman-Users] result of email command Message-ID: <2137.192.168.11.27.1168352070.squirrel@lists.lc-words.com> I want users to subcribe to my mls by email only (as Mailman is not avilable to the world on the machine where it is installed). All works fine but when I subscribe and confirm, the email I get is very strange. It says (in Polish) "Results of email command." The original message is attached and first line says: - Result: Confirmed and then the unprocessed rest of the message. My question is whether I can change some option somewhere so that there are no attachments. Just a plain message saying: Subscribed / Removed from the mailing list. Can it be set somewhere? Thank you! -- Zbigniew Szalbot From zbyszek at szalbot.homedns.org Tue Jan 9 15:09:33 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 15:09:33 +0100 (CET) Subject: [Mailman-Users] list name in email Message-ID: <2131.192.168.11.27.1168351773.squirrel@lists.lc-words.com> Hello, Is it possible to insert an equivalent of %(MM-List-Name)s into verity.txt template? For example, I have list which real name is ppl. It is an abbreviation and does not mean anything. But when people get the confirmation message, they should see a full name. I tried %(MM-List-Name)s, then %(listname)s, then %(description)s but they don't resolve to full list name. Thank you for advice! Warm regards, -- Zbigniew Szalbot From msapiro at value.net Tue Jan 9 18:42:23 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 09:42:23 -0800 Subject: [Mailman-Users] result of email command In-Reply-To: <2137.192.168.11.27.1168352070.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: >I want users to subcribe to my mls by email only (as Mailman is not >avilable to the world on the machine where it is installed). All works >fine but when I subscribe and confirm, the email I get is very strange. It >says (in Polish) "Results of email command." > >The original message is attached and first line says: > >- Result: >Confirmed > >and then the unprocessed rest of the message. My question is whether I can >change some option somewhere so that there are no attachments. Just a >plain message saying: > >Subscribed / Removed from the mailing list. > >Can it be set somewhere? No. There is no such option. You would have to modify the code in Mailman/Queue/CommandRunner.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 9 18:49:52 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 09:49:52 -0800 Subject: [Mailman-Users] list name in email In-Reply-To: <2131.192.168.11.27.1168351773.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: > >Is it possible to insert an equivalent of %(MM-List-Name)s into verity.txt >template? For example, I have list which real name is ppl. It is an >abbreviation and does not mean anything. But when people get the >confirmation message, they should see a full name. > >I tried %(MM-List-Name)s, then %(listname)s, then %(description)s but they >don't resolve to full list name. The substititions in templates are defined in a Python dictionary that is passed to the call to produce the substituted template. In general, the parameters which can be substituted are specific to a given template and are only those which appear in the base template. In this case, you can't add other substitutions to verify.txt unless you modify the calls to Utils.maketext() in Mailman/MailList.py to add the additional substitution parameters to the dictionary that is passed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From zbyszek at szalbot.homedns.org Tue Jan 9 18:51:01 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 18:51:01 +0100 (CET) Subject: [Mailman-Users] result of email command In-Reply-To: References: Message-ID: <61776.192.168.11.7.1168365061.squirrel@lists.lc-words.com> Hello, >>change some option somewhere so that there are no attachments. Just a >>plain message saying: >> >>Subscribed / Removed from the mailing list. >> >>Can it be set somewhere? > > > No. There is no such option. You would have to modify the code in > Mailman/Queue/CommandRunner.py. Thank you Mark - is there a reason why command results returned from web forms differ from email ones? BTW - thank you for your hard work and great piece of software! -- Zbigniew Szalbot From msapiro at value.net Tue Jan 9 19:00:01 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 10:00:01 -0800 Subject: [Mailman-Users] result of email command In-Reply-To: <61776.192.168.11.7.1168365061.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: > >Thank you Mark - is there a reason why command results returned from web >forms differ from email ones? Emails with commands may in general contain multiple commands in the subject and/or body of the email. Thus CommandRunner processes every line of the email until it encounters an error or a non-command and then it lists the rest of the email as 'unprocessed' so in case it actually did contain commands, you know they weren't done. Web forms in general contain a single request, the results of which can be reported more succinctly. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From zbyszek at szalbot.homedns.org Tue Jan 9 19:05:05 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 19:05:05 +0100 (CET) Subject: [Mailman-Users] list name in email In-Reply-To: References: Message-ID: <61908.192.168.11.7.1168365905.squirrel@lists.lc-words.com> Hello, > The substititions in templates are defined in a Python dictionary that > is passed to the call to produce the substituted template. In general, > the parameters which can be substituted are specific to a given > template and are only those which appear in the base template. > > In this case, you can't add other substitutions to verify.txt unless > you modify the calls to Utils.maketext() in Mailman/MailList.py to add > the additional substitution parameters to the dictionary that is > passed. I tried your advice and added such a line: 'MM-List-Name' : mm_list_name, However, mailman stopped sending confirmation messages to me so I guess I must have made a mistake (I added %(mm_list_name)s to verify.txt. Thanks! -- Zbigniew Szalbot From msapiro at value.net Tue Jan 9 19:07:43 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 10:07:43 -0800 Subject: [Mailman-Users] logs no longer working In-Reply-To: <1c4001c733f9$b1abfb60$0200a8c0@D4QCJ541> Message-ID: Webmaster wrote: >I recently upgraded mailman to 2.1.9 and everything seems to >be working fine except somehow all mailman logging has ceased. >I am running fedora core 5. my permissions on /var/log are > >drwxrwsr-x 2 mailman mailman 4096 Jan 7 04:04 mailman > >and in /var/log/mailman are > >-rw-rw-r-- 1 mailman mailman 0 Jan 7 04:04 qrunner > >I have restarted the service with no difference. suggestions anyone? >thank you in advance! My first guess is that the logs just aren't where you are looking. The fact the the dates on /var/log/mailman and /var/log/mailman/qrunner are current seems to contradict this however. Did you upgrade from RedHat RPM or source? Have you looked elsewhere? E.g. find / -name qrunner -print -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alan at patriot.net Tue Jan 9 19:15:55 2007 From: alan at patriot.net (Alan McConnell) Date: Tue, 9 Jan 2007 13:15:55 -0500 Subject: [Mailman-Users] mailman 2.1.5 and Debian upgrades Message-ID: <20070109181555.GA2540@patriot.net> Dear Helpful Experts, Please have patience! I'll try to make this the last revisit of this subject. I am the admin of a four-month old Mailman E-list, running on my ISP, PatriotNet. The people actually responsible for Tech Support at PatriotNet are very reliant on Debian. They are running Debian Sarge, because that is the latest "stable" Debian release(coincidentally, so am I, at home). Debian Sarge provides MM 2.1.5, which Brad and Mark have criticized in rather scathing terms; unfortunately, I've lost/misplaced the exact E-mails saying this. Can I, again, have the Assembled Wisdom(TM) tell me, and the PatriotNet staff, how to proceed to upgrade the MM install from 2.1.5 to 2.1.9? And a few words of wisdom about why this is advisable would also be appreciated. I have spelled out, chapter and verse, all the problems that I have been having with 2.1.5. But heck, what do I know? I'm just a customer, and who pays attention to them? Again apologies for repeat request, and thanks for your anticipated assistance. A grateful Alan -- Alan McConnell : http://patriot.net/users/alan "The intelligence and facts were being fixed around the policy." Impeachment proceedings should be started immediately. From msapiro at value.net Tue Jan 9 19:18:18 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 10:18:18 -0800 Subject: [Mailman-Users] list name in email In-Reply-To: <61908.192.168.11.7.1168365905.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: > >I tried your advice and added such a line: > > 'MM-List-Name' : mm_list_name, > >However, mailman stopped sending confirmation messages to me so I guess I >must have made a mistake (I added %(mm_list_name)s to verify.txt. Yes, you made a mistake. You'll probably find tracebacks from the exception in Mailman's error log. The problem is the value you have assigned to the key 'MM-List-Name' is not a defined variable. You need 'MM-List-Name' : mlist.real_name, rather than what you have. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From zbyszek at szalbot.homedns.org Tue Jan 9 19:28:05 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 19:28:05 +0100 (CET) Subject: [Mailman-Users] list name in email In-Reply-To: References: Message-ID: <62352.192.168.11.7.1168367285.squirrel@lists.lc-words.com> Hi there again, > Yes, you made a mistake. You'll probably find tracebacks from the > exception in Mailman's error log. The problem is the value you have > assigned to the key 'MM-List-Name' is not a defined variable. You need > > 'MM-List-Name' : mlist.real_name, > > rather than what you have. I applied the correction according to your suggestions, restarted mailman but no confirmation email is being sent. I find this in error log: File "/usr/local/mailman/Mailman/MailList.py", line 887, in AddMember {'email' : email, NameError: global name 'mlist' is not defined No worries - I will return to the basics :) -- Zbigniew Szalbot From zbyszek at szalbot.homedns.org Tue Jan 9 19:59:48 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 19:59:48 +0100 (CET) Subject: [Mailman-Users] list name in email In-Reply-To: <200701091142.AA185336280@mail.value.net> References: <200701091142.AA185336280@mail.value.net> Message-ID: <62591.192.168.11.7.1168369188.squirrel@lists.lc-words.com> Hello again, > And I made a mistake too. It should be > > 'MM-List-Name' : self.real_name, Thanks a lot. But this does not give me the full name of the list as on the mailman homepage for the list (where I took the MM-List-Name variable from) but again expands into ppl which is the real name of the list. I do not really want to bother you if this simply cannot be done. I know you are very busy. Thanks! -- Zbigniew Szalbot From msapiro at value.net Tue Jan 9 20:15:20 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 12:15:20 -0700 Subject: [Mailman-Users] list name in email Message-ID: <200701091215.AA354812214@mail.value.net> Zbigniew Szalbot wrote: > >> Yes, you made a mistake. You'll probably find tracebacks from the >> exception in Mailman's error log. The problem is the value you have >> assigned to the key 'MM-List-Name' is not a defined variable. You need >> >> 'MM-List-Name' : mlist.real_name, >> >> rather than what you have. > >I applied the correction according to your suggestions, restarted mailman >but no confirmation email is being sent. > >I find this in error log: > > File "/usr/local/mailman/Mailman/MailList.py", line 887, in AddMember > {'email' : email, >NameError: global name 'mlist' is not defined > And I made a mistake too. It should be 'MM-List-Name' : self.real_name, -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan Sent via the KillerWebMail system at mail.value.net From msapiro at value.net Tue Jan 9 20:23:16 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 12:23:16 -0700 Subject: [Mailman-Users] list name in email Message-ID: <200701091223.AA1685192832@mail.value.net> Zbigniew Szalbot wrote > >Thanks a lot. But this does not give me the full name of the list as on >the mailman homepage for the list (where I took the MM-List-Name variable >from) but again expands into ppl which is the real name of the list. Then I'm guessing what you want is the list description (self.description) rather than the list name (self.real_name). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan Sent via the KillerWebMail system at mail.value.net From zbyszek at szalbot.homedns.org Tue Jan 9 20:28:51 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Tue, 9 Jan 2007 20:28:51 +0100 (CET) Subject: [Mailman-Users] list name in email In-Reply-To: <200701091223.AA1685192832@mail.value.net> References: <200701091223.AA1685192832@mail.value.net> Message-ID: <62745.192.168.11.7.1168370931.squirrel@lists.lc-words.com> Hello, >>Thanks a lot. But this does not give me the full name of the list as on >>the mailman homepage for the list (where I took the MM-List-Name variable >>from) but again expands into ppl which is the real name of the list. > > > Then I'm guessing what you want is the list description (self.description) > rather than the list name (self.real_name). Mark - thank you, thank you very much indeed! Can I have one more question? If I ever want to upgrade mailman (currently I have the latest stable version so no problem), can /usr/local/mailman/Mailman/MailList.py be overwritten during upgrade or is it one of those files that don't get updated? Once again, many thanks for your help! Warm regards, -- Zbigniew Szalbot From liquid at nationalcomfortinstitute.com Tue Jan 9 20:39:14 2007 From: liquid at nationalcomfortinstitute.com (liquid at nationalcomfortinstitute.com) Date: Tue, 9 Jan 2007 14:39:14 -0500 Subject: [Mailman-Users] Sender Name in message In-Reply-To: References: <20070108162938.ci6evalwqokc40g0@webmail.nationalcomfortinstitute.com> Message-ID: <20070109143914.lolsbajlogsk8wg4@webmail.nationalcomfortinstitute.com> Quoting Brad Knowles : > At 4:29 PM -0500 1/8/07, liquid at nationalcomfortinstitute.com wrote: > >> I'm running an anonymous discussion list. The list is setup so replies >> are by directed back to the list. >> >> I would like to be able to add the senders/posters name (the >> (optional) name that is in the system) to the header, message or footer. > > > > If the list is anonymous, then doing this kind of thing would eliminate > the anonymity, and therefore presumably violate the basic purpose of > the list. > > Otherwise, don't run it as an anonymous list. > > -- > Brad Knowles, Sorry I guess I should clarify. I have the discussion list set to anonymous. Because I want email sent from the list email and replied back to the list rather than the poster (so every one gets all posts and replies). But I want the senders real name inserted into the header, message, or footer (as a forced signature in a way). It will dummy proof the list. Because the members of the site will forget to sign the email or forget to CC to the list when replying. But it is important to identify the sender. For several reasons, mainly because the members of the list are competing businesses and they will want to know exactly who they are replying to. I know all this defeats the purpose of an anonymous list. But it has to be as easy as possible or the members won't use it. So what ever I can do to insure this will make every thing better. Jeff From dan at thecsl.org Tue Jan 9 21:42:39 2007 From: dan at thecsl.org (Dan MacNeil) Date: Tue, 09 Jan 2007 15:42:39 -0500 Subject: [Mailman-Users] mailman 2.1.5 and Debian upgrades In-Reply-To: <20070109181555.GA2540@patriot.net> References: <20070109181555.GA2540@patriot.net> Message-ID: <45A3FE3F.2010204@thecsl.org> Alan McConnell wrote: > Dear Helpful Experts, I am hardly an expert, though I do aspire to be helpful. > Can I, again, have the Assembled Wisdom(TM) tell me, and > the PatriotNet staff, how to proceed to upgrade the MM > install from 2.1.5 to 2.1.9? By coincidence, we are a tiny ISP for non-profits. Last night we upgraded our mailman/amavis/postfix server to move from mailman 2.1.5 to 2.1.9 (we also moved from Sarge to Etch) # to replace "sarge" with "etch", $EDITOR /etc/apt/sources.list sudo apt-get update; sudo apt-get dist-upgrade --download-only sudo apt-get dist-upgrade; # remove shunt files from mailman As usual, mailman didn't upgrade until I emptied the shunt directory, but the upgrade scripts made it very clear what the issue was. There were no other problems upgrading mailman. The configuration file setup for amavis change so I spent a bit of time moving things around. --I was surprised at how stock our setup was. The big unresolved problem is that rdiff-backup on the Etch machine now can't talk to the backup repository running sarge rdiff-backup > And a few words of wisdom about why this is advisable would also be > appreciated. In our case, an important customer wanted friendly VERP subject lines in confirmation email messages generated in reply to listname-join at lists.orgainzation.org We know we will have to move to Etch some day soon in any event and this was a relatively low risk start. ########## > > Please have patience! I'll try to make this the last revisit of this > subject. > > I am the admin of a four-month old Mailman E-list, running on my ISP, > PatriotNet. > > The people actually responsible for Tech Support at PatriotNet are very > reliant on Debian. They are running Debian Sarge, because that is the > latest "stable" Debian release(coincidentally, so am I, at home). > Debian Sarge provides MM 2.1.5, which Brad and Mark have criticized in > rather scathing terms; unfortunately, I've lost/misplaced the exact > E-mails saying this. > > Can I, again, have the Assembled Wisdom(TM) tell me, and the PatriotNet > staff, how to proceed to upgrade the MM install from 2.1.5 to 2.1.9? > And a few words of wisdom about why this is advisable would also be > appreciated. > > I have spelled out, chapter and verse, all the problems that I have been > having with 2.1.5. But heck, what do I know? I'm just a customer, > and who pays attention to them? > > Again apologies for repeat request, and thanks for your anticipated > assistance. > > A grateful Alan > From msapiro at value.net Tue Jan 9 22:12:19 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 13:12:19 -0800 Subject: [Mailman-Users] Sender Name in message In-Reply-To: <20070109143914.lolsbajlogsk8wg4@webmail.nationalcomfortinstitute.com> Message-ID: liquid at nationalcomfortinstitute.com wrote: > >Sorry I guess I should clarify. I have the discussion list set to >anonymous. Because I want email sent from the list email and replied >back to the list rather than the poster (so every one gets all posts >and replies). But I want the senders real name inserted into the >header, message, or footer (as a forced signature in a way). How about the following settings: anonymous_list = No first_strip_reply_to = Yes reply_goes_to_list = This List If this is not acceptable, then you have to hack the code to do what you want. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From michael.peterson at gmail.com Wed Jan 10 00:20:31 2007 From: michael.peterson at gmail.com (Michael Peterson) Date: Tue, 9 Jan 2007 15:20:31 -0800 Subject: [Mailman-Users] Mailman archive interface.... Message-ID: <77a3ed9e0701091520v39e538e8y1d904d41c9ce1c4c@mail.gmail.com> I've been working on building a search interface to mailman for a client on mine. Since I didn't see one built into the archive system I built one using the Swishe software. So far everything seems to be working fine...with one exception. For private lists if someone run a search and then links into the mailman web interface...you get presented with the login box...which then redirects you to the top level of the directory. Since I already know excatly which post I'm looking for...and that what was supplied via the link...is there any way to get mailman to direct me to the actual page after the login? I think this is a similar issue to having bookmarks to private mailman articles. --Michael From msapiro at value.net Wed Jan 10 00:55:44 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 15:55:44 -0800 Subject: [Mailman-Users] Mailman archive interface.... In-Reply-To: <77a3ed9e0701091520v39e538e8y1d904d41c9ce1c4c@mail.gmail.com> Message-ID: Michael Peterson wrote: >For private lists if someone run a >search and then links into the mailman web interface...you get >presented with the login box...which then redirects you to the top >level of the directory. Since I already know excatly which post I'm >looking for...and that what was supplied via the link...is there any >way to get mailman to direct me to the actual page after the login? > >I think this is a similar issue to having bookmarks to private mailman articles. This is bug #1080943 which was fixed in Mailman 2.1.7. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 10 02:17:45 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 17:17:45 -0800 Subject: [Mailman-Users] list name in email In-Reply-To: <62745.192.168.11.7.1168370931.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: > >If I ever want to upgrade mailman (currently I have the latest >stable version so no problem), can /usr/local/mailman/Mailman/MailList.py >be overwritten during upgrade or is it one of those files that don't get >updated? It is one of the files that definitely does get overwritten in an upgrade even if the upgraded version didn't change. The things that don't get overwritten are list data and archives, site passwords, updated templates installed per , custom handlers , mm_cfg.py, and a few other thing depending on how you count. Pretty much every python module (.py file) gets replaced in an upgrade. For this reason, whenever you change these things, at a minimum you should make a patch file (diff) and keep a log of everything you've changed so you can easily port your changes forward. Better still, if your changes have general applicability, is to take the trouble to read "Python coding style guide for Mailman" (also included in the source distribution as STYLEGUIDE.txt) and to see the wiki at , so you can code your changes in a way that makes them likely to be accepted, and then contribute them back to the project. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at lostwells.net Wed Jan 10 04:14:47 2007 From: vancleef at lostwells.net (Hank van Cleef) Date: Tue, 9 Jan 2007 20:14:47 -0700 (MST) Subject: [Mailman-Users] getting correct alias domain in message headers Message-ID: <200701100314.l0A3ElDo015540@bronze.lostwells.net> I've brought a fresh installation of Mailman 2.1.9 on line on an IP that has been assigned to mydomain.net for some time. However, I want to appear as otherdomain.com. The DNS records for otherdomain.com have been changed to point to my IP, with A records to otherdomain.com and www.otherdomain.com, and an MX record to point to a mydomain.net A record. What I did to handle mail was add othedomain.com to the sendmail cw file (local-host-names). What I see in the headers in a post to the list is: X-BeenThere: mylist at otherdomain.com X-Mailman-Version: 2.1.9 Precedence: list Reply-To: The Mylist Discussion List Sender: mylist-bounces at mydomain.net Errors-To: mylist-bounces at mydomain.net How do I get the correct names (otherdomain.com) in the last three header lines? I've added to mm_cfg.py DEFAULT_EMAIL_HOST = 'otherdomain.com' DEFAULT_URL_HOST = 'www.otherdomain.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (actually, tried the "add_virtualhost" before the redefined defaults before trying it after). The list URL is correct (withlist/fix_url) but the mail headers aren't. How to fix this? Do I need to restart the qrunners? Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Wed Jan 10 04:29:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 9 Jan 2007 19:29:29 -0800 Subject: [Mailman-Users] getting correct alias domain in message headers In-Reply-To: <200701100314.l0A3ElDo015540@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: > >What I see in the headers in a post to the list is: > >X-BeenThere: mylist at otherdomain.com >X-Mailman-Version: 2.1.9 >Precedence: list >Reply-To: The Mylist Discussion List >Sender: mylist-bounces at mydomain.net >Errors-To: mylist-bounces at mydomain.net > >How do I get the correct names (otherdomain.com) in the last three >header lines? > >I've added to mm_cfg.py > >DEFAULT_EMAIL_HOST = 'otherdomain.com' >DEFAULT_URL_HOST = 'www.otherdomain.com' >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > >(actually, tried the "add_virtualhost" before the redefined defaults >before trying it after). The list URL is correct (withlist/fix_url) >but the mail headers aren't. > >How to fix this? Do I need to restart the qrunners? Well, yes. you always need to do a 'bin/mailmanctl restart' after any mm_cfg.py changes that affect mail handling or delivery (but in this case, fix_url is probably sufficient). But, that said, I don't think this is a Mailman issue. Mailman knows the list's email host is otherdomain.com as evidenced by the X-Been-There: header. It is the outgoing MTA that is changing the domain in the other headers to what it thinks is appropriate for external use. I am not an MTA expert, and even if I were, you haven't told me what the MTA is, so I can't help further. This is a question for your MTA support resources. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jdzemke at gmail.com Wed Jan 10 06:05:44 2007 From: jdzemke at gmail.com (Dan and Jodi Zemke) Date: Tue, 9 Jan 2007 23:05:44 -0600 Subject: [Mailman-Users] make issues Message-ID: I have installed and used mailman on suse 8 and am now doing a fresh install (mailman 2.1.9) on suse 9.3 with python 2.5 (I have tried python 2.4 as well) and continue to get the following errors on make and make install. I am installing with the mailman user and group. Any insight about these errors would be greatly appreciated. ./configure --prefix=/usr/local/mailman-2.1.9 make (the last 4 lines of the make) make[1]: Leaving directory `/usr/local/mailman-2.1.9/messages' make[1]: Entering directory `/usr/local/mailman-2.1.9/tests' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/usr/local/mailman-2.1.9/tests' make install (the last 3 lines of the make install) make[1]: *** [install] Error 1 make[1]: Leaving directory `/usr/local/mailman-2.1.9/tests' make: *** [doinstall] Error 2 From ambrose_christopher at yahoo.com Wed Jan 10 12:12:24 2007 From: ambrose_christopher at yahoo.com (AMBROSE CHRISTOPHER) Date: Wed, 10 Jan 2007 03:12:24 -0800 (PST) Subject: [Mailman-Users] Mailman-Users Digest, Vol 35, Issue 14 In-Reply-To: Message-ID: <547239.13918.qm@web50908.mail.yahoo.com> dont u guys think it a bit convrinent that so many things that are unlikely to happen if left to the general percentages are happening ? seems your not seeing the obvious. you got a very smart bug. ____________________________________________________________________________________ Never Miss an Email Stay connected with Yahoo! Mail on your mobile. Get started! http://mobile.yahoo.com/services?promote=mail From webmaster at web-analysts.net Wed Jan 10 15:10:41 2007 From: webmaster at web-analysts.net (Webmaster) Date: Wed, 10 Jan 2007 09:10:41 -0500 Subject: [Mailman-Users] logs no longer working References: Message-ID: <016701c734c1$1c8d8e40$0200a8c0@D4QCJ541> okay I found them. thanks. how can I change their location so fedora's logrotate is integrated? ----- Original Message ----- From: "Mark Sapiro" To: "Webmaster" ; Sent: Tuesday, January 09, 2007 1:07 PM Subject: Re: [Mailman-Users] logs no longer working > Webmaster wrote: > >>I recently upgraded mailman to 2.1.9 and everything seems to >>be working fine except somehow all mailman logging has ceased. >>I am running fedora core 5. my permissions on /var/log are >> >>drwxrwsr-x 2 mailman mailman 4096 Jan 7 04:04 mailman >> >>and in /var/log/mailman are >> >>-rw-rw-r-- 1 mailman mailman 0 Jan 7 04:04 qrunner >> >>I have restarted the service with no difference. suggestions anyone? >>thank you in advance! > > > My first guess is that the logs just aren't where you are looking. The > fact the the dates on /var/log/mailman and /var/log/mailman/qrunner > are current seems to contradict this however. > > Did you upgrade from RedHat RPM or source? > > Have you looked elsewhere? E.g. > > find / -name qrunner -print > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.432 / Virus Database: 268.16.7/620 - Release Date: 1/8/2007 > 4:12 PM > > From msapiro at value.net Wed Jan 10 17:06:28 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 08:06:28 -0800 Subject: [Mailman-Users] logs no longer working In-Reply-To: <016701c734c1$1c8d8e40$0200a8c0@D4QCJ541> Message-ID: Webmaster wrote: >okay I found them. thanks. how can I change their location so fedora's >logrotate is integrated? In mm_cfg.py, set LOG_DIR = '/var/log/mailman' or wherever you want them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 10 17:23:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 08:23:03 -0800 Subject: [Mailman-Users] make issues In-Reply-To: Message-ID: Dan and Jodi Zemke wrote: >Any insight about these >errors would be greatly appreciated. > >./configure --prefix=/usr/local/mailman-2.1.9 Is the directory into which you unpacked the tarball also /usr/local/mailman-2.1.9 ? The directory in which you unpack, configure and make should not be the 'prefix' directory. >make (the last 4 lines of the make) >make[1]: Leaving directory `/usr/local/mailman-2.1.9/messages' >make[1]: Entering directory `/usr/local/mailman-2.1.9/tests' >make[1]: Nothing to be done for `all'. >make[1]: Leaving directory `/usr/local/mailman-2.1.9/tests' > > >make install (the last 3 lines of the make install) >make[1]: *** [install] Error 1 >make[1]: Leaving directory `/usr/local/mailman-2.1.9/tests' >make: *** [doinstall] Error 2 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 10 17:44:55 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 08:44:55 -0800 Subject: [Mailman-Users] getting correct alias domain in message headers In-Reply-To: Message-ID: Mark Sapiro wrote: > >I am not an MTA expert, and even if I were, you haven't told me what >the MTA is, so I can't help further. This is a question for your MTA >support resources. In a brief, off-list exchange, Hank wrote the following: Anyway, I thought I'd post the "fix" for sendmail for the benefit of the next guy (or gal) to ask the question about making the headers come out right on a domain alias with sendmail. Actually, it's spelled out under in detail 4.8.16, pp. 181-182 of the O'Reilly Sendmail "bat book." MASQUERADE_AS(`mydomain.net')dnl FEATURE(`limited_masquerade')dnl LOCAL_DOMAIN(`mydomain.net otherdomain.com')dnl MASQUERADE_DOMAIN(`mydomain.net')dnl That works as long as "otherdomain.com" is in the $=w table as a canonical name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 10 18:27:23 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 09:27:23 -0800 Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu (SOLVED) In-Reply-To: Message-ID: In an off-list exchange regarding an issue previously posted at and , we may have arrived at a solution/work-around. It seems that the basic issue is that the Mailman installation in some Ubuntu distributions is missing the pythonlib/ directory containing the appropriate Python email library. This is intentional on Ubuntu's part. It is a 'bug fix'. In the off-list exchangeI suggested to Rich: >If you wanted to try doing something with this by hand, you could >unpack the email-2.5.7.gz file from the misc directory in the Mailman >2.1.8 distribution. Then, create pythonlib/ in Mailman's installed >prefix directory (probably create /var/lib/mailman/pythonlib/) and >move the email/ directory from the unpacked email-2.5.7/ directory to >pythonlib/. > >Then you will also have to find the installed paths.py files in >Mailman's bin/, cron/ and tests/ directories (although tests/ is not >important unless you actually want to run unit tests). This file >normally contains: > ># Hack the path to include the parent directory of the $prefix/Mailman package ># directory. >sys.path.insert(0, prefix) > ># We also need the pythonlib directory on the path to pick up any overrides of ># standard modules and packages. Note that these must go at the front of the ># path for this reason. >sys.path.insert(0, os.path.join(prefix, 'pythonlib')) > >Yours is probably missing the pythonlib part which should be inserted. > >I don't know if this will fix the problem or not, but you can try. And Rich replied: >My mailman's paths.py still had the code, so they didn't modify the >2.1.8 release I guess, just left out the email stuff. I just unzipped >the email tar, and created the pythonlib dir, and moved the email subdir >into that dir, and everything worked! -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From traderjoe1854 at yahoo.com Wed Jan 10 18:28:03 2007 From: traderjoe1854 at yahoo.com (Trader Joe) Date: Wed, 10 Jan 2007 09:28:03 -0800 (PST) Subject: [Mailman-Users] Email address with trailing space Message-ID: <20070110172803.14286.qmail@web50915.mail.yahoo.com> While doing "mass subscription", I accidently put in an extra space at the end of several email addresses and now I'm unable to unsubscribe or remove these email via Web tools. Anyone know how to remove these? Example: I put the address as "email at server.com " instead of "email at server.com". I really think removing trailing space should be part of mass subscribtion function, since you can't really have space in the email address. Thanks for all the help. -Joe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From msapiro at value.net Wed Jan 10 18:48:30 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 09:48:30 -0800 Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED) In-Reply-To: Message-ID: Mark Sapiro wrote: > >It seems that the basic issue is that the Mailman installation in some >Ubuntu distributions is missing the pythonlib/ directory containing >the appropriate Python email library. This is intentional on Ubuntu's >part. It is a 'bug fix'. Some additional information: This is mailman 2.1.8-2ubuntu2. The reference to the 'bug fix' is at in which is found * Make sure we don't ship /var/lib/mailman/pythonlib, should make that go away on installations which already have it (closes: #242740). (I couldn't find a description of #242740). The above change seems to have been made some time ago, so perhaps the issue is caused by some more recent change to the Ubuntu Python email library. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From chandler at chapman.edu Wed Jan 10 18:53:40 2007 From: chandler at chapman.edu (Jay Chandler) Date: Wed, 10 Jan 2007 09:53:40 -0800 Subject: [Mailman-Users] Email address with trailing space In-Reply-To: <20070110172803.14286.qmail@web50915.mail.yahoo.com> References: <20070110172803.14286.qmail@web50915.mail.yahoo.com> Message-ID: <45A52824.1050905@chapman.edu> Trader Joe wrote: > While doing "mass subscription", I accidently put in > an extra space at the end of several email addresses > and now I'm unable to unsubscribe or remove these > email via Web tools. Anyone know how to remove these? > > You have to escape them, try preceding the space with "\" -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler at chapman.edu Today's Excuse: You did wha... oh _dear_.... From tmz at pobox.com Wed Jan 10 19:08:51 2007 From: tmz at pobox.com (Todd Zullinger) Date: Wed, 10 Jan 2007 13:08:51 -0500 Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED) In-Reply-To: References: Message-ID: <20070110180851.GC13318@psilocybe.teonanacatl.org> Mark Sapiro wrote: > Some additional information: > > This is mailman 2.1.8-2ubuntu2. > > The reference to the 'bug fix' is at > > in which is found > > * Make sure we don't ship /var/lib/mailman/pythonlib, should make that > go away on installations which already have it (closes: #242740). > > (I couldn't find a description of #242740). That looks to be from the Debian Mailman package, which Ubuntu uses as it's base. See the long trail here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242740 The short summary for the bug is "bad installation when /var/lib/mailman/pythonlib is a symlink." (I've never found the Debian bugs page very easy to follow. :) -- Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ====================================================================== Religion. A daughter of Hope and Fear, explaining to Ignorance the nature of the Unknowable. -- Ambrose Bierce, The Enlarged Devil's Dictionary, 1906 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 542 bytes Desc: not available Url : http://mail.python.org/pipermail/mailman-users/attachments/20070110/6716abea/attachment-0001.pgp From msapiro at value.net Wed Jan 10 19:37:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 10:37:41 -0800 Subject: [Mailman-Users] Email address with trailing space In-Reply-To: <20070110172803.14286.qmail@web50915.mail.yahoo.com> Message-ID: Trader Joe wrote: >While doing "mass subscription", I accidently put in >an extra space at the end of several email addresses >and now I'm unable to unsubscribe or remove these >email via Web tools. Anyone know how to remove these? What Mailman version is this? I am unable to duplicate this with any recent Mailman. What exact format did you use for the address? >I really think removing trailing space should be part >of mass subscribtion function, since you can't really >have space in the email address. It is as far as I can tell. Have you tried unsubscribing these by checking the 'unsub' box on the membership list? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From b19141 at britaine.ctd.anl.gov Wed Jan 10 20:26:41 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Wed, 10 Jan 2007 13:26:41 -0600 (CST) Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED) In-Reply-To: Mail from 'Todd Zullinger ' dated: Wed, 10 Jan 2007 13:08:51 -0500 Message-ID: <200701101926.l0AJQf59005645@britaine.ctd.anl.gov> Mark Sapiro wrote: >> Some additional information: >> >> This is mailman 2.1.8-2ubuntu2. >> >> The reference to the 'bug fix' is at >> >> in which is found >> >> * Make sure we don't ship /var/lib/mailman/pythonlib, should make that >> go away on installations which already have it (closes: #242740). >> >> (I couldn't find a description of #242740). and Todd Zullinger replied: >That looks to be from the Debian Mailman package, which Ubuntu uses as >it's base. See the long trail here: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=242740 > The short summary for the bug is "bad installation when >/var/lib/mailman/pythonlib is a symlink." > >(I've never found the Debian bugs page very easy to follow. :) I read the entire bug page trail, and I am trying to understand it. I looked at my 2.1.9 source test installation (on Solaris 10, where I installed into /opt/mailman), and I see things in the /opt/mailman/pythonlib directory. What is the purpose of the files found therein? If these are needed by Mailman, how can Ubuntu/Debian not supply them? I am trying to understand what is happening (so that I can convince others here that I need to install from the source and not from the Ubuntu package). ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From barry at python.org Wed Jan 10 20:42:28 2007 From: barry at python.org (Barry Warsaw) Date: Wed, 10 Jan 2007 14:42:28 -0500 Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED) In-Reply-To: <200701101926.l0AJQf59005645@britaine.ctd.anl.gov> References: <200701101926.l0AJQf59005645@britaine.ctd.anl.gov> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 10, 2007, at 2:26 PM, Barry Finkel wrote: > I read the entire bug page trail, and I am trying to understand it. > I looked at my 2.1.9 source test installation (on Solaris 10, where I > installed into /opt/mailman), and I see things in the > > /opt/mailman/pythonlib > > directory. What is the purpose of the files found therein? If these > are needed by Mailman, how can Ubuntu/Debian not supply them? I am > trying to understand what is happening (so that I can convince > others here that I need to install from the source and not from the > Ubuntu package). The only reason I can think for U/D to not include that directory is that they are sure that the Python they depend Mailman on already has the email package and codecs that live in pythonlib. The purpose of pythonlib is to provide compatibility between Python versions which might have older versions of the email lib or might be missing the codecs. It's not strictly required to have pythonlib, and should be possible to run without it, but I'm not sure why you would, unless you feel that you're tracking patches in the dependent packages better than the Mailman project is. I don't see how it can hurt to have the pythonlib that Mailman normally installs. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRaVBqXEjvBPtnXfVAQK4AgQAkXT+v8zv1jfHbSZctub+lvdCCFnilOED LzNFAITHjvIwLdU01cC+O5lGKksU3tMH7yZsXHjI24DrXws4txBzuR7WXqwzWFEW PvsvX+LFNUCXemLKGUnjkewU2fcLD+BJnWRX9ZfewPpWsq50K0BReUlCybigRkKt /oGscZtR0kk= =gTi9 -----END PGP SIGNATURE----- From pc2a at pi4cc.nl Wed Jan 10 20:58:56 2007 From: pc2a at pi4cc.nl (Peter) Date: Wed, 10 Jan 2007 19:58:56 +0000 Subject: [Mailman-Users] Private archive access Message-ID: <45A54580.2020002@pi4cc.nl> Hello Just an question about access to a private archive.I n the past I run an archive that was protected via htaccees. With a user name and password every one has the access to the archive. With mailman and its archiver (nice by the way) the directory is protected via the users email adress and user password. Is there a work-a-round to skip the "standard" access? running version 2.1.9-4 Peter From kelly.terry.jones at gmail.com Wed Jan 10 21:06:55 2007 From: kelly.terry.jones at gmail.com (Kelly Jones) Date: Wed, 10 Jan 2007 13:06:55 -0700 Subject: [Mailman-Users] Recovering a config.pck file from the output of dumpdb Message-ID: <26face530701101206y70d64b9fse982bf980c1aa2b0@mail.gmail.com> I backup my mailman config.pck files nightly by running "dumpdb config.pck" and storing the output (the output of dumpdb is easier to read and easier to diff [for CVS'd backups] than the config.pck file itself). How do I get back config.pck from the output of dumpdb? In other words, what command does the opposite/inverse of dumpdb? -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. From msapiro at value.net Wed Jan 10 22:30:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 13:30:14 -0800 Subject: [Mailman-Users] Recovering a config.pck file from the output ofdumpdb In-Reply-To: <26face530701101206y70d64b9fse982bf980c1aa2b0@mail.gmail.com> Message-ID: Kelly Jones wrote: >I backup my mailman config.pck files nightly by running "dumpdb >config.pck" and storing the output (the output of dumpdb is easier to >read and easier to diff [for CVS'd backups] than the config.pck file >itself). > >How do I get back config.pck from the output of dumpdb? > >In other words, what command does the opposite/inverse of dumpdb? There is no command to create the config.pck from the output of dumpdb. The output of dumpdb of a config.pck is basically a dictionary representation where the keys are the names of all the list attributes and the values are the respective values. If you were to take a dumpdb output that looks something like [----- start pickle file -----] <----- start object 1 -----> { 'accept_these_nonmembers': ['msapiro at value.net'], 'acceptable_aliases': '\n', 'admin_immed_notify': True, 'admin_member_chunksize': 30, 'admin_notify_mchanges': 1, 'admin_responses': {}, ... 'welcome_msg': ''} [----- end pickle file -----] and edit it to make something like mlist.accept_these_nonmembers = ['msapiro at value.net'] mlist.acceptable_aliases = '\n' mlist.admin_immed_notify = True mlist.admin_member_chunksize = 30 mlist.admin_notify_mchanges = 1 mlist.admin_responses = {} ... mlist.welcome_msg = '' you could use that as input to bin/config_list. Alternatively, you could make it into a withlist script that would look something like: def undumpdb(mlist): x = { 'accept_these_nonmembers': ['msapiro at value.net'], 'acceptable_aliases': '\n', 'admin_immed_notify': True, 'admin_member_chunksize': 30, 'admin_notify_mchanges': 1, 'admin_responses': {}, ... 'welcome_msg': ''} for key in x.keys(): mlist.__dict__[key] = x[key] mlist.Save() -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 10 22:32:58 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 10 Jan 2007 13:32:58 -0800 Subject: [Mailman-Users] Private archive access In-Reply-To: <45A54580.2020002@pi4cc.nl> Message-ID: Peter wrote: > >Just an question about access to a private archive.I n the past I run an >archive that was protected via htaccees. >With a user name and password every one has the access to the archive. >With mailman and its archiver (nice by the way) the directory is >protected via the users email adress and user password. >Is there a work-a-round to skip the "standard" access? Make the archive public and control access with .htaccess as before. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Rtdos at aol.com Thu Jan 11 14:41:02 2007 From: Rtdos at aol.com (Rtdos at aol.com) Date: Thu, 11 Jan 2007 08:41:02 EST Subject: [Mailman-Users] mail2news gateway question Message-ID: I'm trying to locate information on the mail2news gateway that's available in Mailman but I"m not sure where to look; I correctly am able to get messages made to my list to post to usenet, but am unable to get messages posted to usenet mailed to my list; i do have the hostname and groupname correctly set, both posts to the mailing list and posts to the newsgroup are checked as yes; the groups are not moderated (comp.sys.atari.8bit for example); anything else? Is it something on the server side (news.rtdos.com) that needs to be changed ? -Jeff Wood http://www.rtdos.com From cheema at cheema.com Thu Jan 11 14:45:01 2007 From: cheema at cheema.com (Mubashir Cheema) Date: Thu, 11 Jan 2007 05:45:01 -0800 Subject: [Mailman-Users] Uncaught bounce notifications stop working Message-ID: <20070111134501.GA10657@home.cheema.com> I have a strange problem with a mailman installation on a new server that I have not experienced before. Sometimes mailman will forward me bounced emails that it cannot process automatically. Other times mailman's bounce processer seems to get stuck. It accumulates these emails until I restart the server. Then it sends me hundreds of these. I have not been able to figure out why it gets stuck. I have been unsuccessful in reproducing the problem. My setup: OS: Redhat Linux Fedora Core 5 Mailman version: 2.1.5 Has anybody else had similar trouble before? Google cant find anything relevant. Any ideas in troubleshooting this would be much appreciated. Thanks. Mubashir Cheema cheema at cheema.com From msapiro at value.net Thu Jan 11 17:07:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 08:07:17 -0800 Subject: [Mailman-Users] mail2news gateway question In-Reply-To: Message-ID: Rtdos at aol.com wrote: > >... am unable to get messages posted to >usenet mailed to my list; Is Mailman's crontab running cron/gate_news (default every 5 minutes)? This is what gets usenet posts back to Mailman. >Is it something on the server side (news.rtdos.com) that needs to be changed? No. You shouldn't need to do anything on the news server. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 11 17:12:18 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 08:12:18 -0800 Subject: [Mailman-Users] Uncaught bounce notifications stop working In-Reply-To: <20070111134501.GA10657@home.cheema.com> Message-ID: ----- Original Message --------------- Subject: [Mailman-Users] Uncaught bounce notifications stop working From: Mubashir Cheema Date: Thu, 11 Jan 2007 05:45:01 -0800 To: mailman-users at python.org > >I have a strange problem with a mailman installation on a new server that I have not experienced before. Sometimes mailman will forward me bounced emails that it cannot process automatically. Other times mailman's bounce processer seems to get stuck. It accumulates these emails until I restart the server. Then it sends me hundreds of these. I have not been able to figure out why it gets stuck. I have been unsuccessful in reproducing the problem. It seems that perhaps BounceRunner is dying so the bounces are queued but not processed until you restart. Check Mailman's 'qrunner' and 'error' logs for clues as to why this is happening. Possibly some malformed spam is being sent to the -bounces address and causing problems for BounceRunner. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pdbogen at gmail.com Thu Jan 11 18:14:32 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 11 Jan 2007 11:14:32 -0600 Subject: [Mailman-Users] (no subject) In-Reply-To: <821AB4E5068CAB43A2539D4DD81F38E303CD3D2B@SAMFORDMAIL.ad.samford.edu> References: <821AB4E5068CAB43A2539D4DD81F38E303CD3D2B@SAMFORDMAIL.ad.samford.edu> Message-ID: <6fbe3da00701110914k3298af5eudde0508fc9a85fd9@mail.gmail.com> On 1/3/07, Whitcomb, Jeff wrote: > When someone sends an email with a read receipt request to a list that I > own, I get a lot of uncaught bounce notifications (I have attached one > for reference). I am wondering if there is any way I can stop getting > all these Read Receipt messages when people send an email to a Mailman > list, without turning off bounce processing all together. I tried just > filtering them in Outlook, but you can't filter on an attachment name. > I do currently have all of the bounce notifications going to a folder, > but would like to either stop getting these particular ones, or be able > to further filter them into another folder. This sounds like it should really be a user education issue; convince your users to stop sending 'read receipt' requests. If that won't work, it might be possible to put together some filter rules to hold or reject messages with these requests included; although this is really just a way to reinforce the idea that they shouldn't be sending them. -- - Patrick Bogen From badams at ambrosiasw.com Thu Jan 11 18:36:16 2007 From: badams at ambrosiasw.com (Adams Benjamin) Date: Thu, 11 Jan 2007 12:36:16 -0500 Subject: [Mailman-Users] narrowed down email not being sent Message-ID: <66EBB94D-9D2D-4709-B6A8-6A2F339818D2@ambrosiasw.com> I have it narrowed down to if there are two email addresses or more that the email is being sent to it will not be sent. Ben From badams at ambrosiasw.com Thu Jan 11 18:20:33 2007 From: badams at ambrosiasw.com (Adams Benjamin) Date: Thu, 11 Jan 2007 12:20:33 -0500 Subject: [Mailman-Users] mailman address as cc I get bounce Message-ID: <21ACE49F-B432-445B-AB9C-A35F58D72C6E@ambrosiasw.com> if I send an email to an address and also a mailing list, the email is just sent to the user and the email is not sent to the mailing list. The email dose get posted. Ben From msapiro at value.net Thu Jan 11 18:59:55 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 09:59:55 -0800 Subject: [Mailman-Users] mailman address as cc I get bounce In-Reply-To: <21ACE49F-B432-445B-AB9C-A35F58D72C6E@ambrosiasw.com> Message-ID: Adams Benjamin wrote: >if I send an email to an address and also a mailing list, the email >is just sent to the user and the email is not sent to the mailing >list. The email dose get posted. I am trying to understand the above and correlate it with the subject, and I am totally confused. How do I resolve "the email is not sent to the mailing list" and "The email dose get posted". What is the 'bounce'. Please try to be more specific. If you are saying that if a post contains a Cc: to user at example.com and user at example.com is a member of the list, then user at example.com does not receive the post from the list, this is the expected behavior if user at example.com has the 'nodupes' option selected. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 11 19:02:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 10:02:49 -0800 Subject: [Mailman-Users] narrowed down email not being sent In-Reply-To: <66EBB94D-9D2D-4709-B6A8-6A2F339818D2@ambrosiasw.com> Message-ID: Adams Benjamin wrote: >I have it narrowed down to if there are two email addresses or more >that the email is being sent to it will not be sent. Are you saying that if a list has one member, posts are delivered to that member, but if it has two or more members, no posts are delivered? Please try to give explicit examples of what's happening so we can understand. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From badams at ambrosiasw.com Thu Jan 11 20:59:35 2007 From: badams at ambrosiasw.com (Adams Benjamin) Date: Thu, 11 Jan 2007 14:59:35 -0500 Subject: [Mailman-Users] narrowed down email not being sent In-Reply-To: References: Message-ID: This is how I send: To:email1 at address.com (not on mailing list) cc:email2 at mailinglist.com email1 gets the email, but no subject change email2 - the mailing list doesn't get the email Now watching logs I see: Jan 11 12:55:17 xanadu postfix/local[15561]: EC3F9163F1A: to=, relay=local, delay=1, status=sent (delivered to command: /usr/share/mailman/mail/mailman post mailman_test) Jan 11 12:55:18 xanadu postfix/qmgr[29123]: AD6B2163F1F: from=, size=2151, nrcpt=1 (queue active) Jan 11 12:55:19 xanadu postfix/pickup[14237]: 07013163F2E: uid=77 from= Jan 11 12:55:19 xanadu postfix/qmgr[29123]: 07013163F2E: from=, size=2262, nrcpt=1 (queue active) example2: to:email2 at mailing.com email is sent out fine On Jan 11, 2007, at 1:02 PM, Mark Sapiro wrote: > Adams Benjamin wrote: > >> I have it narrowed down to if there are two email addresses or more >> that the email is being sent to it will not be sent. > > > Are you saying that if a list has one member, posts are delivered to > that member, but if it has two or more members, no posts are > delivered? > > Please try to give explicit examples of what's happening so we can > understand. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From msapiro at value.net Thu Jan 11 21:29:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 12:29:41 -0800 Subject: [Mailman-Users] narrowed down email not being sent In-Reply-To: Message-ID: Adams Benjamin wrote: >This is how I send: >To:email1 at address.com (not on mailing list) >cc:email2 at mailinglist.com > >email1 gets the email, but no subject change as expected >email2 - the mailing list doesn't get the email Does the mail reach the list archives? What's in Mailman's logs? What's in Mailman's qfiles/? See . >Now watching logs I see: >Jan 11 12:55:17 xanadu postfix/local[15561]: EC3F9163F1A: >to=, relay=local, delay=1, status=sent >(delivered to command: /usr/share/mailman/mail/mailman post >mailman_test) The mail was delivered to Mailman. >Jan 11 12:55:18 xanadu postfix/qmgr[29123]: AD6B2163F1F: >from=, size=2151, nrcpt=1 (queue >active) Mailman sent something to one recipient possibly an owner notice to mailman_test-owner at example.com. >Jan 11 12:55:19 xanadu postfix/pickup[14237]: 07013163F2E: uid=77 >from= >Jan 11 12:55:19 xanadu postfix/qmgr[29123]: 07013163F2E: >from=, size=2262, nrcpt=1 (queue >active) Following the above guess, this might be Mailman sending the the -owner mail to the actual owner, but I don't see a (delivered to command: /usr/share/mailman/mail/mailman owner mailman_test), so I don't know what's going on. Where are the mail log entries showing what was done with the all this mail from Mailman? What is in Mailman's vette, post, smtp and smtp-failure logs -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From fholson at cohousing.org Fri Jan 12 02:01:46 2007 From: fholson at cohousing.org (Fred H Olson) Date: Thu, 11 Jan 2007 17:01:46 -0800 (PST) Subject: [Mailman-Users] Domain name in lists sub directory Message-ID: I've recently subscribed to a couple new lists that are hosted on recent versions of Mailman running at different ISPs. I dont manage these lists. I note that the domain name of both lists is encoded in the sub directory for the list. Both also happen to have long domain names. Combined this makes for some rather long URLs or archived messages for example. Below are the URLs of the Info page, archives, and an archived message for the two lists. The lists I manage and most others I've noticed only have the list name as the subdirectory name. Is this a change or an artifact of their installation? Why the difference? ver 2.1.9.cp2 http://mail.minneapolisbikes.org/mailman/listinfo/advocate_minneapolisbikes.org/ http://mail.minneapolisbikes.org/pipermail/advocate_minneapolisbikes.org/ http://mail.minneapolisbikes.org/pipermail/advocate_minneapolisbikes.org/2007-January/000004.html or http://gold.whbdns.com/mailman/listinfo/advocate_minneapolisbikes.org/ http://gold.whbdns.com/pipermail/advocate_minneapolisbikes.org/ http://gold.whbdns.com/pipermail/advocate_minneapolisbikes.org/2007-January/000004.html version 2.1.7.cp2 http://mail.willard-homewood.org/mailman/listinfo/whomail_willard-homewood.org/ http://mail.willard-homewood.org/mailman/private/whomail_willard-homewood.org/ http://mail.willard-homewood.org/mailman/private/whomail_willard-homewood.org/2007-January/000034.html Fred -- Fred H. Olson Minneapolis,MN 55411 USA (near north Mpls) Communications for Justice - My new listserv org. UU, Linux My Link Page: http://fholson.cohousing.org Ham radio:WB0YQM fholson at cohousing.org 612-588-9532 (7am-10pm Central time) From msapiro at value.net Fri Jan 12 02:11:33 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 17:11:33 -0800 Subject: [Mailman-Users] Domain name in lists sub directory In-Reply-To: Message-ID: Fred H Olson wrote: > >The lists I manage and most others I've noticed only have the list name as >the subdirectory name. Is this a change or an artifact of their >installation? Why the difference? The Mailman versions with the domain in the list name are cPanel modified Mailman. This is done by cPanel to allow a single Mailman instance to support lists with the same name on different virtual hosts. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From andrey at chevron.com Fri Jan 12 02:39:09 2007 From: andrey at chevron.com (Yevtikhov, Andrey) Date: Thu, 11 Jan 2007 17:39:09 -0800 Subject: [Mailman-Users] How to reset user password ??? Message-ID: <848EA12A294D2148975B3E3AFD9D5254F46F40@CHVPKNTXC2MD.chvpk.chevrontexaco.net> Hello I am running version 2.1.5 . How I can reset user password ? Tnanx in advance From msapiro at value.net Fri Jan 12 02:57:08 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 11 Jan 2007 17:57:08 -0800 Subject: [Mailman-Users] How to reset user password ??? In-Reply-To: <848EA12A294D2148975B3E3AFD9D5254F46F40@CHVPKNTXC2MD.chvpk.chevrontexaco.net> Message-ID: Yevtikhov, Andrey wrote: >Hello I am running version 2.1.5 . How I can reset user password ? Which user password? If you are talking about the list admin or moderator passwords, see . If you are talking about a member password, see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cheema at cheema.com Fri Jan 12 11:40:17 2007 From: cheema at cheema.com (Mubashir Cheema) Date: Fri, 12 Jan 2007 02:40:17 -0800 Subject: [Mailman-Users] Uncaught bounce notifications stop working In-Reply-To: References: <20070111134501.GA10657@home.cheema.com> Message-ID: <20070112104017.GA12426@home.cheema.com> It appears that BounceRunner was indeed dying and I was suffering from this bug: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1394696&group_id=103 I have upgraded my mailman installation to v 2.1.9 and hope that this will fix the problem. Thanks. -Cheema On Thu, Jan 11, 2007 at 08:12:18AM -0800, Mark Sapiro wrote: > > > ----- Original Message --------------- > > Subject: [Mailman-Users] Uncaught bounce notifications stop working > From: Mubashir Cheema > Date: Thu, 11 Jan 2007 05:45:01 -0800 > To: mailman-users at python.org > > > > >I have a strange problem with a mailman installation on a new server that I have not experienced before. Sometimes mailman will forward me bounced emails that it cannot process automatically. Other times mailman's bounce processer seems to get stuck. It accumulates these emails until I restart the server. Then it sends me hundreds of these. I have not been able to figure out why it gets stuck. I have been unsuccessful in reproducing the problem. > > > It seems that perhaps BounceRunner is dying so the bounces are queued > but not processed until you restart. > > Check Mailman's 'qrunner' and 'error' logs for clues as to why this is > happening. Possibly some malformed spam is being sent to the -bounces > address and causing problems for BounceRunner. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From pmatulis at sympatico.ca Sat Jan 13 05:45:53 2007 From: pmatulis at sympatico.ca (Peter Matulis) Date: Fri, 12 Jan 2007 23:45:53 -0500 Subject: [Mailman-Users] advice on mailman migration Message-ID: <200701122345.53405.pmatulis@sympatico.ca> I have inherited a complex linux server running vserver. It has a mailman server in there and I would like to migrate mailman to another machine. I am looking for advice on how to proceed. Peter From msapiro at value.net Sat Jan 13 06:36:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 12 Jan 2007 21:36:03 -0800 Subject: [Mailman-Users] advice on mailman migration In-Reply-To: <200701122345.53405.pmatulis@sympatico.ca> Message-ID: Peter Matulis wrote: >I have inherited a complex linux server running vserver. It has a >mailman server in there and I would like to migrate mailman to another >machine. I am looking for advice on how to proceed. 1) Install the same or a more recent Mailman on the new machine. 2) See for information on moving the lists to the new host. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at deering.id.au Sun Jan 14 00:13:32 2007 From: geoff at deering.id.au (Geoff Deering) Date: Sun, 14 Jan 2007 10:13:32 +1100 Subject: [Mailman-Users] Problems with Subject Generated via Invites Message-ID: <45A9679C.4060000@deering.id.au> Hi, A few months back I moved one lot of subscriptions to a new site and list (used as an announce list) and invited people to subscribe. Very few people took this up, and after a poorly attended major event I got a lot of feedback that people who thought they had subscribed found out they missed it and were not subscribed. I recently reissued the invite as clearly as possible. The main problem is the Subject line, Mailman does not allow a subject header to introduce the invite. With the amount of spam around these days users can't be blamed for deleting Subject lines such as 'confirm 33f514b7210cb6bea0cdfd9fa0a1d273b5266177' . At first glance it looks like any old spammer phishing for login information. Is it possible to modify the mass mailout subscribe/invite so there is a custom subject header? ------------ Geoff Deering ....................................... Hello Geoff, I'm writing to you to let you know that I am happy to continue receiving your 'announcements' but I ask that you place meaningful text in the Subject line of your emails. The email I received today had this in the subject line: 'confirm 33f514b7210cb6bea0cdfd9fa0a1d273b5266177' At first glance, I almost deleted the email before opening it because I thought it contained viruses. So, this email to ask that you refrain from using meaningless words in the title of your emails, as one is likely to not open it in the first place. Thanks for your attention. Warm regards, Gabriella Sanelli From msapiro at value.net Sun Jan 14 00:56:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 13 Jan 2007 15:56:17 -0800 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: <45A9679C.4060000@deering.id.au> Message-ID: Geoff Deering wrote: >. At first glance it looks like any old spammer phishing for login >information. Is it possible to modify the mass mailout subscribe/invite >so there is a custom subject header? If you set VERP_CONFIRMATIONS = Yes in mm_cfg.py, the subject will be "You have been invited to join the mailing list", and the confirm token will be embedded in the From: address as in From: listname-confirm+23a6e1fdf979dd223e7466e95deb10f486ba3b79 at example.com This requires that your incoming MTA recognizes that the "+token" suffix in the local part is in fact a suffix and deliver a reply as if addressed to listname-confirm at example.com. You have some control over the form of this with the mm_cfg.py settings for VERP_CONFIRM_FORMAT and VERP_CONFIRM_REGEXP, but many MTA's will do the right thing without your having to adjust anything. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at deering.id.au Sun Jan 14 01:36:47 2007 From: geoff at deering.id.au (Geoff Deering) Date: Sun, 14 Jan 2007 11:36:47 +1100 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: References: Message-ID: <45A97B1F.6000800@deering.id.au> Thanks for clarifying that Mark. That's good, but I still think it has a basic interface problem if one is not aware of these features and is just running a standard mail list. It can be quite a problem for the average moderator. Regards Geoff Mark Sapiro said the following on 14/01/2007 10:56 AM: > Geoff Deering wrote: > >> . At first glance it looks like any old spammer phishing for login >> information. Is it possible to modify the mass mailout subscribe/invite >> so there is a custom subject header? >> > > > If you set > > VERP_CONFIRMATIONS = Yes > > in mm_cfg.py, the subject will be "You have been invited to join the > mailing list", and the confirm token will be embedded in > the From: address as in > > From: > listname-confirm+23a6e1fdf979dd223e7466e95deb10f486ba3b79 at example.com > > This requires that your incoming MTA recognizes that the "+token" > suffix in the local part is in fact a suffix and deliver a reply as if > addressed to listname-confirm at example.com. > > You have some control over the form of this with the mm_cfg.py settings > for VERP_CONFIRM_FORMAT and VERP_CONFIRM_REGEXP, but many MTA's will > do the right thing without your having to adjust anything. > > From msapiro at value.net Sun Jan 14 01:55:21 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 13 Jan 2007 16:55:21 -0800 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: <45A97B1F.6000800@deering.id.au> Message-ID: Geoff Deering wrote: >Thanks for clarifying that Mark. That's good, but I still think it has >a basic interface problem if one is not aware of these features and is >just running a standard mail list. It can be quite a problem for the >average moderator. I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting. It defaults to No rather than Yes, because that is the 'safer' setting because some MTA's will not be configured to handle the reply address with confirmation token appended. Granted, many people will install Mailman and run it "out of the box" without reading documentation or exploring site options, but there's not much we can do about that. The installation manual suggests that the installer should review Defaults.py which is extensively commented and make any desired site changes in mm_cfg.py. If you have any specific suggestions for making people do this or making the optional features more visible, please let us know what they are. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at deering.id.au Sun Jan 14 04:00:18 2007 From: geoff at deering.id.au (Geoff Deering) Date: Sun, 14 Jan 2007 14:00:18 +1100 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: References: Message-ID: <45A99CC2.9030806@deering.id.au> Mark Sapiro said the following on 14/01/2007 11:55 AM: > I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting. > It defaults to No rather than Yes, because that is the 'safer' setting > because some MTA's will not be configured to handle the reply address > with confirmation token appended. > > Granted, many people will install Mailman and run it "out of the box" > without reading documentation or exploring site options, but there's > not much we can do about that. > > The installation manual suggests that the installer should review > Defaults.py which is extensively commented and make any desired site > changes in mm_cfg.py. If you have any specific suggestions for making > people do this or making the optional features more visible, please > let us know what they are. > > I can see what you are saying, and the software designers have at least provided such options, but so many people are seeing a web interface and expecting that they should be able to manage all the configuration that regard interfacing with their users from there. I think as much as possible user configuration options should be available in the admin web interface. I hope if is considered for future versions. ------- Geoff From ptomblin at xcski.com Sun Jan 14 05:12:08 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Sat, 13 Jan 2007 23:12:08 -0500 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: <45A99CC2.9030806@deering.id.au> References: <45A99CC2.9030806@deering.id.au> Message-ID: <20070114041208.GA25127@allhats.xcski.com> Quoting Geoff Deering (geoff at deering.id.au): > Mark Sapiro said the following on 14/01/2007 11:55 AM: > > I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting. > > It defaults to No rather than Yes, because that is the 'safer' setting > > because some MTA's will not be configured to handle the reply address > > with confirmation token appended. > > I can see what you are saying, and the software designers have at least > provided such options, but so many people are seeing a web interface and > expecting that they should be able to manage all the configuration that > regard interfacing with their users from there. I think as much as > possible user configuration options should be available in the admin web > interface. I hope if is considered for future versions. The problem as I see it is that people who only configure lists through a web interface are unlikely to have the knowledge of the mail transport agent (MTA) to know if setting VERP_CONFIRMATIONS will work or not. It's only if you're an all-round system administrator who configured the MTA or who has access to the configuration of the MTA that you can safely say for sure whether VERP_CONFIRMATIONS will work or not. -- Paul Tomblin http://blog.xcski.com/ I tried staying in during a fire alarm some years ago. Unfortunately the fire warden wouldn't accept 'A real hacker goes down with his newsfeed' as an excuse. -- Peter Gutman From emmexx at tiscalinet.it Sun Jan 14 09:52:43 2007 From: emmexx at tiscalinet.it (emmexx) Date: Sun, 14 Jan 2007 09:52:43 +0100 Subject: [Mailman-Users] Compulsory username when subscribing Message-ID: <45A9EF5B.8010002@tiscalinet.it> Is it possible to make the username field compulsory when subscribing by web page? Thank you maxx p.s. I can't access the server files From geoff at deering.id.au Sun Jan 14 12:32:58 2007 From: geoff at deering.id.au (Geoff Deering) Date: Sun, 14 Jan 2007 22:32:58 +1100 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: <20070114041208.GA25127@allhats.xcski.com> References: <45A99CC2.9030806@deering.id.au> <20070114041208.GA25127@allhats.xcski.com> Message-ID: <45AA14EA.4010402@deering.id.au> Paul Tomblin said the following on 14/01/2007 3:12 PM: > The problem as I see it is that people who only configure lists through a > web interface are unlikely to have the knowledge of the mail transport > agent (MTA) to know if setting VERP_CONFIRMATIONS will work or not. It's > only if you're an all-round system administrator who configured the MTA or > who has access to the configuration of the MTA that you can safely say > for sure whether VERP_CONFIRMATIONS will work or not. > The other problem is that a lot of people don't have this access, like those who have accounts with only CPanel access or DreamHost without shell access, etc. These people rely purely on a web interface for all their sysconfig. ----------- Geoff From Rtdos at aol.com Sun Jan 14 18:51:04 2007 From: Rtdos at aol.com (Rtdos at aol.com) Date: Sun, 14 Jan 2007 12:51:04 EST Subject: [Mailman-Users] from address Message-ID: ok, i got the mail2news gateway figured out, but now when somone posts to the list it shows up in the from field as the short description of the list rather than the usersname (both in email and in usenet); how can i correct this so that the from field shows the usersname instead? Jeff _http://www.aimpages.com/rtdos/profile.html_ (http://www.aimpages.com/rtdos/profile.html) _http://rtdos.com/mailman/listinfo_ (http://rtdos.com/mailman/listinfo) From msapiro at value.net Sun Jan 14 18:57:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 14 Jan 2007 09:57:14 -0800 Subject: [Mailman-Users] Problems with Subject Generated via Invites In-Reply-To: <45AA14EA.4010402@deering.id.au> Message-ID: Geoff Deering wrote: >Paul Tomblin said the following on 14/01/2007 3:12 PM: >> The problem as I see it is that people who only configure lists through a >> web interface are unlikely to have the knowledge of the mail transport >> agent (MTA) to know if setting VERP_CONFIRMATIONS will work or not. It's >> only if you're an all-round system administrator who configured the MTA or >> who has access to the configuration of the MTA that you can safely say >> for sure whether VERP_CONFIRMATIONS will work or not. >> > >The other problem is that a lot of people don't have this access, like >those who have accounts with only CPanel access or DreamHost without >shell access, etc. These people rely purely on a web interface for all >their sysconfig. That is correct, but if you are suggesting that VERP_CONFIRMATIONS be made an option available to list owners via the web interface, it isn't going to happen because it isn't safe to do so. The typical cPanel or Dreamhost list owner doesn't know if the VERP like confirmations are going to work or not, and if they don't, the list owner only finds out after breaking the list. If we could guarantee that VERP_CONFIRMATIONS would always work, it wouldn't be an option; it would just be the way it worked. Thus, we give the site administration the ability to select this option if it will work in their environment, and we don't make it the default because if we did it would be a limitation on Mailman's ability to run successfully out of the box. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at cww.org.uk Sun Jan 14 19:05:47 2007 From: peter at cww.org.uk (Peter Edley) Date: Sun, 14 Jan 2007 18:05:47 -0000 Subject: [Mailman-Users] Reply emails Message-ID: Hi there folks Got my lists up and running fine, but just one question is it possible to force reply to both list and user, i can get one or the other easily enough, and both if the sender has set the reply to address within their email client,but not if only their from address is set, but would like both to listed when i click reply to button. Peter Edley From ptomblin at xcski.com Sun Jan 14 19:22:12 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Sun, 14 Jan 2007 13:22:12 -0500 Subject: [Mailman-Users] Reply emails In-Reply-To: References: Message-ID: <20070114182212.GA28131@allhats.xcski.com> Quoting Peter Edley (peter at cww.org.uk): > Got my lists up and running fine, but just one question is > it possible to force reply to both list and user, i can get one or the other > easily enough, and both if the sender has set the reply to address within > their email client,but not if only their from address is set, but would like > both to listed when i click reply to button. If a message has two Reply-To addresses, then some mail user agents (MUAs) will send the reply to both addresses, but some wont, so putting a Reply-To for the list and another for the user may or may not do what you want, depending who is replying. -- Paul Tomblin http://blog.xcski.com/ Things which do you no good in aviation: Altitude above you. Runway behind you. Fuel in the truck. Half a second ago. Approach plates in the car. The airspeed you don't have. From msapiro at value.net Sun Jan 14 20:32:43 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 14 Jan 2007 11:32:43 -0800 Subject: [Mailman-Users] from address In-Reply-To: Message-ID: Rtdos at aol.com wrote: >ok, i got the mail2news gateway figured out, but now when somone posts to >the list it shows up in the from field as the short description of the list >rather than the usersname (both in email and in usenet); how can i correct this >so that the from field shows the usersname instead? It seems that you may have General Options->anonymous_list set to Yes. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jan 14 23:36:30 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 14 Jan 2007 14:36:30 -0800 Subject: [Mailman-Users] Compulsory username when subscribing In-Reply-To: <45A9EF5B.8010002@tiscalinet.it> Message-ID: emmexx wrote: >Is it possible to make the username field compulsory when subscribing by >web page? > >Thank you > maxx > >p.s. I can't access the server files Then the answer is No. You would have to modify the script that processes the form. You can edit the template for the list's listinfo page via the admin web interface. You could do things like remove the "(optional)" notation from the "Your name" entry, but given the way the form is created from the template, I don't think you could actually require an entry in that field. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From smueller at merrymtg.com Mon Jan 15 17:54:57 2007 From: smueller at merrymtg.com (Steve Mueller - Merrymeeting, Inc.) Date: Mon, 15 Jan 2007 11:54:57 -0500 Subject: [Mailman-Users] error when going to list admin url Message-ID: <200701151650.l0FGoTK4015678@mailsvr01.frontieradjusters.com> Hi all - Sorry if this is a 'newbie' question but I've searched the archives and can't find an exact match/resolution to the issue I'm having. Here's my story - I've installed Mailman with, at least seemingly, no issues. I've run check_perms and all checked out ok. I was able to create a list from the command line and I received the email indicating that the list had been created which also included the url's to the admin and user frontend for the list. However, when I click on the admin URL I get the message below: Bug in Mailman version 2.1.9 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. I've looked in the logs and they are empty. Do I have to turn logging on or is the a way to allow the printing of the traceback so I can get more info on the error? Thanks in advance for any help/suggestions. Regards, Steve Mueller From b19141 at britaine.ctd.anl.gov Mon Jan 15 18:27:20 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Mon, 15 Jan 2007 11:27:20 -0600 (CST) Subject: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED) Message-ID: <200701151727.l0FHRKev027086@britaine.ctd.anl.gov> On Jan 10, 2007, at 2:26 PM, Barry Finkel wrote: >> I read the entire bug page trail, and I am trying to understand it. >> I looked at my 2.1.9 source test installation (on Solaris 10, where I >> installed into /opt/mailman), and I see things in the >> >> /opt/mailman/pythonlib >> >> directory. What is the purpose of the files found therein? If these >> are needed by Mailman, how can Ubuntu/Debian not supply them? I am >> trying to understand what is happening (so that I can convince >> others here that I need to install from the source and not from the >> Ubuntu package). and Barry Warsaw replied: >The only reason I can think for U/D to not include that directory is >that they are sure that the Python they depend Mailman on already has >the email package and codecs that live in pythonlib. The purpose of >pythonlib is to provide compatibility between Python versions which >might have older versions of the email lib or might be missing the >codecs. > >It's not strictly required to have pythonlib, and should be possible >to run without it, but I'm not sure why you would, unless you feel >that you're tracking patches in the dependent packages better than >the Mailman project is. I don't see how it can hurt to have the >pythonlib that Mailman normally installs. > >- -Barry The original Debian bug report had The short summary for the bug is "bad installation when /var/lib/mailman/pythonlib is a symlink." so, it appears to me that the U/D fix should have been to check for a symlink and not remove pythonlib entirely. I have to assume that the person who originated this thread, Kyle Sexton, installed Mailman via an Ubuntu package install Kyle Sexton wrote: > >Thanks for your reply. I realized after I sent the message that >I left of the version numbers: > >mailman 2.1.8-2ubuntu2 So, there is a packaging problem with Ubuntu and Mailman. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel at anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994 From dan at thecsl.org Mon Jan 15 18:57:45 2007 From: dan at thecsl.org (Dan MacNeil) Date: Mon, 15 Jan 2007 12:57:45 -0500 Subject: [Mailman-Users] Compulsory username when subscribing In-Reply-To: References: Message-ID: <45ABC099.1050500@thecsl.org> not top posting see below. > emmexx wrote: >> Is it possible to make the username field compulsory when subscribing by >> web page? >> p.s. I can't access the server files Mark Sapiro wrote: > Then the answer is No. You would have to modify the script that > processes the form. > > You can edit the template for the list's listinfo page via the admin > web interface. You could do things like remove the "(optional)" > notation from the "Your name" entry, but given the way the form is > created from the template, I don't think you could actually require an > entry in that field. > From a quick look at the template in 2.1.9, it looks like you can stick some javascript in to require that Names be submitted. Obviously, this won't work if the user doesn't have javascript enabled, but javascript beats a stick in the eye. From msapiro at value.net Mon Jan 15 19:11:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 15 Jan 2007 10:11:35 -0800 Subject: [Mailman-Users] us-ascii problem with new install inUbuntu(SOLVED) In-Reply-To: <200701151727.l0FHRKev027086@britaine.ctd.anl.gov> Message-ID: Barry Finkel wrote: > >The original Debian bug report had > > The short summary for the bug is "bad installation when > /var/lib/mailman/pythonlib is a symlink." > >so, it appears to me that the U/D fix should have been to check for a >symlink and not remove pythonlib entirely. Actually, that summary is misleading. The problem was not just that /var/lib/mailman/pythonlib was a symlink, but that it was a symlink to the library of an old (out dated) Python installation. The U/D response to this (completely removing pythonlib from the Mailman installation) was a total overreaction and is wrong and leads to the more recent issue that Kyle and others experienced. Namely, in mailman 2.1.8-2ubuntu2 there is no pythonlib so the email package used is the one from the underlying Python library, and now because of either the Python version or Ubuntu (or Debian) mods, this email package is incompatible with Mailman 2.1.8. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 15 19:32:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 15 Jan 2007 10:32:42 -0800 Subject: [Mailman-Users] Compulsory username when subscribing In-Reply-To: <45ABC099.1050500@thecsl.org> Message-ID: Dan MacNeil wrote: > > From a quick look at the template in 2.1.9, it looks like you can stick >some javascript in to require that Names be submitted. Obviously, this >won't work if the user doesn't have javascript enabled, but javascript >beats a stick in the eye. There are a few issues in trying to do this. In the template, the 'subscribe' button and it's actions are generated from a pseudo tag, so without access to the underlying code, you would have to rewrite the template replacing various pseudo tags with the desired HTML. Then again, without access to the underlying installation, you have to use the admin interface to edit the listinfo template, and we try not to allow javascript in HTML entered via the web interface in order to avoid XSS attacks. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 15 20:07:46 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 15 Jan 2007 11:07:46 -0800 Subject: [Mailman-Users] error when going to list admin url In-Reply-To: <200701151650.l0FGoTK4015678@mailsvr01.frontieradjusters.com> Message-ID: Steve Mueller wrote: > >Here's my story - I've installed Mailman with, at least seemingly, no >issues. I've run check_perms and all checked out ok. I was able to create >a list from the command line and I received the email indicating that the >list had been created which also included the url's to the admin and user >frontend for the list. However, when I click on the admin URL I get the >message below: > > > > >Bug in Mailman version 2.1.9 > > >We're sorry, we hit a bug! > > >Please inform the webmaster for this site of this problem. Printing of >traceback and other system information has been explicitly inhibited, but >the webmaster can find this information in the Mailman error logs. > >I've looked in the logs and they are empty. Do I have to turn logging on or >is the a way to allow the printing of the traceback so I can get more info >on the error? Two things: 1) check for the setting of LOG_DIR in Defaults.py and mm_cfg.py (mm_cfg.py overrides Defaults.py) and make sure you are looking in the correct place for the error log. Also make sure the log's group is the mailman group and it is group writable and Mailman/cgi-bin/admin is group mailman and SETGID. 2) in scripts/driver change the line STEALTH_MODE = 1 just after the comments at the beginning to STEALTH_MODE = 0 This will enable printing the traceback to the web browser. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Terry.Poperszky at SOSStaffing.Com Mon Jan 15 20:01:34 2007 From: Terry.Poperszky at SOSStaffing.Com (Terry Poperszky) Date: Mon, 15 Jan 2007 12:01:34 -0700 Subject: [Mailman-Users] List freezing? Message-ID: <4E1C1AF79DDF3E4EBE8D7F1736228FB624C889@eta.hcwan.net> I have a mailman server (4.12) with a couple of hundred lists on it and it has been working fine, now my largest list (826) has frozen, I can list it, but it I can't add/subtract from it on the command line or the GUI. Can someone point me in the correct direction to troubleshoot this thing? Terry Poperszky Network Manager SOS Staffing Services, Inc. 801-257-5709 From pdbogen at gmail.com Mon Jan 15 20:36:55 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Mon, 15 Jan 2007 13:36:55 -0600 Subject: [Mailman-Users] List freezing? In-Reply-To: <4E1C1AF79DDF3E4EBE8D7F1736228FB624C889@eta.hcwan.net> References: <4E1C1AF79DDF3E4EBE8D7F1736228FB624C889@eta.hcwan.net> Message-ID: <6fbe3da00701151136r1df9392fmc4c6bbdda693dd07@mail.gmail.com> On 1/15/07, Terry Poperszky wrote: > I have a mailman server (4.12) with a couple of hundred lists on it and > it has been working fine, now my largest list (826) has frozen, I can > list it, but it I can't add/subtract from it on the command line or the > GUI. Can someone point me in the correct direction to troubleshoot this > thing? I assume by 'add/subtract' you mean adding and removing list members. What happens when you try to do this? Is there anything interesting in mailman's 'error' log? Also, it's probably not related, if you can't add members, but double-check to make sure that all of mailman's qrunners are running. -- - Patrick Bogen From Terry.Poperszky at SOSStaffing.Com Mon Jan 15 20:40:15 2007 From: Terry.Poperszky at SOSStaffing.Com (Terry Poperszky) Date: Mon, 15 Jan 2007 12:40:15 -0700 Subject: [Mailman-Users] List freezing? References: <4E1C1AF79DDF3E4EBE8D7F1736228FB624C889@eta.hcwan.net> <6fbe3da00701151136r1df9392fmc4c6bbdda693dd07@mail.gmail.com> Message-ID: <4E1C1AF79DDF3E4EBE8D7F1736228FB624C88B@eta.hcwan.net> Thanks, there were stale locks keeping me from accessing the administrative interface (gui/cl). I shut mailman down and deleted the locks and everything is happy now. Sorry for the vague post to start this discussion. Terry -----Original Message----- From: Patrick Bogen [mailto:pdbogen at gmail.com] Sent: Monday, January 15, 2007 12:37 PM To: Terry Poperszky Cc: mailman-users at python.org Subject: Re: [Mailman-Users] List freezing? On 1/15/07, Terry Poperszky wrote: > I have a mailman server (4.12) with a couple of hundred lists on it and > it has been working fine, now my largest list (826) has frozen, I can > list it, but it I can't add/subtract from it on the command line or the > GUI. Can someone point me in the correct direction to troubleshoot this > thing? I assume by 'add/subtract' you mean adding and removing list members. What happens when you try to do this? Is there anything interesting in mailman's 'error' log? Also, it's probably not related, if you can't add members, but double-check to make sure that all of mailman's qrunners are running. -- - Patrick Bogen From md6969 at gmail.com Mon Jan 15 22:00:50 2007 From: md6969 at gmail.com (Martin Dennett) Date: Mon, 15 Jan 2007 21:00:50 +0000 Subject: [Mailman-Users] Filter based on message text Message-ID: <45ABEB82.1070104@gmail.com> Hi Just wondering if it's possible (via spam filters?) to take action on a mail depending on text found in the body of an email? Had a quick check of the FAQ's and didn't see anything that looked applicable. I don't have command line access.... Rgds MD From msapiro at value.net Mon Jan 15 23:53:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 15 Jan 2007 14:53:49 -0800 Subject: [Mailman-Users] Filter based on message text In-Reply-To: <45ABEB82.1070104@gmail.com> Message-ID: Martin Dennett wrote: > >Just wondering if it's possible (via spam filters?) to take action on a >mail depending on text found in the body of an email? Had a quick check >of the FAQ's and didn't see anything that looked applicable. I don't >have command line access.... Mailman doesn't provide the ability to filter based on the actual text in the message body. The way to do this is via a custom handler . Doing this directly requires access beyond what you have, but since installing such a handler for a single list is relatively benign, if you have the ability to code such a handler in Python, you might be able to convince your Mailman host to install it for your list(s). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From khj at be.cs.appstate.edu Mon Jan 15 23:58:00 2007 From: khj at be.cs.appstate.edu (Kenneth Jacker) Date: Mon, 15 Jan 2007 17:58:00 -0500 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages Message-ID: <87fyablwxz.fsf@be.cs.appstate.edu> I'm using firefox-1.5.0.9 on an up-to-date Kubuntu system with mailman-2.1.5-9. Suddenly (maybe a week or so ago), 'firefox' began and continues *crashing* immediately after I enter the "admin page" URL for all of my lists ... I've searched around and found some alleged "work arounds" (removing certain files, not using retained passwords, etc.), but it still won't work. Anyone else seeing this? Is there a *real* "fix"? Thanks for any help, -Kenneth -- Prof Kenneth H Jacker khj at cs.appstate.edu Computer Science Dept www.cs.appstate.edu/~khj Appalachian State Univ Boone, NC 28608 USA From msapiro at value.net Tue Jan 16 01:22:06 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 15 Jan 2007 16:22:06 -0800 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages In-Reply-To: <87fyablwxz.fsf@be.cs.appstate.edu> Message-ID: Kenneth Jacker wrote: >I'm using firefox-1.5.0.9 on an up-to-date Kubuntu system with >mailman-2.1.5-9. > >Suddenly (maybe a week or so ago), 'firefox' began and continues >*crashing* immediately after I enter the "admin page" URL for all of >my lists ... I have no problem with a Mailman 2.1.5 installation in RedHat FC2 with either firefox 1.5.0.8 or 1.5.0.9. Presumably in your case, it crashes on retrieval of the "Administrator Authentication" page or perhaps in trying to fill in the password, but you seem to say below that you have tried turning off password fill in. >I've searched around and found some alleged "work arounds" (removing >certain files, not using retained passwords, etc.), but it still won't >work. > >Anyone else seeing this? Is there a *real* "fix"? I am able to visit with firefox 1.5.0.9 and I get an "unable to verify certificate for unknown reasons", but when I accept the certificate I see the "Administrator Authentication" page and no crash, but this identifies itself as a Mailman 2.1.9 installation, so maybe it isn't the one you're talking about. Can you successfully visit that page? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at python.org Tue Jan 16 04:51:01 2007 From: barry at python.org (Barry Warsaw) Date: Mon, 15 Jan 2007 22:51:01 -0500 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages In-Reply-To: References: Message-ID: <2CFC8488-8AD2-4BDB-9FE2-28321DC501AC@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 15, 2007, at 7:22 PM, Mark Sapiro wrote: > Kenneth Jacker wrote: > >> I'm using firefox-1.5.0.9 on an up-to-date Kubuntu system with >> mailman-2.1.5-9. >> >> Suddenly (maybe a week or so ago), 'firefox' began and continues >> *crashing* immediately after I enter the "admin page" URL for all of >> my lists ... > > > I have no problem with a Mailman 2.1.5 installation in RedHat FC2 with > either firefox 1.5.0.8 or 1.5.0.9. I use FF 1.5.0.9 on OS X (and occasionally Linux) against various and sundry Mailman versions and have never seen a crash. I can't image what would be crashing FF -- our web u/i is pretty darn pedestrian. No Java or Javascript. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRaxLpXEjvBPtnXfVAQIwMAQAtfaFtR0AypkTxr6PskHipDAG8fJkthV4 ZdK7BQoRdKbDy9TOKwbu540IGFuKGJiP543FBsCh2qHGPR9YErVv2To6X5Vgtf9p R3bjzI4GjHykeg13EmEncKbjUn2bkzIcF45LZ9aaY8o/oKlqKy4h6yj7SOOgbVs/ uFBEg8zJylc= =JNvK -----END PGP SIGNATURE----- From pmatulis at sympatico.ca Tue Jan 16 06:41:24 2007 From: pmatulis at sympatico.ca (Peter Matulis) Date: Tue, 16 Jan 2007 00:41:24 -0500 Subject: [Mailman-Users] migrating mailman config Message-ID: <200701160041.24614.pmatulis@sympatico.ca> I am looking for guidance on migrating a mailman setup to a separate server. Is it better to start fresh? Peter From cpz at tuunq.com Tue Jan 16 06:53:20 2007 From: cpz at tuunq.com (Carl Zwanzig) Date: Mon, 15 Jan 2007 21:53:20 -0800 (PST) Subject: [Mailman-Users] migrating mailman config In-Reply-To: <200701160041.24614.pmatulis@sympatico.ca> from Peter Matulis at "Jan 16, 2007 00:41:24 am" Message-ID: <20070116055321.3CE607AE@mail.tuunq.com> In a flurry of recycled electrons, Peter Matulis wrote: > I am looking for guidance on migrating a mailman setup to a separate > server. Is it better to start fresh? Install 2.1.9 on the new server. Read FAQ 3.4 and check this list's archive, it was discussed in the last couple of months. z! From kullmann at elementec.de Tue Jan 16 09:42:25 2007 From: kullmann at elementec.de (Peter Kullmann) Date: Tue, 16 Jan 2007 09:42:25 +0100 Subject: [Mailman-Users] Mailman listed on Update-Scout.com Message-ID: <45AC8FF1.2090000@elementec.de> Hi, Mailman has just been added to Update-Scout.com, an interactive web service, that informs its users about software updates and releases. Users can set up personal update news feeds from the Update-Scout software catalog and even add new entries to the catalog. The address is http://www.update-scout.com . Peter Kullmann ========================================== elementec Software & Consulting Dr. Peter Kullmann Wollgrasweg 49, 70599 Stuttgart, Germany ========================================== Tel +49 - 711 - 4510 17 350 Fax +49 - 711 - 4510 17 222 info at update-scout.com www.update-scout.com ========================================== From her at adm.ku.dk Tue Jan 16 12:04:51 2007 From: her at adm.ku.dk (Henrik Rasmussen) Date: Tue, 16 Jan 2007 12:04:51 +0100 Subject: [Mailman-Users] Mailman's root path or where to place images Message-ID: <78E3AAA50C11F0419C4C3F41707B653009355D5B@taipan.ad.adm.ku.dk> I currently have my mailman icons in an /icons directory relative to Apache's root directory. Example: Icons is in /var/www/icons/ and the source http path to the icons is http://server.xxx.yyy.zz/icons/ In order to put the server behind a proxy server, I need to change the directory to http://server.xxx.yyy.zz/mailman/icons/ By changing the variable IMAGE_LOGOS = '/icons/' to IMAGE_LOGOS = 'icons/' in the file /usr/lib/mailman/Mailman/mm_cfg.py the http path is seemly relative to Mailman's root http://server.xxx.yyy.zz/mailman/icons/ which I suppose should be /usr/lib/mailman/icons/ ,but moving the image file /usr/lib/mailman/icons/ still results in a missing image. My question is, where Mailman's root directory is suppose to be, or rather which directory on the server correspond to http://server.xxx.yyy.zz/mailman/icons/? Henrik From khj at be.cs.appstate.edu Tue Jan 16 15:57:23 2007 From: khj at be.cs.appstate.edu (Kenneth Jacker) Date: Tue, 16 Jan 2007 09:57:23 -0500 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages In-Reply-To: <2CFC8488-8AD2-4BDB-9FE2-28321DC501AC@python.org> (Barry Warsaw's message of "Mon, 15 Jan 2007 22:51:01 -0500") References: <2CFC8488-8AD2-4BDB-9FE2-28321DC501AC@python.org> Message-ID: <87bqkz2f58.fsf@be.cs.appstate.edu> I appreciate both Mark and Barry's informative and prompt replies. Let me do a little more investigating ... maybe there's some conflict with one of my FF plugins ... Thanks for the help, -Kenneth From patrick at malkin.de Tue Jan 16 17:48:05 2007 From: patrick at malkin.de (Patrick Franz) Date: Tue, 16 Jan 2007 17:48:05 +0100 Subject: [Mailman-Users] Low level smtp error Message-ID: <200701161748.05321.patrick@malkin.de> Hi, I'm running a Debian Sarge machine with Exim 4.50 and I recently installed Mailman 2.1.5. The installation itself went without any bigger problems. I can create lists now, I can manage them and I can send mails to those lists. Those mails land in the archive as they should, but they don't get delivered to the subscribers. A look at /var/log/mailman/smtp-failure gives the following: Jan 16 17:12:32 2007 (9353) Low level smtp error: (111, 'Connection refused'), msgid: Jan 16 17:12:32 2007 (9353) Low level smtp error: please run connect() first, msgid: Jan 16 17:12:32 2007 (9353) delivery to footest at myotherdomain.de failed with code -1: please run connect() first Jan 16 17:12:32 2007 (9353) delivery to p200 at mydomain2.de failed with code -1: (111, 'Connection refused') Both p200 at mydomain2.de and footest at myotherdomain.de are subscribed to that list. Any suggestions ? Thx. === = ==== /#/\#\ /#/\#\ /#/ \#\ /#/ \#\ /#/ patrick \#\ /#/ @ \#\ /#/ malkin.de \#\ From msapiro at value.net Tue Jan 16 18:29:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 09:29:02 -0800 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <200701161748.05321.patrick@malkin.de> Message-ID: Patrick Franz wrote: >I can create lists now, I can manage them and I can send mails to those >lists. Those mails land in the archive as they should, but they don't >get delivered to the subscribers. A look at >/var/log/mailman/smtp-failure gives the following: > > >Jan 16 17:12:32 2007 (9353) Low level smtp error: (111, 'Connection >refused'), msgid: >Jan 16 17:12:32 2007 (9353) Low level smtp error: please run connect() >first, msgid: >Jan 16 17:12:32 2007 (9353) delivery to footest at myotherdomain.de failed >with code -1: please run connect() first >Jan 16 17:12:32 2007 (9353) delivery to p200 at mydomain2.de failed with >code -1: (111, 'Connection refused') Your Mailman is unable to connect to your outgoing MTA (Exim). Exim is refusing connection or is not listening on 'localhost' port 25. Can you telnet localhost 25 on the Mailman/Exim box? Presumably Exim is running if you can send mail to Mailman, but there is probably some Exim configuration issue causing it to not accept connects from localhost. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From patrick at malkin.de Tue Jan 16 18:35:12 2007 From: patrick at malkin.de (Patrick Franz) Date: Tue, 16 Jan 2007 18:35:12 +0100 Subject: [Mailman-Users] Low level smtp error In-Reply-To: References: Message-ID: <200701161835.12971.patrick@malkin.de> Hi, Am Dienstag, 16. Januar 2007 18:29 schrieb Mark Sapiro: > Your Mailman is unable to connect to your outgoing MTA (Exim). Exim > is refusing connection or is not listening on 'localhost' port 25. > > Can you > > telnet localhost 25 > > on the Mailman/Exim box? Presumably Exim is running if you can send > mail to Mailman, but there is probably some Exim configuration issue > causing it to not accept connects from localhost. Yes, Exim is running for a year or so and it is working so far. fb04184:~# telnet localhost 25 Trying 127.0.0.1... telnet: Unable to connect to remote host: Connection refused === = ==== /#/\#\ /#/\#\ /#/ \#\ /#/ \#\ /#/ patrick \#\ /#/ @ \#\ /#/ malkin.de \#\ From msapiro at value.net Tue Jan 16 18:37:08 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 09:37:08 -0800 Subject: [Mailman-Users] Mailman listed on Update-Scout.com In-Reply-To: <45AC8FF1.2090000@elementec.de> Message-ID: Peter Kullmann wrote: > >Mailman has just been added to Update-Scout.com, an interactive web >service, that informs its users about software updates and releases. >Users can set up personal update news feeds from the Update-Scout >software catalog and even add new entries to the catalog. >The address is http://www.update-scout.com . I note Mailman's platform is listed as Linux. This is not correct. Mailman can be installed and run on any *nix platform. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Tue Jan 16 18:38:48 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 16 Jan 2007 12:38:48 -0500 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <200701161835.12971.patrick@malkin.de> References: <200701161835.12971.patrick@malkin.de> Message-ID: <20070116173848.GC19047@allhats.xcski.com> Quoting Patrick Franz (patrick at malkin.de): > Hi, > > Am Dienstag, 16. Januar 2007 18:29 schrieb Mark Sapiro: > > Your Mailman is unable to connect to your outgoing MTA (Exim). Exim > > is refusing connection or is not listening on 'localhost' port 25. > > > > Can you > > > > telnet localhost 25 > > > > on the Mailman/Exim box? Presumably Exim is running if you can send > > mail to Mailman, but there is probably some Exim configuration issue > > causing it to not accept connects from localhost. > > Yes, Exim is running for a year or so and it is working so far. > > fb04184:~# telnet localhost 25 > Trying 127.0.0.1... > telnet: Unable to connect to remote host: Connection refused > If it's not listening on port 25 on localhost, then it's not "working so far". You need to figure out where it is listening. -- Paul Tomblin http://blog.xcski.com/ "While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named `Manual'" - Dilbert From al-black at telus.net Tue Jan 16 18:43:03 2007 From: al-black at telus.net (Al Black) Date: Tue, 16 Jan 2007 10:43:03 -0700 Subject: [Mailman-Users] held messages via command line In-Reply-To: <200701161748.05321.patrick@malkin.de> References: <200701161748.05321.patrick@malkin.de> Message-ID: <1168969382.7778.852.camel@localhost.localdomain> Hi gang, Question about removing held messages via command line. I'm using version 2.1.4 on BSD. I've been doing some re-administration, or post administration for lack of a better term, on the machine after being away for a year and a bit. I've cleaned away most of the held messages by command line for the lists using the methods in FAQ 4.74. However, we've got a whack (i.e., several 1000) held messages for the list "Mailman". Both "bin/discard data/heldmsg--*" and "find data -name heldmsg--\* -print | xargs bin/discard" stall when I use them. Even when I use bin/discard for a single held message, it stalls. Any ideas on how to proceed? I could rm the bunch, but I don't have a copy of the empty admin.db copy in (as per the old faq entry). I suppose I could hold my nose, but my gut feeling is that this huge number of held messages is not a good thing... al From patrick at malkin.de Tue Jan 16 18:50:41 2007 From: patrick at malkin.de (Patrick Franz) Date: Tue, 16 Jan 2007 18:50:41 +0100 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <20070116173848.GC19047@allhats.xcski.com> References: <200701161835.12971.patrick@malkin.de> <20070116173848.GC19047@allhats.xcski.com> Message-ID: <200701161850.41393.patrick@malkin.de> Hi, Am Dienstag, 16. Januar 2007 18:38 schrieb Paul Tomblin: > > > Yes, Exim is running for a year or so and it is working so far. > > > > fb04184:~# telnet localhost 25 > > Trying 127.0.0.1... > > telnet: Unable to connect to remote host: Connection refused > > If it's not listening on port 25 on localhost, then it's not "working > so far". You need to figure out where it is listening. The server is used to just forward/redirect mails as those addresses are defined in /etc/aliases. A netstat -lnp gives: tcp 0 0 130.83.2.184:25 0.0.0.0:* LISTEN 21340/exim4 with 130.83.2.184 being the server's IP. === = ==== /#/\#\ /#/\#\ /#/ \#\ /#/ \#\ /#/ patrick \#\ /#/ @ \#\ /#/ malkin.de \#\ From ptomblin at xcski.com Tue Jan 16 19:17:22 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 16 Jan 2007 13:17:22 -0500 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <200701161850.41393.patrick@malkin.de> References: <200701161835.12971.patrick@malkin.de> <20070116173848.GC19047@allhats.xcski.com> <200701161850.41393.patrick@malkin.de> Message-ID: <20070116181722.GA27237@allhats.xcski.com> Quoting Patrick Franz (patrick at malkin.de): > Hi, > > Am Dienstag, 16. Januar 2007 18:38 schrieb Paul Tomblin: > > > > > Yes, Exim is running for a year or so and it is working so far. > > > > > > fb04184:~# telnet localhost 25 > > > Trying 127.0.0.1... > > > telnet: Unable to connect to remote host: Connection refused > > > > If it's not listening on port 25 on localhost, then it's not "working > > so far". You need to figure out where it is listening. > > The server is used to just forward/redirect mails as those addresses are > defined in /etc/aliases. > > > > A netstat -lnp gives: > > tcp 0 0 130.83.2.184:25 0.0.0.0:* > LISTEN 21340/exim4 > > with 130.83.2.184 being the server's IP. Then you need to set SMTPHOST to '130.83.2.184' instead of 'localhost', so that you're not connecting as localhost. -- Paul Tomblin http://blog.xcski.com/ Reliability went through the floor, tunnelled its way to the centre of the Earth, and perished in the magma. -- Saundo From lstone19 at stonejongleux.com Tue Jan 16 19:03:06 2007 From: lstone19 at stonejongleux.com (Larry Stone) Date: Tue, 16 Jan 2007 12:03:06 -0600 (CST) Subject: [Mailman-Users] Low level smtp error In-Reply-To: <200701161850.41393.patrick@malkin.de> References: <200701161835.12971.patrick@malkin.de> <20070116173848.GC19047@allhats.xcski.com> <200701161850.41393.patrick@malkin.de> Message-ID: On Tue, 16 Jan 2007, Patrick Franz wrote: > Hi, > > Am Dienstag, 16. Januar 2007 18:38 schrieb Paul Tomblin: > > > > > Yes, Exim is running for a year or so and it is working so far. > > > > > > fb04184:~# telnet localhost 25 > > > Trying 127.0.0.1... > > > telnet: Unable to connect to remote host: Connection refused > > > > If it's not listening on port 25 on localhost, then it's not "working > > so far". You need to figure out where it is listening. > > The server is used to just forward/redirect mails as those addresses are > defined in /etc/aliases. But it's not. I think you missed in your output from "telnet localhost 25" that it responded "connection refused". > A netstat -lnp gives: > > tcp 0 0 130.83.2.184:25 0.0.0.0:* > LISTEN 21340/exim4 > > with 130.83.2.184 being the server's IP. I'm no expert but I think just because it's listening to 130.83.2.184 on port 25 does not mean it's listening to localhost (127.0.0.1) on port 25. -- Larry Stone lstone19 at stonejongleux.com From ptomblin at xcski.com Tue Jan 16 19:32:32 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 16 Jan 2007 13:32:32 -0500 Subject: [Mailman-Users] Low level smtp error In-Reply-To: References: <200701161835.12971.patrick@malkin.de> <20070116173848.GC19047@allhats.xcski.com> <200701161850.41393.patrick@malkin.de> Message-ID: <20070116183232.GA30196@allhats.xcski.com> Quoting Larry Stone (lstone19 at stonejongleux.com): > On Tue, 16 Jan 2007, Patrick Franz wrote: > > A netstat -lnp gives: > > > > tcp 0 0 130.83.2.184:25 0.0.0.0:* > > LISTEN 21340/exim4 > > > > with 130.83.2.184 being the server's IP. > > I'm no expert but I think just because it's listening to 130.83.2.184 on > port 25 does not mean it's listening to localhost (127.0.0.1) on port 25. Yes, that's exactly what it means. On a mail server configured to accept mail from local senders, that would be 0.0.0.0:25. That's why I suggested he connnect on the 130.83.2.184:25 port instead. -- Paul Tomblin http://blog.xcski.com/ "Think?" I asked. "I don't think. I'm a witness. Someone asks me a question, and I answer it as honestly as I can. How could I be on anyone's *side*?" -- David P. Murphy, on his participation in a lawsuit From msapiro at value.net Tue Jan 16 19:35:08 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 10:35:08 -0800 Subject: [Mailman-Users] Mailman's root path or where to place images In-Reply-To: <78E3AAA50C11F0419C4C3F41707B653009355D5B@taipan.ad.adm.ku.dk> Message-ID: Henrik Rasmussen wrote: > >I currently have my mailman icons in an /icons directory relative to >Apache's root directory. > >Example: > >Icons is in /var/www/icons/ and the source http path to the icons is >http://server.xxx.yyy.zz/icons/ > >In order to put the server behind a proxy server, I need to change the >directory to http://server.xxx.yyy.zz/mailman/icons/ If it really has to be http://server.xxx.yyy.zz/mailman/icons/ and http://server.xxx.yyy.zz/something_else/ won't do, I think you have only one choice. See below. >By changing the variable IMAGE_LOGOS = '/icons/' to IMAGE_LOGOS = >'icons/' in the file /usr/lib/mailman/Mailman/mm_cfg.py the http path is >seemly relative to Mailman's root >http://server.xxx.yyy.zz/mailman/icons/ Actually, it is just a relative path in the HTML to which your browser prepends the current location. >which I suppose should be >/usr/lib/mailman/icons/ ,but moving the image file >/usr/lib/mailman/icons/ still results in a missing image. > >My question is, where Mailman's root directory is suppose to be, or >rather which directory on the server correspond to >http://server.xxx.yyy.zz/mailman/icons/? You have something like ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ in your httpd.conf, so http://server.xxx.yyy.zz/mailman/icons/ corresponds to the CGI named icons in the directory /usr/lib/mailman/cgi-bin/. Ideally, you could alias it in your Apache httpd.conf with something like Alias /mailman/ /usr/lib/mailman/ except this won't work because of the conflict with the ScriptAlias. If you really need the URL for the icons to be http://example.com/mailman/icons/, I think you need to create an 'icons' CGI and put it in /usr/lib/mailman/cgi-bin/. This would be a simple CGI that would just parse the name following http://example.com/mailman/icons/ in the URL and locate and serve that file. There may be some other way to address this in the Apache configuration, but that's an Apache question that I don't know the answer to. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From djk at tobit.co.uk Tue Jan 16 19:25:09 2007 From: djk at tobit.co.uk (Dirk Koopman) Date: Tue, 16 Jan 2007 18:25:09 +0000 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <20070116181722.GA27237@allhats.xcski.com> References: <200701161835.12971.patrick@malkin.de> <20070116173848.GC19047@allhats.xcski.com> <200701161850.41393.patrick@malkin.de> <20070116181722.GA27237@allhats.xcski.com> Message-ID: <45AD1885.9000805@tobit.co.uk> Paul Tomblin wrote: > Quoting Patrick Franz (patrick at malkin.de): >> Hi, >> >> Am Dienstag, 16. Januar 2007 18:38 schrieb Paul Tomblin: >>>> Yes, Exim is running for a year or so and it is working so far. >>>> >>>> fb04184:~# telnet localhost 25 >>>> Trying 127.0.0.1... >>>> telnet: Unable to connect to remote host: Connection refused >>> If it's not listening on port 25 on localhost, then it's not "working >>> so far". You need to figure out where it is listening. >> The server is used to just forward/redirect mails as those addresses are >> defined in /etc/aliases. >> >> >> >> A netstat -lnp gives: >> >> tcp 0 0 130.83.2.184:25 0.0.0.0:* >> LISTEN 21340/exim4 >> >> with 130.83.2.184 being the server's IP. > > Then you need to set SMTPHOST to '130.83.2.184' instead of 'localhost', so > that you're not connecting as localhost. > or comment out the 'local_interfaces = 130.83.2.184' line in exim.conf and restart exim. From patrick at malkin.de Tue Jan 16 19:57:37 2007 From: patrick at malkin.de (Patrick Franz) Date: Tue, 16 Jan 2007 19:57:37 +0100 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <45AD1885.9000805@tobit.co.uk> References: <20070116181722.GA27237@allhats.xcski.com> <45AD1885.9000805@tobit.co.uk> Message-ID: <200701161957.37283.patrick@malkin.de> Hi all, thank you for your help, it's finally working. I changed the local_interfaces to "local_interfaces = 0.0.0.0" and changed the SMTPHOST to 130.83.2.184. === = ==== /#/\#\ /#/\#\ /#/ \#\ /#/ \#\ /#/ patrick \#\ /#/ @ \#\ /#/ malkin.de \#\ From msapiro at value.net Tue Jan 16 20:07:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 11:07:49 -0800 Subject: [Mailman-Users] held messages via command line In-Reply-To: <1168969382.7778.852.camel@localhost.localdomain> Message-ID: Al Black wrote: > >However, we've got a whack (i.e., several 1000) held messages for the >list "Mailman". Both "bin/discard data/heldmsg--*" >and "find data -name heldmsg--\* -print | xargs bin/discard" >stall when I use them. Even when I use bin/discard for a single held >message, it stalls. There is probably a stale lock for the list. Look in Mailman's locks/ directory for stale locks. A lock is two files, one named .lock and one named .lock.... If you find old locks for the mailman list, especially with a non-existant pid, just delete them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From md6969 at gmail.com Tue Jan 16 20:42:14 2007 From: md6969 at gmail.com (Martin Dennett) Date: Tue, 16 Jan 2007 19:42:14 +0000 Subject: [Mailman-Users] Mailman-Users Digest, Vol 35, Issue 26 In-Reply-To: References: Message-ID: <45AD2A96.5050309@gmail.com> mailman-users-request at python.org wrote: > > Subject: > Re: [Mailman-Users] Filter based on message text > From: > Mark Sapiro > Date: > Mon, 15 Jan 2007 14:53:49 -0800 > To: > Martin Dennett , Mailman Users > > > To: > Martin Dennett , Mailman Users > > > > Martin Dennett wrote: > >> Just wondering if it's possible (via spam filters?) to take action on a >> mail depending on text found in the body of an email? Had a quick check >> of the FAQ's and didn't see anything that looked applicable. I don't >> have command line access.... >> > > Mailman doesn't provide the ability to filter based on the actual text > in the message body. > > The way to do this is via a custom handler > . > Doing this directly requires access beyond what you have, but since > installing such a handler for a single list is relatively benign, if > you have the ability to code such a handler in Python, you might be > able to convince your Mailman host to install it for your list(s). Hi Mark I did actually see that in the FAQ's and thought it may have been what I was looking for. I'll have a word with the host and see what they can do. Rgds MD From md6969 at gmail.com Tue Jan 16 20:42:29 2007 From: md6969 at gmail.com (Martin Dennett) Date: Tue, 16 Jan 2007 19:42:29 +0000 Subject: [Mailman-Users] Filter based on message text In-Reply-To: References: Message-ID: <45AD2AA5.5010604@gmail.com> mailman-users-request at python.org wrote: > > Subject: > Re: [Mailman-Users] Filter based on message text > From: > Mark Sapiro > Date: > Mon, 15 Jan 2007 14:53:49 -0800 > To: > Martin Dennett , Mailman Users > > > To: > Martin Dennett , Mailman Users > > > > Martin Dennett wrote: > >> Just wondering if it's possible (via spam filters?) to take action on a >> mail depending on text found in the body of an email? Had a quick check >> of the FAQ's and didn't see anything that looked applicable. I don't >> have command line access.... >> > > Mailman doesn't provide the ability to filter based on the actual text > in the message body. > > The way to do this is via a custom handler > . > Doing this directly requires access beyond what you have, but since > installing such a handler for a single list is relatively benign, if > you have the ability to code such a handler in Python, you might be > able to convince your Mailman host to install it for your list(s). Hi Mark I did actually see that in the FAQ's and thought it may have been what I was looking for. I'll have a word with the host and see what they can do. Rgds MD From julia_frizzell at brown.edu Tue Jan 16 20:36:24 2007 From: julia_frizzell at brown.edu (Julia Frizzell) Date: Tue, 16 Jan 2007 14:36:24 -0500 Subject: [Mailman-Users] Spam Filter disappearing Message-ID: <46FB0370-5A48-49B9-B693-B95B1984CD74@brown.edu> Hello everyone! I did do a search on my question, and I found a solution, but I'm not sure how to work it. I'm running Mailman 2.1.5 under Mac OS X Server 10.4.3. We've just made the full move to Mailman (from an OS 9 product), and of course are being inundated with spam and are working on creating filters. Some of our spam filter sets for lists have been vanishing, and a post in the archives indicated that this was fixed in 2.1.6. Since I'm running under OS X, I haven't done any upgrades to Mailman for fear of things being broken when the next Apple OS update comes out. Is there any way I can just apply a fix for this issue? The Sourceforge site seemed to have an updated Privacy.py file, but it also indicated in the comments that the way it was fixed required an awful hack, so I'm not extremely keen on just popping it there. Is there any way short of trying to upgrade to the latest (which I believe is 2.1.9) that I can remedy the filters vanishing? Thanks in advance. --- Julia Frizzell Systems Administrator/Help Desk Manager The Education Alliance 222 Richmond Street, Suite 300 Providence, Rhode Island 02903-4226 julia_frizzell at brown.edu 401.274.9548 x311 or 800.521.9550 x311 401.421.7650 (fax) http://www.alliance.brown.edu From msapiro at value.net Tue Jan 16 21:47:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 12:47:12 -0800 Subject: [Mailman-Users] Spam Filter disappearing In-Reply-To: <46FB0370-5A48-49B9-B693-B95B1984CD74@brown.edu> Message-ID: Julia Frizzell wrote: > >Is there any way I can just apply a fix for this issue? The >Sourceforge site seemed to have an updated Privacy.py file, but it >also indicated in the comments that the way it was fixed required an >awful hack, so I'm not extremely keen on just popping it there. I'm not sure what comment you are looking at, but if you go to and download the rev 7694 Privacy.py, you should be able to put that in place of your Privacy.py and be OK. Things you need to be aware of are: 1) This will add a text box and help for nonmember_rejection_notice to Privacy options...->Sender filters, but this won't work. You can add text, but the code to use it isn't there. 2) This will add the note Note that headers are collected from all the attachments (except for the mailman administrivia message) and matched against the regular expressions. With this feature, you can effectively sort out messages with dangerous file types or file name extensions. to the help for header_filter_rules, but this will not be true as in 2.1.5, the subpart headers weren't examined. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 16 22:04:34 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 13:04:34 -0800 Subject: [Mailman-Users] Spam Filter disappearing In-Reply-To: Message-ID: Mark Sapiro wrote: >Julia Frizzell wrote: >> >>Is there any way I can just apply a fix for this issue? The >>Sourceforge site seemed to have an updated Privacy.py file, but it >>also indicated in the comments that the way it was fixed required an >>awful hack, so I'm not extremely keen on just popping it there. > >I'm not sure what comment you are looking at I now see you were looking at the code, whereas I was looking at log messages. Actually, the comment about "awful hack" predates 2.1.5 and doesn't refer to the fix for the disappearing header_filter_rules. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gus at clacso.edu.ar Tue Jan 16 21:51:06 2007 From: gus at clacso.edu.ar (Gustavo U. Navarro) Date: Tue, 16 Jan 2007 17:51:06 -0300 Subject: [Mailman-Users] newsletter Message-ID: <45AD3ABA.2020305@clacso.edu.ar> Hi One questions!! Is there a tools in mailman for integrate a mailman list with a newsletter!!! Thanks gus From josh at jbdesign.net Tue Jan 16 22:01:06 2007 From: josh at jbdesign.net (Josh Baird) Date: Tue, 16 Jan 2007 16:01:06 -0500 (EST) Subject: [Mailman-Users] From header Message-ID: <58343.12.169.54.3.1168981266.squirrel@webmail.jbdesign.net> Hi all, Is there a way to add a name to the From: header of the email? Instead of most email clients (Outlook, etc) simply stating the username of the email address, I would like our users to see "From: Our Company's Newsletter ." Thanks, Josh Baird From msapiro at value.net Tue Jan 16 22:34:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 13:34:41 -0800 Subject: [Mailman-Users] newsletter In-Reply-To: <45AD3ABA.2020305@clacso.edu.ar> Message-ID: Gustavo U. Navarro wrote: >Is there a tools in mailman for integrate a mailman list with a >newsletter!!! I'm not sure what you are looking for, but see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 16 22:38:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 13:38:12 -0800 Subject: [Mailman-Users] From header In-Reply-To: <58343.12.169.54.3.1168981266.squirrel@webmail.jbdesign.net> Message-ID: Josh Baird wrote: > >Is there a way to add a name to the From: header of the email? Instead of >most email clients (Outlook, etc) simply stating the username of the email >address, I would like our users to see "From: Our Company's Newsletter >." See the setting for anonymous_list on the list's General Options page. This will replace the contents of the From: header with the lists description and address. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lists at gmnet.net Tue Jan 16 23:24:19 2007 From: lists at gmnet.net (maillists) Date: Tue, 16 Jan 2007 17:24:19 -0500 Subject: [Mailman-Users] Mailman Update... Message-ID: <1168986259.10993.38.camel@localhost> Hi, I am about to do an update from Mailman 2.1.1 to 2.1.9 This is on an older RedHat 9 box. My Python version is 2.2.2 I believe that Mailman is installed via RPM. when I run "rpm qa |grep mailman" I get the following: mailman-2.1.1-5 My mailman "home" directory is /var/mailman I also have files in /var/log/mailman, /var/spool/mailman/ I basically have some questions and need moral support before I do this... I have lots of files in: /var/mailman/qfiles/shunt/ ans also /var/mailman/qfiles/bad/ What should I do with these? Were these old email messages that were never delivered? (I did have a problem with one of my lists not sending mail...) I downloaded the tarball of 2.1.9. the UPGRADE file said that the "upgrade" script would automatically run. Does this mean tht I should just do the ./configure thing as if this is a new install? Does this take care of everything? Finally is there anything that I should watch out for, or does anybody see if I might be heading for disaster? Thanks! rick From geoff at deering.id.au Tue Jan 16 23:30:07 2007 From: geoff at deering.id.au (Geoff Deering) Date: Wed, 17 Jan 2007 09:30:07 +1100 Subject: [Mailman-Users] Configuring Mailman as an announce list Message-ID: <45AD51EF.5050504@deering.id.au> Hi, Can someone please remind me how to configure mailman so that subscriber cannot post to it, only those registered in [Sender filters] List of non-member addresses whose postings should be automatically accepted. I have By default, should new list member postings be moderated? No Action to take when a moderated member posts to the list. Reject Is there something else I am overlooking? Running version 2.1.9.cp2 Geoff From brad at python.org Tue Jan 16 23:27:32 2007 From: brad at python.org (Brad Knowles) Date: Tue, 16 Jan 2007 16:27:32 -0600 Subject: [Mailman-Users] Mailman listed on Update-Scout.com In-Reply-To: <45AC8FF1.2090000@elementec.de> References: <45AC8FF1.2090000@elementec.de> Message-ID: At 9:42 AM +0100 1/16/07, Peter Kullmann wrote: > Mailman has just been added to Update-Scout.com, an interactive web > service, that informs its users about software updates and releases. It is not appropriate to post advertisements of this sort to this mailing list. We consider this to be spamming our list participants. If you want to have your site included in the known set of providers with Mailman services, please see FAQ 1.17 at and follow the links there. -- Brad Knowles Member of the Python.org Postmaster Team Co-moderator of mailman-users and mailman-developers mailing lists From josh at jbdesign.net Tue Jan 16 23:51:09 2007 From: josh at jbdesign.net (Josh Baird) Date: Tue, 16 Jan 2007 17:51:09 -0500 (EST) Subject: [Mailman-Users] From header In-Reply-To: References: <58343.12.169.54.3.1168981266.squirrel@webmail.jbdesign.net> Message-ID: <62237.12.169.54.115.1168987869.squirrel@webmail.jbdesign.net> Mark, I currently have that setting on, and the list description is not in the From: header. Any ideas? Josh > Josh Baird wrote: >> >>Is there a way to add a name to the From: header of the email? Instead >> of >>most email clients (Outlook, etc) simply stating the username of the >> email >>address, I would like our users to see "From: Our Company's Newsletter >>." > > > See the setting for anonymous_list on the list's General Options page. > This will replace the contents of the From: header with the lists > description and address. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Josh Baird JB Design - Professional Web Devel. & IT Consulting Phone: (859) 583-4214 Fax: (859) 239-0031 http://www.jbdesign.net From brad at shub-internet.org Tue Jan 16 23:44:26 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 16 Jan 2007 16:44:26 -0600 Subject: [Mailman-Users] Mailman Update... In-Reply-To: <1168986259.10993.38.camel@localhost> References: <1168986259.10993.38.camel@localhost> Message-ID: At 5:24 PM -0500 1/16/07, maillists wrote: > I basically have some questions and need moral support before I do > this... The upgrade process may be different for you, as it appears that you are using a packaged version from your OS provider. You would need to talk to the person or the group that created that package in order to get details of how their version of the upgrade process would work. > I have lots of files in: > /var/mailman/qfiles/shunt/ ans also /var/mailman/qfiles/bad/ > What should I do with these? For the most part, you shouldn't need to do anything with them. You probably want to take a look at them and see what they are before you throw them away, however. > Were these old email messages that were never delivered? Yup. > I downloaded the tarball of 2.1.9. the UPGRADE file said that the > "upgrade" script would automatically run. Does this mean tht I should > just do the ./configure thing as if this is a new install? Does this > take care of everything? You can't use the standard upgrade process to go from the packaged version of Mailman from someone else to our standard version. If you want to stick with the packaged version, you should get the latest version of the package from the appropriate OS vendor facilities, and use their support mechanism for any questions you may have about their version of Mailman. If you want to use our standard tarball, that will mean a completely separate and distinct installation. Our upgrade process doesn't know anything about the configuration files and locations of data from the packaged version, so you would need to manually copy over everything you wanted to keep. > Finally is there anything that I should watch out for, or does anybody > see if I might be heading for disaster? If you've never installed our software from our standard version of the tarball, then this process is likely to be more work than you're used to. You're going to need to decide whether or not you're going to stick with the packaged version of Mailman as available from your OS provider (and if so, then you need to use their support facilities for any questions you might have), or if you're going to use our standard version as available from our download page. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From brad at shub-internet.org Tue Jan 16 23:46:11 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 16 Jan 2007 16:46:11 -0600 Subject: [Mailman-Users] Configuring Mailman as an announce list In-Reply-To: <45AD51EF.5050504@deering.id.au> References: <45AD51EF.5050504@deering.id.au> Message-ID: At 9:30 AM +1100 1/17/07, Geoff Deering wrote: > Can someone please remind me how to configure mailman so that subscriber > cannot post to it, only those registered in Search the FAQ Wizard for "announce". Read all the entries that are found. If you still have questions, we can try to clear things up for you. > Running version 2.1.9.cp2 I'm not sure which version this is. None of our official versions have a designator like ".cp2" at the end. If this is a cPanel-installed version, please see FAQ 6.11. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From msapiro at value.net Wed Jan 17 00:48:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 15:48:51 -0800 Subject: [Mailman-Users] Configuring Mailman as an announce list In-Reply-To: <45AD51EF.5050504@deering.id.au> Message-ID: Geoff Deering wrote: > >Can someone please remind me how to configure mailman so that subscriber >cannot post to it, only those registered in > >[Sender filters] >List of non-member addresses whose postings should be automatically >accepted. Brad has already referred you to the FAQ where you should find article 3.11 to answer your questions. >I have > >By default, should new list member postings be moderated? No This should be Yes so new members are moderated by default. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 17 00:57:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 15:57:17 -0800 Subject: [Mailman-Users] From header In-Reply-To: <62237.12.169.54.115.1168987869.squirrel@webmail.jbdesign.net> Message-ID: Josh Baird wrote: > >I currently have that setting on, and the list description is not in the >From: header. Any ideas? What Mailman version is this? The list description wasn't added to the From: header for anonymous lists until 2.1.6. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From geoff at deering.id.au Wed Jan 17 01:14:47 2007 From: geoff at deering.id.au (Geoff Deering) Date: Wed, 17 Jan 2007 11:14:47 +1100 Subject: [Mailman-Users] Configuring Mailman as an announce list In-Reply-To: References: Message-ID: <45AD6A77.7070209@deering.id.au> Thanks Mark and Brad. Found both Python and GNU FAQs, and found the answer, nice and clear. Thanks Geoff Mark Sapiro said the following on 17/01/2007 10:48 AM: > Geoff Deering wrote: > >> Can someone please remind me how to configure mailman so that subscriber >> cannot post to it, only those registered in >> >> [Sender filters] >> List of non-member addresses whose postings should be automatically >> accepted. >> > > > Brad has already referred you to the FAQ where you should find article > 3.11 to answer your questions. > > > >> I have >> >> By default, should new list member postings be moderated? No >> > > > This should be Yes so new members are moderated by default. > > From djk at tobit.co.uk Wed Jan 17 01:16:32 2007 From: djk at tobit.co.uk (Dirk Koopman) Date: Wed, 17 Jan 2007 00:16:32 +0000 Subject: [Mailman-Users] Low level smtp error In-Reply-To: <200701161957.37283.patrick@malkin.de> References: <20070116181722.GA27237@allhats.xcski.com> <45AD1885.9000805@tobit.co.uk> <200701161957.37283.patrick@malkin.de> Message-ID: <45AD6AE0.2040100@tobit.co.uk> Patrick Franz wrote: > Hi all, > > thank you for your help, it's finally working. > > I changed the local_interfaces to "local_interfaces = 0.0.0.0" and > changed the SMTPHOST to 130.83.2.184. If you simply comment out the local_interfaces line in exim.conf (0.0.0.0 is the default), you will not need to set SMTPHOST From msapiro at value.net Wed Jan 17 01:22:09 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 16:22:09 -0800 Subject: [Mailman-Users] Mailman Update... In-Reply-To: <1168986259.10993.38.camel@localhost> Message-ID: maillists wrote: > >I am about to do an update from Mailman 2.1.1 to 2.1.9 > >This is on an older RedHat 9 box. >My Python version is 2.2.2 >I believe that Mailman is installed via RPM. I don't think it is as bad as Brad indicates in his reply. I think running configure with "--prefix=/var/mailman" will get you close on older RedHat. You'll probably also need --with-cgi-gid and --with-mail-gid (see ). A more serious issue is Mailman 2.1.9 requires Python 2.3. See which contains a link to a post containing a work around. >when I run "rpm qa |grep mailman" I get the following: >mailman-2.1.1-5 > >My mailman "home" directory is /var/mailman The --prefix above takes care of that. >I also have files in /var/log/mailman, /var/spool/mailman/ These are set in mm_cfg.py which will not be overwritten by 'make install' >I basically have some questions and need moral support before I do >this... > >I have lots of files in: >/var/mailman/qfiles/shunt/ ans also /var/mailman/qfiles/bad/ >What should I do with these? >Were these old email messages that were never delivered? You don't need to do anything, but probably 'old' files should just be deleted. The messages in shunt/ were messages that encountered some error in processing and were shunted. There were messages in Mailman's 'error' log for each one, but these have been probably logrotated into oblivion. The messages in bad/ are messages which were 'preserved' by content filtering's filter_action. >(I did have a problem with one of my lists not sending mail...) That may be the source of the shunted messages. >I downloaded the tarball of 2.1.9. the UPGRADE file said that the >"upgrade" script would automatically run. Does this mean tht I should >just do the ./configure thing as if this is a new install? Does this >take care of everything? Assuming you get the right options to configure, 'make install' will take care of everything. >Finally is there anything that I should watch out for, or does anybody >see if I might be heading for disaster? See above regarding Python incompatability. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From josh at jbdesign.net Wed Jan 17 03:58:28 2007 From: josh at jbdesign.net (Josh Baird) Date: Tue, 16 Jan 2007 21:58:28 -0500 (EST) Subject: [Mailman-Users] From header In-Reply-To: References: <62237.12.169.54.115.1168987869.squirrel@webmail.jbdesign.net> Message-ID: <61314.74.140.192.75.1169002708.squirrel@webmail.jbdesign.net> Turns out I'm not in the best position to upgrade. This system is in heavy production right now, and the most current package from the CentOS repos is currently 2.1.5. I could uninstall completely, and compile 2.1.9 from source I suppose - but would it be easier to simply edit a couple lines of code to add the list description to the From: header? If so, do you know where I could do this? Thanks, Josh Baird > Josh Baird wrote: >> >>I currently have that setting on, and the list description is not in the >>From: header. Any ideas? > > > What Mailman version is this? The list description wasn't added to the > From: header for anonymous lists until 2.1.6. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Josh Baird JB Design - Professional Web Devel. & IT Consulting Phone: (859) 583-4214 Fax: (859) 239-0031 http://www.jbdesign.net From msapiro at value.net Wed Jan 17 04:19:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 19:19:49 -0800 Subject: [Mailman-Users] From header In-Reply-To: <61314.74.140.192.75.1169002708.squirrel@webmail.jbdesign.net> Message-ID: Josh Baird wrote: >but would it be easier to simply edit a couple >lines of code to add the list description to the From: header? > >If so, do you know where I could do this? See -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From josh at jbdesign.net Wed Jan 17 05:19:21 2007 From: josh at jbdesign.net (Josh Baird) Date: Tue, 16 Jan 2007 23:19:21 -0500 (EST) Subject: [Mailman-Users] From header In-Reply-To: References: <61314.74.140.192.75.1169002708.squirrel@webmail.jbdesign.net> Message-ID: <63100.12.169.54.115.1169007561.squirrel@webmail.jbdesign.net> Hmm.. i18ndesc = str(uheader(mlist, mlist.description, 'From')) msg['From'] = formataddr((i18ndesc, mlist.GetListEmail())) Adding those (changing the 2nd line) seemed to break Mailman.. Nothing is getting delivered. The mails are not going out: Jan 16 23:06:45 boxname postfix/local[3079]: AA36831C4FB: to=, relay=local, delay=1, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post list) Is the last thing I see in the maillog.. maybe I should just try upgrading to 2.1.9 by specifying --prefix=/usr/lib/mailman in the configure? > Josh Baird wrote: > >>but would it be easier to simply edit a couple >>lines of code to add the list description to the From: header? >> >>If so, do you know where I could do this? > > > See > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Josh Baird JB Design - Professional Web Devel. & IT Consulting Phone: (859) 583-4214 Fax: (859) 239-0031 http://www.jbdesign.net From josh at jbdesign.net Wed Jan 17 05:33:39 2007 From: josh at jbdesign.net (Josh Baird) Date: Tue, 16 Jan 2007 23:33:39 -0500 (EST) Subject: [Mailman-Users] From header In-Reply-To: <63100.12.169.54.115.1169007561.squirrel@webmail.jbdesign.net> References: <61314.74.140.192.75.1169002708.squirrel@webmail.jbdesign.net> <63100.12.169.54.115.1169007561.squirrel@webmail.jbdesign.net> Message-ID: <63596.12.169.54.115.1169008419.squirrel@webmail.jbdesign.net> Sorry, stupid mistake on my behalf. All fixed now by editing Cleanse.py. Thanks for the help once again! > Hmm.. > > i18ndesc = str(uheader(mlist, mlist.description, 'From')) > msg['From'] = formataddr((i18ndesc, mlist.GetListEmail())) > > Adding those (changing the 2nd line) seemed to break Mailman.. Nothing is > getting delivered. The mails are not going out: > > Jan 16 23:06:45 boxname postfix/local[3079]: AA36831C4FB: > to=, relay=local, delay=1, status=sent (delivered to > command: /usr/lib/mailman/mail/mailman post list) > > Is the last thing I see in the maillog.. maybe I should just try upgrading > to 2.1.9 by specifying --prefix=/usr/lib/mailman in the configure? > > > > >> Josh Baird wrote: >> >>>but would it be easier to simply edit a couple >>>lines of code to add the list description to the From: header? >>> >>>If so, do you know where I could do this? >> >> >> See >> >> >> -- >> Mark Sapiro The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> >> > > > -- > Josh Baird > JB Design - Professional Web Devel. & IT Consulting > Phone: (859) 583-4214 > Fax: (859) 239-0031 > http://www.jbdesign.net > > -- Josh Baird JB Design - Professional Web Devel. & IT Consulting Phone: (859) 583-4214 Fax: (859) 239-0031 http://www.jbdesign.net From msapiro at value.net Wed Jan 17 05:31:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 16 Jan 2007 20:31:17 -0800 Subject: [Mailman-Users] From header In-Reply-To: <63100.12.169.54.115.1169007561.squirrel@webmail.jbdesign.net> Message-ID: Josh Baird wrote: >Hmm.. > > i18ndesc = str(uheader(mlist, mlist.description, 'From')) > msg['From'] = formataddr((i18ndesc, mlist.GetListEmail())) > >Adding those (changing the 2nd line) seemed to break Mailman.. Nothing is >getting delivered. The mails are not going out: Did you also add the lines: from email.Utils import formataddr from Mailman.Logging.Syslog import syslog from Mailman.Handlers.CookHeaders import uheader (the syslog line is not required if you didn't add the syslog('post', 'post to %s from %s anonymized', mlist.internal_name(), msg.get('from')) lines.) Did you pay attention to the indentation of the lines you added? They should be indented the same 8 spaces as the surrounding lines. Indentation counts in Python. >Jan 16 23:06:45 boxname postfix/local[3079]: AA36831C4FB: >to=, relay=local, delay=1, status=sent (delivered to >command: /usr/lib/mailman/mail/mailman post list) > >Is the last thing I see in the maillog.. maybe I should just try upgrading >to 2.1.9 by specifying --prefix=/usr/lib/mailman in the configure? You will find specific error traces in Mailman's error log and probably the messages have been shunted (placed in Mailman's qfiles/shunt/ queue). Once you have corrected Cleanse.py, you can restart Mailman again and run bin/unshunt to reprocess the shunted messages, but first make sure there are no old, unwanted messages in the shunt/ queue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Wed Jan 17 15:27:49 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Wed, 17 Jan 2007 9:27:49 -0500 Subject: [Mailman-Users] Emergency mail to everyone? Message-ID: <19841-SnapperMsgFB251063C1D3E2F0@[10.65.199.43]> My wife is asking what she needs to do with all my servers if i'm incapacitated or dead. One of the things that would need to be turned over to somebody else are all my mailman lists. And so one thing i'm looking at would be a way to send an announcement to all the lists on my server. I understand that you can send mail to a list with an x-approved with the list password, but can you do the same with the admin password? ___ Sent with SnapperMail www.snappermail.com From dave at hamnet.org Wed Jan 17 16:17:34 2007 From: dave at hamnet.org (Dave Foran) Date: Wed, 17 Jan 2007 10:17:34 -0500 Subject: [Mailman-Users] Subscription question(s) Message-ID: I have been looking thru the achives but alas. I am missing something ;-) Is there a way for a list moderator/owner to either unsubscribe or a subsctibe a user to the list using e-mail commands ?? -- Dave Foran Internet ONLY: dave at hamnet.org Cruise Missile Coordinates 41.36.46N 81.25.53W From ptomblin at xcski.com Wed Jan 17 16:58:00 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Wed, 17 Jan 2007 10:58:00 -0500 Subject: [Mailman-Users] Subscription question(s) In-Reply-To: References: Message-ID: <20070117155800.GB32164@allhats.xcski.com> Quoting Dave Foran (dave at hamnet.org): > I have been looking thru the achives but alas. I am missing something ;-) > > Is there a way for a list moderator/owner to either unsubscribe or a > subsctibe > a user to the list using e-mail commands ?? remove_members There is also a "add_members" command. -- Paul Tomblin http://blog.xcski.com/ "You are a human being, capable of emotions and rational thought. A computer is only capable of floating point math and crude malice." http://www.hamsterrepublic.com/james/technomancy/ From msapiro at value.net Wed Jan 17 16:58:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 17 Jan 2007 07:58:42 -0800 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: <19841-SnapperMsgFB251063C1D3E2F0@[10.65.199.43]> Message-ID: Paul Tomblin wrote: >And so one thing i'm looking at >would be a way to send an announcement to all the lists on my server. I >understand that you can send mail to a list with an x-approved with the >list password, but can you do the same with the admin password? If by admin password, you mean the site password, then No. You can include an Approve: or Approved: (not X-Approved:) header with either the list admin or list moderator password to get the message unconditionally accepted. You cannot use the site password for this. This is intentional to discourage sending the site password in the clear in email. You can also include an Urgent: header with the list admin or list moderator password to cause the message to be sent to all list members, digest and regular, without regard for nodups, not metoo, disabled delivery or topics. The message will still appear in the digest and will still be subject to holds unless Approved: is also included, -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Wed Jan 17 17:02:30 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Wed, 17 Jan 2007 11:02:30 -0500 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: References: <19841-SnapperMsgFB251063C1D3E2F0@[10.65.199.43]> Message-ID: <20070117160230.GD32164@allhats.xcski.com> Quoting Mark Sapiro (msapiro at value.net): > Paul Tomblin wrote: > > >And so one thing i'm looking at > >would be a way to send an announcement to all the lists on my server. I > >understand that you can send mail to a list with an x-approved with the > >list password, but can you do the same with the admin password? > > > If by admin password, you mean the site password, then No. > > You can include an Approve: or Approved: (not X-Approved:) header with > either the list admin or list moderator password to get the message > unconditionally accepted. You cannot use the site password for this. > This is intentional to discourage sending the site password in the > clear in email. You mean that if people used the Approve: header that Mailman doesn't strip it out before it sends it? That seems like a huge security hole. Is there a command line tool to approve messages? -- Paul Tomblin http://blog.xcski.com/ "All life is transitory. A dream. We all come together in the same place at the end of time. If I don't see you again here, I will see you in a little while in the place where no shadows fall." - Delenn From msapiro at value.net Wed Jan 17 17:05:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 17 Jan 2007 08:05:29 -0800 Subject: [Mailman-Users] Subscription question(s) In-Reply-To: <20070117155800.GB32164@allhats.xcski.com> Message-ID: Paul Tomblin wrote: >Quoting Dave Foran (dave at hamnet.org): >> >> Is there a way for a list moderator/owner to either unsubscribe or a >> subsctibe >> a user to the list using e-mail commands ?? > >remove_members >There is also a "add_members" command. But these are shell commands. The email subscribe and unsubscribe commands allow specifying an arbitrary address, but the subscribe is subject to the lists subscription confirmation/approval process. You can unsubscribe anyone by email if you know their list password, otherwise the unsubscribe has to be confirmed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 17 17:13:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 17 Jan 2007 08:13:12 -0800 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: <20070117160230.GD32164@allhats.xcski.com> Message-ID: Paul Tomblin wrote: > >You mean that if people used the Approve: header that Mailman doesn't >strip it out before it sends it? That seems like a huge security hole. No I don't mean that. It is removed whether or not the password is valid. When I said "This is intentional to discourage sending the site password in the clear in email." I meant in the email TO the list. The header won't be in the mail FROM the list. >Is there a command line tool to approve messages? No, but it would be pretty simple to modify bin/discard to make one. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Wed Jan 17 17:33:22 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Wed, 17 Jan 2007 11:33:22 -0500 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: References: <20070117160230.GD32164@allhats.xcski.com> Message-ID: <20070117163322.GA5209@allhats.xcski.com> Quoting Mark Sapiro (msapiro at value.net): > Paul Tomblin wrote: > > > >You mean that if people used the Approve: header that Mailman doesn't > >strip it out before it sends it? That seems like a huge security hole. > > > No I don't mean that. It is removed whether or not the password is > valid. When I said "This is intentional to discourage sending the site > password in the clear in email." I meant in the email TO the list. The > header won't be in the mail FROM the list. Well, that wouldn't be a problem in this case because it would be a user or script running on the same box as mailman. > >Is there a command line tool to approve messages? > > > No, but it would be pretty simple to modify bin/discard to make one. I'll look into that, thanks. -- Paul Tomblin http://blog.xcski.com/ "Dumbass PowarRanger Voltron is like the original PowarRanger Voltron, except no one can agree who forms the head, so all you're left with is five assholes." - siln From ddewey at cyberthugs.com Wed Jan 17 17:10:56 2007 From: ddewey at cyberthugs.com (Dave Dewey) Date: Wed, 17 Jan 2007 11:10:56 -0500 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: <19841-SnapperMsgFB251063C1D3E2F0@[10.65.199.43]> References: <19841-SnapperMsgFB251063C1D3E2F0@[10.65.199.43]> Message-ID: <20070117161056.GB22387@huntingcow.cyberthugs.com> Quoting Paul Tomblin (ptomblin at xcski.com): > My wife is asking what she needs to do with all my servers if i'm > incapacitated or dead. One of the things that would need to be turned over > to somebody else are all my mailman lists. And so one thing i'm looking at > would be a way to send an announcement to all the lists on my server. I > understand that you can send mail to a list with an x-approved with the > list password, but can you do the same with the admin password? If my wife started asking me questions like this I'd hire a food taster. dd From lstone19 at stonejongleux.com Wed Jan 17 17:50:55 2007 From: lstone19 at stonejongleux.com (Larry Stone) Date: Wed, 17 Jan 2007 10:50:55 -0600 (CST) Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: References: Message-ID: On Wed, 17 Jan 2007, Mark Sapiro wrote: > Paul Tomblin wrote: > > > >You mean that if people used the Approve: header that Mailman doesn't > >strip it out before it sends it? That seems like a huge security hole. > > No I don't mean that. It is removed whether or not the password is > valid. When I said "This is intentional to discourage sending the site > password in the clear in email." I meant in the email TO the list. The > header won't be in the mail FROM the list. But it also minimizes the risk of accidental disclosure of the site password. I assume if Approved was misspelled in a header or as the first line of the message, it would be included in the message if it was susequently approved by a moderator or met other critieria for not needing moderation. -- Larry Stone lstone19 at stonejongleux.com From msapiro at value.net Wed Jan 17 18:00:20 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 17 Jan 2007 09:00:20 -0800 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: Message-ID: Larry Stone wrote: > >But it also minimizes the risk of accidental disclosure of the site >password. I assume if Approved was misspelled in a header or as the first >line of the message, it would be included in the message if it was >susequently approved by a moderator or met other critieria for not needing >moderation. You are correct that the password could be accidently sent to the list if Approve(d) was misspelled. The risk of this is small as presumably the Approve(d) header/line wouldn't be included in the first place if the message wouldn't otherwise be held, but there is still the risk of someone approving the held post. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From t.d.lee at durham.ac.uk Wed Jan 17 17:55:19 2007 From: t.d.lee at durham.ac.uk (David Lee) Date: Wed, 17 Jan 2007 16:55:19 +0000 (GMT) Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: References: Message-ID: On Wed, 17 Jan 2007, Mark Sapiro wrote: > Paul Tomblin wrote: > > > >You mean that if people used the Approve: header that Mailman doesn't > >strip it out before it sends it? That seems like a huge security hole. > > > No I don't mean that. It is removed whether or not the password is > valid. When I said "This is intentional to discourage sending the site > password in the clear in email." I meant in the email TO the list. The > header won't be in the mail FROM the list. A slight caution there. If the inbound email contains not only the plain text message but also its equivalent in HTML and if the "Approved:" is specified as the first line of the body rather than as a header then the password is in danger of leaking outbound, being stripped only from the plain version but not from the HTML version where it could persist. endif For lists on which body-based "Approved" and HTML-ising senders are likely, it is worth investigating the "collapse_alternatives" and "convert_html_to_plaintext" settings. (I'm willing to be corrected on any of that!) -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. : From msapiro at value.net Wed Jan 17 18:08:04 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 17 Jan 2007 09:08:04 -0800 Subject: [Mailman-Users] Emergency mail to everyone? In-Reply-To: Message-ID: David Lee wrote: > >If the inbound email contains not only the plain text message but also its > equivalent in HTML >and if the "Approved:" is specified as the first line of the body rather > than as a header >then > the password is in danger of leaking outbound, being stripped only from > the plain version but not from the HTML version where it could persist. >endif This was bug 1181161 which was fixed in Mailman 2.1.7, but there can still be problems if 'Approved: password' gets split across lines in quoted printable encoded alternative parts or gets base64 encoded. It's on my list to fix these issues. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spambird at gmx.net Wed Jan 17 21:10:07 2007 From: spambird at gmx.net (Tommy Braun) Date: Wed, 17 Jan 2007 21:10:07 +0100 Subject: [Mailman-Users] template variables ??? Message-ID: <7k0tq25i2afn07c5vrqnm0rsf9rm3uogar@4ax.com> Hi, is there a detailed documentation about the template variables that are available for ALL the mailman files? As I found there seem to be several formats and ideas of how to write template variables, all different in the mail confirmation files, html and configuration interface....??? E.g. ownere-Mail does not work in the subscribeack.txt file. hmmm... Thank you very much for your attention! Tommy From brad at shub-internet.org Wed Jan 17 21:53:08 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 17 Jan 2007 14:53:08 -0600 Subject: [Mailman-Users] template variables ??? In-Reply-To: <7k0tq25i2afn07c5vrqnm0rsf9rm3uogar@4ax.com> References: <7k0tq25i2afn07c5vrqnm0rsf9rm3uogar@4ax.com> Message-ID: At 9:10 PM +0100 1/17/07, Tommy Braun wrote: > is there a detailed documentation about the template variables that > are available for ALL the mailman files? Not that I know of. > As I found there seem to be several formats and ideas of how to write > template variables, all different in the mail confirmation files, html > and configuration interface....??? E.g. ownere-Mail does not work in > the subscribeack.txt file. hmmm... Among other things, I believe that different variables are available in different template files, because they are referenced in different places in the code. Even if there were a single place where all the potential template variables were listed, I don't believe that they would all be available in all templates. I believe that you'd need to check the source code to find out which variables are available in which templates. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From gus at clacso.edu.ar Wed Jan 17 23:43:37 2007 From: gus at clacso.edu.ar (Gustavo U. Navarro) Date: Wed, 17 Jan 2007 19:43:37 -0300 Subject: [Mailman-Users] hello postfix and mailman Message-ID: <45AEA699.1050208@clacso.edu.ar> Dears I have a problem with postfix...and mailman Postfix is run ok but when run with mailman said one error Recipient address rejected: User unknown in local recipient table.. These is my file main.cf myhostname = piluso.clacso.edu.ar # mydomain = clacso.edu.ar alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = clacso.edu.ar, piluso.clacso.edu.ar, muleto.clacso.edu.ar, local host.clacso.edu.ar, , localhost relayhost = mynetworks = 127.0.0.0/8, 168.96.200.0/24 mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all # configuracion mailman relay_domains = piluso.clacso.edu.ar transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 ---------------------------------------------------------------------------------------------------------------- master.cf I put in the file Configuracion para mailman mailman unix - n n - - pipe flags=FR user=list argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} ------------------------------------------------------------------------------------------------------------------------ I created transport with piluso.clacso.edu.ar mailman: after I created the transport.db ----------------------------------------------------------------------- in mm_cfg.py I created # configuracion para mailman MTA = None # No MTA alias processing required #alias for postmaster, abuse and mailer-daemon DEB_LISTMASTER = 'gus at clacso.edu.ar' Someone could help me!!!! Thanks gus From jwblist3 at olympus.net Wed Jan 17 23:55:45 2007 From: jwblist3 at olympus.net (John W. Baxter) Date: Wed, 17 Jan 2007 14:55:45 -0800 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages In-Reply-To: <87bqkz2f58.fsf@be.cs.appstate.edu> Message-ID: On 1/16/07 6:57 AM, "Kenneth Jacker" wrote: > I appreciate both Mark and Barry's informative and prompt replies. > > Let me do a little more investigating ... maybe there's some conflict > with one of my FF plugins ... Did you install a new plugin (or update one) about the time the problem started? A nice thing about Firefox is the wealth of available extensions. The problem with that is that just saying Firefox doesn't identify what is running. --John From carlp at wetleather.com Thu Jan 18 01:18:04 2007 From: carlp at wetleather.com (Carl Paukstis) Date: Wed, 17 Jan 2007 16:18:04 -0800 Subject: [Mailman-Users] Bounce - raw bounce messages? In-Reply-To: References: Message-ID: <20070118001804.GA678@moto1.micapeak.com> I am the system admin and list admin. We're running Mailman 2.1.9 on RHEL. On a moderately high-volume social/chat list, a list member keeps getting disabled for bounces, though he does get SOME or most of his list mail, and gets the "you are disabled" message. What's the best way for me to get/find and examine the actual "raw" bounce messages coming back from his mail server that are causing him to get disabled, so we can work with his provider or filter to prevent this? -- Carl Paukstis carlp at wetleather.com WetLeather.com / Micapeak.com listmaster at micapeak.com Spokane, Washington, USA http://www.paukstis.com/ From brad at shub-internet.org Thu Jan 18 04:59:47 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 17 Jan 2007 21:59:47 -0600 Subject: [Mailman-Users] Bounce - raw bounce messages? In-Reply-To: <20070118001804.GA678@moto1.micapeak.com> References: <20070118001804.GA678@moto1.micapeak.com> Message-ID: At 4:18 PM -0800 1/17/07, Carl Paukstis wrote: > What's the best way for me to get/find and examine the actual "raw" > bounce messages coming back from his mail server that are causing him > to get disabled, so we can work with his provider or filter to prevent > this? Change the alias for -bounces to point directly to your e-mail address, or other suitable e-mail address for the list admins. That way you bypass all bounce processing within Mailman. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From hafter at switch.ch Thu Jan 18 08:12:01 2007 From: hafter at switch.ch (Bettina Hafter) Date: Thu, 18 Jan 2007 08:12:01 +0100 Subject: [Mailman-Users] spam filters should only match list-members Message-ID: <45AF1DC1.9080207@switch.ch> hey there i'v been searching through all archive and FAQ Wizard but could not find the answer. We have a list, which discards all non-members. We have 2 filters which go for spams. 1st filter, if the X-SPAM-header contains xxxxxxx, discard it 2nd filter, if the X-SPAM-header contains xxxx, set it on hold now all the spamers which are marked by our spamassin with xxxx in the mail-header are set on hold. is there a way to teach mailman to do something like that: - discard mails of non-members, regardless whether they match the filters or not - make spam control only for members thanks bettina From her at adm.ku.dk Thu Jan 18 10:50:41 2007 From: her at adm.ku.dk (Henrik Rasmussen) Date: Thu, 18 Jan 2007 10:50:41 +0100 Subject: [Mailman-Users] Mailman's root path or where to place images In-Reply-To: Message-ID: <78E3AAA50C11F0419C4C3F41707B65300954304C@taipan.ad.adm.ku.dk> Thank you Mark. According to my colleague, our Mailman installation is installed by clicking a checkbox when installing RedHat Linux and it seems that it somehow doesn't make use of the httpd.conf file (which I don't understand) since the Script Alias is ScriptAlias /cgi-bin/ "/var/www/cgi-bin/". (which is an empty directory) and Mailman's CGI-scripts is contained in /usr/lib/mailman/cgi-bin/ though you are right about the conflict using Alias /mailman/ /usr/lib/mailman/ so somehow it must be using httpd.conf anyway. I am totally new to both Mailman and Apache so I don't yet know how they work. For now I think i'll scrub the proxy thing, but it would be nice to know how Mailman corresponds with httpd.conf in the default Redhat installation. Henrik -----Oprindelig meddelelse----- Fra: Mark Sapiro [mailto:msapiro at value.net] Sendt: 16. januar 2007 19:35 Til: Henrik Rasmussen; mailman-users at python.org Emne: Re: [Mailman-Users] Mailman's root path or where to place images Henrik Rasmussen wrote: > >I currently have my mailman icons in an /icons directory relative to >Apache's root directory. > >Example: > >Icons is in /var/www/icons/ and the source http path to the icons is >http://server.xxx.yyy.zz/icons/ > >In order to put the server behind a proxy server, I need to change the >directory to http://server.xxx.yyy.zz/mailman/icons/ If it really has to be http://server.xxx.yyy.zz/mailman/icons/ and http://server.xxx.yyy.zz/something_else/ won't do, I think you have only one choice. See below. >By changing the variable IMAGE_LOGOS = '/icons/' to IMAGE_LOGOS = >'icons/' in the file /usr/lib/mailman/Mailman/mm_cfg.py the http path is >seemly relative to Mailman's root >http://server.xxx.yyy.zz/mailman/icons/ Actually, it is just a relative path in the HTML to which your browser prepends the current location. >which I suppose should be >/usr/lib/mailman/icons/ ,but moving the image file >/usr/lib/mailman/icons/ still results in a missing image. > >My question is, where Mailman's root directory is suppose to be, or >rather which directory on the server correspond to >http://server.xxx.yyy.zz/mailman/icons/? You have something like ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ in your httpd.conf, so http://server.xxx.yyy.zz/mailman/icons/ corresponds to the CGI named icons in the directory /usr/lib/mailman/cgi-bin/. Ideally, you could alias it in your Apache httpd.conf with something like Alias /mailman/ /usr/lib/mailman/ except this won't work because of the conflict with the ScriptAlias. If you really need the URL for the icons to be http://example.com/mailman/icons/, I think you need to create an 'icons' CGI and put it in /usr/lib/mailman/cgi-bin/. This would be a simple CGI that would just parse the name following http://example.com/mailman/icons/ in the URL and locate and serve that file. There may be some other way to address this in the Apache configuration, but that's an Apache question that I don't know the answer to. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Thu Jan 18 13:52:50 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Thu, 18 Jan 2007 07:52:50 -0500 Subject: [Mailman-Users] Mailman's root path or where to place images In-Reply-To: <78E3AAA50C11F0419C4C3F41707B65300954304C@taipan.ad.adm.ku.dk> References: <78E3AAA50C11F0419C4C3F41707B65300954304C@taipan.ad.adm.ku.dk> Message-ID: <20070118125250.GC24005@allhats.xcski.com> Quoting Henrik Rasmussen (her at adm.ku.dk): > Thank you Mark. According to my colleague, our Mailman installation is > installed by clicking a checkbox when installing RedHat Linux and it > seems that it somehow doesn't make use of the httpd.conf file (which I > don't understand) since the Script Alias is Depending on the age of your RedHat installation, the mailman rpm should configure Apache for its own purposes by dropping a file in /etc/httpd/conf.d/ -- Paul Tomblin http://blog.xcski.com/ You had me at print("Hello World\n"); From lists at gmnet.net Thu Jan 18 15:24:34 2007 From: lists at gmnet.net (maillists) Date: Thu, 18 Jan 2007 09:24:34 -0500 Subject: [Mailman-Users] Python Requirement Message-ID: <1169130274.10993.127.camel@localhost> Hi, I am upgrading to Mailman 2.1.9 from 2.1.1. I have Python 2.2.2. installed. I am going to un-install and re-install Mailman altogether because I only have a few lists, and I currently have Mailman installed from an RPM and I now want to install it from source. The manual says that Python 2.1 is required, but 2.3 is preferred. http://www.gnu.org/software/mailman/mailman-install/node2.html Is it OK to keep Python my 2.2.? Am I headed for trouble at all? I still need a push to jump off this cliff. Thanks! rick From pdbogen at gmail.com Thu Jan 18 17:54:13 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 18 Jan 2007 10:54:13 -0600 Subject: [Mailman-Users] Python Requirement In-Reply-To: <1169130274.10993.127.camel@localhost> References: <1169130274.10993.127.camel@localhost> Message-ID: <6fbe3da00701180854x55da163bx5424d056b03ed30a@mail.gmail.com> On 1/18/07, maillists wrote: > Is it OK to keep Python my 2.2.? Am I headed for trouble at all? I > still need a push to jump off this cliff. You fool! You'll doom us all with your Python 2.2 foolishness! Ahem. That said, I don't know of any problems with python 2.2, but others may know better. I guess this is a production box? Any chance you could build a test box (vmware image?), install the newest mailman with python 2.2 on that, and test it? -- - Patrick Bogen From khj at be.cs.appstate.edu Thu Jan 18 17:10:12 2007 From: khj at be.cs.appstate.edu (Kenneth Jacker) Date: Thu, 18 Jan 2007 11:10:12 -0500 Subject: [Mailman-Users] OT: Firefox Crashing on Admin Pages In-Reply-To: (John W. Baxter's message of "Wed, 17 Jan 2007 14:55:45 -0800") References: Message-ID: <87irf4xqmz.fsf@be.cs.appstate.edu> jwb> Did you install a new plugin (or update one) about the time the jwb> problem started? No. -Kenneth From msapiro at value.net Thu Jan 18 21:25:38 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 18 Jan 2007 12:25:38 -0800 Subject: [Mailman-Users] Python Requirement In-Reply-To: <6fbe3da00701180854x55da163bx5424d056b03ed30a@mail.gmail.com> Message-ID: Patrick Bogen wrote: >On 1/18/07, maillists wrote: >> Is it OK to keep Python my 2.2.? Am I headed for trouble at all? I >> still need a push to jump off this cliff. >You fool! You'll doom us all with your Python 2.2 foolishness! > > >Ahem. That said, I don't know of any problems with python 2.2, but >others may know better. >I guess this is a production box? Any chance you could build a test >box (vmware image?), install the newest mailman with python 2.2 on >that, and test it? See the reply (to one of maillist's earlier posts) at . Also see . Mailman 2.1.9 et seq requires Python 2.3. In 2.1.9, the work-around is not too difficult, but it will only get worse. Mailman 2.2 will require Python 2.4. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 18 21:32:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 18 Jan 2007 12:32:41 -0800 Subject: [Mailman-Users] Bounce - raw bounce messages? In-Reply-To: <20070118001804.GA678@moto1.micapeak.com> Message-ID: Carl Paukstis wrote: > >What's the best way for me to get/find and examine the actual "raw" >bounce messages coming back from his mail server that are causing him >to get disabled, so we can work with his provider or filter to prevent >this? Set bounce_notify_owner_on_disable to Yes. The notice contains a copy of the bounce. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jan 18 21:59:08 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 18 Jan 2007 12:59:08 -0800 Subject: [Mailman-Users] spam filters should only match list-members In-Reply-To: <45AF1DC1.9080207@switch.ch> Message-ID: Bettina Hafter wrote: > >We have a list, which discards all non-members. We have 2 filters which >go for spams. > >1st filter, if the X-SPAM-header contains xxxxxxx, discard it >2nd filter, if the X-SPAM-header contains xxxx, set it on hold > >now all the spamers which are marked by our spamassin with xxxx in the >mail-header are set on hold. > >is there a way to teach mailman to do something like that: > >- discard mails of non-members, regardless whether they match the >filters or not >- make spam control only for members The issue is because of the order in which things are done in the pipeline of handlers that Mailman uses to process the mail. header_filter_rules are processed by SpamDetect which is first. Membership tests are done in Moderate which comes later. Once a message is held, no more processing is done. If you want to do the membership tests before header_filter_rules, you can reorder the pipeline. This won't work in general because it would apply a moderation hold or reject action or a nonmember hold or reject action before the spam discard action, but in your case where the nonmember action is discard, it may be OK You could put the following lines in mm_cfg.py and restart Mailman to put SpamDetect after Moderate. GLOBAL_PIPELINE.remove('SpamDetect') GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('Moderate') + 1, 'SpamDetect') (the GLOBAL_PIPELINE.insert line is wrapped by my MUA, but it doesn't matter because of Python's 'automatic continuation within parentheses' feature.) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From gus at clacso.edu.ar Fri Jan 19 01:35:58 2007 From: gus at clacso.edu.ar (Gustavo U. Navarro) Date: Thu, 18 Jan 2007 21:35:58 -0300 Subject: [Mailman-Users] and postfix In-Reply-To: References: Message-ID: <45B0126E.4080702@clacso.edu.ar> Mark Could you help me!!! Dears I have a problem with postfix...and mailman Postfix is run ok but when run with mailman said one error Recipient address rejected: User unknown in local recipient table.. These is my file main.cf myhostname = piluso.clacso.edu.ar # mydomain = clacso.edu.ar alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = /etc/mailname mydestination = clacso.edu.ar, piluso.clacso.edu.ar, muleto.clacso.edu.ar, local host.clacso.edu.ar, , localhost relayhost = mynetworks = 127.0.0.0/8, 168.96.200.0/24 mailbox_command = procmail -a "$EXTENSION" mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all # configuracion mailman relay_domains = piluso.clacso.edu.ar transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 ---------------------------------------------------------------------------------------------------------------- master.cf I put in the file Configuracion para mailman mailman unix - n n - - pipe flags=FR user=list argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} ------------------------------------------------------------------------------------------------------------------------ I created transport with piluso.clacso.edu.ar mailman: after I created the transport.db ----------------------------------------------------------------------- in mm_cfg.py I created # configuracion para mailman MTA = None # No MTA alias processing required #alias for postmaster, abuse and mailer-daemon DEB_LISTMASTER = 'gus at clacso.edu.ar' Someone could help me!!!! Thanks gus Mark Sapiro escribi?: > Gustavo U. Navarro wrote: > > >> Is there a tools in mailman for integrate a mailman list with a >> newsletter!!! >> > > > I'm not sure what you are looking for, but see > . > > From msapiro at value.net Fri Jan 19 02:14:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 18 Jan 2007 17:14:26 -0800 Subject: [Mailman-Users] and postfix In-Reply-To: <45B0126E.4080702@clacso.edu.ar> Message-ID: Gustavo U. Navarro wrote: >Mark >Could you help me!!! No, I can't. I know very little about Postfix. I saw your original post and did not reply because I don't know what the problem is. This would appear to be a problem somewhere in the Postfix configuration. I doubt the mail is even getting to the postfix-to-mailman.py script. You need to contact a Postfix list or possibly the author of postfix-to-mailman.py or possibly Debian or Ubuntu if this is a Debian or Ubuntu package. You may also be interested in >master.cf > >I put in the file > >Configuracion para mailman > > mailman unix - n n - - pipe > flags=FR user=list the comments in postfix-to-mailman-2.1.py say the above line should be flags=FR user=mailman:mailman >From this I gather that user= specifies a user and group under which to run the pipe below. This almost certainly needs to be the mailman user and group (which may be 'list' in your case, but maybe not). > argv=/var/lib/mailman/bin/postfix-to-mailman.py ${nexthop} ${user} -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From lstone19 at stonejongleux.com Fri Jan 19 04:41:50 2007 From: lstone19 at stonejongleux.com (Larry Stone) Date: Thu, 18 Jan 2007 21:41:50 -0600 Subject: [Mailman-Users] and postfix In-Reply-To: <45B0126E.4080702@clacso.edu.ar> Message-ID: On 1/18/07 6:35 PM, Gustavo U. Navarro at gus at clacso.edu.ar wrote: > Postfix is run ok but when run with mailman said one error > > Recipient address rejected: User unknown in local recipient table.. To have mailman work with postfix, all the mailman addresses need to be in the Postfix alias file. That is: > main.cf > alias_maps = hash:/etc/aliases > alias_database = hash:/etc/aliases So far so good maybe. Are you manually putting the aliases in /etc/aliases? But better would be to let mailman take care of it for you. But for that to happen, instead of > in mm_cfg.py > MTA = None # No MTA alias processing required You need: MTA = 'Postfix' And then you need to tell Postfix where they are. In my postfix main.cf, I have: # Needed for Mailman alias_maps=hash:/etc/postfix/aliases, hash:/path_to_mailman/data/aliases -- Larry Stone lstone19 at stonejongleux.com http://www.stonejongleux.com/ From msapiro at value.net Fri Jan 19 04:50:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 18 Jan 2007 19:50:29 -0800 Subject: [Mailman-Users] and postfix In-Reply-To: Message-ID: Larry Stone wrote: >On 1/18/07 6:35 PM, Gustavo U. Navarro at gus at clacso.edu.ar wrote: > >> Postfix is run ok but when run with mailman said one error >> >> Recipient address rejected: User unknown in local recipient table.. > >To have mailman work with postfix, all the mailman addresses need to be in >the Postfix alias file. That is: Actually, Gustavo is trying to configure postfix-to-mailman.py which is an alternative to aliases along the lines of mm-handler and qmail-to-mailman.py, both of which are in Mailman's contrib/ directory. (postfix-to-mailman.py can be found with a google search) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dan at thecsl.org Fri Jan 19 15:34:17 2007 From: dan at thecsl.org (Dan MacNeil) Date: Fri, 19 Jan 2007 09:34:17 -0500 Subject: [Mailman-Users] spam filters should only match list-members In-Reply-To: <45AF1DC1.9080207@switch.ch> References: <45AF1DC1.9080207@switch.ch> Message-ID: <45B0D6E9.5070306@thecsl.org> I've often found reading the help for all the options in the admin interface to be helpful. > - discard mails of non-members, regardless whether they match the > filters or not From the admin interface: Privacy Options --> Sender Filters -->generic_nonmember_action : discard From the help link: (privacy): Action to take for postings from non-members for which no explicit action is defined. When a post from a non-member is received, the message's sender is matched against the list of explicitly accepted, held, rejected (bounced), and discarded addresses. If no match is found, then this action is taken. Hope this helps. > - make spam control only for members Bettina Hafter wrote: > hey there > > i'v been searching through all archive and FAQ Wizard but could not find > the answer. > > We have a list, which discards all non-members. We have 2 filters which > go for spams. > > 1st filter, if the X-SPAM-header contains xxxxxxx, discard it > 2nd filter, if the X-SPAM-header contains xxxx, set it on hold > > now all the spamers which are marked by our spamassin with xxxx in the > mail-header are set on hold. > > is there a way to teach mailman to do something like that: > > - discard mails of non-members, regardless whether they match the > filters or not > - make spam control only for members > > thanks > bettina > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dan%40thecsl.org > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From dan at thecsl.org Fri Jan 19 15:37:48 2007 From: dan at thecsl.org (Dan MacNeil) Date: Fri, 19 Jan 2007 09:37:48 -0500 Subject: [Mailman-Users] spam filters should only match list-members In-Reply-To: <45B0D6E9.5070306@thecsl.org> References: <45AF1DC1.9080207@switch.ch> <45B0D6E9.5070306@thecsl.org> Message-ID: <45B0D7BC.3050701@thecsl.org> Never mind, I just read Mark's post on this subject re editing the config file. Sorry for the noise Dan MacNeil wrote: > I've often found reading the help for all the options in the admin > interface to be helpful. > > > > - discard mails of non-members, regardless whether they match the > > filters or not > > From the admin interface: > > Privacy Options > --> Sender Filters > -->generic_nonmember_action : discard > > > From the help link: > > (privacy): Action to take for postings > from non-members for which no explicit > action is defined. > > When a post from a non-member is received, > the message's sender is matched against the > list of explicitly accepted, held, rejected > (bounced), and discarded addresses. If no > match is found, then this action is taken. > > Hope this helps. > > > > > > - make spam control only for members > > > Bettina Hafter wrote: >> hey there >> >> i'v been searching through all archive and FAQ Wizard but could not >> find the answer. >> >> We have a list, which discards all non-members. We have 2 filters >> which go for spams. >> >> 1st filter, if the X-SPAM-header contains xxxxxxx, discard it >> 2nd filter, if the X-SPAM-header contains xxxx, set it on hold >> >> now all the spamers which are marked by our spamassin with xxxx in the >> mail-header are set on hold. >> >> is there a way to teach mailman to do something like that: >> >> - discard mails of non-members, regardless whether they match the >> filters or not >> - make spam control only for members >> >> thanks >> bettina >> ------------------------------------------------------ >> Mailman-Users mailing list >> Mailman-Users at python.org >> http://mail.python.org/mailman/listinfo/mailman-users >> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py >> Searchable Archives: >> http://www.mail-archive.com/mailman-users%40python.org/ >> Unsubscribe: >> http://mail.python.org/mailman/options/mailman-users/dan%40thecsl.org >> >> Security Policy: >> http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > > From vancleef at bronze.lostwells.net Fri Jan 19 16:50:47 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Fri, 19 Jan 2007 08:50:47 -0700 (MST) Subject: [Mailman-Users] htdig authorization problem Message-ID: <200701191550.l0JFoljC016934@bronze.lostwells.net> I have mailman 2.1.9 with the htdig patch installed. Set up to do local search. I rebuilt the archives from the list mbox file a couple of weeks ago, and htdig would search on it, deliver pages, and they could be viewed. This week (several days later), to view a post requires entering a password before viewing. Trying to pull up a second page gets an error message. This affects using the list admin password as well as user passwords. To view any hit, a user account name or the admin pasword (not both) has to be entered in a validation screen. The mailman error log reports htsearch for list: mercedes, cause: auth, detail: -10- Browsers have cookies enabled (mine certainly does). Where do I look? Permissions on the private directory were 2770; I reset them to 2774. All of the files in private/listname are owner/group both mailman, permissions on files are 666, on directories, 2775. Where do I go from here? Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Fri Jan 19 18:31:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 09:31:35 -0800 Subject: [Mailman-Users] htdig authorization problem In-Reply-To: <200701191550.l0JFoljC016934@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: > >I rebuilt the archives from the list mbox file a couple of weeks ago, >and htdig would search on it, deliver pages, and they could be viewed. > >This week (several days later), to view a post requires entering >a password before viewing. Did you change the archive from public to private? Do you have to enter the password each time (not normal) or only once (normal for a private archive)? >Trying to pull up a second page gets an >error message. What error message? If it's the 'we hit a bug' message, what's in Mailman's error log? >This affects using the list admin password as well as >user passwords. To view any hit, a user account name or the admin >pasword (not both) has to be entered in a validation screen. Normal for a private archive, but should only be required the first time. >The mailman error log reports >htsearch for list: mercedes, cause: auth, detail: -10- Looking briefly at the htdig patch, I think this comes from mmsearch.py when private archive authorization fails. >Browsers have cookies enabled (mine certainly does). Where do I look? >Permissions on the private directory were 2770; I reset them to 2774. They shouldn't be 2774. They might need to be 2771 for public archive access to work. Otherwise 2770 should be fine. At this point the process should be running as the 'mailman' group because of the SETGID on the wrapper. >All of the files in private/listname are owner/group both mailman, >permissions on files are 666, on directories, 2775. > >Where do I go from here? I'm not sure anything is wrong, but if you are being required to authorize more than once per session per list, then there is a problem. What about normal archive access without searching? does that work? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jan 19 20:28:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 11:28:12 -0800 Subject: [Mailman-Users] htdig authorization problem In-Reply-To: <200701191831.l0JIV5kK024012@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: >The esteemed Mark Sapiro has said: >> >> Did you change the archive from public to private? Do you have to enter >> the password each time (not normal) or only once (normal for a private >> archive)? >> >I used bin/arch to build the archives from the mbox file, all in the >private directory. Then manually ran nightly_htdig to get the data >bases built. But was the archive 'private' or 'public' (admin Archiving options) before the problem started? >The scenario plays like this: > >On cold entry (no cookies in the browser) go to the archives page from >the main page. User validation screen pops up. Enter username and >password, and you get to the pipermail archives. You can now read those >all day without needing to revalidate. Good. >Now, set up an htdig search, which returns a few pages of hits. Click >on one of those hits, and the validation screen pops up again. >Validate, and the message is displayed. Go back and click on another >hit. The validation screen pops up again, and displays the page after >another validation. > >Trying to display the second page makes the I assume you mean the second page of hits. >htdig Archives Access Failure > >template page pop up. > >This happens with either a user or the admin password active. > >The error log message that accompanies this is: > >Jan 19 11:12:55 2007 (23983) htsearch for list: mercedes, cause: auth, >detail: -10- > >It seems clear to me that the htdig process is not able to find the validation >cookie. I don't think that is the issue. It seems to me that the htdig process finds the cookie the first time, but then removes it. This explains why you need to revalidate when you try to visit the message, and it explains why you get mmsearch.py's authorization error when you try to get the second page of hits. >If this were compiled code and not Python, I'd dbx the thing, >but don't know enough about Python to know how to use the debugging >resources. If there's some sort of crash and traceback message, I don't >know where to look for that either. There wouldn't be a traceback in this case. >For reference, the htdig (3.1.6) build was a default ./configure build. >It wouldn't compile with either the Solaris Studio 11 CC or g++ 4.1.1. >I loaded g++ 2.95.3 on another Solaris 9 machine, did a build there, NFS >mounted the source tree, and did a make install to get it on this >machine. The only additional step needed to get htdig to run its own >rundig was to copy libstdc++ into /usr/lib (a bug in the Solaris >Companion Disk g++ build). > >The default overrides in mm_cfg.py relative to archiving (you'll notice >that some are commented out----I copied this file from the old host >installation, and left the last guy's commented-out stuff in place) > ># HTDIG_MAILMAN_LINK = 'htdig-mailman' >HTDIG_RUNDIG_PATH = '/opt/www/htdig/bin/rundig' >HTDIG_HTSEARCH_PATH = '/opt/www/cgi-bin/htsearch' >USE_HTDIG = 1 > ># ARCHIVE_TO_MBOX = 1 > >GZIP_ARCHIVE_TXT_FILES = 0 It seems that htdig per se is working fine. It returns the hits. I think the problem is in mmsearch.py. It checks to be sure it is authorized for the private archive, and it is. It does the search and displays the results and somehow in this latter step the cookie is removed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Fri Jan 19 23:20:05 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Fri, 19 Jan 2007 15:20:05 -0700 (MST) Subject: [Mailman-Users] htdig authorization problem In-Reply-To: Message-ID: <200701192220.l0JMK507003026@bronze.lostwells.net> The esteemed Mark Sapiro has said: > > > But was the archive 'private' or 'public' (admin Archiving options) > before the problem started? > We're going back to Jan. 11 (when this started), and I'm trying to remember what I changed then. I suspect that I ran check_perms around then an fixed what it griped about, and the permissions on the private directory was one such. Let's assume this was the case (I can easily check, but I don't think setting the directory permission open really proves anything. Nonetheless, I should do it to see that it does clear the fault). > > >The scenario plays like this: > > > >On cold entry (no cookies in the browser) go to the archives page from > >the main page. User validation screen pops up. Enter username and > >password, and you get to the pipermail archives. You can now read those > >all day without needing to revalidate. > > > Good. > > > >Now, set up an htdig search, which returns a few pages of hits. Click > >on one of those hits, and the validation screen pops up again. > >Validate, and the message is displayed. Go back and click on another > >hit. The validation screen pops up again, and displays the page after > >another validation. > > > >Trying to display the second page makes the > > > I assume you mean the second page of hits. > Yes. Htdig will do the search and display a page of returns. Anything beyond that requires revalidation. > > > > >It seems clear to me that the htdig process is not able to find the validation > >cookie. > > > I don't think that is the issue. It seems to me that the htdig process > finds the cookie the first time, but then removes it. This explains > why you need to revalidate when you try to visit the message, and it > explains why you get mmsearch.py's authorization error when you try to > get the second page of hits. Yes, it's the second time in. Doing a second search on top of the first (i.e. changing the htdig search return display and telling it to search again) gets the error. > I have been reading the code (and Python in a Nutshell). mmsearch.py has if mlist.archive_private: if not mlist.WebAuthenticate((mm_cfg.AuthUser, mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin, mm_cfg.AuthSiteAdmin), '', ''): raise _search_exception(listname, 'auth', '-10-') What I'm seeing is consistent with the "if not" condition. And if this is the second pass through this, rather than the first, then it implies that something in the code following is involved. I've included a cut and paste of exactly what is in the mmsearch.py, and will be doing some creative code-reading to see if this call differs from other calls to the same function. I've located the WebAuthenticate() function in SecurityManager.py and note that it is used in several places, all of which behave as expected. > One question comes to mind: why are we revalidating here? I'll assume without having researched it that the entry to the pipermail archives has its own validation, and in my configuration, you can't get to the archive search except from that post-validated page. Theoretically, I suppose I could work around for the moment by simply commenting out that check, but since something's getting trashed somwhere, think it better to pursue debugging the problem. > >If this were compiled code and not Python, I'd dbx the thing, > >but don't know enough about Python to know how to use the debugging > >resources. If there's some sort of crash and traceback message, I don't > >know where to look for that either. > I'm busy reading the O'Reilly python book on debugging to see where I might get some hooks into this. > > There wouldn't be a traceback in this case. > No, I can see that the code has an exit. > > It seems that htdig per se is working fine. It returns the hits. I > think the problem is in mmsearch.py. It checks to be sure it is > authorized for the private archive, and it is. It does the search and > displays the results and somehow in this latter step the cookie is > removed. > I'll guess that you're right about the htdig installation. However some more testing is showing is not that the cookie is being removed, but that we've got something that's nulling something. Running with the admin password set, I go from the admin area to the main list page, then to the archives, where I can read the pipermail archives repeatedly. Do an htdig search, get the first page of hits back, and try to look at one. Anything entered in either the username or password field clears the block. One character in either field suffices, and it does not have to be alphanumeric. After having gone throught this exercise several times, I can go back to the admin pages without having to revalidate---the cookie is still set. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Sat Jan 20 00:36:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 15:36:03 -0800 Subject: [Mailman-Users] htdig authorization problem In-Reply-To: <200701192220.l0JMK507003026@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: >The esteemed Mark Sapiro has said: >> >> >> But was the archive 'private' or 'public' (admin Archiving options) >> before the problem started? >> >We're going back to Jan. 11 (when this started), and I'm trying to >remember what I changed then. I suspect that I ran check_perms around >then an fixed what it griped about, and the permissions on the private >directory was one such. Let's assume this was the case (I can easily >check, but I don't think setting the directory permission open really >proves anything. Nonetheless, I should do it to see that it does clear >the fault). What I'm trying to determine here is if the authorization in mmsearch.py has 'always' been broken and it was only noticed because the archive was changed from 'public' (not requiring authorization) to 'private', or if it worked before and stopped working. >Yes, it's the second time in. Doing a second search on top of the first >(i.e. changing the htdig search return display and telling it to search >again) gets the error. >> >I have been reading the code (and Python in a Nutshell). > >mmsearch.py has > if mlist.archive_private: > if not mlist.WebAuthenticate((mm_cfg.AuthUser, > mm_cfg.AuthListModerator, > mm_cfg.AuthListAdmin, > mm_cfg.AuthSiteAdmin), > '', ''): > raise _search_exception(listname, 'auth', '-10-') Yes. This code says "you can't be here if you don't have the cookie". The first time through you have the cookie and all is good. If you then go to a message, you don't have the cookie, but that code allows you to reauthorize, so you get it again, but you had to reauthorize. If you come through mmsearch.py a second time, you have no cookie and you get the exception. >What I'm seeing is consistent with the "if not" condition. And if this >is the second pass through this, rather than the first, then it implies >that something in the code following is involved. I've included a cut >and paste of exactly what is in the mmsearch.py, and will be doing some >creative code-reading to see if this call differs from other calls to >the same function. I don't see the cut and paste, but I have the patch code, so I don't need it. >I've located the WebAuthenticate() function in SecurityManager.py and >note that it is used in several places, all of which behave as >expected. >> >One question comes to mind: why are we revalidating here? To prevent you from just going directly to an mmsearch URL and searching without authorization. We don't attempt to reauthorize here, because if you are playing by the rules, you are already authorized. We just check. >I'll assume >without having researched it that the entry to the pipermail archives >has its own validation, and in my configuration, you can't get to the >archive search except from that post-validated page. If you are playing by the rules. >Theoretically, I suppose I could work around for the moment by simply >commenting out that check, but since something's getting trashed >somwhere, think it better to pursue debugging the problem. You don't want to comment out the check because it will allow unauthorized users to search the archive by invoking mmsearch directly. They won't be able to view the messages, but they can get information from the search results. >I'll guess that you're right about the htdig installation. However some >more testing is showing is not that the cookie is being removed, but >that we've got something that's nulling something. > >Running with the admin password set, I go from the admin area to the >main list page, then to the archives, where I can read the pipermail >archives repeatedly. Good, but I'm not sure that's relevant to the problem. >Do an htdig search, get the first page of hits back, and try to look at >one. Anything entered in either the username or password field clears >the block. One character in either field suffices, and it does not have to be >alphanumeric. Puzzling, but what then is the exact URL that the search results page links to for the message. >After having gone throught this exercise several times, I can go back to >the admin pages without having to revalidate---the cookie is still set. If the cookie isn't being removed, then perhaps there is something in your web server specific to the URLs that don't work that is not passing the cookie to the environment. This now seems very likely, and would explain why you can reauthorize with 'invalid' data. Look at and and see if there are any clues there. For example are the non-working and only the non-working URLs http scheme that's being redirected to an https scheme URL in your web server. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kelly.terry.jones at gmail.com Sat Jan 20 02:10:58 2007 From: kelly.terry.jones at gmail.com (Kelly Jones) Date: Fri, 19 Jan 2007 18:10:58 -0700 Subject: [Mailman-Users] Preserving auto-discarded messages for site administrator Message-ID: <26face530701191710h2a0c4599h871596c1404fca3f@mail.gmail.com> I administer a Mailman site with many user-owned mailing lists. Users sometimes setup poor auto-discard rules (+ "do not forward auto-discards", of course) and lose important messages to mailing lists. Can I site configure Mailman to preserve all auto-discarded messages in a location where only I can see them? That way I can tell my users they're stupid, but still give them the messages they lost (the best of both worlds!). Users occasionally also manually discard messages by mistake, but my main concern is auto-discards caused by poor rule setup. -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. From kelly.terry.jones at gmail.com Sat Jan 20 02:32:59 2007 From: kelly.terry.jones at gmail.com (Kelly Jones) Date: Fri, 19 Jan 2007 18:32:59 -0700 Subject: [Mailman-Users] Attempt to block spam using X-Spam-Flag blocks all messages to list Message-ID: <26face530701191732u3ed869dftd26ea30c990467ba@mail.gmail.com> One of my users added this as a spam filter: ^x-spam-flag:.*yes (all lower case since spamfilter regexps are case-insensitive-- hyphens not backslashed by accident), and the list started dropping ALL emails. Why? We're running SpamAssassin on another box (mail gets forwarded to the "mailman box" after SpamAssassin is done with it), and I've confirmed that SpamAssassin is running properly and not setting "X-Spam-Flag: Yes" across the board. Even with the forgot-to-backslash-hyphens error, why would that regexp match the headers of every message? We tested this and it's repeatable: with that regexp as a spam filter, emails are dropped-- when that regexp is removed, emails go through properly. -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. From msapiro at value.net Sat Jan 20 02:36:04 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 17:36:04 -0800 Subject: [Mailman-Users] Preserving auto-discarded messages for siteadministrator In-Reply-To: <26face530701191710h2a0c4599h871596c1404fca3f@mail.gmail.com> Message-ID: Kelly Jones wrote: > >Can I site configure Mailman to preserve all auto-discarded messages >in a location where only I can see them? That way I can tell my users >they're stupid, but still give them the messages they lost (the best >of both worlds!). Only by modifying code - most obviously the do_discard() function in Mailman/Handlers/Moderate.py. You could add code to write the message to a file in the data/ directory (or some other directory) as does 'preserving' messages from the admindb interface, or to add it to the 'bad' queue (or some other) as is done by content filtering's 'preserve' action, or deal with it in yet another way. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 20 03:08:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 18:08:42 -0800 Subject: [Mailman-Users] Attempt to block spam using X-Spam-Flag blocks allmessages to list In-Reply-To: <26face530701191732u3ed869dftd26ea30c990467ba@mail.gmail.com> Message-ID: Kelly Jones wrote: >One of my users added this as a spam filter: > >^x-spam-flag:.*yes > >(all lower case since spamfilter regexps are case-insensitive-- >hyphens not backslashed by accident), It doesn't matter. '-' has no special meaning. >and the list started dropping >ALL emails. Why? > >We're running SpamAssassin on another box (mail gets forwarded to the >"mailman box" after SpamAssassin is done with it), and I've confirmed >that SpamAssassin is running properly and not setting "X-Spam-Flag: >Yes" across the board. > >Even with the forgot-to-backslash-hyphens error, why would that regexp >match the headers of every message? > >We tested this and it's repeatable: with that regexp as a spam filter, >emails are dropped-- when that regexp is removed, emails go through >properly. I don't know. There are cases of people using ^x-spam-status:.*yes and having it match X-Spam-Status: No ... tests=BAYES... but X-Spam-Flag: should be just yes or no. In fact, I think by default it is just X-Spam-Flag: YES or not present at all. I haven't looked at this to see if it is actually a possible cause, but the regexp box in header_filter_rules is a list of regexps one per line. If it contains an empty line or a 'blank' line, that might be a regexp that will match anything or any blank. Don't type a new-line after the regexp. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kelly.terry.jones at gmail.com Sat Jan 20 03:14:54 2007 From: kelly.terry.jones at gmail.com (Kelly Jones) Date: Fri, 19 Jan 2007 19:14:54 -0700 Subject: [Mailman-Users] Attempt to block spam using X-Spam-Flag blocks allmessages to list In-Reply-To: References: <26face530701191732u3ed869dftd26ea30c990467ba@mail.gmail.com> Message-ID: <26face530701191814p422956d2k31d0c90847fea46f@mail.gmail.com> On 1/19/07, Mark Sapiro wrote: > > I haven't looked at this to see if it is actually a possible cause, but > the regexp box in header_filter_rules is a list of regexps one per > line. If it contains an empty line or a 'blank' line, that might be a > regexp that will match anything or any blank. Don't type a new-line > after the regexp. Thanks, Mark. I'm pretty sure there was a newline after the regexp. In fact, I dumped the config before we wiped out the filter: header_filter_rules = [('^x-spam-flag:.*yes\r\n\r\n', 3, False)] That second "\r\n" shouldn't be there, should it? Ouch! -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. From vancleef at bronze.lostwells.net Sat Jan 20 03:45:06 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Fri, 19 Jan 2007 19:45:06 -0700 (MST) Subject: [Mailman-Users] htdig authorization problem Message-ID: <200701200245.l0K2j6m9014189@bronze.lostwells.net> I just succeeded in blowing away my spooled mail, so no longer have what was in this thread (yes, I can look at the mailman-users archives). Thankyew Thunderbird, which linked to my local spool instead of the external one it was supposed to. Getting back to the salient points: If the htdig access ever actually worked in the private directory, I can't confirm reliably. Inputs from my listers aren't sufficiently accurate for me to work with (this would be the third case where some of them thought it was working and it wasn't). The error log indicates failures from the time that the archives and htdig data base were built, and are in sufficient quantity that I believe that this problem has existed since I brought them on line. I have checked the problem with a Firefox 1.5.0.9, a late Mozilla build and Netscape 4.78) ancient, but it's the Solaris 9 default). The Apache is 1.13.34 (Solaris 9 build). There is a later version in the Solaris 9 patch cluster, but I am not going to run patching on this box until I can finish building the Mailman installation on another box and switch over. I doubt that this is an Apache problem. The httpd.conf on this site is "right out of the Mailman install guide." I am not using https, and all of the mailman stuff is in one directory tree without symbolic links. Default URL in mm_cfg.py is for the DNS domain being used, and I ran withlist/fix_url to point to that domain before going on-line. Running with Firefox, I cleared the cache and all cookies, then retested as a user, going from the listinfo page. This URL is: http://www.mercedeslist.com/mailman/listinfo/mercedes The archives page is: http://www.mercedeslist.com/mailman/private/mercedes/ As I have said, that directory tree is all in one place on one filesystem. Running as a user, after having assured that Firefox is "cold" (cache cleared, one cookie present), I can get an article to display through htdig by filling in either the account name or the password. Both are not needed. However, for the user account, the name or password has to be correct. If one of the two fields is correct, bogus information in the other does not prevent access. However, in true user state, one field has to be correct. The cookie held by the browser does not go away, and does not appear to be altered. It is valid for authorization to go to the options field without having to revalidate. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Sat Jan 20 03:56:18 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 18:56:18 -0800 Subject: [Mailman-Users] htdig authorization problem In-Reply-To: <200701200245.l0K2j6m9014189@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: > >Running with Firefox, I cleared the cache and all cookies, then retested >as a user, going from the listinfo page. This URL is: >http://www.mercedeslist.com/mailman/listinfo/mercedes > >The archives page is: >http://www.mercedeslist.com/mailman/private/mercedes/ Right, but when you get the archive index page with the search box, what is the POST URL for the search form, and when you get the results page, what are the URLs for the message links and what is the URL for the next page of results. It is these latter URLs that seem to lose the cookie data. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 20 04:40:40 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 19 Jan 2007 19:40:40 -0800 Subject: [Mailman-Users] Attempt to block spam using X-Spam-Flag blocks allmessages to list In-Reply-To: <26face530701191814p422956d2k31d0c90847fea46f@mail.gmail.com> Message-ID: Kelly Jones wrote: > >Thanks, Mark. I'm pretty sure there was a newline after the regexp. > >In fact, I dumped the config before we wiped out the filter: > >header_filter_rules = [('^x-spam-flag:.*yes\r\n\r\n', 3, False)] > >That second "\r\n" shouldn't be there, should it? Ouch! That's correct. the second \r\n results in a null pattern (the null string between the two \r\n pairs) that matches anything. I've fixed this in Subversion for the next release. Empty and blank patterns will be ignored. If you really want a pattern that matches anything, you'll have to use '^' or '.'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Sat Jan 20 05:07:07 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Fri, 19 Jan 2007 21:07:07 -0700 (MST) Subject: [Mailman-Users] htdig authorization problem In-Reply-To: Message-ID: <200701200407.l0K477Kn018344@bronze.lostwells.net> The esteemed Mark Sapiro has said: > > Hank van Cleef wrote: > > > >Running with Firefox, I cleared the cache and all cookies, then retested > >as a user, going from the listinfo page. This URL is: > >http://www.mercedeslist.com/mailman/listinfo/mercedes > > > >The archives page is: > >http://www.mercedeslist.com/mailman/private/mercedes/ > > > Right, but when you get the archive index page with the search box, > what is the POST URL for the search form, and when you get the results > page, what are the URLs for the message links and what is the URL for > the next page of results. It is these latter URLs that seem to lose > the cookie data. > Taken from the apache access_log. Notes interspered: 192.168.1.99 - - [19/Jan/2007:20:36:03 -0700] "GET / HTTP/1.1" 200 4807 192.168.1.99 - - [19/Jan/2007:20:36:03 -0700] "GET /welcome_files/welcome.gif HTTP/1.1" 200 533 (Entry point) 192.168.1.99 - - [19/Jan/2007:20:40:18 -0700] "GET /mailman/listinfo/mercedes HTTP/1.1" 200 6097 192.168.1.99 - - [19/Jan/2007:20:40:32 -0700] "GET /mailman/private/mercedes/ HTTP/1.1" 200 1493 192.168.1.99 - - [19/Jan/2007:20:40:57 -0700] "POST /mailman/private/mercedes/ HTTP/1.1" 200 136912 (Look at a pipermail archive) 192.168.1.99 - - [19/Jan/2007:20:41:31 -0700] "GET /mailman/private/mercedes/Week-of-Mon-20061106/date.html HTTP/1.1" 200 46660 192.168.1.99 - - [19/Jan/2007:20:41:37 -0700] "GET /mailman/private/mercedes/Week-of-Mon-20061106/164538.html HTTP/1.1" 200 2466 192.168.1.99 - - [19/Jan/2007:20:42:08 -0700] "POST (do a search that produces several pages of hits) /mailman/mmsearch/mercedes H TTP/1.1" 200 5922 192.168.1.99 - - [19/Jan/2007:20:42:08 -0700] "GET /htdig//button5.gif HTTP/1.1" 200 780 192.168.1.99 - - [19/Jan/2007:20:42:08 -0700] "GET /htdig//button4.gif HTTP/1.1" 200 786 192.168.1.99 - - [19/Jan/2007:20:42:08 -0700] "GET /htdig//button6.gif HTTP/1.1" 200 791 (Try to look at one) 192.168.1.12 - - [19/Jan/2007:20:42:45 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20060227/145334.html HTTP/1.1" 200 1580 (revalidate with password only) 192.168.1.99 - - [19/Jan/2007:20:43:37 -0700] "POST /mailman/htdig/mercedes/Week -of-Mon-20060227/145334.html HTTP/1.1" 200 4335 192.168.1.99 - - [19/Jan/2007:20:43:39 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20060227/145335.html HTTP/1.1" 200 4018 (Try to look at another) 192.168.1.12 - - [19/Jan/2007:20:44:12 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20030623/041974.html HTTP/1.1" 200 1580 (revalidate with password only) 192.168.1.99 - - [19/Jan/2007:20:44:19 -0700] "POST /mailman/htdig/mercedes/Week -of-Mon-20030623/041974.html HTTP/1.1" 200 4009 192.168.1.99 - - [19/Jan/2007:20:44:21 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20030623/041897.html HTTP/1.1" 200 2395 (Try to view second page) 192.168.1.12 - - [19/Jan/2007:20:44:34 -0700] "GET /mailman/mmsearch/mercedes?config=mercedes;method=and;format=short;sort=score;words=penoff;page=2 HTTP/1.1" 2 00 1336 192.168.1.12 - - [19/Jan/2007:20:45:17 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20040308/073188.html HTTP/1.1" 200 1580 192.168.1.99 - - [19/Jan/2007:20:45:23 -0700] "POST /mailman/htdig/mercedes/Week -of-Mon-20040308/073188.html HTTP/1.1" 200 3364 192.168.1.99 - - [19/Jan/2007:20:45:25 -0700] "GET /mailman/htdig/mercedes/Week- of-Mon-20040308/073191.html HTTP/1.1" 200 2593 (Note: none of the above displayed. Instead, I got the auth error page for htdig) (Now, go over to the options page for the account without having to revalidate) 192.168.1.99 - - [19/Jan/2007:20:45:53 -0700] "GET /icons/mm-icon.png HTTP/1.1" 200 281 192.168.1.99 - - [19/Jan/2007:20:45:54 -0700] "POST /mailman/options/mercedes HT TP/1.1" 200 14726 192.168.1.99 - - [19/Jan/2007:20:46:14 -0700] "GET /favicon.ico HTTP/1.1" 404 28 3 The error log has entries for favicon.ico, which I don't have. No other errors. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From dragon at crimson-dragon.com Sat Jan 20 05:31:51 2007 From: dragon at crimson-dragon.com (Dragon) Date: Fri, 19 Jan 2007 20:31:51 -0800 Subject: [Mailman-Users] Attempt to block spam using X-Spam-Flag blocks allmessages to list In-Reply-To: References: <26face530701191732u3ed869dftd26ea30c990467ba@mail.gmail.com> Message-ID: <7.0.1.0.2.20070119202244.0780e298@crimson-dragon.com> Mark Sapiro sent the message below at 06:08 PM 1/19/2007: >Kelly Jones wrote: > > >One of my users added this as a spam filter: > > > >^x-spam-flag:.*yes > > > >(all lower case since spamfilter regexps are case-insensitive-- > >hyphens not backslashed by accident), > > >It doesn't matter. '-' has no special meaning. In this case, that is correct. The hyphen DOES have special meaning in a character class such as [0-9] which will match all numerals. > >and the list started dropping > >ALL emails. Why? > > > >We're running SpamAssassin on another box (mail gets forwarded to the > >"mailman box" after SpamAssassin is done with it), and I've confirmed > >that SpamAssassin is running properly and not setting "X-Spam-Flag: > >Yes" across the board. > > > >Even with the forgot-to-backslash-hyphens error, why would that regexp > >match the headers of every message? > > > >We tested this and it's repeatable: with that regexp as a spam filter, > >emails are dropped-- when that regexp is removed, emails go through > >properly. > > >I don't know. There are cases of people using > >^x-spam-status:.*yes > >and having it match > >X-Spam-Status: No ... tests=BAYES... Which is to be expected because .* means "match anything 0 or more times". A safer construct there would be to use something like this which will match only whitespace between the : and yes. ^x-spam-status:\s*yes >but X-Spam-Flag: should be just yes or no. In fact, I think by default >it is just > >X-Spam-Flag: YES > >or not present at all. I believe this is correct. I also believe the default is no header if not detected as spam. >I haven't looked at this to see if it is actually a possible cause, but >the regexp box in header_filter_rules is a list of regexps one per >line. If it contains an empty line or a 'blank' line, that might be a >regexp that will match anything or any blank. Don't type a new-line >after the regexp. Well, I think it would indeed result in an empty pattern which would match everything. Sounds like you may have hit the cause. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From rob at poeweb.com Sat Jan 20 10:22:49 2007 From: rob at poeweb.com (Rob Poe) Date: Sat, 20 Jan 2007 03:22:49 -0600 Subject: [Mailman-Users] Interesting request... Message-ID: <45B1DF69.40403@poeweb.com> AOL has implemented a abuse reporting system. IF someone who legitimately subscribes to the list (for whatever reason) marks the list traffic as SPAM, AOL will email a report to the server owner (if they sign up) with an abuse report. The BAD part about that is, that AOL will not tell you WHO it is. The best suggestion is to embed a piece of identifiable data into each message so you KNOW who the user is who received the email. Not knowing exactly how MailMan handles sending of email (maybe this makes a difference on performance, too) would it be hard to put this piece of data into each message mailed? Or perhaps as an on/off option? Perhaps (and this might take more work than is wanted) a userid field in the membership db (this message sent to listname-xx) where xx is the user's id. Or perhaps just an MD5 hash of the user email address and some sort of util to dump the addresses / hash values into a text file so you can look up who it is who's abusing that kind of thing, so that you can handle their unsubscribe or whatever... Just some thoughts.. From brad at shub-internet.org Sat Jan 20 11:06:23 2007 From: brad at shub-internet.org (Brad Knowles) Date: Sat, 20 Jan 2007 04:06:23 -0600 Subject: [Mailman-Users] Interesting request... In-Reply-To: <45B1DF69.40403@poeweb.com> References: <45B1DF69.40403@poeweb.com> Message-ID: At 3:22 AM -0600 1/20/07, Rob Poe wrote: > AOL has implemented a abuse reporting system. IF someone who > legitimately subscribes to the list (for whatever reason) marks the list > traffic as SPAM, AOL will email a report to the server owner (if they > sign up) with an abuse report. Yup. This is a well-known issue. > Not knowing exactly how MailMan handles sending of email (maybe this > makes a difference on performance, too) would it be hard to put this > piece of data into each message mailed? Or perhaps as an on/off option? I suggest you read the FAQ before you do anything else on this subject. And note that I wrote most of what is in the FAQ on this subject, and that I am the former Sr. Internet Mail Administrator for AOL. Their abuse reporting system was implemented after I left, but I know all too well just how some of their processes work internally. > Perhaps (and this might take more work than is wanted) a userid field in > the membership db (this message sent to listname-xx) where xx is the > user's id. Or perhaps just an MD5 hash of the user email address and > some sort of util to dump the addresses / hash values into a text file > so you can look up who it is who's abusing that kind of thing, so that > you can handle their unsubscribe or whatever... Check out the FAQ entries that discuss "personalization". Once you've done that, if there is anything more that you would like to discuss, this would be a good place to do so. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From mihamina.rakotomandimby at etu.univ-orleans.fr Sat Jan 20 12:49:43 2007 From: mihamina.rakotomandimby at etu.univ-orleans.fr (Mihamina Rakotomandimby (R12y)) Date: Sat, 20 Jan 2007 12:49:43 +0100 Subject: [Mailman-Users] subscribe people without notify Message-ID: <1169293783.4536.6.camel@asus.rktmb.org> Hi all, I manage a website that has a newsletter. The newsletter is send by the website embeded PHP script. I would like to switch to a mailman based newsletter. An "announce only" Mailing list, then. I will have to batch subscribe thousands of email adresses, but I dont want them to be affraid by the subscription notification of Mailman. I know they will be, even we announced the switch. They was event affraid of the annouce of the switch, think then... Well. Any suggestion? Thanks in advance. From benjamin at py-soft.co.uk Sat Jan 20 14:49:10 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Sat, 20 Jan 2007 13:49:10 +0000 Subject: [Mailman-Users] subscribe people without notify In-Reply-To: <1169293783.4536.6.camel@asus.rktmb.org> References: <1169293783.4536.6.camel@asus.rktmb.org> Message-ID: <45B21DD6.8050307@py-soft.co.uk> Mihamina Rakotomandimby (R12y) wrote: > I will have to batch subscribe thousands of email adresses, but I dont > want them to be affraid by the subscription notification of Mailman. Use the web admin interface for the list. Look under Membership management -> Mass subscription. Set "subscribe or invite" to subscribe and "send welcome message to new subscribees" to no. Job done! :) Ben From cmowen at att.net Sat Jan 20 16:23:35 2007 From: cmowen at att.net (Charles M. Owen) Date: Sat, 20 Jan 2007 10:23:35 -0500 Subject: [Mailman-Users] Mailman users list Message-ID: I gather from what I read, that if I don't own the server my list is hosted, there is no way to get a full membership list with emails and names. I have found some reference to changing the general information page, but again I don't own the installed instance of Mailman. Charles From peter at coolen.net Sat Jan 20 16:48:23 2007 From: peter at coolen.net (Peter Coolen) Date: Sat, 20 Jan 2007 16:48:23 +0100 Subject: [Mailman-Users] problems with gid when installing Message-ID: <003601c73caa$6b01dea0$2200a8c0@peter> Hi All, I tried to install mailman on my slackware system with postfix (mysql virtual domains) and apache.. I followed the whole mnual ,except the thing about the virtual domains.. I will do this later on. When i want to go to the page www.domain.tld/mailman/create, I get the error below: Mailman CGI error!!! %s --with-cgi-gidwebCGI--with-mail-gidmail-SThe Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:Group mismatch error. Mailman expected the %s wrapper script to be executed as group "%s", but the system's %s server executed the %s script as group "%s". Try tweaking the %s server to run the script as group "%s", or re-run configure, providing the command line option `%s=%s'.Failure to find group name for GID %d. Mailman expected the %s wrapper to be executed as group "%s", but the system's %s server executed the wrapper as GID %d for which the name could not be found. Try adding GID %d to your system as "%s", or tweak your %s server to run the wrapper as group "%s".nobodycreateMailman cgi-wrapper (create)driver????????$ ?  I already reinstalled with the follwing options: ./configure --with-mail-gid = postfix --with-cgi-gid = nobody make make install Postfix has the owner and group postfix and Apache nobody.. Could someone please help me and advise? From msapiro at value.net Sat Jan 20 17:43:15 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 08:43:15 -0800 Subject: [Mailman-Users] Mailman users list In-Reply-To: Message-ID: Charles M. Owen wrote: >I gather from what I read, that if I don't own the server my list is hosted, >there is no way to get a full membership list with emails and names. > >I have found some reference to changing the general information page, but >again I don't own the installed instance of Mailman. See . Particularly the links to scripts that scrape the web admin membership list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 20 18:02:06 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 09:02:06 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <003601c73caa$6b01dea0$2200a8c0@peter> References: <003601c73caa$6b01dea0$2200a8c0@peter> Message-ID: <45B24B0E.4010302@value.net> Peter Coolen wrote: > > When i want to go to the page www.domain.tld/mailman/create, I get the error > below: > > Mailman CGI error!!! > %s > --with-cgi-gidwebCGI--with-mail-gidmail-SThe Mailman CGI wrapper encountered > a fatal error. This entry is being stored in your syslog:Group mismatch > error. Mailman expected the %s wrapper script to be executed as group "%s", > but the system's %s server executed the %s script as group "%s". Try > tweaking the %s server to run the script as group "%s", or re-run configure, > providing the command line option `%s=%s'.Failure to find group name for GID > %d. Mailman expected the %s wrapper to be executed as group "%s", but the > system's %s server executed the wrapper as GID %d for which the name could > not be found. Try adding GID %d to your system as "%s", or tweak your %s > server to run the wrapper as group "%s".nobodycreateMailman cgi-wrapper > (create)driver????????$ ?? There is something wrong with your web server configuration. Instead of executing Mailman's cgi-bin/create wrapper and serving it's output, the web server is serving the wrapper file as text. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 20 18:06:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 09:06:14 -0800 Subject: [Mailman-Users] Mailman users list In-Reply-To: Message-ID: Charles M. Owen wrote: > >I have found some reference to changing the general information page, but >again I don't own the installed instance of Mailman. The list's General information page (listinfo) can be edited via the web admin interface "Edit the public HTML pages and text files" link. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at python.org Sat Jan 20 19:43:16 2007 From: barry at python.org (Barry Warsaw) Date: Sat, 20 Jan 2007 13:43:16 -0500 Subject: [Mailman-Users] Mailman users list In-Reply-To: References: Message-ID: <5F63D79F-8576-470F-896E-49AFA57E9410@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 20, 2007, at 10:23 AM, Charles M. Owen wrote: > I gather from what I read, that if I don't own the server my list > is hosted, > there is no way to get a full membership list with emails and names. If you know the list password you can send the email command 'who' to the -request address. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRbJiyXEjvBPtnXfVAQJF9gP/X12I1zI1R0npp+x+haEkZcePKOI45VXu 3Spq7//XHglJtmN0qdlLLXFq02TzBCUbciw9vafI+xLdWc3c1dGD9u9CxrR5080/ x+WsQfvToWN9ZxHMTD9+yqBq5XEm9a+gZ886Fm3eRoEqpeQILoQelRsnXd59xqo8 6Q9mhiCISUk= =BgP3 -----END PGP SIGNATURE----- From msapiro at value.net Sat Jan 20 19:54:21 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 10:54:21 -0800 Subject: [Mailman-Users] Mailman users list In-Reply-To: <5F63D79F-8576-470F-896E-49AFA57E9410@python.org> Message-ID: Barry Warsaw wrote: > >If you know the list password you can send the email command 'who' to >the -request address. The results don't include hidden members. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From barry at python.org Sat Jan 20 20:30:30 2007 From: barry at python.org (Barry Warsaw) Date: Sat, 20 Jan 2007 14:30:30 -0500 Subject: [Mailman-Users] Mailman users list In-Reply-To: References: Message-ID: <052726AE-2411-4A27-88D4-6B38F86FF2A8@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jan 20, 2007, at 1:54 PM, Mark Sapiro wrote: > Barry Warsaw wrote: >> >> If you know the list password you can send the email command 'who' to >> the -request address. > > The results don't include hidden members. Right. Yep, I think there should be a way for list owners to get this information via the web or email. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRbJt5HEjvBPtnXfVAQKoPAP+KWKeICwUywAAVxzO87A9XMn5YVNiKZMs AY/pesdcJ8d7orx3IRbFuk6vqGwe2HqondAO1YICs3zY5jV8+KPQa1emCsnFNWJt zxQPocLzSp7eNQp0TEO33Ytv33Hcqteyb3QEaZQMeguFXfvB/lUY117IWQk8Wpl+ Xbi688qfVlg= =MS+q -----END PGP SIGNATURE----- From msapiro at value.net Sat Jan 20 20:41:28 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 11:41:28 -0800 Subject: [Mailman-Users] Mailman users list In-Reply-To: <052726AE-2411-4A27-88D4-6B38F86FF2A8@python.org> Message-ID: Barry Warsaw > >On Jan 20, 2007, at 1:54 PM, Mark Sapiro wrote: > >> Barry Warsaw wrote: >>> >>> If you know the list password you can send the email command 'who' to >>> the -request address. >> >> The results don't include hidden members. > >Right. Yep, I think there should be a way for list owners to get >this information via the web or email. There is a patch at for the web roster. I'll look at picking that up and also modifying cmd_who to show the full list if validation is with the admin or moderator password. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pgf at foxharp.boston.ma.us Sat Jan 20 21:14:36 2007 From: pgf at foxharp.boston.ma.us (Paul Fox) Date: Sat, 20 Jan 2007 15:14:36 -0500 Subject: [Mailman-Users] doc patch for postfix virtual domain config Message-ID: <11223.1169324076@foxharp.boston.ma.us> hi -- i'm new at both mailman and postfix, but i thought i'd try and reduce someone else's pain when trying to do what i've been trying to do. i spent a bunch of time last night very confused because i couldn't do a configuration of a mailman list in a postfix virtual domain. from what i read in the docs, it seemed like it should "Just Work". and it would have, except i made one crucial mistake. it turns out that the information i needed to do it right was in the output of "bin/newlist -h", but not in any other doc that i found. (it may be elsewhere, i just didn't find it elsewhere, even after a lot of searching.) the missing piece was that when setting up the list, _that's_ when you have to declare it as being in a virtual domain. not later. and while there's an oblique reference in section 6.1.2 to the "host_name attribute" of a list, this didn't jump out at me, and it might not have helped -- it's the only reference in the docs. here's a doc patch that would have helped me a lot. (i don't have tex or texinfo installed, so i wasn't able to actually try this patch.) it might also be worth adding mention of the postfix-to-mailman-2.1.py script that's fairly widely found when googling, if only to explain why one doesn't need it. i understand that while this works (and i assume is similar to fil at rezo.net's technique, referenced in the docs), it's sub-optimal especially in the face of spam dictionary attacks. (at least, i read that somewhere on the internet last night -- so it must be true!) anyway, i didn't add anything about this, because i don't really feel qualified, but again, it would have helped. thanks, paul --- mailman-install.tex.orig Sat Jan 20 14:46:39 2007 +++ mailman-install.tex Sat Jan 20 15:03:19 2007 @@ -555,6 +555,23 @@ against the \var{host_name} attribute of mailing lists objects, and must be an exact match. +Note that virtual alias mappings will only be created (obviously) by +\program{bin/genaliases} for lists which are addressed in a virtual domain. +Thus, if you ran +\begin{verbatim} + % bin/newlist mylist +\end{verbatim} +then you will not get virtual alias mappings in +\file{/usr/local/mailman/data/virtual-mailman}, but if you ran +\begin{verbatim} + % bin/newlist mylist at dom2.ain +\end{verbatim} +(which will set the \var{host_name} attribute for the list) then +you will. (You will, however, get direct alias entries, i.e. in +\file{/usr/local/mailman/data/aliases}, for both virtual and non-virtual +lists -- both sets of entries are necessary for lists in virtual +domains to work.) + Here's an example. Say that Postfix is configured to handle the virtual domains \code{dom1.ain}, \code{dom2.ain}, and \code{dom3.ain}, and further that in your \file{main.cf} file you've got the following settings: =--------------------- paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 21.0 degrees) From peter at coolen.net Sun Jan 21 00:32:17 2007 From: peter at coolen.net (Peter Coolen) Date: Sun, 21 Jan 2007 00:32:17 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <45B24B0E.4010302@value.net> References: <003601c73caa$6b01dea0$2200a8c0@peter> <45B24B0E.4010302@value.net> Message-ID: <006301c73ceb$392cb1c0$2200a8c0@peter> > > There is something wrong with your web server configuration. > Instead of executing Mailman's cgi-bin/create wrapper and > serving it's output, the web server is serving the wrapper > file as text. > > -- Do you have any idea how to fix this problem with my web server configuration? It is Apache 1.3.36 Below are some setting from apache: LoadModule cgi_module libexec/apache/mod_cgi.so AddModule mod_cgi.c User nobody Group nobody Alias /mailman/ "/usr/local/mailman/cgi-bin/" Options Indexes FollowSymlinks MultiViews ExecCGI AllowOverride None Order allow,deny Allow from all ScriptAlias /mailman/ "usr/local/mailman/cgi-bin/" AddHandler cgi-script .cgi .py Thanks for all help From msapiro at value.net Sun Jan 21 02:06:09 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 17:06:09 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <006301c73ceb$392cb1c0$2200a8c0@peter> Message-ID: Peter Coolen wrote: > >Do you have any idea how to fix this problem with my web server >configuration? It is Apache 1.3.36 > Alias /mailman/ "/usr/local/mailman/cgi-bin/" The above line overrides the ScriptAlias below. Remove it. > > Options Indexes FollowSymlinks MultiViews ExecCGI > AllowOverride None > Order allow,deny > Allow from all > > >ScriptAlias /mailman/ "usr/local/mailman/cgi-bin/" > > AddHandler cgi-script .cgi .py -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jan 21 02:32:07 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 20 Jan 2007 17:32:07 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: Message-ID: Mark Sapiro wrote: >Peter Coolen wrote: >> >>Do you have any idea how to fix this problem with my web server >>configuration? It is Apache 1.3.36 > >> Alias /mailman/ "/usr/local/mailman/cgi-bin/" > > >The above line overrides the ScriptAlias below. Remove it. > > >> >> Options Indexes FollowSymlinks MultiViews ExecCGI >> AllowOverride None >> Order allow,deny >> Allow from all >> >> >>ScriptAlias /mailman/ "usr/local/mailman/cgi-bin/" >> >> AddHandler cgi-script .cgi .py Other issues in your apache config. The Directory section should be "/usr/local/mailman/", not "/usr/local/mailman/cgi-bin/". This is primarily for public archives. Also, if you are going to have public archives, you want Alias /pipermail/ /usr/local/mailman/archives/public/ Finally, the AddHandler is superfluous for Mailman. The only GGIs executed by Apache for Mailman are the compiled wrappers in usr/local/mailman/cgi-bin/ which normally have no extension (unless you specified --with-cgi-ext to configure). Python scripts are executed indirectly by the wrapper, not directly by Apache. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at coolen.net Sun Jan 21 13:07:21 2007 From: peter at coolen.net (Peter Coolen) Date: Sun, 21 Jan 2007 13:07:21 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: References: Message-ID: <003101c73d54$b4740cc0$2200a8c0@peter> > > > Other issues in your apache config. > > The Directory section should be "/usr/local/mailman/", not > "/usr/local/mailman/cgi-bin/". This is primarily for public archives. > Also, if you are going to have public archives, you want > > Alias /pipermail/ /usr/local/mailman/archives/public/ > > Finally, the AddHandler is superfluous for Mailman. The only > GGIs executed by Apache for Mailman are the compiled wrappers > in usr/local/mailman/cgi-bin/ which normally have no > extension (unless you specified --with-cgi-ext to configure). > Python scripts are executed indirectly by the wrapper, not > directly by Apache. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > Hi Mark, Thanks for all your help.. I changed setting in my webserver but now I get a 404 NOT FOUND error... I looked in the manual and there it says $prefix/cgi-bin/ I tried both but both give a 404 not found.. Any other ideas? From leonk at construct.haifa.ac.il Sun Jan 21 16:28:37 2007 From: leonk at construct.haifa.ac.il (Leon Kolchinsky) Date: Sun, 21 Jan 2007 17:28:37 +0200 Subject: [Mailman-Users] Adding disclaimer to message footer via command line Message-ID: <20070121153011.7D4F01C985@mail.edu.haifa.ac.il> Hello All, Our management decided to add disclaimer to every footer in Digest and Non-digest options. I know that this is a bad netiquette but I have no choice. I have a lot of mailinglists running on my server and I though that may be there is a way to do this addition with some script via command line and add this to all lists, and save from myself doing it via web-interface enormous times. Is there a way of doing that? Best Regards, Leon Kolchinsky From msapiro at value.net Sun Jan 21 17:05:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 08:05:39 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <003101c73d54$b4740cc0$2200a8c0@peter> Message-ID: Peter Coolen wrote: > >Thanks for all your help.. I changed setting in my webserver but now I get a >404 NOT FOUND error... > >I looked in the manual and there it says $prefix/cgi-bin/ > >I tried both but both give a 404 not found.. You don't put '$prefix' literally. $ prefix stands for the path you provided to configure with the --prefix= option (default /usr/local/mailman). What is in your Apache configuration now? What is in Apache's error_log associated with the 404? What does 'ls -l /usr/local/mailman/cgi-bin' show? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at coolen.net Sun Jan 21 17:27:02 2007 From: peter at coolen.net (Peter Coolen) Date: Sun, 21 Jan 2007 17:27:02 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: References: <003101c73d54$b4740cc0$2200a8c0@peter> Message-ID: <004501c73d78$fb2b3070$2200a8c0@peter> > > You don't put '$prefix' literally. $ prefix stands for the > path you provided to configure with the --prefix= option > (default /usr/local/mailman). > > What is in your Apache configuration now? Some apache config lines for mailman Alias /pipermail/ "/usr/local/mailman/archives/public/" Options Indexes FollowSymlinks MultiViews AllowOverride None Order allow,deny Allow from all ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" ScriptAlias /mailman/ "usr/local/mailman/cgi-bin/" AllowOverride None Options None Order allow,deny Allow from all Options Indexes FollowSymlinks MultiViews ExecCGI AllowOverride None Order allow,deny Allow from all > > What is in Apache's error_log associated with the 404? > [Sun Jan 21 17:24:24 2007] [error] [client 192.168.0.18] script not found or unable to stat: usr/local/mailman/create [Sun Jan 21 17:24:37 2007] [error] [client 192.168.0.34] script not found or unable to stat: usr/local/mailman/ > What does 'ls -l /usr/local/mailman/cgi-bin' show? > admin at localhost:/var/log/apache$ ls -l /usr/local/mailman/cgi-bin/ total 220 -rwxr-sr-x 1 root mailman 17476 Jan 20 16:19 admin* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 admindb* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 confirm* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 create* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 edithtml* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 listinfo* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 options* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 private* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 rmlist* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 roster* -rwxr-sr-x 1 root mailman 17484 Jan 20 16:19 subscribe* > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From msapiro at value.net Sun Jan 21 17:34:46 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 08:34:46 -0800 Subject: [Mailman-Users] Adding disclaimer to message footer via command line In-Reply-To: <20070121153011.7D4F01C985@mail.edu.haifa.ac.il> Message-ID: Leon Kolchinsky wrote: > >Our management decided to add disclaimer to every footer in Digest and >Non-digest options. >I know that this is a bad netiquette but I have no choice. > >I have a lot of mailinglists running on my server and I though that may be >there is a way to do this addition with some script via command line and add >this to all lists, and save from myself doing it via web-interface enormous >times. You can do this fairly easily in two ways. One is with a bin/withlist script and the other is by running bin/config_list via a shell script. Several examples of withlist scripts (not this exact one) can be found at or . The shell script method is described at . With the shell method, the input to config_list (configfile in the FAQ) would contain msg_footer="""First line of footer Second line ... Last line """ digest_footer="""First line of footer Second line ... Last line """ You also want the set DEFAULT_MSG_FOOTER in mm_cfg.py (if you haven't changed DEFAULT_DIGEST_FOOTER, you don't need to now as it defaults to DEFAULT_MSG_FOOTER) so the footer is set for new lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jan 21 17:45:32 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 08:45:32 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <004501c73d78$fb2b3070$2200a8c0@peter> Message-ID: Peter Coolen wrote: > >Some apache config lines for mailman > > ScriptAlias /cgi-bin/ "/var/www/cgi-bin/" You don't need this for Mailman. You may want it for other reasons. > ScriptAlias /mailman/ "usr/local/mailman/cgi-bin/" Missing a slash. should be ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" > > > Options Indexes FollowSymlinks MultiViews ExecCGI The only option you need on this directory is ExecCGI > AllowOverride None > Order allow,deny > Allow from all > > > >> >> What is in Apache's error_log associated with the 404? >> > >[Sun Jan 21 17:24:24 2007] [error] [client 192.168.0.18] script not found or >unable to stat: usr/local/mailman/create >[Sun Jan 21 17:24:37 2007] [error] [client 192.168.0.34] script not found or >unable to stat: usr/local/mailman/ Note missing slash. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jan 21 17:55:31 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 08:55:31 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <004501c73d78$fb2b3070$2200a8c0@peter> Message-ID: Peter Coolen wrote: > >[Sun Jan 21 17:24:24 2007] [error] [client 192.168.0.18] script not found or >unable to stat: usr/local/mailman/create This error came from the missing slash in ScriptAlias when you tried to visit something like . >[Sun Jan 21 17:24:37 2007] [error] [client 192.168.0.34] script not found or >unable to stat: usr/local/mailman/ And this error came from something like . If you want this latter URL to work (usually people send it to the listinfo page), you need something like RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo in your Apache config. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From manuel at arteryplanet.net Sun Jan 21 18:34:02 2007 From: manuel at arteryplanet.net (ArteryPlanet.Net :: Manuel Kissoyan) Date: Sun, 21 Jan 2007 14:34:02 -0300 Subject: [Mailman-Users] domain in attached file url Message-ID: <01af01c73d82$592617e0$6401a8c0@sarna> I have the scrub list attatchment option turned on for this mailing lists so when an attatchment is sent to the list rather than emailing it to the subscribers, it creates a link at the bottom of the message that you are supposed to be able to click on and it downloads it via web browser. It used to work fine but for some reason lately it doesnt format the link correctly. In other words, its not adding the domain name to the front of the link. A person has to copy and paste the link then manually add the domain to the front. Here is an example: -------------- next part -------------- A non-text attachment was scrubbed... Name: 704.pdf Type: application/pdf Size: 40815 bytes Desc: not available Url : /pipermail/mercedes_okiebenz.com/attachments/20070121/a1db2ede/attachment.pdf Any idea what could be the problem? Thank you in advance! From msapiro at value.net Sun Jan 21 19:22:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 10:22:47 -0800 Subject: [Mailman-Users] domain in attached file url In-Reply-To: <01af01c73d82$592617e0$6401a8c0@sarna> Message-ID: ArteryPlanet.Net :: Manuel Kissoyan wrote: >Here is an example: > >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: 704.pdf >Type: application/pdf >Size: 40815 bytes >Desc: not available >Url : >/pipermail/mercedes_okiebenz.com/attachments/20070121/a1db2ede/attachment.pdf > > >Any idea what could be the problem? This has all the earmarks of a cPanel Mailman - specifically 2.1.9-cp1? If so, this is a cPanel bug (fixed I think in 2.1.9-cp2). In any case, the problem is caused by an incorrect setting for PUBLIC_ARCHIVE_URL in mm_cfg.py. I.e., '/pipermail/%(listname)s' instead of 'http://%(hostname)s/pipermail/%(listname)s'. Also, see -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Sun Jan 21 20:15:07 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Sun, 21 Jan 2007 12:15:07 -0700 (MST) Subject: [Mailman-Users] htdig authorization problem (fixed) In-Reply-To: Message-ID: <200701211915.l0LJF7ed019407@bronze.lostwells.net> I'll sum up the problem I was encountering, and post the fix. I note of thanks to Mark, who worked with me offlist to get a diagnosis. As with many things, what was wrong was blatantly obvious---after the fact. Symptoms: On a new Mailman installation, with the htdig patch and htdig program installed, validation failed when attempting to look at search returns or to run a second modified search. Entering a value user name or a valid user password in the validation form would allow viewing a returned page, but had to be repeated for every page viewed. Diagnosis: The URL in the htdig data base was different from that in Mailman. Solution: 1. Run blow_away_htdig against the affected list. 2. Post a single posting to the affected list. 3. Manually run the nightly_htdig utility that is in the mailman crontab. What is significant is the answer to "how did we get into this jam in the first place?" This installation was set up on a new host site, to host a mail list that had run for years on another host site. Included in moving the list host was a domain name registration used as a virtual domain name. For test, the new list was set up for test at the new host site configured "mylist at newdomain,net." The old host continued to run in parallel as "mylist at aliasdomain.com" until it was clear that the new host was ready to take over for the old one. A part of the new site test configuration included setting up list archives with htdig. The transfer was accomplished by moving the domain registration DNS IP's from the old site to the new. Access to the new site's LAN is via a router NAT table. Except for setting up the MTA (sendmail) to handle mail for for alisasdomain.com, the new host treated the new name as a synonym for the old. Several days later, the site administrator ran bin/withlist -l -r fix_url listname This was considered a cosmetic change, and a quick check showed all of the web pages associated with the list as "working properly" with the alias name in place of the site domain name. Not so. This is what broke the htdig access. Since htdig is an add-on to Mailman, the existing data bases have to be recreated through the steps outlined above. Once again, my thanks to Mark Sapiro for following this through with me. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From kwz-mm at commpartners.com Sun Jan 21 21:01:04 2007 From: kwz-mm at commpartners.com (Karl Zander) Date: Sun, 21 Jan 2007 15:01:04 -0500 Subject: [Mailman-Users] Bypass List Moderation Message-ID: It is possible to get around list moderation? We have a closed, moderated list. There is only one list administrator. He claims he did not approve a message that was sent on to the list. Is it possible to craft a message that already contains the X-Mailman-Approved-At: header and get by moderation? Are there logs of moderations actions? --Karl From msapiro at value.net Sun Jan 21 21:36:25 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 12:36:25 -0800 Subject: [Mailman-Users] Bypass List Moderation In-Reply-To: Message-ID: Karl Zander wrote: > >It is possible to get around list moderation? We have a >closed, moderated list. There is only one list >administrator. He claims he did not approve a message that >was sent on to the list. > >Is it possible to craft a message that already contains >the > >X-Mailman-Approved-At: header and get by moderation? That header is informational only. Including it in a post won't affect moderation or other holds. You can bypass moderation by including a Approved: password header where password is either the admin or moderator password. You probably checked, but is the sender of the post a moderated member? >Are there logs of moderations actions? Holds and approvals of held messages are logged in Mailman's vette log. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kwz-mm at commpartners.com Sun Jan 21 22:02:02 2007 From: kwz-mm at commpartners.com (Karl Zander) Date: Sun, 21 Jan 2007 16:02:02 -0500 Subject: [Mailman-Users] Bypass List Moderation In-Reply-To: References: Message-ID: Thanks Mark. The vette logs show several other messages approved at the same time as this suspect message. I am guessing it was just an error on the list admins part. We have a mischievous person forging From: headers and posting to the list as if they were that subscriber. Any way to fight this besides moderating everything? I have noted FAQ 3.46 so I am guessing that full moderation is our best way for now. mmreencrypt does not look too current. --Karl On Sun, 21 Jan 2007 12:36:25 -0800 Mark Sapiro wrote: > Karl Zander wrote: >> >>It is possible to get around list moderation? We have a >>closed, moderated list. There is only one list >>administrator. He claims he did not approve a message >>that >>was sent on to the list. >> >>Is it possible to craft a message that already contains >>the >> >>X-Mailman-Approved-At: header and get by moderation? > > > That header is informational only. Including it in a >post won't affect > moderation or other holds. You can bypass moderation by >including a > > Approved: password > > header where password is either the admin or moderator >password. > > You probably checked, but is the sender of the post a >moderated member? > > >>Are there logs of moderations actions? > > > Holds and approvals of held messages are logged in >Mailman's vette log. > > -- > Mark Sapiro The highway is for >gamblers, > San Francisco Bay Area, California better use your >sense - B. Dylan > From msapiro at value.net Sun Jan 21 22:37:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 13:37:26 -0800 Subject: [Mailman-Users] Bypass List Moderation In-Reply-To: Message-ID: Karl Zander wrote: > >We have a mischievous person forging From: headers and >posting to the list as if they were that subscriber. Any >way to fight this besides moderating everything? I have >noted FAQ 3.46 so I am guessing that full moderation is >our best way for now. mmreencrypt does not look too >current. mmreencrypt is, as you notice, very out of date. At this point, it is probably only useful as a concept, not as a working product. This and other ideas mentioned in FAQ 3.46 all suffer from the drawback that they require posts to be at least cryptographically signed. This may be an insurmountable hurdle for some list members. Thus, you're pretty much stuck with full moderation unless perhaps you can identify something unique (an ip address maybe) in the headers of the mischievously forged posts, and set header_filter_rules to discard them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at coolen.net Sun Jan 21 23:13:13 2007 From: peter at coolen.net (Peter Coolen) Date: Sun, 21 Jan 2007 23:13:13 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: References: <004501c73d78$fb2b3070$2200a8c0@peter> Message-ID: <006d01c73da9$582add40$2200a8c0@peter> > -----Oorspronkelijk bericht----- > Van: Mark Sapiro [mailto:msapiro at value.net] > Verzonden: zondag 21 januari 2007 17:56 > Aan: Peter Coolen; mailman-users at python.org > Onderwerp: Re: [Mailman-Users] problems with gid when installing > > Peter Coolen wrote: > > > >[Sun Jan 21 17:24:24 2007] [error] [client 192.168.0.18] script not > >found or unable to stat: usr/local/mailman/create > > > This error came from the missing slash in ScriptAlias when > you tried to visit something like > . > I also tried mailman/create/ but create is not a directory.. So you must not use the slash... It still can't find the files.. > > >[Sun Jan 21 17:24:37 2007] [error] [client 192.168.0.34] script not > >found or unable to stat: usr/local/mailman/ > > > And this error came from something like . > > If you want this latter URL to work (usually people send it > to the listinfo page), you need something like > > RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo > > in your Apache config. > I tried example.com/mailman/ just for a visit or a index page but now I receive a 403 forbidden... The error is still [Sun Jan 21 23:08:45 2007] [error] [client 192.168.0.34] script not found or unable to stat: /usr/local/mailman/create Do you have any other ideas for helping me? I changed the missing slash but that was not the fault.. Peter From peter at coolen.net Sun Jan 21 23:17:37 2007 From: peter at coolen.net (Peter Coolen) Date: Sun, 21 Jan 2007 23:17:37 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <006d01c73da9$582add40$2200a8c0@peter> References: <004501c73d78$fb2b3070$2200a8c0@peter> <006d01c73da9$582add40$2200a8c0@peter> Message-ID: <006f01c73da9$f531fdd0$2200a8c0@peter> My access log says this: 192.168.0.34 - - [21/Jan/2007:23:13:50 +0100] "GET /mailman/create HTTP/1.1" 404 295 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.9) Gecko/20061206 Firefox/1.5.0.9" And error log this: [Sun Jan 21 23:13:50 2007] [error] [client 192.168.0.34] script not found or unable to stat: /usr/local/mailman/create Please help > -----Oorspronkelijk bericht----- > Van: mailman-users-bounces+peter=coolen.net at python.org > [mailto:mailman-users-bounces+peter=coolen.net at python.org] > Namens Peter Coolen > Verzonden: zondag 21 januari 2007 23:13 > Aan: mailman-users at python.org > Onderwerp: Re: [Mailman-Users] problems with gid when installing > > > > > -----Oorspronkelijk bericht----- > > Van: Mark Sapiro [mailto:msapiro at value.net] > > Verzonden: zondag 21 januari 2007 17:56 > > Aan: Peter Coolen; mailman-users at python.org > > Onderwerp: Re: [Mailman-Users] problems with gid when installing > > > > Peter Coolen wrote: > > > > > >[Sun Jan 21 17:24:24 2007] [error] [client 192.168.0.18] > script not > > >found or unable to stat: usr/local/mailman/create > > > > > > This error came from the missing slash in ScriptAlias when > you tried > > to visit something like . > > > > I also tried mailman/create/ but create is not a directory.. > So you must not use the slash... It still can't find the files.. > > > > > > >[Sun Jan 21 17:24:37 2007] [error] [client 192.168.0.34] > script not > > >found or unable to stat: usr/local/mailman/ > > > > > > And this error came from something like > . > > > > If you want this latter URL to work (usually people send it to the > > listinfo page), you need something like > > > > RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo > > > > in your Apache config. > > > > I tried example.com/mailman/ just for a visit or a index page > but now I receive a 403 forbidden... > > > The error is still > [Sun Jan 21 23:08:45 2007] [error] [client 192.168.0.34] > script not found or unable to stat: /usr/local/mailman/create > > Do you have any other ideas for helping me? I changed the > missing slash but that was not the fault.. > > Peter > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/peter%40c > oolen.net > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq > 01.027.htp From msapiro at value.net Sun Jan 21 23:36:21 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 21 Jan 2007 14:36:21 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <006d01c73da9$582add40$2200a8c0@peter> Message-ID: Peter Coolen > >I also tried mailman/create/ but create is not a directory.. So you must not >use the slash... It still can't find the files.. Actually, create is a CGI so you can use a slash, but that isn't the issue here. >> If you want this latter URL to work (usually people send it >> to the listinfo page), you need something like >> >> RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo >> >> in your Apache config. >> > >I tried example.com/mailman/ just for a visit or a index page but now I >receive a 403 forbidden... Let's try to debug one issue at a time, but what's in error_log for the 403? >The error is still >[Sun Jan 21 23:08:45 2007] [error] [client 192.168.0.34] script not found or >unable to stat: /usr/local/mailman/create > >Do you have any other ideas for helping me? I changed the missing slash but >that was not the fault.. It was part of it. Apache is now looking for '/usr/local/mailman/create' instead of 'usr/local/mailman/create'. That's progress. So now it looks like a permissions issue. What are the permissions on /usr/local/mailman (the contents looked OK in a prior post). Have you tried running bin/check_perms? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at coolen.net Mon Jan 22 10:05:17 2007 From: peter at coolen.net (Peter Coolen) Date: Mon, 22 Jan 2007 10:05:17 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: References: <006d01c73da9$582add40$2200a8c0@peter> Message-ID: <001c01c73e04$6fcf5b00$2200a8c0@peter> > > > >I tried example.com/mailman/ just for a visit or a index > page but now I > >receive a 403 forbidden... > > > Let's try to debug one issue at a time, but what's in > error_log for the > 403? > > The error when visiting domain.com/mailman/ [Mon Jan 22 10:01:52 2007] [error] [client 62.58.15.252] attempt to invoke directory as script: /usr/local/mailman > So now it looks like a permissions issue. What are the permissions on > /usr/local/mailman (the contents looked OK in a prior post). > > Have you tried running bin/check_perms? Results of bin/check_perms root at localhost:/usr/local/mailman# bin/check_perms Warning: Private archive directory is other-executable (o+x). This could allow other users on your system to read private archives. If you're on a shared multiuser system, you should consult the installation manual on how to fix this. No problems found [18091 refs] root at localhost:/usr/local/mailman# root at suite19:/usr/local/mailman# ls -l total 72 drwxrwsr-x 11 root mailman 4096 Jan 20 16:23 Mailman drwxrwsr-x 4 root mailman 4096 Jan 20 16:19 archives drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 bin drwxrwsrwx 2 root mailman 4096 Jan 20 16:19 cgi-bin drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 cron drwxrwsr-x 2 root mailman 4096 Jan 20 16:30 data drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 icons drwxrwsr-x 3 root mailman 4096 Jan 20 16:28 lists drwxrwsr-x 2 root mailman 4096 Jan 20 16:29 locks drwxrwsr-x 2 root mailman 4096 Jan 20 16:29 logs drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 mail drwxrwsr-x 34 root mailman 4096 Jan 20 16:19 messages drwxrwsr-x 6 root mailman 4096 Jan 20 16:19 pythonlib drwxrwsr-x 11 root mailman 4096 Jan 20 16:29 qfiles drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 scripts drwxrwsr-x 2 root mailman 4096 Jan 20 16:19 spam drwxrwsr-x 35 root mailman 4096 Jan 20 16:19 templates drwxrwsr-x 4 root mailman 4096 Jan 20 16:19 tests Thanks, Peter From peter at coolen.net Mon Jan 22 10:28:07 2007 From: peter at coolen.net (Peter Coolen) Date: Mon, 22 Jan 2007 10:28:07 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <001c01c73e04$6fcf5b00$2200a8c0@peter> References: <006d01c73da9$582add40$2200a8c0@peter> <001c01c73e04$6fcf5b00$2200a8c0@peter> Message-ID: <001d01c73e07$a05ea980$2200a8c0@peter> Don't know why but it works almost ;-) I see a webpage and can create a new mailinglist... Only one last problem I can't create a new mailinglist.. Receive this error: Error: You are not authorized to create new mailing lists I changed the administrators passwd and list creater passwd with bin/mmsitepass -c or without -c but no effect.. Any ideas? thanks From leonk at construct.haifa.ac.il Mon Jan 22 10:43:28 2007 From: leonk at construct.haifa.ac.il (Leon Kolchinsky) Date: Mon, 22 Jan 2007 11:43:28 +0200 Subject: [Mailman-Users] Adding disclaimer to message footer via command line In-Reply-To: Message-ID: <20070122094655.C76D712C536@mail.edu.haifa.ac.il> > -----Original Message----- > From: Mark Sapiro [mailto:msapiro at value.net] > Sent: Sunday, January 21, 2007 6:35 PM > To: Leon Kolchinsky; mailman-users at python.org > Subject: Re: [Mailman-Users] Adding disclaimer to message footer via > command line > > Leon Kolchinsky wrote: > > > >Our management decided to add disclaimer to every footer in Digest and > >Non-digest options. > >I know that this is a bad netiquette but I have no choice. > > > >I have a lot of mailinglists running on my server and I though that may > be > >there is a way to do this addition with some script via command line and > add > >this to all lists, and save from myself doing it via web-interface > enormous > >times. > > > You can do this fairly easily in two ways. One is with a bin/withlist > script and the other is by running bin/config_list via a shell script. > > Several examples of withlist scripts (not this exact one) can be found > at or > . > > The shell script method is described at > . > > With the shell method, the input to config_list (configfile in the FAQ) > would contain > > > msg_footer="""First line of footer > Second line > ... > Last line > """ > digest_footer="""First line of footer > Second line > ... > Last line > """ > > You also want the set DEFAULT_MSG_FOOTER in mm_cfg.py (if you haven't > changed DEFAULT_DIGEST_FOOTER, you don't need to now as it defaults to > DEFAULT_MSG_FOOTER) so the footer is set for new lists. > Thank you Mark, I've created footer.txt file with the following text: msg_footer = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text""" digest_footer = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text""" And run this script: for i in $(/usr/lib/mailman/bin/list_lists -b) ; do /usr/lib/mailman/bin/config_list -i /path_to/footer.txt $i ; done I've also added the following to /usr/lib/mailman/Mailman/mm_cfg.py, so all new created lists will get this disclaimer automatically: DEFAULT_MSG_FOOTER = """_______________________________________________ %(real_name)s mailing list %(real_name)s@%(host_name)s %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s Here comes a disclaimer text""" > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan Best Regards, Leon Kolchinsky From gerrylist at drouillard.ca Mon Jan 22 12:43:19 2007 From: gerrylist at drouillard.ca (Gerald Drouillard) Date: Mon, 22 Jan 2007 06:43:19 -0500 Subject: [Mailman-Users] Changing Unsubscribe to NoMail Message-ID: <45B4A357.1040505@drouillard.ca> I have a list in which I would like the unsubscribe to set the nomail flag on instead of removing them from the list. The reason being that the list administrators tend to upload new email addresses periodically and we would not like to add someone that has already unsubscribed. Is there a magic switch that will turn unsubscribe behavior into nomail behavior? The mailman command line does not support the nomail option? From manuel at arteryplanet.net Mon Jan 22 15:23:52 2007 From: manuel at arteryplanet.net (ArteryPlanet.Net :: Manuel Kissoyan) Date: Mon, 22 Jan 2007 11:23:52 -0300 Subject: [Mailman-Users] domain in attached file url References: Message-ID: <015001c73e30$f79e0870$6401a8c0@sarna> Thanx Mark! That worked. :-) ----- Original Message ----- From: "Mark Sapiro" To: "ArteryPlanet.Net :: Manuel Kissoyan" ; "mailman mailing list" Sent: Sunday, January 21, 2007 3:22 PM Subject: Re: [Mailman-Users] domain in attached file url > ArteryPlanet.Net :: Manuel Kissoyan wrote: > >>Here is an example: >> >>-------------- next part -------------- >>A non-text attachment was scrubbed... >>Name: 704.pdf >>Type: application/pdf >>Size: 40815 bytes >>Desc: not available >>Url : >>/pipermail/mercedes_okiebenz.com/attachments/20070121/a1db2ede/attachment.pdf >> >> >>Any idea what could be the problem? > > > This has all the earmarks of a cPanel Mailman - specifically 2.1.9-cp1? > If so, this is a cPanel bug (fixed I think in 2.1.9-cp2). > > In any case, the problem is caused by an incorrect setting for > PUBLIC_ARCHIVE_URL in mm_cfg.py. I.e., '/pipermail/%(listname)s' > instead of 'http://%(hostname)s/pipermail/%(listname)s'. > > Also, see > > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > From peter at coolen.net Mon Jan 22 15:24:34 2007 From: peter at coolen.net (Peter Coolen) Date: Mon, 22 Jan 2007 15:24:34 +0100 Subject: [Mailman-Users] Mailman, postfix virtual domains and mysql Message-ID: <006401c73e31$09d71a40$2200a8c0@peter> Hi All, Mailman almost works... First some problems with the webserver but that's almost solved (can't use the list creaters and adminstrator password) Also got the following problem: I have a working postfix, mysql and virtual domains on the testserver.. This works fine and is also on the main server.. Now I want to install mailman (done) and integrate with my mailserver.. Does someone have a manual for postfix virtual domains with mysql? I looked it up in the site administrators manual but that's all about virtual domains and not about mysql.. My config files are very different. I use mysql_virtual_alias_maps, mysql_virtual_domains_maps and mysql_virtual_mailbox_maps files In these files are the following lines (table, select_field and where_field are different): user = username password = password hosts = localhost dbname = Databasename table = mailbox select_field = maildir where_field = username Can someone help me with this? Thanks From barth at fh-telekom-leipzig.de Mon Jan 22 14:37:57 2007 From: barth at fh-telekom-leipzig.de (Michael Barth) Date: Mon, 22 Jan 2007 14:37:57 +0100 Subject: [Mailman-Users] Archivierung Message-ID: <001301c73e2a$86ecc180$884bb8d4@fhtelekomleipzig.de> Hallo Mailman-Gemeinde, ich wollte fragen, ob es m?glich ist bei deaktivierter Archivierungsoption auch die Ablage der Attachements in /usr/local/mailman/archives/private/ /attachements zu unterbinden und wenn ja, wie? Danke Micha From kencheney at yahoo.com Mon Jan 22 15:37:27 2007 From: kencheney at yahoo.com (Ken Cheney) Date: Mon, 22 Jan 2007 06:37:27 -0800 (PST) Subject: [Mailman-Users] /bin/sh: mailman: command not found Message-ID: <963694.84811.qm@web53205.mail.yahoo.com> I get a million of these messages from Cron. Subject: [Mailman] Cron mailman/usr/lib/mailman/cron/gate_news I have read that it is because of something messed up with the crontab.in or soemthing. Something to do with the place #6 or something like that. I really did not find the message helpful at all since I know very little about cron in general. Can someone help? Otherwise I have Mailman fully functional on Fedora Core 6 and love it! --------------------------------- Food fight? Enjoy some healthy debate in the Yahoo! Answers Food & Drink Q&A. From msapiro at value.net Mon Jan 22 16:48:23 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 07:48:23 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <001c01c73e04$6fcf5b00$2200a8c0@peter> Message-ID: Peter Coolen wrote: >> > >> >I tried example.com/mailman/ just for a visit or a index >> page but now I >> >receive a 403 forbidden... >> >> >> Let's try to debug one issue at a time, but what's in >> error_log for the >> 403? >> >> >The error when visiting domain.com/mailman/ >[Mon Jan 22 10:01:52 2007] [error] [client 62.58.15.252] attempt to invoke >directory as script: /usr/local/mailman As I said in If you want this latter URL to work (usually people send it to the listinfo page), you need something like RedirectMatch ^/mailman[/]*$ http://example.com/mailman/listinfo in your Apache config. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 22 16:58:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 07:58:51 -0800 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: <001d01c73e07$a05ea980$2200a8c0@peter> Message-ID: Peter Coolen wrote: > Don't know why but it works almost ;-) > >I see a webpage and can create a new mailinglist... > >Only one last problem I can't create a new mailinglist.. > >Receive this error: >Error: You are not authorized to create new mailing lists > >I changed the administrators passwd and list creater passwd with >bin/mmsitepass -c or without -c but no effect.. I have seen other reports of this kind of thing, but first let's see if the web interface works in general. Try creating a list with bin/newlist and see if its web admin interface works. If that's all OK we can come back to the web create issue. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at coolen.net Mon Jan 22 17:16:07 2007 From: peter at coolen.net (Peter Coolen) Date: Mon, 22 Jan 2007 17:16:07 +0100 Subject: [Mailman-Users] problems with gid when installing In-Reply-To: References: <001d01c73e07$a05ea980$2200a8c0@peter> Message-ID: <008701c73e40$9f63dee0$2200a8c0@peter> This is working fine now.. I also found a manual (in the dark environments of the internet) for postfix virtual domains mysql and mailman.. Hope to inform you when it works but don't know for sure. Thanks for all the help.. You are great!! > -----Oorspronkelijk bericht----- > Van: Mark Sapiro [mailto:msapiro at value.net] > Verzonden: maandag 22 januari 2007 16:59 > Aan: Peter Coolen; mailman-users at python.org > Onderwerp: Re: [Mailman-Users] problems with gid when installing > > Peter Coolen wrote: > > > Don't know why but it works almost ;-) > > > >I see a webpage and can create a new mailinglist... > > > >Only one last problem I can't create a new mailinglist.. > > > >Receive this error: > >Error: You are not authorized to create new mailing lists > > > >I changed the administrators passwd and list creater passwd with > >bin/mmsitepass -c or without -c but no effect.. > > > I have seen other reports of this kind of thing, but first > let's see if the web interface works in general. > > Try creating a list with bin/newlist and see if its web admin > interface works. If that's all OK we can come back to the web > create issue. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From msapiro at value.net Mon Jan 22 17:34:43 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 08:34:43 -0800 Subject: [Mailman-Users] /bin/sh: mailman: command not found In-Reply-To: <963694.84811.qm@web53205.mail.yahoo.com> Message-ID: Ken Cheney wrote: > I get a million of these messages from Cron. Subject: [Mailman] Cron mailman/usr/lib/mailman/cron/gate_news > > I have read that it is because of something messed up with the crontab.in or soemthing. Something to do with the place #6 or something like that. There are two ways to install a crontab. The crontab can be a user's crontab and for the mailman user is usually in the file /var/spool/cron/mailman, but is usually manipulated with the crontab command (man 1 crontab). There are also system (package) crontabs which are usually found in the /etc/cron.d/ directory. These crontabs have a different format. Since they are not associated with a particular user, they have an additional entry for the username between the times and the command. Your problem is you have a file that was intended for /etc/cron.d/mailman, and it is installed in /var/spool/cron/mailman. You can fix this by moving /var/spool/cron/mailman to /etc/cron.d/, or by editing /var/spool/cron/mailman (as the mailman user give command 'crontab -e') and removing the word 'mailman' that precedes the command on each line of the file. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 22 19:03:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 10:03:51 -0800 Subject: [Mailman-Users] Changing Unsubscribe to NoMail In-Reply-To: <45B4A357.1040505@drouillard.ca> Message-ID: Gerald Drouillard wrote: >I have a list in which I would like the unsubscribe to set the nomail >flag on instead of removing them from the list. The reason being that >the list administrators tend to upload new email addresses periodically >and we would not like to add someone that has already unsubscribed. > >Is there a magic switch that will turn unsubscribe behavior into nomail >behavior? No. There is no such switch, and implementing one would be tricky. Here are some random thoughts. You could set unsubscribe_policy to Yes, so unsubscribe requires approval, and then manually do what you want. You might be able to automate this or 'semi-automate' it. When you set nomail for the user, you probably also want to set password reminders off. This could cause confusion for a user who changes her/his mind and tries to subscribe and the subscribe fails because (s)he is already a member. >The mailman command line does not support the nomail option? See the set_nomail.py withlist script at or . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Mon Jan 22 19:01:55 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 22 Jan 2007 12:01:55 -0600 Subject: [Mailman-Users] Mailman, postfix virtual domains and mysql In-Reply-To: <006401c73e31$09d71a40$2200a8c0@peter> References: <006401c73e31$09d71a40$2200a8c0@peter> Message-ID: At 3:24 PM +0100 1/22/07, Peter Coolen wrote: > Does someone have a manual for postfix virtual domains with mysql? I looked > it up in the site administrators manual but that's all about virtual domains > and not about mysql.. My config files are very different. This is a problem with postfix, and you're much more likely to get something useful from the documentation & FAQs at postfix.org, as well as reading the archives of the postfix-users mailing list, etc.... If you still don't find the answers to your questions after going through all those resources, you might want to post your question to the postfix-users list. Once you get your postfix issues straightened out, we might be able to help you with your Mailman issues. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From KTaylor at federalworking.com Mon Jan 22 21:10:10 2007 From: KTaylor at federalworking.com (Kent Taylor) Date: Mon, 22 Jan 2007 15:10:10 -0500 Subject: [Mailman-Users] But I don't want any Korean References: <4019801A047A7647BBE1783F5132415737576A@X.fwg.local> <4019801A047A7647BBE1783F5132415737576D@X.fwg.local> Message-ID: <4019801A047A7647BBE1783F5132415737576E@X.fwg.local> Very frustrating. I had a problem installing a mailman update a few months back on Solaris 10. I posted the traceback, and a very patient person directed me through modifying and repacking Setup.py in KoreanCodecs-2.0.5, and that did the trick. Now I'm trying to install another update, and I'm getting *Korean* errors again. I tried editing and repacking the Setup.py file like last time, but that didn't do it. So I did some googling and found instructions for editing and repacking hangul.c in KoreanCodecs-2.0.5. That didn't work either. Is there any way to disable Korean all-together, forever and ever, amen?! It's just so frustrating to waste an entire day working a foreign language issue on a product that will never be used by a non-English speaking person - ever. Anyway, here's the traceback from the log file... admin(2805): [----- Mailman Version: 2.1.9 -----] admin(2805): [----- Traceback ------] admin(2805): Traceback (most recent call last): admin(2805): File "/usr/local/mailman/scripts/driver", line 94, in run_main admin(2805): pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname]) admin(2805): File "/usr/local/mailman/Mailman/Cgi/listinfo.py", line 26, in ? admin(2805): from Mailman import Utils admin(2805): File "/usr/local/mailman/Mailman/Utils.py", line 39, in ? admin(2805): import email.Header admin(2805): File "/usr/local/mailman/pythonlib/email/Header.py", line 13, in ? admin(2805): from email.Charset import Charset admin(2805): File "/usr/local/mailman/pythonlib/email/Charset.py", line 178, in ? admin(2805): add_codec(_charset, _find_asian_codec(_charset, 'korean') or _charset) admin(2805): File "/usr/local/mailman/pythonlib/email/Charset.py", line 163, in _find_asian_codec admin(2805): unicode('foo', charset) admin(2805): File "/usr/sfw/lib/python2.3/encodings/__init__.py", line 91, in search_function admin(2805): mod = __import__(modname, globals(), locals(), _import_tail) admin(2805): File "/usr/local/mailman/pythonlib/korean/johab.py", line 26, in ? admin(2805): from korean.python.johab import * admin(2805): File "/usr/local/mailman/pythonlib/korean/python/johab.py", line 28, in ? admin(2805): johab2uni_chosung = { admin(2805): AttributeError: class Jaeum has no attribute 'SS' admin(2805): [----- Python Information -----] admin(2805): sys.version = 2.3.3 (#1, Dec 16 2004, 14:38:56) [C] admin(2805): sys.executable = /usr/sfw/bin/python admin(2805): sys.prefix = /usr/sfw admin(2805): sys.exec_prefix = /usr/sfw admin(2805): sys.path = /usr/sfw admin(2805): sys.platform = sunos5 admin(2805): [----- Environment Variables -----] admin(2805): SERVER_SOFTWARE: Apache/1.3.36 (Unix) mod_perl/1.29 admin(2805): SCRIPT_NAME: /mailman/listinfo admin(2805): SERVER_SIGNATURE:
Apache/1.3.36 Server at 127.0.0.1 Port 80
admin(2805): admin(2805): REQUEST_METHOD: GET admin(2805): SERVER_PROTOCOL: HTTP/1.1 admin(2805): QUERY_STRING: admin(2805): HTTP_USER_AGENT: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 1.0.3705) admin(2805): HTTP_CONNECTION: Keep-Alive admin(2805): SERVER_NAME: 127.0.0.1 admin(2805): REMOTE_ADDR: 192.168.90.28 admin(2805): SERVER_PORT: 80 admin(2805): SERVER_ADDR: 192.168.90.5 admin(2805): DOCUMENT_ROOT: /var/apache/htdocs admin(2805): PYTHONPATH: /usr/local/mailman admin(2805): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/listinfo admin(2805): SERVER_ADMIN: you at yourhost.com admin(2805): HTTP_HOST: m admin(2805): HTTP_UA_CPU: x86 admin(2805): REQUEST_URI: /mailman/listinfo admin(2805): HTTP_ACCEPT: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, */* admin(2805): GATEWAY_INTERFACE: CGI/1.1 admin(2805): REMOTE_PORT: 3176 admin(2805): HTTP_ACCEPT_LANGUAGE: en-us admin(2805): TZ: -5 admin(2805): HTTP_ACCEPT_ENCODING: gzip, deflate admin(2805): UNIQUE_ID: RbSPvcCoWgUAAAcbN8g Thank you in advance for any assistance in either solving the problem, or side-stepping it by disabling Korean support. /kpt From msapiro at value.net Mon Jan 22 23:29:11 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 14:29:11 -0800 Subject: [Mailman-Users] But I don't want any Korean In-Reply-To: <4019801A047A7647BBE1783F5132415737576E@X.fwg.local> Message-ID: Kent Taylor wrote: > >Is there any way to disable Korean all-together, forever and ever, amen?! It's just so frustrating to waste an entire day working a foreign language issue on a product that will never be used by a non-English speaking person - ever. Well, the real issue is what header files or ?? are missing on Solaris 10 that prevent successful compilation of hangul.c, but that issue aside, I don't offhand know how to remove all traces of Korean from the package in a way that would prevent the kind of error you're seeing. >Anyway, here's the traceback from the log file... >admin(2805): File "/usr/local/mailman/pythonlib/korean/johab.py", line 26, in ? >admin(2805): from korean.python.johab import * >admin(2805): File "/usr/local/mailman/pythonlib/korean/python/johab.py", line 28, in ? >admin(2805): johab2uni_chosung = { >admin(2805): AttributeError: class Jaeum has no attribute 'SS' Is there a hangul.so (or hangul with some other extension) file in /usr/local/mailman/pythonlib/korean/c/? If so, try removing it or renaming it. It is probably defective since you can't compile hangul.c and your edit may have broken it. If it isn't there, the library will fall back to /usr/local/mailman/pythonlib/korean/python/hangul.py which should work. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From chris.glanville at nec.com.au Tue Jan 23 03:55:41 2007 From: chris.glanville at nec.com.au (Christopher Glanville) Date: Tue, 23 Jan 2007 13:55:41 +1100 Subject: [Mailman-Users] mailman domain error Message-ID: <45B5792D.7010203@nec.com.au> Hi, Can anyone help me. I have got 2 domains. Domain a.com and domain b.com and I would like to be able to write messages to either of those domains. I cannot work out how you do this though since my mailman router does not take into account anywhere the domain name, only $local_part (see below) So another question is since it (apparently) doesn't look at the $local_part why is it that a.com works but b.com doesn't. The /var/log/exim4/mainlog file shows no difference between a.com and b.com but yet b.com doesn't arrive?? Many thanks in advance for any help on offer de Chris G PS my mailman router is: mailman_router: driver = accept require_files = MAILMAN_HOME/lists/$local_part/config.pck local_part_suffix_optional local_part_suffix = -bounces : -bounces+* : \ -confirm+* : -join : -leave : \ -owner : -request : -admin transport = mailman_transport From msapiro at value.net Tue Jan 23 07:53:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 22 Jan 2007 22:53:49 -0800 Subject: [Mailman-Users] mailman domain error In-Reply-To: <45B5792D.7010203@nec.com.au> Message-ID: Christopher Glanville wrote: >The /var/log/exim4/mainlog file shows no difference between a.com and >b.com but yet b.com doesn't arrive?? Are you saying that mail to list at b.com produces an exim log entry like 2007-01-22 22:38:05 JCB6FF-0001N0-GS => list R=mailman_router T=mailman_transport If so, that message got delivered to Mailman's 'in' queue (or at least got piped to the wrapper, but if list at a.com works, we can assume that the wrapper does the same thing because it's called the same way). Lot's of things can happen to the message after that, but the most likely is the message is held because require_explicit_destination is yes, and Mailman is looking for list at a.com and list at b.com is not in acceptable_aliases. What's in the admindb interface waiting for moderator action? What's in Mailman's vette log? What's in Mailman's other logs? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From leonk at construct.haifa.ac.il Tue Jan 23 16:31:56 2007 From: leonk at construct.haifa.ac.il (Leon Kolchinsky) Date: Tue, 23 Jan 2007 17:31:56 +0200 Subject: [Mailman-Users] Mailman, postfix virtual domains and mysql In-Reply-To: Message-ID: <20070123153529.6434914AF4C@mail.edu.haifa.ac.il> > -----Original Message----- > From: Brad Knowles [mailto:brad at shub-internet.org] > Sent: Monday, January 22, 2007 8:02 PM > To: Peter Coolen; mailman-users at python.org > Subject: Re: [Mailman-Users] Mailman, postfix virtual domains and mysql > > At 3:24 PM +0100 1/22/07, Peter Coolen wrote: > > > Does someone have a manual for postfix virtual domains with mysql? I > looked > > it up in the site administrators manual but that's all about virtual > domains > > and not about mysql.. My config files are very different. > You can look at my little howto here - http://www.web-cyradm.org/pipermail/web-cyradm/2005-August/019307.html It's an integration of Web-cyradm (postfix+cyrus+mysql virt. domains+web interface) with mailman installation. Best Regards, Leon Kolchinsky > This is a problem with postfix, and you're much more likely to get > something useful from the documentation & FAQs at postfix.org, as > well as reading the archives of the postfix-users mailing list, > etc.... If you still don't find the answers to your questions after > going through all those resources, you might want to post your > question to the postfix-users list. > > Once you get your postfix issues straightened out, we might be able > to help you with your Mailman issues. > > -- > Brad Knowles , Consultant & Author > Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and > Responsibilities" > Founding Member and Platinum Individual Sponsor of LOPSA: > > Papers: LinkedIn Profile: > From DPiniella at med.miami.edu Tue Jan 23 20:47:51 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 14:47:51 -0500 Subject: [Mailman-Users] mailman install problem Message-ID: Hi, I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm running into problems with "make install". I have no cc installed, I am using GCC 3.4.5 which I've installed from blastwave.org; python is 2.3.5. I've searched the archives of the list and hit up google to no avail, any suggestion(s) or hints would be most appreciated, I'm ready to scrap this install. I don't know if it's something funky in Sol10's make or maybe mailman's expecting gcc to be cc (see "unable to execute cc: No such file or directory \ error: command 'cc' failed with exit status 1" -- I did NOT specify the --with-gcc=no option during the configure). bash-3.00# make install Creating architecture independent directories... chmod o-r /usr/local/mailman/archives/private Creating architecture dependent directories... make[1]: Entering directory `/usr/local/mailman/bin' for f in mmsitepass newlist rmlist add_members list_members remove_members clone_member update arch sync_members check_db withlist check_perms find_member version config_list list_lists dumpdb cleanarch list_admins genaliases change_pw mailmanctl qrunner inject unshunt fix_url.py convert.py transcheck b4b5-archfix list_owners msgfmt.py show_qfiles discard rb-archfix reset_pw.py; \ do \ .././install-sh -c -m 755 ../build/bin/$f /usr/local/mailman/bin; \ done make[1]: Leaving directory `/usr/local/mailman/bin' make[1]: Entering directory `/usr/local/mailman/cron' for f in crontab.in; \ do \ .././install-sh -c -m 644 $f /usr/local/mailman/cron; \ done for f in checkdbs mailpasswds senddigests gate_news nightly_gzip bumpdigests disabled; \ do \ .././install-sh -c -m 755 ../build/cron/$f /usr/local/mailman/cron; \ done make[1]: Leaving directory `/usr/local/mailman/cron' make[1]: Entering directory `/usr/local/mailman/misc' for i in ./*.jpg ./*.png; \ do \ .././install-sh -c -m 644 $i /usr/local/mailman/icons; \ done for d in bin cron scripts tests; \ do \ dir=/usr/local/mailman/$d; \ .././install-sh -c -m 644 paths.py $dir; \ done .././install-sh -c -m 755 mailman /usr/local/mailman/scripts .././install-sh -c -m 644 sitelist.cfg /usr/local/mailman/data for p in email-2.5.8 JapaneseCodecs-1.4.11 KoreanCodecs-2.0.5; \ do \ gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \ (cd ./$p ; umask 02 ; PYTHONPATH=/usr/local/mailman/pythonlib /opt/csw/bin/python setup.py --quiet install --install-lib /usr/local/mailman/pythonlib --install-purelib /usr/local/mailman/pythonlib --install-data /usr/local/mailman/pythonlib); \ done /opt/csw/lib/python2.3/distutils/dist.py:213: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) unable to execute cc: No such file or directory error: command 'cc' failed with exit status 1 make[1]: *** [install-packages] Error 1 make[1]: Leaving directory `/usr/local/mailman/misc' *** Error code 2 The following command caused the error: for d in bin cron misc Mailman scripts src templates messages tests; \ do \ (cd $d; make DESTDIR= install); \ done make: Fatal error: Command failed for target `doinstall' bash-3.00# Dave From msapiro at value.net Tue Jan 23 21:17:01 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 12:17:01 -0800 Subject: [Mailman-Users] mailman install problem In-Reply-To: Message-ID: Piniella, David A wrote: > >I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm >running into problems with "make install". >I have no cc installed, I am using GCC 3.4.5 which I've installed from >blastwave.org; python is 2.3.5. > >I've searched the archives of the list and hit up google to no avail, >any suggestion(s) or hints would be most appreciated, I'm ready to scrap >this install. I don't know if it's something funky in Sol10's make or >maybe mailman's expecting gcc to be cc (see "unable to execute cc: No >such file or directory \ error: command 'cc' failed with exit status 1" >-- I did NOT specify the --with-gcc=no option during the configure). configure should find an appropriate C compiler and taylor the Makefile appropriately. Were there any errors from configure. What does config.log say about the C compiler? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From DPiniella at med.miami.edu Tue Jan 23 21:41:09 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 15:41:09 -0500 Subject: [Mailman-Users] mailman install problem References: Message-ID: I don't see any obvious errors, but I don't know... bash-3.00# more config.log This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. configure:558: checking for --with-python configure:576: checking for python configure:612: checking Python interpreter configure:628: checking Python version configure:662: checking that Python has a working distutils configure:728: checking for a BSD compatible install configure:781: checking whether make sets ${MAKE} configure:810: checking for true configure:846: checking for --without-gcc configure:875: checking for gcc configure:988: checking whether the C compiler (gcc ) works configure:1004: gcc -o conftest conftest.c 1>&5 configure:1030: checking whether the C compiler (gcc ) is a cross-compiler configure:1035: checking whether we are using GNU C configure:1044: gcc -E conftest.c configure:1063: checking whether gcc accepts -g configure:1115: checking whether #! works in shell scripts configure:1148: checking for --with-var-prefix configure:1163: checking for --with-permcheck configure:1195: checking for --with-username configure:1213: checking for user name "mailman" configure:1259: checking for --with-groupname configure:1278: checking for group name "mailman" configure:1323: checking permissions on /usr/local/mailman configure:1379: checking for mail wrapper group; i.e. --with-mail-gid configure:1438: checking for CGI wrapper group; i.e. --with-cgi-gid configure:1500: checking for CGI extensions configure:1520: checking for --with-mailhost configure:1538: checking for --with-urlhost configure:1567: checking for default mail host name configure:1574: checking for default URL host component configure:1586: checking for strerror configure:1614: gcc -o conftest -g -O2 conftest.c 1>&5 configure:1586: checking for setregid configure:1614: gcc -o conftest -g -O2 conftest.c 1>&5 configure:1586: checking for syslog configure:1614: gcc -o conftest -g -O2 conftest.c 1>&5 configure:1677: checking how to run the C preprocessor configure:1698: gcc -E conftest.c >/dev/null 2>conftest.out configure:1757: checking for ANSI C header files configure:1770: gcc -E conftest.c >/dev/null 2>conftest.out configure:1837: gcc -o conftest -g -O2 conftest.c 1>&5 configure:1864: checking for syslog.h configure:1874: gcc -E conftest.c >/dev/null 2>conftest.out configure:1903: checking for uid_t in sys/types.h configure:1937: checking type of array argument to getgroups configure:1970: gcc -o conftest -g -O2 conftest.c 1>&5 configure:2012: checking for vsnprintf configure:2040: gcc -o conftest -g -O2 conftest.c 1>&5 configure:2024: warning: conflicting types for built-in function 'vsnprintf' bash-3.00# -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Tue 1/23/2007 3:17 PM To: Piniella, David A; mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem Piniella, David A wrote: > >I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm >running into problems with "make install". >I have no cc installed, I am using GCC 3.4.5 which I've installed from >blastwave.org; python is 2.3.5. > >I've searched the archives of the list and hit up google to no avail, >any suggestion(s) or hints would be most appreciated, I'm ready to scrap >this install. I don't know if it's something funky in Sol10's make or >maybe mailman's expecting gcc to be cc (see "unable to execute cc: No >such file or directory \ error: command 'cc' failed with exit status 1" >-- I did NOT specify the --with-gcc=no option during the configure). configure should find an appropriate C compiler and taylor the Makefile appropriately. Were there any errors from configure. What does config.log say about the C compiler? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Tue Jan 23 21:52:27 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Tue, 23 Jan 2007 13:52:27 -0700 (MST) Subject: [Mailman-Users] mailman install problem In-Reply-To: Message-ID: <200701232052.l0NKqRXB008444@bronze.lostwells.net> The esteemed Piniella, David A has said: > > Hi, > > I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm > running into problems with "make install". > I have no cc installed, I am using GCC 3.4.5 which I've installed from > blastwave.org; python is 2.3.5. > > I've searched the archives of the list and hit up google to no avail, > any suggestion(s) or hints would be most appreciated, I'm ready to scrap > this install. I don't know if it's something funky in Sol10's make or > maybe mailman's expecting gcc to be cc (see "unable to execute cc: No > such file or directory \ error: command 'cc' failed with exit status 1" > -- I did NOT specify the --with-gcc=no option during the configure). (snippity snippity) > > /opt/csw/lib/python2.3/distutils/dist.py:213: UserWarning: 'licence' > distribution option is deprecated; use 'license' > warnings.warn(msg) > unable to execute cc: No such file or directory > error: command 'cc' failed with exit status 1 > make[1]: *** [install-packages] Error 1 > make[1]: Leaving directory `/usr/local/mailman/misc' > *** Error code 2 You're probably seeing what's a well-known problem with Solaris using GNU-type configure and Makefile generation. Easy to fix. The cc that some makefile is finding is probably /usr/ucb/cc in the Solaris install. That is a stub that does nothing. Rename it to cc.bsd. On a Solaris site, you have to set up PATH as a post-install operation. Most Solaris admins have a post-install script for doing this. Do a check, using the which command. which gcc should point to the path where the gcc you want to use is located, and do a version check. Then do a which cc. Unless you have Studio 11 installed, you should get a "not found" return. The Studio 11 compiler resources are in /opt/SUNWspro/bin if they are installed. You may have to locate the offending Makefile or rerun configure to recover, but try make install first, after assuring that nothing can find /usr/ucb/cc. Hank Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From DPiniella at med.miami.edu Tue Jan 23 22:04:26 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 16:04:26 -0500 Subject: [Mailman-Users] mailman install problem References: <200701232052.l0NKqRXB008444@bronze.lostwells.net> Message-ID: I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): bash-3.00# which gcc /opt/csw/gcc3/bin/gcc bash-3.00# which cc no cc in /usr/local/sbin /opt/csw/sbin /opt/sfw/sbin /opt/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /opt/bin /bin /usr/openwin/bin /opt/csw/bin /opt/sfw/bin /usr/apache/bin /opt/csw/gcc3/bin /usr/ccs/bin bash-3.00# I'm still getting the same "unable to execute cc" error. I really don't understand it; would there be any cached info? -d. -----Original Message----- From: Hank van Cleef [mailto:vancleef at bronze.lostwells.net] Sent: Tue 1/23/2007 3:52 PM To: Piniella, David A Cc: mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem The esteemed Piniella, David A has said: > > Hi, > > I'm trying to install mailman 2.1.9 on a Solaris 10 x86 machine and I'm > running into problems with "make install". > I have no cc installed, I am using GCC 3.4.5 which I've installed from > blastwave.org; python is 2.3.5. > > I've searched the archives of the list and hit up google to no avail, > any suggestion(s) or hints would be most appreciated, I'm ready to scrap > this install. I don't know if it's something funky in Sol10's make or > maybe mailman's expecting gcc to be cc (see "unable to execute cc: No > such file or directory \ error: command 'cc' failed with exit status 1" > -- I did NOT specify the --with-gcc=no option during the configure). (snippity snippity) > > /opt/csw/lib/python2.3/distutils/dist.py:213: UserWarning: 'licence' > distribution option is deprecated; use 'license' > warnings.warn(msg) > unable to execute cc: No such file or directory > error: command 'cc' failed with exit status 1 > make[1]: *** [install-packages] Error 1 > make[1]: Leaving directory `/usr/local/mailman/misc' > *** Error code 2 You're probably seeing what's a well-known problem with Solaris using GNU-type configure and Makefile generation. Easy to fix. The cc that some makefile is finding is probably /usr/ucb/cc in the Solaris install. That is a stub that does nothing. Rename it to cc.bsd. On a Solaris site, you have to set up PATH as a post-install operation. Most Solaris admins have a post-install script for doing this. Do a check, using the which command. which gcc should point to the path where the gcc you want to use is located, and do a version check. Then do a which cc. Unless you have Studio 11 installed, you should get a "not found" return. The Studio 11 compiler resources are in /opt/SUNWspro/bin if they are installed. You may have to locate the offending Makefile or rerun configure to recover, but try make install first, after assuring that nothing can find /usr/ucb/cc. Hank Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Tue Jan 23 22:17:22 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 13:17:22 -0800 Subject: [Mailman-Users] mailman install problem In-Reply-To: Message-ID: Piniella, David A wrote: >I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): >I'm still getting the same "unable to execute cc" error. I really don't understand it; would there be any cached info? Did you rerun configure (not just config.status) after making those changes? If all else fails, look at src/Makefile in the directory in which you are running make and find the CC= line (which probably says 'CC= cc') and change it to 'CC= gcc'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From DPiniella at med.miami.edu Tue Jan 23 22:38:23 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 16:38:23 -0500 Subject: [Mailman-Users] mailman install problem References: Message-ID: Thanks for you help, guys. Actually, I checked the Makefile in /usr/local/mailman (my $prefix), and /usr/local/mailman/src/Makefile and they both have CC= gcc. I have deleted the Makefiles, config.cache & config.status, rerun ./configure (my specific options are --prefix, --with-cgi-gid, --with-mailhost and --with-urlhost) and re-run make and make install. I keep getting the error on make install. For laughs, since I saw the Makefile had the full path in the PYTHON= line, I put the full path to gcc in the CC= line, re-ran configure and it still fails. -d. -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Tuesday, January 23, 2007 4:17 PM To: Piniella, David A; Hank van Cleef Cc: mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem Piniella, David A wrote: >I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): >I'm still getting the same "unable to execute cc" error. I really don't understand it; would there be any cached info? Did you rerun configure (not just config.status) after making those changes? If all else fails, look at src/Makefile in the directory in which you are running make and find the CC= line (which probably says 'CC= cc') and change it to 'CC= gcc'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Tue Jan 23 22:51:36 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Tue, 23 Jan 2007 14:51:36 -0700 (MST) Subject: [Mailman-Users] mailman install problem In-Reply-To: Message-ID: <200701232151.l0NLpamW012735@bronze.lostwells.net> The esteemed Piniella, David A has said: > > I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): > > bash-3.00# which gcc > /opt/csw/gcc3/bin/gcc > > bash-3.00# which cc > no cc in /usr/local/sbin /opt/csw/sbin /opt/sfw/sbin /opt/sbin /usr/sbin /sbin /usr/local/bin /usr/bin /opt/bin /bin /usr/openwin/bin /opt/csw/bin /opt/sfw/bin /usr/apache/bin /opt/csw/gcc3/bin /usr/ccs/bin > > bash-3.00# > > I'm still getting the same "unable to execute cc" error. I really don't understand it; would there be any cached info? Hokay! Here's the deal. I have just walked this question through with a junk Mailman 2.1.9 tree. This tree was originally build using Studio 11 cc. I took the pointer to that out of my PATH, ran a make clean, and ran configure. It crashed at what appears to be the same point yours did. Then I ran a make distclean, and reran configure. That ran to completion properly. Followed that up with a make, although that doesn't compile the stuff in the misc directory. However, checking that makefile it has CC=gcc. I'll suggest that you start over with a make distclean and a new configure. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Tue Jan 23 23:08:43 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 14:08:43 -0800 Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: Piniella, David A wrote: >Thanks for you help, guys. Actually, I checked the Makefile in >/usr/local/mailman (my $prefix), and /usr/local/mailman/src/Makefile and >they both have CC=3D gcc. I have deleted the Makefiles, config.cache & >config.status, rerun ./configure (my specific options are --prefix, >--with-cgi-gid, --with-mailhost and --with-urlhost) and re-run make and >make install. I keep getting the error on make install. For laughs, >since I saw the Makefile had the full path in the PYTHON=3D line, I put >the full path to gcc in the CC=3D line, re-ran configure and it still >fails. Yeah, I realized the problem after I sent my last reply. The problem is in the 'make install'. The install target runs the install target of misc/Makefile which in turn runs install-packages which installs the email, JapaneseCodecs, and KoreanCodecs packages. This install starts by unzipping and expanding the .tar.gz files containing the packages and then running the setup.py file from the package. Part of the KoreanCodecs package requires compilation of C modules. I think this is where you and other Solaris users run into difficulty. I'm not really an expert on this, but perhaps if you put a symlink to your gcc named cc somewhere on your path before running make install, this will do it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From DPiniella at med.miami.edu Tue Jan 23 23:11:40 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 17:11:40 -0500 Subject: [Mailman-Users] mailman install problem References: <200701232151.l0NLpamW012735@bronze.lostwells.net> Message-ID: Hmmm, that didn't work. Same error about no cc... -----Original Message----- From: Hank van Cleef [mailto:vancleef at bronze.lostwells.net] Sent: Tuesday, January 23, 2007 4:52 PM To: Piniella, David A Cc: mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem The esteemed Piniella, David A has said: > > I have actually already renamed the /usr/ucb/cc (to cc_old) and modified my path (specifically for the install): > > bash-3.00# which gcc > /opt/csw/gcc3/bin/gcc > > bash-3.00# which cc > no cc in /usr/local/sbin /opt/csw/sbin /opt/sfw/sbin /opt/sbin > /usr/sbin /sbin /usr/local/bin /usr/bin /opt/bin /bin /usr/openwin/bin > /opt/csw/bin /opt/sfw/bin /usr/apache/bin /opt/csw/gcc3/bin > /usr/ccs/bin > > bash-3.00# > > I'm still getting the same "unable to execute cc" error. I really don't understand it; would there be any cached info? Hokay! Here's the deal. I have just walked this question through with a junk Mailman 2.1.9 tree. This tree was originally build using Studio 11 cc. I took the pointer to that out of my PATH, ran a make clean, and ran configure. It crashed at what appears to be the same point yours did. Then I ran a make distclean, and reran configure. That ran to completion properly. Followed that up with a make, although that doesn't compile the stuff in the misc directory. However, checking that makefile it has CC=gcc. I'll suggest that you start over with a make distclean and a new configure. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From DPiniella at med.miami.edu Tue Jan 23 23:21:22 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 17:21:22 -0500 Subject: [Mailman-Users] mailman install problem - Solaris References: Message-ID: No dice, I tried that with gcc and yacc. Is there any way to just avoid the Japanese and Korean codecs packages' compilation, or to skip them entirely? I don't really need to host any lists in Japanese or Korean (or do these packages do something else?) -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Tuesday, January 23, 2007 5:09 PM To: Piniella, David A; Hank van Cleef Cc: mailman-users at python.org; Kent Taylor Subject: RE: [Mailman-Users] mailman install problem - Solaris Piniella, David A wrote: >Thanks for you help, guys. Actually, I checked the Makefile in >/usr/local/mailman (my $prefix), and /usr/local/mailman/src/Makefile >and they both have CC=3D gcc. I have deleted the Makefiles, >config.cache & config.status, rerun ./configure (my specific options >are --prefix, --with-cgi-gid, --with-mailhost and --with-urlhost) and >re-run make and make install. I keep getting the error on make install. >For laughs, since I saw the Makefile had the full path in the PYTHON=3D >line, I put the full path to gcc in the CC=3D line, re-ran configure >and it still fails. Yeah, I realized the problem after I sent my last reply. The problem is in the 'make install'. The install target runs the install target of misc/Makefile which in turn runs install-packages which installs the email, JapaneseCodecs, and KoreanCodecs packages. This install starts by unzipping and expanding the .tar.gz files containing the packages and then running the setup.py file from the package. Part of the KoreanCodecs package requires compilation of C modules. I think this is where you and other Solaris users run into difficulty. I'm not really an expert on this, but perhaps if you put a symlink to your gcc named cc somewhere on your path before running make install, this will do it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 23 23:59:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 14:59:02 -0800 Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: Piniella, David A wrote: > >No dice, I tried that with gcc and yacc. Is there any way to just avoid >the Japanese and Korean codecs packages' compilation, or to skip them >entirely? I don't really need to host any lists in Japanese or Korean >(or do these packages do something else?) This too is really tricky. See yesterday's take on this in the thread at . There is some issue which seems to affect some combination of Solaris release > 8 and some versions of Python's distutils module and probably the specific configuration of the Solaris machine that impacts the installation of the C modules in the KoreanCodecs package. You can't just eliminate the Korean codecs because it causes problems for the email package. If your Python is 2.4 or later however, there are Korean codecs in Python so you don't need the package in Mailman's pythonlib. If you have an earlier Python, installing CJKCodecs might eliminate the need for the Korean and Japanese codecs in Mailman's pythonlib. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From peter at cww.org.uk Wed Jan 24 00:31:13 2007 From: peter at cww.org.uk (Peter Edley) Date: Tue, 23 Jan 2007 23:31:13 -0000 Subject: [Mailman-Users] some messages get treat as spam Message-ID: I have an issue with a list I am running some messages sent to the list are getting treat as spam by some users systems but not all of the messages are. There does not seem to be a pattern at this point in time, the messages I know that have been treat as spam have come from users using different isp's and different email clients so there does not seem to be a pattern there. This is not just one user who is finding messages marked as spam although if a message is marked as spam for one affected user it seems to be for all of them. But not all users are affected by this. Any help in tracking down the problem would be greatly received. From msapiro at value.net Wed Jan 24 01:27:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 16:27:49 -0800 Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: Mark Sapiro wrote: >Piniella, David A wrote: >> >>No dice, I tried that with gcc and yacc. Is there any way to just avoid >>the Japanese and Korean codecs packages' compilation, or to skip them >>entirely? I don't really need to host any lists in Japanese or Korean >>(or do these packages do something else?) > > >This too is really tricky. See yesterday's take on this in the thread >at >. I *think* the attached patch to misc/Makefile will solve the problem. Here's the procedure: After running 'configure' apply the attached patch to misc/Makefile. Then if you have a pythonlib/korean directory in your installation ($prefix) directory left over from previous attempts, remove it. Then 'make install' should give you a working installation. This installed version of the Korean codecs will not have the compiled C language modules, but if you aren't actually using Korean, the Python modules will be good enough - the only difference is performance. Let us know how it works out. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Makefile.diff.txt Url: http://mail.python.org/pipermail/mailman-users/attachments/20070123/0726ccdc/attachment.txt From msapiro at value.net Wed Jan 24 01:52:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 16:52:59 -0800 Subject: [Mailman-Users] some messages get treat as spam In-Reply-To: Message-ID: Peter Edley wrote: >I have an issue with a list I am running some messages sent to the list are >getting treat as spam by some users systems but not all of the messages are. > > > >There does not seem to be a pattern at this point in time, the messages I >know that have been treat as spam have come from users using different isp's >and different email clients so there does not seem to be a pattern there. Also, not all messages from the list are treated as spam so it would seem that no Mailman specific or list specific message characteristics are the trigger either. >This is not just one user who is finding messages marked as spam although if >a message is marked as spam for one affected user it seems to be for all of >them. > > > >But not all users are affected by this. The first thing to investigate is what do the affected recipients have in common? Also, if one of user-a's posts is treated as spam by the affected recipients, are all of user-a's so treated? There's not really a whole lot you can find out from the large ISPs about why they flag particular messages. They are understandably reluctant to disclose what criteria they use. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From DPiniella at med.miami.edu Wed Jan 24 03:56:53 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 21:56:53 -0500 Subject: [Mailman-Users] mailman install problem - Solaris References: Message-ID: I did a make distclean, a new configure, patched, verified that my $prefix/pythonlib/ dir had no korean dir (a japanese dir though) and then make and make install and this is where it breaks: (a lot of listing and compiling, well after where it was breaking before and then ) Compiling /usr/local/mailman/Mailman/htmlformat.py ... Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/mm_cfg.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 46, in ? import paths File "/usr/local/mailman/bin/paths.py", line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 bash-3.00# Could this be because I am using Python 2.3.5 or my python doesn't have the korean module? Dave -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Tue 1/23/2007 7:27 PM To: Piniella, David A; Hank van Cleef Cc: Kent Taylor; mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris Mark Sapiro wrote: >Piniella, David A wrote: >> >>No dice, I tried that with gcc and yacc. Is there any way to just avoid >>the Japanese and Korean codecs packages' compilation, or to skip them >>entirely? I don't really need to host any lists in Japanese or Korean >>(or do these packages do something else?) > > >This too is really tricky. See yesterday's take on this in the thread >at >. I *think* the attached patch to misc/Makefile will solve the problem. Here's the procedure: After running 'configure' apply the attached patch to misc/Makefile. Then if you have a pythonlib/korean directory in your installation ($prefix) directory left over from previous attempts, remove it. Then 'make install' should give you a working installation. This installed version of the Korean codecs will not have the compiled C language modules, but if you aren't actually using Korean, the Python modules will be good enough - the only difference is performance. Let us know how it works out. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From DPiniella at med.miami.edu Wed Jan 24 04:09:36 2007 From: DPiniella at med.miami.edu (Piniella, David A) Date: Tue, 23 Jan 2007 22:09:36 -0500 Subject: [Mailman-Users] mailman install problem - Solaris References: Message-ID: OK, for giggles, I updated python to 2.5 from 2.3.5, and now configure does this: checking for group name "mailman"... Traceback (most recent call last): File "conftest.py", line 1, in import grp ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open failed: No such file or directory cat: cannot open conftest.out configure: error: ***** No "mailman" group found! ***** Your system must have a "mailman" group defined ***** (usually in your /etc/group file). Please see the INSTALL ***** file for details. bash-3.00# cat /etc/group | grep mailman mailman::100:mailman bash-3.00# ...what? Dave. -----Original Message----- From: mailman-users-bounces+dpiniella=med.miami.edu at python.org on behalf of Piniella, David A Sent: Tue 1/23/2007 9:56 PM To: Mark Sapiro; Hank van Cleef Cc: Kent Taylor; mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris I did a make distclean, a new configure, patched, verified that my $prefix/pythonlib/ dir had no korean dir (a japanese dir though) and then make and make install and this is where it breaks: (a lot of listing and compiling, well after where it was breaking before and then ) Compiling /usr/local/mailman/Mailman/htmlformat.py ... Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/mm_cfg.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 46, in ? import paths File "/usr/local/mailman/bin/paths.py", line 60, in ? import korean ImportError: No module named korean make: *** [update] Error 1 bash-3.00# Could this be because I am using Python 2.3.5 or my python doesn't have the korean module? Dave -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Tue 1/23/2007 7:27 PM To: Piniella, David A; Hank van Cleef Cc: Kent Taylor; mailman-users at python.org Subject: Re: [Mailman-Users] mailman install problem - Solaris Mark Sapiro wrote: >Piniella, David A wrote: >> >>No dice, I tried that with gcc and yacc. Is there any way to just avoid >>the Japanese and Korean codecs packages' compilation, or to skip them >>entirely? I don't really need to host any lists in Japanese or Korean >>(or do these packages do something else?) > > >This too is really tricky. See yesterday's take on this in the thread >at >. I *think* the attached patch to misc/Makefile will solve the problem. Here's the procedure: After running 'configure' apply the attached patch to misc/Makefile. Then if you have a pythonlib/korean directory in your installation ($prefix) directory left over from previous attempts, remove it. Then 'make install' should give you a working installation. This installed version of the Korean codecs will not have the compiled C language modules, but if you aren't actually using Korean, the Python modules will be good enough - the only difference is performance. Let us know how it works out. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users at python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dpiniella%40med.miami.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From msapiro at value.net Wed Jan 24 04:55:31 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 19:55:31 -0800 Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: Piniella, David A wrote: > >I did a make distclean, a new configure, patched, verified that my = >$prefix/pythonlib/ dir had no korean dir (a japanese dir though) and = >then make and make install and this is where it breaks: > >(a lot of listing and compiling, well after where it was breaking before = >and then ) >Compiling /usr/local/mailman/Mailman/htmlformat.py ... >Compiling /usr/local/mailman/Mailman/i18n.py ... >Compiling /usr/local/mailman/Mailman/mm_cfg.py ... >Compiling /usr/local/mailman/Mailman/versions.py ... >Traceback (most recent call last): > File "bin/update", line 46, in ? > import paths > File "/usr/local/mailman/bin/paths.py", line 60, in ? > import korean >ImportError: No module named korean >make: *** [update] Error 1 >bash-3.00# So mailman got completely installed and got to the last step which is running bin/update to update the previously existing installation if any. If this is a brand new install, you're done except there is a problem with importing the korean codecs. Things to check (although I don't know how your later Python update may fit in) Is there now a /usr/local/mailman/pythonlib/korean/ (installed by the last make install)? Does it have at least mappings/ and python/ subdirectories and do all three of these directories including korean/ itself have several .py and .pyc files including a __init__.py and __init__.pyc in each? Also is there a file /usr/local/mailman/pythonlib/korean.pth? Does /usr/local/mailman/bin/paths.py contain among other things prefix = '/usr/local/mailman' and later on # We also need the pythonlib directory on the path to pick up any overrides of # standard modules and packages. Note that these must go at the front of the # path for this reason. sys.path.insert(0, os.path.join(prefix, 'pythonlib')) If all the above is true, I can't understand the error. >Could this be because I am using Python 2.3.5 or my python doesn't have >the korean module? It's not supposed to be. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jan 24 05:01:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 23 Jan 2007 20:01:12 -0800 Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: Piniella, David A wrote: > >OK, for giggles, I updated python to 2.5 from 2.3.5, and now configure >does this: > >checking for group name "mailman"... Traceback (most recent call last): > File "conftest.py", line 1, in > import grp >ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open failed: No such >file or directory The above is the significant error. The others are secondary. It looks like Python 2.5 is not completely/correctly installed. >cat: cannot open conftest.out >configure: error: >***** No "mailman" group found! >***** Your system must have a "mailman" group defined >***** (usually in your /etc/group file). Please see the INSTALL >***** file for details. The "No "mailman" group found!" error is bogus. It is a side effect of the prior errors. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Wed Jan 24 05:19:21 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Tue, 23 Jan 2007 21:19:21 -0700 (MST) Subject: [Mailman-Users] mailman install problem - Solaris In-Reply-To: Message-ID: <200701240419.l0O4JLmC002806@bronze.lostwells.net> The esteemed Piniella, David A has said: > > > > OK, for giggles, I updated python to 2.5 from 2.3.5, and now configure does this: > > checking for group name "mailman"... Traceback (most recent call last): > File "conftest.py", line 1, in > import grp > ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open failed: No such file or directory > cat: cannot open conftest.out > configure: error: > ***** No "mailman" group found! > ***** Your system must have a "mailman" group defined > ***** (usually in your /etc/group file). Please see the INSTALL > ***** file for details. > bash-3.00# cat /etc/group | grep mailman > mailman::100:mailman > bash-3.00# > > ...what? David, at this point I'm going to bow out and let Mark do the talking. The only real contribution I had to make was to flag the /usr/bin/cc issue in Solaris, which is is something that bites almost everyone sooner or later. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From tomnaugh at gmail.com Wed Jan 24 22:13:10 2007 From: tomnaugh at gmail.com (Tom Kavanaugh) Date: Wed, 24 Jan 2007 13:13:10 -0800 Subject: [Mailman-Users] Level's of list admin? Message-ID: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> Hello, My mail list is running for over a year now. Most of my mail lists are for projects, and these projects have Project Managers. I am considering handing over tasks like adding/deleting users to Project Managers. Making these Project Managers as list moderators does not give them access to add/delete users. Is there a way to give them this access. I do not want to make them list admin's. Like a lower level of list admin, where they cannot change any list parameter. But, just be able to add/remove users. Thanks Tom From phanh at canby.k12.or.us Wed Jan 24 23:36:55 2007 From: phanh at canby.k12.or.us (Hung Phan) Date: Wed, 24 Jan 2007 14:36:55 -0800 Subject: [Mailman-Users] Conceal receiver addresses Message-ID: <6E1724D9-BA9C-4B93-92DA-2A619CC82759@canby.k12.or.us> Hello, We got request from our users to conceal the receiver addresses. We searched but came back empty. Is there a way to conceal the receiver addresses in Mailman? Thank you, From msapiro at value.net Thu Jan 25 02:01:07 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 24 Jan 2007 17:01:07 -0800 Subject: [Mailman-Users] Conceal receiver addresses In-Reply-To: <6E1724D9-BA9C-4B93-92DA-2A619CC82759@canby.k12.or.us> Message-ID: Hung Phan wrote: > >We got request from our users to conceal the receiver addresses. We >searched but came back empty. Is there a way to conceal the receiver >addresses in Mailman? If you mean the list posting address, the answer is no. If you mean the individual recipient (list member) addresses, set Non-digest options->personalize to No. But then I think I really don't understand your question, as if the list is fully personalized, each recipient sees only his or her own address, so that shouldn't be an issue. So please be specific about what addresses you see in what messages that you don't want to see. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spyropolymiadis at kromestudios.com Thu Jan 25 02:46:52 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Thu, 25 Jan 2007 12:16:52 +1030 Subject: [Mailman-Users] Level's of list admin? In-Reply-To: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> References: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> Message-ID: <45B80C0C.70404@kromestudios.com> Tom Kavanaugh wrote: > Hello, > > My mail list is running for over a year now. > Most of my mail lists are for projects, and these projects have Project > Managers. > I am considering handing over tasks like adding/deleting users to Project > Managers. > > Making these Project Managers as list moderators does not give them access > to add/delete users. > Is there a way to give them this access. I do not want to make them list > admin's. > > Like a lower level of list admin, where they cannot change any list > parameter. But, just be able to add/remove users. > > Thanks > Tom This is a great question - I too am looking for the exact same thing... Cheers :) This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. From msapiro at value.net Thu Jan 25 02:47:53 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 24 Jan 2007 17:47:53 -0800 Subject: [Mailman-Users] Level's of list admin? In-Reply-To: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> Message-ID: Tom Kavanaugh wrote: > >Making these Project Managers as list moderators does not give them access >to add/delete users. >Is there a way to give them this access. I do not want to make them list >admin's. > >Like a lower level of list admin, where they cannot change any list >parameter. But, just be able to add/remove users. This capability is fairly often requested and may or may not be implemented in the future, but it currently doesn't exist. There is a very kludgey way to do more or less what you want as follows: Set the list's subscribe_policy to Require approval and unsubscribe_policy to Yes. Then the moderator can subscribe someone from the listinfo page and approve the subscription from the admindb page without the subscribee needing to confirm. Likwise, the moderator can unsubscribe someone from their user options login page and approve the unsubscription from the admindb page without the unsubscribee needing to confirm. Of course, setting these policies may be unsatisfactory for other reasons. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Thu Jan 25 04:06:21 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 24 Jan 2007 21:06:21 -0600 Subject: [Mailman-Users] Level's of list admin? In-Reply-To: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> References: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> Message-ID: At 1:13 PM -0800 1/24/07, Tom Kavanaugh wrote: > Making these Project Managers as list moderators does not give them access > to add/delete users. > Is there a way to give them this access. I do not want to make them list > admin's. Not in the current code, no. You can have site admins, who can do anything on any list anywhere on the site, by using the site admin password. You can also use the site admin password to create lists, or you can have a separate list creation password. Then you have list admins, and then list moderators. There aren't any other levels of list administration personnel. > Like a lower level of list admin, where they cannot change any list > parameter. But, just be able to add/remove users. You could change the source code. I don't know how hard that would be to do, but there are others on this list who might be able to give you some guidance there. Keep in mind that there may already be patches to do this sort of thing. You should look at the SourceForge patch list for Mailman, to see if there is anything that addresses your question. If there is not already an existing patch to achieve this functionality, then one thing we'd ask you to do is that once you've made the necessary code changes at your site to then share those with the rest of the community via the same patch facility. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From tomnaugh at gmail.com Thu Jan 25 07:54:56 2007 From: tomnaugh at gmail.com (Tom Kavanaugh) Date: Wed, 24 Jan 2007 22:54:56 -0800 Subject: [Mailman-Users] Level's of list admin? In-Reply-To: References: <98a90c220701241313o32f38048ic97bb144eb43cc19@mail.gmail.com> Message-ID: <98a90c220701242254t32305d14ka77277b53cecc283@mail.gmail.com> Thanks for your emails. I looked around sourceforge, and it seems that there are requests for this patches, and people are working on it. Tom On 1/24/07, Brad Knowles wrote: > > At 1:13 PM -0800 1/24/07, Tom Kavanaugh wrote: > > > Making these Project Managers as list moderators does not give them > access > > to add/delete users. > > Is there a way to give them this access. I do not want to make them > list > > admin's. > > Not in the current code, no. > > You can have site admins, who can do anything on any list anywhere on > the site, by using the site admin password. You can also use the > site admin password to create lists, or you can have a separate list > creation password. > > Then you have list admins, and then list moderators. There aren't > any other levels of list administration personnel. > > > Like a lower level of list admin, where they cannot change any list > > parameter. But, just be able to add/remove users. > > You could change the source code. I don't know how hard that would > be to do, but there are others on this list who might be able to give > you some guidance there. > > Keep in mind that there may already be patches to do this sort of > thing. You should look at the SourceForge patch list for Mailman, to > see if there is anything that addresses your question. > > If there is not already an existing patch to achieve this > functionality, then one thing we'd ask you to do is that once you've > made the necessary code changes at your site to then share those with > the rest of the community via the same patch facility. > > -- > Brad Knowles , Consultant & Author > Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and > Responsibilities" > Founding Member and Platinum Individual Sponsor of LOPSA: > > Papers: LinkedIn Profile: > > From kencheney at yahoo.com Thu Jan 25 17:50:55 2007 From: kencheney at yahoo.com (Ken Cheney) Date: Thu, 25 Jan 2007 08:50:55 -0800 (PST) Subject: [Mailman-Users] Lists nested in other lists Message-ID: <789852.84738.qm@web53208.mail.yahoo.com> I know I have seen some documentation on being able to have lists nested in other lists. I can't seem to locate it now. What I want to do is have someone subscribe to a list such as - hockey player - and by virtue of subscribing to that list they are part of the Athletics list. So they will then receive messages sent to both the Athletics list and the Hockey Player lists. Is this possible? --------------------------------- Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. From pdbogen at gmail.com Thu Jan 25 18:38:52 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 25 Jan 2007 11:38:52 -0600 Subject: [Mailman-Users] Lists nested in other lists In-Reply-To: <789852.84738.qm@web53208.mail.yahoo.com> References: <789852.84738.qm@web53208.mail.yahoo.com> Message-ID: <6fbe3da00701250938m2efa233ev24edeae621077a4f@mail.gmail.com> On 1/25/07, Ken Cheney wrote: > I know I have seen some documentation on being able to have lists nested in other lists. I can't seem to locate it now. > > What I want to do is have someone subscribe to a list such as - hockey player - and by virtue of subscribing to that list they are part of the Athletics list. > > So they will then receive messages sent to both the Athletics list and the Hockey Player lists. What you're looking for are "umbrella lists". Basically, the 'hockey players list' is a member of the 'Athletics' list. There are some options to help with this, such as setting the Athletics list not to send password reminders (since the password reminder would go to all of the hockey players list. -- - Patrick Bogen From sascha.kaempf at arcor.de Thu Jan 25 15:51:27 2007 From: sascha.kaempf at arcor.de (sascha.kaempf at arcor.de) Date: Thu, 25 Jan 2007 15:51:27 +0100 (CET) Subject: [Mailman-Users] Problems Exim: Child process of mailman_transport transport returned 2 Message-ID: <23544969.1169736687835.JavaMail.ngmail@webmail17> Hi list, I have just installed Mailman and run into a problem i can not understand: 2007-01-25 15:47:41 1HA5t7-0005Xc-Gb ** listname at myserver R=mailman_router T=mailman_transport: Child process of mailman_transport transport returned 2 from command: /usr/local/mailman/mail/mailman Mails can not be delivery to Mailman. I?m using Mailman 2.1.9 in combination with Exim 4.63. The problem has been, that the mail-gid was different, than what Mailman expected: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "mail", but the system's mail server executed the mail script as group "root". Try tweaking the mail server to run the script as group "mail", or re-run configure, providing the command line option `--with-mail-gid=root'. So I did a make clean followed by: ./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=root i also tried ./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=0 followed by make install. Both should work, no ? h1055564:/tmp/mailman-2.1.9# cat /etc/group | grep root root:x:0: Once done I stopped Exim & mailmanctl and started both applications again. Still, I receive the error mentioned above but I can not find any mistake: h1055564:/tmp/mailman-2.1.9# /usr/local/mailman/bin/check_perms -f Keine Probleme aufgetreten h1055564:/tmp/mailman-2.1.9# /usr/local/mailman/mail/mailman post post script got no listname. Any idea? Perhaps it is a stupid error I?ve just overlooked but I run out of ideas -;( Regards Sascha From ptomblin at xcski.com Thu Jan 25 20:45:53 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Thu, 25 Jan 2007 14:45:53 -0500 Subject: [Mailman-Users] Problems Exim: Child process of mailman_transport transport returned 2 In-Reply-To: <23544969.1169736687835.JavaMail.ngmail@webmail17> References: <23544969.1169736687835.JavaMail.ngmail@webmail17> Message-ID: <20070125194553.GA6217@allhats.xcski.com> Quoting sascha.kaempf at arcor.de (sascha.kaempf at arcor.de): > group "root". Try tweaking the mail server to run the > script as group "mail", or re-run configure, > providing the command line option `--with-mail-gid=root'. ^^^^^^^^^^^^^^^^^^^^ > > So I did a make clean followed by: > > ./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=root ^^^^^^^^^^^^^^^^^^^^ > i also tried > ./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=0 > followed by make install. > > Both should work, no ? Read the error message again. It told you to use "--with-mail-gid=root" and you turned around and ran it with "--with-mail-gid=mail". How could you possibly expect that to work? Although if mail is operating with gid "root", your mail server is seriously badly configured. -- Paul Tomblin http://blog.xcski.com/ "Power corrupts. Powerpoint corrupts absolutely." - Vint Cerf From msapiro at value.net Thu Jan 25 20:56:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 25 Jan 2007 11:56:47 -0800 Subject: [Mailman-Users] Problems Exim: Child process of mailman_transporttransport returned 2 In-Reply-To: <23544969.1169736687835.JavaMail.ngmail@webmail17> Message-ID: sascha.kaempf at arcor.de wrote: > >The problem has been, that the mail-gid was different, than what Mailman expected: > >Group mismatch error. Mailman expected the mail >wrapper script to be executed as group "mail", but >the system's mail server executed the mail script as >group "root". Try tweaking the mail server to run the >script as group "mail", or re-run configure, >providing the command line option `--with-mail-gid=root'. > >So I did a make clean followed by: > >./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=root >i also tried >./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=0 >followed by make install. > >Both should work, no ? No. You can configure with ./configure --with-mail-gid=root --with-cgi-gid=www-data (i.e., don't just add --with-mail-gid=root; you also have to remove --with-mail-gid=mail) or you can put group = mail in the mailman-transport in your Exim configuration. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at bronze.lostwells.net Fri Jan 26 00:14:45 2007 From: vancleef at bronze.lostwells.net (Hank van Cleef) Date: Thu, 25 Jan 2007 16:14:45 -0700 (MST) Subject: [Mailman-Users] Mailman log rotation Message-ID: <200701252314.l0PNEj4E019792@bronze.lostwells.net> I want to put the Mailman logs into the Solaris logadm.conf file for automatic cron rotation. This moves the old logfiles to logfiles.0 and touches new logfiles. I'm assuming that the qrunners have to be restarted. Anything else? Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From msapiro at value.net Fri Jan 26 01:02:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 25 Jan 2007 16:02:17 -0800 Subject: [Mailman-Users] Mailman log rotation In-Reply-To: <200701252314.l0PNEj4E019792@bronze.lostwells.net> Message-ID: Hank van Cleef wrote: >I want to put the Mailman logs into the Solaris logadm.conf file >for automatic cron rotation. > >This moves the old logfiles to logfiles.0 and touches new logfiles. >I'm assuming that the qrunners have to be restarted. Anything else? Qrunners don't need to be restarted, just log files reopened /path/to/bin/mailmanctl reopen That should be sufficient. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From sascha.kaempf at arcor.de Fri Jan 26 08:51:24 2007 From: sascha.kaempf at arcor.de (sascha.kaempf at arcor.de) Date: Fri, 26 Jan 2007 08:51:24 +0100 (CET) Subject: [Mailman-Users] Problems Exim: Child process of mailman_transporttransport returned 2 In-Reply-To: References: Message-ID: <27116130.1169797884754.JavaMail.ngmail@webmail18> Hi, > >./configure --with-mail-gid=mail --with-cgi-gid=www-data > --with-mail-gid=root > >i also tried > >./configure --with-mail-gid=mail --with-cgi-gid=www-data --with-mail-gid=0 > >followed by make install. > > > >Both should work, no ? > > No. You can configure with > > ./configure --with-mail-gid=root --with-cgi-gid=www-data > > (i.e., don't just add --with-mail-gid=root; you also have to remove > --with-mail-gid=mail) or you can put Okay, did that make clean ./configure --with-mail-gid=root --with-cgi-gid=www-data make install Stop & Start MTA and Mailman but sill: Child process of mailman_transport transport returned 2 from command: /usr/local/mailman/mail/mailman > group = mail > > in the mailman-transport in your Exim configuration. Did this as well: Changed the group to mail, stopped and started exim and then make clean ./configure --with-mail-gid=mail --with-cgi-gid=www-data make install Stop and Start Mailman but still Child process of mailman_transport transport returned 2 from command: /usr/local/mailman/mail/mailman I?m running out of ideas ;( Kind regards Sascha From jacob at metaroar.com Fri Jan 26 14:30:57 2007 From: jacob at metaroar.com (Jacob Sam-La Rose) Date: Fri, 26 Jan 2007 13:30:57 +0000 Subject: [Mailman-Users] List name stripped from subject header - how to prevent/workaround this? Message-ID: <422888EA-958B-4855-87FF-CD042E48E779@metaroar.com> (just realised my last message didn't have a subject... Doh!) Hi there, I've recently configured a mailman mailing list. Among other things, I've been thrown by the fact that any time I mention the name of the list in the "subject:" of an email, it gets stripped. The public name for the list is FYI, the prefix for the subject line is FYI - and if I write FYI anywhere in the subject line, it's automatically removed. I don't often mention the name of the list, but it'd be good to know what to do if I need to. Thanks, Jacob.// From jacob at metaroar.com Fri Jan 26 14:10:54 2007 From: jacob at metaroar.com (Jacob Sam-La Rose) Date: Fri, 26 Jan 2007 13:10:54 +0000 Subject: [Mailman-Users] (no subject) Message-ID: <1DDB48A3-39AB-4683-B821-A2C8BCCF7590@metaroar.com> Hi there, I've recently configured a mailman mailing list. Among other things, I've been thrown by the fact that any time I mention the name of the list in the "subject:" of an email, it gets stripped. The public name for the list is FYI, the prefix for the subject line is FYI - and if I write FYI anywhere in the subject line, it's automatically removed. I don't often mention the name of the list, but it'd be good to know what to do if I need to. Thanks, Jacob.// From jacob at metaroar.com Fri Jan 26 15:24:34 2007 From: jacob at metaroar.com (Jacob Sam-La Rose) Date: Fri, 26 Jan 2007 14:24:34 +0000 Subject: [Mailman-Users] List security: approved line got mailed out to list users Message-ID: <192C574B-A1EF-4BE9-B010-260B62C9399C@metaroar.com> Hi. I've got my list configured as an announcement-only list, and the first few mailings I've sent have gone through exactly as planned. I use "Approved: password" as the first line to approve mailings. I inadvertently sent email to the list from one of my other email addresses, and when the message went out, the Approved: line was there, intact. There was a space above it, if that means anything (the sent email doesn't have that space...) I changed the password - easily done, no security problems there. But I'd still like to know what could have allowed this to happen. Since then, I've set up a test list and tried to replicate the behaviour - thus far no success. Anyone have any suggestions as to what might have happened? Thanks, Jacob Sam-La Rose Executive Editor "FYI" / Metaroar.com From vancleef at lostwells.net Fri Jan 26 15:33:03 2007 From: vancleef at lostwells.net (Hank van Cleef) Date: Fri, 26 Jan 2007 07:33:03 -0700 (MST) Subject: [Mailman-Users] Mailman log rotation In-Reply-To: Message-ID: <200701261433.l0QEX3YC004680@bronze.lostwells.net> The esteemed Mark Sapiro has said: > > Hank van Cleef wrote: > > >I want to put the Mailman logs into the Solaris logadm.conf file > >for automatic cron rotation. > > > >This moves the old logfiles to logfiles.0 and touches new logfiles. > >I'm assuming that the qrunners have to be restarted. Anything else? > > > Qrunners don't need to be restarted, just log files reopened > > /path/to/bin/mailmanctl reopen > > That should be sufficient. > Thanks much, Mark. I used the "mailmanctl reopen" in the /etc/logadm.conf file (with the full paths to everything---mandatory for cron jobs) and let cron do its thing. This morning, the logs are rotated and writing happily. Hank -- Hank van Cleef (vancleef at lostwells.net, hvanclee at nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" From robertj at linux4free.com Fri Jan 26 18:12:10 2007 From: robertj at linux4free.com (Rob Jackson) Date: Fri, 26 Jan 2007 10:12:10 -0700 Subject: [Mailman-Users] Expiration on moderated requests Message-ID: <200701261712.l0QHC28b019260@resources.rootsweb.com> I am looking into a way to expire any moderated requests that are older than 2 weeks. Has this been discussed before? -Rob From ki at knifecenter.com Fri Jan 26 18:31:49 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 12:31:49 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications Message-ID: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? From alan at patriot.net Fri Jan 26 19:45:36 2007 From: alan at patriot.net (Alan McConnell) Date: Fri, 26 Jan 2007 13:45:36 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: References: Message-ID: <20070126184536.GA2636@patriot.net> On Fri, Jan 26, 2007 at 12:31:49PM -0500, Ki Song wrote: > Every subscription/unsubscription notification is sent twice to the admin's > email address. > How can I make sure only 1 notification is sent? What mailman version are you using? I have exactly this problem, and the sysadmins my E-list is running on are running 2.1.5, which people here have deprecated. Alan -- Alan McConnell : http://patriot.net/users/alan There are many good Impeachment sites; one of the best is: www.waifllc.org From msapiro at value.net Fri Jan 26 20:00:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 11:00:14 -0800 Subject: [Mailman-Users] List security: approved line got mailed out to listusers In-Reply-To: <192C574B-A1EF-4BE9-B010-260B62C9399C@metaroar.com> Message-ID: Jacob Sam-La Rose wrote: > >I've got my list configured as an announcement-only list, and the >first few mailings I've sent have gone through exactly as planned. I >use "Approved: password" as the first line to approve mailings. I >inadvertently sent email to the list from one of my other email >addresses, and when the message went out, the Approved: line was >there, intact. There was a space above it, if that means anything >(the sent email doesn't have that space...) What Mailman version is this? Do you have a copy of the message from the list - complete with all headers? If nothing else, if the list is archived, this copy will be in archives/private/listname.mbox/listname.mbox. How did the message get sent to the list? Was it held and manually approved (a clue that something was wrong with Approved:). Was the Approved: line that went to the list in the first text/plain part of the message or was it in a subsequent part, e.g. an HTML alternative part. Approved: body lines must be the first non-blank line in the first text/plain part of the message. If found there, they will be removed. Beginning in Mailman 2.1.7, an attempt is made to remove the approved line from other parts of the message, but it must first be found in the first text/plain part, and this removal from other parts isn't perfect. So, based on what little I have to go on so far, I will guess that the message you sent to the list was multipart/alternative with text/plain and text/html alternative parts and the Approved: line was found in and removed from the text/plain part and the message was accepted, but either because this is Mailman prior to 2.1.7 or because of something unusual about the way the Approved: line appeared in the html part, it wasn't removed from that part and that's where people saw it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ptomblin at xcski.com Fri Jan 26 20:02:45 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Fri, 26 Jan 2007 14:02:45 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: <20070126184536.GA2636@patriot.net> References: <20070126184536.GA2636@patriot.net> Message-ID: <20070126190245.GB30385@allhats.xcski.com> Quoting Alan McConnell (alan at patriot.net): > On Fri, Jan 26, 2007 at 12:31:49PM -0500, Ki Song wrote: > > Every subscription/unsubscription notification is sent twice to the admin's > > email address. > > How can I make sure only 1 notification is sent? > What mailman version are you using? I have exactly this problem, > and the sysadmins my E-list is running on are running 2.1.5, which > people here have deprecated. I don't think it's anything to do with 2.1.5 - I'm running the same and don't get duplicates. -- Paul Tomblin http://blog.xcski.com/ "Tech Services - We Aim To Please, We Shoot To Kill" -- H. Wade Minter, ASR From ki at knifecenter.com Fri Jan 26 18:55:04 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 12:55:04 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications Message-ID: Every subscription/unsubscription notification is sent twice to the admin's email address. How can I make sure only 1 notification is sent? From dragon at crimson-dragon.com Fri Jan 26 20:20:03 2007 From: dragon at crimson-dragon.com (Dragon) Date: Fri, 26 Jan 2007 11:20:03 -0800 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: References: Message-ID: <7.0.1.0.2.20070126111709.05cd3d60@crimson-dragon.com> Ki Song wrote: >Every subscription/unsubscription notification is sent twice to the admin's >email address. >How can I make sure only 1 notification is sent? ---------------- End original message. --------------------- Are you certain of that? It could be that the admin has a filter rule in place that duplicates the mail and makes it look like it is sent twice. If it is indeed being sent twice, I would expect the messages to have different message IDs, the time sent may or may not be different. If the message IDs are the same on both copies, I would strongly suspect you are getting bit by a filter rule and Mailman is doing the right thing. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From msapiro at value.net Fri Jan 26 21:04:04 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 12:04:04 -0800 Subject: [Mailman-Users] Problems Exim: Child process ofmailman_transporttransport returned 2 In-Reply-To: <27116130.1169797884754.JavaMail.ngmail@webmail18> Message-ID: sascha.kaempf at arcor.de wrote: > >make clean >./configure --with-mail-gid=root --with-cgi-gid=www-data >make install >Stop & Start MTA and Mailman > >but sill: > >Child process of mailman_transport transport returned 2 from command: /usr/= >local/mailman/mail/mailman And what does the error message say about 'expected' and 'got' group? >> group = mail >> >> in the mailman-transport in your Exim configuration. > >Did this as well: Changed the group to mail, stopped and started exim and then Did you also put an appropriate 'user ='? >make clean >./configure --with-mail-gid=mail --with-cgi-gid=www-data >make install >Stop and Start Mailman but still > >Child process of mailman_transport transport returned 2 from command: /usr/local/mailman/mail/mailman And what did the error message say about 'expected' and 'got' group here? Also, see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jan 26 21:31:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 12:31:27 -0800 Subject: [Mailman-Users] Expiration on moderated requests In-Reply-To: <200701261712.l0QHC28b019260@resources.rootsweb.com> Message-ID: Rob Jackson wrote: >I am looking into a way to expire any moderated requests that are older than >2 weeks. If your Mailman is 2.1.6 or later, set max_days_to_hold to 14. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ki at knifecenter.com Fri Jan 26 21:33:45 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 15:33:45 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: <7.0.1.0.2.20070126111709.05cd3d60@crimson-dragon.com> Message-ID: >> Every subscription/unsubscription notification is sent twice to the admin's >> email address. >> How can I make sure only 1 notification is sent? > ---------------- End original message. --------------------- > > Are you certain of that? > > It could be that the admin has a filter rule in place that duplicates > the mail and makes it look like it is sent twice. > > If it is indeed being sent twice, I would expect the messages to have > different message IDs, the time sent may or may not be different. If > the message IDs are the same on both copies, I would strongly suspect > you are getting bit by a filter rule and Mailman is doing the right thing. > > Dragon > I am certain it is the EXACT same message. How do I know this? The message ID's for the duplicate emails are exactly the same: Message-ID: Could this be a postfix issue? I don't think so ... because my other, regular messages, are being sent without duplicates. From julia_frizzell at brown.edu Fri Jan 26 21:35:26 2007 From: julia_frizzell at brown.edu (Julia Frizzell) Date: Fri, 26 Jan 2007 15:35:26 -0500 Subject: [Mailman-Users] Problem with explicit destination Message-ID: We have a few lists configured to accept all mail addressed to them, mainly as they are email addresses on our website set for people to make inquiries at. We have the lists configured to use explicit destination, and reject anything that is not explicity sent to the list address. However, some mail still gets through. For example, this came in: > To: But we're not alliancecoatings.com Are the spammers forging list headers to allow the message to go through? If so, is there a way around this? We're running Mailman 2.1.5 on Mac OS X 10.4 server. --- Julia Frizzell Systems Administrator/Help Desk Manager The Education Alliance 222 Richmond Street, Suite 300 Providence, Rhode Island 02903-4226 julia_frizzell at brown.edu 401.274.9548 x311 or 800.521.9550 x311 401.421.7650 (fax) http://www.alliance.brown.edu From wo_shi_big_stomach at mac.com Fri Jan 26 21:11:30 2007 From: wo_shi_big_stomach at mac.com (wo_shi_big_stomach) Date: Fri, 26 Jan 2007 12:11:30 -0800 Subject: [Mailman-Users] apache22 DocumenRoot Message-ID: <45BA6072.8050708@mac.com> Greetings. I'm relatively new to Apache2 and even newer to Mailman. On FreeBSD 6.1, I installed Apache 2.2 and Mailman from ports. By default, Apache's DocumentRoot is: /usr/local/www/apache22/data Mailman installs into: /usr/local/mailman My question: In the Apache httpd.conf file, what's the appropriate path so users see Mailman? I thought of symlinking /usr/local/mailman under the DocumentRoot, but I'm concerned about security implications of that. What's the best way to set this up? thanks! /wsbs From msapiro at value.net Fri Jan 26 21:44:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 12:44:14 -0800 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: Ki Song quoted Dragon and wrote: >> >> It could be that the admin has a filter rule in place that duplicates >> the mail and makes it look like it is sent twice. >I am certain it is the EXACT same message. >How do I know this? >The message ID's for the duplicate emails are exactly the same: > >Message-ID: OK. It is the same message. Did you check the filter rules in your email client as Dragon suggests to be sure that they are not responsible for duplicating the message? Also, What is the contents of the list's owner and moderator attributes. Are you or something that forwards to you listed twice? Also, check for that Message-ID in Mailman's 'smtp' log and see how many recipients it was sent to. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Fri Jan 26 21:46:35 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 26 Jan 2007 14:46:35 -0600 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: References: Message-ID: At 3:33 PM -0500 1/26/07, Ki Song wrote: > I am certain it is the EXACT same message. > How do I know this? > The message ID's for the duplicate emails are exactly the same: Just because the message-ids are exactly the same doesn't mean that this problem wasn't caused by filter rules. Check your queue-ids. That will tell you where the duplication is occurring. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From msapiro at value.net Fri Jan 26 21:53:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 12:53:39 -0800 Subject: [Mailman-Users] Problem with explicit destination In-Reply-To: Message-ID: Julia Frizzell wrote: > >However, some mail still gets through. For example, this came in: > >> To: > >But we're not alliancecoatings.com What about Cc:? If your list's require_explicit_destination is set to Yes, a post should be held if the list posting address or an address in the list's acceptable_aliases does not appear in a To: or Cc: header of the post. The only thing that would bypass this is an Approved: header with the list's admin or moderator password. If posts are not being held in your case, please provide Mailman version, settings for require_explicit_destination and acceptable_aliases, and the complete headers of the post, and we'll try to figure it out. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jan 26 21:55:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 12:55:51 -0800 Subject: [Mailman-Users] apache22 DocumenRoot In-Reply-To: <45BA6072.8050708@mac.com> Message-ID: wo_shi_big_stomach wrote: > >My question: In the Apache httpd.conf file, what's the appropriate > path so users see Mailman? See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From julia_frizzell at brown.edu Fri Jan 26 22:06:44 2007 From: julia_frizzell at brown.edu (Julia Frizzell) Date: Fri, 26 Jan 2007 16:06:44 -0500 Subject: [Mailman-Users] Problem with explicit destination In-Reply-To: References: Message-ID: <48B679A0-042B-4FF5-A5B9-6992B8A81D7A@brown.edu> Just got one in right now, so let's use this one. I've replaced our @address with @xxx. As far as I can see, there's no cc in here. As i said in my original message, we're running Mailman 2.1.5 on OS X 10.4. We have set require_explicit_destination to Yes and acceptable_aliases is blank. From: public_relations at planar.com Subject: [Publications] Most popular Date: January 26, 2007 3:52:27 PM EST To: publications at accessola.com Received: from ex-gateway1-in.AD.Brown.Edu ([128.148.21.51]) by mail1.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:53:03 -0500 Received: from draco.services.brown.edu ([128.148.106.172]) by ex- gateway1-in.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 15:52:38 -0500 Received: from list.alliance.brown.edu (list.alliance.brown.edu [128.148.108.6]) by draco.services.brown.edu (Switch-3.1.10/ Switch-3.1.7/) with ESMTP id l0QKqcNZ027652; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from list.alliance.brown.edu (localhost [127.0.0.1]) by list.alliance.brown.edu (Postfix) with ESMTP id 3B13B1AB177; Fri, 26 Jan 2007 15:52:38 -0500 (EST) Received: from cpe-69-203-99-40.nyc.res.rr.com (cpe-69-203-99-40.nyc.res.rr.com [69.203.99.40]) by list.alliance.brown.edu (Postfix) with ESMTP id 1E7581AB153 for ; Fri, 26 Jan 2007 15:52:36 -0500 (EST) Received: from [70.34.194.185] (HELO JKDJPUF) by 69.203.99.40 (CommuniGate Pro SMTP 5.0.11) with SMTP id 40033759 for publications at accessola.com; Fri, 26 Jan 2007 15:52:27 -0500 X-Original-To: publications at xxx Delivered-To: publications at xxx Message-Id: <020501c7418b$e3c1b190 $2863cb45 at cpe692039940.nyc.res.rr.com> Mime-Version: 1.0 X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Beenthere: publications at xxx X-Mailman-Version: 2.1.5 Precedence: list Content-Type: multipart/mixed; boundary="===============1298335293==" Sender: publications-bounces at xxx Errors-To: publications-bounces at xxx X-Brown-Proofpoint: Not Infected X-Proofpoint-Spam-Reason: safe Return-Path: publications-bounces at xxx X-Originalarrivaltime: 26 Jan 2007 20:53:03.0635 (UTC) FILETIME= [F8F40630:01C7418B] On Jan 26, 2007, at 3:53 PM, Mark Sapiro wrote: > Julia Frizzell wrote: >> >> However, some mail still gets through. For example, this came in: >> >>> To: >> >> But we're not alliancecoatings.com > > > What about Cc:? > > If your list's require_explicit_destination is set to Yes, a post > should be held if the list posting address or an address in the list's > acceptable_aliases does not appear in a To: or Cc: header of the post. > > The only thing that would bypass this is an Approved: header with the > list's admin or moderator password. > > If posts are not being held in your case, please provide Mailman > version, settings for require_explicit_destination and > acceptable_aliases, and the complete headers of the post, and we'll > try to figure it out. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > From ki at knifecenter.com Fri Jan 26 22:07:08 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 16:07:08 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: >>> It could be that the admin has a filter rule in place that duplicates >>> the mail and makes it look like it is sent twice. > >> I am certain it is the EXACT same message. >> How do I know this? >> The message ID's for the duplicate emails are exactly the same: >> >> Message-ID: > > > OK. It is the same message. Did you check the filter rules in your > email client as Dragon suggests to be sure that they are not > responsible for duplicating the message? > I checked the filter rules. I could not find anything that could possibly duplicate messages. There is only one reference to the messages that are being duplicated (the filter/rule looks for where the message is being SENT to) > Also, What is the contents of the list's owner and moderator > attributes. Are you or something that forwards to you listed twice? > Where could I find these attributes? Is it on the web admin interface, or is it somewhere else? > Also, check for that Message-ID in Mailman's 'smtp' log and see how > many recipients it was sent to. The message-ID from mailman's smtp log shows something interesting. Every message that is duplicated, shows the same message-ID, but it says that it is being sent to 2 recipients. Is that normal? I ask because as far as I know, these subscribe messages are being sent to me, the administrator, and the actual email that is being subscribed/unsubscribed. Is that normal, or would it be two different message-ID's, if only 1 message was being sent to me and 1 message was being sent to the email address that is being subscribed/unsubscribed? From dragon at crimson-dragon.com Fri Jan 26 22:18:36 2007 From: dragon at crimson-dragon.com (Dragon) Date: Fri, 26 Jan 2007 13:18:36 -0800 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: References: <7.0.1.0.2.20070126111709.05cd3d60@crimson-dragon.com> Message-ID: <7.0.1.0.2.20070126131643.0595ba20@crimson-dragon.com> Ki Song wrote: > >> Every subscription/unsubscription notification is sent twice to > the admin's > >> email address. > >> How can I make sure only 1 notification is sent? > > ---------------- End original message. --------------------- > > > > Are you certain of that? > > > > It could be that the admin has a filter rule in place that duplicates > > the mail and makes it look like it is sent twice. > > > > If it is indeed being sent twice, I would expect the messages to have > > different message IDs, the time sent may or may not be different. If > > the message IDs are the same on both copies, I would strongly suspect > > you are getting bit by a filter rule and Mailman is doing the right thing. > > > > Dragon > > >I am certain it is the EXACT same message. >How do I know this? >The message ID's for the duplicate emails are exactly the same: > >Message-ID: > > >Could this be a postfix issue? I don't think so ... because my other, >regular messages, are being sent without duplicates. ---------------- End original message. --------------------- OK, so it is probably NOT mailman causing this. Which is what I said earlier. There is a very slim possibility of it being a configuration issue with Postfix but I doubt it. It's almost certain to be a MUA filter issue instead of an MTA issue. Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From msapiro at value.net Fri Jan 26 22:21:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 13:21:02 -0800 Subject: [Mailman-Users] List name stripped from subject header - how toprevent/workaround this? In-Reply-To: <422888EA-958B-4855-87FF-CD042E48E779@metaroar.com> Message-ID: Jacob Sam-La Rose wrote: > >I've recently configured a mailman mailing list. Among other things, >I've been thrown by the fact that any time I mention the name of the >list in the "subject:" of an email, it gets stripped. The public >name for the list is FYI, the prefix for the subject line is FYI - >and if I write FYI anywhere in the subject line, it's automatically >removed. I don't often mention the name of the list, but it'd be >good to know what to do if I need to. Multiple occurrences of subject_prefix in the subject are replaced with just one occurrence at the beginning of the subject to prevent 'build up' in replies. If you configure subject_prefix with brackets (e.g. [FYI]) as is conventionally done for prefixes, unbracketed FYI should not be removed. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jan 26 22:36:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 13:36:35 -0800 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: Ki Song quoted Mark Sapiro and wrote: > >> Also, What is the contents of the list's owner and moderator >> attributes. Are you or something that forwards to you listed twice? >> >Where could I find these attributes? Is it on the web admin interface, or is >it somewhere else? Web admin, General options. >> Also, check for that Message-ID in Mailman's 'smtp' log and see how >> many recipients it was sent to. > >The message-ID from mailman's smtp log shows something interesting. Every >message that is duplicated, shows the same message-ID, but it says that it >is being sent to 2 recipients. Is that normal? It is normal if the total number of addresses in the 'owner' and 'moderator' lists is two. >I ask because as far as I >know, these subscribe messages are being sent to me, the administrator, and >the actual email that is being subscribed/unsubscribed. Is that normal, or >would it be two different message-ID's, if only 1 message was being sent to >me and 1 message was being sent to the email address that is being >subscribed/unsubscribed? The owner notice and the user notice are different messages with different Message-IDs. Note that some notifications such as held message notifications are sent twice and have two smtp log entries. The first send has one recipient which is the list's -owner address, and this is followed by the resend to the owners and moderators. This is not the case for (un)subscribe notices however. Subscribe and unsubscribe owner notices are sent directly to the owners and moderators without going through the -owner address. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ki at knifecenter.com Fri Jan 26 22:37:19 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 16:37:19 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: >>>> It could be that the admin has a filter rule in place that duplicates >>>> the mail and makes it look like it is sent twice. >> >>> I am certain it is the EXACT same message. >>> How do I know this? >>> The message ID's for the duplicate emails are exactly the same: >>> >>> Message-ID: >> >> >> OK. It is the same message. Did you check the filter rules in your >> email client as Dragon suggests to be sure that they are not >> responsible for duplicating the message? >> > I checked the filter rules. I could not find anything that could possibly > duplicate messages. There is only one reference to the messages that are > being duplicated (the filter/rule looks for where the message is being SENT > to) > >> Also, What is the contents of the list's owner and moderator >> attributes. Are you or something that forwards to you listed twice? >> > Where could I find these attributes? Is it on the web admin interface, or is > it somewhere else? > >> Also, check for that Message-ID in Mailman's 'smtp' log and see how >> many recipients it was sent to. > > The message-ID from mailman's smtp log shows something interesting. Every > message that is duplicated, shows the same message-ID, but it says that it > is being sent to 2 recipients. Is that normal? I ask because as far as I > know, these subscribe messages are being sent to me, the administrator, and > the actual email that is being subscribed/unsubscribed. Is that normal, or > would it be two different message-ID's, if only 1 message was being sent to > me and 1 message was being sent to the email address that is being > subscribed/unsubscribed? One thing I do notice is that the administrator and moderator addresses listed in the GENERAL OPTIONS web admin page of each list is the same address (newsletter at knifecenter.com). Further below, on that same page, there is an option that says, "Should the administrator get notices of subscribes and unsubscribes?" I have that checked to YES. Could it be that because the administrator and moderator addresses are the same (newsletter at knifecenter.com) and because the administrator is getting notices of subscribes and unsubscribes, that the message is being sent twice? I'm assuming the moderator gets notices of subscribes/unsubscribes automatically. Let me check. (It may take a while ... because there are a couple hundred/thousand subscribe/unsubscribe messages in queue. From alan at patriot.net Fri Jan 26 22:41:37 2007 From: alan at patriot.net (Alan McConnell) Date: Fri, 26 Jan 2007 16:41:37 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: References: Message-ID: <20070126214137.GD3294@patriot.net> On Fri, Jan 26, 2007 at 02:46:35PM -0600, Brad Knowles wrote: > At 3:33 PM -0500 1/26/07, Ki Song wrote: > > > I am certain it is the EXACT same message. > > How do I know this? > > The message ID's for the duplicate emails are exactly the same: > > Just because the message-ids are exactly the same doesn't mean that > this problem wasn't caused by filter rules. The filter list on my E-list seem pretty simple. > Check your queue-ids. That will tell you where the duplication is occurring. What are "queue-ids"? Are they something that a mailman admin can see? I have no access to any log files; they are available only to the sys-admins of my ISP. Alan -- Alan McConnell : http://patriot.net/users/alan There are many good Impeachment sites; one of the best is: www.waifllc.org From msapiro at value.net Fri Jan 26 22:55:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 13:55:27 -0800 Subject: [Mailman-Users] Problem with explicit destination In-Reply-To: <48B679A0-042B-4FF5-A5B9-6992B8A81D7A@brown.edu> Message-ID: Julia Frizzell wrote: >Just got one in right now, so let's use this one. I've replaced our >@address with @xxx. > >As far as I can see, there's no cc in here. As i said in my original >message, we're running Mailman 2.1.5 on OS X 10.4. We have set >require_explicit_destination to Yes and acceptable_aliases is blank. If this is the Apple OS X Server Mailman, it may have modifications that make it behave differently from standard Mailman. > From: public_relations at planar.com > Subject: [Publications] Most popular > Date: January 26, 2007 3:52:27 PM EST > To: publications at accessola.com Where are you seeing the above headers? This appears to be some MUA's rendering of the message, not the raw message headers. In a raw message, the above headers would not precede the Received: headers. Do you have access to the global mailbox in the list's archive? It is the file archives/private/listname.mbox/listname.mbox. If you don't have direct access to the file, you may have a link to it on the list's archive table of contents page, and even if not, you may be able to access it via a URL like http://example.com/mailman/private/listname.mbox/listname.mbox. What are the headers of this message in that file? > Received: from ex-gateway1-in.AD.Brown.Edu ([128.148.21.51]) by >mail1.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan >2007 15:53:03 -0500 > Received: from draco.services.brown.edu ([128.148.106.172]) by ex- >gateway1-in.AD.Brown.Edu with Microsoft SMTPSVC(6.0.3790.1830); Fri, >26 Jan 2007 15:52:38 -0500 > Received: from list.alliance.brown.edu (list.alliance.brown.edu >[128.148.108.6]) by draco.services.brown.edu (Switch-3.1.10/ >Switch-3.1.7/) with ESMTP id l0QKqcNZ027652; Fri, 26 Jan 2007 >15:52:38 -0500 (EST) > Received: from list.alliance.brown.edu (localhost [127.0.0.1]) by >list.alliance.brown.edu (Postfix) with ESMTP id 3B13B1AB177; Fri, 26 >Jan 2007 15:52:38 -0500 (EST) > Received: from cpe-69-203-99-40.nyc.res.rr.com >(cpe-69-203-99-40.nyc.res.rr.com [69.203.99.40]) by >list.alliance.brown.edu (Postfix) with ESMTP id 1E7581AB153 for >; Fri, 26 Jan 2007 15:52:36 -0500 (EST) > Received: from [70.34.194.185] (HELO JKDJPUF) by 69.203.99.40 >(CommuniGate Pro SMTP 5.0.11) with SMTP id 40033759 for >publications at accessola.com; Fri, 26 Jan 2007 15:52:27 -0500 > X-Original-To: publications at xxx > Delivered-To: publications at xxx > Message-Id: <020501c7418b$e3c1b190 >$2863cb45 at cpe692039940.nyc.res.rr.com> > Mime-Version: 1.0 > X-Priority: 3 > X-Msmail-Priority: Normal > X-Mailer: Microsoft Outlook Express 6.00.2900.2869 > X-Mimeole: Produced By Microsoft MimeOLE V6.00.2900.2962 > X-Beenthere: publications at xxx > X-Mailman-Version: 2.1.5 > Precedence: list > Content-Type: multipart/mixed; boundary="===============1298335293==" > Sender: publications-bounces at xxx > Errors-To: publications-bounces at xxx > X-Brown-Proofpoint: Not Infected > X-Proofpoint-Spam-Reason: safe > Return-Path: publications-bounces at xxx > X-Originalarrivaltime: 26 Jan 2007 20:53:03.0635 (UTC) FILETIME= >[F8F40630:01C7418B] The rest of these headers look like those from a raw message, but since the first few were moved, I can't be sure what else may have been altered. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jan 26 23:10:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 14:10:59 -0800 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: Ki Song wrote: > >One thing I do notice is that the administrator and moderator addresses >listed in the GENERAL OPTIONS web admin page of each list is the same >address (newsletter at knifecenter.com). Bingo! >Further below, on that same page, there is an option that says, "Should the >administrator get notices of subscribes and unsubscribes?" I have that >checked to YES. This causes the notice to be sent. This particular notice is sent to both the owners and the moderators. You are listed twice - you get it twice. Some (very few, I don't remember which offhand) notices are sent to owner only. Most are sent to owner and moderator. None are sent to moderator only. Thus it makes no sense to list an address as both owner and moderator and only results in duplicate notices. See and for more information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ki at knifecenter.com Fri Jan 26 23:22:49 2007 From: ki at knifecenter.com (Ki Song) Date: Fri, 26 Jan 2007 17:22:49 -0500 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: Message-ID: >>> OK. It is the same message. Did you check the filter rules in your >>> email client as Dragon suggests to be sure that they are not >>> responsible for duplicating the message? >>> >> I checked the filter rules. I could not find anything that could possibly >> duplicate messages. There is only one reference to the messages that are >> being duplicated (the filter/rule looks for where the message is being SENT >> to) >> >>> Also, What is the contents of the list's owner and moderator >>> attributes. Are you or something that forwards to you listed twice? >>> >> Where could I find these attributes? Is it on the web admin interface, or is >> it somewhere else? >> >>> Also, check for that Message-ID in Mailman's 'smtp' log and see how >>> many recipients it was sent to. >> >> The message-ID from mailman's smtp log shows something interesting. Every >> message that is duplicated, shows the same message-ID, but it says that it >> is being sent to 2 recipients. Is that normal? I ask because as far as I >> know, these subscribe messages are being sent to me, the administrator, and >> the actual email that is being subscribed/unsubscribed. Is that normal, or >> would it be two different message-ID's, if only 1 message was being sent to >> me and 1 message was being sent to the email address that is being >> subscribed/unsubscribed? > > > One thing I do notice is that the administrator and moderator addresses > listed in the GENERAL OPTIONS web admin page of each list is the same > address (newsletter at knifecenter.com). > Further below, on that same page, there is an option that says, "Should the > administrator get notices of subscribes and unsubscribes?" I have that > checked to YES. > > Could it be that because the administrator and moderator addresses are the > same (newsletter at knifecenter.com) and because the administrator is getting > notices of subscribes and unsubscribes, that the message is being sent > twice? I'm assuming the moderator gets notices of subscribes/unsubscribes > automatically. > > Let me check. (It may take a while ... because there are a couple > hundred/thousand subscribe/unsubscribe messages in queue. > That's what it was. From chandler.lists at chapman.edu Fri Jan 26 23:00:46 2007 From: chandler.lists at chapman.edu (Jay Chandler) Date: Fri, 26 Jan 2007 14:00:46 -0800 Subject: [Mailman-Users] Group Mismatch Error Message-ID: <45BA7A0E.7060302@chapman.edu> Time for this old chestnut again, but with a bit of a twist. Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. Attempted to send a test message to my list. ommand died with status 2: "/usr/local/mailman/mail/mailman post netoplist". Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group "nobody", but the system's mail server executed the mail script as group "mailman". Try tweaking the mail server to run the script as group "nobody", or re-run configure, providing the command line option `--with-mail-gid=mailman'. Yet... mybox# ll total 38 -rw-r----- 1 root mailman 41 Jan 26 13:33 adm.pw -rw-rw---- 1 mailman mailman 1995 Jan 26 13:36 aliases -rw-rw---- 1 mailman mailman 16384 Jan 26 13:36 aliases.db -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version -rw-rw---- 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg Is there something blindingly obvious that I'm missing? -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler at chapman.edu Today's Excuse: Just pick up the phone and give modem connect sounds. "Well you said we should get more lines so we don't have voice lines." From jacob at metaroar.com Fri Jan 26 23:59:27 2007 From: jacob at metaroar.com (Jacob Sam-La Rose) Date: Fri, 26 Jan 2007 22:59:27 +0000 Subject: [Mailman-Users] List security: approved line got mailed out to listusers In-Reply-To: References: Message-ID: Thanks for the response, Mark. I'm only just getting used to the concept of community via mailing list (I'm more used to user forums...!) On 26 Jan 2007, at 19:00, Mark Sapiro wrote: > Jacob Sam-La Rose wrote: >> >> I've got my list configured as an announcement-only list, and the >> first few mailings I've sent have gone through exactly as planned. I >> use "Approved: password" as the first line to approve mailings. I >> inadvertently sent email to the list from one of my other email >> addresses, and when the message went out, the Approved: line was >> there, intact. There was a space above it, if that means anything >> (the sent email doesn't have that space...) > > > What Mailman version is this? > 2.1.9.cp2 > Do you have a copy of the message from the list - complete with all > headers? If nothing else, if the list is archived, this copy will be > in archives/private/listname.mbox/listname.mbox. Headers: Subject: FYI (important): any email to / Jacob this morning... Date: 26 January 2007 11:00:05 GMT To: fyi at metaroar.com Return-Path: Envelope-To: jacob at jsamlarose.com Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 Received: from yosafa by mrfriendly.asmallorange.com with local- bsmtp (Exim 4.63) (envelope-from ) id 1HAOrV-0000z6-3K for jacob at jsamlarose.com; Fri, 26 Jan 2007 06:03:20 -0500 Received: from hypnotoad.liquidweb.com ([72.52.133.24]:50358) by mrfriendly.asmallorange.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1HAOrU-0000xz-PZ for jacob at jsamlarose.com; Fri, 26 Jan 2007 06:03:16 -0500 Received: from localhost ([127.0.0.1]:50149 helo=hypnotoad.liquidweb.com) by hypnotoad.liquidweb.com with esmtp (Exim 4.63) (envelope-from ) id 1HAOoT-00032t-0j; Fri, 26 Jan 2007 06:00:09 -0500 Received: from [81.103.209.178] (port=56306) by hypnotoad.liquidweb.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1HAOoR-00032U-85 for fyi at metaroar.com; Fri, 26 Jan 2007 06:00:07 -0500 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mrfriendly.asmallorange.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=AWL,HTML_MESSAGE autolearn=ham version=3.1.7 Mime-Version: 1.0 (Apple Message framework v752.2) Message-Id: <68175EC0-1B93-4673-AD2D-2188F7E0DE29 at metaroar.com> X-Mailer: Apple Mail (2.752.2) X-Clamantivirus-Scanner: This mail is clean X-Clamantivirus-Scanner: This mail is clean X-Beenthere: fyi at metaroar.com X-Mailman-Version: 2.1.9.cp2 Precedence: list List-Id: "Everything you wanted to know about poetry, but didn't know who to ask..." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2746362320716674074==" Errors-To: fyi-bounces at metaroar.com X-Antiabuse: This header was added to track abuse, please include it with any abuse report X-Antiabuse: Primary Hostname - hypnotoad.liquidweb.com X-Antiabuse: Original Domain - jsamlarose.com X-Antiabuse: Originator/Caller UID/GID - [0 0] / [47 12] X-Antiabuse: Sender Address Domain - metaroar.com X-Source: X-Source-Args: X-Source-Dir: X-Antivirus-Scanner: Clean mail though you should still use an Antivirus Do you need to see the body of the email? > > How did the message get sent to the list? Was it held and manually > approved (a clue that something was wrong with Approved:). Sent as email straight to the list - didn't have to be manually approved - it went straight through. > > Was the Approved: line that went to the list in the first text/plain > part of the message or was it in a subsequent part, e.g. an HTML > alternative part. It was in the first text/plain part - though in the sent version I've got of the mail, the Approved: line is the very first line. Once it went through the list, there was a line space at the top of the email, before the Approved: line... > > Approved: body lines must be the first non-blank line in the first > text/plain part of the message. If found there, they will be removed. > Beginning in Mailman 2.1.7, an attempt is made to remove the approved > line from other parts of the message, but it must first be found in > the first text/plain part, and this removal from other parts isn't > perfect. > > So, based on what little I have to go on so far, I will guess that the > message you sent to the list was multipart/alternative with text/plain > and text/html alternative parts and the Approved: line was found in > and removed from the text/plain part and the message was accepted, but > either because this is Mailman prior to 2.1.7 or because of something > unusual about the way the Approved: line appeared in the html part, it > wasn't removed from that part and that's where people saw it. Headers say multipart/mixed... Anything else this could be? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > Jacob Sam-La Rose Executive Editor "FYI" / Metaroar.com From brad at shub-internet.org Sat Jan 27 01:52:57 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 26 Jan 2007 18:52:57 -0600 Subject: [Mailman-Users] Duplicate Subscribe/Unsubscribe Notifications In-Reply-To: <20070126214137.GD3294@patriot.net> References: <20070126214137.GD3294@patriot.net> Message-ID: At 4:41 PM -0500 1/26/07, Alan McConnell wrote: >> Check your queue-ids. That will tell you where the duplication is >> occurring. > > What are "queue-ids"? Are they something that a mailman admin > can see? I have no access to any log files; they are available > only to the sys-admins of my ISP. The queue-ids are typically shown in the contents of the various "Received:" headers on each message. They would also show up in the system logs for the mail server. These logs may only be accessible to your mail server administrator -- they are outside of Mailman, and unfortunately not even the internal Mailman logs are available via the web. For example, on the message I am responding to, this is a sample of the "Received:" headers I found: Received: from bag.python.org (bag [127.0.0.1]) by bag.python.org (Postfix) with ESMTP id 943801E4011 for ; Fri, 26 Jan 2007 22:42:32 +0100 (CET) Received: from bag (HELO bag.python.org) (127.0.0.1) by bag.python.org with SMTP; 26 Jan 2007 22:42:32 +0100 Received: from jefferson.patriot.net (jefferson.patriot.net [209.249.176.3]) by bag.python.org (Postfix) with ESMTP for ; Fri, 26 Jan 2007 22:42:31 +0100 (CET) Received: from patriot.net (postfix at pool180-173.patriot.net [209.249.180.173]) by jefferson.patriot.net (8.13.4/8.13.4/Debian-3sarge3) with ESMTP id l0QLgPrM022931; Fri, 26 Jan 2007 16:42:29 -0500 Received: by patriot.net (Postfix, from userid 500) id 8ABEC47587; Fri, 26 Jan 2007 16:41:37 -0500 (EST) In each case, where it says "id 8ABEC47587" or "with ESMTP id l0QLgPrM022931", or something like that, the ids it is referring to are called "queue ids". If you are looking at the system log for the mail services on a given server, the only way you can typically tie in a given log entry to a given message is through the queue-ids. Looking in the system log file for postfix on this machine, the entries relevant to queue-id 943801E4011 are: Jan 26 22:42:32 bag postfix/smtpd[27954]: 943801E4011: client=bag[127.0.0.1] Jan 26 22:42:32 bag postfix/cleanup[28483]: 943801E4011: message-id=<20070126214137.GD3294 at patriot.net> Jan 26 22:42:32 bag postfix/qmgr[27081]: 943801E4011: from=, size=2239, nrcpt=1 (queue active) Jan 26 22:42:32 bag postfix/local[28226]: 943801E4011: to=, orig_to=, relay=local, delay=0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post mailman-users) Jan 26 22:42:32 bag postfix/qmgr[27081]: 943801E4011: removed You see the message-id here once, but all the other log entries relative to this particular event are logged with only the date and the queue-id, as well as whatever other information was being logged. So, you need the queue-id in order to be able to tie them all together. Now, these are not the only log entries for this message. Because of the way the mail server on this machine is configured, it actually handles each message three times -- once on inbound (before scanning for spam and viruses), once on inbound (after scanning), and again after the message has gone through Mailman and is being sent out. So, if we look for other log entries relative to this message-id, we find that we have to look at 992 different queue-ids, one for each of the subscribers on the outbound side, plus one on inbound (before scanning) and another on inbound (after scanning). I'll spare you and not even show you the complete list of all the queue-ids in question, and of course I'd never show you the complete set of all those log entries. Anyway, my point is this -- if you look at the headers of two messages that appear to be identical, you can look at the "Received:" headers to see if they really are identical. If each and every queue-id in both messages are exactly the same, then there must have been some sort of duplication that occurred within your mail client or somewhere else outside of the normal SMTP Message Transfer Agent system. If the queue-ids are identical up to a point but they diverge after that point, that tells you exactly where the message was somehow duplicated. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From brad at shub-internet.org Sat Jan 27 01:56:27 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 26 Jan 2007 18:56:27 -0600 Subject: [Mailman-Users] List security: approved line got mailed out to listusers In-Reply-To: References: Message-ID: At 10:59 PM +0000 1/26/07, Jacob Sam-La Rose wrote: >> What Mailman version is this? > >2.1.9.cp2 That's a cPanel version number. Please see FAQ 6.11. >> Do you have a copy of the message from the list - complete with all >> headers? If nothing else, if the list is archived, this copy will be >> in archives/private/listname.mbox/listname.mbox. > > Headers: > > Subject: FYI (important): any email to / Jacob this morning... > Date: 26 January 2007 11:00:05 GMT > To: fyi at metaroar.com > Return-Path: > Envelope-To: jacob at jsamlarose.com > Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 > Received: from yosafa by mrfriendly.asmallorange.com with Something has munged the heck out of these headers. In the raw mbox file, there are no preceding space characters before any of them. We want to see what is in the raw mbox file, not anything else. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From msapiro at value.net Sat Jan 27 02:33:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 17:33:49 -0800 Subject: [Mailman-Users] Group Mismatch Error In-Reply-To: <45BA7A0E.7060302@chapman.edu> Message-ID: Jay Chandler wrote: > >Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. > >Attempted to send a test message to my list. > >ommand died with status 2: "/usr/local/mailman/mail/mailman post > netoplist". Command output: Group mismatch error. Mailman expected the > mail wrapper script to be executed as group "nobody", but the system's mail > server executed the mail script as group "mailman". Try tweaking the mail > server to run the script as group "nobody", or re-run configure, providing > the command line option `--with-mail-gid=mailman'. > > >Yet... >mybox# ll >total 38 >-rw-r----- 1 root mailman 41 Jan 26 13:33 adm.pw >-rw-rw---- 1 mailman mailman 1995 Jan 26 13:36 aliases >-rw-rw---- 1 mailman mailman 16384 Jan 26 13:36 aliases.db >-rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version >-rw-rw---- 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid >-rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg > >Is there something blindingly obvious that I'm missing? Maybe. Where did the netoptlist alias come from. Did Postfix find the alias somewhere else (maybe /etc/aliases*) either before or instead of Mailman's data/aliases*? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From chandler.lists at chapman.edu Sat Jan 27 02:36:40 2007 From: chandler.lists at chapman.edu (Jay Chandler) Date: Fri, 26 Jan 2007 17:36:40 -0800 Subject: [Mailman-Users] Group Mismatch Error In-Reply-To: References: Message-ID: <45BAACA8.5080800@chapman.edu> Mark Sapiro wrote: > Jay Chandler wrote: > >> Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. >> >> Attempted to send a test message to my list. >> >> ommand died with status 2: "/usr/local/mailman/mail/mailman post >> netoplist". Command output: Group mismatch error. Mailman expected the >> mail wrapper script to be executed as group "nobody", but the system's mail >> server executed the mail script as group "mailman". Try tweaking the mail >> server to run the script as group "nobody", or re-run configure, providing >> the command line option `--with-mail-gid=mailman'. >> >> >> Yet... >> mybox# ll >> total 38 >> -rw-r----- 1 root mailman 41 Jan 26 13:33 adm.pw >> -rw-rw---- 1 mailman mailman 1995 Jan 26 13:36 aliases >> -rw-rw---- 1 mailman mailman 16384 Jan 26 13:36 aliases.db >> -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version >> -rw-rw---- 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid >> -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg >> >> Is there something blindingly obvious that I'm missing? >> > > > Maybe. Where did the netoptlist alias come from. Did Postfix find the > alias somewhere else (maybe /etc/aliases*) either before or instead of > Mailman's data/aliases*? > > Nope-- I created that myself as a test list. The other aliases file is owned by root:wheel. -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / chandler at chapman.edu Today's Excuse: Just pick up the phone and give modem connect sounds. "Well you said we should get more lines so we don't have voice lines." From kelly.terry.jones at gmail.com Sat Jan 27 02:47:23 2007 From: kelly.terry.jones at gmail.com (Kelly Jones) Date: Fri, 26 Jan 2007 18:47:23 -0700 Subject: [Mailman-Users] Finding the recipients for a given archived email Message-ID: <26face530701261747n22e7576bhdd39299baea4efbc@mail.gmail.com> I have a mailing list whose membership changes frequently. I want to find out who received a two-month-old email in the archives. In other words, I want to know the list membership at the time that message was sent. How can I do this? I realize I could look at sendmail logs (if they went back that far), but is there an "pure Mailman" way to do this? I believe (not sure) that the vette(?) log keeps track of subscribes/unsubscribes, so I could theoretically reconstruct the list, starting with the current membership and working backward. Is this possible? Is there an easier way? -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. From msapiro at value.net Sat Jan 27 03:13:39 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 18:13:39 -0800 Subject: [Mailman-Users] List security: approved line got mailed out to listusers In-Reply-To: Message-ID: Jacob Sam-La Rose wrote: > >Headers: > >Subject: FYI (important): any email to / Jacob this morning... > Date: 26 January 2007 11:00:05 GMT > To: fyi at metaroar.com As Brad points out in another reply, these don't look like raw message headers for a few reasons, not the least of which being Subject:, Date: and To: preceeding the headers immediately below. > Return-Path: > Envelope-To: jacob at jsamlarose.com > Delivery-Date: Fri, 26 Jan 2007 06:03:20 -0500 > Received: from yosafa by mrfriendly.asmallorange.com with local- >bsmtp (Exim 4.63) (envelope-from >) id 1HAOrV-0000z6-3K for >jacob at jsamlarose.com; Fri, 26 Jan 2007 06:03:20 -0500 > Received: from hypnotoad.liquidweb.com ([72.52.133.24]:50358) by >mrfriendly.asmallorange.com with esmtps (TLSv1:AES256-SHA:256) (Exim >4.63) (envelope-from ) id 1HAOrU-0000xz-PZ >for jacob at jsamlarose.com; Fri, 26 Jan 2007 06:03:16 -0500 > Received: from localhost ([127.0.0.1]:50149 >helo=hypnotoad.liquidweb.com) by hypnotoad.liquidweb.com with esmtp >(Exim 4.63) (envelope-from ) id >1HAOoT-00032t-0j; Fri, 26 Jan 2007 06:00:09 -0500 > Received: from [81.103.209.178] (port=56306) by >hypnotoad.liquidweb.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim >4.63) (envelope-from ) id 1HAOoR-00032U-85 for >fyi at metaroar.com; Fri, 26 Jan 2007 06:00:07 -0500 > X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on >mrfriendly.asmallorange.com > X-Spam-Level: > X-Spam-Status: No, score=0.0 required=7.0 tests=AWL,HTML_MESSAGE >autolearn=ham version=3.1.7 > Mime-Version: 1.0 (Apple Message framework v752.2) > Message-Id: <68175EC0-1B93-4673-AD2D-2188F7E0DE29 at metaroar.com> > X-Mailer: Apple Mail (2.752.2) > X-Clamantivirus-Scanner: This mail is clean > X-Clamantivirus-Scanner: This mail is clean > X-Beenthere: fyi at metaroar.com > X-Mailman-Version: 2.1.9.cp2 > Precedence: list > List-Id: "Everything you wanted to know about poetry, but didn't >know who to ask..." > List-Unsubscribe: fyi_metaroar.com>, > List-Archive: > List-Post: > List-Help: > List-Subscribe: fyi_metaroar.com>, > Content-Type: multipart/mixed; >boundary="===============2746362320716674074==" The multipart/mixed structure is probably due to Mailman's adding either msg_header or msg_footer or both as separate MIME parts, thus, by itself this doesn't tell me much about the original message. > Errors-To: fyi-bounces at metaroar.com > X-Antiabuse: This header was added to track abuse, please include >it with any abuse report > X-Antiabuse: Primary Hostname - hypnotoad.liquidweb.com > X-Antiabuse: Original Domain - jsamlarose.com > X-Antiabuse: Originator/Caller UID/GID - [0 0] / [47 12] > X-Antiabuse: Sender Address Domain - metaroar.com > X-Source: > X-Source-Args: > X-Source-Dir: > X-Antivirus-Scanner: Clean mail though you should still use an >Antivirus > >Do you need to see the body of the email? I need to see the mime structure of the message including the part headers and at least the initial lines of the part that still has the Approved: line in it, and I need to see this as a raw message, not interpreted by some MUA. >> How did the message get sent to the list? Was it held and manually >> approved (a clue that something was wrong with Approved:). > >Sent as email straight to the list - didn't have to be manually >approved - it went straight through. > >> >> Was the Approved: line that went to the list in the first text/plain >> part of the message or was it in a subsequent part, e.g. an HTML >> alternative part. > >It was in the first text/plain part - though in the sent version I've >got of the mail, the Approved: line is the very first line. Once it >went through the list, there was a line space at the top of the >email, before the Approved: line... Assuming that the message actually needed to be approved, the line would have been removed at least from the first text/plain part. If you are able to get that 'sent version' in its raw form, that would be most useful. You appear to be using Apple mail. You can view raw source via View->Message->Raw source (option-command-U). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 27 03:25:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 18:25:27 -0800 Subject: [Mailman-Users] Group Mismatch Error In-Reply-To: <45BAACA8.5080800@chapman.edu> Message-ID: Jay Chandler wrote: >Mark Sapiro wrote: >> Jay Chandler wrote: >> >>> Postfix (latest stable), FreeBSD 6.2, latest version of Mailman. >>> >>> Attempted to send a test message to my list. >>> >>> ommand died with status 2: "/usr/local/mailman/mail/mailman post >>> netoplist". Command output: Group mismatch error. Mailman expected the >>> mail wrapper script to be executed as group "nobody", but the system's mail >>> server executed the mail script as group "mailman". Try tweaking the mail >>> server to run the script as group "nobody", or re-run configure, providing >>> the command line option `--with-mail-gid=mailman'. >>> >>> >>> Yet... >>> mybox# ll >>> total 38 >>> -rw-r----- 1 root mailman 41 Jan 26 13:33 adm.pw >>> -rw-rw---- 1 mailman mailman 1995 Jan 26 13:36 aliases >>> -rw-rw---- 1 mailman mailman 16384 Jan 26 13:36 aliases.db >>> -rw-r--r-- 1 root mailman 10 Jan 8 10:32 last_mailman_version >>> -rw-rw---- 1 mailman mailman 6 Jan 26 11:13 master-qrunner.pid >>> -rw-r--r-- 1 root mailman 14114 Jan 8 10:32 sitelist.cfg >>> >>> Is there something blindingly obvious that I'm missing? >>> >> >> >> Maybe. Where did the netoptlist alias come from. Did Postfix find the >> alias somewhere else (maybe /etc/aliases*) either before or instead of >> Mailman's data/aliases*? >> >> >Nope-- I created that myself as a test list. > >The other aliases file is owned by root:wheel. My mistake, I got it backwards. Postfix is executing the wrapper as mailman:mailman, the owner:group of the aliases. Mailman's wrapper is expecting group 'nobody'. You can't change the owner:group of the aliases or list creation won't be able to update them. This means you need to reconfigure the wrapper to expect group 'mailman' instead of 'nobody'. There is probably some FreeBSD port magic way to do this, but I don't know what it is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jan 27 03:41:13 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 26 Jan 2007 18:41:13 -0800 Subject: [Mailman-Users] Finding the recipients for a given archived email In-Reply-To: <26face530701261747n22e7576bhdd39299baea4efbc@mail.gmail.com> Message-ID: Kelly Jones wrote: >I have a mailing list whose membership changes frequently. I want to >find out who received a two-month-old email in the archives. In other >words, I want to know the list membership at the time that message was >sent. I'm assuming you don't care about regular vs digest which you can't track because changes aren't logged. >I believe (not sure) that the vette(?) log keeps track of >subscribes/unsubscribes, so I could theoretically reconstruct the >list, starting with the current membership and working backward. Is >this possible? Is there an easier way? It's the subscribe log, but yes you can get the subscribes and unsubscribes and work backwards. Address changes currently aren't logged (they will be in 2.2), but that may not be significant for your purpose. No, I don't know an easier way unless you have a backup somewhere of the list's config.pck from the date of interest. If you do, you could use bin/dumpdb to get the information. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pmatulis at sympatico.ca Mon Jan 29 04:27:17 2007 From: pmatulis at sympatico.ca (Peter Matulis) Date: Sun, 28 Jan 2007 22:27:17 -0500 Subject: [Mailman-Users] migrating Mailman server Message-ID: <200701282227.17267.pmatulis@sympatico.ca> I have the task of setting up a replacement for an existing Mailman/Postfix server. I am new to Mailman and I am looking for some guidance in this transition. Mailman is currently being used solely as a diffusion of information. That is, it does not accept contributions from list members (read-only). Firstly, should I attempt to migrate data/files over to the new system or should I start fresh? The new system will be running OpenBSD 4.0. Other comments welcome. Peter From vanhorn at whidbey.com Mon Jan 29 11:07:33 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Mon, 29 Jan 2007 02:07:33 -0800 Subject: [Mailman-Users] Moving lists Message-ID: <45BDC765.3050004@whidbey.com> My old Mailman host died a while back, and I'm finally getting around to getting the new one running again. Before I shut off the old host I tarred up the old files and have them on the new server. I just moved the components from the old archives and lists directories into the new locations, and when I go to http://.com/mailman/admin/ I get the front page, but all the links are to the old server. At that point I moved /usr/local/mailman/lists/ to /usr/local/mailman/lists/.bak and created the list fresh with the newlist command. But when I went in to the admin page I discovered that there were no members of the list, and when I went to the archive the messages were all there, but the "more information about this list" link was back to the old server again. So, where do I dig up the membership list, and how do I deal with all the old URLs? Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From vancleef at lostwells.net Mon Jan 29 16:11:33 2007 From: vancleef at lostwells.net (vancleef at lostwells.net) Date: Mon, 29 Jan 2007 08:11:33 -0700 (MST) Subject: [Mailman-Users] migrating Mailman server In-Reply-To: <200701282227.17267.pmatulis@sympatico.ca> Message-ID: <200701291511.l0TFBXFs026380@julie.lostwells.net> > > I have the task of setting up a replacement for an existing > Mailman/Postfix server. I am new to Mailman and I am looking for some > guidance in this transition. Mailman is currently being used solely as > a diffusion of information. That is, it does not accept contributions > from list members (read-only). > > Firstly, should I attempt to migrate data/files over to the new system > or should I start fresh? > > The new system will be running OpenBSD 4.0. > I have just moved a 9-year-old list from another installation to mine, and have a draft how-to faq on how I did it that isn't quite ready for prime time. Since I know there isn't any clear information on this in the current mailman FAQ tree, I'll give the salient points fairly briefly. I'm sure that the Mailman developers will want to comment, so I'll let them do the talking after posting this. It's fairly easy to do a seamless migration of an old Mailman list's personality and history into a new Mailman install. Based on a migration from Mailman 2.1.4 to 2.1.9, what you need from the old installation are: (base directory is the old mailman tree, typically /usr/local/mailman) 1. All of the files under the ./lists/ directory. 2. All of the files under the ./archives/private/ directory. 3. ./Mailman/mm_cfg.py 4. Any other files in the ./archives directory with in their names. A tar of those directory trees plus the mm_cfg.py file gives you the old list's configuration, personality, membership data base, and archives. On your new system, do a new installation of Mailman at the revision level that the old list was running on. I was moving from a 2.1.4 installation, and building from source, so had to get the Mailman 2.1.4 sources. Follow the instructions in the build and installation guide on the Mailman web site exactly (don't plan on just running configure and doing a make---there is a lot more you need to do). On the fresh installation, create a new list with the same name as the one you are moving. For example, if you're moving from "waffles at wafflehaus.org," create a new "waffles" list. Use that newly-created list to check out your installation. You can add a few local list member names to convenient mail addresses on your site, and use this to check out the integration with your mailer and web server. Use the old list's mm_cfg.py as a guide in chosing what to put in your installation's mm_cfg.py. Once you have your installation running, take a look in the ./list/. You'll find config.pck. Check its owner/group and permissions. Copy the old list's config.pck file into the new installation's directory and set its owner/group and permissions to match. Run the fix_url script as needed to get the correct URL for your new installation installed. If there are html files in the old list's list/ directory (template file overlays), copy them over as well. You should now be able to go to the listinfo page for the list, go into the mailman administrator options page, and review such things as the administrator/moderator addresses and settings, list mailto address, etc. Double check that the link-across URL's between pages are correct for your installation. Populate the archives directories. I still haven't worked out the best way for doing this, but you'll need the pipermail archives directories and files, and control files that the old Mailman created. The ./bin/check_perms script will help you getting all the owner/group and permissions set properly (Mailman is quite fussy about these). You should now have your old list completely installed on your new site. From there, you can build the current versions of Python (2.5), Mailman (2.1.9) and do an upgrade installation. Hank From pdbogen at gmail.com Mon Jan 29 16:31:19 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Mon, 29 Jan 2007 09:31:19 -0600 Subject: [Mailman-Users] Moving lists In-Reply-To: <45BDC765.3050004@whidbey.com> References: <45BDC765.3050004@whidbey.com> Message-ID: <6fbe3da00701290731x62593e84yfb1e742b37e01a8d@mail.gmail.com> On 1/29/07, G. Armour Van Horn wrote: > So, where do I dig up the membership list, and how do I deal with all > the old URLs? FAQ 3.4 should help with this. Let us know if you still have issues. -- - Patrick Bogen From mjnf at uevora.pt Mon Jan 29 16:57:37 2007 From: mjnf at uevora.pt (Mario Filipe) Date: Mon, 29 Jan 2007 15:57:37 +0000 Subject: [Mailman-Users] questions related to batch creation and management of several lists Message-ID: <45BE1971.8010909@uevora.pt> Hi I'm using mailman 2.1.9-4 on a Debian Sarge server. I need to create a batch of lists for the management of each of our institutional units (departments, services, etc.) Apart from the members and the name, the setup is very similar for all of them so I looked at the FAQ and I'm wondering if I can use the answer number 4.38 (quoted below) as a solution ? Q: I am the site administrator and I'd like to change the configuration of ALL existing lists. How to do that? A: Use /usr/lib/mailman/bin/config_list Here's an example: 1. Login your shell 2. Create a file (/path/to/configfile) and add your configuration *) 3. Change the configuration using this shell script: for i in $(/usr/lib/mailman/bin/list_lists -b) ; do /usr/lib/mailman/bin/config_list -i /path/to/configfile $i ; done If you only want to change some lists but not all, replace the for i in $(/usr/lib/mailman/bin/list_lists -b) in the above script with for example for i in list1 list2 list3 To check for errors before doing the changes, you can simulate your changes using the -c flag. see: config_list --help My other question is related to the way these lists are to be used: - they are to be directly addressable, meaning that anyone (not everyone we don't need more SPAM) can send a message to them - they are also to be used under umbrella lists and here is my problem because some people are in more than one of those lists and under the umbrella lists they are going to get multiple copies of the messages, right? Is there a way to prevent this? Thanks -- Mario Filipe Servi?o de Computa??o da Universidade de ?vora mjnf at uevora.pt http://home.uevora.pt/~mjnf/ From zbyszek at szalbot.homedns.org Mon Jan 29 17:22:09 2007 From: zbyszek at szalbot.homedns.org (Zbigniew Szalbot) Date: Mon, 29 Jan 2007 17:22:09 +0100 (CET) Subject: [Mailman-Users] performance differences between limited and full personalization Message-ID: <62863.192.168.11.7.1170087729.squirrel@lists.lc-words.com> Dear friends, I have a question about possible performance differences between limited and full personalization in mailman 2.1.9. That is, I set up full personalization for two lists that I have (they are more like for sending newsletters than for discussion). Anyway, I wonder whether I would have any gain in terms of performance if I switched from full to limited personalization. I read the description but it does not say anything about this issue. There's only comparison between personalization as such and no personalization at all. In other words, do I gain anything from changing from full to limited personalization? I like when people recieving our newsletters do not have to guess the email they were subscribed with but if it should help, I would switch from full to limited and place their emails in the email footer. Warm regards, -- Zbigniew Szalbot From reis.orlando at gmail.com Mon Jan 29 17:23:55 2007 From: reis.orlando at gmail.com (Orlando Reis) Date: Mon, 29 Jan 2007 16:23:55 +0000 Subject: [Mailman-Users] Moving lists between virtual domains. Message-ID: <474f4b810701290823g4c3678a1w64f9004159ef4dc7@mail.gmail.com> Hi all, athough this question as been posted in the past and I have searched and searched the mailing list I haven't found a simple a and clear solution to the problem. I have my default mailman URL at www.mainhost.com And have several other vhosts added POSTFIX_STYLE_VIRTUAL_DOMAINS = ['vhost1.org', vhost1.eu' ,'vhost2.org', ' vhost2.eu','vhost3.eu'] #add virtual hosts VIRTUAL_HOSTS.clear() add_virtualhost('www.vhost1.org', 'vhost1.org') add_virtualhost('www.vhost1.eu','vhost1.eu') add_virtualhost('www.vhost2.org', 'vhost2.org') add_virtualhost('www.vhost2.eu','vhost2.eu') add_virtualhost('www.vhost3.eu','vhost3.eu') add_virtualhost('www.mainhost.com','mainhost.com') I have lists on all domains What I wan't to do is move a list from vhost1.org to vhost1.eu. Is there any howto on how to do this. http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.029.htp Is not very excplicit on how to do this, hence I don't think it is the same thing. image that i have the following lists: list_all, list_member, list_workproj1, list_workproj2 If I issue the fix_url command bin/withlist -l -r fix_url list_all --urlhost=http://www.vhost1.eu That will change the url for the list configuration, but I will also have to rebuild the archives? Thanks in advance Orlando From ki at knifecenter.com Mon Jan 29 18:01:17 2007 From: ki at knifecenter.com (Ki Song) Date: Mon, 29 Jan 2007 12:01:17 -0500 Subject: [Mailman-Users] Mailman not working after reboot Message-ID: I recently rebooted my Fedora server. It has a copy of Mailman 2.1.8 installed. I usually have to restart mailman by running mailmanctl after rebooting. 1. How do I add mailmanctl as a program that will run on boot? I don't want to have to run mailmanctl every time I reboot the server. 2. Since the last reboot, I started the mailmanctl program, but it doesn't look like the mailman server is running properly. The web admin pages are running, but it looks like some parts of mailman have not started. Specifically, the subscribe/unsubscribe requests are not being processed. What other processes need to be started in order for mailman to run properly? From ki at knifecenter.com Mon Jan 29 18:17:45 2007 From: ki at knifecenter.com (Ki Song) Date: Mon, 29 Jan 2007 12:17:45 -0500 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: Message-ID: > I recently rebooted my Fedora server. > It has a copy of Mailman 2.1.8 installed. > I usually have to restart mailman by running mailmanctl after rebooting. > > 1. How do I add mailmanctl as a program that will run on boot? I don't want > to have to run mailmanctl every time I reboot the server. > > 2. Since the last reboot, I started the mailmanctl program, but it doesn't > look like the mailman server is running properly. The web admin pages are > running, but it looks like some parts of mailman have not started. > Specifically, the subscribe/unsubscribe requests are not being processed. > What other processes need to be started in order for mailman to run > properly? Nevermind about question 2. I found out that the subscription confirmation email that is being sent to the mailman admin is the only part that was turned off. The actual server is running properly. I still need to know how to make mailman run by default on startup. From dave at hamnet.org Mon Jan 29 18:35:46 2007 From: dave at hamnet.org (Dave Foran) Date: Mon, 29 Jan 2007 12:35:46 -0500 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: Message-ID: Run chkconfig is where the start ups go something like chkconfig -l 345 mailmain It has been a while.. Do man chkconfig DAve > -----Original Message----- > From: mailman-users-bounces+dave=hamnet.org at python.org > [mailto:mailman-users-bounces+dave=hamnet.org at python.org]On Behalf Of Ki > Song > Sent: Monday, January 29, 2007 12:18 > To: mailman-users at python.org > Subject: Re: [Mailman-Users] Mailman not working after reboot > > > > I recently rebooted my Fedora server. > > It has a copy of Mailman 2.1.8 installed. > > I usually have to restart mailman by running mailmanctl after rebooting. > > > > 1. How do I add mailmanctl as a program that will run on boot? > I don't want > > to have to run mailmanctl every time I reboot the server. > > > > 2. Since the last reboot, I started the mailmanctl program, but > it doesn't > > look like the mailman server is running properly. The web admin > pages are > > running, but it looks like some parts of mailman have not started. > > Specifically, the subscribe/unsubscribe requests are not being > processed. > > What other processes need to be started in order for mailman to run > > properly? > > > Nevermind about question 2. I found out that the subscription confirmation > email that is being sent to the mailman admin is the only part that was > turned off. The actual server is running properly. > > I still need to know how to make mailman run by default on startup. > > ------------------------------------------------------ > Mailman-Users mailing list > Mailman-Users at python.org > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: > http://www.mail-archive.com/mailman-users%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-users/dave%40hamnet.org > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From pdbogen at gmail.com Mon Jan 29 18:42:54 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Mon, 29 Jan 2007 11:42:54 -0600 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: References: Message-ID: <6fbe3da00701290942j4775b11cr879c531a84646128@mail.gmail.com> On 1/29/07, Ki Song wrote: > 1. How do I add mailmanctl as a program that will run on boot? I don't want > to have to run mailmanctl every time I reboot the server. This is strictly a Fedora question, not a Mailman question. You'd be best served addressing it to a Fedora mailing list. -- - Patrick Bogen From msapiro at value.net Mon Jan 29 18:52:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 09:52:49 -0800 Subject: [Mailman-Users] questions related to batch creation and managementof several lists In-Reply-To: <45BE1971.8010909@uevora.pt> Message-ID: Mario Filipe wrote: > >Apart from the members and the name, the setup is very similar for all >of them so I looked at the FAQ and I'm wondering if I can use the answer > number 4.38 (quoted below) as a solution ? Yes. Configure one list via the web. Write it's configuration with 'bin/config_list -o'. Remove any list specific stuff - mostly look at the first 6 items. Use the rest as input to 'bin/config_list -i'. See 'bin/config_list --help'. >My other question is related to the way these lists are to be used: > >- they are to be directly addressable, meaning that anyone (not everyone >we don't need more SPAM) can send a message to them > >- they are also to be used under umbrella lists and here is my problem >because some people are in more than one of those lists and under the >umbrella lists they are going to get multiple copies of the messages, >right? Is there a way to prevent this? Not with current Mailman. See for an alternative to umbrella lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jan 29 19:04:46 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 10:04:46 -0800 Subject: [Mailman-Users] Moving lists between virtual domains. In-Reply-To: <474f4b810701290823g4c3678a1w64f9004159ef4dc7@mail.gmail.com> Message-ID: Orlando Reis wrote: >Hi all, athough this question as been posted in the past and I have searched >and searched the mailing list I haven't found a simple a and clear solution >to the problem. > >I have my default mailman URL at www.mainhost.com >And have several other vhosts added > >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['vhost1.org', vhost1.eu' ,'vhost2.org', ' >vhost2.eu','vhost3.eu'] >#add virtual hosts >VIRTUAL_HOSTS.clear() >add_virtualhost('www.vhost1.org', 'vhost1.org') >add_virtualhost('www.vhost1.eu','vhost1.eu') >add_virtualhost('www.vhost2.org', 'vhost2.org') >add_virtualhost('www.vhost2.eu','vhost2.eu') >add_virtualhost('www.vhost3.eu','vhost3.eu') >add_virtualhost('www.mainhost.com','mainhost.com') > >I have lists on all domains > >What I wan't to do is move a list from vhost1.org to vhost1.eu. Is there any >howto on how to do this. You've answered your own question. >image that i have the following lists: list_all, list_member, >list_workproj1, list_workproj2 > >If I issue the fix_url command > >bin/withlist -l -r fix_url list_all --urlhost=http://www.vhost1.eu Actually, it should be bin/withlist -l -r fix_url list_all --urlhost=www.vhost1.eu >That will change the url for the list configuration, but I will also have to >rebuild the archives? Yes, but the only thing in the archives that is 'wrong' is the link to the listinfo page from the table of contents page and the periodic index pages. The table of contents will fix itself when a message is archived and current and new index pages will too. You can fix old index pages manually if it's important, or create some kind of script to do it, or rebuild the entire archive with 'bin/arch --wipe'. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From reis.orlando at gmail.com Mon Jan 29 19:21:54 2007 From: reis.orlando at gmail.com (Orlando Reis) Date: Mon, 29 Jan 2007 18:21:54 +0000 Subject: [Mailman-Users] Moving lists between virtual domains. In-Reply-To: References: <474f4b810701290823g4c3678a1w64f9004159ef4dc7@mail.gmail.com> Message-ID: <474f4b810701291021pd951b2tecb0037d792f06a1@mail.gmail.com> Thanks for you reply mark. I had little time to do it and that was what I did, after doing that for each of the lists I wanted to move, I got several errors. I then remembered, I don't know if that is mandatory, to regenerate virtual-mailman.db using genaliases commmand. so the steps I took per mailing list where: withlist -l -r fix_url listname --urlhost=www.vhost1.eu bin/arch --wipe listname and at the end i did genaliases command and did /etc/init.d/mailman restart And it worked, thanks Mark On 1/29/07, Mark Sapiro wrote: > > Orlando Reis wrote: > > >Hi all, athough this question as been posted in the past and I have > searched > >and searched the mailing list I haven't found a simple a and clear > solution > >to the problem. > > > >I have my default mailman URL at www.mainhost.com > >And have several other vhosts added > > > >POSTFIX_STYLE_VIRTUAL_DOMAINS = ['vhost1.org', vhost1.eu' ,'vhost2.org', > ' > >vhost2.eu','vhost3.eu'] > >#add virtual hosts > >VIRTUAL_HOSTS.clear() > >add_virtualhost('www.vhost1.org', 'vhost1.org') > >add_virtualhost('www.vhost1.eu','vhost1.eu') > >add_virtualhost('www.vhost2.org', 'vhost2.org') > >add_virtualhost('www.vhost2.eu','vhost2.eu') > >add_virtualhost('www.vhost3.eu','vhost3.eu') > >add_virtualhost('www.mainhost.com','mainhost.com') > > > >I have lists on all domains > > > >What I wan't to do is move a list from vhost1.org to vhost1.eu. Is there > any > >howto on how to do this. > > > You've answered your own question. > > > >image that i have the following lists: list_all, list_member, > >list_workproj1, list_workproj2 > > > >If I issue the fix_url command > > > >bin/withlist -l -r fix_url list_all --urlhost=http://www.vhost1.eu > > > Actually, it should be > > bin/withlist -l -r fix_url list_all --urlhost=www.vhost1.eu > > >That will change the url for the list configuration, but I will also have > to > >rebuild the archives? > > > Yes, but the only thing in the archives that is 'wrong' is the link to > the listinfo page from the table of contents page and the periodic > index pages. The table of contents will fix itself when a message is > archived and current and new index pages will too. > > You can fix old index pages manually if it's important, or create some > kind of script to do it, or rebuild the entire archive with 'bin/arch > --wipe'. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From msapiro at value.net Mon Jan 29 19:35:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 10:35:41 -0800 Subject: [Mailman-Users] performance differences between limited and fullpersonalization In-Reply-To: <62863.192.168.11.7.1170087729.squirrel@lists.lc-words.com> Message-ID: Zbigniew Szalbot wrote: > >In other words, do I gain anything from changing from full to limited >personalization? I like when people recieving our newsletters do not have >to guess the email they were subscribed with but if it should help, I >would switch from full to limited and place their emails in the email >footer. With respect to performance, there is no difference between personalize Yes and Full. In either case, each subscriber receives an individualized message (whether or not the messages are in fact different). The performance hit is in sending a separate message to each recipient via a separate SMTP transaction. The actual content of the message and the To: header doesn't matter. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Mon Jan 29 20:04:58 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 29 Jan 2007 13:04:58 -0600 Subject: [Mailman-Users] performance differences between limited and full personalization In-Reply-To: <62863.192.168.11.7.1170087729.squirrel@lists.lc-words.com> References: <62863.192.168.11.7.1170087729.squirrel@lists.lc-words.com> Message-ID: At 5:22 PM +0100 1/29/07, Zbigniew Szalbot wrote: > Anyway, I wonder whether I would have > any gain in terms of performance if I switched from full to limited > personalization. Not really. Either way, the system has to create individual copies of the messages to be sent, and that's the biggest performance hit. > In other words, do I gain anything from changing from full to limited > personalization? I like when people recieving our newsletters do not have > to guess the email they were subscribed with but if it should help, I > would switch from full to limited and place their emails in the email > footer. Full personalization will change the way the headers look. Users will no longer see that the post is addressed to the list, with them getting a copy. They will now see that messages appear to be directly addressed to them by the sender, without any mention of the list. One of these behaviours may be more desirable for your users, who may be confused by the other type of behaviour. It's up to you to decide which makes more sense. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From brad at shub-internet.org Mon Jan 29 20:06:16 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 29 Jan 2007 13:06:16 -0600 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: References: Message-ID: At 12:01 PM -0500 1/29/07, Ki Song wrote: > I recently rebooted my Fedora server. > It has a copy of Mailman 2.1.8 installed. > I usually have to restart mailman by running mailmanctl after rebooting. > > 1. How do I add mailmanctl as a program that will run on boot? I don't want > to have to run mailmanctl every time I reboot the server. That's a Fedora problem. I suggest you use their resources to find the answer to this question. If you have Mailman questions, we should be able to help with those. But we can't provide support for OS-specific issues. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From msapiro at value.net Mon Jan 29 21:37:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 12:37:24 -0800 Subject: [Mailman-Users] migrating Mailman server In-Reply-To: <200701291511.l0TFBXFs026380@julie.lostwells.net> Message-ID: Hank van Cleef wrote: >I have just moved a 9-year-old list from another installation to mine, >and have a draft how-to faq on how I did it that isn't quite ready for >prime time. Since I know there isn't any clear information on this in >the current mailman FAQ tree, I'll give the salient points fairly >briefly. I'm sure that the Mailman developers will want to comment, >so I'll let them do the talking after posting this. I have a few initial remarks interspersed below. >It's fairly easy to do a seamless migration of an old Mailman list's >personality and history into a new Mailman install. Based on a >migration from Mailman 2.1.4 to 2.1.9, what you need from the old >installation are: > >(base directory is the old mailman tree, typically /usr/local/mailman) > >1. All of the files under the ./lists/ directory. >2. All of the files under the ./archives/private/ directory. >3. ./Mailman/mm_cfg.py >4. Any other files in the ./archives directory with in >their names. Depending on how you do archives, you *may* not need 2. You may just need the ./archives/private/.mbox/.mbox files. >A tar of those directory trees plus the mm_cfg.py file gives you the >old list's configuration, personality, membership data base, and >archives. > >On your new system, do a new installation of Mailman at the revision >level that the old list was running on. I was moving from a 2.1.4 >installation, and building from source, so had to get the Mailman >2.1.4 sources. Follow the instructions in the build and installation >guide on the Mailman web site exactly (don't plan on just running >configure and doing a make---there is a lot more you need to do). It should not be necessary to install the "same" version and then upgrade. In this example, it should be OK to just install Mailman 2.1.9 directly on the new system. Mailman is aware enough to update a newly encountered, older version config.pck (or even config.db from 2.0.x) to the current format. A lot of what bin/update does when you update to a new release is stuff that Mailman will do on the fly when you drop an 'old' list into a working Mailman, or it is generic stuff having to do with file locations, queue entry formats and other things not directly relevant to a list. Thus, it is normally just fine to drop a 2.1.4 config.pck into a working 2.1.9 installation. >On the fresh installation, create a new list with the same name as the >one you are moving. For example, if you're moving from >"waffles at wafflehaus.org," create a new "waffles" list. Use that >newly-created list to check out your installation. You can add a few >local list member names to convenient mail addresses on your site, and >use this to check out the integration with your mailer and web server. >Use the old list's mm_cfg.py as a guide in chosing what to put in >your installation's mm_cfg.py. > >Once you have your installation running, take a look in the >./list/. You'll find config.pck. Check its >owner/group and permissions. Copy the old list's config.pck file into >the new installation's directory and set its owner/group and >permissions to match. Run the fix_url script as needed to get the >correct URL for your new installation installed. If there are html >files in the old list's list/ directory (template file >overlays), copy them over as well. > >You should now be able to go to the listinfo page for the list, go >into the mailman administrator options page, and review such things as >the administrator/moderator addresses and settings, list mailto >address, etc. Double check that the link-across URL's between pages >are correct for your installation. > >Populate the archives directories. I still haven't worked out the >best way for doing this, but you'll need the pipermail archives >directories and files, and control files that the old Mailman created. >The ./bin/check_perms script will help you getting all the owner/group >and permissions set properly (Mailman is quite fussy about these). Assuming you have a complete archives/private/.mbox/.mbox from the old installation, you can completely build the pipermail archive on the new installation by the following process. 0) Migrate the list and run fix_url if needed. 1) Copy the archives/private/.mbox/.mbox to the new installation. 2) Run bin/cleanarch -n < archives/private/.mbox/.mbox to help find any unescaped 'From ' lines in the .mbox file. If that finds any problems, run bin/cleanarch < archives/private/.mbox/.mbox > tmp cp tmp archives/private/.mbox/.mbox 3) Run bin/arch --wipe to build the new archive. If the .mbox is large, this may choke in which case, run for example: bin/arch --wipe --end=1000 followed by bin/arch --start=1001 --end=2000 etc. Note --wipe on first bin/arch only. Do not try to run the above in parallel - locks will prevent it anyway. >You should now have your old list completely installed on your new >site. From there, you can build the current versions of Python >(2.5), Mailman (2.1.9) and do an upgrade installation. As I indicate above, it is OK to start with an up-to-date installation and avoid the upgrade step. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vanhorn at whidbey.com Mon Jan 29 22:57:04 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Mon, 29 Jan 2007 13:57:04 -0800 Subject: [Mailman-Users] Moving lists In-Reply-To: <6fbe3da00701290731x62593e84yfb1e742b37e01a8d@mail.gmail.com> References: <45BDC765.3050004@whidbey.com> <6fbe3da00701290731x62593e84yfb1e742b37e01a8d@mail.gmail.com> Message-ID: <45BE6DB0.7080203@whidbey.com> Patrick, The problem with the old server is that it won't accept mail for Mailman. Something about my last attempt to upgrade Mailman there broke it. I'm putting this function on a new server because I just don't have time to figure out the problem on the old one, and the new one has enough horsepower to run the lists along with its other tasks, thus letting me run one less server. However, the same reason I want to move the list means that I can't use the "who command via mail to get the list. Certainly the data is in a file somewhere. Van Patrick Bogen wrote: > On 1/29/07, G. Armour Van Horn wrote: > >> So, where do I dig up the membership list, and how do I deal with all >> the old URLs? > > > FAQ 3.4 > > should help with this. Let us know if you still have issues. > -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From vanhorn at whidbey.com Mon Jan 29 23:27:32 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Mon, 29 Jan 2007 14:27:32 -0800 Subject: [Mailman-Users] Moving lists In-Reply-To: <6fbe3da00701290731x62593e84yfb1e742b37e01a8d@mail.gmail.com> References: <45BDC765.3050004@whidbey.com> <6fbe3da00701290731x62593e84yfb1e742b37e01a8d@mail.gmail.com> Message-ID: <45BE74D4.30300@whidbey.com> A little more digging suggests it may be possible to extract the data with the dumpdb command run against the config.pck. That provides a lot of stuff that isn't needed, like the bounce status of the members which is hardly of interest after the time the server has been offline, but the users and other data seems to all be there. It looks like I could extract the information from that and use the add_members command to add the digest and regular members in two operations, but I probably lose their names and I certainly would lose their passwords. But is there a way to get everything back easily from this data? Van Patrick Bogen wrote: > On 1/29/07, G. Armour Van Horn wrote: > >> So, where do I dig up the membership list, and how do I deal with all >> the old URLs? > > > FAQ 3.4 > > should help with this. Let us know if you still have issues. > -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From msapiro at value.net Mon Jan 29 23:27:48 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 14:27:48 -0800 Subject: [Mailman-Users] Moving lists In-Reply-To: <45BE6DB0.7080203@whidbey.com> Message-ID: G. Armour Van Horn wrote: > >The problem with the old server is that it won't accept mail for >Mailman. Something about my last attempt to upgrade Mailman there broke >it. I'm putting this function on a new server because I just don't have >time to figure out the problem on the old one, and the new one has >enough horsepower to run the lists along with its other tasks, thus >letting me run one less server. > >However, the same reason I want to move the list means that I can't use >the "who command via mail to get the list. Certainly the data >is in a file somewhere. FAQ 3.4 is a hodge podge of obsolete and newer stuff. See the two archive posts linked from the second paragraph of the FAQ. Also see . Basically, if your old list's are down, all you need to do for lists is move the lists//config.pck files and run fix_url if any domain names changed. For archives, you can move the entire archives/private/ structure, or if you want to rebuild the archives, see the post linked above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vanhorn at whidbey.com Tue Jan 30 00:30:17 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Mon, 29 Jan 2007 15:30:17 -0800 Subject: [Mailman-Users] Moving lists In-Reply-To: References: Message-ID: <45BE8389.4030907@whidbey.com> Mark, Thanks. ../../bin/withlist -l -r fix_url worked like a charm. I'm sure there's some cleanup to do, but I'll bet that took care of most of it. Van Mark Sapiro wrote: >G. Armour Van Horn wrote: > > >>The problem with the old server is that it won't accept mail for >>Mailman. Something about my last attempt to upgrade Mailman there broke >>it. I'm putting this function on a new server because I just don't have >>time to figure out the problem on the old one, and the new one has >>enough horsepower to run the lists along with its other tasks, thus >>letting me run one less server. >> >>However, the same reason I want to move the list means that I can't use >>the "who command via mail to get the list. Certainly the data >>is in a file somewhere. >> >> > > >FAQ 3.4 is a hodge podge of obsolete and newer stuff. See the two >archive posts linked from the second paragraph of the FAQ. Also see >. > >Basically, if your old list's are down, all you need to do for lists is >move the lists//config.pck files and run fix_url if any >domain names changed. > >For archives, you can move the entire archives/private/ structure, or >if you want to rebuild the archives, see the post linked above. > > > -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From wo_shi_big_stomach at mac.com Tue Jan 30 00:50:31 2007 From: wo_shi_big_stomach at mac.com (David Newman) Date: Mon, 29 Jan 2007 15:50:31 -0800 Subject: [Mailman-Users] virtual domain setup with postfix Message-ID: MM 2.1.9, Postfix 2.3.5, cyrus-imap 2.3.7, all on FreeBSD 6.1 installed from ports Postfix already handles mail for multiple virtual domains defined in a MySQL database. I believe virtual domain setup is OK, as individual users have been sending and receiving mail for some time. Having problems with Mailman, though. I've read these instructions many times: http://www.list.org/mailman-install/postfix-virtual.html Besides doing what's listed there, I also defined a virtual mailbox for a new "pctest" list (without that, mail sent to pctest at virt1.tld bounces). However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to pctest at virt1.tld; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). Basically, postfix delivers message to pctest at virt1.tld but nothing happens after that. Thanks in advance for clues on fixing this. /wsbs from virtual-mailman (note that I have run postmap on this and restarted mailman and postfix multiple times, but no joy): # STANZA START: pctest # CREATED: Mon Jan 29 15:05:35 2007 pctest at virt1.tld pctest pctest-admin at virt1.tld pctest-admin pctest-bounces at virt1.tld pctest-bounces pctest-confirm at virt1.tld pctest-confirm pctest-join at virt1.tld pctest-join pctest-leave at virt1.tld pctest-leave pctest-owner at virt1.tld pctest-owner pctest-request at virt1.tld pctest-request pctest-subscribe at virt1.tld pctest-subscribe pctest-unsubscribe at virt1.tld pctest-unsubscribe # STANZA END: pctest from mm_cfg.py: # Put YOUR site-specific settings below this line. $SMTPHOST = virt1.tld DEFAULT_EMAIL_HOST = 'virt1.tld' DEFAULT_URL_HOST = 'virt1.tld' IMAGE_LOGOS = '/icons/' MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virt1.tld'] VIRTUAL_HOSTS.clear() add_virtualhost('mail.virt1.tld', 'virt1.tld') from main.cf: recipient_delimiter = + unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/usr/local/etc/postfix/mysql_virtual_alias_maps.cf, hash:/usr/local/mailman/data/virtual-mailman from master.cf: (nothing MM specific) From msapiro at value.net Tue Jan 30 01:18:06 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 29 Jan 2007 16:18:06 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: Message-ID: David Newman wrote: > >Having problems with Mailman, though. I've read these instructions many times: > >http://www.list.org/mailman-install/postfix-virtual.html > >Besides doing what's listed there, I also defined a virtual mailbox for a new "pctest" list (without that, mail sent to pctest at virt1.tld bounces). > >However, MM never distributes the mail to list subscribers. /var/log/maillog says each message is sent to pctest at virt1.tld; however, the only files in /usr/local/mailman/logs that change are smtp and subscribe (and then only when list members are added). > >Basically, postfix delivers message to pctest at virt1.tld but nothing happens after that. Presumably, that's because Postfix is delivering the mail to a local mailbox 'pctest' instead of piping it to Mailman's mail wrapper via the command "/usr/local/mailman/mail/mailman post pctest". This is really a Postfix question, not a Mailman question, but you might find the post at to be helpful. You might also find something of interest at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pgf at foxharp.boston.ma.us Tue Jan 30 02:21:10 2007 From: pgf at foxharp.boston.ma.us (Paul Fox) Date: Mon, 29 Jan 2007 20:21:10 -0500 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: References: Message-ID: <22886.1170120070@foxharp.boston.ma.us> david wrote: > Postfix already handles mail for multiple virtual domains > defined in a MySQL database. I believe virtual domain setup > is OK, as individual users have been sending and receiving > mail for some time. > > Having problems with Mailman, though. I've read these > instructions many times: > > http://www.list.org/mailman-install/postfix-virtual.html > > Besides doing what's listed there, I also defined a virtual > mailbox for a new "pctest" list (without that, mail sent to > pctest at virt1.tld bounces). > > However, MM never distributes the mail to list subscribers. > /var/log/maillog says each message is sent to > pctest at virt1.tld; however, the only files in > /usr/local/mailman/logs that change are smtp and subscribe > (and then only when list members are added). so it sounds like you have postfix aliases set up for "pctest-*", but not "pctest" itself? is that right? > Basically, postfix delivers message to pctest at virt1.tld but nothing happens > after that. i don't use mysql, but my epiphany was when i realized i needed two separate mappings to be in place to get postfix and mailman working together. you need the virtual domain map (which i believe you have) and you need the map that takes the result of the virtual domain map, and turns it into a "real" destination. paul =--------------------- paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 15.1 degrees) From vanhorn at whidbey.com Tue Jan 30 09:37:49 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Tue, 30 Jan 2007 00:37:49 -0800 Subject: [Mailman-Users] Moved list, archiving Message-ID: <45BF03DD.7050800@whidbey.com> After moving the list to it's new home and running the script to update the archive, I ended up with a raft of messages in the January 2007 archive that are probably ancient. They show no subject, and all of them are dated this afternoon, probably at the time that I ran the script. Is there any safe way to clear those out? Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From brad at shub-internet.org Tue Jan 30 09:52:14 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 30 Jan 2007 02:52:14 -0600 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <45BF03DD.7050800@whidbey.com> References: <45BF03DD.7050800@whidbey.com> Message-ID: At 12:37 AM -0800 1/30/07, G. Armour Van Horn wrote: > After moving the list to it's new home and running the script to update > the archive, I ended up with a raft of messages in the January 2007 > archive that are probably ancient. They show no subject, and all of them > are dated this afternoon, probably at the time that I ran the script. Is > there any safe way to clear those out? That's an artifact of the date-correction routines in the pipermail archiving system that was integrated into Mailman. I've got an item on the request list to move the date correction routines into Mailman itself, right after message reception. That way the messages get corrected once on input and then never need to get corrected again, and you don't wind up with the situation that you have now. I don't know that there's any way to fix this problem with the current code, short of going in and manually editing the raw mailbox to correct the date header (and any other headers that need fixing), and then completely re-generating your archives. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From ptomblin at xcski.com Tue Jan 30 13:37:48 2007 From: ptomblin at xcski.com (Paul Tomblin) Date: Tue, 30 Jan 2007 07:37:48 -0500 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <45BF03DD.7050800@whidbey.com> References: <45BF03DD.7050800@whidbey.com> Message-ID: <20070130123748.GA15436@allhats.xcski.com> Quoting G. Armour Van Horn (vanhorn at whidbey.com): > After moving the list to it's new home and running the script to update > the archive, I ended up with a raft of messages in the January 2007 > archive that are probably ancient. They show no subject, and all of them > are dated this afternoon, probably at the time that I ran the script. Is > there any safe way to clear those out? That happened to me when I moved my archives because I had old messages that had an "unescaped" "From " line in the body. I guess there was a time when pipermail didn't put a ">" in front of the word "From " in the body of a message, and so when I ran "arch" on that mbox I got a lot of gibberish messages dated today. The user contributed program "cleanarch" can help fix up some (but not all) of those and I had to use sed to fix the rest. Another problem I ran into were some messages that came around 1 Jan 2000 that had a date of 1 Jan 100. I also discovered some very old messages that had a header line of Content-Type: TEXT/PLAIN; charset=".chrsc" which confused arch as well. It wasn't until I fixed all of these problems that I was able to finally run arch in a way that built good archives. -- Paul Tomblin http://blog.xcski.com/ Don't you just hate them? Don't you just wanna break their ribs, cut their backs open and pull their lungs out from behind? -- Ina Faye-Lund, on script kiddies From wo_shi_big_stomach at mac.com Tue Jan 30 18:24:01 2007 From: wo_shi_big_stomach at mac.com (David Newman) Date: Tue, 30 Jan 2007 09:24:01 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: References: Message-ID: <0009A672-0110-1000-CD0C-FCC7AC400EF2-Webmail-10020@mac.com> On Monday, January 29, 2007, at 04:18PM, "Mark Sapiro" wrote: >>Basically, postfix delivers message to pctest at virt1.tld but nothing happens after that. > > >Presumably, that's because Postfix is delivering the mail to a local >mailbox 'pctest' instead of piping it to Mailman's mail wrapper via >the command "/usr/local/mailman/mail/mailman post pctest". Yup. That is exactly what's happening (except that it's a virtual mailbox and not a local user account). >This is really a Postfix question, not a Mailman question Yes and no. I'd say it's more of a clueless-pilot question, esp. since Postfix is doing exactly what it's told -- in this instance, deliver messages to pctest at virt1.tld. The problem here is mailman-specific, though I'm unsure whether the solution is in mailman configuration or some combo of postfix and mailman configs. I've read and reread and reread the mailman docs, and I don't see where and how virtual addresses get piped to the command above. The file /usr/local/mailman/data/aliases has commands like the above; the file /usr/local/mailman/data/virtual-mailman does not. For example, aliases has: pctest: "|/usr/local/mailman/mail/mailman post pctest" but virtual-mailman has: pctest at virt1.tld pctest I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. , but you >might find the post at > >to be helpful. Thanks. That post in turn links to an earlier howto which covers aliases but not virtual-mailman. On Monday, January 29, 2007, at 05:47PM, "Paul Fox" wrote: > > However, MM never distributes the mail to list subscribers. > > /var/log/maillog says each message is sent to > > pctest at virt1.tld; however, the only files in > > /usr/local/mailman/logs that change are smtp and subscribe > > (and then only when list members are added). > >so it sounds like you have postfix aliases set up for "pctest-*", but >not "pctest" itself? is that right? Actually, the opposite. I'd set up a virtual mailbox for "pctest" but none of the rest of the pctest-* hierarchy. It's not covered in the docs, but from Mark's email I gather that I shouldn't need this step -- instead mail should be piped to the command Mark gave above. > > Basically, postfix delivers message to pctest at virt1.tld but nothing happens > > after that. > >i don't use mysql, but my epiphany was when i realized i needed >two separate mappings to be in place to get postfix and mailman >working together. you need the virtual domain map (which i believe >you have) and you need the map that takes the result of the virtual >domain map, and turns it into a "real" destination. Right. That's really my question -- how is that done? thanks! /wsbs From pgf at foxharp.boston.ma.us Tue Jan 30 18:33:07 2007 From: pgf at foxharp.boston.ma.us (Paul Fox) Date: Tue, 30 Jan 2007 12:33:07 -0500 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <0009A672-0110-1000-CD0C-FCC7AC400EF2-Webmail-10020@mac.com> References: <0009A672-0110-1000-CD0C-FCC7AC400EF2-Webmail-10020@mac.com> Message-ID: <21892.1170178387@foxharp.boston.ma.us> david wrote: > I've read and reread and reread the mailman docs, and I don't see where and how > virtual addresses get piped to the command above. The file > /usr/local/mailman/data/aliases has commands like the above; the file > /usr/local/mailman/data/virtual-mailman does not. > > For example, aliases has: > > pctest: "|/usr/local/mailman/mail/mailman post pctest" > > but virtual-mailman has: > > pctest at virt1.tld pctest > > I'm missing how to glue the two together, and this is NOT covered in the > existing mailman docs. ... > > > >i don't use mysql, but my epiphany was when i realized i needed > >two separate mappings to be in place to get postfix and mailman > >working together. you need the virtual domain map (which i believe > >you have) and you need the map that takes the result of the virtual > >domain map, and turns it into a "real" destination. > > Right. That's really my question -- how is that done? as i understand it, it's done automatically by postfix, if you tell it about all the maps. if you weren't using mysql, the definition of virtual_alias_maps should include the alias maps for any virtual domains: virtual_alias_maps = hash:/usr/local/mailman/data/virtual-mailman and the postfix definition of "alias_maps" should refer to both /etc/aliases and /usr/local/mailman/data/aliases: alias_maps = hash:/etc/aliases hash:/usr/local/mailman/data/aliases postfix will resolve using first the virtual_alias_maps, and then the alias_maps. but i don't know how mysql affects any of that. paul =--------------------- paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 24.8 degrees) From pgf at foxharp.boston.ma.us Tue Jan 30 18:48:06 2007 From: pgf at foxharp.boston.ma.us (Paul Fox) Date: Tue, 30 Jan 2007 12:48:06 -0500 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <474f4b810701300944r3f6e4c12r36bb776bbecef905@mail.gmail.com> References: <0009A672-0110-1000-CD0C-FCC7AC400EF2-Webmail-10020@mac.com> <21892.1170178387@foxharp.boston.ma.us> <474f4b810701300944r3f6e4c12r36bb776bbecef905@mail.gmail.com> Message-ID: <26303.1170179286@foxharp.boston.ma.us> [ cc'ing the list on reply ] orlando wrote: > I think he still has to issue the genaliases command. oh, yes. in addition, all of the hash maps need to have postmap run on them. paul > > the virtual_alias_map is the one that should have a mysql entry: > > virtual_alias_maps = hash:/usr/local/mailman/data/virtual-mailman, > mysql:/usr/local/etc/postfix/mysql/mysql_virtual_alias_maps.cf > > > alias_maps = hash:/usr/local/mailman/data/aliases, > hash:/usr/local/etc/postfix/aliases > > Orlando > =--------------------- paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 26.4 degrees) From msapiro at value.net Tue Jan 30 18:49:11 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 09:49:11 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <0009A672-0110-1000-CD0C-FCC7AC400EF2-Webmail-10020@mac.com> Message-ID: David Newman wrote: > >pctest: "|/usr/local/mailman/mail/mailman post pctest" > >but virtual-mailman has: > >pctest at virt1.tld pctest > >I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. Do you have the appropriate alias_maps entry in your postfix configuration pointing to aliases as discussed in Do you have "MTA = 'Postfix'" in your mm_cfg.py and have you run bin/genaliases to create the appropriate entries in data/aliases* and data/virtual-mailman*? You have to do all the stuff in sec 6.1.1 of the manual as well as the stuff in sec 6.1.2 that you said you'd read many times. >Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. I'm sure this can be improved. We'd appreciate the help. >Actually, the opposite. I'd set up a virtual mailbox for "pctest" but none of the rest of the pctest-* hierarchy. It's not covered in the docs, but from Mark's email I gather that I shouldn't need this step -- instead mail should be piped to the command Mark gave above. You need entries in virtual-mailman* for addresses in your postfix virtual domains to map them to local addresses, AND you need entries in aliases* to cause these local addresses to be piped to the wrapper. If you have MTA = 'Postfix' Mailman should take care of maintaining data/aliases* and data/virtual-mailman* for you, but you need to reference them in the postfix config as discissed in and -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 30 18:56:37 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 09:56:37 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <21892.1170178387@foxharp.boston.ma.us> Message-ID: Paul Fox wrote: > >as i understand it, it's done automatically by postfix, if you >tell it about all the maps. if you weren't using mysql, the >definition of virtual_alias_maps should include the alias maps >for any virtual domains: > >virtual_alias_maps = > hash:/usr/local/mailman/data/virtual-mailman > >and the postfix definition of "alias_maps" should refer to both >/etc/aliases and /usr/local/mailman/data/aliases: > >alias_maps = > hash:/etc/aliases > hash:/usr/local/mailman/data/aliases > >postfix will resolve using first the virtual_alias_maps, and then >the alias_maps. > >but i don't know how mysql affects any of that. My understanding is that if you are using mysql, you might have something like alias_maps = mysql:/etc/aliases hash:/usr/local/mailman/data/aliases i.e., you could still use a hash for mailman's aliases and virtual-mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jan 30 19:00:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 10:00:24 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <26303.1170179286@foxharp.boston.ma.us> Message-ID: Paul Fox wrote: >[ cc'ing the list on reply ] > >orlando wrote: > > I think he still has to issue the genaliases command. > >oh, yes. in addition, all of the hash maps need to have postmap >run on them. Assuming MTA = 'Postfix', genaliases and list creation/deletion will run the commands defined by POSTFIX_ALIAS_CMD = '/usr/sbin/postalias' POSTFIX_MAP_CMD = '/usr/sbin/postmap' or whatever you may have redefined them to in mm_cfg.py. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pgf at foxharp.boston.ma.us Tue Jan 30 19:04:28 2007 From: pgf at foxharp.boston.ma.us (Paul Fox) Date: Tue, 30 Jan 2007 13:04:28 -0500 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: References: Message-ID: <29894.1170180268@foxharp.boston.ma.us> mark wrote: > David Newman wrote: > > > Once I get this running I'd be glad to write up > > documentation and submit it for possible inclusion. > > I'm sure this can be improved. We'd appreciate the help. in that vein -- i never saw any yea or nay on the minor doc addition i submitted on a related aspect of lists at virtual domains. at the time i thought i might have sent the change to the wrong place (i.e. the users', not the developers' list) but now i'm just wondering if it fell through the cracks: http://www.mail-archive.com/mailman-users%40python.org/msg43083.html paul p.s. the searchable archives at mail-archive.com are nice, but they'd be a _lot_ more useful if they didn't obscure anything that looked like an email address. text describing mailman and postfix config is rendered practically useless because of it. at the least, they shouldn't obscure any address ending in ".tld" or "example.com". ;-/ =--------------------- paul fox, pgf at foxharp.boston.ma.us (arlington, ma, where it's 25.9 degrees) From msapiro at value.net Tue Jan 30 19:35:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 10:35:36 -0800 Subject: [Mailman-Users] virtual domain setup with postfix In-Reply-To: <29894.1170180268@foxharp.boston.ma.us> Message-ID: Paul Fox wrote: > >in that vein -- i never saw any yea or nay on the minor doc >addition i submitted on a related aspect of lists at virtual >domains. at the time i thought i might have sent the change to >the wrong place (i.e. the users', not the developers' list) but >now i'm just wondering if it fell through the cracks: > http://www.mail-archive.com/mailman-users%40python.org/msg43083.html It's in my inbox. I haven't had time to do anything with it, but I at least have seen it. That said, it is probably better to post something like this to the patch tracker , or if you think it needs discussion first, to the mailman-developers. >p.s. the searchable archives at mail-archive.com are nice, but they'd >be a _lot_ more useful if they didn't obscure anything that looked >like an email address. text describing mailman and postfix config >is rendered practically useless because of it. at the least, they >shouldn't obscure any address ending in ".tld" or "example.com". ;-/ Of course, we don't control mail-archive.com. It is our 'official' searchable archive (although google with site:mail.python.org inurl:mailman works pretty well), but if we ever get archive search integrated in Mailman OOTB, we might drop it. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vancleef at lostwells.net Tue Jan 30 22:51:00 2007 From: vancleef at lostwells.net (vancleef at lostwells.net) Date: Tue, 30 Jan 2007 14:51:00 -0700 (MST) Subject: [Mailman-Users] Can't create a new list Message-ID: <200701302151.l0ULp0JN001597@julie.lostwells.net> I'm trying to create a new list on a Mailman 2.1.9 installation. The list is set up at www.mydomain.net with virtual hosting of otherdomain.com. When I use either www.mydomain.net or www.otherdomain.com to get to mailman/create, and try to create the new list, every try returns me Error: Unknown virtual host for attempts to create under either domain. How can I create a new list successfully? I need to create lists in both domains. Hank From msapiro at value.net Tue Jan 30 23:07:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 14:07:51 -0800 Subject: [Mailman-Users] Can't create a new list In-Reply-To: <200701302151.l0ULp0JN001597@julie.lostwells.net> Message-ID: vancleef at lostwells.net wrote: > >When I use either www.mydomain.net or www.otherdomain.com to get to >mailman/create, and try to create the new list, every try returns me >Error: Unknown virtual host for attempts to create >under either domain. It appears that www.domain.ext is the domain set by your web server in the variable HTTP_HOST or if that isn't set, SERVER_NAME in the environment that is passes to the create cgi. >How can I create a new list successfully? I need to create lists in >both domains. You can use bin/newlist, but the real solution is to figure out what's in the web server configuration that is causing it to pass the 'wrong' domain. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dgood at independence.k12.ia.us Tue Jan 30 23:23:21 2007 From: dgood at independence.k12.ia.us (Dan Good) Date: Tue, 30 Jan 2007 16:23:21 -0600 Subject: [Mailman-Users] mailing lists Message-ID: <87FF7255-A052-46C6-89EB-DB998D568C45@independence.k12.ia.us> Hello, I am writing because I'm having some difficulty with a group within my mailing lists. I am unable to access the web interfaces for this group. All others work fine. This I get a login prompt but noting else. Any ideas on how to fix this? Thanks Dan From vanhorn at whidbey.com Wed Jan 31 00:33:53 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Tue, 30 Jan 2007 15:33:53 -0800 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <20070130123748.GA15436@allhats.xcski.com> References: <45BF03DD.7050800@whidbey.com> <20070130123748.GA15436@allhats.xcski.com> Message-ID: <45BFD5E1.60702@whidbey.com> Paul Tomblin wrote: >Quoting G. Armour Van Horn (vanhorn at whidbey.com): > > >>After moving the list to it's new home and running the script to update >>the archive, I ended up with a raft of messages in the January 2007 >>archive that are probably ancient. They show no subject, and all of them >>are dated this afternoon, probably at the time that I ran the script. Is >>there any safe way to clear those out? >> >> > >That happened to me when I moved my archives because I had old messages >that had an "unescaped" "From " line in the body. I guess there was a >time when pipermail didn't put a ">" in front of the word "From " in the >body of a message, and so when I ran "arch" on that mbox I got a lot of >gibberish messages dated today. The user contributed program "cleanarch" >can help fix up some (but not all) of those and I had to use sed to fix >the rest. Another problem I ran into were some messages that came around >1 Jan 2000 that had a date of 1 Jan 100. I also discovered some very old >messages that had a header line of >Content-Type: TEXT/PLAIN; charset=".chrsc" >which confused arch as well. It wasn't until I fixed all >of these problems that I was able to finally run arch in a way that built >good archives. > > That sounds ugly, given that the mbox file is over 20 megs. I guess I'll try cleanarch and ignore the rest of it, as I lack the skill (or patience) to find and repair the errors in the mbox. But thanks for the lead. Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From msapiro at value.net Wed Jan 31 00:51:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 15:51:57 -0800 Subject: [Mailman-Users] mailing lists In-Reply-To: <87FF7255-A052-46C6-89EB-DB998D568C45@independence.k12.ia.us> Message-ID: Dan Good wrote: > >I am unable to access the web interfaces for this group. All others >work fine. This I get a login prompt but noting else. The list is probably locked, and the lock is almost certainly stale. See which I just wrote. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From vanhorn at whidbey.com Wed Jan 31 01:16:02 2007 From: vanhorn at whidbey.com (G. Armour Van Horn) Date: Tue, 30 Jan 2007 16:16:02 -0800 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <20070130123748.GA15436@allhats.xcski.com> References: <45BF03DD.7050800@whidbey.com> <20070130123748.GA15436@allhats.xcski.com> Message-ID: <45BFDFC2.1080102@whidbey.com> Paul Tomblin wrote: >Quoting G. Armour Van Horn (vanhorn at whidbey.com): > > >>After moving the list to it's new home and running the script to update >>the archive, I ended up with a raft of messages in the January 2007 >>archive that are probably ancient. They show no subject, and all of them >>are dated this afternoon, probably at the time that I ran the script. Is >>there any safe way to clear those out? >> >> > >That happened to me when I moved my archives because I had old messages >that had an "unescaped" "From " line in the body. I guess there was a >time when pipermail didn't put a ">" in front of the word "From " in the >body of a message, and so when I ran "arch" on that mbox I got a lot of >gibberish messages dated today. The user contributed program "cleanarch" >can help fix up some (but not all) of those and I had to use sed to fix >the rest. Another problem I ran into were some messages that came around >1 Jan 2000 that had a date of 1 Jan 100. I also discovered some very old >messages that had a header line of >Content-Type: TEXT/PLAIN; charset=".chrsc" >which confused arch as well. It wasn't until I fixed all >of these problems that I was able to finally run arch in a way that built >good archives. > > > I spoke too soon. I got a lot of this: #Unix-From line changed: 175609 From the wire service copy: #######Unix-From line changed: 176324 From the MM press release: ##########################Unix-From line changed: 178901 From a designers view I think FW is the most powerful tool. I designed ######Unix-From line changed: 179571 From my web site: Unix-From line changed: 179573 From my experience, there is no specific palette grouping that causes Pal to (I had used the "-s 100" option to output a # every hundred lines.) Every case cleanarch came upon was a valid bit of text inside a message. Then I went and looked at the actual output, and saw that cleanarch had prepended a ">" to the lines that were part of running text, so I renamed files so the output from cleanarch was the live file and ran arch again. I think it may have made things worse, it looks like the same messages that were there before still ended up in the January archive. They still have date tags based on the time of running arch for the first time on the new machine yesterday afternoon. These dates are not found in the mbox file. Looking at the messages in the January archive, it looks like there are only about 25 messages, not really a huge task to go back and repair manually. The question then becomes, what do I need to do to the mbox file so that arch will know where to actually break things, and do I need to do anything special to make sure that the messed up archive elements are no longer present? Van -- ---------------------------------------------------------- Sign up now for Quotes of the Day, a handful of quotations on a theme delivered every morning. Enlightenment! Daily, for free! mailto:twisted at whidbey.com?subject=Subscribe_QOTD For photography, web design, hosting, and maintenance, visit Van's home page: http://www.domainvanhorn.com/van/ ----------------------------------------------------------- From msapiro at value.net Wed Jan 31 01:26:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 16:26:36 -0800 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <45BFDFC2.1080102@whidbey.com> Message-ID: G. Armour Van Horn wrote: >I spoke too soon. I got a lot of this: > >#Unix-From line changed: 175609 > From the wire service copy: >#######Unix-From line changed: 176324 > From the MM press release: >##########################Unix-From line changed: 178901 > From a designers view I think FW is the most powerful tool. I designed >######Unix-From line changed: 179571 > From my web site: >Unix-From line changed: 179573 > From my experience, there is no specific palette grouping that causes >Pal to > >(I had used the "-s 100" option to output a # every hundred lines.) This is normal output from cleanarch doing what it is supposed to do, Namely prepending '>' to lines that begin with 'From ' that don't look like Unix mbox message separators >Every case cleanarch came upon was a valid bit of text inside a message. >Then I went and looked at the actual output, and saw that cleanarch had >prepended a ">" to the lines that were part of running text, so I >renamed files so the output from cleanarch was the live file and ran >arch again. So far so good. >I think it may have made things worse, it looks like the same messages >that were there before still ended up in the January archive. They still >have date tags based on the time of running arch for the first time on >the new machine yesterday afternoon. These dates are not found in the >mbox file. Did you remember the --wipe option when you reran bin/arch? >Looking at the messages in the January archive, it looks like there are >only about 25 messages, not really a huge task to go back and repair >manually. The question then becomes, what do I need to do to the mbox >file so that arch will know where to actually break things, and do I >need to do anything special to make sure that the messed up archive >elements are no longer present? First make sure you've run 'bin/arch --wipe' with the cleanarch'd .mbox. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From worldoff9908 at sacbeemail.com Wed Jan 31 00:25:45 2007 From: worldoff9908 at sacbeemail.com (NFN Smith) Date: Tue, 30 Jan 2007 16:25:45 -0700 Subject: [Mailman-Users] Shunting problem Message-ID: <7C129292E9FD3C54BB4A02206C61A572@worldoff9908.sacbeemail.com> I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, I'm getting an increasing number of messages shunted, with error logs that look like: > Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding Unicode is not supported > Jan 30 23:10:53 2007 (3315) Traceback (most recent call last): > File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop > self._onefile(msg, msgdata) > File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in process > send_digests(mlist, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests > send_i18n_digests(mlist, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests > msg = scrubber(mlist, msg) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 318, in process > partcharset = part.get_content_charset() > File "email/Message.py", line 800, in get_content_charset > TypeError: decoding Unicode is not supported > > Jan 30 23:10:53 2007 (3315) SHUNTING: 1170193244.4528749+524dabeddb1737e4b548d3ad0d7c3d9bd2c7c1a0 I have no idea why messages might have unicode in them. This machine has the following python modules: python-central 0.5.12 python-minimal 2.4.4-1 python2.3 2.3.5-16 python2.4 2.4.4-1 python2.4-minimal 2.4.4-1 I'm not aware of any config changes that have been made to this machine recently. Two questions: 1) How do I get the shunted messages cleared? What has to happen before I run unshunt? 2) What do I need to do to clear the problem that is causing shunting? Smith Composed by sacbeemail. Get Your Free E-mail at http://www.sacbeemail.com . Or visit Northern California?s premiere news and information website at http://www.sacbee.com . From msapiro at value.net Wed Jan 31 01:49:10 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 16:49:10 -0800 Subject: [Mailman-Users] Shunting problem In-Reply-To: <7C129292E9FD3C54BB4A02206C61A572@worldoff9908.sacbeemail.com> Message-ID: NFN Smith wrote: >I'm running Mailman 2.1.5 on a Debian 3.1 box. In the last few days, >I'm getting an increasing number of messages shunted, with error logs >that look like: > >> Jan 30 23:10:53 2007 (3315) Uncaught runner exception: decoding >Unicode is not supported >> Jan 30 23:10:53 2007 (3315) Traceback (most recent call last): >> File "/var/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop >> self._onefile(msg, msgdata) >> File "/var/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile >> keepqueued =3D self._dispose(mlist, msg, msgdata) >> File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, >in _dispose >> more =3D self._dopipeline(mlist, msg, msgdata, pipeline) >> File "/var/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, >in _dopipeline >> sys.modules[modname].process(mlist, msg, msgdata) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 91, in >process >> send_digests(mlist, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 132, in >send_digests >> send_i18n_digests(mlist, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 306, in >send_i18n_digests >> msg =3D scrubber(mlist, msg) >> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 318, in >process >> partcharset =3D part.get_content_charset() >> File "email/Message.py", line 800, in get_content_charset >> TypeError: decoding Unicode is not supported >> = > >> Jan 30 23:10:53 2007 (3315) SHUNTING: >1170193244.4528749+524dabeddb1737e4b548d3ad0d7c3d9bd2c7c1a0 I believe you'll find the underlying problem is that there is a message in /var/lib/mailman/lists//digest.mbox with a Content-Type: header with a charset="Unicode" parameter. If you edit the dgest.mbox file (possibly changing charset="Unicode" to charset="utf-8" or deleting the offending message), that will allow the list to resume processing. As to which , it's the one that hasn't produced a digest since this started. >Two questions: > >1) How do I get the shunted messages cleared? What has to happen >before I run unshunt? Fix the digest.mbox (or just move it aside) >2) What do I need to do to clear the problem that is causing shunting? See 1). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Wed Jan 31 01:53:49 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 30 Jan 2007 18:53:49 -0600 Subject: [Mailman-Users] Moved list, archiving In-Reply-To: <45BFD5E1.60702@whidbey.com> References: <45BF03DD.7050800@whidbey.com> <20070130123748.GA15436@allhats.xcski.com> <45BFD5E1.60702@whidbey.com> Message-ID: At 3:33 PM -0800 1/30/07, G. Armour Van Horn wrote: > That sounds ugly, given that the mbox file is over 20 megs. I guess I'll > try cleanarch and ignore the rest of it, as I lack the skill (or > patience) to find and repair the errors in the mbox. But thanks for the > lead. Try doing this kind of thing on a mailbox that is almost 2GB in size, and part of your problem is that the machine it's on doesn't support large files, and has only 1GB of RAM. Large mailbox files are a serious pain. -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From msapiro at value.net Wed Jan 31 01:58:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 30 Jan 2007 16:58:57 -0800 Subject: [Mailman-Users] Shunting problem In-Reply-To: Message-ID: Mark Sapiro wrote: >NFN Smith wrote: > >>2) What do I need to do to clear the problem that is causing shunting? > > >See 1). Note: if you meant what do you need to do to prevent this from happening again, upgrade to Mailman 2.1.7 or later. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From wo_shi_big_stomach at mac.com Wed Jan 31 02:57:02 2007 From: wo_shi_big_stomach at mac.com (wo_shi_big_stomach) Date: Tue, 30 Jan 2007 17:57:02 -0800 Subject: [Mailman-Users] virtual domain setup with postfix SOLVED In-Reply-To: References: Message-ID: <45BFF76E.2000102@mac.com> On 1/30/07 9:49 AM, Mark Sapiro wrote: > David Newman wrote: >> pctest: "|/usr/local/mailman/mail/mailman post pctest" >> >> but virtual-mailman has: >> >> pctest at virt1.tld pctest >> >> I'm missing how to glue the two together, and this is NOT covered in the existing mailman docs. > > > Do you have the appropriate alias_maps entry in your postfix > configuration pointing to aliases as discussed in > Yes. This is the part that was missing. I was trying with alias_maps or virtual_alias_maps but not both. MM needs both in this setup. One final problem is that I got the 'Mailman expected the mail wrapper script to be executed as group "nobody"' error because MM for postfix installs with GID mailman. My hack was to uninstall, change the GID to 'nobody' in the FreeBSD ports Makefile, and reinstall. This may have security implications but I'm not sure about that. > > Do you have "MTA = 'Postfix'" in your mm_cfg.py and have you run > bin/genaliases to create the appropriate entries in data/aliases* and > data/virtual-mailman*? > > You have to do all the stuff in sec 6.1.1 of the manual as well as the > stuff in sec 6.1.2 that you said you'd read many times. > > >> Once I get this running I'd be glad to write up documentation and submit it for possible inclusion. Doing all of 6.1.1 and 6.1.2 is something I'll propose adding to 6.1.2. At one stage I did have alias_maps but took it out because it's not given in 6.1.2. Thanks all for your help in getting this set up. It will take me a day or two to write up suggested changes to 6.1.2, which I'll post to the list. thanks again /wsbs From stephen at xemacs.org Wed Jan 31 04:30:06 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 31 Jan 2007 12:30:06 +0900 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: References: Message-ID: <87ejpb6fgh.fsf@uwakimon.sk.tsukuba.ac.jp> Brad Knowles writes: > If you have Mailman questions, we should be able to help with those. > But we can't provide support for OS-specific issues. However, members of this list often do; eg, this thread got 3 answers. How about starting an OS-specific section of the FAQ, similar to the MTA Integration section? Then you could change the above reply to "OS-specific issues are off-topic on this list; they are best asked on the channels provided by that OS. However, you can find some user-contributed answers in the OS-specific section of the FAQ." Also, encourage those who do provide answers on-list to add them to the FAQ and answer on list with "I just added an answer to that question to the FAQ". From brad at shub-internet.org Wed Jan 31 08:32:23 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 31 Jan 2007 01:32:23 -0600 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: <87ejpb6fgh.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87ejpb6fgh.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: At 12:30 PM +0900 1/31/07, Stephen J. Turnbull wrote: > > If you have Mailman questions, we should be able to help with those. > > But we can't provide support for OS-specific issues. > > However, members of this list often do; eg, this thread got 3 answers. Of which two were "We can't help you with OS-specific issues", and I don't know if the third was actually helpful or not -- we have no evidence that the OP saw that response, or that it was helpful to the OP. > How about starting an OS-specific section of the FAQ, similar to the > MTA Integration section? Then you could change the above reply to > "OS-specific issues are off-topic on this list; they are best asked on > the channels provided by that OS. However, you can find some > user-contributed answers in the OS-specific section of the FAQ." There are already some OS-specific items listed in the FAQ. I see no reason why those could not be expanded (where appropriate), or new OS-specific items added. I'm not sure we need a separate OS-specific section, however. I don't know how that would affect the FAQ organization structure. Currently, I think we are putting OS-specific questions in the appropriate section and then trying to make sure that we label them appropriately. Moreover, I think we need to be talking about platform-specific questions, and not just OS-specific. For example, cPanel is a platform, and can presumably run on multiple different OSes. If we were to have a separate section for these kinds of questions, I think we would want to put all platform-specific and OS-specific questions together. > Also, encourage those who do provide answers on-list to add them to > the FAQ and answer on list with "I just added an answer to that > question to the FAQ". My general policy has been to answer things directly two or three times, but beyond that to then summarize the responses and put them into the FAQ, and thereafter to primarily refer to the answers that are already in the FAQ. Do we need a FAQ entry on what the proper way is to answer a question? -- Brad Knowles , Consultant & Author Co-author of SAGE Booklet #15 "Internet Postmaster: Duties and Responsibilities" Founding Member and Platinum Individual Sponsor of LOPSA: Papers: LinkedIn Profile: From gstein at lyra.org Wed Jan 31 14:44:08 2007 From: gstein at lyra.org (gstein at lyra.org) Date: Wed, 31 Jan 2007 05:44:08 -0800 Subject: [Mailman-Users] received your email Message-ID: <200701311344.l0VDi8HR002675@nebula.lyra.org> Hi, [ Re: Test ] I have received your email, but it may take a while to respond. I'm really sorry to have to hook up this auto-responder, as it is so impersonal. However, I get a lot of email every day and find it very difficult to keep up with it. Please be patient while I try to get to your message. Please feel free to resend your message if you think I've missed it. I'll always respond to personal email first. If your email is regarding some of the software that I work on (if you have questions, comments, suggestions, etc), then please resend it to the appropriate mailing list: mod_dav WebDAV ViewCVS Subversion edna Thank you! Cheers, -g -- Greg Stein, http://www.lyra.org/ From stephen at xemacs.org Wed Jan 31 15:51:26 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 31 Jan 2007 23:51:26 +0900 Subject: [Mailman-Users] Mailman not working after reboot In-Reply-To: References: <87ejpb6fgh.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <87bqkfw8pd.fsf@uwakimon.sk.tsukuba.ac.jp> Brad Knowles writes: > > However, members of this list often do; eg, this thread got 3 answers. > > Of which two were "We can't help you with OS-specific issues", Of course. My point is that people do respond, not that it's very helpful; I'm looking for ways to save some of that effort. > Moreover, I think we need to be talking about platform-specific > questions, and not just OS-specific. For example, cPanel is a > platform, and can presumably run on multiple different OSes. If we > were to have a separate section for these kinds of questions, I think > we would want to put all platform-specific and OS-specific questions > together. Right. I actually thought of the cPanel angle, but left it out. > Do we need a FAQ entry on what the proper way is to answer a question? Yes. It's a policy issue. Sometimes the OP will respond to the "nice person who actually answered my question", and start a thread. I think providing answers to off-topic FAQs is a Good Thing[tm], but it should be kept off-list and it shouldn't clutter the main sections of the FAQ. From brad at python.org Wed Jan 31 16:42:35 2007 From: brad at python.org (Brad Knowles) Date: Wed, 31 Jan 2007 09:42:35 -0600 Subject: [Mailman-Users] received your email In-Reply-To: <200701311344.l0VDi8HR002675@nebula.lyra.org> References: <200701311344.l0VDi8HR002675@nebula.lyra.org> Message-ID: At 5:44 AM -0800 1/31/07, gstein at lyra.org wrote: > I have received your email, but it may take a while to respond. I'm really > sorry to have to hook up this auto-responder, as it is so impersonal. > However, I get a lot of email every day and find it very difficult to keep > up with it. Please be patient while I try to get to your message. Sorry folks. This one got through. This user is now moderated, and will not be un-moderated until such time as they can prove that they understand how to properly operate a mail system. -- Brad Knowles Member of the Python.org Postmaster Team Co-moderator of mailman-users and mailman-developers mailing lists From pmatulis at sympatico.ca Wed Jan 31 20:57:01 2007 From: pmatulis at sympatico.ca (Peter Matulis) Date: Wed, 31 Jan 2007 14:57:01 -0500 Subject: [Mailman-Users] separate mailman and web servers Message-ID: <200701311457.01835.pmatulis@sympatico.ca> Can someone explain to me how mailman and the web server can exist on separate machines? I am new to mailman and I'm having a hard time understanding how mailman communicates with its web server. I have a new client that connects to an external web server to add list members but mailman (and postfix) runs on a local system. I see that in /usr/local/mailman/Mailman/mm_cfg.py mailman is pointed to this external web server with DEFAULT_URL_HOST. Any pointers on how postfix fits into this communication are also appreciated. The online docs at list.org for Site Administrators do not explain much. What my client appears to have is a simple diffusion setup. They use it as a means to send info to multiple people. So members do not contribute. P