From msapiro at value.net Fri Jun 1 01:20:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 16:20:24 -0700 Subject: [Mailman-Users] Mailman Splitting Subject In-Reply-To: <87myzt3sov.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Stephen J. Turnbull wrote: > >It's almost a trivial patch; in the email/Generator.py file find the >keyword argument continuation_ws='\t' to the Header initialization and >change the '\t' to ' '. This is an incomplete solution. See Mailman/Handlers/CookHeaders.py. You really need to patch the prefix_subject function in that module by changing ws = '\t' in # Try to figure out what the continuation_ws is for the header if isinstance(subject, Header): lines = str(subject).splitlines() else: lines = subject.splitlines() ws = '\t' if len(lines) > 1 and lines[1] and lines[1][0] in ' \t': ws = lines[1][0] to ws = ' ' or possibly replace that whole piece with just ws = ' ' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 01:29:56 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 16:29:56 -0700 Subject: [Mailman-Users] Maximum template size? In-Reply-To: <20070526025447.F24171BF258@ws1-1.us4.outblaze.com> Message-ID: Carter Braxton wrote: > >I just tested this to be certain, and the variable substitution does not take place -- the invitation email that is sent contains the variable names rather than the values: The problem is the non-substitution '%' characters in your template. E.g., >75% of email traffic on the Internet > http://www.test.test/cgi-bin/mailman/options/test/name%40domain.com > > The part that reads "name%40domain.com" is based on your email > address. For example, if you signed up with an email address of > "foo at bar.com," you would point your web browser to: > > http://www.test.test/cgi-bin/mailman/options/test/foo%40bar.com All the above '%' characters need to be doubled as '%%' so they are not confused with substitutions such as the following. >Your address "%(email)s" has been invited to join the %(listname)s >mailing list at %(hostname)s by the %(listname)s mailing list owner. >You may accept the invitation by simply replying to this message, >keeping the Subject: header intact. > >You can also visit this web page: > > %(confirmurl)s > >Or you should include the following line -- and only the following >line -- in a message to %(requestaddr)s: > > confirm %(cookie)s > >Note that simply sending a `reply' to this message should work from >most mail readers. > >If you want to decline this invitation, please simply disregard this >message. If you have any questions, please send them to >%(listowner)s. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 01:45:08 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 16:45:08 -0700 Subject: [Mailman-Users] No domain name, Can I use mailman to build a maillist? In-Reply-To: <20070525154949.80382d80.ibatis2@163.com> Message-ID: jetspeed wrote: >I use exim4 as MTA, and mailman as maillist >But I have no domain name besides my IP, so mails from other smtp servers can't be relayed to my MTA, How can I deal with this situation? I think you can set DEFAULT_URL_HOST = 'xxx.xxx.xxx.xxx' DEFAULT_EMAIL_HOST = '[xxx.xxx.xxx.xxx]' and Mailman will work. but you may have issues with other MTAs refusing to deliver to address literals. OTOH, for less that $1.00/month you can register a domain including DNS service with, e.g., . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 01:54:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 16:54:26 -0700 Subject: [Mailman-Users] how can i simulate mailman pages In-Reply-To: <20070526182136.2EC151E4008@bag.python.org> Message-ID: wrote: >'The problem is probably that the /admin/* pages require the list or site >admin password to be in a cookie, and normal users aren't going to have >that.' So, it seems you want to make your own web form which circumvents the Mailman subscribe process and subscribes the user directly via the admin mass subscribe page. >is it possible to set a cookie by hand. You don't need to do this. You just send the admin password with the cgi data as shown for example at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 02:16:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 17:16:49 -0700 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: <7c5b3fd245874985b5fa1fa9049a7b2c@shambhala.com> Message-ID: Leonard Jacobs wrote: >I am trying to run Mailman 2.1.9 on a CentOS 4 server with postfix 2.4.1. I had Mailman 2.1.5 running on a slower system and wanted to offload some apps to this newer server but am having problems. check_perms has no errors. Creating lists works fine and when postings are submitted the messages are delivered to the list admins re posting verifications. > >But only a few of the messages are getting delivered. logs/smtp-failure shows many of this type of error: >"delivery to someone at gmail.com failed with code -1: (104, 'Connection reset by peer')" I am also seeing many " Low level smtp error: Server not connected, msgid" errors. I did try all the suggested fixes in the FAQ including adding the line to get error output in the logs/error file. And this file is showing successful delivery, such as >"May 26 16:33:44 2007 qrunner(20744): reply: '250 2.1.5 Ok\r\n' >May 26 16:33:44 2007 qrunner(20744): reply: retcode (250); Msg: 2.1.5 Ok >May 26 16:33:44 2007 qrunner(20744): send: 'rcpt TO:\r\n"" >but the majority of the messages are simply stuck in the qfiles/out and qfile/rety directory. Leonard, I don't know where you are with this. I've read the rest of the thread, but I don't know if you've discovered anything or not. Here's what I can tell you. >From the Mailman/Python/smtplib point of view, Postfix is dropping the connection unexpectedly. You only show a small debug snippet above, but somewhere in the debug output there should be a point where something goes wrong in the SMTP transaction sequence. This should give you a clue. I'm guessing, since individual notices work, that postfix doesn't like transactions with a lot of recipients. Try setting SMTP_MAX_RCPTS = 1 in mm_cfg.py and restarting mailman. If that works, you can then look at why Postfix doesn't like more than x recipients in a transaction. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 02:23:09 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 17:23:09 -0700 Subject: [Mailman-Users] a question about unadvertised lists and spam In-Reply-To: <1180447571.5640.16.camel@localhost> Message-ID: Dennis Morgan wrote: > >My question is - are spamers able to pick up lists from the default (but >not easily accessible) default mailman listinfo page and start >bombarding us with spam on all lists? Or should I set the "Advertise >this list" option to "no" for the lists on the default listinfo page? My opinion, based on only anecdotal observation is that it doesn't matter. The spammers will get your list addresses from spyware on your list member's computers (it only takes one). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 02:35:33 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 17:35:33 -0700 Subject: [Mailman-Users] Point of Clarification for announcement lists In-Reply-To: <1180460378.465c655ae05b4@secure.terabolic.com> Message-ID: bishop at disinfo.net wrote: > >I'm assuming that this directory is in the root of the /usr/lib/Mailman/ >directory. Is this correct? I've created the following directory structure: >/usr/lib/mailman/Lists/XXXX-high-school-announcements/en It should be 'lists', not 'Lists' and the /usr/lib/mailman/lists/XXXX-high-school-announcements/ directory should have already existed before you started, at least if the XXXX-high-school-announcements/ list existed. Also, if 'XXXX' is literally part of the list name, it will be lower case 'xxxx'. I.e., The en/directory is created in the already existing lists// directory that also contains files like config.pck, config.pck.last, request.pck and pending.pck. If that directory doesn't exist in /usr/lib/mailman, then look elsewhere, maybe /var/mailman/. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 1 03:38:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 18:38:42 -0700 Subject: [Mailman-Users] odd empty bounce message generated upon posting toa mailing list In-Reply-To: Message-ID: Jon Pauli wrote: > >I have a couple of mailing lists and every time anyone- member or >non-member posts, everything works fine but the list owner gets > >1)An uncaught bounce notification containing an empty attachment >called ForwardedMessage.eml. Thunderbird is the MUA so I'm guessing it >is responsible for determining how to interpret the attachment, but >even if I save it as a text file it is a 2 byte long file with no >visible characters in it...I didn't take a hex editor to it. I >understand why listowner gets these, I'm just not sure how it can work >with a 2 byte file and no headers ;) This is the message/rfc822 part attached to the bounce notification. T'bird will call it ForwardedMessage.eml if it can't find a Subject: in it which in this case, it can't because the message has no headers and no body. I think this represents a null message sent to the listnam-bounces address, being detected as 'unrecognized' (not surprising) and forwarded to the owner. >2. An email where no subject and no sender appear in the MUA. The >headers are as follows: > >Delivered-To: me at mydomain.com >Return-Path: < >mailman-bounces at mail.mydomain.com> >Received: from [192.168.10.22] (softdnserr [127.0.0.1]) >by mail.mydomain.com with esmtp; Thu, 31 May 2007 09:57:36 -0500id >00A9A0CA.465EE260.00010B2E >Sender: mailman-bounces at mail.mydomain.com >Errors-To: mailman-bounces at mail.mydomain.com >Message-ID: >Date: Thu, 31 May 2007 09:57:36 -0500 >To: undisclosed-recipients: ; This appears to be the result of a null message delivered to the listname-owner address with a few headers added by Mailman and the outgoing MTA. >The interesting things I noticed are: > >1. The Received: header line is wrong. The mail server has a DNS >server running on it as well as the MTA. its IP is 192.168.11.22 NOT >10.22 There is no 192.168.10.22 on my network. This happens only for >mailman emails. I don't recall having to set any IPs when I set up >mailman. What is wrong here? Your outgoing MTA thinks its 'localhost' is 192.168.10.22. Check the MTA configuration for any occurrence of 192.168.10.22. >2. The end of the Message-ID: line contains only mydomain, not say, >mydomain.com like non-mailman emails. I think your MTA made up this message-id, so again, look to your MTA. >3. There is no Sender showing up in the MUA but the Sender: header is >present. It looks like Thunderbird maybe uses the From: header instead >of the Sender header despite naming the column where this would appear >"Sender". This is really a T'bird question, but yes, what T'bird labels as 'sender' in the folder contents pane comes from the From: header. It seems what is happening is for every incoming message to listname at example.com, a null (empty) message is also delivered to listname-bounces at example.com and listname-owner at example.com. When you say "every time anyone- member or non-member posts", do non-member posts get held, rejected or discarded? If so, I think that says these extra null messages are created at incoming message time, probably from some mis-configuration of aliases or routers/transports in the incoming MTA. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From admin2 at enabled.com Fri Jun 1 06:17:26 2007 From: admin2 at enabled.com (Noah) Date: Thu, 31 May 2007 21:17:26 -0700 Subject: [Mailman-Users] OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/testing.mbox' Message-ID: <465F9DD6.3020908@enabled.com> Hi, Okay I give up. I am attempting to create a mail list called testing but I receive the error below. What are the proper permissions for /usr/local/mailman/archives/private/ ? # ls -dl /usr/local/mailman/archives/private/ drwxr-s--x 131 mailman mailman 3072 Feb 28 16:18 /usr/local/mailman/archives/private/ ---- snip ---- May 31 20:40:33 2007 admin(27921): @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ admin(27921): [----- Mailman Version: 2.1.9 -----] admin(27921): [----- Traceback ------] admin(27921): Traceback (most recent call last): admin(27921): File "/usr/local/mailman/scripts/driver", line 101, in run_main admin(27921): main() admin(27921): File "/usr/local/mailman/Mailman/Cgi/create.py", line 56, in main admin(27921): process_request(doc, cgidata) admin(27921): File "/usr/local/mailman/Mailman/Cgi/create.py", line 190, in process_request admin(27921): mlist.Create(listname, owner, pw, langs, emailhost) admin(27921): File "/usr/local/mailman/Mailman/MailList.py", line 493, in Create admin(27921): self.InitVars(name, admin, crypted_password) admin(27921): File "/usr/local/mailman/Mailman/MailList.py", line 404, in InitVars admin(27921): baseclass.InitVars(self) admin(27921): File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 96, in InitVars admin(27921): os.mkdir(self.archive_dir()+'.mbox', 02775) admin(27921): OSError: [Errno 13] Permission denied: '/usr/local/mailman/archives/private/testing.mbox' admin(27921): [----- Python Information -----] ---- snip --- From msapiro at value.net Fri Jun 1 07:40:34 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 31 May 2007 22:40:34 -0700 Subject: [Mailman-Users] OSError: [Errno 13] Permission denied:'/usr/local/mailman/archives/private/testing.mbox' In-Reply-To: <465F9DD6.3020908@enabled.com> Message-ID: Noah > >Okay I give up. I am attempting to create a mail list called testing >but I receive the error below. > >What are the proper permissions for /usr/local/mailman/archives/private/ ? > > ># ls -dl /usr/local/mailman/archives/private/ >drwxr-s--x 131 mailman mailman 3072 Feb 28 16:18 >/usr/local/mailman/archives/private/ Should be those plus g+w, i.e. 2771 or rwxrws--x -- 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 Jun 1 07:54:00 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 1 Jun 2007 00:54:00 -0500 Subject: [Mailman-Users] a question about unadvertised lists and spam In-Reply-To: <1180447571.5640.16.camel@localhost> References: <1180447571.5640.16.camel@localhost> Message-ID: On 5/29/07, Dennis Morgan wrote: > My question is - are spamers able to pick up lists from the default (but > not easily accessible) default mailman listinfo page and start > bombarding us with spam on all lists? Yes. > Or should I set the "Advertise > this list" option to "no" for the lists on the default listinfo page? That would be your choice. But anything that is publicly accessible is game for being snarfed by spammers. There are tools that use this fact to their advantage against spammers, by creating bogus e-mail addresses as part of a "honeypot" campaign, where they know that each address they generate is unique and they know all the details of which IP address was scanning their system at what time when they generated that address, and if anyone ever tries to send anything to that address not only are they automatically blacklisted but so is the IP address that did the original scan, and so on. However, this doesn't help you if you're just trying to run some mailing lists for your customers or your community. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From cpreston at glasshouse.com Fri Jun 1 02:22:33 2007 From: cpreston at glasshouse.com (Curtis Preston) Date: Thu, 31 May 2007 20:22:33 -0400 Subject: [Mailman-Users] ANSWER: Integrating PHP to Mailman Message-ID: <4FBA0941CF3D9347889AA5FF23A809BE73F59A@ghmail02.glasshousetech.com> As some of you are aware, I've been integrating Mailman with PHP to integrate it into Joomla!. I had a version that did it using command line options, but that didn't work for a lot of people, so I did some work to figure out how to do it via the file_get_contents function in PHP. I have pulled it off and my Joomla! component is just about ready to go out to the community, but I thought I'd send a non-Joomla! version to show how to use PHP to administer Mailman. Attached is a demo script that will demonstrate how I did this. Hopefully you should be able to look at the script and its output and learn how to do what YOU need to do. To use the script, put it in the doc directory of your web server, calling it mailman.php. Then edit it and change the value of $domain to your domain, change $email to some valid email address, and change $adminpw to the admin password of your site. Leave diag at 1 to see the most information. Set it to 0 to turn off most of it, and set it to 2 for debugging. Then run yourdomain/mailman.php and watch the show. 1. List all the lists on your server 2. List all the lists that the email address you supplied is subscribe to, and how they're subscribed (digest or regular) 3. Do #2 again in a different way 4. Unsubscribe the email address you gave from all lists 5. Subscribe the email address you gave to all lists 6. Change the subscription to digest mode on all lists Here 'tis: -------cut and paste----- \n" ; #Build the command to list all lists $adminurl="http://" . $domain . "/mailman/admin"; if ( "$diag" == 1 ) {print "
adminurl=$adminurl\n" ;} #Run the command $content=file_get_contents("$adminurl","FALSE"); #Split the output into an array that we can loop through $array = preg_split('/\n/',$content); #For each line in the output foreach ($array as $element) { #As soon as we see the first line of the list of lists, say so if ( preg_match("/a href=.*strong.*strong/", "$element") ) { $table="on";} if ( "$diag" == 2 ) {print "
$table:$element";} if ( "$table" == "on" ) { #We're inside the table if ( preg_match("/a href=.*strong.*strong/", "$element") ) { #If it's the line with the listname... if ( "$diag" == 2 ) {print "
list:$element\n";} $listname = preg_replace("/.*href=./","","$element") ; $listname = preg_replace("/.>.*/","","$listname") ; $listname = preg_replace("/.*\//","","$listname") ; if ( "$diag" == 2 ) {print "
listname:$listname\n";} } else { if ( "$diag" == 2 ) {print "
desc:$element\n";} if ( preg_match("/.*<.td>/", "$element") ) { #If it's the line with the description $description = preg_replace("/.*/","","$element") ; $description = preg_replace("/<.td>.*/","","$description") ; $description = preg_replace("/<\/*em>/","","$description") ; $lists["$listname"] = "$description"; if ( "$diag" == 2 ) {print "
description:$description\n";} } } #When the table ends, there's no more work to do if ( preg_match("/<.table>/", "$element") ) { $table="off";} } } if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} #Loop through the associative array of lists and descriptions and print them out foreach ($lists as $listname => $desc) { if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} } if ( "$diag" == 1 ) {print "
ListnameDescription
$listname$desc
\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n" ;} #For each list foreach ($lists as $listname => $desc) { #Find email in list #Build a command to list if a member is in a given list $findemailurl="http://" . $domain . "/mailman/admin/" . $listname . "/members?findmember=" . $email . "&setmemberopts_btn&adminpw=" . "$adminpw"; if ( "$diag" == 1 ) {print "\n" ;} #Run the command $content=file_get_contents("$findemailurl","FALSE"); #The line we're looking for looks like this: # $digestline="INPUT name=." . $email . "_digest."; $ondigestline="INPUT name=." . $email . "_digest. type=.CHECKBOX. value=.on."; if ( "$diag" == 2 ) {print "\n" ;} if ( "$diag" == 2 ) {print "\n" ;} #if we found the member, then they'll be a line that has this string in it. if ( preg_match("/$digestline/", "$content") ) { #He's subscribed. Is he subscribe in digest format? if ( preg_match("/$ondigestline/", "$content") ) { if ( "$diag" == 1 ) {print "\n";} #Add the user listname and digest to the email_lists array $email_lists["$listname"] = "digest"; } else { if ( "$diag" == 1 ) {print "\n";} #Add the user listname and regular to the email_lists array $email_lists["$listname"] = "regular"; } } } if ( "$diag" == 1 ) {print "
ListnameRegular/Digest
FindMemberUrl=$findemailurl
$digestline
$ondigestline
$listnameDigest
$listnameRegular
\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n" ;} #This just demonstrates how to use the array that we created above foreach ($email_lists as $listy => $digesty) { if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} if ( "$diag" == 1 ) {print "\n";} } if ( "$diag" == 1 ) {print "
Same info again just to show you how to use the array.
$listy$digesty
\n";} if ( "$diag" == 1 ) {print "\n";} #Unsub email from all lists foreach ($lists as $listname => $desc) { #Build the command $unsuburl = "http://" . $domain . "/mailman/admin/" . $listname . "/members/remove?send_unsub_ack_to_this_batch=0&send_unsub_notifications _to_list_owner=0&unsubscribees_upload=" . $email . "&adminpw=" . $adminpw; if ( "$diag" == 1 ) {print "\n";} #Run the command $content=file_get_contents("$unsuburl","FALSE"); } if ( "$diag" == 1 ) {print "
UnsubscribeUrl:$unsuburl
\n";} #Sub email to all lists if ( "$diag" == 1 ) {print "\n";} foreach ($lists as $listname => $desc) { #Build the command $subscribeurl="http://" . $domain . "/mailman/admin/" . $listname . "/members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0¬ ification_to_list_owner=0&subscribees_upload=" . $email . "&adminpw=" . $adminpw ; if ( "$diag" == 1 ) {print "\n";} #Run the command $content=file_get_contents("$subscribeurl","FALSE"); } if ( "$diag" == 1 ) {print "
SubscribeUrl:$subscribeurl
\n";} #Set digest mode on for all lists if ( "$diag" == 1 ) {print "\n";} foreach ($lists as $listname => $desc) { #Build the command $turnondigesturl="http://" . $domain . "/mailman/admin/" . $listname . "/members?user=" . $email . "&" . $email . "_digest=1&setmemberopts_btn&adminpw=" . "$adminpw"; if ( "$diag" == 1 ) {print "\n";} #Run the command $content=file_get_contents("$turnondigesturl","FALSE"); } if ( "$diag" == 1 ) {print "
DigestOnUrl:$turnondigesturl
\n";} ?> --- W. Curtis Preston Author of O'Reilly's Backup & Recovery and Using SANs and NAS VP Data Protection GlassHouse Technologies From pfonville at troxlerlabs.com Fri Jun 1 14:27:34 2007 From: pfonville at troxlerlabs.com (Phil Fonville) Date: Fri, 1 Jun 2007 08:27:34 -0400 Subject: [Mailman-Users] Unable to Create New Lists Message-ID: <7C0A972FBA61F145984B9E890AA006A701131930@SNEEZY.troxlerlabs.local> My thanks to Dan Phillips, Mark Sapiro and any others who pointed out (correctly) that I needed fully qualified domain names for several items in mm_cfg.py. My problem evaporated after I changed DEFAULT_NNTP_HOST = 'bashful' DEFAULT_EMAIL_HOST = 'bashful' DEFAULT_URL_HOST - 'bashful' To DEFAULT_NNTP_HOST = 'bashful.troxlerlabs.local' DEFAULT_EMAIL_HOST = 'bashful.troxlerlabs.local' DEFAULT_URL_HOST - 'bashful.troxlerlabs.local' Thanks again. Phil From admin2 at enabled.com Fri Jun 1 15:47:57 2007 From: admin2 at enabled.com (Noah) Date: Fri, 01 Jun 2007 06:47:57 -0700 Subject: [Mailman-Users] OSError: [Errno 13] Permission denied:'/usr/local/mailman/archives/private/testing.mbox' [solved] In-Reply-To: References: Message-ID: <4660238D.3090406@enabled.com> Mark Sapiro wrote: > Noah >> Okay I give up. I am attempting to create a mail list called testing >> but I receive the error below. >> >> What are the proper permissions for /usr/local/mailman/archives/private/ ? >> >> >> # ls -dl /usr/local/mailman/archives/private/ >> drwxr-s--x 131 mailman mailman 3072 Feb 28 16:18 >> /usr/local/mailman/archives/private/ > > Should be those plus g+w, i.e. 2771 or rwxrws--x > > thanks Mark - that worked well From msapiro at value.net Fri Jun 1 20:32:43 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 01 Jun 2007 11:32:43 -0700 Subject: [Mailman-Users] multiple header_filter_rules? In-Reply-To: <71EDD17333FA81976377B366@bossland.lsit.ucsb.edu> References: <71EDD17333FA81976377B366@bossland.lsit.ucsb.edu> Message-ID: <4660664B.40608@value.net> David R Bosso wrote: > --On May 22, 2007 4:53:05 PM -0700 Mark Sapiro wrote: > >> David R Bosso wrote: >>> >>> I have 2 rules set up. For a given test message, Rule 1 does not match, >>> and Rule 2 does. If I have Rule 1 set to discard, and Rule 2 set to >>> Hold, the message is discarded. If I make the single change of setting >>> Rule 2 to Defer, then the message is accepted. >> >> Can you provide the contents of header_filter_rules, ideally from the >> output of >> >> bin/dumpdb lists//config.pck > > 'header_filter_rules': [ ( '^Return-Path: > (?!())', > 3, > False), > ('^Subject: test', 7, False)], > >> and a copy of >> the test message that illustrates the problem. > > A mail from me (rule 1 does not match), with the subject "test". Sorry for the long delay in following up. I have tried to duplicate this and I can't. I have the exact header_filter_rules as above and I send a message from me (also doesn't match rule 1) with 'Subject: test' and it is held by rule 2. I have tested with both the current SpamDetect.py rev 8146 and the 2.1.9 base rev 7750 with the same result. See for more including the source of these. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From patrick.krusenotto at googlemail.com Fri Jun 1 22:38:50 2007 From: patrick.krusenotto at googlemail.com (Patrick Krusenotto) Date: Fri, 01 Jun 2007 22:38:50 +0200 Subject: [Mailman-Users] Problem with googlemail Message-ID: <466083DA.303@googlemail.com> Hello altogether, My Name is Patrick and I am new to this list. I have got a serious problem with googlemail that I could'nt solve myself yet. I installed the mailman on top of exim on a suse virtual server under http://iqool.de/mailman It works perfect with all the accounts I tested it with. But there is one exception : Mailman does not get any mailings through my googlemail account. While all the administrative mailman-mails are coming through, all the member mailings are absorbed. The googlemail server gives no error. It just eats the mails and seems to throw them to /dev/null I tried over and over again, but had no success. I was very surprised, that I do not have any Problems to receive mails from mailman-users at python.org. Can anyone give me hint? Is there a special configuration, that is needed to let googlemail deliver the mails? Thank you very much for your help. Patrick From brad at shub-internet.org Fri Jun 1 22:58:00 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 1 Jun 2007 15:58:00 -0500 Subject: [Mailman-Users] Problem with googlemail In-Reply-To: <466083DA.303@googlemail.com> References: <466083DA.303@googlemail.com> Message-ID: On 6/1/07, Patrick Krusenotto wrote: > My Name is Patrick and I am new to this list. I have got a serious > problem with googlemail that I could'nt solve myself yet. Did you try searching the FAQ Wizard for "Google" or "Gmail"? If so, then you should have run across FAQ 3.42, which addresses one specific problem with Google at the bottom. Make sure to go back and re-read that one again. If you've already seen that and this is not the problem you're having, please help us understand how your situation is different from the one described. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From mymailmanlist at gmail.com Fri Jun 1 23:15:08 2007 From: mymailmanlist at gmail.com (Me Myself) Date: Fri, 1 Jun 2007 14:15:08 -0700 Subject: [Mailman-Users] Does Mailman require a MySQL database? Message-ID: Wasn't sure as the install was done automatically in cpanel. Thanks. From msapiro at value.net Fri Jun 1 23:40:13 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 1 Jun 2007 14:40:13 -0700 Subject: [Mailman-Users] Does Mailman require a MySQL database? In-Reply-To: Message-ID: Me Myself wrote: >Wasn't sure as the install was done automatically in cpanel. Subject to the implied caveat at , no MySQL or other DBM is required by standard mailman. All information is stored as Python pickles. -- 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 Jun 1 23:40:20 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 1 Jun 2007 16:40:20 -0500 Subject: [Mailman-Users] Does Mailman require a MySQL database? In-Reply-To: References: Message-ID: On 6/1/07, Me Myself wrote: > Wasn't sure as the install was done automatically in cpanel. Mailman does not make any use of MySQL, at least not in any version I know of that has been released to date. I can't speak for what cPanel may have done to the code after they took it from our website and then made modifications to it. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From jens.andersson at teleservice.net Fri Jun 1 23:13:00 2007 From: jens.andersson at teleservice.net (Jens Andersson) Date: Fri, 1 Jun 2007 23:13:00 +0200 Subject: [Mailman-Users] (no subject) Message-ID: <0BCD4AFDA07A9049928A34359243F7052EC4CE@sato.internal.teleservice.net> unsubscribe From mymailmanlist at gmail.com Fri Jun 1 23:17:10 2007 From: mymailmanlist at gmail.com (Me Myself) Date: Fri, 1 Jun 2007 14:17:10 -0700 Subject: [Mailman-Users] How do I change the footer and owner email address? Message-ID: I'm using cpanel and RHL. The URL at the bottom of the mailman mailings (that's supposed to go to our mailman page) is incorrect and produces a 404. Emails also that are supposed to go to mailman-owner are going to our web host postmaster instead. How do I correct this? Thanks in advance. From msapiro at value.net Sat Jun 2 01:14:02 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 1 Jun 2007 16:14:02 -0700 Subject: [Mailman-Users] How do I change the footer and owner email address? In-Reply-To: Message-ID: Me Myself wrote: >I'm using cpanel and RHL. See . >The URL at the bottom of the mailman mailings (that's supposed to go to our >mailman page) is incorrect and produces a 404. You might be able to adjust this by editing msg_footer on the admin Non-digest options page and digest_footer on the admin Digest options page. You might be able to set new list defaults for these with the mm_cfg.py settings DEFAULT_MSG_FOOTER and DEFAULT_DIGEST_FOOTER. >Emails also that are >supposed to go to mailman-owner are going to our web host postmaster >instead. If you can access the admin interface for the 'mailman' list and its 'owner' is not the postmaster address, then this is probably a cPanel feature. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cbraxton at iname.com Sat Jun 2 04:47:54 2007 From: cbraxton at iname.com (Carter Braxton) Date: Fri, 1 Jun 2007 21:47:54 -0500 Subject: [Mailman-Users] Maximum template size? Message-ID: <20070602024754.72C461F50B1@ws1-2.us4.outblaze.com> "Mark Sapiro" wrote: > The problem is the non-substitution '%' characters in your template. Ouch, this is another one of those "D'oh!" moments! Should have seen that, thanks for pointing it out. Is there a way to escape the "%" sign to prevent substitution? (I'm not very familiar with Python, have been a C programmer for 25 years.) Also, I was wondering, what is the reason for using the hex code "%40" instead of "@" in the URLs provided to users? -- Carter Braxton cbraxton at iname.com (Note: Any ads appended here are from my email service.) = AMP Violin Lessons on DVD Studio Lessons on DVD for Beginners and Intermediates. http://a8-asy.a8ww.net/a8-ads/adftrclick?redirectid=452d3305c117066abeb6338b13e75f27 From msapiro at value.net Sat Jun 2 05:42:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 1 Jun 2007 20:42:03 -0700 Subject: [Mailman-Users] Maximum template size? In-Reply-To: <20070602024754.72C461F50B1@ws1-2.us4.outblaze.com> Message-ID: Carter Braxton wrote: >"Mark Sapiro" wrote: >> The problem is the non-substitution '%' characters in your template. > >Ouch, this is another one of those "D'oh!" moments! Should have seen that, >thanks for pointing it out. Is there a way to escape the "%" sign to prevent >substitution? (I'm not very familiar with Python, have been a C programmer >for 25 years.) As I tried to indicate in my first reply, you escape the % by doubling it. I.e. A single % is an interpolation of some kind; a double %% is a literal %. >Also, I was wondering, what is the reason for using the hex >code "%40" instead of "@" in the URLs provided to users? It really isn't necessary to use %40 instead of @ in the user options URL. Mailman uses Python's urllib.quote() function to insure that various characters that can cause problems are represented as %xx codes. The urllib.quote() function encodes most non-alphanumeric characters although it is not necessary to do many of them. In short, if you want to use @ rather than %40 in the user options URL in your text, that shouldn't be a problem. The following URL types all work to retrieve the options (or options login) page for user at example.com. http://www.example.com/mailman/options/user at example.com http://www.example.com/mailman/options/user%40example.com http://www.example.com/mailman/options/user--at--example.com -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From r.barrett at openinfo.co.uk Sat Jun 2 11:10:42 2007 From: r.barrett at openinfo.co.uk (Richard Barrett) Date: Sat, 2 Jun 2007 10:10:42 +0100 Subject: [Mailman-Users] Pipermail --> MHonArc error Message-ID: <3104B592-2578-4708-B180-2CB378CC4511@openinfo.co.uk> Karl I just noticed the posting that you made to mailman-users. I think that what is triggering the exception is the way you are running arch. When you run arch the first time with the --wipe option, the existing HTML archive content is deleted and the new HTML archive content is generated by MHonArc from the list's .mbox content, assuming you have set the list to use mhonarc as it archive page generator. When you then run arch a second time without the the --wipe option you are telling MHonArc to generate HTML archive content from the same .mbox with the same content as on the previous run with the -- wipe option. But MHonArc does not find any new messages to add to the HTML archive as it is being handed the same messages again. Normally, MHonArc "optimises out" "duplicate" messages (based on Message-id: I believe). I think that when it finds nothing to add to the HTML archive it closes the pipe connection back to the Mailman process prematurely, leading to the exception. I will publish a revised MHonArc/Mailman integration patch to handle this condition but in the meantime you should be able avoid the problem by not running arch with the same input .mbox as on a previous run. No loss, as the second run of arch serves no useful purpose. Regards Richard On Tue May 1 21:56:17 CEST 2007 you posted the following to the mailman-users list: I am trying to convert a list from the Pipermail archiver to MhonArc. I can run /bin/arch --wipe listname successfully. I get this error when generating the MhonArc archive with /bin/arch listname Pickling archive state into /data/mailman/archives/private/listname/pipermail.pck Traceback (most recent call last): File "./arch", line 202, in ? main() File "./arch", line 190, in main archiver.processUnixMailbox(fp, start, end) File "/data/mailman/Mailman/Archiver/pipermail.py", line 576, in processUnixMailbox self.mhonarcProcessUnixMailbox(input, start, end) File "/data/mailman/Mailman/Archiver/pipermail.py", line 706, in mhonarcProcessUnixMailbox status = mhonarch_process.close() IOError: [Errno 32] Broken pipe If I switch back to Pipermail it will run successfully. It looks too that I miss March and April 2007 archives when trying to convert to MHonArc, but Pipermail generates them. Would this point to an problem in the .mbox file? --Karl From patrick.krusenotto at googlemail.com Sat Jun 2 16:14:54 2007 From: patrick.krusenotto at googlemail.com (Patrick Krusenotto) Date: Sat, 02 Jun 2007 16:14:54 +0200 Subject: [Mailman-Users] Problem with googlemail In-Reply-To: References: <466083DA.303@googlemail.com> Message-ID: <46617B5E.6080108@googlemail.com> Hi Brad, thank you for your info. The way google handles Mailing-Lists seems very odd to me. I now found the emails together with most of the mailman-list-emails in a special "spam"-Folder that can only be accessed via http (I use pop). I had to add the address of the mailing list to my contacts, to make google path the mails trough. Thank you very much. > Did you try searching the FAQ Wizard for "Google" or "Gmail"? If so, > then you should have run across FAQ 3.42, which addresses one specific > problem with Google at the bottom. Make sure to go back and re-read > that one again. From dbosso+lists.mailman at lsit.ucsb.edu Sun Jun 3 15:42:24 2007 From: dbosso+lists.mailman at lsit.ucsb.edu (David R Bosso) Date: Sun, 03 Jun 2007 06:42:24 -0700 Subject: [Mailman-Users] multiple header_filter_rules? Message-ID: <76AEABB5818E67EEBA49E3F4@[192.168.0.147]> --On Friday, June 1, 2007 11:32 AM -0700 Mark Sapiro wrote: > David R Bosso wrote: >> --On May 22, 2007 4:53:05 PM -0700 Mark Sapiro wrote: >> >>> David R Bosso wrote: >>>> >>>> I have 2 rules set up. For a given test message, Rule 1 does not >>>> match, and Rule 2 does. If I have Rule 1 set to discard, and Rule 2 >>>> set to Hold, the message is discarded. If I make the single change >>>> of setting Rule 2 to Defer, then the message is accepted. >>> >>> Can you provide the contents of header_filter_rules, ideally from the >>> output of >>> >>> bin/dumpdb lists//config.pck >> >> 'header_filter_rules': [ ( '^Return-Path: >> (?!())', >> 3, >> False), >> ('^Subject: test', 7, False)], >> >>> and a copy of >>> the test message that illustrates the problem. >> >> A mail from me (rule 1 does not match), with the subject "test". > > > Sorry for the long delay in following up. I have tried to duplicate this > and I can't. I have the exact header_filter_rules as above and I send a > message from me (also doesn't match rule 1) with 'Subject: test' and it > is held by rule 2. [whoops. sent this to the list with the wrong address the first time] Rule 1 is (I thought) Match Return-Path:, only if it's not followed by dbosso at lsit.ucsb.edu. This should discard for any Return Path but my email address, did you modify it to match yours, or do I have the (?!...) syntax wrong? -David > I have tested with both the current SpamDetect.py rev 8146 and the 2.1.9 > base rev 7750 with the same result. See > aint/mailman/Mailman/Handlers/SpamDetect.py?view=log> for more including > the source of these. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jun 3 18:56:33 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 3 Jun 2007 09:56:33 -0700 Subject: [Mailman-Users] multiple header_filter_rules? In-Reply-To: <76AEABB5818E67EEBA49E3F4@[192.168.0.147]> Message-ID: David R Bosso wrote: > >Rule 1 is (I thought) Match Return-Path:, only if it's not followed by >dbosso at lsit.ucsb.edu. This should discard for any Return Path but my email >address, did you modify it to match yours, or do I have the (?!...) syntax >wrong? My mistake. I didn't really look at the Rule 1 pattern. The pattern is correct for what you want and it works. It didn't discard my test messages because my test setup uses Exim and Exim's pipe driver doesn't add a Return-Path: header, so rule 1 didn't match because there was no Return-Path: at all. I retested using bin/inject to deliver the messages. A message with Return-path: Subject: test was discarded by rule 1. A message with Return-path: Subject: test was held by rule 2, so I am still unable to duplicate the problem. What's in Mailman's vette log for the discarded message that should be held by rule 2? If that doesn't offer a clue, I suggest you get and compare it to your Mailman/Handlers/SpamDetect.py to see if there is any difference. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From john.r.bell at cox.net Sun Jun 3 20:10:42 2007 From: john.r.bell at cox.net (John Bell) Date: Sun, 3 Jun 2007 11:10:42 -0700 Subject: [Mailman-Users] Edit to FAQ 3.11 How do I create a newsletter/announcement/one-way list? References: Message-ID: <000601c7a60a$819d6c50$e44a6f44@BLACKBOX> In FAQ 3.11 it mentions how to do the following: Features: Members join by filling in a form on your website (and replying to the confirmation email). They will be sent a welcome message that does not mention how to post to the list. They will receive your newsletters, with a footer that gives simple instructions for unsubscribing. Only authorized persons can post to the list (send the newsletters). (Note: For this FAQ we are discussing how to setup an announcement list for a band.) The post assumes that you have access to the command line. I'm website owner, and my host has set up the mailman feature, but I can only access the HTML admin pages to configure my mailing list. I don't have access to the source code or command line features. Like others, I want a one-way notification system - only I send messages to folks who want to join my mailing list to get news, etc, about my site. I found a workaround to both HTML and emails, but it's a but sneaky. So here is information for whom it may concern, and if appropriate perhaps someone could update the FAQ page. If I've done something completely unnessary and there's a simpler way to do this please also let me know. --- The following is a guide to setting up a newsletter type mailing list bypassing all HTML and emails from mailman to subscribers when they subscribe and unsubscribe. The only requirement is that you are able to create your own CGI scripts. I did this is perl and I assume this is also possible with other languages. First I went through all the options to ensure that a subscribing person would not get any email when they subscribed or unsubscribed, or due to other events. This is how I set it up (for the version I have, 2.1.9): All the following I set to no in general options: -Send password reminders - Send monthly password reminders - Send welcome message to newly subscribed members - Send goodbye message to members when they are unsubscribed - Send mail to poster when their posting is held for approval All the following is set to yes in general options: - Should the list moderators get immediate notice of new requests, as well as daily notices about collected ones - Should administrator get notices of subscribes and unsubscribes - Emergency moderation of all list traffic [probably not necessary but I'm paranoid] Under Privacy Options, subscription rules, - What steps are required for subscription = Require approval - Is the list moderator's approval required for unsubscription requests? = Yes These last two seemed to stop all emails when subscribing or unsubscribing - you as the moderator will get them all. However as you're also the only one sending out emails to the list this doesn't matter. Before sending anything, process all the requests, then send the message. The second step is to hide all the mailman HTML. I did this by creating my own perl script. On my own HTML page I have a simple form as follows (stripping all the formatting):
I.e. two parameters - email and status. The perl script 'subscribe.cgi' then does the following: If the user wants to subscribe I execute these lines: use LWP::Simple; [place at the top of the file] $link = "http://[my URL]/mailman/subscribe/[my mailman listname]?email=".$FORM{'email'}."\&email-button=Subscribe"; $webpage = get($link); And to unsubscribe: $link = "http://[my URL]/mailman/options/[my mailman listname]?email=".$FORM{'email'}."\&login-unsub=Unsubscribe"; $webpage = get($link); In other words, the script gets the page - executing the command, and instead of displaying the reulting HTML it gets captured by the variable $webpage which I can parse to display as I want, or ignore completely and do my own thing. Comments welcome! ----- Original Message ----- From: "Mark Sapiro" To: "David R Bosso" ; Sent: Sunday, June 03, 2007 9:56 AM Subject: Re: [Mailman-Users] multiple header_filter_rules? > David R Bosso wrote: >> >>Rule 1 is (I thought) Match Return-Path:, only if it's not followed by >>dbosso at lsit.ucsb.edu. This should discard for any Return Path but my >>email >>address, did you modify it to match yours, or do I have the (?!...) syntax >>wrong? > > > My mistake. I didn't really look at the Rule 1 pattern. The pattern is > correct for what you want and it works. It didn't discard my test > messages because my test setup uses Exim and Exim's pipe driver > doesn't add a Return-Path: header, so rule 1 didn't match because > there was no Return-Path: at all. > > I retested using bin/inject to deliver the messages. A message with > > Return-path: > Subject: test > > was discarded by rule 1. A message with > > Return-path: > Subject: test > > was held by rule 2, so I am still unable to duplicate the problem. > > What's in Mailman's vette log for the discarded message that should be > held by rule 2? > > If that doesn't offer a clue, I suggest you get > > and compare it to your Mailman/Handlers/SpamDetect.py to see if there > is any difference. > > -- > 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/john.r.bell%40cox.net > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From msapiro at value.net Sun Jun 3 23:37:53 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 3 Jun 2007 14:37:53 -0700 Subject: [Mailman-Users] Edit to FAQ 3.11 How do I create anewsletter/announcement/one-way list? In-Reply-To: <000601c7a60a$819d6c50$e44a6f44@BLACKBOX> Message-ID: John Bell wrote: > >The post assumes that you have access to the command line. I have updated the FAQ to indicate that beginning with Mailman 2.1.6, you can edit the subscribeack.txt (welcome message) template via the admin web interface. Also, the stuff in the FAQ about config_list is not a requirement. It is just an alternative to using the admin web interface. >I'm website >owner, and my host has set up the mailman feature, but I can only access the >HTML admin pages to configure my mailing list. I don't have access to the >source code or command line features. Like others, I want a one-way >notification system - only I send messages to folks who want to join my >mailing list to get news, etc, about my site. I looked through the FAQ and the only thing (other than the optional config_list stuff) mentioned there that requires more than access to the web admin interface is the part about adding OWNERS_CAN_ENABLE_PERSONALIZATION = 1 to mm_cfg.py which is only necessary if you want to personalize the list to include a personalized link to the user's options page in the msg_footer. >I found a workaround to both HTML and emails, but it's a but sneaky. So here >is information for whom it may concern, and if appropriate perhaps someone >could update the FAQ page. If I've done something completely unnessary and >there's a simpler way to do this please also let me know. > >--- > >The following is a guide to setting up a newsletter type mailing list >bypassing all HTML and emails from mailman to subscribers when they >subscribe and unsubscribe. The only requirement is that you are able to >create your own CGI scripts. I did this is perl and I assume this is also >possible with other languages. > >First I went through all the options to ensure that a subscribing person >would not get any email when they subscribed or unsubscribed, or due to >other events. This is how I set it up (for the version I have, 2.1.9): > >All the following I set to no in general options: > > -Send password reminders >- Send monthly password reminders >- Send welcome message to newly subscribed members >- Send goodbye message to members when they are unsubscribed >- Send mail to poster when their posting is held for approval > >All the following is set to yes in general options: > >- Should the list moderators get immediate notice of new requests, as well >as daily notices about collected ones >- Should administrator get notices of subscribes and unsubscribes >- Emergency moderation of all list traffic [probably not necessary but I'm >paranoid] > >Under Privacy Options, subscription rules, > >- What steps are required for subscription = Require approval >- Is the list moderator's approval required for unsubscription requests? = >Yes > >These last two seemed to stop all emails when subscribing or unsubscribing - >you as the moderator will get them all. However as you're also the only one >sending out emails to the list this doesn't matter. Before sending anything, >process all the requests, then send the message. > >The second step is to hide all the mailman HTML. I did this by creating my >own perl script. On my own HTML page I have a simple form as follows >(stripping all the formatting): > >
> > > > >
> >I.e. two parameters - email and status. > >The perl script 'subscribe.cgi' then does the following: > >If the user wants to subscribe I execute these lines: > > use LWP::Simple; [place at the top of the file] > > $link = "http://[my URL]/mailman/subscribe/[my mailman >listname]?email=".$FORM{'email'}."\&email-button=Subscribe"; > $webpage = get($link); > >And to unsubscribe: > > $link = "http://[my URL]/mailman/options/[my mailman >listname]?email=".$FORM{'email'}."\&login-unsub=Unsubscribe"; > $webpage = get($link); > >In other words, the script gets the page - executing the command, and >instead of displaying the reulting HTML it gets captured by the variable >$webpage which I can parse to display as I want, or ignore completely and do >my own thing. > >Comments welcome! What you describe presumably works for you, and what you've done to achieve your goal of eliminating (un)subscribe email seems fine, but it seems to me that this goal is distinct from the goal of a one-way/announce only list. Thus, it seems that this might be more appropriate in a separate FAQ. Finally, go to to see why it's not a good idea to hijack existing threads for new subjects. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ljacobs at shambhala.com Mon Jun 4 06:31:01 2007 From: ljacobs at shambhala.com (Leonard Jacobs) Date: Mon, 04 Jun 2007 00:31:01 -0400 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: References: Message-ID: <46639585.6060800@shambhala.com> > > On 5/29/07, Barry Warsaw wrote: > > >/ Does anybody else use Postfix 2.4? > / > Actually, I'm pretty sure we are currently using it on the NTP Public > Services Project pages at ntp.isc.org, which is the project I had > gotten involved in years ago, prior to getting involved in Mailman. > I got on this mailing list in order to help me figure out if it would > be a good idea to switch from Majordomo to Mailman, and I haven't > looked back since. > > Currently, these are the two primary open source projects where I > spend most of my time. > > > If you want to give it a test, I could install the latest postfix 2.5 > experimental or non-production patch releases on the python.org mail > servers, so that we can give the newer code a try. ;) > > > Seriously, I am quite convinced that the problem here is a > mis-configuration between Mailman and postfix, and that neither > program is necessarily "at fault". > > -- > Brad Knowles >, Consultant & Author > LinkedIn Profile: > Slides from Invited Talks: Still having problems with Maioman via Postfix 2.4, so I just upgraded to the stable patch 2.4.3. My edited mm_cfg.py file: MTA = 'Postfix' DEFAULT_URL_HOST = 'lists.shambhala.com' DEFAULT_EMAIL_HOST = 'lists.shambhala.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) OWNERS_CAN_ENABLE_PERSONALIZATION = 1 SMTPPORT = 25 SMTPHOST = '192.168.1.130' [user]# ifconfig | grep 130 inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0 [user]# postconf | grep version mail_version = 2.4.3 Yes, I have stopped & restarted Mailman after each mm_cfg.py change and no, there are no anti-virus or other rejections with postfix. Additionally I am not running SELinux on this box. After my recent Postfix upgrade to 2.4.3, my logs/smtp-failure contains: Jun 03 23:54:13 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308 at shambhala.com> Jun 03 23:54:19 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308 at shambhala.com> Jun 03 23:54:20 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308 at shambhala.com> Jun 03 23:54:21 2007 (29345) Low level smtp error: (4, 'Interrupted system call'), msgid: <46591BE4.3030308 at shambhala.com> Now one clue that might be relevant is that when creating test lists and testing sending messages to beta users of these lists, all works fine. But as soon as the list contains the actual number of users, in one case 5,100 members, in another 350 members, the mailings to the subscribers fail with the error as listed above. And there is no obvious throttling on the Postfix MTA. Think I should try downgrading to an earlier version of Postfix? It does seem like a recent upgrade of Postfix may have broken the connection that once did exist. Any other thoughts or suggestions would be appreciated. Thanks. --- [This E-mail scanned for viruses by Declude EVA] From brad at shub-internet.org Mon Jun 4 06:55:46 2007 From: brad at shub-internet.org (Brad Knowles) Date: Sun, 3 Jun 2007 23:55:46 -0500 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: <46639585.6060800@shambhala.com> References: <46639585.6060800@shambhala.com> Message-ID: On 6/4/07, Leonard Jacobs wrote: > Yes, I have stopped & restarted Mailman after each mm_cfg.py change and > no, there are no anti-virus or other rejections with postfix. > Additionally I am not running SELinux on this box. I haven't checked the earlier messages in this thread -- I'm assuming you have also done the stuff mentioned in FAQ 4.73 and 6.14? > Now one clue that might be relevant is that when creating test lists and > testing sending messages to beta users of these lists, all works fine. > But as soon as the list contains the actual number of users, in one case > 5,100 members, in another 350 members, the mailings to the subscribers > fail with the error as listed above. And there is no obvious throttling > on the Postfix MTA. What is your "SMTP_MAX_RCPTS" setting? Check both Defaults.py and mm_cfg.py. Also check the value of "SMTP_MAX_SESSIONS_PER_CONNECTION". Then compare against their companion values in your postfix configuration. If you don't define the specific companion values in your /etc/postfix/main.cf, then you may need to take a look at the output of "postconf -d" and look for them. See also the postfix documentation on these values, especially . -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From ljacobs at shambhala.com Mon Jun 4 07:21:33 2007 From: ljacobs at shambhala.com (Leonard Jacobs) Date: Mon, 04 Jun 2007 01:21:33 -0400 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: References: Message-ID: <4663A15D.8040508@shambhala.com> > > ubject: > Re: [Mailman-Users] Low level smtp error: Server not connected > From: > Leonard Jacobs > Date: > Mon, 04 Jun 2007 00:31:01 -0400 > To: > mailman-users at python.org > > To: > mailman-users at python.org > > Content-Transfer-Encoding: > 7bit > Precedence: > list > MIME-Version: > 1.0 > References: > > In-Reply-To: > > Message-ID: > <46639585.6060800 at shambhala.com> > Content-Type: > text/plain; charset=ISO-8859-1; format=flowed > Message: > 5 > > >> >> On 5/29/07, Barry Warsaw wrote: >> >> >/ Does anybody else use Postfix 2.4? >> / >> Actually, I'm pretty sure we are currently using it on the NTP Public >> Services Project pages at ntp.isc.org, which is the project I had >> gotten involved in years ago, prior to getting involved in Mailman. I >> got on this mailing list in order to help me figure out if it would >> be a good idea to switch from Majordomo to Mailman, and I haven't >> looked back since. >> >> Currently, these are the two primary open source projects where I >> spend most of my time. >> >> >> If you want to give it a test, I could install the latest postfix 2.5 >> experimental or non-production patch releases on the python.org mail >> servers, so that we can give the newer code a try. ;) >> >> >> Seriously, I am quite convinced that the problem here is a >> mis-configuration between Mailman and postfix, and that neither >> program is necessarily "at fault". >> >> -- >> Brad Knowles > >, Consultant >> & Author >> LinkedIn Profile: >> Slides from Invited Talks: > > > Still having problems with Maioman via Postfix 2.4, so I just upgraded > to the stable patch 2.4.3. My edited mm_cfg.py file: > MTA = 'Postfix' > DEFAULT_URL_HOST = 'lists.shambhala.com' > DEFAULT_EMAIL_HOST = 'lists.shambhala.com' > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > OWNERS_CAN_ENABLE_PERSONALIZATION = 1 > SMTPPORT = 25 > SMTPHOST = '192.168.1.130' > > [user]# ifconfig | grep 130 > inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0 > > [user]# postconf | grep version > mail_version = 2.4.3 > > Yes, I have stopped & restarted Mailman after each mm_cfg.py change > and no, there are no anti-virus or other rejections with postfix. > Additionally I am not running SELinux on this box. > > After my recent Postfix upgrade to 2.4.3, my logs/smtp-failure contains: > Jun 03 23:54:13 2007 (29345) Low level smtp error: (4, 'Interrupted > system call'), msgid: <46591BE4.3030308 at shambhala.com> > Jun 03 23:54:19 2007 (29345) Low level smtp error: (4, 'Interrupted > system call'), msgid: <46591BE4.3030308 at shambhala.com> > Jun 03 23:54:20 2007 (29345) Low level smtp error: (4, 'Interrupted > system call'), msgid: <46591BE4.3030308 at shambhala.com> > Jun 03 23:54:21 2007 (29345) Low level smtp error: (4, 'Interrupted > system call'), msgid: <46591BE4.3030308 at shambhala.com> > > Now one clue that might be relevant is that when creating test lists > and testing sending messages to beta users of these lists, all works > fine. But as soon as the list contains the actual number of users, in > one case 5,100 members, in another 350 members, the mailings to the > subscribers fail with the error as listed above. And there is no > obvious throttling on the Postfix MTA. > > Think I should try downgrading to an earlier version of Postfix? It > does seem like a recent upgrade of Postfix may have broken the > connection that once did exist. Any other thoughts or suggestions > would be appreciated. > > Thanks. > > --- > [This E-mail scanned for viruses by Declude EVA] > > > > > ------------------------------------------------------------------------ > > Subject: > Re: [Mailman-Users] Low level smtp error: Server not connected > From: > Brad Knowles > Date: > Sun, 3 Jun 2007 23:55:46 -0500 > To: > Leonard Jacobs , mailman-users at python.org > > To: > Leonard Jacobs , mailman-users at python.org > > Precedence: > list > MIME-Version: > 1.0 > References: > > <46639585.6060800 at shambhala.com> > In-Reply-To: > <46639585.6060800 at shambhala.com> > Message-ID: > > Content-Type: > text/plain; charset="us-ascii" ; format="flowed" > Message: > 6 > > > On 6/4/07, Leonard Jacobs wrote: > >> Yes, I have stopped & restarted Mailman after each mm_cfg.py change and >> no, there are no anti-virus or other rejections with postfix. >> Additionally I am not running SELinux on this box. > > I haven't checked the earlier messages in this thread -- I'm assuming > you have also done the stuff mentioned in FAQ 4.73 and 6.14? > >> Now one clue that might be relevant is that when creating test lists >> and >> testing sending messages to beta users of these lists, all works fine. >> But as soon as the list contains the actual number of users, in one >> case >> 5,100 members, in another 350 members, the mailings to the subscribers >> fail with the error as listed above. And there is no obvious throttling >> on the Postfix MTA. > > What is your "SMTP_MAX_RCPTS" setting? Check both Defaults.py and > mm_cfg.py. Also check the value of > "SMTP_MAX_SESSIONS_PER_CONNECTION". Then compare against their > companion values in your postfix configuration. If you don't define > the specific companion values in your /etc/postfix/main.cf, then you > may need to take a look at the output of "postconf -d" and look for them. > > See also the postfix documentation on these values, especially > . > > ------------------------------------------------------------------------ > > ------------------------------------------------------ > 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/ Yes, I have tried all the suggestions provided earlier in FAQ 4.73 & 6.14. I don't have any adjustments to the defaukt settings you mentioned in my mm_cfg.py file, but Defaults.py state: [user]# grep SESSIONS Mailman/Defaults.py SMTP_MAX_SESSIONS_PER_CONNECTION = 0 [root at tao mailman]# grep RCPTS Mailman/Defaults.py SMTP_MAX_RCPTS = 500 In /etc/postfix/main.cf I have the following settings: smtpd_client_connection_limit_exceptions = $mynetworks local_destination_concurrency_limit = 2 default_destination_concurrency_limit = 100 default_destination_recipient_limit = 50 maximal_backoff_time = 1000s minimal_backoff_time = 300s Think these need tweaking? Which other postfix settings are the "companion values" to those Mailman ones? Thanks. --- [This E-mail scanned for viruses by Declude EVA] From brad at shub-internet.org Mon Jun 4 07:33:46 2007 From: brad at shub-internet.org (Brad Knowles) Date: Mon, 4 Jun 2007 00:33:46 -0500 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: <4663A15D.8040508@shambhala.com> References: <4663A15D.8040508@shambhala.com> Message-ID: On 6/4/07, Leonard Jacobs wrote: > Yes, I have tried all the suggestions provided earlier in FAQ 4.73 & 6.14. Could you also trim your replies? Including several levels of additional material from previous replies makes it very difficult to tell who has said what, and where the new text is. > In /etc/postfix/main.cf I have the following settings: As I said, you may also need to look at the output of "postconf -d", because the program may be taking some defaults that have been compiled in as opposed to being defined in your configuration file. > Which other postfix settings are the "companion values" to those Mailman > ones? See the link I previously posted. You should pay special attention to the "Recipients" section further down that page (at ). Just because the standard postfix source compiled-in value may be higher than the value you define in your mm_cfg.py file, doesn't mean that the people who created the binary package for your platform actually used that default when building the package. You need to check what they actually provided to you, and you can only do that through the output of "postconf -d". -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From scry_mr at yahoo.ca Mon Jun 4 15:28:39 2007 From: scry_mr at yahoo.ca (Juan Miscaro) Date: Mon, 4 Jun 2007 09:28:39 -0400 (EDT) Subject: [Mailman-Users] deleting users over multiple lists Message-ID: <271724.98513.qm@web63908.mail.re1.yahoo.com> Is there any way to delete subscriber addresses over multiple lists easily (command line)? I am using Mailman 2.1.8 on OpenBSD 4.0. I also want to be able to remove all addresses from particular domains. I am looking at the remove_members command but I'm not sure. I don't want to mess up. Thank you. Juan __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From scry_mr at yahoo.ca Mon Jun 4 16:09:12 2007 From: scry_mr at yahoo.ca (Juan Miscaro) Date: Mon, 4 Jun 2007 10:09:12 -0400 (EDT) Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <46641499.4050303@agora-net.com> Message-ID: <100395.60256.qm@web63915.mail.re1.yahoo.com> --- Ryan Steele wrote: > Juan Miscaro wrote: > > Is there any way to delete subscriber addresses over multiple lists > > easily (command line)? I am using Mailman 2.1.8 on OpenBSD 4.0. > > > > > > Maybe something like this for a single user: > for list in `bin/list_lists | awk '{print $1}'` do; > bin/remove_members $list username > done Can't I just go $ bin/remove_members --fromall user at example.com ? > ...or this for multiple users > users='foo bar baz' > for list in `bin/list_lists | awk '{print $1}'` do; > bin/remove_members $list users > done > > > I also want to be able to remove all addresses from particular > domains. > > > > You mean, remove all members from all lists belonging to a particular > domain name? Yes, that is what I mean. I want to be able to go $ bin/remove_members --fromall *@example.com but I read on the mailman FAQ that regexp/globs are not permitted. Juan Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com From steele at agora-net.com Mon Jun 4 15:33:13 2007 From: steele at agora-net.com (Ryan Steele) Date: Mon, 04 Jun 2007 09:33:13 -0400 Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <271724.98513.qm@web63908.mail.re1.yahoo.com> References: <271724.98513.qm@web63908.mail.re1.yahoo.com> Message-ID: <46641499.4050303@agora-net.com> Juan Miscaro wrote: > Is there any way to delete subscriber addresses over multiple lists > easily (command line)? I am using Mailman 2.1.8 on OpenBSD 4.0. > > Maybe something like this for a single user: for list in `bin/list_lists | awk '{print $1}'` do; bin/remove_members $list username done ...or this for multiple users users='foo bar baz' for list in `bin/list_lists | awk '{print $1}'` do; bin/remove_members $list users done > I also want to be able to remove all addresses from particular domains. > You mean, remove all members from all lists belonging to a particular domain name? > I am looking at the remove_members command but I'm not sure. I don't > want to mess up. > > Thank you. > > Juan > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > ------------------------------------------------------ > 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/steele%40agora-net.com > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > -- Ryan Steele Systems Administrator From steele at agora-net.com Mon Jun 4 16:00:03 2007 From: steele at agora-net.com (Ryan Steele) Date: Mon, 04 Jun 2007 10:00:03 -0400 Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <100395.60256.qm@web63915.mail.re1.yahoo.com> References: <100395.60256.qm@web63915.mail.re1.yahoo.com> Message-ID: <46641AE3.2020806@agora-net.com> Juan Miscaro wrote: > --- Ryan Steele wrote: > > >> Juan Miscaro wrote: >> >>> Is there any way to delete subscriber addresses over multiple lists >>> easily (command line)? I am using Mailman 2.1.8 on OpenBSD 4.0. >>> >>> >>> >> Maybe something like this for a single user: >> for list in `bin/list_lists | awk '{print $1}'` do; >> bin/remove_members $list username >> done >> > > Can't I just go > > $ bin/remove_members --fromall user at example.com > > ? > > Yes, but only if you want them removed from every list. Your request indicated to me you only wanted to remove them from a subset of all the lists - e.g., you said "multiple lists", not "all lists". >> ...or this for multiple users >> users='foo bar baz' >> for list in `bin/list_lists | awk '{print $1}'` do; >> bin/remove_members $list users >> done >> >> >>> I also want to be able to remove all addresses from particular >>> >> domains. >> >>> >>> >> You mean, remove all members from all lists belonging to a particular >> domain name? >> > > Yes, that is what I mean. > > I want to be able to go > > $ bin/remove_members --fromall *@example.com > > but I read on the mailman FAQ that regexp/globs are not permitted. > > Juan > > You want to use bin/withlist, which will support regular expressions. > > Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com > -- Ryan Steele Systems Administrator From msapiro at value.net Tue Jun 5 03:19:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 4 Jun 2007 18:19:57 -0700 Subject: [Mailman-Users] Low level smtp error: Server not connected In-Reply-To: <4663A15D.8040508@shambhala.com> Message-ID: Leonard Jacobs wrote: >I don't have any adjustments to the defaukt settings you mentioned in my >mm_cfg.py file, but Defaults.py state: > >[user]# grep SESSIONS Mailman/Defaults.py >SMTP_MAX_SESSIONS_PER_CONNECTION = 0 >[root at tao mailman]# grep RCPTS Mailman/Defaults.py >SMTP_MAX_RCPTS = 500 Please see my reply in this thread at . >In /etc/postfix/main.cf I have the following settings: >smtpd_client_connection_limit_exceptions = $mynetworks >local_destination_concurrency_limit = 2 >default_destination_concurrency_limit = 100 >default_destination_recipient_limit = 50 The above seems possibly inconsistent with SMTP_MAX_RCPTS = 500 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jun 5 03:47:05 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 4 Jun 2007 18:47:05 -0700 Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <46641AE3.2020806@agora-net.com> Message-ID: Ryan Steele wrote: >Juan Miscaro wrote: >> I want to be able to go >> >> $ bin/remove_members --fromall *@example.com >> >> but I read on the mailman FAQ that regexp/globs are not permitted. >> >> Juan >> >> > >You want to use bin/withlist, which will support regular expressions. Well, you can do anything with withlist, but you have to write the Python script to do it. There is no Mailman MailList method that directly supports deleting all members matching a regexp. It seems to me that the easiest way to do this is to use bin/find_member which does accept regexps to create a list of members to be deleted and then use bin/remove_members to process that list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From spyropolymiadis at kromestudios.com Tue Jun 5 03:32:01 2007 From: spyropolymiadis at kromestudios.com (Spyro Polymiadis) Date: Tue, 05 Jun 2007 11:02:01 +0930 Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <46641AE3.2020806@agora-net.com> References: <100395.60256.qm@web63915.mail.re1.yahoo.com> <46641AE3.2020806@agora-net.com> Message-ID: <4664BD11.30203@kromestudios.com> Ive come up with my own little function.. its not ideal but certainly does the job - no hiccups so far with it... basically i have a script called unsubuser, it prompts you for the username of the person you wish to unsub from lists, the it calls this function i wrote, displays the lists that person is subscribed to, and if its ok, press enter to begin the removal... unsubscribe () ( cd /var/lib/mailman/lists/ #This will search for instances of the username in the available lists and chomp the output to a file that contains just the listnames grep $USERNAME * -R | sed -e s"/\// /g" | grep Binary | awk '{print $3}' | sort -u > /tmp/sub echo "This will remove $USERNAME from these lists: " cat /tmp/sub echo "Press ENTER to continue (no going back) or Control-C to quit" read -e #This unsubs the users from the lists in the file for d in `cat /tmp/sub` ; do echo "$USERNAME"@domain.com | remove_members -f - $d ; echo "Removing subscription from $d" ; done ) The only flaw i see with it, is the listadmins email address is in each of the lists, but not necessarily a member of them.. so when you go to remove a person who is also a list admin it shows all the lists... but the function still works... I would like to see a more sane way of unsubbing a person from all lists easier though... Cheers Spyro Ryan Steele wrote: > Juan Miscaro wrote: > >> --- Ryan Steele wrote: >> >> >> >>> Juan Miscaro wrote: >>> >>> >>>> Is there any way to delete subscriber addresses over multiple lists >>>> easily (command line)? I am using Mailman 2.1.8 on OpenBSD 4.0. >>>> >>>> >>>> >>>> >>> Maybe something like this for a single user: >>> for list in `bin/list_lists | awk '{print $1}'` do; >>> bin/remove_members $list username >>> done >>> >>> >> Can't I just go >> >> $ bin/remove_members --fromall user at example.com >> >> ? >> >> >> > > Yes, but only if you want them removed from every list. Your request > indicated to me you only wanted to remove them from a subset of all the > lists - e.g., you said "multiple lists", not "all lists". > > >>> ...or this for multiple users >>> users='foo bar baz' >>> for list in `bin/list_lists | awk '{print $1}'` do; >>> bin/remove_members $list users >>> done >>> >>> >>> >>>> I also want to be able to remove all addresses from particular >>>> >>>> >>> domains. >>> >>> >>>> >>>> >>>> >>> You mean, remove all members from all lists belonging to a particular >>> domain name? >>> >>> >> Yes, that is what I mean. >> >> I want to be able to go >> >> $ bin/remove_members --fromall *@example.com >> >> but I read on the mailman FAQ that regexp/globs are not permitted. >> >> Juan >> >> >> > > You want to use bin/withlist, which will support regular expressions. > > >> Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com >> >> > > > 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 Tue Jun 5 04:16:31 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 4 Jun 2007 19:16:31 -0700 Subject: [Mailman-Users] deleting users over multiple lists In-Reply-To: <4664BD11.30203@kromestudios.com> Message-ID: Spyro Polymiadis >I would like to see a more sane way of unsubbing a person from all lists >easier though... As noted in the post you quoted, to remove a single address from all lists. bin/remove_members --fromall user at example.com See my reply at for my thoughts on removing all members matching some regexp from all lists. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Tue Jun 5 21:11:16 2007 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 5 Jun 2007 12:11:16 -0700 Subject: [Mailman-Users] question about moving list and archives Message-ID: <27572d930706051211r660a49fcie7240cede185398@mail.gmail.com> I have moved a list from another mailman installation. I moved the list files and the archives and then ran fix_url. Everything looks good except for the To: address in individual messages in the archive. It still has the old URL/mail address. Also, the link labeled 'More Info on this List...." still points to the old URL. So, what else do I need to do? Does the arch utility take care of this? It was my understanding that the arch utility was for rebuilding an archive after editing it or removing messages. Also, the documentation says something like this: /bin/arch mylist archives/private/mylist.mbox/mylist.mbox My lists don't have a mylist.mbox file in the mylist.mbox directory. Any advice would be helpful. -- Christopher Adams adamsca at gmail.com From art.campbell at gmail.com Tue Jun 5 21:26:25 2007 From: art.campbell at gmail.com (Art Campbell) Date: Tue, 5 Jun 2007 15:26:25 -0400 Subject: [Mailman-Users] Mailman and Community Server list gateway? Message-ID: A number of my list users have asked for a forum-like interface, for several reasons: ease of use, browser interface, easier to see old postings, etc. I'm open to setting something like that up as an addition to the list. But I want to integrate it with the existing mailman set up. I've found one package, published by www.communityserver.org, that is a decent forum and has a list gateway so that forum posts are echoed to the mailing list, and listers can reply to them via email (and the replies are added to the thread). So, the questions: Has anyone set up the Community Server and its list gateway with a mailman list? Problems? Any other software that does a comparable job? Thanks, Art -- Art Campbell art.campbell at gmail.com "... In my opinion, there's nothing in this world beats a '52 Vincent and a redheaded girl." -- Richard Thompson No disclaimers apply. DoD 358 From gilmore.126 at osu.edu Tue Jun 5 22:25:39 2007 From: gilmore.126 at osu.edu (Melinda Gilmore) Date: Tue, 5 Jun 2007 16:25:39 -0400 Subject: [Mailman-Users] Email subscription Message-ID: <009701c7a7af$ae895660$6ef39280@oitlan.oit.ohiostate.edu> I have been searching the archives and have not been able to find my answer. I just want to be able to subscribe by email. Does not seem to be working. Do you send to listname-subscribe at lists.blah blah blah and then subscribe. Is there something else that needs to be running on the machine. I just have a simple set up with Mailman 2.0 and sendmail. Any direction would be greatly appreciated. Melinda Gilmore Systems Engineer OIT/Enterprise Messaging 614-292-4953 From brad at shub-internet.org Tue Jun 5 22:42:39 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 5 Jun 2007 15:42:39 -0500 Subject: [Mailman-Users] Mailman and Community Server list gateway? In-Reply-To: References: Message-ID: On 6/5/07, Art Campbell wrote: > Any other software that does a > comparable job? Search the FAQ Wizard for "Joomla" or "PHPBB". -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Tue Jun 5 22:45:48 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 5 Jun 2007 13:45:48 -0700 Subject: [Mailman-Users] question about moving list and archives In-Reply-To: <27572d930706051211r660a49fcie7240cede185398@mail.gmail.com> Message-ID: Christopher Adams wrote: >I have moved a list from another mailman installation. I moved the >list files and the archives and then ran fix_url. Everything looks >good except for the To: address in individual messages in the archive. >It still has the old URL/mail address. Also, the link labeled 'More >Info on this List...." still points to the old URL. > >So, what else do I need to do? Does the arch utility take care of >this? It was my understanding that the arch utility was for rebuilding >an archive after editing it or removing messages. Also, the >documentation says something like this: > >/bin/arch mylist archives/private/mylist.mbox/mylist.mbox > >My lists don't have a mylist.mbox file in the mylist.mbox directory. >Any advice would be helpful. You don't have the mylist.mbox file, because you didn't move it from the old installation. It was really the only archive file you needed to move. Without it, you can't rebuild the archives, and rebuilding is the way to fix the issues above. If you can get the .mbox file, then simply running bin/arch --wipe mylist will recreate the HTML archive and will fix the 'More Info on this List....' links. However, it is a good idea to first check the .mbox for unescaped From_ lines using bin/cleanarch. Where are you seeing the To: address in individual messages in the archive? Normally the HTML archive contains no message headers. If you are seeing this in quotes of prior posts, the only way to change that is to edit the .mbox prior to running bin/arch. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Tue Jun 5 22:53:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 5 Jun 2007 13:53:35 -0700 Subject: [Mailman-Users] Email subscription In-Reply-To: <009701c7a7af$ae895660$6ef39280@oitlan.oit.ohiostate.edu> Message-ID: Melinda Gilmore wrote: >I have been searching the archives and have not been able to find my answer. >I just want to be able to subscribe by email. Does not seem to be working. >Do you send to listname-subscribe at lists.blah blah blah and then subscribe. >Is there something else that needs to be running on the machine. I just >have a simple set up with Mailman 2.0 and sendmail. Any direction would be >greatly appreciated. If this is really Mailman 2.0, I think you have to send a 'subscribe' command to listname-request at lists.blah blah blah. The listname-subscribe and listname-join addresses were first introduced in Mailman 2.1. If it's really Mailman 2.1, and you get no response to a message to listname-subscribe, see . Also check the list's Privacy options...->Subscription rules->subscribe_policy. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Tue Jun 5 23:41:53 2007 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 5 Jun 2007 14:41:53 -0700 Subject: [Mailman-Users] question about moving list and archives In-Reply-To: References: <27572d930706051211r660a49fcie7240cede185398@mail.gmail.com> Message-ID: <27572d930706051441r110cd696m517ecc9074dac8d6@mail.gmail.com> Mark, Yes, you're right about the list.mbox file. This was given to me by someone else and I was surprised that the mbox file wasn't included. Does this mean that a new mbox file will be created with the next post? How do messages append to the archive if there is no mbox file? I have other lists that have been archiving for years and have no mbox file. I guess I am a bit confused by the use of the mbox file for archives. On 6/5/07, Mark Sapiro wrote: > Christopher Adams wrote: > > >I have moved a list from another mailman installation. I moved the > >list files and the archives and then ran fix_url. Everything looks > >good except for the To: address in individual messages in the archive. > >It still has the old URL/mail address. Also, the link labeled 'More > >Info on this List...." still points to the old URL. > > > >So, what else do I need to do? Does the arch utility take care of > >this? It was my understanding that the arch utility was for rebuilding > >an archive after editing it or removing messages. Also, the > >documentation says something like this: > > > >/bin/arch mylist archives/private/mylist.mbox/mylist.mbox > > > >My lists don't have a mylist.mbox file in the mylist.mbox directory. > >Any advice would be helpful. > > > You don't have the mylist.mbox file, because you didn't move it from > the old installation. It was really the only archive file you needed > to move. Without it, you can't rebuild the archives, and rebuilding is > the way to fix the issues above. > > If you can get the .mbox file, then simply running > > bin/arch --wipe mylist > > will recreate the HTML archive and will fix the 'More Info on this > List....' links. However, it is a good idea to first check the .mbox > for unescaped From_ lines using bin/cleanarch. > > Where are you seeing the To: address in individual messages in the > archive? Normally the HTML archive contains no message headers. If you > are seeing this in quotes of prior posts, the only way to change that > is to edit the .mbox prior to running bin/arch. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Christopher Adams adamsca at gmail.com From msapiro at value.net Wed Jun 6 00:37:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 5 Jun 2007 15:37:59 -0700 Subject: [Mailman-Users] question about moving list and archives In-Reply-To: <27572d930706051441r110cd696m517ecc9074dac8d6@mail.gmail.com> Message-ID: Christopher Adams wrote: > >Yes, you're right about the list.mbox file. This was given to me by >someone else and I was surprised that the mbox file wasn't included. >Does this mean that a new mbox file will be created with the next >post? Yes, but it will contain only that and subsequent posts. It won't contain any of the prior posts. >How do messages append to the archive if there is no mbox file? The pipermail archives and the .mbox file are independent. What is maintained as messages are posted depends on the setting of ARCHIVE_TO_MBOX. Defaults.py has the following # ARCHIVE_TO_MBOX #-1 - do not do any archiving # 0 - do not archive to mbox, use builtin mailman html archiving only # 1 - archive to mbox to use an external archiving mechanism only # 2 - archive to both mbox and builtin mailman html archiving - # use this to make both external archiving mechanism work and # mailman's builtin html archiving. the flat mail file can be # useful for searching, external archivers, etc. ARCHIVE_TO_MBOX = 2 The references to external archiving assume that an external archiver will use the .mbox file, but this isn't necessarily the case. The default setting archives messages to both the .mbox and the pipermail archive. The pipermail archive can be rebuilt from the .mbox, but not vice versa >I have other lists that have been archiving for years and have no mbox >file. I guess I am a bit confused by the use of the mbox file for >archives. It seems that perhaps you have (had) set ARCHIVE_TO_MBOX to 0 in mm_cfg.py. If you don't have a .mbox file, it is possible to create one by concatenating all the periodic .txt files, but there are problems with this as email addresses may have been obscured and many of the original message headers are missing. In the absense of any .mbox file, the only way to fix the listinfo links in the HTML archive is by editing the individual HTML files. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jenred at gmail.com Wed Jun 6 01:07:48 2007 From: jenred at gmail.com (Jennifer Redman) Date: Tue, 5 Jun 2007 16:07:48 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes Message-ID: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> Hello! Trying to setup Mailman with Postfix 2.5 on FreeBSD 6.2. The web part works fine. However, the integration with Postfix -- not so good, appears to be something to do with the Virtual Mailbox setup. Messages keep bouncing with : The mail system
(expanded from
): unknown user: "main at foo.org"
Below please find my main.cf and mm_cfg.py, vhosts, and vmaps. I've pretty much tried every modification I can find in the postfix/mailman/freebsd faq's, docs in addition to some tinkering of my own. When a list is created the virtual-mailman gets updated and "appears to be correct." Anyone able to take a look as say "oh this isn't working because of x?" Thanks, Jen Here is my main.cf: queue_directory = /var/spool/postfix command_directory = /usr/local/sbin daemon_directory = /usr/local/libexec/postfix mail_owner = postfix mynetworks = 192.168.1.0/24 127.0.0.0/8 xxx.xx.xx.xx/29 debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin xxgdb $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/local/sbin/sendmail newaliases_path = /usr/local/bin/newaliases html_directory = no manpage_directory = /usr/local/man sample_directory = /usr/local/etc/postfix readme_directory = no alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = $mydomain mailbox_size_limit = 0 inet_interfaces = all #Virtual Mailboxes for blah.org, foo.org, blah.com virtual_mailbox_domains = /usr/local/etc/postfix/vhosts.txt virtual_mailbox_base = /var/spool/vmail virtual_mailbox_maps = hash:/usr/local/etc/postfix/vmaps.txt virtual_minimum_uid = 100 virtual_uid_maps = static:1002 virtual_gid_maps = static:1002 virtual_alias_maps = hash:/etc/postfix/valias.txt, hash:/usr/local/mailman/data/virtual-mailman # For SMTP-AUTH smtpd_use_tls = yes smtpd_tls_auth_only = yes smtpd_tls_key_file = /etc/ssl/private/newname.pem smtpd_tls_cert_file = /etc/ssl/certs/newname.pem #smtpd_tls_CAfile = /usr/local/etc/postfix/ssl/permit.pem smtpd_tls_loglevel = 3 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom #For SMTP-AUTH smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_relay_restrictions = permit_sasl_authenticated #Mailman recipient_delimiter = + owner_request_special = no Here are the relevant entries from mm_cfg.py DEFAULT_EMAIL_HOST = 'lists.blah.org' DEFAULT_URL_HOST = 'lists.blah.org' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.blah.org'] Entries from vhosts.txt: foo.org OK blah.org OK blah.com OK lists.blah.org OK Entries from vmaps: jen at foo.org foo.org/jen/ jen at blah.org blah.org/jen/ jen at blah.com blah.com/jen/ From msapiro at value.net Wed Jun 6 01:42:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 5 Jun 2007 16:42:49 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5Virtual Mailboxes In-Reply-To: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> Message-ID: Jennifer Redman wrote: > >Here is my main.cf: > >alias_maps = hash:/etc/aliases Try alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases You may need to run postalias after making this change. See -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jenred at gmail.com Wed Jun 6 02:15:13 2007 From: jenred at gmail.com (Jennifer Redman) Date: Tue, 5 Jun 2007 17:15:13 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5Virtual Mailboxes In-Reply-To: References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> Message-ID: <93f118f0706051715l4170ed94k3be93d29d8bd7b8d@mail.gmail.com> > Try > > alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases > > You may need to run postalias after making this change. Ok tried this approach. Same error. I was actually following the instructions from 6.1.2 Virtual Domains with the original configuration....Thank you very much for the suggestion though. See > > I think I may have the above memorized at this point ;>. I believe the problem is something to do with the virtual mailbox setup. Postfix instructions are here: http://www.postfix.org/VIRTUAL_README.html "There is one major limitation: virtual aliases and virtual mailboxes can't directly deliver to mailing list managers such as majordomo. The solution is to set up virtual aliases that direct virtual addresses to the local delivery agent: /etc/postfix/main.cf : virtual_alias_maps = hash:/etc/postfix/virtual /etc/postfix/virtual : listname-request at example.com listname-request listname at example.com listname owner-listname at example.com owner-listname /etc/aliases: listname: "|/some/where/majordomo/wrapper ..." owner-listname: ... listname-request: ... " I believe the above example is for Majordomo -- having trouble translating for Mailman. Any ideas? From msapiro at value.net Wed Jun 6 02:49:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 5 Jun 2007 17:49:47 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix2.5Virtual Mailboxes In-Reply-To: <93f118f0706051715l4170ed94k3be93d29d8bd7b8d@mail.gmail.com> Message-ID: Jennifer Redman wrote: >> Try >> >> alias_maps = hash:/etc/aliases, hash:/usr/local/mailman/data/aliases >> >> You may need to run postalias after making this change. > > >Ok tried this approach. Same error. I was actually following the >instructions from 6.1.2 Virtual Domains with the original >configuration....Thank you very much for the suggestion though. 6.1.2 is a suplement to, not a replacement for 6.1.1. > >See >> >> I think I may have the above memorized at this point ;>. > >I believe the problem is something to do with the virtual mailbox setup. >Postfix instructions are here: > >http://www.postfix.org/VIRTUAL_README.html > >"There is one major limitation: virtual aliases and virtual mailboxes can't >directly deliver to mailing list managers such as majordomo. The solution is >to set up virtual aliases that direct virtual addresses to the local >delivery agent: > >/etc/postfix/main.cf : > virtual_alias_maps > = >hash:/etc/postfix/virtual > >/etc/postfix/virtual : > listname-request at example.com listname-request > listname at example.com listname > owner-listname at example.com owner-listname > >/etc/aliases: > listname: "|/some/where/majordomo/wrapper ..." > owner-listname: ... > listname-request: ... > >" > >I believe the above example is for Majordomo -- having trouble translating >for Mailman. Any ideas? I'm not really a Postfix guy at all. Others on the mailman-users list know a lot more than I about Postfix, but the mailman translation of the above is straightforward. Mailman creates data/virtual-mailman* which corresponds to the mailman portion of/etc/postfix/virtual above and which maps in your case listname at lists.blah.org listname listname-bounces at lists.blah.org listname-bounces etc. i.e. it maps the address at lists.blah.org addresses to the corresponding local addresses. Then the mailman created data/aliases* pipes those local addresses to the mailman wrapper. This corresponds to the mailman portion of /etc/aliases. Possibly there is a permissions issue. What does ls -l mailman/data show? Also, what's in mailman/data/aliases and mailman/data/virtual-mailman? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From rr6 at columbia.edu Wed Jun 6 10:24:39 2007 From: rr6 at columbia.edu (Sekhar Ramakrishnan) Date: Wed, 06 Jun 2007 04:24:39 -0400 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits Message-ID: <46663707.20059.57B464@rr6.columbia.edu> This is my first post and I apologize if this has been dealt with; I was not able to find the right way to search the archives. I also apologize for the length. I administer half a dozen lists with membership ranging from 100 to 500, the number of messages ranging from 1 to 30 a day on each list, but monthly bandwidth for all lists together under 4 GB. A small commercial place where our domain was hosted recently decided to stop supporting Mailman, partly because their version of cPanel didn't include Mailman space in the user's quota. We found a number of places that offered "unlimited" Mailman lists, chose one and moved everything there via a cPanel backup. The move worked fine, and all the Mailman archives were intact. A couple of days later, we found that some messages were not going through and learned from the support people that there was an hourly limit on the number of messages - the 250 limit meant that a list with 300 people could not get even a single message out, and that if a message went out to a list with 200, there could not be another message for an hour. The only solution they offer is for us to get a dedicated server, which costs about ten times as much and is far beyond what we need by way of bandwidth. What we found upsetting (besides the policy being unannounced) was that other places we contacted all have similar hourly limits, even as they all advertise "unlimited" mailing lists. We are not sure what the reason is for these limits. Is it that the SMTP servers cannot tell the difference between Mailman mail and other mail so the places are afraid of spammers giving their servers a bad name? Or is it that SMTP takes up so much resource that a limit is necessary? Finally, and this is the main reason for this post, are there commercial places that support Mailman with more reasonable limits on the number of messages? Thank you all for any advice. Sekhar From ivanlan at pauahtun.org Wed Jun 6 14:38:37 2007 From: ivanlan at pauahtun.org (Ivan Van Laningham) Date: Wed, 06 Jun 2007 06:38:37 -0600 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits In-Reply-To: <46663707.20059.57B464@rr6.columbia.edu> References: <46663707.20059.57B464@rr6.columbia.edu> Message-ID: <4666AACD.6050007@pauahtun.org> Hi All-- I run ten to eleven mailing lists, with, just as you have, 100-500 members apiece. I have a dedicated server with Godaddy. They told me that yes, I could run mailing lists. They didn't tell me in advance that there was a daily limit of 1000 outgoing messages per day. I discovered that as soon as the first mailing list went into operation and I had to wait 24 hours for the counter to be reset. In order to raise the limit to something reasonable, I had to provide documentation to Godaddy through some automated tools they have. I think in the end it amounted to about 20 pages of justification. It was definitely a pain, because their base assumption is that mailing lists are newsletters sent to customers. It follows that if you are a capitalist with customers, you lust to become an evil spammer, and only the fear of legal action and forcible disconnection keeps you from inundating the net with enlargement ads. You have to provide samples of your "newsletters," which is a bit difficult if you want to provide a modicum of privacy for your subscribers. I made calculations based on the size of the lists and the number of subscribers and requested my limit be raised to that limit. Godaddy cut that request to 1/3, which irritated me a lot, but all the messages went through without a hitch. Later, I realized that my calculations were off because I didn't remember that mailman will batch the transmissions so that I had far fewer outgoing emails than I thought. This would be different if I turned on full personalization, but I don't have any need for that. All in all, the Godaddy experience has been positive. I lease a far better machine than the prior one that I owned, and pay far less than I did when I colocated my server at a local ISP (you can get _substantial_ discounts by paying in full for two to five years in advance: _ask_). I get more bandwidth, and the automated tools are, I reluctantly admit, not bad at all (Plesk; it's worth the monthly fee, just don't access it with IE. Use only Firefox). The cons are that Godaddy's service when you call to talk to a tech is not the best. Mostly, it consists of asking, "Did you read the FAQ on xxx?", stating "There is nothing wrong with our mail system," or saying, "I'm sorry, we don't support that software, since we don't force you to use it." (This last despite the fact that the software in question is the only software supplied on the system, and so you are forced to use it by default. They say you can install whatever you want on your system.) You'll end up googling a lot. You learn quickly, however. ;-) If you don't have the need for a dedicated server, you could go with a dedicated virtual server, which is a great deal cheaper, but you don't get things like three dedicated IP addresses and you have to share the machine (it looks like your own machine, however, because you're in a chroot box). They also have hosting plans that might include mailing lists, but I never really considered those. Hope this helps. Metta, Ivan Sekhar Ramakrishnan wrote: > > We are not sure what the reason is for these limits. Is it that the SMTP > servers cannot tell the difference between Mailman mail and other mail so > the places are afraid of spammers giving their servers a bad name? Or is it > that SMTP takes up so much resource that a limit is necessary? > > Finally, and this is the main reason for this post, are there commercial > places that support Mailman with more reasonable limits on the number of > messages? > -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours From brian at emwd.com Wed Jun 6 14:54:09 2007 From: brian at emwd.com (Brian Carpenter) Date: Wed, 6 Jun 2007 08:54:09 -0400 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits In-Reply-To: <4666AACD.6050007@pauahtun.org> Message-ID: You can also check out my services at http://www.emwd.com/mailman.html. I do not place any sort of message limits on my mailman clients. Kind regards, Brian Carpenter -------------------------------------- EMWD - Executive Officer -----Original Message----- From: mailman-users-bounces+brian=emwd.com at python.org [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of Ivan Van Laningham Sent: Wednesday, June 06, 2007 8:39 AM To: rajasekhar at columbia.edu; mailman-users at python.org Subject: Re: [Mailman-Users] Desperate to find a place without Mailman message limits Hi All-- I run ten to eleven mailing lists, with, just as you have, 100-500 members apiece. I have a dedicated server with Godaddy. They told me that yes, I could run mailing lists. They didn't tell me in advance that there was a daily limit of 1000 outgoing messages per day. I discovered that as soon as the first mailing list went into operation and I had to wait 24 hours for the counter to be reset. In order to raise the limit to something reasonable, I had to provide documentation to Godaddy through some automated tools they have. I think in the end it amounted to about 20 pages of justification. It was definitely a pain, because their base assumption is that mailing lists are newsletters sent to customers. It follows that if you are a capitalist with customers, you lust to become an evil spammer, and only the fear of legal action and forcible disconnection keeps you from inundating the net with enlargement ads. You have to provide samples of your "newsletters," which is a bit difficult if you want to provide a modicum of privacy for your subscribers. I made calculations based on the size of the lists and the number of subscribers and requested my limit be raised to that limit. Godaddy cut that request to 1/3, which irritated me a lot, but all the messages went through without a hitch. Later, I realized that my calculations were off because I didn't remember that mailman will batch the transmissions so that I had far fewer outgoing emails than I thought. This would be different if I turned on full personalization, but I don't have any need for that. All in all, the Godaddy experience has been positive. I lease a far better machine than the prior one that I owned, and pay far less than I did when I colocated my server at a local ISP (you can get _substantial_ discounts by paying in full for two to five years in advance: _ask_). I get more bandwidth, and the automated tools are, I reluctantly admit, not bad at all (Plesk; it's worth the monthly fee, just don't access it with IE. Use only Firefox). The cons are that Godaddy's service when you call to talk to a tech is not the best. Mostly, it consists of asking, "Did you read the FAQ on xxx?", stating "There is nothing wrong with our mail system," or saying, "I'm sorry, we don't support that software, since we don't force you to use it." (This last despite the fact that the software in question is the only software supplied on the system, and so you are forced to use it by default. They say you can install whatever you want on your system.) You'll end up googling a lot. You learn quickly, however. ;-) If you don't have the need for a dedicated server, you could go with a dedicated virtual server, which is a great deal cheaper, but you don't get things like three dedicated IP addresses and you have to share the machine (it looks like your own machine, however, because you're in a chroot box). They also have hosting plans that might include mailing lists, but I never really considered those. Hope this helps. Metta, Ivan Sekhar Ramakrishnan wrote: > > We are not sure what the reason is for these limits. Is it that the > SMTP > servers cannot tell the difference between Mailman mail and other mail so > the places are afraid of spammers giving their servers a bad name? Or is it > that SMTP takes up so much resource that a limit is necessary? > > Finally, and this is the main reason for this post, are there > commercial > places that support Mailman with more reasonable limits on the number of > messages? > -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningh am.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours ------------------------------------------------------ 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/brian%40emwd.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From japruim at raoset.com Wed Jun 6 15:06:52 2007 From: japruim at raoset.com (Jason Pruim) Date: Wed, 6 Jun 2007 09:06:52 -0400 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits In-Reply-To: References: Message-ID: <15502DC7-0FE5-47A9-9BBB-1D623ABC6844@raoset.com> Well if we are all going to throw in our hats... www.raoset.com/hosting/ As long as you don't bring my server down I don't put limits on stuff ;) On Jun 6, 2007, at 8:54 AM, Brian Carpenter wrote: > You can also check out my services at http://www.emwd.com/ > mailman.html. I do > not place any sort of message limits on my mailman clients. > > Kind regards, > Brian Carpenter > -------------------------------------- > EMWD - Executive Officer > > > > -----Original Message----- > From: mailman-users-bounces+brian=emwd.com at python.org > [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf > Of Ivan > Van Laningham > Sent: Wednesday, June 06, 2007 8:39 AM > To: rajasekhar at columbia.edu; mailman-users at python.org > Subject: Re: [Mailman-Users] Desperate to find a place without Mailman > message limits > > > Hi All-- > I run ten to eleven mailing lists, with, just as you have, 100-500 > members apiece. I have a dedicated server with Godaddy. They told me > that yes, I could run mailing lists. They didn't tell me in advance > that there was a daily limit of 1000 outgoing messages per day. I > discovered that as soon as the first mailing list went into operation > and I had to wait 24 hours for the counter to be reset. > > In order to raise the limit to something reasonable, I had to provide > documentation to Godaddy through some automated tools they have. I > think in the end it amounted to about 20 pages of justification. > It was > definitely a pain, because their base assumption is that mailing lists > are newsletters sent to customers. It follows that if you are a > capitalist with customers, you lust to become an evil spammer, and > only > the fear of legal action and forcible disconnection keeps you from > inundating the net with enlargement ads. > > You have to provide samples of your "newsletters," which is a bit > difficult if you want to provide a modicum of privacy for your > subscribers. > > I made calculations based on the size of the lists and the number of > subscribers and requested my limit be raised to that limit. > Godaddy cut > that request to 1/3, which irritated me a lot, but all the messages > went > through without a hitch. Later, I realized that my calculations were > off because I didn't remember that mailman will batch the > transmissions > so that I had far fewer outgoing emails than I thought. This would be > different if I turned on full personalization, but I don't have any > need > for that. > > All in all, the Godaddy experience has been positive. I lease a far > better machine than the prior one that I owned, and pay far less > than I > did when I colocated my server at a local ISP (you can get > _substantial_ > discounts by paying in full for two to five years in advance: > _ask_). I > get more bandwidth, and the automated tools are, I reluctantly admit, > not bad at all (Plesk; it's worth the monthly fee, just don't > access it > with IE. Use only Firefox). > > The cons are that Godaddy's service when you call to talk to a tech is > not the best. Mostly, it consists of asking, "Did you read the FAQ on > xxx?", stating "There is nothing wrong with our mail system," or > saying, > "I'm sorry, we don't support that software, since we don't force > you to > use it." (This last despite the fact that the software in question is > the only software supplied on the system, and so you are forced to use > it by default. They say you can install whatever you want on your > system.) You'll end up googling a lot. You learn quickly, > however. ;-) > > If you don't have the need for a dedicated server, you could go with a > dedicated virtual server, which is a great deal cheaper, but you don't > get things like three dedicated IP addresses and you have to share the > machine (it looks like your own machine, however, because you're in a > chroot box). > > They also have hosting plans that might include mailing lists, but I > never really considered those. > > Hope this helps. > > Metta, > Ivan > > Sekhar Ramakrishnan wrote: >> >> We are not sure what the reason is for these limits. Is it that the >> SMTP >> servers cannot tell the difference between Mailman mail and other >> mail so >> the places are afraid of spammers giving their servers a bad name? >> Or is > it >> that SMTP takes up so much resource that a limit is necessary? >> >> Finally, and this is the main reason for this post, are there >> commercial >> places that support Mailman with more reasonable limits on the >> number of >> messages? >> > > -- > Ivan Van Laningham > God N Locomotive Works > http://www.pauahtun.org/ > http://www.python.org/workshops/1998-11/proceedings/papers/ > laningham/laningh > am.html > Army Signal Corps: Cu Chi, Class of '70 > Author: Teach Yourself Python in 24 Hours > ------------------------------------------------------ > 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/brian%40emwd.com > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py? > req=show&file=faq01.027.htp > > ------------------------------------------------------ > 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/ > japruim%40raoset.com > > Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? > req=show&file=faq01.027.htp > From barry at python.org Wed Jun 6 15:28:21 2007 From: barry at python.org (Barry Warsaw) Date: Wed, 6 Jun 2007 09:28:21 -0400 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits In-Reply-To: <15502DC7-0FE5-47A9-9BBB-1D623ABC6844@raoset.com> References: <15502DC7-0FE5-47A9-9BBB-1D623ABC6844@raoset.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 6, 2007, at 9:06 AM, Jason Pruim wrote: > Well if we are all going to throw in our hats... www.raoset.com/ > hosting/ > > As long as you don't bring my server down I don't put limits on > stuff ;) If you're a Mailman hosting provider, be sure you're on the list: http://wiki.list.org/display/COM/Mailman+hosting+services If you're looking for hosting services, check that list! :) - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRma2dnEjvBPtnXfVAQIyiAP+Iij1jg9BYJRSvRWEjM0WSWgUV+v3Rtcy jwiX9OkdCe9ShNK6G11HTJFtlkgayoF1Ne7R9s1UlkRBrW6CywWXFOOID2XGhbtE PTC3nvBoeRMqGXb5v4A/xH4shAVlWZTBplMZnSCht2fxJbPMxlbOseonWQQvYuEL mN5j0t7489Y= =naAn -----END PGP SIGNATURE----- From kencheney at yahoo.com Wed Jun 6 17:41:52 2007 From: kencheney at yahoo.com (Ken Cheney) Date: Wed, 6 Jun 2007 08:41:52 -0700 (PDT) Subject: [Mailman-Users] /bin/sh: mailman: command not found Message-ID: <75210.26229.qm@web53201.mail.re2.yahoo.com> I have seen this error asked about many times and all seem to point to crontab.in and something in the 6th position. However I am a mailman/Linux n00b. How do I fix this? Subject: Cron <mailman at listserv> mailman /usr/lib/mailman/cron/gate_news Content-Type: text/plain; charset=UTF-8 Auto-Submitted: auto-generated X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/usr/lib/mailman> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=mailman> X-Cron-Env: <USER=mailman> --------------------------------- Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. From jeff at jwswinc.com Wed Jun 6 20:03:39 2007 From: jeff at jwswinc.com (Jeff Williams) Date: Wed, 06 Jun 2007 11:03:39 -0700 Subject: [Mailman-Users] Mailing list issue Message-ID: Hey guys. I have two different mailing lists on two different domains. One has been in operation for some time (shoptalk at identitypullman.com) and the other is new (list at rockhoundsoftball.com) The new rockhound list is doing something that is causing me fits. The "From" address looks like this: From: list at rockhoundsoftball.com (sent by list-bounces at rockhoundsoftball.com) On my Identity list, it simply looks like this: From: Shop Talk The added header information ?(sent by list-bounces at rockhoundsoftball.com)? is really interfering with people?s ability to receive messages as spam software seems to be grabbing these emails. I have compared preferences for both sites, and I don?t know what is different. How can I fix this??????? Thank you in advance for your help. JW ______________________________________________________________________ JWSW, Incorporated http://www.jwswinc.com 509.432.1220 From joshua at eeinternet.com Wed Jun 6 20:35:15 2007 From: joshua at eeinternet.com (Joshua J. Kugler) Date: Wed, 6 Jun 2007 10:35:15 -0800 Subject: [Mailman-Users] Desperate to find a place without Mailman message limits In-Reply-To: <46663707.20059.57B464@rr6.columbia.edu> References: <46663707.20059.57B464@rr6.columbia.edu> Message-ID: <200706061035.18151.joshua@eeinternet.com> On Wednesday 06 June 2007 00:24, Sekhar Ramakrishnan wrote: > Finally, and this is the main reason for this post, are there commercial > places that support Mailman with more reasonable limits on the number of > messages? textdrive.com has reasonably priced plans that include mailman. I've not seen anything about mailman limits, all their feature list says is "Host Mailman mailing lists complete with archives." Might be worth checking them out. Their AUP says you can't send out "Unsolicited Bulk Email (?UBE?, ?spam?)". It also says you can't run "unconfirmed" mailing lists. That is, your mailing lists have to be Opt-In. If they ask who referred you, say "jkugler." :) j -- Joshua Kugler Lead System Admin -- Senior Programmer http://www.eeinternet.com PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111 From drm_contractors_inc at yahoo.com Wed Jun 6 20:34:41 2007 From: drm_contractors_inc at yahoo.com (Arlene Munoz) Date: Wed, 6 Jun 2007 13:34:41 -0500 (CDT) Subject: [Mailman-Users] Mailman-Users Digest, Vol 40, Issue 1 In-Reply-To: Message-ID: <765711.22126.qm@web62405.mail.re1.yahoo.com> por favor no quiero que me sigan enviando sus mensajes, les voy a pedir que respeten mis descisiones y mi espacio. mailman-users-request at python.org escribi?: Send Mailman-Users mailing list submissions to mailman-users at python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to mailman-users-request at python.org You can reach the person managing the list at mailman-users-owner at python.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Mailman-Users digest..." Today's Topics: 1. odd empty bounce message generated upon posting to a mailing list (Jon Pauli) 2. Unable to Create New Lists (Phil Fonville) 3. Which script does /admin/members call? (Curtis Preston) 4. Re: Unable to Create New Lists (Mark Sapiro) 5. Re: Mailman Splitting Subject (Mark Sapiro) 6. Re: Maximum template size? (Mark Sapiro) 7. Re: No domain name, Can I use mailman to build a maillist? (Mark Sapiro) 8. Re: how can i simulate mailman pages (Mark Sapiro) 9. Re: Low level smtp error: Server not connected (Mark Sapiro) 10. Re: a question about unadvertised lists and spam (Mark Sapiro) De: "Jon Pauli" Para: mailman-users at python.org Fecha: Thu, 31 May 2007 12:29:05 -0500 Asunto: [Mailman-Users] odd empty bounce message generated upon posting to a mailing list Hello, I have been looking around in the docs and have not seen anything that matches my issue. I have a couple of mailing lists and every time anyone- member or non-member posts, everything works fine but the list owner gets 1)An uncaught bounce notification containing an empty attachment called ForwardedMessage.eml. Thunderbird is the MUA so I'm guessing it is responsible for determining how to interpret the attachment, but even if I save it as a text file it is a 2 byte long file with no visible characters in it...I didn't take a hex editor to it. I understand why listowner gets these, I'm just not sure how it can work with a 2 byte file and no headers ;) 2. An email where no subject and no sender appear in the MUA. The headers are as follows: Delivered-To: me at mydomain.com Return-Path: < mailman-bounces at mail.mydomain.com> Received: from [192.168.10.22] (softdnserr [127.0.0.1]) by mail.mydomain.com with esmtp; Thu, 31 May 2007 09:57:36 -0500id 00A9A0CA.465EE260.00010B2E Sender: mailman-bounces at mail.mydomain.com Errors-To: mailman-bounces at mail.mydomain.com Message-ID: Date: Thu, 31 May 2007 09:57:36 -0500 To: undisclosed-recipients: ; The interesting things I noticed are: 1. The Received: header line is wrong. The mail server has a DNS server running on it as well as the MTA. its IP is 192.168.11.22 NOT 10.22 There is no 192.168.10.22 on my network. This happens only for mailman emails. I don't recall having to set any IPs when I set up mailman. What is wrong here? 2. The end of the Message-ID: line contains only mydomain, not say, mydomain.com like non-mailman emails. 3. There is no Sender showing up in the MUA but the Sender: header is present. It looks like Thunderbird maybe uses the From: header instead of the Sender header despite naming the column where this would appear "Sender". I'd appreciate any thoughts or insight into this. I am confused. De: "Phil Fonville" Para: Fecha: Thu, 31 May 2007 14:21:49 -0400 Asunto: [Mailman-Users] Unable to Create New Lists I am unable to create new lists with either the web interface or the newlist script. However, I can post to my existing lists, and the posts go out to list subscribers. Failed attempts yield this message: Error: Unknown virtual host: bashful at troxlerlabs.local my mm_cfg.py file contains: DEFAULT_URL_PATTERN = 'http://%s/mailman/ DEFAULT_NNTP_HOST = 'bashful' DEFAULT_EMAIL_HOST = 'bashful' DEFAULT_URL_HOST - 'bashful' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) I did run the fix_url script against my existing lists. I see no evidence of problems when I run the check_perms and check_db scripts. My hostname (physical and virtual [see below]) is bashful.troxlerlabs.local I have stopped and restarted the qrunner. I should mention that my setup includes Postfix and Apache running in the same host. All this is in a SUSE Linux 10.2 virtual machine with NAT and ports 25 and 80 forwarded to their respective applications. This virtual machine worked fine on a different host, pfonvillepc2 (with "pfonvillepc2" substituted for all instances of "bashful") before moving it to bashful. I have looked for posts and FAQs for similar problem(s) but couldn't find any. Would be grateful for any help. De: "Curtis Preston" Para: Fecha: Thu, 31 May 2007 17:08:36 -0400 Asunto: [Mailman-Users] Which script does /admin/members call? I need to know which script is called when I run the /admin/members page and press Submit. I can't figure it out since ./cgi-bin/members is a binary. (I'm continuing down my path of trying to figure out how to set the digest mode via wget and I need to see how Mailman is parsing this form.) --- W. Curtis Preston Author of O'Reilly's Backup & Recovery and Using SANs and NAS VP Data Protection GlassHouse Technologies De: Mark Sapiro Para: "Phil Fonville" , Fecha: Thu, 31 May 2007 14:15:17 -0700 Asunto: Re: [Mailman-Users] Unable to Create New Lists Phil Fonville wrote: > >I am unable to create new lists with either the web interface or the >newlist script. However, I can post to my existing lists, and the posts >go out to list subscribers. > >Failed attempts yield this message: > > Error: Unknown virtual host: bashful at troxlerlabs.local > > >my mm_cfg.py file contains: > > DEFAULT_URL_PATTERN = 'http://%s/mailman/ > > DEFAULT_NNTP_HOST = 'bashful' This only affects mail <-> news gatewaying > DEFAULT_EMAIL_HOST = 'bashful' > > DEFAULT_URL_HOST - 'bashful' All the above host names must be fully qualified - i.e... 'bashful.troxlerlabs.local', not just 'bashful'. Also, I assume the above '_' instead of '=' is just a typo in your email. Finally, it would be good here to remove the Defaults.py add_virtualhost() entry by inserting VIRTUAL_HOSTS.clear() prior to > add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) > > >I did run the fix_url script against my existing lists. I see no >evidence of problems when I run the check_perms and check_db scripts. > >My hostname (physical and virtual [see below]) is >bashful.troxlerlabs.local After you fix mm_cfg.py as above, it would be good to run fix_url again. Also see . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro CC: mailman-users at python.org Para: "Stephen J. Turnbull" , lloyd at viplist.us Fecha: Thu, 31 May 2007 16:20:24 -0700 Asunto: Re: [Mailman-Users] Mailman Splitting Subject Stephen J. Turnbull wrote: > >It's almost a trivial patch; in the email/Generator.py file find the >keyword argument continuation_ws='\t' to the Header initialization and >change the '\t' to ' '. This is an incomplete solution. See Mailman/Handlers/CookHeaders.py. You really need to patch the prefix_subject function in that module by changing ws = '\t' in # Try to figure out what the continuation_ws is for the header if isinstance(subject, Header): lines = str(subject).splitlines() else: lines = subject.splitlines() ws = '\t' if len(lines) > 1 and lines[1] and lines[1][0] in ' \t': ws = lines[1][0] to ws = ' ' or possibly replace that whole piece with just ws = ' ' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro CC: mailman-users at python.org Para: "Carter Braxton" , "Patrick Bogen" Fecha: Thu, 31 May 2007 16:29:56 -0700 Asunto: Re: [Mailman-Users] Maximum template size? Carter Braxton wrote: > >I just tested this to be certain, and the variable substitution does not take place -- the invitation email that is sent contains the variable names rather than the values: The problem is the non-substitution '%' characters in your template. E.g., >75% of email traffic on the Internet > http://www.test.test/cgi-bin/mailman/options/test/name%40domain.com > > The part that reads "name%40domain.com" is based on your email > address. For example, if you signed up with an email address of > "foo at bar.com," you would point your web browser to: > > http://www.test.test/cgi-bin/mailman/options/test/foo%40bar.com All the above '%' characters need to be doubled as '%%' so they are not confused with substitutions such as the following. >Your address "%(email)s" has been invited to join the %(listname)s >mailing list at %(hostname)s by the %(listname)s mailing list owner. >You may accept the invitation by simply replying to this message, >keeping the Subject: header intact. > >You can also visit this web page: > > %(confirmurl)s > >Or you should include the following line -- and only the following >line -- in a message to %(requestaddr)s: > > confirm %(cookie)s > >Note that simply sending a `reply' to this message should work from >most mail readers. > >If you want to decline this invitation, please simply disregard this >message. If you have any questions, please send them to >%(listowner)s. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro Para: jetspeed , mailman Fecha: Thu, 31 May 2007 16:45:08 -0700 Asunto: Re: [Mailman-Users] No domain name, Can I use mailman to build a maillist? jetspeed wrote: >I use exim4 as MTA, and mailman as maillist >But I have no domain name besides my IP, so mails from other smtp servers can't be relayed to my MTA, How can I deal with this situation? I think you can set DEFAULT_URL_HOST = 'xxx.xxx.xxx.xxx' DEFAULT_EMAIL_HOST = '[xxx.xxx.xxx.xxx]' and Mailman will work. but you may have issues with other MTAs refusing to deliver to address literals. OTOH, for less that $1.00/month you can register a domain including DNS service with, e.g., . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro Para: , Fecha: Thu, 31 May 2007 16:54:26 -0700 Asunto: Re: [Mailman-Users] how can i simulate mailman pages wrote: >'The problem is probably that the /admin/* pages require the list or site >admin password to be in a cookie, and normal users aren't going to have >that.' So, it seems you want to make your own web form which circumvents the Mailman subscribe process and subscribes the user directly via the admin mass subscribe page. >is it possible to set a cookie by hand. You don't need to do this. You just send the admin password with the cgi data as shown for example at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro Para: ljacobs at shambhala.com, Fecha: Thu, 31 May 2007 17:16:49 -0700 Asunto: Re: [Mailman-Users] Low level smtp error: Server not connected Leonard Jacobs wrote: >I am trying to run Mailman 2.1.9 on a CentOS 4 server with postfix 2.4.1. I had Mailman 2.1.5 running on a slower system and wanted to offload some apps to this newer server but am having problems. check_perms has no errors. Creating lists works fine and when postings are submitted the messages are delivered to the list admins re posting verifications. > >But only a few of the messages are getting delivered. logs/smtp-failure shows many of this type of error: >"delivery to someone at gmail.com failed with code -1: (104, 'Connection reset by peer')" I am also seeing many " Low level smtp error: Server not connected, msgid" errors. I did try all the suggested fixes in the FAQ including adding the line to get error output in the logs/error file. And this file is showing successful delivery, such as >"May 26 16:33:44 2007 qrunner(20744): reply: '250 2.1.5 Ok\r\n' >May 26 16:33:44 2007 qrunner(20744): reply: retcode (250); Msg: 2.1.5 Ok >May 26 16:33:44 2007 qrunner(20744): send: 'rcpt TO:\r\n"" >but the majority of the messages are simply stuck in the qfiles/out and qfile/rety directory. Leonard, I don't know where you are with this. I've read the rest of the thread, but I don't know if you've discovered anything or not. Here's what I can tell you. >From the Mailman/Python/smtplib point of view, Postfix is dropping the connection unexpectedly. You only show a small debug snippet above, but somewhere in the debug output there should be a point where something goes wrong in the SMTP transaction sequence. This should give you a clue. I'm guessing, since individual notices work, that postfix doesn't like transactions with a lot of recipients. Try setting SMTP_MAX_RCPTS = 1 in mm_cfg.py and restarting mailman. If that works, you can then look at why Postfix doesn't like more than x recipients in a transaction. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan De: Mark Sapiro Para: Dennis at top-dog-home.com, mailman-users at python.org Fecha: Thu, 31 May 2007 17:23:09 -0700 Asunto: Re: [Mailman-Users] a question about unadvertised lists and spam Dennis Morgan wrote: > >My question is - are spamers able to pick up lists from the default (but >not easily accessible) default mailman listinfo page and start >bombarding us with spam on all lists? Or should I set the "Advertise >this list" option to "no" for the lists on the default listinfo page? My opinion, based on only anecdotal observation is that it doesn't matter. The spammers will get your list addresses from spyware on your list member's computers (it only takes one). -- 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/ __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ?gratis! Reg?strate ya - http://correo.espanol.yahoo.com/ From cjgeier at wisc.edu Wed Jun 6 21:07:01 2007 From: cjgeier at wisc.edu (Chris Geier) Date: Wed, 06 Jun 2007 14:07:01 -0500 Subject: [Mailman-Users] startup commands on OSX Message-ID: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> Hello: I have a question I hope someone can help me with. I have Mailman loaded on a Mac and it has been working fine. The computer lost power the other evening and shutdown. After restarting the computer I can access the Mailman lists, but any mail does not get sent. I added several new users today and I did not get the new user notifications. Then I sent an email to one of the lists and I get nothing. The guy that used to manage the system has left the company. I thought there was something I needed to run at the command line to get the mail moving? Anyone know what the commands are to get the mail moving again? Thanks for any help! -Chris From parturi at bairesweb.com Wed Jun 6 21:40:08 2007 From: parturi at bairesweb.com (Pablo L. Arturi) Date: Wed, 6 Jun 2007 16:40:08 -0300 Subject: [Mailman-Users] 2 MTA 1 mailman for the same vdomain Message-ID: <111f01c7a872$7dede7f0$0400a8c0@bworg196ib52so> Hello guys, this is my first install of mailman. I'll explain my setup. I have 1 mail server running postfix for vdomains using mysql, to lets say domain.com I have another server running postfix-mailman, to manage some mailing lists for domain.com I am not sure how to continue with this. my first postfix server manages all mails for domain.com, and now I need to start creating lists for domain.com. Not sure if I need to setup lists.domain.com or use domain.com and "map" users at domain.com to send all messages to the second machine running postfix-mailman. I have installed mailman and could create a mailing list, but I am not sure how should I start mapping mail accounts to the mailing list server. Any help? Thank you very much! Pablo From Ralf.Hildebrandt at charite.de Wed Jun 6 22:11:43 2007 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Wed, 6 Jun 2007 22:11:43 +0200 Subject: [Mailman-Users] startup commands on OSX In-Reply-To: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> References: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> Message-ID: <20070606201143.GI19640@charite.de> * Chris Geier : > After restarting the computer I can access the Mailman lists, but any mail > does not get sent. Is the QueueRunner process running? -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt at charite.de Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk at charite.de From lstone19 at stonejongleux.com Wed Jun 6 23:07:38 2007 From: lstone19 at stonejongleux.com (Larry Stone) Date: Wed, 6 Jun 2007 16:07:38 -0500 (CDT) Subject: [Mailman-Users] startup commands on OSX In-Reply-To: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> References: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> Message-ID: On Wed, 6 Jun 2007, Chris Geier wrote: > Hello: > > I have a question I hope someone can help me with. > > I have Mailman loaded on a Mac and it has been working fine. > > The computer lost power the other evening and shutdown. > > After restarting the computer I can access the Mailman lists, but any mail > does not get sent. > > Anyone know what the commands are to get the mail moving again? Sounds like there's nothing on your computer to start mailman automatically at boot. To start it on your current running system, go into Terminal and type: sudo /path/to/mailman/bin/mailmanctl start where /path/to/mailman is the path to where mailman is (for instance, if it's in the Applications folder in a folder called Mailman, then you'd put /Applications/Mailman there). To have Mailman start at boot time, follow these instructions from my guid to installing Mailman on Mac OS X (the full guide can be found in the archives - it's from July 2005): Step 8) Configure your system to start Mailman when it is booted. a) Open Terminal and change directory to /Library/LaunchDaemons: sudo su cd /Library/LaunchDaemons *** June 2007 addendum: my original said to cd to /System/Library/LaunchDaemons. I've since learned that Apple recommends that only Apple provided startup files be there and 3rd-party startup files be in /Library/LaunchDaemons (not withstanding that other 3rd-party packages have put stuff in /System/Library/LaunchDaemons). b) Create the Mailman startup preference file: touch mailman.plist c) Using your favorite method of text editing, add the following content to mailman.plist: Disabled Label mailman OnDemand ProgramArguments /Applications/Mailman/bin/mailmanctl start ServiceIPC RunAtLoad d) Verify the file ownership and permissions: ls -l You should see one of the lines saying something like: -rw-r--r-- 5 root wheel 170 12 May 11:21 mailman e) If the permissions (rw-r--r--) are not correct, type: chmod 644 mailman.plist f) If the owner (root) or group (wheel) is not correct, type: chown root:wheel Mailman g) Reboot (Restart) your system. When it finishes rebooting, Mailman should be running. To verify, open Terminal and type: ps -ax | grep python You should see a bunch of lines like this: 434 ?? Ss 0:00.04 python bin/mailmanctl -s start 443 ?? S 4:19.95 /usr/bin/python /Applications/Mailman/bin/qrunner --r 444 ?? S 4:08.58 /usr/bin/python /Applications/Mailman/bin/qrunner --r 445 ?? S 4:11.20 /usr/bin/python /Applications/Mailman/bin/qrunner --r 446 ?? S 4:06.93 /usr/bin/python /Applications/Mailman/bin/qrunner --r 447 ?? S 3:59.35 /usr/bin/python /Applications/Mailman/bin/qrunner --r 448 ?? S 4:16.59 /usr/bin/python /Applications/Mailman/bin/qrunner --r 449 ?? S 4:04.08 /usr/bin/python /Applications/Mailman/bin/qrunner --r 450 ?? S 0:00.85 /usr/bin/python /Applications/Mailman/bin/qrunner --r 16621 std R+ 0:00.00 grep -i python (The numbers will vary. The important thing is that you see the qrunner processes) -- Larry Stone lstone19 at stonejongleux.com From dan at music.memphis.edu Wed Jun 6 22:39:54 2007 From: dan at music.memphis.edu (Dan) Date: Wed, 06 Jun 2007 15:39:54 -0500 Subject: [Mailman-Users] startup commands on OSX In-Reply-To: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> References: <007d01c7a86d$dd21ccf0$0402a8c0@ad.ophth.wisc.edu> Message-ID: <46671B9A.4020603@music.memphis.edu> Chris Geier wrote: > I have Mailman loaded on a Mac and it has been working fine. > > The computer lost power the other evening and shutdown. > > After restarting the computer I can access the Mailman lists, but any mail > does not get sent. > > I added several new users today and I did not get the new user > notifications. Then I sent an email to one of the lists and I get nothing. > > The guy that used to manage the system has left the company. > > I thought there was something I needed to run at the command line to get the > mail moving? > > Anyone know what the commands are to get the mail moving again? > > Thanks for any help! OS X client or server? Which version? Apple's install or from source? If it's the out of the box OS X Server version, start the qrunners with /usr/share/mailman/bin mailmanctl start. If it's from source, the location of the mailman/bin folder is likely to be different. The Server version should have a Mailman folder in /System/Library/StartupItems/ that starts it automatically at boot time. You can also create one yourself to run on the OS X client. Dan From jreddy at bnl.gov Wed Jun 6 23:34:45 2007 From: jreddy at bnl.gov (John Reddy) Date: Wed, 06 Jun 2007 17:34:45 -0400 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) Message-ID: <46672875.1030608@bnl.gov> I've checked the FAQ and Googled this before coming here to ask for advice. Background: Running Debian 4.0, x86_64, MTA is Postfix, packaged Debian Mailman (version listed "2.1.9-7"), Python version 2.4.4. I'm having a problem where the archives are not ingesting MIME email for various mailing lists that I maintain. A message goes to the mailing list, is processed properly and gets reflected to the recipients. All email to the list winds up in /var/lib/mailman/archives/private/listname.mbox/listname.mbox. However, messages that have MIME encoding don't make it to /var/lib/mailman/archives/private/listname for inclusion in the web page. I tried running mmarch to rebuild the archive, and got the following output: > [root at mailserver] # mmarch --wipe testmaillist-l testmaillist-l.mbox.o > #00000 <200601010510.k015A1J17411 at sample.email.bnl.gov> > figuring article archives > 2006-January > #00001 <200601020510.k025A0829608 at sample.email.bnl.gov> > figuring article archives > 2006-January > #00002 <200601030510.k035A1w11781 at sample.email.bnl.gov> > figuring article archives > 2006-January > Updating index files for archive [2006-January] > Date > Subject > Author > Thread > Computing threaded index > Updating HTML for article 0 > Updating HTML for article 1 > Updating HTML for article 2 > Pickling archive state into > /var/lib/mailman/archives/private/testmaillist-l/pipermail.pck > Traceback (most recent call last): > File "/usr/sbin/mmarch", line 200, in ? > main() > File "/usr/sbin/mmarch", line 188, in main > archiver.processUnixMailbox(fp, start, end) > File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in > processUnixMailbox > m = mbox.next() > File "/usr/lib/python2.4/mailbox.py", line 35, in next > return self.factory(_Subfile(self.fp, start, stop)) > File "/var/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber > return mailbox.scrub(msg) > File "/var/lib/mailman/Mailman/Mailbox.py", line 109, in scrub > return self._scrubber(self._mlist, msg) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 393, in > process > replace_payload_by_text(msg, sep.join(text), charset) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in > replace_payload_by_text > msg.set_payload(text, charset) > File "email/Message.py", line 218, in set_payload > File "email/Message.py", line 242, in set_charset > TypeError: us-ascii "mmarch" seems to be having trouble with the Content-Type header line. If I pull out that line for a given message, it is ingested, though it displays the full MIME text. Any direction on where to look would be appreciated. -John -- John Reddy jreddy at bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs From tkikuchi at is.kochi-u.ac.jp Thu Jun 7 02:08:14 2007 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu, 07 Jun 2007 09:08:14 +0900 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <46672875.1030608@bnl.gov> References: <46672875.1030608@bnl.gov> Message-ID: <46674C6E.1040506@is.kochi-u.ac.jp> >> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in >> replace_payload_by_text >> msg.set_payload(text, charset) >> File "email/Message.py", line 218, in set_payload >> File "email/Message.py", line 242, in set_charset >> TypeError: us-ascii > > "mmarch" seems to be having trouble with the Content-Type header line. > If I pull out that line for a given message, it is ingested, though it > displays the full MIME text. What exactly was the Content-Type header line ? -- Tokio Kikuchi, tkikuchi at is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From msapiro at value.net Thu Jun 7 02:48:52 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 6 Jun 2007 17:48:52 -0700 Subject: [Mailman-Users] /bin/sh: mailman: command not found In-Reply-To: <75210.26229.qm@web53201.mail.re2.yahoo.com> Message-ID: Ken Cheney wrote: >I have seen this error asked about many times and all seem to point to crontab.in and something in the 6th position. > > However I am a mailman/Linux n00b. How do I fix this? See for example and perhaps . Either remove the word 'mailman' from between the times and the command in the mailman crontab, or install the crontab as is in /etc/cron.d/mailman instead of /var/spool/cron/mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 7 03:06:21 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 6 Jun 2007 18:06:21 -0700 Subject: [Mailman-Users] Mailing list issue In-Reply-To: Message-ID: Jeff Williams wrote: > >I have two different mailing lists on two different domains. One has been in >operation for some time (shoptalk at identitypullman.com) and the other is new >(list at rockhoundsoftball.com) Are these domains served by the same Mailman installation? >The new rockhound list is doing something that is causing me fits. > >The "From" address looks like this: > >From: list at rockhoundsoftball.com (sent by >list-bounces at rockhoundsoftball.com) > >On my Identity list, it simply looks like this: > >From: Shop Talk > >The added header information "(sent by list-bounces at rockhoundsoftball.com)" >is really interfering with people's ability to receive messages as spam >software seems to be grabbing these emails. I have compared preferences for >both sites, and I don't know what is different. The added information is probably added by the recipient's mail client, not by Mailman. See although your symptom seems somewhat different. It appears that both lists are anonymous. "Shop Talk" in the From: of the shoptalk at identitypullman.com list comes from the description setting on the list's General Options page. If this is set on the other list, and it is the same Mailman, I don't know why the From: would be different. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 7 04:16:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 6 Jun 2007 19:16:59 -0700 Subject: [Mailman-Users] 2 MTA 1 mailman for the same vdomain In-Reply-To: <111f01c7a872$7dede7f0$0400a8c0@bworg196ib52so> Message-ID: Pablo L. Arturi wrote: > >I have 1 mail server running postfix for vdomains using mysql, to lets say domain.com >I have another server running postfix-mailman, to manage some mailing lists for domain.com > >I am not sure how to continue with this. > >my first postfix server manages all mails for domain.com, and now I need to start creating lists for domain.com. Not sure if I need to setup lists.domain.com or use domain.com and "map" users at domain.com to send all messages to the second machine running postfix-mailman. You can do it either way. Set up a lists.example.com domain for mail lists only which directs all mail to the mailman server, or tell the main MTA for example.com the send all mail for the 10 addresses list at example.com list-admin at example.com list-bounces at example.com list-confirm at example.com list-join at example.com list-leave at example.com list-owner at example.com list-request at example.com list-subscribe at example.com list-unsubscribe at example.com for each list to the mailman server. Yet another possibility is to use NFS to make the mail/mailman wrapper on the Mailman machine accessible to the main mail server and pipe the list mail directly to the wrapper on the Mailman machine. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From parturi at bairesweb.com Thu Jun 7 05:13:36 2007 From: parturi at bairesweb.com (Pablo L. Arturi) Date: Thu, 7 Jun 2007 00:13:36 -0300 Subject: [Mailman-Users] User unknown? Message-ID: <153f01c7a8b1$d6efb560$0400a8c0@bworg196ib52so> Hello people. I am sure I am missing something, but can't figure it what. I am following this instructions: http://www.gnu.org/software/mailman/mailman-install/postfix-virtual.html when I send a mail from parturi at domain_sender.com to the list chuchucha at example.com, I get postfix telling me the user doesn't exist, while it should be (and appears to find it) find it from the alias database. domain names replaced by example.com and sender_domain.com Thank you for your patience and help! Refards, Pablo This are all relevant logs and configurations I have made: This is the content of my mm_cfg.py (comments removed). *********************************************** [root at lists mailman]# cat /etc/mailman/mm_cfg.py *********************************************** from Defaults import * import pwd, grp MAILMAN_UID = pwd.getpwnam('mailman')[2] MAILMAN_GID = grp.getgrnam('mailman')[2] from socket import * try: fqdn = getfqdn() except: fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = fqdn DEFAULT_EMAIL_HOST = fqdn add_virtualhost("news.example.com", "news.example.com") add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) MTA = 'Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS = ['news.example.com'] I tried to send a message to chuchucha at news.example.com, this is the transcript of the log sessions ************************ tail -f /var/log/maillog ************************ Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: mynetworks ~? debug_peer_list Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: mynetworks ~? fast_flush_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: mynetworks ~? mynetworks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? debug_peer_list Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? fast_flush_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? mynetworks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? permit_mx_backup_networks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? qmqpd_authorized_clients Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: relay_domains ~? relay_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: user = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: password = ******** Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: dbname = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: table = postfix_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: select_field = transport Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: where_field = domain Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: additional_conditions = Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-transport.cf: hosts = localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: mysqlname_parse: /etc/postfix/mysql-transport.cf: adding host 'localhost' to list of mysql server hosts Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_open: mysql:/etc/postfix/mysql-transport.cf Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: permit_mx_backup_networks ~? debug_peer_list Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: permit_mx_backup_networks ~? fast_flush_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: permit_mx_backup_networks ~? mynetworks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: permit_mx_backup_networks ~? permit_mx_backup_networks Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: user = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: password = ******** Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: dbname = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: table = postfix_virtual Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: select_field = destination Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: where_field = email Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: additional_conditions = Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual.cf: hosts = localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: mysqlname_parse: /etc/postfix/mysql-virtual.cf: adding host 'localhost' to list of mysql server hosts Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_open: mysql:/etc/postfix/mysql-virtual.cf Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_open: hash:/etc/mailman/virtual-mailman Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: user = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: password = ******** Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: dbname = postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: table = postfix_users Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: select_field = maildir Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: where_field = email Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: additional_conditions = and postfix = 'y' Jun 6 23:55:37 lists postfix/smtpd[15635]: cfg_get_str: /etc/postfix/mysql-virtual-maps.cf: hosts = localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: mysqlname_parse: /etc/postfix/mysql-virtual-maps.cf: adding host 'localhost' to list of mysql server hosts Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_open: mysql:/etc/postfix/mysql-virtual-maps.cf Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_open: unix:passwd.byname Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? debug_peer_list Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? fast_flush_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? mynetworks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? permit_mx_backup_networks Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? qmqpd_authorized_clients Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? relay_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: smtpd_access_maps ~? smtpd_access_maps Jun 6 23:55:37 lists postfix/smtpd[15635]: smtpd_sasl_initialize: SASL config file is smtpd.conf Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: fast_flush_domains ~? debug_peer_list Jun 6 23:55:37 lists postfix/smtpd[15635]: match_string: fast_flush_domains ~? fast_flush_domains Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_create: 0x808b968 18000 Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_stop: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_start: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: connection established Jun 6 23:55:37 lists postfix/smtpd[15635]: master_notify: status 0 Jun 6 23:55:37 lists postfix/smtpd[15635]: name_mask: resource Jun 6 23:55:37 lists postfix/smtpd[15635]: name_mask: software Jun 6 23:55:37 lists postfix/smtpd[15635]: name_mask: noanonymous Jun 6 23:55:37 lists postfix/smtpd[15635]: connect from dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4] Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: dcc-hq-host-200-59-45-4.dnsba.com: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: 200.59.45.4: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: dcc-hq-host-200-59-45-4.dnsba.com: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: 200.59.45.4: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 220 news.example.com ESMTP Postfix Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_pat: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: < dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: EHLO dnsba.com Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-PIPELINING Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-SIZE 10240000 Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-VRFY Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-ETRN Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-AUTH PLAIN LOGIN Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250-AUTH=PLAIN LOGIN Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: dcc-hq-host-200-59-45-4.dnsba.com: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: 200.59.45.4: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250 8BITMIME Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_pat: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: < dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: MAIL FROM: SIZE=1390 Jun 6 23:55:37 lists postfix/smtpd[15635]: extract_addr: input: Jun 6 23:55:37 lists postfix/smtpd[15635]: smtpd_check_addr: addr=parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: connect to subsystem private/rewrite Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr request = rewrite Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr rule = canonicalize Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr address = parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: rewrite_clnt: canonicalize: parturi at domain_sender.com -> parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr request = resolve Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr address = parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: transport Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: transport Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: smtp Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: nexthop Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: nexthop Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: recipient Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: recipient Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: flags Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: flags Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: 4096 Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: resolve_clnt: `parturi at domain_sender.com' -> transp=`smtp' host=`domain_sender.com' rcpt=`parturi at domain_sender.com' flags= class=default Jun 6 23:55:37 lists postfix/smtpd[15635]: ctable_locate: install entry key parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: extract_addr: result: parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: fsspace: .: block size 4096, blocks free 48010832 Jun 6 23:55:37 lists postfix/smtpd[15635]: smtpd_check_size: blocks 4096 avail 48010832 min_free 0 msg_size_limit 10240000 Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250 Ok Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_pat: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: < dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: RCPT TO: Jun 6 23:55:37 lists postfix/smtpd[15635]: extract_addr: input: Jun 6 23:55:37 lists postfix/smtpd[15635]: smtpd_check_addr: addr=chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr request = rewrite Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr rule = canonicalize Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr address = chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: rewrite_clnt: canonicalize: chuchucha at news.example.com -> chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr request = resolve Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr address = chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: transport Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: transport Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: virtual Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: nexthop Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: nexthop Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: recipient Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: recipient Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: flags Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: flags Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: 256 Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: resolve_clnt: `chuchucha at news.example.com' -> transp=`virtual' host=`news.example.com' rcpt=`chuchucha at news.example.com' flags= class=local Jun 6 23:55:37 lists postfix/smtpd[15635]: ctable_locate: install entry key chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: extract_addr: result: chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr request = rewrite Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr rule = canonicalize Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr address = postmaster Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: address Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: postmaster at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: private/rewrite socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: rewrite_clnt: canonicalize: postmaster -> postmaster at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: >>> START Recipient address RESTRICTIONS <<< Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=permit_sasl_authenticated Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=permit_sasl_authenticated status=0 Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=permit_mynetworks Jun 6 23:55:37 lists postfix/smtpd[15635]: permit_mynetworks: dcc-hq-host-200-59-45-4.dnsba.com 200.59.45.4 Jun 6 23:55:37 lists postfix/smtpd[15635]: match_hostname: dcc-hq-host-200-59-45-4.dnsba.com ~? 127.0.0.1/32 Jun 6 23:55:37 lists postfix/smtpd[15635]: match_hostaddr: 200.59.45.4 ~? 127.0.0.1/32 Jun 6 23:55:37 lists postfix/smtpd[15635]: match_hostname: dcc-hq-host-200-59-45-4.dnsba.com ~? 200.59.45.167/32 Jun 6 23:55:37 lists postfix/smtpd[15635]: match_hostaddr: 200.59.45.4 ~? 200.59.45.167/32 Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: dcc-hq-host-200-59-45-4.dnsba.com: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: match_list_match: 200.59.45.4: no match Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=permit_mynetworks status=0 Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=reject_unauth_destination Jun 6 23:55:37 lists postfix/smtpd[15635]: reject_unauth_destination: chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: permit_auth_destination: chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: ctable_locate: leave existing entry key chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=reject_unauth_destination status=0 Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=reject_unknown_sender_domain Jun 6 23:55:37 lists postfix/smtpd[15635]: reject_unknown_address: parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: ctable_locate: move existing entry key parturi at domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: reject_unknown_mailhost: domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: lookup domain_sender.com type 1 flags 0 Jun 6 23:55:37 lists postfix/smtpd[15635]: dns_query: domain_sender.com (A): OK Jun 6 23:55:37 lists postfix/smtpd[15635]: dns_get_answer: type A for domain_sender.com Jun 6 23:55:37 lists postfix/smtpd[15635]: generic_checks: name=reject_unknown_sender_domain status=0 Jun 6 23:55:37 lists postfix/smtpd[15635]: >>> END Recipient address RESTRICTIONS <<< Jun 6 23:55:37 lists postfix/smtpd[15635]: >>> CHECKING RECIPIENT MAPS <<< Jun 6 23:55:37 lists postfix/smtpd[15635]: ctable_locate: move existing entry key chuchucha at news.example.com Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: recipient_canonical_maps: chuchucha at news.example.com: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: recipient_canonical_maps: chuchucha: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: recipient_canonical_maps: @news.example.com: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: mail_addr_find: chuchucha at news.example.com -> (not found) Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: canonical_maps: chuchucha at news.example.com: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: canonical_maps: chuchucha: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: canonical_maps: @news.example.com: not found Jun 6 23:55:37 lists postfix/smtpd[15635]: mail_addr_find: chuchucha at news.example.com -> (not found) Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_mysql_lookup using sql query: select destination from postfix_virtual where email = 'chuchucha at news.example.com' Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_mysql_get_active: attempting to connect to host localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_mysql: successful connection to host localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_mysql: successful query from host localhost Jun 6 23:55:37 lists postfix/smtpd[15635]: dict_mysql_lookup: retrieved 0 rows Jun 6 23:55:37 lists postfix/smtpd[15635]: maps_find: virtual_alias_maps: hash:/etc/mailman/virtual-mailman(0,100): chuchucha at news.example.com = chuchucha Jun 6 23:55:37 lists postfix/smtpd[15635]: mail_addr_find: chuchucha at news.example.com -> chuchucha Jun 6 23:55:37 lists postfix/smtpd[15635]: connect to subsystem public/cleanup Jun 6 23:55:37 lists postfix/smtpd[15635]: public/cleanup socket: wanted attribute: queue_id Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: queue_id Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: A57F287C036 Jun 6 23:55:37 lists postfix/smtpd[15635]: public/cleanup socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: send attr flags = 50 Jun 6 23:55:37 lists postfix/smtpd[15635]: A57F287C036: client=dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4] Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250 Ok Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_pat: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: < dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: DATA Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 354 End data with . Jun 6 23:55:37 lists postfix/smtpd[15635]: public/cleanup socket: wanted attribute: status Jun 6 23:55:37 lists postfix/cleanup[15641]: A57F287C036: message-id=<152a01c7a8af$64e71f00$0400a8c0 at bworg196ib52so> Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: status Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: 0 Jun 6 23:55:37 lists postfix/smtpd[15635]: public/cleanup socket: wanted attribute: reason Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: reason Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute value: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: public/cleanup socket: wanted attribute: (list terminator) Jun 6 23:55:37 lists postfix/smtpd[15635]: input attribute name: (end) Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 250 Ok: queued as A57F287C036 Jun 6 23:55:37 lists postfix/qmgr[30622]: A57F287C036: from=, size=1602, nrcpt=1 (queue active) Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_pat: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: < dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: QUIT Jun 6 23:55:37 lists postfix/smtpd[15635]: > dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4]: 221 Bye Jun 6 23:55:37 lists postfix/smtpd[15635]: disconnect from dcc-hq-host-200-59-45-4.dnsba.com[200.59.45.4] Jun 6 23:55:37 lists postfix/smtpd[15635]: master_notify: status 1 Jun 6 23:55:37 lists postfix/smtpd[15635]: connection closed Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_stop: 0x808b968 Jun 6 23:55:37 lists postfix/smtpd[15635]: watchdog_start: 0x808b968 Jun 6 23:55:37 lists postfix/virtual[15643]: A57F287C036: to=, relay=virtual, delay=0, status=bounced (unknown user: "chuchucha at news.example.com") Jun 6 23:55:37 lists postfix/cleanup[15641]: B1FB287C038: message-id=<20070607025537.B1FB287C038 at news.example.com> Jun 6 23:55:37 lists postfix/qmgr[30622]: B1FB287C038: from=<>, size=3344, nrcpt=1 (queue active) Jun 6 23:55:37 lists postfix/qmgr[30622]: A57F287C036: removed Jun 6 23:55:38 lists postfix/smtp[15647]: B1FB287C038: to=, relay=mx1.spambrake.com[200.59.45.241], delay=1, status=sent (250 Ok: queued as 29E22120227) Jun 6 23:55:38 lists postfix/qmgr[30622]: B1FB287C038: removed Resulting in a message coming back to myself telling me: This is the Postfix program at host news.example.com. I'm sorry to have to inform you that your message could not be be delivered to one or more recipients. It's attached below. For further assistance, please send mail to If you do so, please include this problem report. You can delete your own text from the attached returned message. The Postfix program : unknown user: "chuchucha at news.example.com" ****************************************** [root at lists mailman]# postconf -n ****************************************** alias_maps = hash:/etc/postfix/aliases, hash:/etc/mailman/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 home_mailbox = Maildir/ html_directory = no local_recipient_maps = $alias_map $virtual_alias_maps $virtual_mailbox_maps unix:passwd.byname mailq_path = /usr/bin/mailq manpage_directory = /usr/local/man mydestination = $myhostname, $transport_maps mydomain = news.example.com myhostname = news.example.com mynetworks = 127.0.0.1/32, 200.59.45.167/32 myorigin = $mydomain newaliases_path = /usr/bin/newaliases readme_directory = no recipient_delimiter = + sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, reject_unknown_sender_domain smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous transport_maps = mysql:/etc/postfix/mysql-transport.cf unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/mysql-virtual.cf, hash:/etc/mailman/virtual-mailman virtual_create_maildirsize = yes virtual_gid_maps = mysql:/etc/postfix/mysql-virtual-gid.cf virtual_mailbox_base = /home/vmail virtual_mailbox_limit_maps = mysql:/etc/postfix/mysql-virtual-mailbox-limit-maps.cf virtual_mailbox_limit_override = yes virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-maps.cf virtual_maildir_extended = yes virtual_maildir_limit_message = Lo siento. El mensaje no se pudo entregar debido a que el usuario excedio su capacidad en espacio. virtual_overquota_bounce = yes virtual_uid_maps = mysql:/etc/postfix/mysql-virtual-uid.cf ******************************************************* [root at lists mailman]# cat /etc/mailman/aliases ******************************************************* # STANZA START: chuchucha # CREATED: Wed Jun 6 21:20:40 2007 chuchucha: "|/usr/lib/mailman/mail/mailman post chuchucha" chuchucha-admin: "|/usr/lib/mailman/mail/mailman admin chuchucha" chuchucha-bounces: "|/usr/lib/mailman/mail/mailman bounces chuchucha" chuchucha-confirm: "|/usr/lib/mailman/mail/mailman confirm chuchucha" chuchucha-join: "|/usr/lib/mailman/mail/mailman join chuchucha" chuchucha-leave: "|/usr/lib/mailman/mail/mailman leave chuchucha" chuchucha-owner: "|/usr/lib/mailman/mail/mailman owner chuchucha" chuchucha-request: "|/usr/lib/mailman/mail/mailman request chuchucha" chuchucha-subscribe: "|/usr/lib/mailman/mail/mailman subscribe chuchucha" chuchucha-unsubscribe: "|/usr/lib/mailman/mail/mailman unsubscribe chuchucha" # STANZA END: chuchucha *************************************************************** [root at lists mailman]# cat /etc/mailman/virtual-mailman *************************************************************** # STANZA START: chuchucha # CREATED: Wed Jun 6 21:20:40 2007 chuchucha at news.example.com chuchucha chuchucha-admin at news.example.com chuchucha-admin chuchucha-bounces at news.example.com chuchucha-bounces chuchucha-confirm at news.example.com chuchucha-confirm chuchucha-join at news.example.com chuchucha-join chuchucha-leave at news.example.com chuchucha-leave chuchucha-owner at news.example.com chuchucha-owner chuchucha-request at news.example.com chuchucha-request chuchucha-subscribe at news.example.com chuchucha-subscribe chuchucha-unsubscribe at news.example.com chuchucha-unsubscribe # STANZA END: chuchucha From jeff at jwswinc.com Thu Jun 7 07:28:29 2007 From: jeff at jwswinc.com (Jeff Williams) Date: Wed, 06 Jun 2007 22:28:29 -0700 Subject: [Mailman-Users] Mailing list issue In-Reply-To: Message-ID: >> I have two different mailing lists on two different domains. One has been in >> operation for some time (shoptalk at identitypullman.com) and the other is new >> (list at rockhoundsoftball.com) > Are these domains served by the same Mailman installation? Yes. >> The added header information "(sent by list-bounces at rockhoundsoftball.com)" >> is really interfering with people's ability to receive messages as spam >> software seems to be grabbing these emails. I have compared preferences for >> both sites, and I don't know what is different. > The added information is probably added by the recipient's mail client, > not by Mailman. See > > although your symptom seems somewhat different. Well... I am a recipient to both of these lists, and this is why I can see the change. Why would my pop client change or rewrite *any* address let alone one of these but not the other? > It appears that both lists are anonymous. "Shop Talk" in the From: of > the shoptalk at identitypullman.com list comes from the description > setting on the list's General Options page. If this is set on the > other list, and it is the same Mailman, I don't know why the From: > would be different. As far as I can tell, all of the settings are identical. ______________________________________________________________________ JWSW, Incorporated http://www.jwswinc.com 509.432.1220 From manyacool81 at list.ru Thu Jun 7 10:26:18 2007 From: manyacool81 at list.ru (Elly cool) Date: Thu, 07 Jun 2007 15:26:18 +0700 Subject: [Mailman-Users] (no subject) Message-ID: Elly From jreddy at bnl.gov Thu Jun 7 14:45:28 2007 From: jreddy at bnl.gov (John Reddy) Date: Thu, 07 Jun 2007 08:45:28 -0400 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <46674C6E.1040506@is.kochi-u.ac.jp> References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> Message-ID: <4667FDE8.6080306@bnl.gov> On 6/6/2007 8:08 PM Tokio Kikuchi said the following: >>> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in >>> replace_payload_by_text >>> msg.set_payload(text, charset) >>> File "email/Message.py", line 218, in set_payload >>> File "email/Message.py", line 242, in set_charset >>> TypeError: us-ascii >> "mmarch" seems to be having trouble with the Content-Type header >> line. If I pull out that line for a given message, it is ingested, >> though it displays the full MIME text. > What exactly was the Content-Type header line ? Here's the snippit of message header. I don't see any problem with the line as is, this is how it exists in the message header. The mbox is readable by mutt (my text email reader of choice). Content-Transfer-Encoding: binary Content-Type: multipart/alternative; boundary="_----------=_1136314441199510" MIME-Version: 1.0 If I delete these lines from the mbox, the process will continue to the next entry in the mbox and then it will fail with the same set of error messages again: Content-Transfer-Encoding: binary Content-Type: multipart/alternative; boundary="_----------=_1136319711206230" MIME-Version: 1.0 Doesn't make much sense to me why it's having trouble ingesting MIME. -John -- John Reddy jreddy at bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs From tkikuchi at is.kochi-u.ac.jp Thu Jun 7 15:03:07 2007 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu, 07 Jun 2007 22:03:07 +0900 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <4667FDE8.6080306@bnl.gov> References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> <4667FDE8.6080306@bnl.gov> Message-ID: <4668020B.6060709@is.kochi-u.ac.jp> John Reddy wrote: >> What exactly was the Content-Type header line ? > Here's the snippit of message header. I don't see any problem with the > line as is, this is how it exists in the message header. The mbox is > readable by mutt (my text email reader of choice). > > Content-Transfer-Encoding: binary > Content-Type: multipart/alternative; > boundary="_----------=_1136314441199510" > MIME-Version: 1.0 > > If I delete these lines from the mbox, the process will continue to the > next entry in the mbox and then it will fail with the same set of error > messages again: How about deleteing the first line (Content-Transfer-Encoding: binary) and leave the rest. > > Content-Transfer-Encoding: binary > Content-Type: multipart/alternative; > boundary="_----------=_1136319711206230" > MIME-Version: 1.0 > > Doesn't make much sense to me why it's having trouble ingesting MIME. I believe CTE should not be in the main section of message header if Content-Type is multipart. > > -John > -- Tokio Kikuchi, tkikuchi at is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ From brad at shub-internet.org Thu Jun 7 15:37:20 2007 From: brad at shub-internet.org (Brad Knowles) Date: Thu, 7 Jun 2007 08:37:20 -0500 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <4668020B.6060709@is.kochi-u.ac.jp> References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> <4667FDE8.6080306@bnl.gov> <4668020B.6060709@is.kochi-u.ac.jp> Message-ID: On 6/7/07, Tokio Kikuchi wrote: > I believe CTE should not be in the main section of message header if > Content-Type is multipart. In addition, would this not point to a potential bug in the "email" module that we inherit from Python (see ), as opposed to a potential bug within Mailman itself? -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From benjamin at py-soft.co.uk Thu Jun 7 15:01:46 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 07 Jun 2007 14:01:46 +0100 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> Message-ID: <466801BA.7040709@py-soft.co.uk> Jennifer Redman wrote: > However, the integration with Postfix -- not so good, appears to be > something to do with the Virtual Mailbox setup. If you can set aside a sub-domain for your mailing lists, eg lists.example.com, then it's worth using the sendmail mm-handler script with postfix. Download the script from http://mailman.svn.sourceforge.net/viewvc/*checkout*/mailman/trunk/mailman/contrib/mm-handler?revision=5100 Install it in /usr/local/bin, make sure it's executable by mailman. Edit the config at the top of the file. Edit postfix/main.cf as follows: relay_domains = lists.example.com # Needed for interface to mailman: transport_maps = hash:/etc/postfix/transport mailman_destination_recipient_limit = 1 Add the following to /etc/postfix/virtual: ## ## Redirect mail to the standard Mailman admin addresses to the ## master admin address. (Midway.uchicago.edu is our site's central ## mail-routing server, and it carries aliases for maintenance groups. ## Not a good plan to entrust Mailman maintenance mail to Mailman.) ## mailman at lists.example.com mailman-owner at example.com mailman-owner at lists.example.com mailman-owner at example.com ## ## These addresses are required or recommended either by convention ## or by RFC 2142, "Mailbox Names for Common Services, Roles and ## Functions". Honor them. ## MAILER-DAEMON at lists.example.com mailman-owner at example.com postmaster at lists.example.com mailman-owner at example.com webmaster at lists.example.com mailman-owner at example.com abuse at lists.example.com mailman-owner at example.com root at lists.example.com mailman-owner at example.com Make sure that mailman-owner is aliased to an admin account. Create the file /etc/postfix/transport as follows: lists.example.com mailman:example.com Add the following to postfix/master.cf: mailman unix - n n - - pipe flags=FRu user=mailman:mailman argv=/usr/local/bin/mm-handler ${nexthop} ${user} -r $sender Run postmap /etc/postfix/transport, postmap /etc/postfix/virtual and restart postfix. Edit the mailman config file mm_cfg.py to include: MTA = None I know it's a bit more complicated initially, but with this set up this is it! :-) There are other way of achieving this but none, in my opinion, are as good as mm-handler. See the link [1] to decide whether mm-handler is suitable for your site. As you use postfix, you might also want to install the Postfix XVERP patch - see [2] for the patch and [3] for details of config options. (You'll also need to add smtpd_authorized_verp_clients = 127.0.0.1 to /etc/postfix/main.cf) Take care, Ben [1] http://mailman.svn.sourceforge.net/viewvc/mailman/trunk/mailman/contrib/README.mm-handler?view=markup [2] https://sourceforge.net/tracker/index.php?func=detail&aid=869638&group_id=103&atid=300103 [3] https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 From jreddy at bnl.gov Thu Jun 7 15:46:08 2007 From: jreddy at bnl.gov (John Reddy) Date: Thu, 07 Jun 2007 09:46:08 -0400 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> <4667FDE8.6080306@bnl.gov> <4668020B.6060709@is.kochi-u.ac.jp> Message-ID: <46680C20.80103@bnl.gov> On 6/7/2007 9:37 AM Brad Knowles said the following: > In addition, would this not point to a potential bug in the "email" > module that we inherit from Python (see > ), as opposed to a > potential bug within Mailman itself? This may be the case. This system was recently (a couple of months ago) upgraded to the 64bit Debian. It could be a problem within one of the packages, either mailman or python. -John -- John Reddy jreddy at bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs From jreddy at bnl.gov Thu Jun 7 15:46:32 2007 From: jreddy at bnl.gov (John Reddy) Date: Thu, 07 Jun 2007 09:46:32 -0400 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <4668020B.6060709@is.kochi-u.ac.jp> References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> <4667FDE8.6080306@bnl.gov> <4668020B.6060709@is.kochi-u.ac.jp> Message-ID: <46680C38.2010600@bnl.gov> On 6/7/2007 9:03 AM Tokio Kikuchi said the following: > John Reddy wrote: > >>> What exactly was the Content-Type header line ? >> Here's the snippit of message header. I don't see any problem with >> the line as is, this is how it exists in the message header. The >> mbox is readable by mutt (my text email reader of choice). >> >> Content-Transfer-Encoding: binary >> Content-Type: multipart/alternative; >> boundary="_----------=_1136314441199510" >> MIME-Version: 1.0 >> >> If I delete these lines from the mbox, the process will continue to >> the next entry in the mbox and then it will fail with the same set of >> error messages again: > How about deleteing the first line (Content-Transfer-Encoding: binary) > and leave the rest. Removing the Content-Transfer-Encoding header doesn't resolve the problem. Only removing the Content-Type header does. It's not that the mails suddenly changed. We have dozens of mailing lists with mbox files going back a couple of years. It's just that I've been looking into this recently and just noticed it. -John -- John Reddy jreddy at bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs From brad at shub-internet.org Thu Jun 7 16:20:45 2007 From: brad at shub-internet.org (Brad Knowles) Date: Thu, 7 Jun 2007 09:20:45 -0500 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <46680C20.80103@bnl.gov> References: <46672875.1030608@bnl.gov> <46674C6E.1040506@is.kochi-u.ac.jp> <4667FDE8.6080306@bnl.gov> <4668020B.6060709@is.kochi-u.ac.jp> <46680C20.80103@bnl.gov> Message-ID: On 6/7/07, John Reddy wrote: > This may be the case. This system was recently (a couple of months ago) > upgraded to the 64bit Debian. It could be a problem within one of the > packages, either mailman or python. Now that you remind me that this is Debian and you're using the packaged version of Mailman, I am having this vague feeling that we've run into problems before with Debian and the way they handle (mishandle) the email module within Python. I'm not sure this is related, but check out the thread at . If this does turn out to be related, then it sounds like we have another issue to put into the FAQ Wizard. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Thu Jun 7 16:31:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 7 Jun 2007 07:31:36 -0700 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <46680C38.2010600@bnl.gov> Message-ID: John Reddy wrote: >Removing the Content-Transfer-Encoding header doesn't resolve the >problem. Only removing the Content-Type header does. It's not that the >mails suddenly changed. We have dozens of mailing lists with mbox files >going back a couple of years. It's just that I've been looking into >this recently and just noticed it. What are all the sub-part Content-* headers in this message? -- 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 Thu Jun 7 17:48:22 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Thu, 7 Jun 2007 10:48:22 -0500 (CDT) Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: Mail from 'Brad Knowles ' dated: Thu, 7 Jun 2007 09:20:45 -0500 Message-ID: <200706071548.l57FmMt3009972@britaine.ctd.anl.gov> On 6/7/07, John Reddy wrote: >> This may be the case. This system was recently (a couple of months ago) >> upgraded to the 64bit Debian. It could be a problem within one of the >> packages, either mailman or python. And Brad Knowles replied: >Now that you remind me that this is Debian and you're using the >packaged version of Mailman, I am having this vague feeling that >we've run into problems before with Debian and the way they handle >(mishandle) the email module within Python. > >I'm not sure this is related, but check out the thread at >. > >If this does turn out to be related, then it sounds like we have >another issue to put into the FAQ Wizard. Because I had no idea exactly what source I was using when I first installed Mailman 2.1.5+ on Ubuntu (based on Debian), I decided that I had to use the current 2.1.9 source. My management wanted a package install, so I built a package from the 2.1.9 source. It was not difficult. I had to determine how to tell the package not to remove the pythonlib library, which, in my case, was not empty. ---------------------------------------------------------------------- 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 benjamin at py-soft.co.uk Thu Jun 7 18:13:36 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Thu, 07 Jun 2007 17:13:36 +0100 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <466801BA.7040709@py-soft.co.uk> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> <466801BA.7040709@py-soft.co.uk> Message-ID: <46682EB0.8010509@py-soft.co.uk> Benjamin Donnachie wrote: > If you can set aside a sub-domain for your mailing lists, eg > lists.example.com, then it's worth using the sendmail mm-handler script > with postfix. I've just written a very simple script which I use as a cronjob to keep a postfix access map of current lists up-to-date. Thus avoiding potential backscatter with the listhost domain. If you adopt the mm-handler method, please let me know if you'd like a copy. Take care, Ben From marcy.setter at gmail.com Thu Jun 7 18:01:00 2007 From: marcy.setter at gmail.com (Marcy Setter) Date: Thu, 7 Jun 2007 12:01:00 -0400 Subject: [Mailman-Users] Newbie Question Message-ID: <46682bbd.5e39152f.24e6.ffffa44e@mx.google.com> I'm with a non-profit and looking at replacements for Lyris List manager. Does Mailman offer a web interface option to read messages as well as individual emails? Thank you, Marcy From pdbogen at gmail.com Thu Jun 7 21:43:57 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 7 Jun 2007 14:43:57 -0500 Subject: [Mailman-Users] Fwd: Newbie Question In-Reply-To: <6fbe3da00706071243h7bfa9caic64d2de02a681622@mail.gmail.com> References: <46682bbd.5e39152f.24e6.ffffa44e@mx.google.com> <6fbe3da00706071243h7bfa9caic64d2de02a681622@mail.gmail.com> Message-ID: <6fbe3da00706071243j15144eeav511dcfd103f4cbf6@mail.gmail.com> Forgot reply-to-all. Sorry for duplicates. ---------- Forwarded message ---------- From: Patrick Bogen Date: Jun 7, 2007 2:43 PM Subject: Re: [Mailman-Users] Newbie Question To: Marcy Setter On 6/7/07, Marcy Setter wrote: > I'm with a non-profit and looking at replacements for Lyris List manager. > Does Mailman offer a web interface option to read messages as well as > individual emails? For reading, yes. You can review the archives, and (with a bit more work) incorporate a search function into them. Note that there is no mechanism for SENDING mail to the list using a website (you'd have to use something else, such as a web-based email solution, like Horde or Squirrelmail.) -- - Patrick Bogen -- - Patrick Bogen From jenred at gmail.com Fri Jun 8 01:30:02 2007 From: jenred at gmail.com (Jennifer Redman) Date: Thu, 7 Jun 2007 16:30:02 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <466801BA.7040709@py-soft.co.uk> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> <466801BA.7040709@py-soft.co.uk> Message-ID: <93f118f0706071630w7e2a14f2h6c11a8557274fd11@mail.gmail.com> Your script and instructions work beautifully. Had to change a few paths and kept getting a no module error when I added MTA = None -- easy configuration compared to the other method I was attempting. Thanks Ben! Jen On 6/7/07, Benjamin Donnachie wrote: > > Jennifer Redman wrote: > > However, the integration with Postfix -- not so good, appears to be > > something to do with the Virtual Mailbox setup. > > If you can set aside a sub-domain for your mailing lists, eg > lists.example.com, then it's worth using the sendmail mm-handler script > with postfix. > > Download the script from > > http://mailman.svn.sourceforge.net/viewvc/*checkout*/mailman/trunk/mailman/contrib/mm-handler?revision=5100 > > Install it in /usr/local/bin, make sure it's executable by mailman. > Edit the config at the top of the file. > > Edit postfix/main.cf as follows: > > relay_domains = lists.example.com > # Needed for interface to mailman: > transport_maps = hash:/etc/postfix/transport > mailman_destination_recipient_limit = 1 > > > Add the following to /etc/postfix/virtual: > > ## > ## Redirect mail to the standard Mailman admin addresses to the > ## master admin address. (Midway.uchicago.edu is our site's central > ## mail-routing server, and it carries aliases for maintenance groups. > ## Not a good plan to entrust Mailman maintenance mail to Mailman.) > ## > mailman at lists.example.com mailman-owner at example.com > mailman-owner at lists.example.com mailman-owner at example.com > > ## > ## These addresses are required or recommended either by convention > ## or by RFC 2142, "Mailbox Names for Common Services, Roles and > ## Functions". Honor them. > ## > MAILER-DAEMON at lists.example.com mailman-owner at example.com > postmaster at lists.example.com mailman-owner at example.com > webmaster at lists.example.com mailman-owner at example.com > abuse at lists.example.com mailman-owner at example.com > root at lists.example.com mailman-owner at example.com > > Make sure that mailman-owner is aliased to an admin account. > > Create the file /etc/postfix/transport as follows: > > lists.example.com mailman:example.com > > Add the following to postfix/master.cf: > > mailman unix - n n - - pipe > flags=FRu user=mailman:mailman > argv=/usr/local/bin/mm-handler ${nexthop} ${user} -r $sender > > > Run postmap /etc/postfix/transport, postmap /etc/postfix/virtual and > restart postfix. > > Edit the mailman config file mm_cfg.py to include: > > MTA = None > > > I know it's a bit more complicated initially, but with this set up this > is it! :-) There are other way of achieving this but none, in my > opinion, are as good as mm-handler. > > See the link [1] to decide whether mm-handler is suitable for your site. > > As you use postfix, you might also want to install the Postfix XVERP > patch - see [2] for the patch and [3] for details of config options. > (You'll also need to add smtpd_authorized_verp_clients = 127.0.0.1 to > /etc/postfix/main.cf) > > Take care, > > Ben > > > [1] > > http://mailman.svn.sourceforge.net/viewvc/mailman/trunk/mailman/contrib/README.mm-handler?view=markup > [2] > > https://sourceforge.net/tracker/index.php?func=detail&aid=869638&group_id=103&atid=300103 > [3] > > https://sourceforge.net/tracker/?func=detail&atid=300103&aid=731100&group_id=103 > From msapiro at value.net Fri Jun 8 02:33:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 7 Jun 2007 17:33:42 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix2.5 Virtual Mailboxes In-Reply-To: <93f118f0706071630w7e2a14f2h6c11a8557274fd11@mail.gmail.com> Message-ID: Jennifer Redman wrote: > >Had to change a few paths and kept getting a no module error when I added >MTA = None -- easy configuration compared to the other method I was >attempting. I assume you figured it out, but if not, it must be MTA = None and not MTA = 'None' -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jenred at gmail.com Fri Jun 8 03:18:56 2007 From: jenred at gmail.com (Jennifer Redman) Date: Thu, 7 Jun 2007 18:18:56 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix2.5 Virtual Mailboxes In-Reply-To: References: <93f118f0706071630w7e2a14f2h6c11a8557274fd11@mail.gmail.com> Message-ID: <93f118f0706071818h195d88ffi6de80575f4c075b6@mail.gmail.com> I did originally make the MTA = 'None' mistake. Thanks for your help as well Mark. Jen On 6/7/07, Mark Sapiro wrote: > > Jennifer Redman wrote: > > > >Had to change a few paths and kept getting a no module error when I added > >MTA = None -- easy configuration compared to the other method I was > >attempting. > > > I assume you figured it out, but if not, it must be > > MTA = None > > and not > > MTA = 'None' > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From msapiro at value.net Fri Jun 8 03:50:26 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 7 Jun 2007 18:50:26 -0700 Subject: [Mailman-Users] Mailing list issue In-Reply-To: Message-ID: Jeff Williams wrote: > >Well... I am a recipient to both of these lists, and this is why I can see >the change. Why would my pop client change or rewrite *any* address let >alone one of these but not the other? Ask Bill Gates :-) >> It appears that both lists are anonymous. "Shop Talk" in the From: of >> the shoptalk at identitypullman.com list comes from the description >> setting on the list's General Options page. If this is set on the >> other list, and it is the same Mailman, I don't know why the From: >> would be different. > >As far as I can tell, all of the settings are identical. I don't understand why there is no 'real name' (from the list's description) in the From: address of the list at rockhoundsoftball.com posts. I also don't understand why one list would get the "(sent by list-bounces at rockhoundsoftball.com)" added and the other not, but mailman is not adding this to either list's posts. Both list's posts are sent by the corresponding -bounces address and contain Sender: and Errors-To: headers with the -bounces address. Sometimes outgoing MTAs rewrite From: headers if the domain in From: is a CNAME, but I looked at your DNS entries and that is not the case here I don't understand just where this From: is getting munged and what is causing it and why it happens only to one list, but I'm sure it is not Mailman that's doing it. Are these two domains treated differently by the outgoing MTA? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From root at home.mbg.it Fri Jun 8 03:32:36 2007 From: root at home.mbg.it (Gio MBG Canepa (root)) Date: Fri, 8 Jun 2007 03:32:36 +0200 Subject: [Mailman-Users] Mail from GioMBG > Move and rename a list to new hostname and rebuilt old archive into new-list-name Message-ID: <200706080332.36558.root@home.mbg.it> Hi All! It's GioMBG from 9Records.com writing (a very happy mailman user) The question: I have built now my new fedora moonshine and I have changed the host name: from > home.mbg.it > to > home.9records.com I woul like to rename my old list > 9records > to > mailman so to do email to list like > mailman at home.9records.com suggestions? many thanks 2 all and BIG Respect to Mark Sapiro Kindly GioMBG -- Gi? "MBG" Canepa - E Mail: mbg a mbg.it Phone & Fax +39 0541 985 737 - Mobile +39 393 33 567 07 http://www.mbg.it | http://www.9Records.com Snail mail P.O. Box 59 / 47838 Riccione Italy From msapiro at value.net Fri Jun 8 04:22:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 7 Jun 2007 19:22:57 -0700 Subject: [Mailman-Users] Mail from GioMBG > Move and rename a list to newhostname and rebuilt old archive into new-list-name In-Reply-To: <200706080332.36558.root@home.mbg.it> Message-ID: Gio MBG Canepa (root) wrote: >I woul like to rename my old list > 9records > to > mailman >so to do email to list like > mailman at home.9records.com >suggestions? See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carbonnb at gmail.com Fri Jun 8 16:30:42 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Fri, 8 Jun 2007 10:30:42 -0400 Subject: [Mailman-Users] Default Languages Message-ID: Is it possible to have the admin interface for a list in 1 language, English, and have the user interface a different language, French, using 2.1.6 or 2.1.9? The only thing I can come up with is to actually change the language of the list to French, and edit the translation file and remove the translations for the Admin interface so that it gets displayed in the default text, which is English. Is there an easier way to do this? -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From msapiro at value.net Fri Jun 8 17:16:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 08:16:54 -0700 Subject: [Mailman-Users] Default Languages In-Reply-To: Message-ID: Bryan Carbonnell wrote: >Is it possible to have the admin interface for a list in 1 language, >English, and have the user interface a different language, French, >using 2.1.6 or 2.1.9? > >The only thing I can come up with is to actually change the language >of the list to French, and edit the translation file and remove the >translations for the Admin interface so that it gets displayed in the >default text, which is English. > >Is there an easier way to do this? I'm not sure if this is what you wan't, but you can set the list's default language to English, and make sure that French is an available language. Then users can set their preferred language to French. The tricky part is setting the default language for a new member to French. This would require implementing a new list attribute, e.g., default_member_language, or a really ugly hack to Mailman/MailList.py in the ApprovedAddMember() method. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carbonnb at gmail.com Fri Jun 8 17:29:55 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Fri, 8 Jun 2007 11:29:55 -0400 Subject: [Mailman-Users] Default Languages In-Reply-To: References: Message-ID: On 6/8/07, Mark Sapiro wrote: > Bryan Carbonnell wrote: > > >Is it possible to have the admin interface for a list in 1 language, > >English, and have the user interface a different language, French, > >using 2.1.6 or 2.1.9? > > > >The only thing I can come up with is to actually change the language > >of the list to French, and edit the translation file and remove the > >translations for the Admin interface so that it gets displayed in the > >default text, which is English. > > > >Is there an easier way to do this? > > > I'm not sure if this is what you wan't, but you can set the list's > default language to English, and make sure that French is an available > language. Then users can set their preferred language to French. > > The tricky part is setting the default language for a new member to > French. This would require implementing a new list attribute, e.g., > default_member_language, or a really ugly hack to Mailman/MailList.py > in the ApprovedAddMember() method. I don't want the user to have a choice in their default language. Here is the problem I have been running into, with the choice of English and French, when there user confirms their subscription, the confirmation page is in English, because that is the default. The user never gets a chance to see the confirmation in French. That is why I was looking for a way to have my cake and eat it too :) -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From msapiro at value.net Fri Jun 8 18:14:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 09:14:17 -0700 Subject: [Mailman-Users] Default Languages In-Reply-To: Message-ID: Bryan Carbonnell wrote: > >I don't want the user to have a choice in their default language. > >Here is the problem I have been running into, with the choice of >English and French, when there user confirms their subscription, the >confirmation page is in English, because that is the default. > >The user never gets a chance to see the confirmation in French. To address the confirmation page, you could apply the following patch to Mailman/Cgi/confirm.py --- Mailman/Cgi/confirm.py 2007-05-07 15:34:26.593750000 -0700 +++ Mailman/Cgi/confirmx.py 2007-06-08 08:47:46.000000000 -0700 @@ -66,8 +66,12 @@ return # Set the language for the list - i18n.set_language(mlist.preferred_language) - doc.set_language(mlist.preferred_language) + try: + p_l = mlist.default_user_language + except NameError: + p_l = mlist.preferred_language + i18n.set_language(p_l) + doc.set_language(p_l) # Get the form data to see if this is a second-step confirmation cgidata = cgi.FieldStorage(keep_blank_values=1) You could than use bin/withlist or the following shell script to set default_user_language for the target list. #! /bin/bash tf=`mktemp` echo mlist.default_user_language = \'fr\' > $tf bin/config_list -i $tf listname rm $tf You could also patch the the ApprovedAddMember() method in Mailman/MailList.py in a similar way the set the member's language if desired. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carbonnb at gmail.com Fri Jun 8 19:23:59 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Fri, 8 Jun 2007 13:23:59 -0400 Subject: [Mailman-Users] Default Languages In-Reply-To: References: Message-ID: On 6/8/07, Mark Sapiro wrote: > Bryan Carbonnell wrote: > > > >I don't want the user to have a choice in their default language. > > > >Here is the problem I have been running into, with the choice of > >English and French, when there user confirms their subscription, the > >confirmation page is in English, because that is the default. > > > >The user never gets a chance to see the confirmation in French. > > > To address the confirmation page, you could apply the following patch > to Mailman/Cgi/confirm.py Thanks Mark, I'll give this a shot and report back -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From jeffs at tolisgroup.com Fri Jun 8 19:48:15 2007 From: jeffs at tolisgroup.com (Jeff Shepherd) Date: Fri, 8 Jun 2007 10:48:15 -0700 Subject: [Mailman-Users] Complete List... Message-ID: <54CA8C00-F22B-427F-83E9-B8195AF30E4E@tolisgroup.com> Hello, I'm relatively new to Mailman (switching from ezmlm) and I'm curious if there is a way (outside of the command line) if you can view a listing of a complete list to be able to print it for hard copy reasons, so that you don't have to print 26 different ones? I figured out how to do that in the command line (/usr/lib/mailman/ bin/list_memers [listname]) but most of the company management doesn't know the command line and I'm trying to take the step of them having to go through me to export the list in the command line and give them the ability to do it themselves. Thanks for the help! -Jeff From mbomgardner at kletc.org Fri Jun 8 19:52:25 2007 From: mbomgardner at kletc.org (Mark Bomgardner) Date: Fri, 8 Jun 2007 12:52:25 -0500 Subject: [Mailman-Users] Announcement List Message-ID: <00e501c7a9f5$c5eec630$51cc5290$@org> I am using Mailman 2.1.9 with an announcement list. I don't want to use the moderated option, so I am using the Approved: option. The problem is that this shows up in the announcement. Can this be removed and still allow the message to go through? markb From b19141 at britaine.ctd.anl.gov Fri Jun 8 21:06:05 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Fri, 8 Jun 2007 14:06:05 -0500 (CDT) Subject: [Mailman-Users] Complete List... In-Reply-To: Mail from 'Jeff Shepherd ' dated: Fri, 8 Jun 2007 10:48:15 -0700 Message-ID: <200706081906.l58J651s020335@britaine.ctd.anl.gov> Jeff Shepherd wrote: >Hello, >I'm relatively new to Mailman (switching from ezmlm) and I'm curious >if there is a way (outside of the command line) if you can view a >listing of a complete list to be able to print it for hard copy >reasons, so that you don't have to print 26 different ones? > >I figured out how to do that in the command line (/usr/lib/mailman/ >bin/list_memers [listname]) but most of the company management >doesn't know the command line and I'm trying to take the step of them >having to go through me to export the list in the command line and >give them the ability to do it themselves. I wrote a shell script that essentially does #!/bin/csh foreach list (`ls /var/lib/mailman/lists`) /usr/lib/mailman/bin/list_members $list end does some reformatting, and stores the file on the Mailman machine. The output has -------- listname1 user1 at example.com ... -------- listname2 user2 at example.com ... -------- so it can be searched by listname or e-mail address. I run the cron every hour. The list of all subscribers to all lists is available to those who have access to the Mailman machine. Something like that might suit your needs. Depending upon the frequency of subscribes and unsubscribes, you could run it more frequently. ---------------------------------------------------------------------- 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 gilmore.126 at osu.edu Fri Jun 8 21:54:25 2007 From: gilmore.126 at osu.edu (Melinda Gilmore) Date: Fri, 8 Jun 2007 15:54:25 -0400 Subject: [Mailman-Users] no subscribers Message-ID: <008301c7aa06$d13a19c0$6ef39280@oitlan.oit.ohiostate.edu> Help! We just had a strange thing happen, a lists subscribers were all removed and no mail was going out. If there are not subscribers where does the mail go? I have looked in all the logs and it looks like the mail was sent. However, it seems to go into la la land. User wants to know if the mail is kept somewhere where we can retrieve. Not where that mail is? Any guidance would be appreciated. Melinda Gilmore Systems Engineer OIT/Enterprise Messaging 614-292-4953 From msapiro at value.net Fri Jun 8 21:57:46 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 12:57:46 -0700 Subject: [Mailman-Users] Complete List... In-Reply-To: <54CA8C00-F22B-427F-83E9-B8195AF30E4E@tolisgroup.com> Message-ID: Jeff Shepherd wrote: >I'm relatively new to Mailman (switching from ezmlm) and I'm curious >if there is a way (outside of the command line) if you can view a >listing of a complete list to be able to print it for hard copy >reasons, so that you don't have to print 26 different ones? See and also . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 8 22:07:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 13:07:27 -0700 Subject: [Mailman-Users] no subscribers In-Reply-To: <008301c7aa06$d13a19c0$6ef39280@oitlan.oit.ohiostate.edu> Message-ID: Melinda Gilmore wrote: >Help! We just had a strange thing happen, a lists subscribers were all >removed and no mail was going out. If there are not subscribers where does >the mail go? I have looked in all the logs and it looks like the mail was >sent. However, it seems to go into la la land. If a list has no members, no post is sent. What did you see in what log? You might have seen a reject of an attempted post. >User wants to know if the mail is kept somewhere where we can retrieve. Not >where that mail is? Any guidance would be appreciated. Assuming archiving is enabled for the list, a post will be in the list's archive. With default archiving settings, a copy of the message is also in the archives/private/listname.mbox/listname.mbox file. If the list is digestable, even if there are no members, the post will be added to lists/listname/digest.mbox, but this file is deleted when periodic or size triggered digests are processed, and with no members, no digest will be sent. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 8 22:21:13 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 13:21:13 -0700 Subject: [Mailman-Users] Announcement List In-Reply-To: <00e501c7a9f5$c5eec630$51cc5290$@org> Message-ID: Mark Bomgardner wrote: >I am using Mailman 2.1.9 with an announcement list. I don't want to use the >moderated option, so I am using the Approved: option. The >problem is that this shows up in the announcement. Can this be removed and >still allow the message to go through? If you post with an actual Approved: header, Mailman will remove it. If you post with an Approved: line as the first non-blank line in the first text/plain part of the message, it will be removed from that part and an attempt will be made to remove it from other text/* parts of the message (e.g. from the text/html alternative of a multipart/alternative message). This attempt does not always succeed. In particular, if the poster's MUA creates a multipart/alternative message and because of additional or whatever tags, the Approved: gets split across lines in the raw HTML, it won't be removed. The best solution is to post with an actual header or post plain text only. See the thread at for more on this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From scry_mr at yahoo.ca Sat Jun 9 01:28:55 2007 From: scry_mr at yahoo.ca (Juan Miscaro) Date: Fri, 8 Jun 2007 19:28:55 -0400 (EDT) Subject: [Mailman-Users] removed subcribers still there Message-ID: <332322.41645.qm@web63910.mail.re1.yahoo.com> I have removed a lot of stale subscribers from my lists with the command $ remove_members --fromall $ mailmanctl stop $ mailmanctl start I have also restarted my MTA (postfix). Nevertheless, my mail logs continue to show sending attempts to the removed addresses. The peculiarity here is that the subscribers happen to reside on my own internal domain. The accounts however do not exist. As expected, when I search for the recipients I see in my mail logs I do not find them: $ find_member .*\@example.com$ What's happening? I am running Mailman 2.1.8 on OpenBSD 4.0 with Postfix 2.3.2. Juan Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail at http://mrd.mail.yahoo.com/try_beta?.intl=ca From brad at shub-internet.org Sat Jun 9 01:36:47 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 8 Jun 2007 18:36:47 -0500 Subject: [Mailman-Users] removed subcribers still there In-Reply-To: <332322.41645.qm@web63910.mail.re1.yahoo.com> References: <332322.41645.qm@web63910.mail.re1.yahoo.com> Message-ID: On 6/8/07, Juan Miscaro wrote: > Nevertheless, my mail logs continue to show sending attempts to the > removed addresses. It sounds to me like those messages were already delivered by Mailman to your MTA, and your MTA is continuing to try to deliver those messages. > As expected, when I search for the recipients I see in my mail logs I > do not find them: > > $ find_member .*\@example.com$ They may be listed as local subscribers without a domain portion. Try doing a "find_member" based on the user portion of the name. That's assuming that you've got new messages that are still coming out of Mailman and being delivered to the MTA, for these customers. This could also be a problem with mail forwarding. If you turn on personalization, the return address for each outgoing message will have the original recipient name encoded in it, and that can help you figure out where the messages are originally being addressed. > What's happening? I am running Mailman 2.1.8 on OpenBSD 4.0 with > Postfix 2.3.2. You might want to upgrade to Mailman 2.1.9, since there was a known security vulnerability with version 2.1.8. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Sat Jun 9 01:46:05 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 16:46:05 -0700 Subject: [Mailman-Users] removed subcribers still there In-Reply-To: Message-ID: Brad Knowles wrote: >On 6/8/07, Juan Miscaro wrote: > >> Nevertheless, my mail logs continue to show sending attempts to the >> removed addresses. > >It sounds to me like those messages were already delivered by Mailman >to your MTA, and your MTA is continuing to try to deliver those >messages. > Another possibility is that for these non-existent local addresses The local outgoing MTA is reporting an error at SMTP time that Mailman thinks is retryable causing mailman to queue the message in its 'retry' queue for later retry. What's in Mailman's smtp and smtp-failure logs and Mailman's qfiles/retry directory? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jobfile at media-alliance.org Sat Jun 9 03:12:24 2007 From: jobfile at media-alliance.org (Media Alliance JobFile) Date: Fri, 08 Jun 2007 18:12:24 -0700 Subject: [Mailman-Users] does mailman filter Message-ID: <4669FE78.30408@media-alliance.org> I have been sending an email to my list with the same subject, and it does not go to "pending moderator requests." I have tried about 10 times, and I am thinking it might be blocking me because it thinks I am spamming. Is this a possibility? My email is a job list, so it probably contains many spammy elements, like repetition and similar format. It is mostly plaintext with a bold here and there. Any help is appreciated. From msapiro at value.net Sat Jun 9 03:52:30 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 8 Jun 2007 18:52:30 -0700 Subject: [Mailman-Users] does mailman filter In-Reply-To: <4669FE78.30408@media-alliance.org> Message-ID: Media Alliance JobFile wrote: >I have been sending an email to my list with the same subject, and it >does not go to "pending moderator requests." Do you have access to Mailman's logs? If so, check Mailman's vette log. Also see for general troubleshooting. >I have tried about 10 times, and I am thinking it might be blocking me >because it thinks I am spamming. Is this a possibility? Yes, see Privacy options...->Spam filters in the list's admin interface. >My email is a job list, so it probably contains many spammy elements, >like repetition and similar format. It is mostly plaintext with a bold >here and there. Any help is appreciated. Mailman's spam filtering is based only on headers, not body contents, although it is possible the list's Content filtering is deleting all the message body parts, e.g. if the post is an HTML only message and the list doesn't accepot text/html parts. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From scry_mr at yahoo.ca Sat Jun 9 13:02:55 2007 From: scry_mr at yahoo.ca (Juan Miscaro) Date: Sat, 9 Jun 2007 07:02:55 -0400 (EDT) Subject: [Mailman-Users] removed subcribers still there In-Reply-To: Message-ID: <908308.69524.qm@web63915.mail.re1.yahoo.com> --- Mark Sapiro wrote: > Brad Knowles wrote: > > >On 6/8/07, Juan Miscaro wrote: > > > >> Nevertheless, my mail logs continue to show sending attempts to > the > >> removed addresses. > > > >It sounds to me like those messages were already delivered by > Mailman > >to your MTA, and your MTA is continuing to try to deliver those > >messages. My MTA is rejecting with a 550 (user does not exist): Jun 9 06:46:32 paladin postfix/smtpd[24327]: 096FCC4408: reject: RCPT from localhost[127.0.0.1]: 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table; from= to= proto=ESMTP helo= > Another possibility is that for these non-existent local addresses > The > local outgoing MTA is reporting an error at SMTP time that Mailman > thinks is retryable causing mailman to queue the message in its > 'retry' queue for later retry. > What's in Mailman's smtp and smtp-failure logs and Mailman's > qfiles/retry directory? Indeed I did find related data in these places. $ tail -1 smtp Jun 09 06:46:35 2007 (10585) <20070604205900.3839FC43EC at mail.example.com> smtp to list for 500 recips, completed in 123.168 seconds $ tail -600 smtp-failure | grep example Jun 09 06:46:35 2007 (10585) delivery to user at example.com failed with code -1: Connection unexpectedly closed $ ls qfiles/retry/ total 340 -rw-rw---- 1 _mailman _mailman 168K Jun 9 06:46 1180990742.5870631+624e43c97588e6d1b02021804f85513e7a31e195.pck What can I do to stop this delivery? Just delete the .pck file? Thank you very much. Juan Make free worldwide PC-to-PC calls. Try the new Yahoo! Canada Messenger with Voice at http://ca.messenger.yahoo.com/ From stephen at xemacs.org Sat Jun 9 13:56:23 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 09 Jun 2007 20:56:23 +0900 Subject: [Mailman-Users] removed subcribers still there In-Reply-To: <908308.69524.qm@web63915.mail.re1.yahoo.com> References: <908308.69524.qm@web63915.mail.re1.yahoo.com> Message-ID: <87zm39fijc.fsf@uwakimon.sk.tsukuba.ac.jp> Juan Miscaro writes: > My MTA is rejecting with a 550 (user does not exist): No, it would appear that it is in an error state, closing the connection before receiving and acknowledging a QUIT command (required by RFC 2821, section 4.1.1.10): > $ tail -600 smtp-failure | grep example > Jun 09 06:46:35 2007 (10585) delivery to user at example.com failed with > code -1: Connection unexpectedly closed RFC 2821 requires that the sender (mailman) treat this as a temporary failure of the "command or transaction". The receiving MTA may think that the RCPT TO command has succeeded (in the sense of having sent a valid response, even though it's a failure response), I guess, but it's not obvious to me that Mailman necessarily gets the 550. This is arguably a bug in Mailman (if it actually sees the 550 response), but it's definitely buggy and very error-prone behavior on the part of the MTA. You might want to get one that's a little more conformant with the spirit of the RFCs. > -rw-rw---- 1 _mailman _mailman 168K Jun 9 06:46 > 1180990742.5870631+624e43c97588e6d1b02021804f85513e7a31e195.pck > > What can I do to stop this delivery? Just delete the .pck file? Deleting the .pck file should do the trick. From msapiro at value.net Sun Jun 10 03:25:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 9 Jun 2007 18:25:24 -0700 Subject: [Mailman-Users] Improved processing of Approve(d): lines - was: Announcement List In-Reply-To: Message-ID: Mark Sapiro wrote: > >If you post with an Approved: line as the first non-blank line in the >first text/plain part of the message, it will be removed from that >part and an attempt will be made to remove it from other text/* parts >of the message (e.g. from the text/html alternative of a >multipart/alternative message). This attempt does not always succeed. >In particular, if the poster's MUA creates a multipart/alternative >message and because of additional or whatever tags, the >Approved: gets split across lines in the raw HTML, it won't >be removed. I have implemented an enhancement to the module (Mailman/Handlers/Approve.py) that looks for and removes Approve(d): lines. The enhancement should resolve the failed attempts at removal. The new code has been checked in to SVN and will be in the next release of Mailman. If you need this funcionality, the module can be obtained at . This module should work in any Mailman 2.1.x version. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From benjamin at py-soft.co.uk Sun Jun 10 16:08:30 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Sun, 10 Jun 2007 15:08:30 +0100 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <93f118f0706071630w7e2a14f2h6c11a8557274fd11@mail.gmail.com> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> <466801BA.7040709@py-soft.co.uk> <93f118f0706071630w7e2a14f2h6c11a8557274fd11@mail.gmail.com> Message-ID: <466C05DE.2000109@py-soft.co.uk> Jennifer Redman wrote: > Your script and instructions work beautifully. Excellent stuff! :-) It's definitely a better solution in my opinion! :) > Had to change a few paths and kept getting a no module error when I added > MTA = None -- easy configuration compared to the other method I was > attempting. I kept getting that and in the end replaced it with: MTA = '' Take care, Ben From msapiro at value.net Sun Jun 10 19:01:52 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 10 Jun 2007 10:01:52 -0700 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix2.5 Virtual Mailboxes In-Reply-To: <466C05DE.2000109@py-soft.co.uk> Message-ID: Benjamin Donnachie wrote: > >I kept getting that and in the end replaced it with: > >MTA = '' That will work and so will MTA = 0 MTA = False MTA = [] MTA = {} MTA = x where x is one of No, no, Off or off because these are all defined as False in Defaults.py. These all work because they are either False or 0 or things that have length 0 which all evaluate as False in Python if statements. Defaults.py says: MTA should name a module in Mailman/MTA which provides the MTA specific functionality for creating and removing lists. Some MTAs like Exim can be configured to automatically recognize new lists, in which case the MTA variable should be set to None. This means MTA = None (which also evaluates as False) and not MTA = 'None' which will cause Mailman to look for the module Mailman/MTA/None.py which doesn't exist. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From benjamin at py-soft.co.uk Sun Jun 10 19:42:38 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Sun, 10 Jun 2007 18:42:38 +0100 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <46682EB0.8010509@py-soft.co.uk> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> <466801BA.7040709@py-soft.co.uk> <46682EB0.8010509@py-soft.co.uk> Message-ID: <466C380E.1060001@py-soft.co.uk> Benjamin Donnachie wrote: > I've just written a very simple script which I use as a cronjob to keep > a postfix access map of current lists up-to-date. Thus avoiding > potential backscatter with the listhost domain. A copy of the script is below. You'll probably need to edit it for your site. I pipe the output to /etc/postfix/mm-handler_access. With smtpd_recipient_restrictions including "check_recipient_access regexp:/etc/postfix/mm-handler_access", in postfix's main.cf. Remembering to run postmap /etc/postfix/mm-handler_access after. The access map that it generates ensures that postfix only accepts messages for valid mailman lists and thus prevents your system from becoming a potential source of backscatter spam when using mm-handler. Take care, Ben #!/bin/bash # Generate postfix access maps for valid mailman addresses # By Benjamin Donnachie cat << EOF # # Generated `/bin/date` # # # Lists to accept: # EOF for domain in listhost.example.com listhost.example.org; do echo "# ** Domain $domain" for list in $( /usr/lib/mailman/bin/list_lists -V $domain -b ); do cat << EOF # # * List $list # /$list@$domain/ DUNNO /$list-admin@$domain/ DUNNO /$list-bounces@$domain/ DUNNO /$list-bounces\+.*=.*\..@$domain/ DUNNO /$list-confirm@$domain/ DUNNO /$list-join@$domain/ DUNNO /$list-leave@$domain/ DUNNO /$list-owner@$domain/ DUNNO /$list-request@$domain/ DUNNO /$list-subscribe@$domain/ DUNNO /$list-unsubscribe@$domain/ DUNNO /owner-$list@$domain/ DUNNO EOF done cat << EOF # # * Administrative aliases for domain $domain # /MAILER-DAEMON@$domain/ DUNNO /postmaster@$domain/ DUNNO /webmaster@$domain/ DUNNO /abuse@$domain/ DUNNO /mailman-loop@$domain/ DUNNO # # * If not listed above, reject # /$domain/ REJECT Unknown list - see http://$domain/ # # EOF done From srb at umich.edu Mon Jun 11 00:15:13 2007 From: srb at umich.edu (Steve Burling) Date: Sun, 10 Jun 2007 18:15:13 -0400 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix2.5 Virtual Mailboxes In-Reply-To: References: Message-ID: <6EF2A8A7E65A2D25E0511EE5@srb.local> --On June 10, 2007 10:01:52 AM -0700 Mark Sapiro wrote: > Defaults.py says: > > MTA should name a module in Mailman/MTA which provides the MTA > specific functionality for creating and removing lists. Some MTAs > like Exim can be configured to automatically recognize new lists, > in which case the MTA variable should be set to None. To which I reply: Given the number of times that this comes up as a point of confusion, maybe that comment should read: ...in which case the MTA variable should be set to None (not 'None'). -- Steve Burling University of Michigan, ICPSR Voice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 From msapiro at value.net Mon Jun 11 01:55:31 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 10 Jun 2007 16:55:31 -0700 Subject: [Mailman-Users] Default Languages In-Reply-To: Message-ID: Mark Sapiro wrote: > >To address the confirmation page, you could apply the following patch >to Mailman/Cgi/confirm.py > >--- Mailman/Cgi/confirm.py 2007-05-07 15:34:26.593750000 -0700 >+++ Mailman/Cgi/confirmx.py 2007-06-08 08:47:46.000000000 -0700 >@@ -66,8 +66,12 @@ > return > > # Set the language for the list >- i18n.set_language(mlist.preferred_language) >- doc.set_language(mlist.preferred_language) >+ try: >+ p_l = mlist.default_user_language >+ except NameError: >+ p_l = mlist.preferred_language >+ i18n.set_language(p_l) >+ doc.set_language(p_l) Sorry, brain cramp. The above patch won't quite do. It needs to be --- Mailman/Cgi/confirm.py 2007-05-07 15:34:26.593750000 -0700 +++ Mailman/Cgi/confirmx.py 2007-06-08 08:47:46.000000000 -0700 @@ -66,8 +66,12 @@ return # Set the language for the list - i18n.set_language(mlist.preferred_language) - doc.set_language(mlist.preferred_language) + try: + p_l = mlist.default_user_language + except AttributeError: + p_l = mlist.preferred_language + i18n.set_language(p_l) + doc.set_language(p_l) I.e., the exception if the list doesn't have a default_user_language attribute is AttributeError, not NameError. Sorry for any confusion. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Mon Jun 11 02:09:10 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 10 Jun 2007 17:09:10 -0700 Subject: [Mailman-Users] Default Languages In-Reply-To: Message-ID: Mark Sapiro wrote: > >Sorry, brain cramp. The above patch won't quite do. It needs to be > >--- Mailman/Cgi/confirm.py 2007-05-07 15:34:26.593750000 -0700 >+++ Mailman/Cgi/confirmx.py 2007-06-08 08:47:46.000000000 -0700 >@@ -66,8 +66,12 @@ > return > > # Set the language for the list >- i18n.set_language(mlist.preferred_language) >- doc.set_language(mlist.preferred_language) >+ try: >+ p_l = mlist.default_user_language >+ except AttributeError: >+ p_l = mlist.preferred_language >+ i18n.set_language(p_l) >+ doc.set_language(p_l) > >I.e., the exception if the list doesn't have a default_user_language >attribute is AttributeError, not NameError. Wow! I seem to be having a real problem getting this right. The above patch has the correct modification in it, but I managed to not include the trailing context. The original had this problem too. Here is the complete, correct (I hope) patch. --- confirm.py 2007-05-07 15:34:26.593750000 -0700 +++ confirmx.py 2007-06-10 17:02:50.687500000 -0700 @@ -66,8 +66,12 @@ return # Set the language for the list - i18n.set_language(mlist.preferred_language) - doc.set_language(mlist.preferred_language) + try: + p_l = mlist.default_user_language + except AttributeError: + p_l = mlist.preferred_language + i18n.set_language(p_l) + doc.set_language(p_l) # Get the form data to see if this is a second-step confirmation cgidata = cgi.FieldStorage(keep_blank_values=1) -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From benjamin at py-soft.co.uk Mon Jun 11 06:27:55 2007 From: benjamin at py-soft.co.uk (Benjamin Donnachie) Date: Mon, 11 Jun 2007 05:27:55 +0100 Subject: [Mailman-Users] Bounced messages with Mailman 2.1 and Postfix 2.5 Virtual Mailboxes In-Reply-To: <466C380E.1060001@py-soft.co.uk> References: <93f118f0706051607k54a94786te933f808aa0868eb@mail.gmail.com> <466801BA.7040709@py-soft.co.uk> <46682EB0.8010509@py-soft.co.uk> <466C380E.1060001@py-soft.co.uk> Message-ID: <466CCF4B.30505@py-soft.co.uk> Benjamin Donnachie wrote: > /$list-bounces\+.*=.*\..@$domain/ DUNNO Ooops! That should be: /$list-bounces\+.*=.*\..*@$domain/ DUNNO Ben From picon at webmail.co.za Mon Jun 11 13:32:12 2007 From: picon at webmail.co.za (picon at webmail.co.za) Date: Mon, 11 Jun 2007 13:32:12 +0200 (SAST) Subject: [Mailman-Users] (no subject) Message-ID: <35031.196.23.43.3.1181561532.squirrel@mail.webmail.co.za> Hi there I have been trying to sort out this isue for a while now and I'm not getting anywhere. Every morning I get the following yet, there are no such mails waiting. I am running mandriva 2007.0, mailman-2.1.9-1mdv2007.0 Does anyone know where to disable these? Thanks -----Original Message----- From: mailman-bounces at jhb.ucs.co.za [mailto:mailman-bounces at jhb.ucs.co.za] On Behalf Of support.specialty-bounces at jhb.ucs.co.za Sent: 22 May 2007 08:00 AM To: support.specialty-owner at jhb.ucs.co.za Subject: 3 Support.specialty moderator request(s) waiting The Support.specialty at jhb.ucs.co.za mailing list has 3 request(s) waiting for your consideration at: http://jhb.ucs.co.za/mailman/admindb/support.specialty Please attend to this at your earliest convenience. This notice of pending requests, if any, will be sent out daily. Pending posts: From: lakesvouchers at telkomsa.net on Tue Apr 10 10:08:43 2007 Subject: Date: 10/04/2007 10:05:25 Exception: LAKE CELLULAR (SiteID:5127) (Version: 2.2.12.132) Cause: Message has implicit destination From: vodacomballito at telkomsa.net on Tue Apr 10 13:07:17 2007 Subject: Date: 2007/04/10 01:06:37 PM Exception: LIFESTYLE CELLULAR (SiteID:4994) (Version: 2.2.12.133) Cause: Message has implicit destination From: active at sello.co.za on Tue Apr 10 13:59:29 2007 Subject: Date: 10/04/2007 01:58:53 PM Exception: SELLO ACTIVE CELLULAR (SiteID:5045) (Version: 2.2.12.132) Cause: Message has implicit destination ------------------------------------------- South Africas premier free email service - www.webmail.co.za ------------------------------------------------------------------ For super low premiums, click here http://www.webmail.co.za/dd.pwm From msapiro at value.net Mon Jun 11 16:53:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 11 Jun 2007 07:53:12 -0700 Subject: [Mailman-Users] Mysterious moderator requests - was: (no subject) In-Reply-To: <35031.196.23.43.3.1181561532.squirrel@mail.webmail.co.za> Message-ID: picon at webmail.co.za wrote: > >Every morning I get the following yet, there are no such mails waiting. >I am running mandriva 2007.0, mailman-2.1.9-1mdv2007.0 > >Does anyone know where to disable these? >The Support.specialty at jhb.ucs.co.za mailing list has 3 request(s) >waiting for your consideration at: > > http://jhb.ucs.co.za/mailman/admindb/support.specialty The usual cause of this is you have residue of an old or test installation that has these pending requests. In addition, there is some misconfiguration in that installation since as far as I can tell, there is no DNS A or CNAME record for jhb.ucs.co.za, only an MX and a TXT record so the jhb.ucs.co.za domain is only valid for email, not for web access. To what URL are you going to check for these requests? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carbonnb at gmail.com Mon Jun 11 20:34:24 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Mon, 11 Jun 2007 14:34:24 -0400 Subject: [Mailman-Users] Default Languages In-Reply-To: References: Message-ID: On 6/10/07, Mark Sapiro wrote: > Mark Sapiro wrote: > > > >Sorry, brain cramp. The above patch won't quite do. It needs to be Thanks for all this Mark. Even after all this, I didn't test it. It seems that I can't touch the MM source code with this installation :( So I will have to work out a different way. -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From michael at livingroutes.org Wed Jun 13 16:11:37 2007 From: michael at livingroutes.org (michael at livingroutes.org) Date: Wed, 13 Jun 2007 16:11:37 +0200 (CEST) Subject: [Mailman-Users] changing email address on multiple lists Message-ID: <49347.151.203.151.115.1181743897.squirrel@mail.livingroutes.org> I work for an organization that maintains about 80 different private lists. Awhile back, we had our admissions director manually apply to all 80 lists which took her about 2 hours and she has since left the organization. Is there any way to change her email address on all the lists simultaneously? What's the best way of getting another user onto all the lists? From msapiro at value.net Wed Jun 13 16:59:28 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 13 Jun 2007 07:59:28 -0700 Subject: [Mailman-Users] changing email address on multiple lists In-Reply-To: <49347.151.203.151.115.1181743897.squirrel@mail.livingroutes.org> Message-ID: michael at livingroutes.org wrote: >I work for an organization that maintains about 80 different private >lists. Awhile back, we had our admissions director manually apply to all >80 lists which took her about 2 hours and she has since left the >organization. Is there any way to change her email address on all the >lists simultaneously? What's the best way of getting another user onto all >the lists? There are several ways to do this. If you know her password to any list, or the site admin password, log on to her user options page for the list. From there, you can change name and address globally (but not if you authorized with the list admin password - only the user's or site admin password works for a global change). If you have command line access to the Mailman installation, you can use bin/remove_members to remove her from all the lists with one command an then use bin/add_members in a shell script to add a new member to all lists. E.g. (for illustration only, may contain typos, you may want more options on the add_members command) #! /bin/bash file=`mktemp` echo Real Name \ > $file for list in `bin/list_lists -b` do bin/add_members -r $file $list done rm $file You might also use the withlist script at (mirrored at ) to change the address on all lists, but as it is, it won't change the name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From dbarraclough at nationtalk.ca Wed Jun 13 17:17:17 2007 From: dbarraclough at nationtalk.ca (Don Barraclough) Date: Wed, 13 Jun 2007 11:17:17 -0400 Subject: [Mailman-Users] Looking for contractor for Mailman maintenance/support Message-ID: <001401c7adcd$ee330350$ca9909f0$@ca> We are a for profit company that is looking for assistance with our mailing list strategy and software. Although we are not a large company we are not looking for anything for free. Situation: Our current host provides the Mailman software and we have been using it for almost one year. Lately we find that some of the emails are going out while others are not. We have placed seeds in the database to confirm this result. At first we thought it was a host issue but now we are fairly certain it is a software maintenance thing. Our larger list of 3,100 addresses were deleted and then recreated and it worked perfect for a day or two. Our smaller list of 1,000 seems to send unique headings to our seed hotmail account, but not our daily e-newsletter, although we believe most are going out in any event. Another issue we had not too long ago was when we would approve the send the emails were sent 6 to 8 hours later. Any assistance would be welcome. I can be reached day or night at the below telephone number. Thanks in advance for your attention. 1-866-651-8516 Toronto, Canada EDT From pdbogen at gmail.com Wed Jun 13 17:50:31 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Wed, 13 Jun 2007 10:50:31 -0500 Subject: [Mailman-Users] Looking for contractor for Mailman maintenance/support In-Reply-To: <001401c7adcd$ee330350$ca9909f0$@ca> References: <001401c7adcd$ee330350$ca9909f0$@ca> Message-ID: <6fbe3da00706130850t231f1237u380c06cb8bed7a48@mail.gmail.com> On 6/13/07, Don Barraclough wrote: > At first we thought it was a host issue but now we are fairly certain it is > a software maintenance thing. Our larger list of 3,100 addresses were > deleted and then recreated and it worked perfect for a day or two. > > Another issue we had not too long ago was when we would approve the send the > emails were sent 6 to 8 hours later. This sounds like a rate-limiting situation. You might check with your Mailman host to see if they limit in any way the number of messages that can be sent per minute, hour, day, etc. -- - Patrick Bogen From roberto at leibman.net Wed Jun 13 18:44:51 2007 From: roberto at leibman.net (Roberto Leibman) Date: Wed, 13 Jun 2007 09:44:51 -0700 Subject: [Mailman-Users] Problems with virtual domains on postfix... Message-ID: <46701F03.6040006@leibman.net> Help! I can't get my list to work. For some reason postfix keeps redirecting email sent to the list to the non-list domain. Thanks for you help... Roberto ---------------------------- Details: The List: lug-nuts at saclug.org The "Real" Domain: leibmanland.com The message from a bounced back message sent to lug-nuts at saclug.org: : data format error. Command output: lug-nuts: Mailbox does not exist The postfix message (from mail.log) 6ADC07040E6: to=, orig_to=, relay=spamassassin, delay=2.4, delays=0.12/0.01/0/2.3, dsn=2.0.0, status=sent (delivered via spamassassin service) --------------------------- The configuration: Environment: Ubuntu feisty running on an AMD64. Postfix version: 2.3.8. Mailman (2.1.9... I think) Excerpts from /etc/postfix/main.cf alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases mydestination = localhost, localhost.localdomain, localhost, mail, mail.leibmanland.com, [69.62.235.30] virtual_alias_maps = hash:/etc/postfix/virtual, hash:/var/lib/mailman/data/virtual-mailman virtual_mailbox_domains=leibmanland.com list.saclug.org placerliberty.org freezlets.com leibman.net mail.leibman.net byrongalvez.com mail.freezlets.com mail.byrongalvez.com lpsacramento.com mail.lpsacramento.com lpsacramento.org mail.lpsacramento.org saclug.org owner_request_special=no allow_mail_to_commands = alias mailman_destination_recipient_limit = 1 Excerpts from /etc/postfix/master.cf mailman unix - n n - - pipe flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py Excerpts from /etc/mailman/mm_cfg.py DEFAULT_EMAIL_HOST = 'leibmanland.com' DEFAULT_URL_HOST = 'www.leibmanland.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, 'saclug.org') MTA='Postfix' POSTFIX_STYLE_VIRTUAL_DOMAINS=['placerliberty.org', 'saclug.org'] Excerpts from /var/lib/mailman/data/virtual-mailman # STANZA START: lug-nuts # CREATED: Tue Jun 12 17:04:53 2007 lug-nuts at saclug.org lug-nuts lug-nuts-admin at saclug.org lug-nuts-admin lug-nuts-bounces at saclug.org lug-nuts-bounces lug-nuts-confirm at saclug.org lug-nuts-confirm lug-nuts-join at saclug.org lug-nuts-join lug-nuts-leave at saclug.org lug-nuts-leave lug-nuts-owner at saclug.org lug-nuts-owner lug-nuts-request at saclug.org lug-nuts-request lug-nuts-subscribe at saclug.org lug-nuts-subscribe lug-nuts-unsubscribe at saclug.org lug-nuts-unsubscribe # STANZA END: lug-nuts Excerpts from /var/lib/mailman/data/aliases # STANZA START: lug-nuts # CREATED: Tue Jun 12 17:04:53 2007 lug-nuts: "|/var/lib/mailman/mail/mailman post lug-nuts" lug-nuts-admin: "|/var/lib/mailman/mail/mailman admin lug-nuts" lug-nuts-bounces: "|/var/lib/mailman/mail/mailman bounces lug-nuts" lug-nuts-confirm: "|/var/lib/mailman/mail/mailman confirm lug-nuts" lug-nuts-join: "|/var/lib/mailman/mail/mailman join lug-nuts" lug-nuts-leave: "|/var/lib/mailman/mail/mailman leave lug-nuts" lug-nuts-owner: "|/var/lib/mailman/mail/mailman owner lug-nuts" lug-nuts-request: "|/var/lib/mailman/mail/mailman request lug-nuts" lug-nuts-subscribe: "|/var/lib/mailman/mail/mailman subscribe lug-nuts" lug-nuts-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe lug-nuts" # STANZA END: lug-nuts From sfeng at stanford.edu Wed Jun 13 20:38:55 2007 From: sfeng at stanford.edu (Xueshan Feng) Date: Wed, 13 Jun 2007 11:38:55 -0700 Subject: [Mailman-Users] sendgiest cron job failure In-Reply-To: <46701F03.6040006@leibman.net> References: <46701F03.6040006@leibman.net> Message-ID: <1181759935.23589.109.camel@hoss.stanford.edu> We have 18K mailing lists. The "senddigest" cron job runs at noon daily. It came to our attention that many lists don't get digests. I put some debugging code in "senddigest", and I found out that there were two lists's digests had TypeError while being processed and 'senddigest" job just bailed out on the exception. No further lists will be processed for digest. Since this happens only to two lists out of 18K lists, I suspect this might not be a general system configuration error, but I wanted to confirm that. The work-around I have now is to have exception handling in "senddigest" code which skips the bad digest and log the error in mailman's error log. Both the patch and the digest error messages are included below. Anyone knows if the problem is fixable? Thanks, Xueshan --- senddigests 2007-06-13 10:48:54.000000000 -0700 +++ senddigests.orig 2007-06-12 10:53:08.000000000 -0700 @@ -38,7 +38,6 @@ from Mailman import Utils from Mailman import MailList from Mailman.i18n import _ -from Mailman.Logging.Syslog import syslog # Work around known problems with some RedHat cron daemons import signal @@ -83,12 +82,9 @@ mlist = MailList.MailList(listname, lock=0) if mlist.digest_send_periodic: mlist.Lock() - try: - try: - mlist.send_digest_now() - mlist.Save() - except (ValueError, TypeError), e: - syslog ('error', 'Broken digest: %s: %s', listname, e) + try: + mlist.send_digest_now() + mlist.Save() finally: mlist.Unlock() The digest error messages are two types: 1. Traceback (most recent call last): File "./senddigests", line 95, in ? main() File "./senddigests", line 87, in main mlist.send_digest_now() File "/var/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digest s send_i18n_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_d igests msg = scrubber(mlist, msg) File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 372, in process t = unicode(t, partcharset, 'replace') TypeError: coercing to Unicode: need string or buffer, NoneType found 2.Traceback (most recent call last): File "./senddigests", line 95, in ? main() File "./senddigests", line 87, in main mlist.send_digest_now() File "/var/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests msg = scrubber(mlist, msg) File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 306, in process url = save_attachment(mlist, part, dir) File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 483, in save_attachment if os.path.exists(path): File "/usr/lib/python2.3/posixpath.py", line 174, in exists st = os.stat(path) TypeError: stat() argument 1 must be (encoded string without NULL bytes), not str From joasia at redakcja.esensja.pl Wed Jun 13 20:47:53 2007 From: joasia at redakcja.esensja.pl (Jo'Asia) Date: Wed, 13 Jun 2007 20:47:53 +0200 Subject: [Mailman-Users] List archive and config problem Message-ID: <234616913.20070613204753@redakcja.esensja.pl> OK, the stroy is long, but there may be a lot of reasons for the problems, so here it goes. Last week the server running mailman had been upgraded (meaning a completly new machine with all the data migrated from the old one). At this time also mailman has been upgraded from 2.1.5 to 2.1.9 Some minor problems appeared, like rights to archives, but they have been fixed. Unfortunately, one of the lists set for public archive is creating a private archive. The WWW admin interface still showed the archive option set to 'public'. I tried to switch it to private and back to public and saw this error message: 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 checked the log - there is *some* info, nothing helpful to me, but, if necessary, I can quote it... Now even an attemt to log into the admin interface of this list generates this error message. :( I run check_db - it says the config.pck file is OK. List as such is running OK - mails are recieved, delivered and archived (still in *private* archive directory), only the admin interface is broken. Where else should I look for the cause? If everything else fails it's possible to create a new list and import as much information from "strings dump" of the pickle file but I'd rather revive the current one. And fix this damn archiving... Jo'Asia -- Joanna Slupek --- --- --- .-- --- " --- http://esensja.pl |--- '-- |--- | | '-- | --| joasia at redakcja.esensja.pl --- ---' --- | | ---' | '--. -------------------------------------------------------------------' ---- From msapiro at value.net Thu Jun 14 03:41:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 13 Jun 2007 18:41:12 -0700 Subject: [Mailman-Users] sendgiest cron job failure In-Reply-To: <1181759935.23589.109.camel@hoss.stanford.edu> Message-ID: Xueshan Feng wrote: > >Since this happens only to two lists out of 18K lists, I suspect this >might not be a general system configuration error, but I wanted to >confirm that. The problem is some mal-formed message in lists//digest.mbox >The work-around I have now is to have exception handling in "senddigest" >code which skips the bad digest and log the error in mailman's error >log. > >Both the patch and the digest error messages are included below. > >Anyone knows if the problem is fixable? > >Thanks, > >Xueshan > >--- senddigests 2007-06-13 10:48:54.000000000 -0700 >+++ senddigests.orig 2007-06-12 10:53:08.000000000 -0700 >@@ -38,7 +38,6 @@ > from Mailman import Utils > from Mailman import MailList > from Mailman.i18n import _ >-from Mailman.Logging.Syslog import syslog > > # Work around known problems with some RedHat cron daemons > import signal >@@ -83,12 +82,9 @@ > mlist = MailList.MailList(listname, lock=0) > if mlist.digest_send_periodic: > mlist.Lock() >- try: >- try: >- mlist.send_digest_now() >- mlist.Save() >- except (ValueError, TypeError), e: I don't know if this is your patch or an emailing artifact, but the above except and the preceding try should be indented the same amount. >- syslog ('error', 'Broken digest: %s: %s', listname, >e) >+ try: >+ mlist.send_digest_now() >+ mlist.Save() > finally: > mlist.Unlock() The patch looks good. I may put something similar in cron/senddigests for the next release. > >The digest error messages are two types: > > >1. Traceback (most recent call last): > File "./senddigests", line 95, in ? > main() > File "./senddigests", line 87, in main > mlist.send_digest_now() > File "/var/lib/mailman/Mailman/Digester.py", line 60, in >send_digest_now > ToDigest.send_digests(self, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in >send_digest >s > send_i18n_digests(mlist, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in >send_i18n_d >igests > msg = scrubber(mlist, msg) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 372, in >process > t = unicode(t, partcharset, 'replace') >TypeError: coercing to Unicode: need string or buffer, NoneType found Possibly a message with an empty sub-part. This is something we should check in Scrubber. Try the following patch to Mailman/Handlers/Scrubber.py --- Scrubber.py (revision 8236) +++ Scrubber.py (working copy) @@ -373,7 +373,7 @@ partcharset = str(partcharset) else: partcharset = part.get_content_charset() - if partcharset and partcharset <> charset: + if t and partcharset and partcharset <> charset: try: t = unicode(t, partcharset, 'replace') except (UnicodeError, LookupError, ValueError, AssertionError): (The last line above is wrapped - the 'except' should be all one line). >2.Traceback (most recent call last): > File "./senddigests", line 95, in ? > main() > File "./senddigests", line 87, in main > mlist.send_digest_now() > File "/var/lib/mailman/Mailman/Digester.py", line 60, in >send_digest_now > ToDigest.send_digests(self, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in >send_digests > send_i18n_digests(mlist, mboxfp) > File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in >send_i18n_digests > msg = scrubber(mlist, msg) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 306, in >process > url = save_attachment(mlist, part, dir) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 483, in >save_attachment > if os.path.exists(path): > File "/usr/lib/python2.3/posixpath.py", line 174, in exists > st = os.stat(path) >TypeError: stat() argument 1 must be (encoded string without NULL >bytes), not str This too looks like a possible Scrubber bug. There is something wierd abour the filename= parameter of an attachment, but it looks to me like the code is pretty well protected. I'd like to see the message (or .mbox) that causes this one and maybe the first one too. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 14 04:16:55 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 13 Jun 2007 19:16:55 -0700 Subject: [Mailman-Users] List archive and config problem In-Reply-To: <234616913.20070613204753@redakcja.esensja.pl> Message-ID: Jo'Asia wrote: > >I checked the log - there is *some* info, nothing helpful to me, but, >if necessary, I can quote it... That's what it's for. Please send the tracebacks from Mailman's error log. >Now even an attemt to log into the admin interface of this list >generates this error message. :( > >I run check_db - it says the config.pck file is OK. It only checks that it can be read as a pickle. It doesn't check the integrity of the data. >List as such is running OK - mails are recieved, delivered and >archived (still in *private* archive directory), only the admin >interface is broken. All lists are archived in the private directory. The public directory only contains symlinks to the private archives. The good news is if the list works, the config.pck is OK. >Where else should I look for the cause? Tell us what the error messages say. >If everything else fails it's possible to create a new list and >import as much information from "strings dump" of the pickle file but >I'd rather revive the current one. And fix this damn archiving... It's very tedious, and in this case, I don't think it's necessary. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 14 05:23:34 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 13 Jun 2007 20:23:34 -0700 Subject: [Mailman-Users] Problems with virtual domains on postfix... In-Reply-To: <46701F03.6040006@leibman.net> Message-ID: Roberto Leibman wrote: >Help! I can't get my list to work. For some reason postfix keeps >redirecting email sent to the list to the non-list domain. I've looked over the information you includes, and I don't see anything obviously wrong, but I know almost nothing about Postfix. Perhaps someone else on this list can help, but the Mailman stuff that relates to Postfix looks OK. This is really a Postfix question, and I suggest you may get better help from Postfix support resources. There is one problem in you Mailman config that I tont't think affects the problem you're having, but will affect other things. In mm_cfg.py, you have add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, 'saclug.org') The second of these effectively nullifies the first. All 'url hosts' in add_virtualhost() directives must be unique because the 'url host' is a key in a python dictionary mapping and the 'email host' is the value of that key. So, in the above, the first add_virtualhost() just sets the value of the 'www.leibmanland.com' key to 'leibmanland.com' and the second replaces that value with 'saclug.org'. See for some consequences of this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From l.h. at raqtweak.com Thu Jun 14 07:25:27 2007 From: l.h. at raqtweak.com (L. H.) Date: Thu, 14 Jun 2007 07:25:27 +0200 Subject: [Mailman-Users] Member only list? Message-ID: <20070614052450.M67952@raqtweak.com> Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non- member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks! From l.h. at raqtweak.com Wed Jun 13 20:24:31 2007 From: l.h. at raqtweak.com (L. H.) Date: Wed, 13 Jun 2007 20:24:31 +0200 Subject: [Mailman-Users] Member only list? Message-ID: <92443234F7504DB0BEDE04AA7735052C@WORKSTATION> Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non-member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks! From l.h. at raqtweak.com Wed Jun 13 00:37:12 2007 From: l.h. at raqtweak.com (L. H.) Date: Wed, 13 Jun 2007 00:37:12 +0200 Subject: [Mailman-Users] Member only list? Message-ID: Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non-member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks! From l.h. at raqtweak.com Thu Jun 14 21:14:17 2007 From: l.h. at raqtweak.com (L. H.) Date: Thu, 14 Jun 2007 21:14:17 +0200 Subject: [Mailman-Users] Member only list? Message-ID: <47FC6DB11BE94F49918B6DE198051905@WORKSTATION> Hi, I am currently running 2.1.9, and am trying to setup a member only list function using config_list. I've found a few instructions, but they seem to be for older versions of which the commands are no longer recognized. What I want to do is have 3 setups: 1) Everyone, members or no members, can post 2) Only members can post, no moderation required for them. Drop all non-member submissions. 3) All emails sent to the list (member + non member) must be approved by the admin. Which configuration lines should I use for this? I currently use: 1) Everyone: generic_nonmember_action = 0 default_member_moderation = 0 2) Members only: default_member_moderation = 0 generic_nonmember_action = 2 3) Moderation for everyone: default_member_moderation = 1 member_moderation_action = 0 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 Please advise. Thanks! From wonko at 4amlunch.net Thu Jun 14 20:53:41 2007 From: wonko at 4amlunch.net (Brian Hechinger) Date: Thu, 14 Jun 2007 13:53:41 -0500 Subject: [Mailman-Users] Server Migration (and archive repair) Message-ID: <20070614185341.GT21321@lisa.4amlunch.net> I need to build a new mailman server. What is the best/easiest way to migrate lists (and their archives) to the new machine? Something that used rsync would be nice so I could keep things as up to date as possible and then do a final rsync right before the migration. This is definitely something that needs to be done slowly and kept up with, our archives are currently 26GB in size. ;) The other thing is, a previous admin tried to clear out the archives for a couple of lists, and now the new messages are no longer archived. How do I repair these broken archives? Thanks, -brian -- "Perl can be fast and elegant as much as J2EE can be fast and elegant. In the hands of a skilled artisan, it can and does happen; it's just that most of the shit out there is built by people who'd be better suited to making sure that my burger is cooked thoroughly." -- Jonathan Patschke From prieheck at iwu.edu Thu Jun 14 22:37:16 2007 From: prieheck at iwu.edu (Pat Riehecky) Date: Thu, 14 Jun 2007 15:37:16 -0500 Subject: [Mailman-Users] mailman clustering? Message-ID: <1181853436.6468.50.camel@thales.iwu.edu> I am trying to build a nice failover system for random parts of our infrastructure. Does anyone know how to force mailman to replicate changes over to another identically configured system? I thought about using rsync for this but I am trying to keep the sync triggered by updates on the primary server rather than just seeing if in the last few minutes any files have changed. Ideally I would like to round robin the primary and the secondary to split the load up, but I cannot do that without being sure that they are kept in sync with each other. How close to possible is this idea? Is there something I should read? I checked the FAQ and didn't see anything... Pat From msapiro at value.net Fri Jun 15 00:59:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 14 Jun 2007 15:59:24 -0700 Subject: [Mailman-Users] Member only list? In-Reply-To: <47FC6DB11BE94F49918B6DE198051905@WORKSTATION> Message-ID: L. H. wrote: > >I am currently running 2.1.9, and am trying to setup a member only list >function using config_list. > >I've found a few instructions, but they seem to be for older versions of >which the commands are no longer recognized. > >What I want to do is have 3 setups: > >1) Everyone, members or no members, can post >2) Only members can post, no moderation required for them. Drop all >non-member submissions. >3) All emails sent to the list (member + non member) must be approved by the >admin. > >Which configuration lines should I use for this? >I currently use: > >1) Everyone: >generic_nonmember_action = 0 >default_member_moderation = 0 > >2) Members only: >default_member_moderation = 0 >generic_nonmember_action = 2 > >3) Moderation for everyone: > >default_member_moderation = 1 >member_moderation_action = 0 >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' >generic_nonmember_action = 1 The above looks OK to me for what you want. What specifically is your problem? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From l.h. at raqtweak.com Fri Jun 15 01:08:43 2007 From: l.h. at raqtweak.com (L. H.) Date: Fri, 15 Jun 2007 01:08:43 +0200 Subject: [Mailman-Users] Member only list? In-Reply-To: References: <47FC6DB11BE94F49918B6DE198051905@WORKSTATION> Message-ID: > >1) Everyone: > >generic_nonmember_action = 0 > >default_member_moderation = 0 > > > >2) Members only: > >default_member_moderation = 0 > >generic_nonmember_action = 2 > > > >3) Moderation for everyone: > > > >default_member_moderation = 1 > >member_moderation_action = 0 > >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' > >generic_nonmember_action = 1 > > > The above looks OK to me for what you want. What specifically is your > problem? I thought it would be OK, but, if I set it to any, or members only, it STILL sends the list admin "approve this post" messages... and puts them on hold until he does approve... From msapiro at value.net Fri Jun 15 02:03:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 14 Jun 2007 17:03:29 -0700 Subject: [Mailman-Users] Server Migration (and archive repair) In-Reply-To: <20070614185341.GT21321@lisa.4amlunch.net> Message-ID: Brian Hechinger wrote: >I need to build a new mailman server. What is the best/easiest way to >migrate lists (and their archives) to the new machine? Something that >used rsync would be nice so I could keep things as up to date as possible >and then do a final rsync right before the migration. The directories you need to rsync are Mailman's lists/ and archives/private/ directories. If you're concerned about held messages, you can also do the data/ directory, but it may be better to approve/reject/discard any held messages during the final switchover after stopping the MTA and before the final rsync. When you're ready to do the final switchover, shut down the incoming MTA on the old box, wait for Mailman to process all its queues, do the rsync and finally change DNS or whatever to have the new box take over. >The other thing is, a previous admin tried to clear out the archives for >a couple of lists, and now the new messages are no longer archived. How >do I repair these broken archives? First, is the list's Archiving Options->archive set to Yes? Are some lists being archived? If so, good, but if not, is ArchRunner running (ps -fAw | grep qrunner)? What's in Mailman's error log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 15 02:07:33 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 14 Jun 2007 17:07:33 -0700 Subject: [Mailman-Users] Member only list? In-Reply-To: Message-ID: L. H. wrote: >> >1) Everyone: >> >generic_nonmember_action = 0 >> >default_member_moderation = 0 >> > >> >2) Members only: >> >default_member_moderation = 0 >> >generic_nonmember_action = 2 >> > >> >3) Moderation for everyone: >> > >> >default_member_moderation = 1 >> >member_moderation_action = 0 >> >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' >> >generic_nonmember_action = 1 >> >> >> The above looks OK to me for what you want. What specifically is your >> problem? > >I thought it would be OK, but, if I set it to any, or members only, it STILL >sends the list admin "approve this post" messages... and puts them on hold >until he does approve... Are you talking about Case 1 or Case 2 or both? What is the reason why the post is held? You will find the reason in the admindb interface, in the notice to the admin and in Mailman's vette log. -- 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 Jun 15 08:15:10 2007 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 15 Jun 2007 01:15:10 -0500 Subject: [Mailman-Users] mailman clustering? In-Reply-To: <1181853436.6468.50.camel@thales.iwu.edu> References: <1181853436.6468.50.camel@thales.iwu.edu> Message-ID: On 6/14/07, Pat Riehecky wrote: > How close to possible is this idea? Is there something I should read? > I checked the FAQ and didn't see anything... You probably did the intelligent thing and searched for the word "cluster" and didn't find it. That's because FAQ 4.75 didn't have that keyword in the title or in the body. I've now fixed that. Anyway, FAQ 4.75 provides about as much information as I know of that exists on this topic. If you find out anything else, please let us know. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From wonko at 4amlunch.net Fri Jun 15 15:13:28 2007 From: wonko at 4amlunch.net (Brian Hechinger) Date: Fri, 15 Jun 2007 08:13:28 -0500 Subject: [Mailman-Users] Server Migration (and archive repair) In-Reply-To: References: <20070614185341.GT21321@lisa.4amlunch.net> Message-ID: <20070615131328.GA10234@lisa.4amlunch.net> On Thu, Jun 14, 2007 at 05:03:29PM -0700, Mark Sapiro wrote: > > The directories you need to rsync are Mailman's lists/ and > archives/private/ directories. If you're concerned about held Ok, good, that's easy enough. > messages, you can also do the data/ directory, but it may be better to > approve/reject/discard any held messages during the final switchover > after stopping the MTA and before the final rsync. Most people don't bother cleaning out there held messages. This will be a good chance to get rid of those. :) > When you're ready to do the final switchover, shut down the incoming > MTA on the old box, wait for Mailman to process all its queues, do the > rsync and finally change DNS or whatever to have the new box take over. Yeah, this part is the portion I'm comforable with, just didn't know what exactly should be copied over. > First, is the list's Archiving Options->archive set to Yes? > > Are some lists being archived? If so, good, but if not, is ArchRunner > running (ps -fAw | grep qrunner)? Archives work for all lists. Archives worked fine up until the previous mailing list admin (actually a desktop fellow who was new to linux, yay) did his "magic". > What's in Mailman's error log? Ah ha! He made the mbox files owned by root, not mailman. ooops! -brian -- "Perl can be fast and elegant as much as J2EE can be fast and elegant. In the hands of a skilled artisan, it can and does happen; it's just that most of the shit out there is built by people who'd be better suited to making sure that my burger is cooked thoroughly." -- Jonathan Patschke From dan at tangledhelix.com Tue Jun 12 20:59:18 2007 From: dan at tangledhelix.com (Dan Lowe) Date: Tue, 12 Jun 2007 14:59:18 -0400 Subject: [Mailman-Users] Assertion error in senddigests Message-ID: <34309B04-9D78-4567-9BE9-0E2E87825E42@tangledhelix.com> I know a bit of Python, but this traceback is way over my head. I'm getting this every day when the senddigests cron job runs: Traceback (most recent call last): File "/usr/local/pkg/mailman/cron/senddigests", line 94, in main() File "/usr/local/pkg/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/usr/local/pkg/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line 324, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/pkg/mailman/Mailman/Handlers/Scrubber.py", line 373, in process t = t.encode(charset, 'replace') File "/usr/local/pkg/python/lib/python2.5/encodings/ quopri_codec.py", line 20, in quopri_encode assert errors == 'strict' AssertionError Searching list archives and Google haven't turned up anything that looks useful. The traceback doesn't even point to which list was being operated on at the time of the error. The only thing I've found in the Mailman logs is this sort of message, in logs/error: Jun 12 16:08:44 2007 (504) send_digests() failed: Jun 12 16:11:40 2007 (504) send_digests() failed: Jun 12 16:18:20 2007 (504) send_digests() failed: Jun 12 16:21:30 2007 (504) send_digests() failed: Jun 12 16:21:40 2007 (504) send_digests() failed: Jun 12 16:23:06 2007 (504) send_digests() failed: Jun 12 16:47:21 2007 (504) send_digests() failed: Jun 12 16:49:58 2007 (504) send_digests() failed: Jun 12 16:58:42 2007 (504) send_digests() failed: Jun 12 17:20:15 2007 (504) send_digests() failed: Also, though most of my lists are set as digestable (but not digesting by default), none of my lists have any digest-enabled subscribers... -dan From msapiro at value.net Fri Jun 15 23:32:55 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 15 Jun 2007 14:32:55 -0700 Subject: [Mailman-Users] sendgiest cron job failure In-Reply-To: Message-ID: Mark Sapiro wrote: >Xueshan Feng wrote: >> >>The digest error messages are two types: >> >> >>1. Traceback (most recent call last): >> File "./senddigests", line 95, in ? >> main() >> File "./senddigests", line 87, in main >> mlist.send_digest_now() >> File "/var/lib/mailman/Mailman/Digester.py", line 60, in >>send_digest_now >> ToDigest.send_digests(self, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in >>send_digest >>s >> send_i18n_digests(mlist, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in >>send_i18n_d >>igests >> msg = scrubber(mlist, msg) >> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 372, in >>process >> t = unicode(t, partcharset, 'replace') >>TypeError: coercing to Unicode: need string or buffer, NoneType found > > >Possibly a message with an empty sub-part. This is something we should >check in Scrubber. Actually, it turns out that this was a delivery status notification returned to the list. The Python email package handles message/delivery-status parts in a speial way which results in part payloads of None. >>2.Traceback (most recent call last): >> File "./senddigests", line 95, in ? >> main() >> File "./senddigests", line 87, in main >> mlist.send_digest_now() >> File "/var/lib/mailman/Mailman/Digester.py", line 60, in >>send_digest_now >> ToDigest.send_digests(self, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in >>send_digests >> send_i18n_digests(mlist, mboxfp) >> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 324, in >>send_i18n_digests >> msg = scrubber(mlist, msg) >> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 306, in >>process >> url = save_attachment(mlist, part, dir) >> File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 483, in >>save_attachment >> if os.path.exists(path): >> File "/usr/lib/python2.3/posixpath.py", line 174, in exists >> st = os.stat(path) >>TypeError: stat() argument 1 must be (encoded string without NULL >>bytes), not str And this was a message with an improprly encoded RFC 2047 filename parameter which had a trailing null byte. Both of these issues are fixed by the attached Scrubber.patch.txt patch to Mailman/Handlers/Scrubber.py. -- 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: Scrubber.patch.txt Url: http://mail.python.org/pipermail/mailman-users/attachments/20070615/feefde5f/attachment.txt From msapiro at value.net Sat Jun 16 00:29:49 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 15 Jun 2007 15:29:49 -0700 Subject: [Mailman-Users] Assertion error in senddigests In-Reply-To: <34309B04-9D78-4567-9BE9-0E2E87825E42@tangledhelix.com> Message-ID: Dan Lowe wrote: >I know a bit of Python, but this traceback is way over my head. I'm >getting this every day when the senddigests cron job runs: > >Traceback (most recent call last): > File "/usr/local/pkg/mailman/cron/senddigests", line 94, in > main() > File "/usr/local/pkg/mailman/cron/senddigests", line 86, in main > mlist.send_digest_now() > File "/usr/local/pkg/mailman/Mailman/Digester.py", line 60, in >send_digest_now > ToDigest.send_digests(self, mboxfp) > File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line >142, in send_digests > send_i18n_digests(mlist, mboxfp) > File "/usr/local/pkg/mailman/Mailman/Handlers/ToDigest.py", line >324, in send_i18n_digests > msg = scrubber(mlist, msg) > File "/usr/local/pkg/mailman/Mailman/Handlers/Scrubber.py", line >373, in process > t = t.encode(charset, 'replace') > File "/usr/local/pkg/python/lib/python2.5/encodings/ >quopri_codec.py", line 20, in quopri_encode > assert errors == 'strict' >AssertionError > >Searching list archives and Google haven't turned up anything that >looks useful. The traceback doesn't even point to which list was >being operated on at the time of the error. The only thing I've found >in the Mailman logs is this sort of message, in logs/error: > >Jun 12 16:08:44 2007 (504) send_digests() failed: >Jun 12 16:11:40 2007 (504) send_digests() failed: >Jun 12 16:18:20 2007 (504) send_digests() failed: >Jun 12 16:21:30 2007 (504) send_digests() failed: >Jun 12 16:21:40 2007 (504) send_digests() failed: >Jun 12 16:23:06 2007 (504) send_digests() failed: >Jun 12 16:47:21 2007 (504) send_digests() failed: >Jun 12 16:49:58 2007 (504) send_digests() failed: >Jun 12 16:58:42 2007 (504) send_digests() failed: >Jun 12 17:20:15 2007 (504) send_digests() failed: > >Also, though most of my lists are set as digestable (but not >digesting by default), none of my lists have any digest-enabled >subscribers... Every post to the list triggers a digest on size and produces the above error log message. You may be able to deduce the list from the timing of the messages. Even if there are no digest members, if the list is digestable, a digest.mbox is maintained and processed. At least one of your lists has a lists//digest.mbox file with a bad message in it. The bad message (I think) has a Content-Type: header with a charset="quoted-printable" parameter. The attached senddigests.patch.txt patch to cron.senddigests will produce stderr output pointing to the offending list and digest.mbox. If you run it from the command line, you will see the output. If cron runs it, you should get the output in email rather than the above traceback. You can catch the AssertionError in scrubber. There is a fixed version of Scrubber.py in SVN at (rev. 8237) which has this and a few other post 2.1.9 fixes. -- 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: senddigests.patch.txt Url: http://mail.python.org/pipermail/mailman-users/attachments/20070615/8cfff515/attachment.txt From letb24 at aol.com Sat Jun 16 19:02:54 2007 From: letb24 at aol.com (letb24 at aol.com) Date: Sat, 16 Jun 2007 13:02:54 -0400 Subject: [Mailman-Users] List Message-ID: <8C97E4F50AF10EA-14D4-697B@WEBMAIL-MB09.sysops.aol.com> Hey everyone! Really new to all this, I know I can search the FAQ, and I did, but was hoping someone wasn't busy this morning and could give me a step by step at how to extract my email list so I can have a hard copy. Lately, I have been getting a lot of bounces and notices have been sent out that their account will be deleted. Any idea why this is happening? From about 980 people, almost 120 people don't get the email. I realize some might be from old emails but I know others used to get it with the old way. Thanks a lot. ________________________________________________________________________ AOL now offers free email to everyone. Find out more about what's free from AOL at AOL.com. From msapiro at value.net Sat Jun 16 19:37:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 16 Jun 2007 10:37:03 -0700 Subject: [Mailman-Users] List In-Reply-To: <8C97E4F50AF10EA-14D4-697B@WEBMAIL-MB09.sysops.aol.com> Message-ID: letb24 at aol.com wrote: > >Really new to all this, I know I can search the FAQ, and I did, but was hoping someone wasn't busy this morning and could give me a step by step at how to extract my email list so I can have a hard copy. If you mean extract a list of members, your search should have led you to which should answer this question. If you need more help than that, please ask a more specific question. >Lately, I have been getting a lot of bounces and notices have been sent out that their account will be deleted. Any idea why this is happening? If you set Bounce processing->bounce_notify_owner_on_disable to Yes, the list owner will receive a notice with a copy of the bounce that triggers a disable. This should help you determine why posts are bouncing. >From about 980 people, almost 120 people don't get the email. I realize some might be from old emails but I know others used to get it with the old way. Do these almost 120 people have delivery enabled? Do bounces for these members appear in Mailman's bounce log? Is there anything in Mailman's smtp-failure log? Set Bounce processing->bounce_unrecognized_goes_to_list_owner to Yes so you see bounces that aren't recognized as such. If a member has delivery enabled and the members delivery doesn't bounce, It is probably being spam filtered somewhere outside of Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From guvnur at gmail.com Sun Jun 17 18:40:42 2007 From: guvnur at gmail.com (Michael Ballard) Date: Sun, 17 Jun 2007 09:40:42 -0700 Subject: [Mailman-Users] Cron gate news Illegal Command Message-ID: I recently installed mailman 2.1.9-2 via RPM on Fedora Core 6. Everything seems to be working fine except every 5 minutes I receive the following error via my mailman list: "Illegal command: /usr/lib/mailman/cron/gate_news" root is sending it. /usr/lib/mailman/cron/gate_news/ has the same permissions as the other cron jobs in //usr/lib/mailman/cron/ I edited /usr/lib/mailman/cron/crontab.in/, commenting out what I thought the offending line was: "0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news" to "# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman /usr/lib/mailman/cron/gate_news" After editing the file, I restart mailman as root, so the cron permissions are all correct. But I still receive the error. Any help would be much appreciated, the same E-mail every 5 minutes is getting awfully annoying. -- Censorship is telling a man he can't have a steak just because a baby can't chew it. - Mark Twain From msapiro at value.net Sun Jun 17 18:57:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 17 Jun 2007 09:57:03 -0700 Subject: [Mailman-Users] Cron gate news Illegal Command In-Reply-To: Message-ID: Michael Ballard wrote: >I recently installed mailman 2.1.9-2 via RPM on Fedora Core 6. > >Everything seems to be working fine except every 5 minutes I receive the >following error via my mailman list: > >"Illegal command: /usr/lib/mailman/cron/gate_news" > >root is sending it. I don't know what would be causing this. Is there any other information in the emailed error or anything in Mailman's logs, particularly 'error' and 'fromusenet'? Do any of your lists have gateway_to_mail set to Yes? What happens if you 'su mailman' and try to run /usr/lib/mailman/cron/gate_news ? >/usr/lib/mailman/cron/gate_news/ has the same permissions as the other cron >jobs in //usr/lib/mailman/cron/ > >I edited /usr/lib/mailman/cron/crontab.in/, commenting out what I thought >the offending line was: > >"0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman >/usr/lib/mailman/cron/gate_news" >to >"# 0,5,10,15,20,25,30,35,40,45,50,55 * * * * mailman >/usr/lib/mailman/cron/gate_news" > >After editing the file, I restart mailman as root, so the cron permissions >are all correct. The crontab.in file is not the running crontab. The RPM probably installs that file in /etc/cron.d/mailman which is the file you'd have to edit to stop running the /usr/lib/mailman/cron/gate_news command. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jun 17 19:01:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 17 Jun 2007 10:01:35 -0700 Subject: [Mailman-Users] Cron gate news Illegal Command In-Reply-To: Message-ID: Mark Sapiro wrote: >Michael Ballard wrote: > >>I recently installed mailman 2.1.9-2 via RPM on Fedora Core 6. >> >>Everything seems to be working fine except every 5 minutes I receive the >>following error via my mailman list: >> >>"Illegal command: /usr/lib/mailman/cron/gate_news" >> >>root is sending it. > > >I don't know what would be causing this. Actually, I do. What is the first line of /usr/lib/mailman/cron/gate_news ? It will be something like #! /usr/bin/python It is probably this which is the 'Illegal command'. What about the other scripts in /usr/lib/mailman/cron/ ? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Tue Jun 19 00:17:36 2007 From: adamsca at gmail.com (Christopher Adams) Date: Mon, 18 Jun 2007 15:17:36 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions Message-ID: <27572d930706181517l3b76811ct762a7e709f47cff1@mail.gmail.com> After a hardware failure, I am trying to install Mailman on another server. As per the documentation, I added myself to the Mailman group and ran the configure as me. I used --with-mail-gid=mailman and --with-cgi-gid=www. I then ran make install. It seemed to work okay. I ran ./check_perms -f and all looks okay. I went to the mailman directory and did this: cd /usr/local/mailman chgrp mailman . chmod a+rx,g+ws I added a ScriptAlias entry in the apache conf file: ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ I restarted Apache, Postfix, and Mailman. No matter what I do, if I go to the URL: http://mydomain.com/mailman/admin/create I get the message: "You don't have permission to access /mailman/ on this server." I tried doing the configure with actual gid number and tried using different combinations such as mail-gid=postfix and cgi-gid=nobody. None of that seems to make a difference. I would appreciate any ideas as to what is going on. It appears to be a permissions problem but I would like to narrow it down one way or another. Thanks -- Christopher Adams adamsca at gmail.com From msapiro at value.net Tue Jun 19 00:37:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 18 Jun 2007 15:37:47 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: <27572d930706181517l3b76811ct762a7e709f47cff1@mail.gmail.com> Message-ID: Christopher Adams wrote: > >I then ran make install. It seemed to work okay. I ran ./check_perms >-f and all looks okay. > >I went to the mailman directory and did this: > >cd /usr/local/mailman >chgrp mailman . >chmod a+rx,g+ws You don't trust check_perms? >I added a ScriptAlias entry in the apache conf file: > >ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/ > >I restarted Apache, Postfix, and Mailman. > >No matter what I do, if I go to the URL: > >http://mydomain.com/mailman/admin/create > >I get the message: > >"You don't have permission to access /mailman/ on this server." What does the apache error_log say about this? What are the ownership and permissions of the files in /usr/local/mailman/cgi-bin/ ? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From adamsca at gmail.com Tue Jun 19 00:52:47 2007 From: adamsca at gmail.com (Christopher Adams) Date: Mon, 18 Jun 2007 15:52:47 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: References: <27572d930706181517l3b76811ct762a7e709f47cff1@mail.gmail.com> Message-ID: <27572d930706181552n33f08cd5ta0766d62be0dfc60@mail.gmail.com> >You don't trust check_perms? Not sure about that. > What does the apache error_log say about this? client denied by server configuration: /usr/local/mailman/cgi-bin/create > What are the ownership and permissions of the files in > /usr/local/mailman/cgi-bin/ ? mailman.mailman rwxr-sr-x From msapiro at value.net Tue Jun 19 01:15:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 18 Jun 2007 16:15:47 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: <27572d930706181552n33f08cd5ta0766d62be0dfc60@mail.gmail.com> Message-ID: Christopher Adams wrote: > >> What does the apache error_log say about this? > >client denied by server configuration: /usr/local/mailman/cgi-bin/create So this is an apache configuration issue, not a Mailman permissions issue. Do you have ExecCGI implicitly or explicitly on the /usr/local/mailman/cgi-bin/ directory in the apache config plus all the other apache stuff like mod_cgi? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From JLeavelle at PensionRights.org Tue Jun 19 02:12:40 2007 From: JLeavelle at PensionRights.org (Joellen Leavelle) Date: Mon, 18 Jun 2007 20:12:40 -0400 Subject: [Mailman-Users] People are dropping off several of our listservs and we don't know why Message-ID: <5B204A7D0543C44DB984C8305F14496738D280@studebaker.PRC.Local> Hi. My subject line basically says it all. We run several listservs (both internal and external) and all of a sudden several people just stopped receiving the messages we sent. At first we thought it was a problem with our internal e-mail set up, but a few months later other people started telling us that they hadn't received any listserv messages for 2 months. Have any of you ever experienced this problem? If so, how do you fix it? I've gone in to look at the subscription list and the people who aren't receiving the messages are still on the list. As a side note, our vendor does not know what the problem is nor does he know how to fix it. I'm posting here in hopes that there is something very simple that we are overlooking. I have been on this listserv for about a week and it seems that many of you are much more technically-savvy than I am. I apologize in advance for not knowing things that may be basic. Any advice you could give would be much appreciated. Thanks! Joellen Leavelle Communications Coordinator and Logistics Manager Pension Rights Center 1350 Connecticut Avenue, NW Suite 206 Washington, DC 20036 Phone: (202) 296-3776 Fax: (202) 296-1571 www.pensionrights.org From adamsca at gmail.com Tue Jun 19 02:55:57 2007 From: adamsca at gmail.com (Christopher Adams) Date: Mon, 18 Jun 2007 17:55:57 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: References: <27572d930706181552n33f08cd5ta0766d62be0dfc60@mail.gmail.com> Message-ID: <27572d930706181755u31340181vec9479224db8e784@mail.gmail.com> On 6/18/07, Mark Sapiro wrote: > Christopher Adams wrote: > > > >> What does the apache error_log say about this? > > > >client denied by server configuration: /usr/local/mailman/cgi-bin/create > > > So this is an apache configuration issue, not a Mailman permissions > issue. Do you have ExecCGI implicitly or explicitly on the > /usr/local/mailman/cgi-bin/ directory in the apache config plus all > the other apache stuff like mod_cgi? Yes, I see that it is an Apache issue. In httpd.conf, for the Document Root, I have set: RewriteEngine On Options FollowSymLinks ExecCGI AllowOverride None Order deny,allow Deny from all Options All I also have a Directory entry for the /usr/local/mailman directory, with ExecCGI specified, which I guess is redundant if I have it above. As for mod_cgi, Apache says that it is loading it on startup. I know this isn't and Apache mailing list, but if you have suggestions, they are most welcome. Chris From msapiro at value.net Tue Jun 19 02:59:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 18 Jun 2007 17:59:57 -0700 Subject: [Mailman-Users] People are dropping off several of our listservsand we don't know why In-Reply-To: <5B204A7D0543C44DB984C8305F14496738D280@studebaker.PRC.Local> Message-ID: Joellen Leavelle wrote: >Hi. My subject line basically says it all. We run several listservs >(both internal and external) and all of a sudden several people just >stopped receiving the messages we sent. At first we thought it was a >problem with our internal e-mail set up, but a few months later other >people started telling us that they hadn't received any listserv >messages for 2 months. Have any of you ever experienced this problem? >If so, how do you fix it? I've gone in to look at the subscription list >and the people who aren't receiving the messages are still on the list. And is their delivery enabled? >As a side note, our vendor does not know what the problem is nor does he >know how to fix it. I'm posting here in hopes that there is something >very simple that we are overlooking. You should have all the notifications on the Bounce processing page set to Yes. You or your vendor should check Mailman's 'bounce' log to see if bounces are being returned. If the user's delivery is enabled, and they aren't bouncing, the messages are getting spam filtered or otherwise dropped outside of 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 Jun 19 03:09:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 18 Jun 2007 18:09:12 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: <27572d930706181755u31340181vec9479224db8e784@mail.gmail.com> Message-ID: Christopher Adams wrote: >Yes, I see that it is an Apache issue. In httpd.conf, for the Document >Root, I have set: > > > RewriteEngine On > Options FollowSymLinks ExecCGI > AllowOverride None > Order deny,allow > Deny from all So you are denying access to everyone not matching an applicable Allow. Do you have an Allow directive somewhere that would allow access to the mailman CGIs? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carconni at earthlink.net Tue Jun 19 04:35:23 2007 From: carconni at earthlink.net (carconni) Date: Mon, 18 Jun 2007 19:35:23 -0700 Subject: [Mailman-Users] moved lists and now they don't work Message-ID: Hi I had to move lists. We had a hardware failure and they had to move to our new mail server. The mail server migration went fine and we thought mailman moved okay as well but we were wrong. Earlier today I tried to create a new list and and got an error so my boss said to check permissions. I ran the /usr/share/mailman/bin/ check_perms -f in every mailman file I could find but Im still getting permission errors. I even gave global permissions to all the archives but no luck. Right now, lists have stopped - they just aren't working and I just can't figure out what the problem is. The more we tried to fix it, the worse it got. Unfortunately my company heavily relies on them so I figured before I set out to manually configure mail aliases, does anyone know a way around this mess? from var/mailman/logs/error: (the permissions and ownership for the client-list is -rw-r--r-- 1 root mailman 479 Jun 18 13:30 / private/var/mailman/archives/private/client-list/index.html) Jun 18 19:24:34 2007 (10816) SHUNTING: 1182219873.5167899 +ceff885a98ff1c83a23f7e83b4d94678813ee808 Jun 18 19:25:36 2007 (10819) Uncaught runner exception: [Errno 1] Operation not permitted: '/private/var/mailman/archives/public/client- list' Jun 18 19:25:36 2007 (10819) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose mlist.Save() File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save self.CheckHTMLArchiveDir() File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, in CheckHTMLArchiveDir breaklink(pubdir) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, in breaklink os.unlink(link) OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ archives/public/client-list' Jun 18 19:25:36 2007 (10819) SHUNTING: 1182219935.3121431 +07ef8a32317dde697d0042ee151b8fd11d41b398 Jun 18 19:25:36 2007 (10816) Uncaught runner exception: [Errno 13] Permission denied: '/private/var/mailman/archives/private/client-list/ index.html' Jun 18 19:25:36 2007 (10816) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, in ArchiveMail h.close() File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, in close self.write_TOC() File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line 1048, in write_TOC toc = open(os.path.join(self.basedir, 'index.html'), 'w') IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/client-list/index.html' Jun 18 19:25:36 2007 (10816) SHUNTING: 1182219935.3121431 +1f5997710b510ce2af03c4b18e68bca2a9a7cf5d Jun 18 19:25:53 2007 (10819) Uncaught runner exception: [Errno 1] Operation not permitted: '/private/var/mailman/archives/public/client- list' Jun 18 19:25:53 2007 (10819) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose mlist.Save() File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save self.CheckHTMLArchiveDir() File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, in CheckHTMLArchiveDir breaklink(pubdir) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, in breaklink os.unlink(link) OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ archives/public/client-list' Jun 18 19:25:53 2007 (10819) SHUNTING: 1182219952.298547 +a97ef5907aa7d67744b62971add1b089b4336b32 Jun 18 19:25:53 2007 (10816) Uncaught runner exception: [Errno 13] Permission denied: '/private/var/mailman/archives/private/client-list/ index.html' Jun 18 19:25:53 2007 (10816) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, in ArchiveMail h.close() File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, in close self.write_TOC() File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line 1048, in write_TOC toc = open(os.path.join(self.basedir, 'index.html'), 'w') IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/client-list/index.html' Jun 18 19:25:53 2007 (10816) SHUNTING: 1182219952.298547 +542a885011bac44ed8f869a06f7c64ebe07acaf9 Jun 18 19:27:07 2007 (10819) Uncaught runner exception: [Errno 1] Operation not permitted: '/private/var/mailman/archives/public/client- list' Jun 18 19:27:07 2007 (10819) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 133, in _dispose mlist.Save() File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save self.CheckHTMLArchiveDir() File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, in CheckHTMLArchiveDir breaklink(pubdir) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, in breaklink os.unlink(link) OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ archives/public/client-list' Jun 18 19:27:07 2007 (10819) SHUNTING: 1182220026.5520279 +b4a5f31a903a595b30aad7c8b13e6b37e44b3b25 Jun 18 19:27:07 2007 (10816) Uncaught runner exception: [Errno 13] Permission denied: '/private/var/mailman/archives/private/client-list/ index.html' Jun 18 19:27:07 2007 (10816) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, in ArchiveMail h.close() File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, in close self.write_TOC() File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line 1048, in write_TOC toc = open(os.path.join(self.basedir, 'index.html'), 'w') IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/client-list/index.html' Jun 18 19:27:07 2007 (10816) SHUNTING: 1182220026.5520279 +eddee6c8cd6b87769edeaa60fe9c23f1e3e19640 From msapiro at value.net Tue Jun 19 07:08:40 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 18 Jun 2007 22:08:40 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: Message-ID: carconni wrote: > >I had to move lists. We had a hardware failure and they had to move >to our new mail server. The mail server migration went fine and we >thought mailman moved okay as well but we were wrong. > >Earlier today I tried to create a new list and and got an error so my >boss said to check permissions. I ran the /usr/share/mailman/bin/ >check_perms -f in every mailman file I could find but Im still >getting permission errors. I even gave global permissions to all the >archives but no luck. It doesn't matter where your current directory is. You just run /usr/share/mailman/bin/check_perms -f as root until it reports no errors. >Right now, lists have stopped - they just aren't working and I just >can't figure out what the problem is. The more we tried to fix it, >the worse it got. Unfortunately my company heavily relies on them so >I figured before I set out to manually configure mail aliases, does >anyone know a way around this mess? > >from var/mailman/logs/error: (the permissions and ownership for the >client-list is -rw-r--r-- 1 root mailman 479 Jun 18 13:30 / >private/var/mailman/archives/private/client-list/index.html) It should be group writable - i.e. -rw-rw-r-- 1 root mailman >Jun 18 19:24:34 2007 (10816) SHUNTING: 1182219873.5167899 >+ceff885a98ff1c83a23f7e83b4d94678813ee808 >Jun 18 19:25:36 2007 (10819) Uncaught runner exception: [Errno 1] >Operation not permitted: '/private/var/mailman/archives/public/client- >list' >Jun 18 19:25:36 2007 (10819) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >133, in _dispose > mlist.Save() > File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save > self.CheckHTMLArchiveDir() > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >in CheckHTMLArchiveDir > breaklink(pubdir) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >in breaklink > os.unlink(link) >OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >archives/public/client-list' I'm guessing when you backed up and moved from the old machines, you wound up with files in /private/var/mailman/archives/public/ There should only be symlinks in that directory. Every /private/var/mailman/archives/public/ and /private/var/mailman/archives/public/ is a symlink to the corresponding /private/var/mailman/archives/private/ and /private/var/mailman/archives/private/ directory. Either fixing that or simply removing everything in the /private/var/mailman/archives/public/ will allow Mailman to recreate the proper symlinks. >Jun 18 19:25:36 2007 (10819) SHUNTING: 1182219935.3121431 >+07ef8a32317dde697d0042ee151b8fd11d41b398 >Jun 18 19:25:36 2007 (10816) Uncaught runner exception: [Errno 13] >Permission denied: '/private/var/mailman/archives/private/client-list/ >index.html' >Jun 18 19:25:36 2007 (10816) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >_dispose > mlist.ArchiveMail(msg) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >in ArchiveMail > h.close() > File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >in close > self.write_TOC() > File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >1048, in write_TOC > toc = open(os.path.join(self.basedir, 'index.html'), 'w') >IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/client-list/index.html' > >Jun 18 19:25:36 2007 (10816) SHUNTING: 1182219935.3121431 >+1f5997710b510ce2af03c4b18e68bca2a9a7cf5d >Jun 18 19:25:53 2007 (10819) Uncaught runner exception: [Errno 1] >Operation not permitted: '/private/var/mailman/archives/public/client- >list' >Jun 18 19:25:53 2007 (10819) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >133, in _dispose > mlist.Save() > File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save > self.CheckHTMLArchiveDir() > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >in CheckHTMLArchiveDir > breaklink(pubdir) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >in breaklink > os.unlink(link) >OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >archives/public/client-list' > >Jun 18 19:25:53 2007 (10819) SHUNTING: 1182219952.298547 >+a97ef5907aa7d67744b62971add1b089b4336b32 >Jun 18 19:25:53 2007 (10816) Uncaught runner exception: [Errno 13] >Permission denied: '/private/var/mailman/archives/private/client-list/ >index.html' >Jun 18 19:25:53 2007 (10816) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >_dispose > mlist.ArchiveMail(msg) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >in ArchiveMail > h.close() > File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >in close > self.write_TOC() > File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >1048, in write_TOC > toc = open(os.path.join(self.basedir, 'index.html'), 'w') >IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/client-list/index.html' > >Jun 18 19:25:53 2007 (10816) SHUNTING: 1182219952.298547 >+542a885011bac44ed8f869a06f7c64ebe07acaf9 >Jun 18 19:27:07 2007 (10819) Uncaught runner exception: [Errno 1] >Operation not permitted: '/private/var/mailman/archives/public/client- >list' >Jun 18 19:27:07 2007 (10819) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >133, in _dispose > mlist.Save() > File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save > self.CheckHTMLArchiveDir() > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >in CheckHTMLArchiveDir > breaklink(pubdir) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >in breaklink > os.unlink(link) >OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >archives/public/client-list' > >Jun 18 19:27:07 2007 (10819) SHUNTING: 1182220026.5520279 >+b4a5f31a903a595b30aad7c8b13e6b37e44b3b25 >Jun 18 19:27:07 2007 (10816) Uncaught runner exception: [Errno 13] >Permission denied: '/private/var/mailman/archives/private/client-list/ >index.html' >Jun 18 19:27:07 2007 (10816) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >_dispose > mlist.ArchiveMail(msg) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >in ArchiveMail > h.close() > File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >in close > self.write_TOC() > File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >1048, in write_TOC > toc = open(os.path.join(self.basedir, 'index.html'), 'w') >IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/client-list/index.html' > >Jun 18 19:27:07 2007 (10816) SHUNTING: 1182220026.5520279 >+eddee6c8cd6b87769edeaa60fe9c23f1e3e19640 > > > >------------------------------------------------------ >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/msapiro%40value.net > >Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From devon at jobspeed.com.au Tue Jun 19 08:00:11 2007 From: devon at jobspeed.com.au (AusArchitect) Date: Mon, 18 Jun 2007 23:00:11 -0700 (PDT) Subject: [Mailman-Users] Newbe question - Can I do this with Mailman? Message-ID: <11188463.post@talk.nabble.com> Hi, Can I run Mailman on my linux webserver and have it do the following? Each of my clients is a company with say 1000 clients of their own, The 30 companies want to give me a email list with their 1000 clients. I then need to send out 30,000 emails with each being taylored to those companies graphics style (with their logo's, fonts etc from a template). The killer is that across the 30 companies there are probably duplicate email addresses, so i need to de-duplicate but also make sure that these duplicates are sent mail (over a period of time) by all the companies they are with. EG, company 1 would send dupe #1 on 1st email, Company 2 would send dupe #1 on second email ( a week later ). The email content will be the 5 url links which each company wants to send out to their clients (links to pages on my website). So each of the 30 companies will have 5 url's which will be in a email which looks like it comes from them. 1 email = 5x url's to 5 pages on my site. for example. Any help would be most apprecated. Thanks -- View this message in context: http://www.nabble.com/Newbe-question---Can-I-do-this-with-Mailman--tf3944271.html#a11188463 Sent from the Mailman - Users mailing list archive at Nabble.com. From brad at shub-internet.org Tue Jun 19 08:13:43 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 19 Jun 2007 01:13:43 -0500 Subject: [Mailman-Users] Newbe question - Can I do this with Mailman? In-Reply-To: <11188463.post@talk.nabble.com> References: <11188463.post@talk.nabble.com> Message-ID: On 6/18/07, AusArchitect wrote: > So each of the 30 companies will have 5 url's which will be in a email which > looks like it comes from them. > 1 email = 5x url's to 5 pages on my site. for example. Search the FAQ Wizard for "look and feel". Read all articles that are returned, as well as the other related ones that you are referred to. See also FAQs 1.22 and 1.23. Once you've read those, if you have any further questions, please let us know what issues you have that were not addressed. > View this message in context: >http://www.nabble.com/Newbe-question---Can-I-do-this-with-Mailman--tf3944271.html#a11188463 > Sent from the Mailman - Users mailing list archive at Nabble.com. I think we're going to have to fix this problem. They are not authorized to act as a gateway of this list. I think this has to stop. See FAQ 1.18. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From adamsca at gmail.com Tue Jun 19 21:40:07 2007 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 19 Jun 2007 12:40:07 -0700 Subject: [Mailman-Users] Mailman installation problem/permissions In-Reply-To: References: <27572d930706181755u31340181vec9479224db8e784@mail.gmail.com> Message-ID: <27572d930706191240l5c9b1030xa9ead8dcc18345d7@mail.gmail.com> Thank you for pointing that out. Mailman is now working okay. On 6/18/07, Mark Sapiro wrote: > Christopher Adams wrote: > > >Yes, I see that it is an Apache issue. In httpd.conf, for the Document > >Root, I have set: > > > > > > RewriteEngine On > > Options FollowSymLinks ExecCGI > > AllowOverride None > > Order deny,allow > > Deny from all > > > So you are denying access to everyone not matching an applicable Allow. > Do you have an Allow directive somewhere that would allow access to > the mailman CGIs? > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > -- Christopher Adams adamsca at gmail.com From adamsca at gmail.com Tue Jun 19 23:02:51 2007 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 19 Jun 2007 14:02:51 -0700 Subject: [Mailman-Users] problem creating new list on the web - Unkown Virtual Host Message-ID: <27572d930706191402k38634465hd38607a171b581f9@mail.gmail.com> When I create a list via the web, I get the dreaded 'Unknown Virtual Host mailinglists.state.or.us' message. I consulted the FAQ, but I couldn't see what was wrong: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.036.htp I didn't configure the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST during the configuration of Mailman, so I added them to mm_cfg.py and restarted mailman. My entry looks like this: #Virtual Host and Email Host add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us' DEFAULT_URL_HOST = 'mailinglists.state.or.us' Other list admin functions from the web work and I can create lists from the command line. Any tips on what to look for? -- Christopher Adams adamsca at gmail.com From brad at shub-internet.org Wed Jun 20 01:33:25 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 19 Jun 2007 18:33:25 -0500 Subject: [Mailman-Users] problem creating new list on the web - Unkown Virtual Host In-Reply-To: <27572d930706191402k38634465hd38607a171b581f9@mail.gmail.com> References: <27572d930706191402k38634465hd38607a171b581f9@mail.gmail.com> Message-ID: On 6/19/07, Christopher Adams wrote: > When I create a list via the web, I get the dreaded 'Unknown Virtual > Host mailinglists.state.or.us' message. That name does not exist in the DNS: % dig mailinglists.state.or.us. any ; <<>> DiG 9.3.4 <<>> mailinglists.state.or.us. any ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49283 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mailinglists.state.or.us. IN ANY ;; Query time: 3 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Tue Jun 19 18:30:48 2007 ;; MSG SIZE rcvd: 42 % dig @lynx.state.or.us. mailinglists.state.or.us. any ; <<>> DiG 9.3.4 <<>> @lynx.state.or.us. mailinglists.state.or.us. any ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12659 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;mailinglists.state.or.us. IN ANY ;; AUTHORITY SECTION: state.or.us. 3600 IN SOA lynx.state.or.us. dns-admin.state.or.us. 2007061500 10800 1800 604800 3600 ;; Query time: 72 msec ;; SERVER: 159.121.107.82#53(159.121.107.82) ;; WHEN: Tue Jun 19 18:31:44 2007 ;; MSG SIZE rcvd: 93 You might want to get that fixed. While you're at it, you should have your nameserver administrators look into fixing the other things wrong with the domain -- see . -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Wed Jun 20 02:56:57 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 19 Jun 2007 17:56:57 -0700 Subject: [Mailman-Users] problem creating new list on the web - UnkownVirtual Host In-Reply-To: <27572d930706191402k38634465hd38607a171b581f9@mail.gmail.com> Message-ID: Christopher Adams wrote: >When I create a list via the web, I get the dreaded 'Unknown Virtual >Host mailinglists.state.or.us' message. > >I consulted the FAQ, but I couldn't see what was wrong: > >http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.036.htp Also see (now referenced from 4.36). >I didn't configure the DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST during >the configuration of Mailman, so I added them to mm_cfg.py and >restarted mailman. My entry looks like this: > >#Virtual Host and Email Host >add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) >DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us' >DEFAULT_URL_HOST = 'mailinglists.state.or.us' Presumably the definitions of DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in Defaults.py are wrong since you didn't configure them and your host is 'Unknown'. Therefore, there are two problems with the above. The first problem is you want to remove the erroneous VIRTUAL_HOSTS entry created in Defaults.py. This is not critical, but it is good practice. The main problem is you need to move the add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) directive to a point AFTER you have redefined DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST. Otherwise, you are just re-adding the erroneous entry from Defaults.py. So what you want is VIRTUAL_HOSTS.clear() DEFAULT_EMAIL_HOST = 'mailinglists.state.or.us' DEFAULT_URL_HOST = 'mailinglists.state.or.us' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) (the first 3 can be in any order, but the add_virtualhost() must be the last of the 4. >Other list admin functions from the web work and I can create lists >from the command line. You may need to run fix_url on the lists you created from the command line. See the above referenced FAQ 4.62 and also 4.69. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From G.Booth at usm.edu Wed Jun 20 04:10:33 2007 From: G.Booth at usm.edu (George Booth) Date: Tue, 19 Jun 2007 21:10:33 -0500 Subject: [Mailman-Users] Troublesome Mailman Errors Message-ID: <001b01c7b2e0$2f1e1eb0$f3cb5f83@elysium> Greetings, I've been unable to find answers for two problems that have been plaguing me for about a week or so now, and decided to turn to the list for help. We're running Mailman on an IBM server with RedHat 2.6.9-42.0.10.EL-i686 The first problem is that messages sent to one of my lists (750+ members) don't get propagated out to all the members. At this point, I'm not sure what percentage is receiving and what percentage isn't receiving, but based on small samplings, I think it's safe to conclude that more aren't receiving than are. Checking the post log, I see the following for test messages I've sent to the list; I know of 5 people who have received it, of which I am not one: Jun 19 10:47:31 2007 (32175) post to usmtalk from g.booth at usm.edu, size=2800, message-id=<005101c7b289$16a60070$f3cb5f83 at elysium>, 7 failures Jun 19 15:20:28 2007 (32175) post to usmtalk from g.booth at usm.edu, size=2646, message-id=<001301c7b2ad$9f179e40$f3cb5f83 at elysium>, 7 failures One person has been trying to send a message to the list for the last week; he's tried 3 times and, although he's received all of my test messages to the list, he has not seen his own messages come through. I myself have not received any email from the list in around a week, and quite a few others have received no messages at all either. I'm unable to get cooperation from our server admins to get messages traced as they go through our rather complex email system, and am told this is a Mailman problem, so I figured I'd see what the experts think might be possible situations. The other issue we're facing, which I'm also told by the server admins is an internal Mailman problem, is that often the Mailman processes, while outwardly appearing to run, just "stop" working; mail gets queued up, and I have to restart the Mailman service to get the queue moving again. In the Mailman error log, I'm seeing the following tracebacks on an almost minute-by-minute basis: Jun 19 20:22:04 2007 (11284) Uncaught runner exception: Jun 19 20:22:04 2007 (11284) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 273, in send_i18n_digests msg = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/var/mailman/Mailman/Mailbox.py", line 41, in _safeparser return email.message_from_file(fp, Message) File "/var/mailman/pythonlib/email/__init__.py", line 63, in message_from_file return Parser(_class, strict=strict).parse(fp) File "/var/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/var/mailman/pythonlib/email/Parser.py", line 218, in _parsebody payload[start:terminator]) File "/usr/lib/python2.3/sre.py", line 156, in split return _compile(pattern, 0).split(string, maxsplit) MemoryError Jun 19 20:22:04 2007 (11284) SHUNTING: 1182289757.230494+ae5c970b2a7ffee54cafa14a22bf0a5b052b671e Jun 19 20:23:11 2007 (11284) Uncaught runner exception: Jun 19 20:23:11 2007 (11284) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 273, in send_i18n_digests msg = mbox.next() File "/usr/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/var/mailman/Mailman/Mailbox.py", line 41, in _safeparser return email.message_from_file(fp, Message) File "/var/mailman/pythonlib/email/__init__.py", line 63, in message_from_file return Parser(_class, strict=strict).parse(fp) File "/var/mailman/pythonlib/email/Parser.py", line 64, in parse self._parsebody(root, fp, firstbodyline) File "/var/mailman/pythonlib/email/Parser.py", line 218, in _parsebody payload[start:terminator]) MemoryError Jun 19 20:23:11 2007 (11284) SHUNTING: 1182292904.783638+0a96719432d01f6522da13a1fb9ef301d37d0344 June 15 is when the first of these showed up, which leads me to believe it's a seperate issue from the non-delivery of email to all recipients of a list (which, of course, I could be completely wrong about), since the last time I received a message from this list was June 11. Any pointers or suggestions would be greatly appreciated. I have asked the server admins if there could be a physical memory problem, which would cause the Memory Error listed above, and received a negative. I also have asked if the memory allocation for Python was sufficient, and was told it has access to all 16GB of memory that the server holds. I've also come across a suggestion to add the line " self.__conn.set_debuglevel(1)" to the SMTPDirect.py file and restarted Mailman, but that hasn't seemed to help either. Thanks in advance for any help, George Booth <>-<>-<>-<>-<>-<>-<>-<>-<> George Booth iTech Applications Administrator G.Booth at usm.edu University of Southern Mississippi From adamsca at gmail.com Wed Jun 20 05:54:02 2007 From: adamsca at gmail.com (Christopher Adams) Date: Tue, 19 Jun 2007 20:54:02 -0700 Subject: [Mailman-Users] problem creating new list on the web - Unkown Virtual Host In-Reply-To: References: <27572d930706191402k38634465hd38607a171b581f9@mail.gmail.com> Message-ID: <27572d930706192054o5618236cl789d19b74ad409bb@mail.gmail.com> Brad, Sorry for putting you through that. 'mailinglists.state.or.us' is not the actual domain name. I used it as an example. The actual name is 'listsmart.osl.state.or.us' and does exist in DNS. I have a server with 2 NICs. One of the NICs has the 'listsmart.osl.state.or.us' IP attached to it along with another IP. I don't know if that makes any difference. On 6/19/07, Brad Knowles wrote: > On 6/19/07, Christopher Adams wrote: > > > When I create a list via the web, I get the dreaded 'Unknown Virtual > > Host mailinglists.state.or.us' message. > > That name does not exist in the DNS: > > % dig mailinglists.state.or.us. any > > ; <<>> DiG 9.3.4 <<>> mailinglists.state.or.us. any > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 49283 > ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;mailinglists.state.or.us. IN ANY > > ;; Query time: 3 msec > ;; SERVER: 192.168.1.1#53(192.168.1.1) > ;; WHEN: Tue Jun 19 18:30:48 2007 > ;; MSG SIZE rcvd: 42 > > > % dig @lynx.state.or.us. mailinglists.state.or.us. any > > ; <<>> DiG 9.3.4 <<>> @lynx.state.or.us. mailinglists.state.or.us. any > ; (1 server found) > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12659 > ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;mailinglists.state.or.us. IN ANY > > ;; AUTHORITY SECTION: > state.or.us. 3600 IN SOA lynx.state.or.us. > dns-admin.state.or.us. 2007061500 10800 1800 604800 3600 > > ;; Query time: 72 msec > ;; SERVER: 159.121.107.82#53(159.121.107.82) > ;; WHEN: Tue Jun 19 18:31:44 2007 > ;; MSG SIZE rcvd: 93 > > > You might want to get that fixed. > > While you're at it, you should have your nameserver administrators > look into fixing the other things wrong with the domain -- see > . > > -- > Brad Knowles , Consultant & Author > LinkedIn Profile: > Slides from Invited Talks: > > 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 > -- Christopher Adams adamsca at gmail.com From msapiro at value.net Wed Jun 20 06:53:23 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 19 Jun 2007 21:53:23 -0700 Subject: [Mailman-Users] Troublesome Mailman Errors In-Reply-To: <001b01c7b2e0$2f1e1eb0$f3cb5f83@elysium> Message-ID: George Booth wrote: > >I've been unable to find answers for two problems that have been plaguing me >for about a week or so now, and decided to turn to the list for help. We're >running Mailman on an IBM server with RedHat 2.6.9-42.0.10.EL-i686 > >The first problem is that messages sent to one of my lists (750+ members) >don't get propagated out to all the members. At this point, I'm not sure >what percentage is receiving and what percentage isn't receiving, but based >on small samplings, I think it's safe to conclude that more aren't receiving >than are. Checking the post log, I see the following for test messages I've >sent to the list; I know of 5 people who have received it, of which I am not >one: > >Jun 19 10:47:31 2007 (32175) post to usmtalk from g.booth at usm.edu, >size=2800, message-id=<005101c7b289$16a60070$f3cb5f83 at elysium>, 7 failures >Jun 19 15:20:28 2007 (32175) post to usmtalk from g.booth at usm.edu, >size=2646, message-id=<001301c7b2ad$9f179e40$f3cb5f83 at elysium>, 7 failures Look in Mailman's smtp and smtp-failure logs. smtp will tell you how many recipients were sent to and smtp-failure will tell you what the failure reasons are. >One person has been trying to send a message to the list for the last week; >he's tried 3 times and, although he's received all of my test messages to >the list, he has not seen his own messages come through. Has anyone else seen his posts? Are they in the archive? Does he have 'not metoo' set? Does he have 'no dups' set and Cc: himself?. Does he use gmail (see the end of ) >I myself have not >received any email from the list in around a week, and quite a few others >have received no messages at all either. I'm unable to get cooperation from >our server admins to get messages traced as they go through our rather >complex email system, and am told this is a Mailman problem, so I figured >I'd see what the experts think might be possible situations. > >The other issue we're facing, which I'm also told by the server admins is an >internal Mailman problem, is that often the Mailman processes, while >outwardly appearing to run, just "stop" working; mail gets queued up, and I >have to restart the Mailman service to get the queue moving again. In the >Mailman error log, I'm seeing the following tracebacks on an almost >minute-by-minute basis: > >Jun 19 20:22:04 2007 (11284) Uncaught runner exception: >Jun 19 20:22:04 2007 (11284) Traceback (most recent call last): > File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop > self._onefile(msg, msgdata) > File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/var/mailman/Mailman/Queue/IncomingRunner.py", line 153, in >_dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/var/mailman/Mailman/Handlers/ToDigest.py", line 91, in process > send_digests(mlist, mboxfp) > File "/var/mailman/Mailman/Handlers/ToDigest.py", line 132, in >send_digests > send_i18n_digests(mlist, mboxfp) > File "/var/mailman/Mailman/Handlers/ToDigest.py", line 273, in >send_i18n_digests > msg = mbox.next() > File "/usr/lib/python2.3/mailbox.py", line 35, in next > return self.factory(_Subfile(self.fp, start, stop)) > File "/var/mailman/Mailman/Mailbox.py", line 41, in _safeparser > return email.message_from_file(fp, Message) > File "/var/mailman/pythonlib/email/__init__.py", line 63, in >message_from_file > return Parser(_class, strict=strict).parse(fp) > File "/var/mailman/pythonlib/email/Parser.py", line 64, in parse > self._parsebody(root, fp, firstbodyline) > File "/var/mailman/pythonlib/email/Parser.py", line 218, in _parsebody > payload[start:terminator]) > File "/usr/lib/python2.3/sre.py", line 156, in split > return _compile(pattern, 0).split(string, maxsplit) >MemoryError >Jun 19 20:22:04 2007 (11284) SHUNTING: >1182289757.230494+ae5c970b2a7ffee54cafa14a22bf0a5b052b671e There is a VERY large message in the lists//digest.mbox file for the list that is being posted to at the time that these errors occur. This is causing Mailman (IncomingRunner) to grow large in parsing this message to the point it is denied additional memory by the OS. Find the offending list and either move the digest.mbox aside or edit the file and remove the huge message. You should be able to find the digest.mbox by just looking for the huge one. What actually happens here is IncomingRunner is processing a new post. It adds the post to digest.mbox for an eventual digest and then sees that digest.mbox exceeds digest_size_threshhold and tries to send a digest now and encounters the error. This is an older Mailman as the current release will catch the exception and not shunt the message, but digests will still be blocked. Once you fix the digest.mbox, you can run bin/unshunt to finish processing the messages, although it is a good idea to first examine the messages in qfiles/shunt with bin/show_qfiles to make sure all are wanted. >June 15 is when the first of these showed up, which leads me to believe it's >a seperate issue from the non-delivery of email to all recipients of a list >(which, of course, I could be completely wrong about), since the last time I >received a message from this list was June 11. It's the reason no one has received a message from this list since June 15. It is not related to prior non-receipts. >Any pointers or suggestions >would be greatly appreciated. I have asked the server admins if there could >be a physical memory problem, which would cause the Memory Error listed >above, and received a negative. I also have asked if the memory allocation >for Python was sufficient, and was told it has access to all 16GB of memory >that the server holds. I've also come across a suggestion to add the line " >self.__conn.set_debuglevel(1)" to the SMTPDirect.py file and restarted >Mailman, but that hasn't seemed to help either. You're not getting to SMTPDirect.py because the messages are shunted before delivery. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From hopkins.jenny at gmail.com Wed Jun 20 14:17:52 2007 From: hopkins.jenny at gmail.com (Jenny Hopkins) Date: Wed, 20 Jun 2007 13:17:52 +0100 Subject: [Mailman-Users] lurker behaving strangely Message-ID: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> Hullo there, I've recently taken over the admin of a server running mailman and lurker, for several mailing lists. It was noticed that the archives were out of date and new messages weren't archiving. I traced the problem in the end to the mailman mm_cfg.py script having PUBLIC_EXTERNAL_ARCHIVER = 'usr/bin/lurker-index-mm -l %(listname)s -m' rather than the newer wrapper /usr/bin/lurker-index-lc, the wrapper script probably having been updated in an upgrade from debian sarge to etch. I did a mass import sudo /usr/bin/lurker-index -v -c /etc/lurker/lurker.conf -l -i /var/lib/mailman/archives/public/.mbox/.mbox The mails now all appeared up to date in the webpage showing the archives, and new posts appeared as they should. Hoorah! A few days later, I got a mail from someone telling me the archives had vanished again. On looking, the lurker page showed old mails once again. The external archiver error log has non-zero exit status: 127 again. Re-running the mass import for one of the lists adds only two test mails I sent since fixing the individual archiver. What is going on?! I'm completely bewildered. Any help appreciated, I realise this post is probably a bit garbled. Thanks, Jenny From carbonnb at gmail.com Wed Jun 20 14:46:24 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Wed, 20 Jun 2007 08:46:24 -0400 Subject: [Mailman-Users] Custom verify.txt has Wrong Content-Type Message-ID: I have created a custom verify.txt for one of my lists, that is bilingual, English & Chinese. It is in $PREFIX/lists//en It goes out just fine, but the MIME Content-Type is wrong for this file to be read properly. It has a charset of us-ascii. Is there anyway to change it to utf-8 easily or do I need to change the source code somewhere? -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From hopkins.jenny at gmail.com Wed Jun 20 15:02:29 2007 From: hopkins.jenny at gmail.com (Jenny Hopkins) Date: Wed, 20 Jun 2007 14:02:29 +0100 Subject: [Mailman-Users] lurker behaving strangely In-Reply-To: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> References: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> Message-ID: <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> On 20/06/07, Jenny Hopkins wrote: > Hullo there, > > I've recently taken over the admin of a server running mailman and > lurker, for several mailing lists. > > It was noticed that the archives were out of date and new messages > weren't archiving. I traced the problem in the end to the mailman > mm_cfg.py script having > PUBLIC_EXTERNAL_ARCHIVER = 'usr/bin/lurker-index-mm -l %(listname)s -m' > rather than the newer wrapper /usr/bin/lurker-index-lc, the wrapper > script probably having been updated in an upgrade from debian sarge to > etch. > > I did a mass import > sudo /usr/bin/lurker-index -v -c /etc/lurker/lurker.conf -l > -i /var/lib/mailman/archives/public/.mbox/.mbox > > The mails now all appeared up to date in the webpage showing the > archives, and new posts appeared as they should. > Hoorah! > > A few days later, I got a mail from someone telling me the archives > had vanished again. > > On looking, the lurker page showed old mails once again. The external > archiver error log has non-zero exit status: 127 again. > > Re-running the mass import for one of the lists adds only two test > mails I sent since fixing the individual archiver. > Further info on this post. The archive mbox still has the complete set of mails in it. lurker webpage shows, as I said, only old mails. If I click on thread tree it seems to know about the other mails there should be in that thread, but says they are 'deleted'. Even if I rerun the lurker-index to reimport mails they think they are deleted. Using the -d option leaves the lurker db as the original size, without it it doubles so it obviously is importing correctly. Why would the lurker database think mails are deleted? Thanks, Jenny From brad at shub-internet.org Wed Jun 20 20:13:27 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 20 Jun 2007 13:13:27 -0500 Subject: [Mailman-Users] lurker behaving strangely In-Reply-To: <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> References: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> Message-ID: On 6/20/07, Jenny Hopkins wrote: > Why would the lurker database think mails are deleted? This is a problem with lurker and not Mailman. I've never even heard of lurker before, and I've been involved in running mailing lists for over a decade, and I've been involved in the Mailman project for several years. I suspect you'll get a lot more help with your problem if you consult the documentation for lurker, their FAQ, their mailing lists, etc.... That said, knowing nothing at all about the particular external archiver you're using, it sounds to me like you might have a cron job left lying around from before your upgrade and which is pulling up the old wrapper script with the old configuration details, and isn't working as desired. At the very least, it wouldn't hurt to check your cron jobs to make sure they're all in order. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From G.Booth at usm.edu Wed Jun 20 20:36:39 2007 From: G.Booth at usm.edu (George Booth) Date: Wed, 20 Jun 2007 13:36:39 -0500 Subject: [Mailman-Users] Troublesome Mailman Errors In-Reply-To: Message-ID: <000e01c7b369$f1171bf0$f3cb5f83@elysium> Mark Sapiro wrote: >There is a VERY large message in the lists//digest.mbox file >for the list that is being posted to at the time that these errors >occur. >This is causing Mailman (IncomingRunner) to grow large in parsing this >message to the point it is denied additional memory by the OS. >Find the offending list and either move the digest.mbox aside or edit >the file and remove the huge message. You should be able to find the >digest.mbox by just looking for the huge one. There was indeed a very large digest.mbox for one of the lists (not for the one we've been having issues with, though), so I removed the digest.mbox (that list is set up to be used as a departmental email address, so there are only 2 recipients on the list and they weren't digesting anyway), and that removed the MemoryErrors I've been seeing. BTW, I should mention that my version of Mailman is 2.1.5 However, now I'm getting different errors. When I restarted Mailman after removing the digest.mbox file, the errors were: Jun 20 05:36:40 2007 (28020) Cannot connect to SMTP server localhost on port smtp Jun 20 06:00:13 2007 (20879) Cannot connect to SMTP server localhost on port smtp Jun 20 08:02:55 2007 (23371) Cannot connect to SMTP server localhost on port smtp Each instance above is after a restart of the Mailman service. The server admins checked smtp on the box, did somethings that they didn't share with me, and now, I'm getting: Jun 20 09:17:20 2007 (31631) Uncaught runner exception: SMTP instance has no attribute 'sock' Jun 20 09:17:20 2007 (31631) Traceback (most recent call last): File "/var/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/var/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/mailman/Mailman/Queue/OutgoingRunner.py", line 73, in _dispose self._func(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 163, in process conn.quit() File "/var/mailman/Mailman/Handlers/SMTPDirect.py", line 90, in quit self.__conn.quit() File "/usr/lib/python2.3/smtplib.py", line 708, in quit self.docmd("quit") File "/usr/lib/python2.3/smtplib.py", line 369, in docmd self.putcmd(cmd,args) File "/usr/lib/python2.3/smtplib.py", line 325, in putcmd self.send(str) File "/usr/lib/python2.3/smtplib.py", line 310, in send if self.sock: AttributeError: SMTP instance has no attribute 'sock' Jun 20 09:17:20 2007 (31631) SHUNTING: 1182344407.694294+91d21113f1e46e0b450308adbe350c1c50faeff1 At this point, I now have 1500+ emails in the outgoing queue, which won't go anywhere. I've done more checking online and found several things to try, including testing Python's smtp connection, and changed the SMTPHOST from 'localhost' to the actual IP of the box in mm_cfg.py, just in case, with no change. My mailman/smtp log shows some messages going through: Jun 20 09:41:03 2007 (15107) <200706201149.l5KBnHH0029291 at mail.usm.edu> smtp for 2 recips, completed in 0.009 seconds Jun 20 09:41:03 2007 (15107) <200706201150.l5KBoNUw006869 at auxprd.usm.edu> smtp for 6 recips, completed in 0.005 seconds Jun 20 09:41:03 2007 (15107) smtp for 1 recips, completed in 0.003 seconds Jun 20 09:41:03 2007 (15107) smtp for 1 recips, completed in 0.009 seconds Jun 20 09:41:03 2007 (15107) smtp for 1 recips, completed in 0.003 seconds Jun 20 09:41:03 2007 (15107) smtp for 1 recips, completed in 0.008 seconds Jun 20 09:41:06 2007 (15547) <200706201200.l5KC00cm000949 at www.usm.edu> smtp for 1 recips, completed in 0.733 seconds Jun 20 11:10:39 2007 (28494) <001601c25c6a$f7e82470$001ad6b4 at casa9cfb6824b4> smtp for 3 recips, completed in 3599.674 seconds Jun 20 12:10:39 2007 (28494) <001501c7b31a$e9beb6a0$000a4dd4 at ntserver> smtp for 1 recips, completed in 3599.660 seconds Jun 20 13:10:39 2007 (28494) <2154.82.128.1.35.1181656670.squirrel at 72.36.213.90> smtp for 1 recips, completed in 3599.643 seconds But my post log shows failures: Jun 20 09:41:03 2007 (15107) post to george from mail at usm.edu, size=74664, message-id=<200706201149.l5KBnHH0029291 at mail.usm.edu>, 2 failures Jun 20 09:41:03 2007 (15107) post to appsupport from appsup at auxprd.usm.edu, size=2249, message-id=<200706201150.l5KBoNUw006869 at auxprd.usm.edu>, 6 failures Jun 20 09:41:03 2007 (15107) post to sharecare from sharecare-bounces at usm.edu, size=1010, message-id=, 1 failures Jun 20 09:41:03 2007 (15107) post to sharecare from sharecare-owner at usm.edu, size=5000, message-id=, 1 failures Jun 20 09:41:03 2007 (15107) post to rutabaga from rutabaga-bounces at usm.edu, size=1024, message-id=, 1 failures Jun 20 09:41:03 2007 (15107) post to rutabaga from rutabaga-owner at usm.edu, size=3794, message-id=, 1 failures Jun 20 09:41:06 2007 (15547) post to system-reports from root at www.usm.edu, size=2264, message-id=<200706201200.l5KC00cm000949 at www.usm.edu>, 1 failures Jun 20 11:10:39 2007 (28494) post to itc from dlamongst at link2rewards.com, size=2524, message-id=<001601c25c6a$f7e82470$001ad6b4 at casa9cfb6824b4>, 3 failures Jun 20 12:10:39 2007 (28494) post to hr from scredential at adore.dk, size=3975, message-id=<001501c7b31a$e9beb6a0$000a4dd4 at ntserver>, 1 failures Jun 20 13:10:39 2007 (28494) post to med.relations from edward_moore22 at yahoo.co.uk, size=4429, message-id=<2154.82.128.1.35.1181656670.squirrel at 72.36.213.90>, 1 failures And not that many attempts, based on the number of messages waiting in the outgoing queue. The smtp-failure log doesn't show anything useful that I can see: Jun 20 09:59:57 2007 (23726) Low level smtp error: [Errno 32] Broken pipe, msgid: <001601c25c6a$f7e82470$001ad6b4 at casa9cfb6824b4> Jun 20 10:10:40 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: <001601c25c6a$f7e82470$001ad6b4 at casa9cfb6824b4> Jun 20 11:10:39 2007 (28494) delivery to Steven.Blesse at usm.edu failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:39 2007 (28494) delivery to Shelton.Houston at usm.edu failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:39 2007 (28494) delivery to Christopher.Herrod at usm.edu failed with code -1: [Errno 32] Broken pipe Jun 20 11:10:40 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: <001501c7b31a$e9beb6a0$000a4dd4 at ntserver> Jun 20 12:10:39 2007 (28494) delivery to Amy.Byxbe at usm.edu failed with code -1: [Errno 32] Broken pipe Jun 20 12:10:39 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: <2154.82.128.1.35.1181656670.squirrel at 72.36.213.90> Jun 20 13:10:39 2007 (28494) delivery to Tyshuna.Dyess at usm.edu failed with code -1: [Errno 32] Broken pipe Jun 20 13:10:39 2007 (28494) Low level smtp error: [Errno 32] Broken pipe, msgid: <200706200100.l5K101Nx032748 at auxprd.usm.edu> At this point, I'm at a loss. I've gone through the steps outline in the FAQ entry "4.78. Troubleshooting: No mail going out to lists members", and all seems well there. Only other thing I can think of is that under my /var/mailman/locks directory, I have the following: [root at mail1 locks]# ls -al total 8 drwxrwsr-x 2 root mailman 4096 Jun 20 13:30 . drwxrwsr-x 21 root mailman 4096 Jun 19 20:02 .. -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner -rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner.mail1.usm.edu.28475 -rw-rw-r-- 1 mailman mailman 53 Jan 18 2006 master-qrunner.mail.usm.edu.1757.1 [root at mail1 locks]# I don't know if these are required or if I should delete them, or if they even have anything whatsoever to do with the issue at hand. I did find it odd that two of them seem to be dated as June 21, 2007, which is tomorrow (assuming I read that correctly), although a check of the "date" command on the server shows the correct date and time. Once again, any help would be greatly appreciated. Thanks, George Booth <>-<>-<>-<>-<>-<>-<>-<>-<> George Booth iTech Applications Administrator G.Booth at usm.edu University of Southern Mississippi From hopkins.jenny at gmail.com Wed Jun 20 20:43:29 2007 From: hopkins.jenny at gmail.com (Jenny Hopkins) Date: Wed, 20 Jun 2007 19:43:29 +0100 Subject: [Mailman-Users] lurker behaving strangely In-Reply-To: References: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> Message-ID: <9713998d0706201143oc677ffp44173e6e76e5ec82@mail.gmail.com> On 20/06/07, Brad Knowles wrote: > On 6/20/07, Jenny Hopkins wrote: > > > Why would the lurker database think mails are deleted? > > This is a problem with lurker and not Mailman. I've never even heard > of lurker before, and I've been involved in running mailing lists for > over a decade, and I've been involved in the Mailman project for > several years. > > I suspect you'll get a lot more help with your problem if you consult > the documentation for lurker, their FAQ, their mailing lists, etc.... > I'm sorry - I presumed lurker was a sort of add-on to mailman, and thought I saw references to it as I went through the mailman archives. (Googling for 'lurker' and anything to do with mailing lists or irc tends to bring up the wrong references :-)) > > That said, knowing nothing at all about the particular external > archiver you're using, it sounds to me like you might have a cron job > left lying around from before your upgrade and which is pulling up > the old wrapper script with the old configuration details, and isn't > working as desired. > > At the very least, it wouldn't hurt to check your cron jobs to make > sure they're all in order. > Thanks, Brad, I'll check this out. Sorry for mis-post. Jenny From jon.slater at mesanetworks.net Thu Jun 21 00:29:30 2007 From: jon.slater at mesanetworks.net (Jon Slater) Date: Wed, 20 Jun 2007 16:29:30 -0600 Subject: [Mailman-Users] I lost my patch :-( Message-ID: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> I had to re-install MM from scratch this weekend. A long time ago, I had installed a patch that allowed ALL of the member?s of one group to send mail to another group. Example: In my ?board_member? list, under ?Privacy options? (Sender filters). I have: ?@members? in the box labeled ?List of non-member addresses whose postings should be automatically accepted? That way, anyone on the ?member?s? list can e-mail the ?board_member? list. But, in order for this to work, there was a patch that I had to install in MM. I remember it was really easy to do, but I can?t find my instructions. Does anyone know where that?s explained? And how I get it back? Thanks! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.1/857 - Release Date: 6/20/2007 2:18 PM From tkikuchi at is.kochi-u.ac.jp Thu Jun 21 03:35:28 2007 From: tkikuchi at is.kochi-u.ac.jp (Tokio Kikuchi) Date: Thu, 21 Jun 2007 10:35:28 +0900 Subject: [Mailman-Users] I lost my patch :-( In-Reply-To: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> References: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> Message-ID: <4679D5E0.2010005@is.kochi-u.ac.jp> > In my ?board_member? list, under ?Privacy options? (Sender filters). I > have: > > ?@members? in the box labeled ?List of non-member addresses whose postings > should be automatically accepted? http://sourceforge.net/tracker/index.php?func=detail&aid=1220144&group_id=103&atid=300103 From brad at shub-internet.org Thu Jun 21 05:45:57 2007 From: brad at shub-internet.org (Brad Knowles) Date: Wed, 20 Jun 2007 22:45:57 -0500 Subject: [Mailman-Users] lurker behaving strangely In-Reply-To: <9713998d0706201143oc677ffp44173e6e76e5ec82@mail.gmail.com> References: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> <9713998d0706201143oc677ffp44173e6e76e5ec82@mail.gmail.com> Message-ID: On 6/20/07, Jenny Hopkins wrote: > I'm sorry - I presumed lurker was a sort of add-on to mailman, and > thought I saw references to it as I went through the mailman archives. > (Googling for 'lurker' and anything to do with mailing lists or irc > tends to bring up the wrong references :-)) Well, it is an add-on. However, it's not included as part of the standard Mailman package that we provide, and there really aren't any official parts of Mailman that aren't included in that package. In this case, it's an add-on that is provided by some third party, which makes use of hooks that we do provide as part of the Mailman package. So, there isn't any problem with those hooks (so far as I can tell), which means that whatever problems you're having would appear to be contained solely within that third-party add-on. >> At the very least, it wouldn't hurt to check your cron jobs to make >> sure they're all in order. >> > > Thanks, Brad, I'll check this out. Good luck. Please do let us know how things turn out. We don't provide official support for third-party add-ons, but it can be useful for us to provide links to where people can get support, in case someone else in the future follows the same logic that you did. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Thu Jun 21 07:46:40 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 20 Jun 2007 22:46:40 -0700 Subject: [Mailman-Users] Troublesome Mailman Errors In-Reply-To: <000e01c7b369$f1171bf0$f3cb5f83@elysium> Message-ID: George Booth wrote: >There was indeed a very large digest.mbox for one of the lists (not for the >one we've been having issues with, though), so I removed the digest.mbox >(that list is set up to be used as a departmental email address, so there >are only 2 recipients on the list and they weren't digesting anyway), and >that removed the MemoryErrors I've been seeing. BTW, I should mention that >my version of Mailman is 2.1.5 > >However, now I'm getting different errors. When I restarted Mailman after >removing the digest.mbox file, the errors were: > Various errors and tracebacks snipped. In your OP you said >I've also come across a suggestion to add the line > " self.__conn.set_debuglevel(1)" to the SMTPDirect.py file and > restarted Mailman, but that hasn't seemed to help either. No, but if it is still there it will definitely cause multiple problems of the type you are seeing with your Python version (2.3.?) That suggestion is only applicable to Python 2.4 and above. See . >At this point, I'm at a loss. I've gone through the steps outline in the FAQ >entry "4.78. Troubleshooting: No mail going out to lists members", and all >seems well there. Only other thing I can think of is that under my >/var/mailman/locks directory, I have the following: > >[root at mail1 locks]# ls -al >total 8 >drwxrwsr-x 2 root mailman 4096 Jun 20 13:30 . >drwxrwsr-x 21 root mailman 4096 Jun 19 20:02 .. >-rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner >-rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 >master-qrunner.mail1.usm.edu.28475 >-rw-rw-r-- 1 mailman mailman 53 Jan 18 2006 >master-qrunner.mail.usm.edu.1757.1 >[root at mail1 locks]# > >I don't know if these are required or if I should delete them, or if they >even have anything whatsoever to do with the issue at hand. I did find it >odd that two of them seem to be dated as June 21, 2007, which is tomorrow >(assuming I read that correctly), although a check of the "date" command on >the server shows the correct date and time. I'm not sure about the date issue, but those are the mailmanctl locks that attempt to prevent you starting (not restarting) Mailman when it's already running. Those locks should be there and are not the cause of your problems. If you still have the self.__conn.set_debuglevel(1) in SMTPDirect.py, remove it, and then let us know if there are any errors/problems remaining. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alfrag at econ.soc.uoc.gr Thu Jun 21 10:25:16 2007 From: alfrag at econ.soc.uoc.gr (Alexandros Fragkiadakis) Date: Thu, 21 Jun 2007 11:25:16 +0300 (EEST) Subject: [Mailman-Users] backup lists Message-ID: <2044.147.52.239.225.1182414316.squirrel@147.52.239.224> hi all, sorry if this question has been asked before. How can i backup my lists and their configuration options? Regards, Alexandros -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From G.Booth at usm.edu Thu Jun 21 13:21:24 2007 From: G.Booth at usm.edu (George Booth) Date: Thu, 21 Jun 2007 06:21:24 -0500 Subject: [Mailman-Users] Troublesome Mailman Errors In-Reply-To: Message-ID: <000901c7b3f6$4d99f2d0$f3cb5f83@elysium> Mark, Removing that line indeed caused our listserv mail to flow once again. You are a genius! I still got a failure showing up in the /var/log/mailman/post log when when I tried sending a test message to the list that hasn't been delivering to everyone, but I'm just glad the mail is flowing again. :) And I guess Mailman is using the 2.3 installation of Python on our system; I did a search on Python to see which version we were using, and it appears we have both 2.3 and 2.6.16 installed (I'd thought maybe we were using the 2.6.16 until I saw the 2.3 version up there - I'll ask the server admins to verify that). I also did still see the smtp error in the /var/log/mailman/error log when I restarted Mailman after removing that line: Jun 21 05:48:11 2007 (28494) Cannot connect to SMTP server 131.95.82.161 on port smtp But since mail is flowing, I don't know if I should even concern myself over that or not. Anyway, thank you again! Next time I make it to San Francisco, I owe you a beer. :) Thanks, George Booth -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Thursday, June 21, 2007 12:47 AM To: George Booth; mailman-users at python.org Subject: Re: [Mailman-Users] Troublesome Mailman Errors George Booth wrote: >There was indeed a very large digest.mbox for one of the lists (not for the >one we've been having issues with, though), so I removed the digest.mbox >(that list is set up to be used as a departmental email address, so there >are only 2 recipients on the list and they weren't digesting anyway), and >that removed the MemoryErrors I've been seeing. BTW, I should mention that >my version of Mailman is 2.1.5 > >However, now I'm getting different errors. When I restarted Mailman after >removing the digest.mbox file, the errors were: > Various errors and tracebacks snipped. In your OP you said >I've also come across a suggestion to add the line > " self.__conn.set_debuglevel(1)" to the SMTPDirect.py file and > restarted Mailman, but that hasn't seemed to help either. No, but if it is still there it will definitely cause multiple problems of the type you are seeing with your Python version (2.3.?) That suggestion is only applicable to Python 2.4 and above. See . >At this point, I'm at a loss. I've gone through the steps outline in the FAQ >entry "4.78. Troubleshooting: No mail going out to lists members", and all >seems well there. Only other thing I can think of is that under my >/var/mailman/locks directory, I have the following: > >[root at mail1 locks]# ls -al >total 8 >drwxrwsr-x 2 root mailman 4096 Jun 20 13:30 . >drwxrwsr-x 21 root mailman 4096 Jun 19 20:02 .. >-rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 master-qrunner >-rw-rw-r-- 2 mailman mailman 53 Jun 21 2007 >master-qrunner.mail1.usm.edu.28475 >-rw-rw-r-- 1 mailman mailman 53 Jan 18 2006 >master-qrunner.mail.usm.edu.1757.1 >[root at mail1 locks]# > >I don't know if these are required or if I should delete them, or if they >even have anything whatsoever to do with the issue at hand. I did find it >odd that two of them seem to be dated as June 21, 2007, which is tomorrow >(assuming I read that correctly), although a check of the "date" command on >the server shows the correct date and time. I'm not sure about the date issue, but those are the mailmanctl locks that attempt to prevent you starting (not restarting) Mailman when it's already running. Those locks should be there and are not the cause of your problems. If you still have the self.__conn.set_debuglevel(1) in SMTPDirect.py, remove it, and then let us know if there are any errors/problems remaining. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jon.slater at mesanetworks.net Thu Jun 21 15:14:46 2007 From: jon.slater at mesanetworks.net (Jon Slater) Date: Thu, 21 Jun 2007 07:14:46 -0600 Subject: [Mailman-Users] spamd error message Message-ID: <005b01c7b406$23f1ef90$6bd5ceb0$@slater@mesanetworks.net> Hmmm? Everything *seems* to be working? But when I check my log files, I see: Jun 20 18:50:21 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 18:50:22 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 18:50:22 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 18:50:22 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 18:50:33 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 18:54:01 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 19:18:42 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 19:53:37 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 21:03:58 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 21:03:58 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 21:03:59 2007 (2903) spamd: could not connect to spamd on localhost Jun 20 21:16:22 2007 (2903) spamd: could not connect to spamd on localhost What?s wrong? Thanks! Jon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.9.1/857 - Release Date: 6/20/2007 2:18 PM From msapiro at value.net Thu Jun 21 16:40:41 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 07:40:41 -0700 Subject: [Mailman-Users] Troublesome Mailman Errors In-Reply-To: <000901c7b3f6$4d99f2d0$f3cb5f83@elysium> Message-ID: George Booth wrote: > >Removing that line indeed caused our listserv mail to flow once again. You >are a genius! I still got a failure showing up in the /var/log/mailman/post >log when when I tried sending a test message to the list that hasn't been >delivering to everyone, but I'm just glad the mail is flowing again. :) OK. That's good. Now we can get back to the original non-delivery problem. >And >I guess Mailman is using the 2.3 installation of Python on our system; The tracebacks in your posts showed Python library modules loaded from /usr/lib/python2.3 so that's the version Mailman is using. > I did >a search on Python to see which version we were using, and it appears we >have both 2.3 and 2.6.16 installed (I'd thought maybe we were using the >2.6.16 until I saw the 2.3 version up there - I'll ask the server admins to >verify that). I don't know what 2.6.16 would be. The latest Python is 2.5.1. >I also did still see the smtp error in the /var/log/mailman/error log when I >restarted Mailman after removing that line: > >Jun 21 05:48:11 2007 (28494) Cannot connect to SMTP server 131.95.82.161 on >port smtp > >But since mail is flowing, I don't know if I should even concern myself over >that or not. This is different. Last time you reported "Cannot connect to SMTP server localhost on port smtp". Did you add SMTPHOST = '131.95.82.161' to mm_cfg.py in the mean time. This message comes from OutgoingRunner when SMTPDirect.py is unable to connect to the server because of a Python library socket.error exception. It is only logged once, the first time it occurs after OutgoingRunner is (re)started. What do you see in Mailman's smtp and smtp-failure logs? There is something flakey between Mailman and the outgoing MTA. This is quite possibly the cause of your lost messages, but we need to see some more clues which may be in the smtp-failure log. It is puzzling because usually, a "Cannot connect" problem is a hard failure and no mail goes out at all. >Anyway, thank you again! Next time I make it to San Francisco, I owe you a >beer. :) I'll accept. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 21 16:44:30 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 07:44:30 -0700 Subject: [Mailman-Users] spamd error message In-Reply-To: <005b01c7b406$23f1ef90$6bd5ceb0$@slater@mesanetworks.net> Message-ID: Jon Slater wrote: >Hmmm Everything *seems* to be working > >But when I check my log files, I see: > >Jun 20 18:50:21 2007 (2903) spamd: could not connect to spamd on localhost In what log do you see this? Why do you think this is a Mailman issue? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From pdbogen at gmail.com Thu Jun 21 17:09:37 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 21 Jun 2007 10:09:37 -0500 Subject: [Mailman-Users] backup lists In-Reply-To: <2044.147.52.239.225.1182414316.squirrel@147.52.239.224> References: <2044.147.52.239.225.1182414316.squirrel@147.52.239.224> Message-ID: <6fbe3da00706210809y7ae1cdbbw178b568a3cebd322@mail.gmail.com> On 6/21/07, Alexandros Fragkiadakis wrote: > sorry if this question has been asked before. How can i backup my lists > and their configuration options? Searching the FAQ for 'backup' reveals FAQ 4.18 , "4.18. How do I backup my lists and their configurations/membership rosters?" -- - Patrick Bogen From msapiro at value.net Thu Jun 21 17:16:38 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 08:16:38 -0700 Subject: [Mailman-Users] Custom verify.txt has Wrong Content-Type In-Reply-To: Message-ID: Bryan Carbonnell wrote: >I have created a custom verify.txt for one of my lists, that is >bilingual, English & Chinese. > >It is in $PREFIX/lists//en > >It goes out just fine, but the MIME Content-Type is wrong for this >file to be read properly. It has a charset of us-ascii. > >Is there anyway to change it to utf-8 easily or do I need to change >the source code somewhere? This is not the normal way to handle a bilingual list. For discussion, I'm going to use 'zh-CN - Chinese (China)' but it could just as well be 'zh-TW - Chinese (Taiwan)', 'fr - French' or any other language for which there is a Mailman translation. First make sure that the desired language, Chinese (China) is checked in available_languages ont the Language options page in the admin interface. Then when a user requests subscription via the web, the user can specify Chinese (China) as their preferred language and they will receive the zh-CN version of verify.txt rather than the en version. You can still make a list specific template in english in $PREFIX/lists//en and chinese in $PREFIX/lists//zh-CN if the default template isn't suitable for the list. If you really want to make the english template bilingual and the charset utf-8, you can change the charset for english. In general, changing the charset can be problematic because the charset in which the language messages and templates are encoded may not be compatible with the new charset, but changing english to utf-8 should be OK as utf-8 is a superset of the default us-ascii. To make this specific change, put add_language('en', 'English (USA)', 'utf-8') in mm_cfg.py and restart Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From slc at publicus.net Thu Jun 21 18:32:37 2007 From: slc at publicus.net (Steven Clift) Date: Thu, 21 Jun 2007 11:32:37 -0500 Subject: [Mailman-Users] Feature comparison chart? Message-ID: <0a4601c7b421$c8e379e0$6600a8c0@publicus> Does anyone know of a feature comparison chart that compares Mailman to tools like: Sympa (open source) GroupServer (open source, zope-based) Listserv (commercial) YahooGroups (ad supported) GoogleGroups (ad supported) Thanks, Steven Clift . . . . . . . . . . . . . . . . . . Steven Clift - clift at publicus.net Web: http://publicus.net Blog: http://dowire.org/notes NGO: http://e-democracy.org Replies to slc@ may be missed. . . . . . . . . . . . . . . . . . . From carbonnb at gmail.com Thu Jun 21 20:05:02 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Thu, 21 Jun 2007 14:05:02 -0400 Subject: [Mailman-Users] Custom verify.txt has Wrong Content-Type In-Reply-To: References: Message-ID: On 6/21/07, Mark Sapiro wrote: > This is not the normal way to handle a bilingual list. For discussion, I know it's not the normal way to do things. I like to do things the hard way :) Actually I am trying to do away with access to the web interface altogether for the end users. I am just talking about e-mail MIME encoding only. > You can still make a list specific template in english in > $PREFIX/lists//en > and chinese in $PREFIX/lists//zh-CN if the default template > isn't suitable for the list. Which I have done, with the english templates, by making them bilingual. > If you really want to make the english template bilingual and the > charset utf-8, you can change the charset for english. In general, > changing the charset can be problematic because the charset in which > the language messages and templates are encoded may not be compatible > with the new charset, but changing english to utf-8 should be OK as > utf-8 is a superset of the default us-ascii. Hmmm, that hadn't occured to me. I may have to revisit this down the road then. > To make this specific change, put > > add_language('en', 'English (USA)', 'utf-8') > > in mm_cfg.py and restart Mailman. Thanks, -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From Aaron.Schubert at dhss.mo.gov Thu Jun 21 21:03:43 2007 From: Aaron.Schubert at dhss.mo.gov (Aaron Schubert) Date: Thu, 21 Jun 2007 14:03:43 -0500 Subject: [Mailman-Users] stat=unknown mailer error 2 Message-ID: <467A853A.AB84.001A.0@dhss.mo.gov> When sending an email message to a test list on our mailman list server I receive the following error in the sendmail maillog. Here is the maillog entry. Jun 21 13:55:50 listserv1 sendmail[4764]: l5LItoG2004763: to="|/usr/local/mailman/mail/mailman post unixtest", ctladdr= (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30989, dsn=5.3.0, stat=unknown mailer error 2 I am not sure what is happening but it looks like the error is when it tries to post. Does anyone know what the stat=unknown mailer error 2 means and how to correct it? Any help would be appreciated. From brianmaull at yahoo.com Thu Jun 21 21:14:38 2007 From: brianmaull at yahoo.com (Brian Maull) Date: Thu, 21 Jun 2007 12:14:38 -0700 (PDT) Subject: [Mailman-Users] Changed Firewall and Now Mailman is not working Message-ID: <293765.7317.qm@web53204.mail.re2.yahoo.com> Hello, We changed the firewall in our network and now our mailman installation is no longer working. From the server mailman is installed on I can access the internet just fine, so DNS and the default gateway are functioning. Is there anything in the mailman setup or in Red Hat 9 that I should check to see if it is pointing at my old firewall? Thanks, Brian From msapiro at value.net Fri Jun 22 00:07:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 15:07:59 -0700 Subject: [Mailman-Users] stat=unknown mailer error 2 In-Reply-To: <467A853A.AB84.001A.0@dhss.mo.gov> Message-ID: Aaron Schubert wrote: >When sending an email message to a test list on our mailman list server I receive the following error in the sendmail maillog. Here is the maillog entry. > >Jun 21 13:55:50 listserv1 sendmail[4764]: l5LItoG2004763: to="|/usr/local/mailman/mail/mailman post unixtest", ctladdr= (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30989, dsn=5.3.0, stat=unknown mailer error 2 > >I am not sure what is happening but it looks like the error is when it tries to post. Does anyone know what the stat=unknown mailer error 2 means and how to correct it? Any help would be appreciated. It means the /usr/local/mailman/mail/mailman wrapper exited with a "group mismatch" error. See for more generic info on this error and its correction. There is a more detailed error message that may not be in your MTA logs but should at least be in the DSN returned to the poster. This detailed message will tell you as what group the wrapper was invoked and what group was expected. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 22 00:15:34 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 15:15:34 -0700 Subject: [Mailman-Users] Changed Firewall and Now Mailman is not working In-Reply-To: <293765.7317.qm@web53204.mail.re2.yahoo.com> Message-ID: Brian Maull wrote: > We changed the firewall in our network and now our mailman installation is no longer working. From the server mailman is installed on I can access the internet just fine, so DNS and the default gateway are functioning. This says nothing about the DNS records for your server. It only says you can access DNS records for the internet names you try to access. It doesn't say that I can find proper DNS records to allow me to access you or send mail to you. >Is there anything in the mailman setup or in Red Hat 9 that I should check to see if it is pointing at my old firewall? What doesn't work? Can you access Mailman's web interface? Do post's bounce? If so, why? If not, do they reach Mailman's archives? Are they logged in Mailman's post log and smtp log. Is there anything in Mailman's smtp-failure log? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jonsson at mj1.mine.nu Fri Jun 22 00:14:32 2007 From: jonsson at mj1.mine.nu (mattias jonsson) Date: Fri, 22 Jun 2007 00:14:32 +0200 Subject: [Mailman-Users] Mailman for windows Message-ID: <000001c7b451$8b6018f0$0500a8c0@liomk23cfxd68z> Hm exist mailman for windows?? From msapiro at value.net Fri Jun 22 00:51:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 15:51:36 -0700 Subject: [Mailman-Users] Mailman for windows In-Reply-To: <000001c7b451$8b6018f0$0500a8c0@liomk23cfxd68z> Message-ID: mattias jonsson wrote: >Hm exist mailman for windows?? You can run Python, Mailman, an MTA and a web server under cygwin on Windows, but there are security and other issues that make this a poor choice for a production installation. See also and . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 22 00:58:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 15:58:47 -0700 Subject: [Mailman-Users] Changed Firewall and Now Mailman is not working In-Reply-To: <1728417820-1182465331-cardhu_decombobulator_blackberry.rim.net-502697269-@bxe106.bisx.prod.on.blackberry> Message-ID: brianmaull at yahoo.com wrote: > >Posts get to the mailman server, but don't make it to the archives, bounce, or go out to the list. It is not clear to me why posts are not getting to the archive. If everything worked before and the firewall is the only change and the posts reach Mailman, the should get to the archive even if they can't get sent out. Is there anything in Mailman's error log? >There is nothing in the smtp failure log, but there are errors in another log that say (Name service error for yahoo.ca: Host not found, try again). Which other log? See for some hints on this one. >I can ping yahoo.ca no problem from the server Can you connect to port 25 at yahoo.ca (something that your firewall may well be blocking). -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 22 01:15:55 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 21 Jun 2007 16:15:55 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: <0AFB8437-04DC-433B-A4CB-304DFF0E621B@earthlink.net> Message-ID: carconni wrote: > >Thank you, moving public out of the /var/mailman/archives/public >directory helped, now I can see my lists but I've lost my archives >and it doesn't seem to matter how many times or where I run /usr/ >share/mailman/bin/check_perms -f, I'm still getting these crazy >errors on various tasks: > >IOError: [Errno 2] No such file or directory: '/private/var/mailman/ >archives/private/ui.mbox/ui.mbox' So there is no '/private/var/mailman/archives/private/ui.mbox/ui.mbox' file. Did you move it? It should exist. >IOError: [Errno 2] No such file or directory: '/private/var/mailman/ >archives/private/blogsafety-requests.mbox/blogsafety-requests.mbox' Likewise '/private/var/mailman/archives/private/blogsafety-requests.mbox/blogsafety-requests.mbox'. >IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/tvguide-requests/index.html' What are the permissions on this path? They should be similar to [msapiro at sb7 var]$ ls -ld mailman drwxrwsr-x 19 root mailman 4096 Mar 3 21:02 mailman/ [msapiro at sb7 var]$ ls -ld mailman/archives drwxrwsr-x 4 root mailman 4096 Mar 21 2005 mailman/archives/ [msapiro at sb7 var]$ ls -ld mailman/archives/private drwxrws--x 74 root mailman 4096 May 4 09:30 mailman/archives/private/ [msapiro at sb7 var]$ ls -ld mailman/archives/private/gpc-test drwxrwsr-x 14 msapiro mailman 4096 Apr 4 03:27 mailman/archives/private/gpc-test/ [msapiro at sb7 var]$ ls -l mailman/archives/private/gpc-test/index.html -rw-rw-r-- 1 msapiro mailman 4899 Apr 3 08:56 mailman/archives/private/gpc-test/index.html The owner (root, msapiro) is not important, but the group should be mailman in every case. > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >in breaklink > os.unlink(link) >OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >archives/public/engineering' Is '/private/var/mailman/archives/public/engineering' a symlink to '/private/var/mailman/archives/private/engineering'? That's what it should be. What are the permissions on /private/var/mailman/archives/public? They should be similar to [msapiro at sb7 var]$ ls -ld mailman/archives/public drwxrwsr-x 2 root mailman 4096 May 4 09:30 mailman/archives/public/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From bgmahesh at gmail.com Fri Jun 22 08:13:43 2007 From: bgmahesh at gmail.com (BG Mahesh) Date: Fri, 22 Jun 2007 11:43:43 +0530 Subject: [Mailman-Users] Hosting multiple domains on the same mailman installation Message-ID: <5227ac5c0706212313r6d6a4818k893558295c57b57a@mail.gmail.com> hi Currently we are hosting lists.xyz.com using Mailman. Can I use the same installation to host lists.abc.com ? I don't want the mailing lists of lists.abc.com to have a return id of lists.xyz.com. i.e. I want to host the following mailing list on the only server I have which hosts mailman, users at lists.xyz.com members at lists.xyz.com charter at lists.abc.com etc at lists.abc.com Any help is appreciated -- -- B.G. Mahesh http://www.greynium.com/ http://www.oneindia.in/ http://www.click.in/ - Free Indian Classifieds From depstein at enr-corp.com Fri Jun 22 17:31:16 2007 From: depstein at enr-corp.com (David Epstein) Date: Fri, 22 Jun 2007 11:31:16 -0400 Subject: [Mailman-Users] Problem with Configuration Message-ID: I have been trying to get mailman to work on my box but unfortunately it refuses to work properly. While users can subscribe, when they send mail to the posting email address, they don't receive confirmation of the posting and the email isn't posted or sent to an administrator for confirmation. I'm probably missing or not understanding some random setting to get it to work properly. Any help would be appreciated! From dragon at crimson-dragon.com Fri Jun 22 17:51:54 2007 From: dragon at crimson-dragon.com (Dragon) Date: Fri, 22 Jun 2007 08:51:54 -0700 Subject: [Mailman-Users] Problem with Configuration In-Reply-To: References: Message-ID: <200706221548.l5MFm7wP031673@unreal.eroded.org> David Epstein wrote: >I have been trying to get mailman to work on my box but unfortunately it >refuses to work properly. While users can subscribe, when they send >mail to the posting email address, they don't receive confirmation of >the posting and the email isn't posted or sent to an administrator for >confirmation. I'm probably missing or not understanding some random >setting to get it to work properly. > > > >Any help would be appreciated! ---------------- End original message. --------------------- We are going to need more detail than that. Are the Qrunners running? (Do "ps aux | grep mailman" as root to find out) What is your MTA? Have you set up the aliases for the list(s) so your MTA knows how to route list traffic? What is in the mailman error, smtp and vette logs? Dragon ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From msapiro at value.net Fri Jun 22 17:57:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 22 Jun 2007 08:57:54 -0700 Subject: [Mailman-Users] Hosting multiple domains on the same mailmaninstallation In-Reply-To: <5227ac5c0706212313r6d6a4818k893558295c57b57a@mail.gmail.com> Message-ID: BG Mahesh wrote: > >Currently we are hosting lists.xyz.com using Mailman. Can I use the same >installation to host lists.abc.com ? >I don't want the mailing lists of lists.abc.com to have a return id of >lists.xyz.com. i.e. I want to host the following mailing list on the only >server I have which hosts mailman, > >users at lists.xyz.com >members at lists.xyz.com > >charter at lists.abc.com >etc at lists.abc.com Put add_virtualhost('www.abc.com', 'lists.abc.com') in mm_cfg.py where www.abc.com is the host name you use for web access for the abc.com domain. Currently (Mailman 2.1), you are restricted in that you can't have the same list name in both domains. You also need to configure your web server and MTA appropriately. See bin/newlist --help for info on creating lists in the abc.com domain. For web create, visiting the 'create' page on the www.abc.com host will create the list in that domain. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From root at home.9records.com Fri Jun 22 17:52:11 2007 From: root at home.9records.com (Gio MBG Canepa root) Date: Fri, 22 Jun 2007 17:52:11 +0200 Subject: [Mailman-Users] Mail from GioMBG > When I attempt to edit some user configuration I receive Internal Server Error (very strangerous! only on same user!) Message-ID: <200706221752.11798.root@home.9records.com> I All Mailman Staff! I have a strange error only when I attempt to modify some configurations on some mailman users... I can explane better: If I go here: http://home.9records.com/mailman/options/mailman/alkemy--at--mbg.it I can edit the user alkemy AT mbg.it but if I go here: http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com I receive an INTERNAL SERVER ERROR! NB] The alkexkenji user esist and is active like the first user alkemy! I have this error when I click on the link of the user and at the same the user have the same kind of error when attemp to modify Yours mailman configuration by self... Any suggestions? MANY Thanks! GioMBG -- Gi? "MBG" Canepa - E Mail: mbg a mbg.it Phone & Fax +39 0541 985 737 - Mobile +39 393 33 567 07 http://www.mbg.it | http://www.9Records.com Snail mail P.O. Box 59 / 47838 Riccione Italy From msapiro at value.net Fri Jun 22 19:13:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 22 Jun 2007 10:13:35 -0700 Subject: [Mailman-Users] Problem with Configuration In-Reply-To: <200706221548.l5MFm7wP031673@unreal.eroded.org> Message-ID: Dragon wrote: >David Epstein wrote: >>I have been trying to get mailman to work on my box but unfortunately it >>refuses to work properly. While users can subscribe, when they send >>mail to the posting email address, they don't receive confirmation of >>the posting and the email isn't posted or sent to an administrator for >>confirmation. I'm probably missing or not understanding some random >>setting to get it to work properly. >> >> >> >>Any help would be appreciated! >---------------- End original message. --------------------- > >We are going to need more detail than that. > >Are the Qrunners running? (Do "ps aux | grep mailman" as root to find out) > >What is your MTA? > >Have you set up the aliases for the list(s) so your MTA knows how to >route list traffic? > >What is in the mailman error, smtp and vette logs? See for a list of things to check. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 22 19:21:38 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 22 Jun 2007 10:21:38 -0700 Subject: [Mailman-Users] Mail from GioMBG > When I attempt to edit some userconfiguration I receive Internal Server Error (verystrangerous! only on same user!) In-Reply-To: <200706221752.11798.root@home.9records.com> Message-ID: Gio MBG Canepa root wrote: > >I have a strange error only when I attempt to modify some configurations on >some mailman users... I can explane better: >If I go here: >http://home.9records.com/mailman/options/mailman/alkemy--at--mbg.it >I can edit the user alkemy AT mbg.it >but if I go here: >http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com >I receive an INTERNAL SERVER ERROR! >NB] The alkexkenji user esist and is active like the first user alkemy! >I have this error when I click on the link of the user and at the same the >user have the same kind of error when attemp to modify Yours mailman >configuration by self... There is some corrupt data or other problem associated with the alexkenji--at--alexkenji.com user. There will be detailed error information in Mailman's 'error' log for these errors. This is the information we need to diagnose this problem. If you don't have access to this log, you need to work with the people who do. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ddjones at riddlemaster.org Sat Jun 23 04:22:29 2007 From: ddjones at riddlemaster.org (Daniel D Jones) Date: Fri, 22 Jun 2007 22:22:29 -0400 Subject: [Mailman-Users] Message failures Message-ID: <200706222222.30200.ddjones@riddlemaster.org> I'm having an issue with Mailman being unable to send messages through qmail. I'm not sure which one has the problem, so I'm sending to both lists. As soon as I figure out which program is at fault, I'll remove the other list from any replies. I'm running a Debian server with Mailman and qmail. We recent had a brief power outage. I shut the server down, then rebooted. When it came back up, I'd stopped receiving mail. I troubleshot and found out that something I'd installed on the server had evidently installed qpopper as a dependency. It was binding to port 110 before qmail's pop3d, so pop3d obviously wasn't working. I uninstalled qpopper and thought that I had everything fixed. However, either mailman is not working correctly or qmail isn't allowing mailman to work. Messages are coming into the list. I receive the messages in my mailbox, located on the same server. (Both my address and the list address are @riddlemaster.org addresses.) However, none of the other list members are receiving mail. Checking the mailman/post logs, I see a great deal of this: Jun 22 17:42:59 2007 (2503) post to listname from rvh40 at xxxxx.com, size=3715, message-id=<6019BB4F-A03B-4CD3-93BF-1B58FD917B49 at xxxxx.com>, 16 failures Jun 22 20:22:59 2007 (2503) post to listname from rex at yyyyy.com, size=1920, message-id=<20070623002827.GI4853 at yyyyy.com>, 16 failures Jun 22 21:15:55 2007 (13367) post to listname from ddjones at riddlemaster.org, size=1481, message-id=<200706222124.18534.ddjones at riddlemaster.org>, 16 failures (List members email addresses obscured.) There are 17 addresses subbed to the list, including mine. So it appears that my email address is succeeding but all of the rest are failing. I don't find any errors or related entries in any of the qmail logs. I can email members of the list directly, using qmail on the same server that hosts mailman. So mail is flowing through the system, both in and out. For some reason, however, it appears that mailman can't send messages outside my domain. Any hints or suggestions on how to troubleshoot this issue would be greatly appreciated. From msapiro at value.net Sat Jun 23 06:44:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 22 Jun 2007 21:44:35 -0700 Subject: [Mailman-Users] Message failures In-Reply-To: <200706222222.30200.ddjones@riddlemaster.org> Message-ID: Daniel D Jones wrote: > >Messages are coming into the list. I receive the messages in my mailbox, >located on the same server. (Both my address and the list address are >@riddlemaster.org addresses.) However, none of the other list members are >receiving mail. Checking the mailman/post logs, I see a great deal of this: > >Jun 22 17:42:59 2007 (2503) post to listname from rvh40 at xxxxx.com, size=3715, >message-id=<6019BB4F-A03B-4CD3-93BF-1B58FD917B49 at xxxxx.com>, 16 failures >Jun 22 20:22:59 2007 (2503) post to listname from rex at yyyyy.com, size=1920, >message-id=<20070623002827.GI4853 at yyyyy.com>, 16 failures >Jun 22 21:15:55 2007 (13367) post to listname from ddjones at riddlemaster.org, >size=1481, message-id=<200706222124.18534.ddjones at riddlemaster.org>, 16 >failures > >(List members email addresses obscured.) There are 17 addresses subbed to the >list, including mine. So it appears that my email address is succeeding but >all of the rest are failing. I don't find any errors or related entries in >any of the qmail logs. What is in Mailman's smtp-failure log? Since failures are reported to Mailman at SMTP time, I'd say qmail is not accepting the other 16 recipients. The smtp-failure log should give more detail on the reason. I don't know why qmail wouldn't log this somewhere too. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sat Jun 23 07:38:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 22 Jun 2007 22:38:36 -0700 Subject: [Mailman-Users] Mail from GioMBG > When I attempt to edit someuserconfiguration I receive Internal Server Error(verystrangerous! only on same user!) In-Reply-To: Message-ID: Mark Sapiro wrote: >Gio MBG Canepa root wrote: >> >>I have a strange error only when I attempt to modify some configurations on >>some mailman users... I can explane better: >>If I go here: >>http://home.9records.com/mailman/options/mailman/alkemy--at--mbg.it >>I can edit the user alkemy AT mbg.it >>but if I go here: >>http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com >>I receive an INTERNAL SERVER ERROR! >>NB] The alkexkenji user esist and is active like the first user alkemy! >>I have this error when I click on the link of the user and at the same the >>user have the same kind of error when attemp to modify Yours mailman >>configuration by self... > > >There is some corrupt data or other problem associated with the >alexkenji--at--alexkenji.com user. I still think this is correct, but >There will be detailed error information in Mailman's 'error' log for >these errors. This is the information we need to diagnose this problem. I misunderstood the error (I was thinking it was Mailman's 'we hit a bug' message, but it's not). There may or may not be anything in Mailman's error log about this. I still think it's likely, but not guaranteed. There will also probably be something in the apache error_log. It may or may not be more informative than "premature end of script headers". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From ddjones at riddlemaster.org Sat Jun 23 17:52:34 2007 From: ddjones at riddlemaster.org (Daniel D Jones) Date: Sat, 23 Jun 2007 11:52:34 -0400 Subject: [Mailman-Users] Message failures - solved In-Reply-To: <200706222222.30200.ddjones@riddlemaster.org> References: <200706222222.30200.ddjones@riddlemaster.org> Message-ID: <200706231152.34923.ddjones@riddlemaster.org> On Friday 22 June 2007 22:22, Daniel D Jones wrote: > I'm having an issue with Mailman being unable to send messages through > qmail. I'm not sure which one has the problem, so I'm sending to both > lists. As soon as I figure out which program is at fault, I'll remove the > other list from any replies. > > I'm running a Debian server with Mailman and qmail. We recent had a brief > power outage. I shut the server down, then rebooted. When it came back > up, I'd stopped receiving mail. I troubleshot and found out that > something I'd installed on the server had evidently installed qpopper as a > dependency. It was binding to port 110 before qmail's pop3d, so pop3d > obviously wasn't working. I uninstalled qpopper and thought that I had > everything fixed. However, either mailman is not working correctly or qmail > isn't allowing mailman to work. > > Messages are coming into the list. I receive the messages in my mailbox, > located on the same server. (Both my address and the list address are > @riddlemaster.org addresses.) However, none of the other list members are > receiving mail. Checking the mailman/post logs, I see a great deal of > this: > > Jun 22 17:42:59 2007 (2503) post to listname from rvh40 at xxxxx.com, > size=3715, message-id=<6019BB4F-A03B-4CD3-93BF-1B58FD917B49 at xxxxx.com>, 16 > failures Jun 22 20:22:59 2007 (2503) post to listname from rex at yyyyy.com, > size=1920, message-id=<20070623002827.GI4853 at yyyyy.com>, 16 failures > Jun 22 21:15:55 2007 (13367) post to listname from > ddjones at riddlemaster.org, size=1481, > message-id=<200706222124.18534.ddjones at riddlemaster.org>, 16 failures > > (List members email addresses obscured.) There are 17 addresses subbed to > the list, including mine. So it appears that my email address is > succeeding but all of the rest are failing. I don't find any errors or > related entries in any of the qmail logs. > > I can email members of the list directly, using qmail on the same server > that hosts mailman. So mail is flowing through the system, both in and > out. For some reason, however, it appears that mailman can't send messages > outside my domain. Any hints or suggestions on how to troubleshoot this > issue would be greatly appreciated. Follow up with the resolution for the sake of anyone searching the archives at a later date. The issue turned out to be with qmail, not mailman. I had the following line in my tcp.smtp.cdb file: 127:allow,RELAYCLIENT="" The correct line is: 127.:allow,RELAYCLIENT="" Notice the period after the 127. It tells qmail that the 127 is a wildcard. Without the period, it's taken as an exact match. This prevented any mail generated on the server from being sent outside the domain, but allowed mail coming from another authorized relay IP to get through. From puckett_chuck at hotmail.com Sat Jun 23 19:01:04 2007 From: puckett_chuck at hotmail.com (Chuck Puckett) Date: Sat, 23 Jun 2007 12:01:04 -0500 Subject: [Mailman-Users] announcements only: setting? Message-ID: I have a list I use for announcements only (no user posts). My provider just moved the list from one server to another, and did so by copying the list membership. Unfortunately, the new list just had default settings, and my list members all started getting lots of emails as replies were sent out to everybody, etc. [Even caused some unsubscribing, as members suddenly thought they were going to be flooded by emails]. I changed list_post_header to NO, and that stopped the rampant replies, etc. Also, the copier forgot to set me as mod on my entry in the list, so my apology emailed got bounced. I set my mod bit on, and resent the apology, but it doesn't seem to have gone out. At least neither I nor my wife received it. What exactly are the settings to make a list "announcements-only" and to make sure I can still post? Thanks Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) From brian at emwd.com Sat Jun 23 19:13:23 2007 From: brian at emwd.com (Brian Carpenter) Date: Sat, 23 Jun 2007 13:13:23 -0400 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: Message-ID: Hi Chris: I have some instructions regarding this topic that I provide my mailman hosting clients. You can access them at: http://www.emwd.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarti cleid=19 Kind regards, Brian Carpenter -------------------------------------- EMWD - Executive Officer -----Original Message----- From: mailman-users-bounces+brian=emwd.com at python.org [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of Chuck Puckett Sent: Saturday, June 23, 2007 1:01 PM To: mailman-users at python.org Subject: [Mailman-Users] announcements only: setting? I have a list I use for announcements only (no user posts). My provider just moved the list from one server to another, and did so by copying the list membership. Unfortunately, the new list just had default settings, and my list members all started getting lots of emails as replies were sent out to everybody, etc. [Even caused some unsubscribing, as members suddenly thought they were going to be flooded by emails]. I changed list_post_header to NO, and that stopped the rampant replies, etc. Also, the copier forgot to set me as mod on my entry in the list, so my apology emailed got bounced. I set my mod bit on, and resent the apology, but it doesn't seem to have gone out. At least neither I nor my wife received it. What exactly are the settings to make a list "announcements-only" and to make sure I can still post? Thanks Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) ------------------------------------------------------ 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/brian%40emwd.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From msapiro at value.net Sat Jun 23 19:58:12 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 23 Jun 2007 10:58:12 -0700 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: Message-ID: Chuck Puckett wrote > >I changed list_post_header to NO, and that stopped the rampant replies, etc. >Also, the copier forgot to set me as mod on my entry in the list, so my >apology emailed got bounced. I set my mod bit on, and resent the apology, >but it doesn't seem to have gone out. At least neither I nor my wife >received it. I'm confused. If anything, you would want moderation set Off for you, not On, and On for everyone else. >What exactly are the settings to make a list "announcements-only" and to >make sure I can still post? Thanks See for our suggestions. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From thezachflower at gmail.com Sat Jun 23 20:46:52 2007 From: thezachflower at gmail.com (thezachflower) Date: Sat, 23 Jun 2007 11:46:52 -0700 (PDT) Subject: [Mailman-Users] Max_Message_Size Question Message-ID: <11269104.post@talk.nabble.com> I'm administering a mailing list and the users require a max message size of over 15MB. Setting the value to 0 is really the same as setting it to 3MB, which does not work as every attachment sent is at least 7MB. I've also tried to set the value to 15MB on the web config and it still sets the max size as 3MB. This is extremely important for this mailing list to be useful at all, does anybody have any suggestions as to how I can fix this? Thanks, Zachary Flower -- View this message in context: http://www.nabble.com/Max_Message_Size-Question-tf3970162.html#a11269104 Sent from the Mailman - Users mailing list archive at Nabble.com. From msapiro at value.net Sat Jun 23 21:51:22 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 23 Jun 2007 12:51:22 -0700 Subject: [Mailman-Users] Max_Message_Size Question In-Reply-To: <11269104.post@talk.nabble.com> Message-ID: thezachflower wrote: > >I'm administering a mailing list and the users require a max message size of >over 15MB. Setting the value to 0 is really the same as setting it to 3MB, If that is the case, I'm guessing that the 3MB limit is in your MTA or somewhere else outside of Mailman. >which does not work as every attachment sent is at least 7MB. I've also >tried to set the value to 15MB on the web config and it still sets the max >size as 3MB. This is extremely important for this mailing list to be useful >at all, does anybody have any suggestions as to how I can fix this? Are the messages being held in Mailman with a reason like Message body is too big: nn bytes with a limit of nn KB or are they behing held for some other reason or is something entirely different happening? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From puckett_chuck at hotmail.com Sun Jun 24 03:40:08 2007 From: puckett_chuck at hotmail.com (Chuck Puckett) Date: Sat, 23 Jun 2007 20:40:08 -0500 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: References: Message-ID: It fails either way. Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Saturday, June 23, 2007 12:58 PM To: Chuck Puckett; mailman-users at python.org Subject: Re: [Mailman-Users] announcements only: setting? Chuck Puckett wrote > >I changed list_post_header to NO, and that stopped the rampant replies, etc. >Also, the copier forgot to set me as mod on my entry in the list, so my >apology emailed got bounced. I set my mod bit on, and resent the apology, >but it doesn't seem to have gone out. At least neither I nor my wife >received it. I'm confused. If anything, you would want moderation set Off for you, not On, and On for everyone else. >What exactly are the settings to make a list "announcements-only" and to >make sure I can still post? Thanks See for our suggestions. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Sun Jun 24 05:44:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 23 Jun 2007 20:44:54 -0700 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: References: Message-ID: <467DE8B6.3010100@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Puckett wrote: > It fails either way. and > But I have made it so that I am not-mod, everybody else is mod. I > understand that it is correct. Yes, but that's only part of it. Have you read the FAQ at and followed all the settings there? - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California Better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGfei2VVuXXpU7hpMRAmNuAJ9vVE6Y1zL+jp2IVkGb+di5stFJLQCfeZ81 NAOACnkyE9Y7fOF2Fw9VgCQ= =Oo/w -----END PGP SIGNATURE----- From puckett_chuck at hotmail.com Sun Jun 24 05:56:34 2007 From: puckett_chuck at hotmail.com (Chuck Puckett) Date: Sat, 23 Jun 2007 22:56:34 -0500 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: <467DE8B6.3010100@value.net> References: <467DE8B6.3010100@value.net> Message-ID: Yes. I had already followed those instructions. Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Saturday, June 23, 2007 10:45 PM To: Chuck Puckett Cc: mailman-users at python.org Subject: Re: [Mailman-Users] announcements only: setting? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Puckett wrote: > It fails either way. and > But I have made it so that I am not-mod, everybody else is mod. I > understand that it is correct. Yes, but that's only part of it. Have you read the FAQ at and followed all the settings there? - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California Better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGfei2VVuXXpU7hpMRAmNuAJ9vVE6Y1zL+jp2IVkGb+di5stFJLQCfeZ81 NAOACnkyE9Y7fOF2Fw9VgCQ= =Oo/w -----END PGP SIGNATURE----- From nick_airey at yahoo.com Sun Jun 24 06:00:28 2007 From: nick_airey at yahoo.com (Nick Airey) Date: Sat, 23 Jun 2007 21:00:28 -0700 (PDT) Subject: [Mailman-Users] mailman installation with DMZ Message-ID: <79865.88914.qm@web36814.mail.mud.yahoo.com> Hi Everyone, I would like some advice on the best way to set up a mailman installation in the presence of a DMZ, ie. I have a webserver in the DMZ which is accessible to the public. The MTA, however, is in the safe zone. The public needs access to the mailman web interface, implying that this should be run from the webserver in the DMZ. However the MTA in the safe zone needs to make a pipe connection to mailman, which (I assume) in turn needs access to the disk partition where the mailman files are stored. Hence mailman needs to be co-located with the MTA. As a quick fix: (a) I setup mailman and its web interface completely in the safe zone, and set the webserver in the DMZ to proxy URI "/mailman/*", to the internal webserver. This works, but I'm not sure if this is the ideal solution. I'm also not crazy about parts of an internal webserver being accessible to the internet. Other possibilities I considered were: (b) split the mailman installation, run the web part in the DMZ, accessing an NFS mounted disk on an internal machine. The MTA part of mailman running in the safe zone, can then access the same disk and process mail as normal. Worst case scenario, if the disk mount becomes unmounted (or otherwise unwritable), the web interface is unusable. However the MTA part (sending, receiving mails) still keeps working. (c) run mailman completely in the DMZ, and run a MTA on the DMZ, which can relay to the MTA in the safe zone for delivery. I don't really like this for a few reasons involving mail security and policy of running "minimalist" machines in the DMZ. Any thoughts would be much appreciated. I'm leaning towards switching to option (b), but I'm not sure exactly how to split the installation. I would also be willing to document this as a "best practice" for the mailman documentation. (I'm sure this question must come up all the time for fresh installations) Nick From msapiro at value.net Sun Jun 24 06:11:19 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 23 Jun 2007 21:11:19 -0700 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: References: <467DE8B6.3010100@value.net> Message-ID: <467DEEE7.7080303@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chuck Puckett wrote: > Yes. I had already followed those instructions. So what happens to the message you try to post? Is it held for some reason? Do you get anything back? If it just disappears into a black hole, try setting Privacy options...->Sender filters->generic_nonmember_action and Privacy options...->Sender filters->member_moderation_action to Hold or something other than Discard so you can see which if either of thes applies to your post. If you have access to Mailman's logs, look in the vette log too. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California Better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGfe7nVVuXXpU7hpMRAnvUAKD4IfRX/q9cML91xCT3U9pyVRmWiACeKt55 Zkg6louZCL/V79S0spo5+t0= =dzLe -----END PGP SIGNATURE----- From thezachflower at gmail.com Sun Jun 24 06:42:13 2007 From: thezachflower at gmail.com (Zachary Flower) Date: Sat, 23 Jun 2007 22:42:13 -0600 Subject: [Mailman-Users] Max_Message_Size Question In-Reply-To: References: Message-ID: <1182660133.2432.10.camel@sathure.keblesema.com> > >which does not work as every attachment sent is at least 7MB. I've also > >tried to set the value to 15MB on the web config and it still sets the max > >size as 3MB. This is extremely important for this mailing list to be useful > >at all, does anybody have any suggestions as to how I can fix this? > > > Are the messages being held in Mailman with a reason like > > Message body is too big: nn bytes with a limit of nn KB > > or are they behing held for some other reason or is something entirely > different happening? > The messages are actually being bounced back to the sender if they are over 3MB, which is also a problem. I would settle for the messages being held for moderator approval because at least they would get through, but as of now, they are being rejected completely. Zach From msapiro at value.net Sun Jun 24 06:54:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Sat, 23 Jun 2007 21:54:54 -0700 Subject: [Mailman-Users] Max_Message_Size Question In-Reply-To: <1182660133.2432.10.camel@sathure.keblesema.com> Message-ID: Zachary Flower wrote: >> >which does not work as every attachment sent is at least 7MB. I've also >> >tried to set the value to 15MB on the web config and it still sets the max >> >size as 3MB. This is extremely important for this mailing list to be useful >> >at all, does anybody have any suggestions as to how I can fix this? >> >> >> Are the messages being held in Mailman with a reason like >> >> Message body is too big: nn bytes with a limit of nn KB >> >> or are they behing held for some other reason or is something entirely >> different happening? >> > >The messages are actually being bounced back to the sender if they are >over 3MB, which is also a problem. I would settle for the messages being >held for moderator approval because at least they would get through, but >as of now, they are being rejected completely. And now I am even more certain that this is not a Mailman issue. I don't think the mail even reaches Mailman. I think it is being rejected by the incoming MTA. What does the bounce message look like? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From brad at shub-internet.org Sun Jun 24 06:56:43 2007 From: brad at shub-internet.org (Brad Knowles) Date: Sat, 23 Jun 2007 23:56:43 -0500 Subject: [Mailman-Users] mailman installation with DMZ In-Reply-To: <79865.88914.qm@web36814.mail.mud.yahoo.com> References: <79865.88914.qm@web36814.mail.mud.yahoo.com> Message-ID: On 6/23/07, Nick Airey wrote: > Any thoughts would be much appreciated. I'm leaning towards switching > to option (b), but I'm not sure exactly how to split the installation. The reality is that there is no one single "Best Practice" for this situation. What is Best Practice for your site might be considered totally unacceptable somewhere else. For example, the Mailman code is written in such a way as to be as robust as it can be in the face of whatever potential additional problems that using NFS might present. So, in theory, putting all of Mailman on NFS should "just work". But I know plenty of people who would run screaming in terror at the thought of running NFS in their DMZ. If that works for you, then you should be okay. But other sites might feel differently. My personal suggestion would be to have a minimal MTA+Mailman+web server on the machine in the DMZ, and tightly control the inputs and outputs from the machine in both directions, perhaps with a front-end web proxy that is appropriately secured, application-level gateway filter for the incoming and outgoing mail, etc.... But just because that's my personal preference doesn't necessarily make that a "Best Practice" that should be implemented everywhere -- other sites might prefer the NFS solution, or maybe something else. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Sun Jun 24 16:47:54 2007 From: msapiro at value.net (Mark Sapiro) Date: Sun, 24 Jun 2007 07:47:54 -0700 Subject: [Mailman-Users] announcements only: setting? In-Reply-To: Message-ID: Mark Sapiro wrote: >So what happens to the message you try to post? Is it held for some >reason? Do you get anything back? Chuck Puckett wrote: >I wonder if it's ever reaching mailman. The error message in the bounced >message is > >Reporting-MTA: dns;bay0-omc1-s24.bay0.hotmail.com >Received-From-MTA: dns;hotmail.com >Arrival-Date: Sat, 23 Jun 2007 21:01:50 -0700 > >Final-Recipient: rfc822;announcements at lists.puckettpublishing.com >Action: failed >Status: 5.5.0 >Diagnostic-Code: smtp;553 sorry, that domain isn't in my list of allowed >rcpthosts (#5.7.1) Yes, it isn't reaching Mailman. It appears to be a hotmail issue. It looks like hotmail won't deliver to the lists.puckettpublishing.com domain. I don't know why. There doesn't appear to be an MX DNS record for lists.puckettpublishing.com, but there is an A record so that should be OK. >I have a support request into my web host (www.hiwaay.net). It may help if they add an MX record to DNS for lists.puckettpublishing.com, but this may be something you have to pursue with hotmail. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alfrag at econ.soc.uoc.gr Mon Jun 25 08:58:05 2007 From: alfrag at econ.soc.uoc.gr (Alexandros Fragkiadakis) Date: Mon, 25 Jun 2007 09:58:05 +0300 (EEST) Subject: [Mailman-Users] Max_Message_Size Question In-Reply-To: <11269104.post@talk.nabble.com> References: <11269104.post@talk.nabble.com> Message-ID: <1427.147.52.239.225.1182754685.squirrel@147.52.239.224> On Sat, June 23, 2007 21:46, thezachflower wrote: > > I'm administering a mailing list and the users require a max message size > of over 15MB. Setting the value to 0 is really the same as setting it to > 3MB, > which does not work as every attachment sent is at least 7MB. I've also > tried to set the value to 15MB on the web config and it still sets the > max size as 3MB. This is extremely important for this mailing list to be > useful at all, does anybody have any suggestions as to how I can fix this? > > > Thanks, > Zachary Flower > -- > View this message in context: > http://www.nabble.com/Max_Message_Size-Question-tf3970162.html#a11269104 > Sent from the Mailman - Users mailing list archive at Nabble.com. > > > ------------------------------------------------------ Does your smtp server allow this size limit? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From jeffs at tolisgroup.com Mon Jun 25 18:33:23 2007 From: jeffs at tolisgroup.com (Jeff Shepherd) Date: Mon, 25 Jun 2007 09:33:23 -0700 Subject: [Mailman-Users] ACK Column... Message-ID: Hello, I was curious as to what the column "ack" was for under the Membership Management section. I've checked the Administrator Manual, but that section is empty, along with several other sections. What does that field mean and what's the difference between checked and unchecked users? Thanks for the help! -Jeff From dan at music.memphis.edu Mon Jun 25 18:40:15 2007 From: dan at music.memphis.edu (Dan Phillips) Date: Mon, 25 Jun 2007 11:40:15 -0500 Subject: [Mailman-Users] ACK Column... In-Reply-To: References: Message-ID: On Jun 25, 2007, at 11:33 AM, Jeff Shepherd wrote: > What does that field mean and what's the difference between checked > and unchecked users? It reflects the "Receive acknowledgement mail when you send mail to the list?" line from the user prefs page. If checked, the sender gets: "Your message entitled was successfully received by the mailing list." Dan From anne.ramey at ncmail.net Mon Jun 25 21:22:57 2007 From: anne.ramey at ncmail.net (Anne Ramey) Date: Mon, 25 Jun 2007 15:22:57 -0400 Subject: [Mailman-Users] archRunner hogging CPU Message-ID: <46801611.8050404@ncmail.net> It appears my archive runner is flipping out today. It is hogging the CPU and can't seem to keep up with the messages. I restarted mailman and it doesn't seem to have helped. It doesn't appear as if we are seeing any unusual traffic, so I can't think of what would cause this. It isn't completely stuck...it's processing messages, just really slowly and taking lots of CPU to do it. We are using Exim version 4.43 on RHEL 4 and mailman version 2.1.9rc1. Ideas? top - 15:15:49 up 152 days, 16:33, 5 users, load average: 1.25, 1.45, 1.49 Tasks: 153 total, 2 running, 150 sleeping, 1 stopped, 0 zombie Cpu(s): 25.0% us, 0.2% sy, 0.0% ni, 72.6% id, 2.2% wa, 0.0% hi, 0.0% si Mem: 4086484k total, 1987572k used, 2098912k free, 515092k buffers Swap: 2048276k total, 144k used, 2048132k free, 512688k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13486 mailman 25 0 233m 227m 2412 R 99.9 5.7 40:38.48 python 281 root 15 0 0 0 0 S 0.3 0.0 79:02.77 kjournald 13921 root 15 0 0 0 0 S 0.3 0.0 0:20.23 pdflush 13482 mailman 16 0 15328 9716 2372 S 0.3 0.2 0:06.15 python mailman 28270 1 0 Jun19 ? 00:00:00 /usr/bin/python /usr/local/bin/mailmanctl start mailman 13479 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13480 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13481 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13482 28270 0 14:34 ? 00:00:06 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13483 28270 0 14:34 ? 00:00:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13484 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s mailman 13485 28270 0 14:34 ? 00:00:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13486 28270 98 14:34 ? 00:42:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s Anne From brian at emwd.com Mon Jun 25 21:51:40 2007 From: brian at emwd.com (Brian Carpenter) Date: Mon, 25 Jun 2007 15:51:40 -0400 Subject: [Mailman-Users] archRunner hogging CPU In-Reply-To: <46801611.8050404@ncmail.net> Message-ID: Hi Anne: It doesn't seem your load is that high (1.49 15 minute avg.) and you have plenty of memory left. There isn't that many running processes (153) either. Is this a dedicated server used only for mailman or is this a shared hosting environment? According to your top output, your server should be keeping up fine with any messages being sent to mailman. Kind regards, Brian Carpenter -------------------------------------- EMWD - Executive Officer www.emwd.com -----Original Message----- From: mailman-users-bounces+brian=emwd.com at python.org [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of Anne Ramey Sent: Monday, June 25, 2007 3:23 PM To: mailman-users at python.org Subject: [Mailman-Users] archRunner hogging CPU It appears my archive runner is flipping out today. It is hogging the CPU and can't seem to keep up with the messages. I restarted mailman and it doesn't seem to have helped. It doesn't appear as if we are seeing any unusual traffic, so I can't think of what would cause this. It isn't completely stuck...it's processing messages, just really slowly and taking lots of CPU to do it. We are using Exim version 4.43 on RHEL 4 and mailman version 2.1.9rc1. Ideas? top - 15:15:49 up 152 days, 16:33, 5 users, load average: 1.25, 1.45, 1.49 Tasks: 153 total, 2 running, 150 sleeping, 1 stopped, 0 zombie Cpu(s): 25.0% us, 0.2% sy, 0.0% ni, 72.6% id, 2.2% wa, 0.0% hi, 0.0% si Mem: 4086484k total, 1987572k used, 2098912k free, 515092k buffers Swap: 2048276k total, 144k used, 2048132k free, 512688k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 13486 mailman 25 0 233m 227m 2412 R 99.9 5.7 40:38.48 python 281 root 15 0 0 0 0 S 0.3 0.0 79:02.77 kjournald 13921 root 15 0 0 0 0 S 0.3 0.0 0:20.23 pdflush 13482 mailman 16 0 15328 9716 2372 S 0.3 0.2 0:06.15 python mailman 28270 1 0 Jun19 ? 00:00:00 /usr/bin/python /usr/local/bin/mailmanctl start mailman 13479 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 13480 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 13481 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 13482 28270 0 14:34 ? 00:00:06 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 13483 28270 0 14:34 ? 00:00:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 13484 28270 0 14:34 ? 00:00:00 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s mailman 13485 28270 0 14:34 ? 00:00:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 13486 28270 98 14:34 ? 00:42:04 /usr/bin/python /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s Anne ------------------------------------------------------ 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/brian%40emwd.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp From anne.ramey at ncmail.net Mon Jun 25 22:23:04 2007 From: anne.ramey at ncmail.net (Anne Ramey) Date: Mon, 25 Jun 2007 16:23:04 -0400 Subject: [Mailman-Users] archRunner hogging CPU In-Reply-To: References: Message-ID: <46802428.8060404@ncmail.net> This is a dedicated server that does mailman and one low traffic web site. CPU load is usually ~0.05 or there abouts. I have never seen the archive runner taking up so much CPU. It's been doing it for hours. The other queues are running fine. Posted messages go out in a timely manner. It's just taking 15+ minutes to archive the messages. It's hogging the CPU and making other things I'm trying to do slower to respond, especially web site functions (including mailman's admin sites). Anne Brian Carpenter wrote: > Hi Anne: > > It doesn't seem your load is that high (1.49 15 minute avg.) and you have > plenty of memory left. There isn't that many running processes (153) either. > Is this a dedicated server used only for mailman or is this a shared hosting > environment? According to your top output, your server should be keeping up > fine with any messages being sent to mailman. > > Kind regards, > Brian Carpenter > -------------------------------------- > EMWD - Executive Officer > www.emwd.com > > > > -----Original Message----- > From: mailman-users-bounces+brian=emwd.com at python.org > [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of Anne > Ramey > Sent: Monday, June 25, 2007 3:23 PM > To: mailman-users at python.org > Subject: [Mailman-Users] archRunner hogging CPU > > > It appears my archive runner is flipping out today. It is hogging the > CPU and can't seem to keep up with the messages. I restarted mailman > and it doesn't seem to have helped. It doesn't appear as if we are > seeing any unusual traffic, so I can't think of what would cause this. > It isn't completely stuck...it's processing messages, just really slowly > and taking lots of CPU to do it. We are using Exim version 4.43 on RHEL > 4 and mailman version 2.1.9rc1. Ideas? > > top - 15:15:49 up 152 days, 16:33, 5 users, load average: 1.25, 1.45, 1.49 > Tasks: 153 total, 2 running, 150 sleeping, 1 stopped, 0 zombie > Cpu(s): 25.0% us, 0.2% sy, 0.0% ni, 72.6% id, 2.2% wa, 0.0% hi, 0.0% si > Mem: 4086484k total, 1987572k used, 2098912k free, 515092k buffers > Swap: 2048276k total, 144k used, 2048132k free, 512688k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 13486 mailman 25 0 233m 227m 2412 R 99.9 5.7 40:38.48 python > 281 root 15 0 0 0 0 S 0.3 0.0 79:02.77 kjournald > 13921 root 15 0 0 0 0 S 0.3 0.0 0:20.23 pdflush > 13482 mailman 16 0 15328 9716 2372 S 0.3 0.2 0:06.15 python > > > mailman 28270 1 0 Jun19 ? 00:00:00 /usr/bin/python > /usr/local/bin/mailmanctl start > mailman 13479 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s > mailman 13480 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s > mailman 13481 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s > mailman 13482 28270 0 14:34 ? 00:00:06 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s > mailman 13483 28270 0 14:34 ? 00:00:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s > mailman 13484 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s > mailman 13485 28270 0 14:34 ? 00:00:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s > mailman 13486 28270 98 14:34 ? 00:42:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s > > > Anne > ------------------------------------------------------ > 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/brian%40emwd.com > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > > > From anne.ramey at ncmail.net Mon Jun 25 22:54:23 2007 From: anne.ramey at ncmail.net (Anne Ramey) Date: Mon, 25 Jun 2007 16:54:23 -0400 Subject: [Mailman-Users] archRunner hogging CPU In-Reply-To: References: Message-ID: <46802B7F.1090804@ncmail.net> Continued digging lead me to FAQ 4.41....how recent is this. Does anyone else still run into this on the newer versions? I'll talk to some of my list owners and I can change the default, but I was wondering if I was chasing a false lead? (Another note, most of the lists are fewer than 100 members) Anne Brian Carpenter wrote: > Hi Anne: > > It doesn't seem your load is that high (1.49 15 minute avg.) and you have > plenty of memory left. There isn't that many running processes (153) either. > Is this a dedicated server used only for mailman or is this a shared hosting > environment? According to your top output, your server should be keeping up > fine with any messages being sent to mailman. > > Kind regards, > Brian Carpenter > -------------------------------------- > EMWD - Executive Officer > www.emwd.com > > > > -----Original Message----- > From: mailman-users-bounces+brian=emwd.com at python.org > [mailto:mailman-users-bounces+brian=emwd.com at python.org] On Behalf Of Anne > Ramey > Sent: Monday, June 25, 2007 3:23 PM > To: mailman-users at python.org > Subject: [Mailman-Users] archRunner hogging CPU > > > It appears my archive runner is flipping out today. It is hogging the > CPU and can't seem to keep up with the messages. I restarted mailman > and it doesn't seem to have helped. It doesn't appear as if we are > seeing any unusual traffic, so I can't think of what would cause this. > It isn't completely stuck...it's processing messages, just really slowly > and taking lots of CPU to do it. We are using Exim version 4.43 on RHEL > 4 and mailman version 2.1.9rc1. Ideas? > > top - 15:15:49 up 152 days, 16:33, 5 users, load average: 1.25, 1.45, 1.49 > Tasks: 153 total, 2 running, 150 sleeping, 1 stopped, 0 zombie > Cpu(s): 25.0% us, 0.2% sy, 0.0% ni, 72.6% id, 2.2% wa, 0.0% hi, 0.0% si > Mem: 4086484k total, 1987572k used, 2098912k free, 515092k buffers > Swap: 2048276k total, 144k used, 2048132k free, 512688k cached > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 13486 mailman 25 0 233m 227m 2412 R 99.9 5.7 40:38.48 python > 281 root 15 0 0 0 0 S 0.3 0.0 79:02.77 kjournald > 13921 root 15 0 0 0 0 S 0.3 0.0 0:20.23 pdflush > 13482 mailman 16 0 15328 9716 2372 S 0.3 0.2 0:06.15 python > > > mailman 28270 1 0 Jun19 ? 00:00:00 /usr/bin/python > /usr/local/bin/mailmanctl start > mailman 13479 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s > mailman 13480 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s > mailman 13481 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s > mailman 13482 28270 0 14:34 ? 00:00:06 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s > mailman 13483 28270 0 14:34 ? 00:00:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s > mailman 13484 28270 0 14:34 ? 00:00:00 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s > mailman 13485 28270 0 14:34 ? 00:00:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s > mailman 13486 28270 98 14:34 ? 00:42:04 /usr/bin/python > /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s > > > Anne > ------------------------------------------------------ > 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/brian%40emwd.com > > Security Policy: > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp > > > From msapiro at value.net Mon Jun 25 23:20:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Mon, 25 Jun 2007 14:20:36 -0700 Subject: [Mailman-Users] archRunner hogging CPU In-Reply-To: <46802B7F.1090804@ncmail.net> Message-ID: Anne Ramey wrote: >Continued digging lead me to FAQ 4.41....how recent is this. Not very. The FAQ article is about 3 years old, and the list archive thread it refers to regards a Mailman 2.0.11 installation >Does >anyone else still run into this on the newer versions? I'll talk to >some of my list owners and I can change the default, but I was wondering >if I was chasing a false lead? (Another note, most of the lists are >fewer than 100 members) You could try killing ArchRunner. If you 'kill -TERM' it, mailmanctl won't restart it. Then if things don't clear out, check for stale locks from the ArchRunner process. See . That chould get things goung normally, but the messages to be archived will start piling up in the qfiles/archive queue. Then you need to figure out what's wrong. Can you pinpoint a specific list? If so, you could just try rebuilding its archive with bin/arch --wipe and then restart ArchRunner with /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s or by stopping and starting mailmanctl (IIRC restart won't restart ArchRunner if it was SIGTERMed). Note that rebuilding the archive with bin/arch is not a step to be taken lightly as it MAY renumber messages and invalidate saved URLs, but if the issue is a corrupt archives/private//database/* file, there may be no choice. You may also wish to check the archives/private/.mbox/.mbox file with bin/cleanarch before running bin/arch. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From tron478 at googlemail.com Tue Jun 26 08:51:45 2007 From: tron478 at googlemail.com (TRON478) Date: Tue, 26 Jun 2007 08:51:45 +0200 Subject: [Mailman-Users] export list subscribers list Message-ID: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> hi, is it possible to export the subscribers list of a list to a text, csv or another file format? thats very important for me, but i couldnt find a function in the list administration interface. thanks yavuz From Ralf.Hildebrandt at charite.de Tue Jun 26 08:55:54 2007 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Tue, 26 Jun 2007 08:55:54 +0200 Subject: [Mailman-Users] export list subscribers list In-Reply-To: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> References: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> Message-ID: <20070626065554.GH9005@charite.de> * TRON478 : > hi, > > is it possible to export the subscribers list of a list to a text, csv or > another file format? You can, but not via the webinterface: ./list_members listenname -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt at charite.de Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk at charite.de From Hagedorn at uni-koeln.de Tue Jun 26 09:14:01 2007 From: Hagedorn at uni-koeln.de (Sebastian Hagedorn) Date: Tue, 26 Jun 2007 09:14:01 +0200 Subject: [Mailman-Users] export list subscribers list In-Reply-To: <20070626065554.GH9005@charite.de> References: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> <20070626065554.GH9005@charite.de> Message-ID: --On 26. Juni 2007 08:55:54 +0200 Ralf Hildebrandt wrote: >> is it possible to export the subscribers list of a list to a text, csv or >> another file format? > > You can, but not via the webinterface: > > ./list_members listenname That's a feature that many of our listowners ask for. Fortunately there's an alternative that doesn't require my help: the e-mail interface. You can get a list of subscribers by sending a mail to listname-request with the text who -- .:.Sebastian Hagedorn - RZKR-R1 (Geb?ude 52), Zimmer 18.:. Zentrum f?r angewandte Informatik - Universit?tsweiter Service RRZK .:.Universit?t zu K?ln / Cologne University - ? +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. From Ralf.Hildebrandt at charite.de Tue Jun 26 09:15:56 2007 From: Ralf.Hildebrandt at charite.de (Ralf Hildebrandt) Date: Tue, 26 Jun 2007 09:15:56 +0200 Subject: [Mailman-Users] export list subscribers list In-Reply-To: References: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> <20070626065554.GH9005@charite.de> Message-ID: <20070626071556.GN9005@charite.de> * Sebastian Hagedorn : > That's a feature that many of our listowners ask for. Fortunately there's > an alternative that doesn't require my help: the e-mail interface. You can > get a list of subscribers by sending a mail to listname-request with the > text > > who Ah, excellent. -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt at charite.de Charite - Universit?tsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to plonk at charite.de From tron478 at googlemail.com Tue Jun 26 08:50:13 2007 From: tron478 at googlemail.com (TRON478) Date: Tue, 26 Jun 2007 08:50:13 +0200 Subject: [Mailman-Users] Is it possible to reply to listname@lists... and not to listname-bounces@lists... Message-ID: <865f632b0706252350wc3989b5s53b13f76d923c72b@mail.gmail.com> Hello, when i get a mail from my mail i can reply to the list via the adress listname-bounces at lists.mailman.com but i want to reply via listname at lists.mailman.com is this possible? thanks yavuz From carbonnb at gmail.com Tue Jun 26 12:14:02 2007 From: carbonnb at gmail.com (Bryan Carbonnell) Date: Tue, 26 Jun 2007 06:14:02 -0400 Subject: [Mailman-Users] export list subscribers list In-Reply-To: References: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> <20070626065554.GH9005@charite.de> Message-ID: On 6/26/07, Sebastian Hagedorn wrote: > --On 26. Juni 2007 08:55:54 +0200 Ralf Hildebrandt > wrote: > > >> is it possible to export the subscribers list of a list to a text, csv or > >> another file format? > > > > You can, but not via the webinterface: > > > > ./list_members listenname > > That's a feature that many of our listowners ask for. Fortunately there's > an alternative that doesn't require my help: the e-mail interface. You can > get a list of subscribers by sending a mail to listname-request with the > text > > who But, IIRC, that won't give you the members that have set "Conceal yourself from subscriber list?" to Yes. -- Bryan Carbonnell - carbonnb at gmail.com Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting "What a great ride!" From mwelch at redwoodalliance.org Thu Jun 21 04:04:49 2007 From: mwelch at redwoodalliance.org (Michael Welch) Date: Wed, 20 Jun 2007 19:04:49 -0700 Subject: [Mailman-Users] I lost my patch :-( In-Reply-To: <4679D5E0.2010005@is.kochi-u.ac.jp> References: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> <4679D5E0.2010005@is.kochi-u.ac.jp> Message-ID: <20070626112005.818A41E4007@bag.python.org> This list's posts started showing up with all the line returns ignored. None of my other emails are showing up this way. Not sure when it started, I have been on vacation. But I noticed it earlier today and decided to start watching it. Am I the only one? Tokio Kikuchi wrote at 06:35 PM 06/20/2007: >> In my ?board_member? list, under ?Privacy options? (Sender filters). I > have: > > ?@members? in the box labeled ?List of non-member addresses whose postings > should be automatically accepted? http://sourceforge.net/tracker/index.php?func=detail&aid=1220144&group_id=103&atid=300103 ------------------------------------------------------ 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: - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 mwelch at redwoodalliance.org www.redwoodalliance.org From root at home.9records.com Tue Jun 26 17:10:04 2007 From: root at home.9records.com (Gio MBG Canepa root) Date: Tue, 26 Jun 2007 17:10:04 +0200 Subject: [Mailman-Users] mail from GioMBG > fresh installation of mailman but Internal Server Error (only on edit some users) remain! Message-ID: <200706261710.04830.root@home.9records.com> Hi Mark! ---| Here the apache error Log: |--- [Tue Jun 26 17:03:00 2007] [error] [client 127.0.0.1] ModSecurity: Access denied with code 500 (phase 1). Pattern match "\\\\.(?:c(?:o(?:nf(?:ig)?|m)| s(?:proj|r)?|dx|er|fg|md)|p(?:rinter|ass|db|ol|wd)|v(?:b(?:proj|s)?|sdisco)| a(?:s(?:ax?|cx)|xd)|s(?:html?|ql|tm|ys)|d(?:bf?|at|ll|os)|i(?:d[acq]|n[ci])| ba(?:[kt]|ckup)|res(?:ources|x)|l(?:icx|nk|og)|\\\\w{,5}~|webinfo|ht[rw]| xs ..." at REQUEST_BASENAME. [id "960035"] [msg "URL file extension is restricted by policy"] [severity "CRITICAL"] [hostname "home.9records.com"] [uri "/mailman/options/mailman/alexkenji--at--alexkenji.com"] [unique_id "bOj5IH8AAAEAAA6QRT4AAAAB"] ---| end httpd error log |--- These logs are generated in /var/log/httpd/error_log by trying access here: http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com PLUS I can write that I've removed all mailman and after I have reinstalled but... I HAVE THE SAME PROBLEM! Very strangerous! i have succesfull added the users and (for example) like in the old mailman installation If I go here: http://home.9records.com/mailman/options/mailman/alkemy--at--mbg.it I can edit the user alkemy AT mbg.it but if I go here: http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com I receive an INTERNAL SERVER ERROR! See on the start of this message to see the httpd error_log is possible that depend from cgi? if yes what I can control? waht I can do? many Thanks GioMBG Gio MBG Canepa root wrote: I have a strange error only when I attempt to modify some configurations on some mailman users... I can explane better: If I go here: http://home.9records.com/mailman/options/mailman/alkemy--at--mbg.it I can edit the user alkemy AT mbg.it but if I go here: http://home.9records.com/mailman/options/mailman/alexkenji--at--alexkenji.com I receive an INTERNAL SERVER ERROR! NB] The alkexkenji user esist and is active like the first user alkemy! I have this error when I click on the link of the user and at the same the user have the same kind of error when attemp to modify Yours mailman configuration by self... >There is some corrupt data or other problem associated with the >alexkenji--at--alexkenji.com user. I still think this is correct, but >There will be detailed error information in Mailman's 'error' log for >these errors. This is the information we need to diagnose this problem. I misunderstood the error (I was thinking it was Mailman's 'we hit a bug' message, but it's not). There may or may not be anything in Mailman's error log about this. I still think it's likely, but not guaranteed. There will also probably be something in the apache error_log. It may or may not be more informative than "premature end of script headers". -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From alberto.v.i.mail at gmail.com Tue Jun 26 17:27:28 2007 From: alberto.v.i.mail at gmail.com (Alberto V. I.) Date: Tue, 26 Jun 2007 17:27:28 +0200 Subject: [Mailman-Users] Problem with mailman and exim. Message-ID: <1182871648.13237.10.camel@alberto-laptop> Hi, I am new at this list. I have a problem with mailman and exim: I create mailman list and then I receive the notificacion to admin email, then I create anyother list without problems, beeing notified by mailman, but I cannot receive mails to list, If I send any mail to list, I obtain no result. I followed : /usr/share/doc/mailman/README.Exim4.Debian I did everything but/except : "and list all your Mailman domains in"POSTFIX_STYLE_VIRTUAL_DOMAINS". All the rest things are made, do I need to use virtual domains? Using mailman 2.1.9 and exim 4.63 under debian GNU/Linux. From anne.ramey at ncmail.net Tue Jun 26 17:44:43 2007 From: anne.ramey at ncmail.net (Anne Ramey) Date: Tue, 26 Jun 2007 11:44:43 -0400 Subject: [Mailman-Users] archRunner hogging CPU In-Reply-To: References: Message-ID: <4681346B.8050504@ncmail.net> Mark Sapiro wrote: > Anne Ramey wrote: > > >> Continued digging lead me to FAQ 4.41....how recent is this. >> > > > Not very. The FAQ article is about 3 years old, and the list archive > thread it refers to regards a Mailman 2.0.11 installation > > > >> Does >> anyone else still run into this on the newer versions? I'll talk to >> some of my list owners and I can change the default, but I was wondering >> if I was chasing a false lead? (Another note, most of the lists are >> fewer than 100 members) >> > > > You could try killing ArchRunner. If you 'kill -TERM' it, mailmanctl > won't restart it. > > Then if things don't clear out, check for stale locks from the > ArchRunner process. See > . > > That chould get things goung normally, but the messages to be archived > will start piling up in the qfiles/archive queue. > > Then you need to figure out what's wrong. Can you pinpoint a specific > list? If so, you could just try rebuilding its archive with > > bin/arch --wipe > > and then restart ArchRunner with > > /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s > > or by stopping and starting mailmanctl (IIRC restart won't restart > ArchRunner if it was SIGTERMed). > > Note that rebuilding the archive with bin/arch is not a step to be > taken lightly as it MAY renumber messages and invalidate saved URLs, > but if the issue is a corrupt archives/private//database/* > file, there may be no choice. > > You may also wish to check the > archives/private/.mbox/.mbox file with > bin/cleanarch before running bin/arch. > I did both, just to be safe. The two main offenders now have weekly archives and I used the above to rebuild the archives on the most high traffic list. Now the archiving qrunner is caught up, my load is back down and everything is great. Thanks so much, Anne From mwelch at redwoodalliance.org Tue Jun 26 17:55:40 2007 From: mwelch at redwoodalliance.org (Michael Welch) Date: Tue, 26 Jun 2007 08:55:40 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: <20070626112005.818A41E4007@bag.python.org> References: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> <4679D5E0.2010005@is.kochi-u.ac.jp> <20070626112005.818A41E4007@bag.python.org> Message-ID: <20070626161900.800BE1E4007@bag.python.org> Hi again. The problem seemed cured, now I am getting garbled posts again. Further, this post took a full 6 days to show up after I sent it. Maybe I am on moderation, and the moderator is slow at checking in. Or ?? Michael Welch wrote at 07:04 PM 06/20/2007: >This list's posts started showing up with all the line returns ignored. None of my other emails are showing up this way. Not sure when it started, I have been on vacation. But I noticed it earlier today and decided to start watching it. > >Am I the only one? - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 mwelch at redwoodalliance.org www.redwoodalliance.org From brad at shub-internet.org Tue Jun 26 18:20:33 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 26 Jun 2007 11:20:33 -0500 Subject: [Mailman-Users] Is it possible to reply to listname@lists... and not to listname-bounces@lists... In-Reply-To: <865f632b0706252350wc3989b5s53b13f76d923c72b@mail.gmail.com> References: <865f632b0706252350wc3989b5s53b13f76d923c72b@mail.gmail.com> Message-ID: On 6/26/07, TRON478 wrote: > when i get a mail from my mail i can reply to the list via the adress > > listname-bounces at lists.mailman.com > > but i want to reply via > > listname at lists.mailman.com > > is this possible? This is a client problem. There is nothing in Mailman that prevents you from replying to whatever address you want. What your client allows you to do, or makes easy for you to do, that's a completely different matter. If your client isn't letting you do what you want to do, you need to fix your client. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From brad at shub-internet.org Tue Jun 26 18:29:30 2007 From: brad at shub-internet.org (Brad Knowles) Date: Tue, 26 Jun 2007 11:29:30 -0500 Subject: [Mailman-Users] post formatting and timing In-Reply-To: <20070626161900.800BE1E4007@bag.python.org> References: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> <4679D5E0.2010005@is.kochi-u.ac.jp> <20070626112005.818A41E4007@bag.python.org> <20070626161900.800BE1E4007@bag.python.org> Message-ID: On 6/26/07, Michael Welch wrote: > Hi again. The problem seemed cured, now I am getting garbled posts again. > > Further, this post took a full 6 days to show up after I sent it. > > Maybe I am on moderation, and the moderator is slow at checking in. Or ?? Try checking your headers again: Received: from homepower.com (rickgermany.com [72.32.57.52]) by bag.python.org (Postfix) with ESMTP for ; Tue, 26 Jun 2007 13:20:00 +0200 (CEST) Received: from adsl-66-126-233-22.dsl.anhm01.pacbell.net [66.126.233.22] by homepower.com with SMTP; Wed, 20 Jun 2007 19:15:19 -0700 Whatever machine is running homepower.com, they delayed your mail, not us. Moreover, mailman-users is one of the very few mailman-* lists where new members are not moderated by default. Once you're subscribed, you should be able to post immediately. I can't speak to the other problems. -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From mwelch at redwoodalliance.org Tue Jun 26 18:42:26 2007 From: mwelch at redwoodalliance.org (Michael Welch) Date: Tue, 26 Jun 2007 09:42:26 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: References: <03fc01c7b38a$784476c0$68cd6440$@slater@mesanetworks.net> <4679D5E0.2010005@is.kochi-u.ac.jp> <20070626112005.818A41E4007@bag.python.org> <20070626161900.800BE1E4007@bag.python.org> Message-ID: <20070626164255.7C9C11E4007@bag.python.org> Thanks Brad & Dan for straightening me out. Kinda embarrassing, since I am a header watcher. Peace. Brad Knowles wrote at 09:29 AM 06/26/2007: >On 6/26/07, Michael Welch wrote: > >> Hi again. The problem seemed cured, now I am getting garbled posts again. >> >> Further, this post took a full 6 days to show up after I sent it. >> >> Maybe I am on moderation, and the moderator is slow at checking in. Or ?? > >Try checking your headers again: > > Received: from homepower.com (rickgermany.com [72.32.57.52]) > by bag.python.org (Postfix) with ESMTP > for ; Tue, 26 Jun 2007 > 13:20:00 +0200 (CEST) > Received: from adsl-66-126-233-22.dsl.anhm01.pacbell.net > [66.126.233.22] by homepower.com with SMTP; Wed, > 20 Jun 2007 19:15:19 -0700 > >Whatever machine is running homepower.com, they delayed your mail, not us. > >Moreover, mailman-users is one of the very few mailman-* lists where new members are not moderated by default. Once you're subscribed, you should be able to post immediately. > > >I can't speak to the other problems. > >-- >Brad Knowles , Consultant & Author >LinkedIn Profile: >Slides from Invited Talks: > >09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 mwelch at redwoodalliance.org www.redwoodalliance.org From jeffrey at goldmark.org Tue Jun 26 20:03:13 2007 From: jeffrey at goldmark.org (Jeffrey Goldberg) Date: Tue, 26 Jun 2007 13:03:13 -0500 Subject: [Mailman-Users] mail from GioMBG > fresh installation of mailman but Internal Server Error (only on edit some users) remain! In-Reply-To: <200706261710.04830.root@home.9records.com> References: <200706261710.04830.root@home.9records.com> Message-ID: <10FDCE53-66FF-49D7-A25F-4F5646DBDB33@goldmark.org> [mailed and posted] On Jun 26, 2007, at 10:10 AM, Gio MBG Canepa root wrote: > Hi Mark! > ---| Here the apache error Log: |--- > [Tue Jun 26 17:03:00 2007] [error] [client 127.0.0.1] ModSecurity: > Access > denied with code 500 (phase 1). Pattern match "\\\\.(?:c(?:o(?:nf > (?:ig)?|m)| > s(?:proj|r)?|dx|er|fg|md)|p(?:rinter|ass|db|ol|wd)|v(?:b(?:proj|s)?| > sdisco)| > a(?:s(?:ax?|cx)|xd)|s(?:html?|ql|tm|ys)|d(?:bf?|at|ll|os)|i(?:d > [acq]|n[ci])| > ba(?:[kt]|ckup)|res(?:ources|x)|l(?:icx|nk|og)|\\\\w{,5}~|webinfo|ht > [rw]| > xs ..." at REQUEST_BASENAME. [id "960035"] [msg "URL file extension is > restricted by policy"] [severity "CRITICAL"] [hostname "home. > 9records.com"] > [uri "/mailman/options/mailman/alexkenji--at--alexkenji.com"] That answers the question. Your apache add-on of mod_security is not allowing access to any URI ending with ".com". You may wish to disable mod_security for the mailman directory. I don't know how to do that, having never used mod_security (which isn't part of the normal apache distribution). Looking at the documentation at http://www.modsecurity.org/documentation/modsecurity-apache/2.1.0/ html-multipage/03-configuration-directives.html it looks like setting SecRuleEngine off within the appropriate or of your apache configuration should solve the problem. But keep in mind that this is the first time I've ever looked at mod_security, so don't put a great deal of trust in my suggestion. -j -- Jeffrey Goldberg http://www.goldmark.org/jeff/ From shuklapr at iitk.ac.in Tue Jun 26 22:14:18 2007 From: shuklapr at iitk.ac.in (shuklapr at iitk.ac.in) Date: Wed, 27 Jun 2007 01:44:18 +0530 (IST) Subject: [Mailman-Users] Mailman-Users Digest, Vol 40, Issue 41 In-Reply-To: References: Message-ID: <1166.172.26.93.215.1182888858.squirrel@newwebmail.iitk.ac.in> hey..pple.. me prat from india... can any one tell me wat is all you pple disscuss here.. i mean how it's important... i mean where it is used... i'll be really helpful to you.. thanks.. prat... > Send Mailman-Users mailing list submissions to > mailman-users at python.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://mail.python.org/mailman/listinfo/mailman-users > or, via email, send a message with subject or body 'help' to > mailman-users-request at python.org > > You can reach the person managing the list at > mailman-users-owner at python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Mailman-Users digest..." > Today's Topics: > > 1. Re: export list subscribers list (Bryan Carbonnell) > 2. Re: I lost my patch :-( (Michael Welch) > 3. mail from GioMBG > fresh installation of mailman but Internal > Server Error (only on edit some users) remain! (Gio MBG Canepa root) > 4. Problem with mailman and exim. (Alberto V. I.) > 5. Re: archRunner hogging CPU (Anne Ramey) > 6. Re: post formatting and timing (Michael Welch) > 7. Re: Is it possible to reply to listname at lists... and not to > listname-bounces at lists... (Brad Knowles) > 8. Re: post formatting and timing (Brad Knowles) > 9. Re: post formatting and timing (Michael Welch) > ------------------------------------------------------ > 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/ From msapiro at value.net Wed Jun 27 00:04:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 15:04:51 -0700 Subject: [Mailman-Users] export list subscribers list In-Reply-To: <865f632b0706252351n8684b45r71bf63c0f7a02e7e@mail.gmail.com> Message-ID: TRON478 wrote: > >is it possible to export the subscribers list of a list to a text, csv or >another file format? See . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 00:21:07 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 15:21:07 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: <20070626161900.800BE1E4007@bag.python.org> Message-ID: Michael Welch wrote: >Hi again. The problem seemed cured, now I am getting garbled posts again. Here's my guess about the 'missing' line returns. The original posts in the "I lost my patch :-(" thread were in charset utf-8 and were base64 encoded. So were a couple of the posts in today's "export list subscribers list" thread. My guess (I haven't actually looked at the raw decoded message) is that the decoded plain text has *nix only line endings as opposed to endings. This would not violate RFC 2821 as the data on the wire is the base64 encoded data, not the original text. I think the issue may be that your MUA doesn't recognize a single in the decoded text as a line break. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 00:26:40 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 15:26:40 -0700 Subject: [Mailman-Users] Is it possible to reply to listname@lists...and not to listname-bounces@lists... In-Reply-To: Message-ID: Brad Knowles wrote: >On 6/26/07, TRON478 wrote: > >> when i get a mail from my mail i can reply to the list via the adress >> >> listname-bounces at lists.mailman.com >> >> but i want to reply via >> >> listname at lists.mailman.com >> >> is this possible? > >This is a client problem. Agreed. See for some more information on this. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 01:52:42 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 16:52:42 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: Message-ID: Mark Sapiro wrote: > >My guess (I haven't actually looked at the raw decoded message) is that >the decoded plain text has *nix only line endings as opposed to > endings. This would not violate RFC 2821 as the data on the >wire is the base64 encoded data, not the original text. I have now looked, and in today's two base64 encoded posts in the "export list subscribers list" thread, the decoded message body does have text with only as a line ending. So, >I think the issue may be that your MUA doesn't recognize a single >in the decoded text as a line break. I don't know if there is a standard that says your MUA 'should' recognize a single in the decoded text as a line break, but of five MUA's I just tried, four - Ultrafunk Popcorn 1.76, Mozilla Thunderbird 2.0.0.4, MS Outlook Express 6 and Mutt 1.4.2.1i - all rendered in the decoded text as a line break. The fifth - Qualcomm Eudora 5.2 (very old) - didn't decode the base64 encoded text at all, it just displayed the raw base64 encoded data. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From root at home.9records.com Wed Jun 27 02:26:41 2007 From: root at home.9records.com (Gio MBG Canepa root) Date: Wed, 27 Jun 2007 02:26:41 +0200 Subject: [Mailman-Users] Mail from GioMBG > hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security Message-ID: <200706270226.41152.root@home.9records.com> MANY Thanks Jeffrey! SINCERLY! I have resolved with this hack into my: /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf Simply I have commented: SecRule REQUEST_BASENAME as # SecRule REQUEST_BASENAME I think that is the minor hack to prevent this kind of apache+mod_security+mailman error and to alowed the .shtml file extension in my html... YES You have just resolved not one but the 2 unique most bad problem into my newest monshine (fedora7)! MANY THANKs! GioMBG ---| hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security |--- # Restrict file extension # # TODO the list of file extensions below are virtually always considered unsafe # and not in use in any valid program. If your application uses one of # these extensions, please remove it from the list of blocked extensions. # You may need to use ModSecurity Core Rule Set Templates to do so, otherwise # comment the whole rule. # # SecRule REQUEST_BASENAME "\.(?:c(?:o(?:nf(?:ig)?|m)|s(?:proj|r)?|dx|er|fg|md)|p(?:rinter|ass|db|ol|wd)|v(?:b(?:proj|s)?|sdisco)|a(?:s(?:ax?|cx)|xd)|s(?:html?|ql|tm|ys)|d(?:bf?|at|ll|os)|i(?:d[acq]|n[ci])|ba(?:[kt]|ckup)|res(?:ources|x)|l(?:icx|nk|og)|\w{,5}~|webinfo|ht[rw]|xs[dx]|exe|key|mdb|old)$" \ "t:urlDecodeUni, t:lowercase, deny,log,auditlog,status:500,msg:'URL file extension is restricted by policy', severity:'2',id:'960035'" -- Gi? "MBG" Canepa - E Mail: mbg a mbg.it Phone & Fax +39 0541 985 737 - Mobile +39 393 33 567 07 http://www.mbg.it | http://www.9Records.com Snail mail P.O. Box 59 / 47838 Riccione Italy From ivanlan at pauahtun.org Wed Jun 27 02:39:18 2007 From: ivanlan at pauahtun.org (Ivan Van Laningham) Date: Tue, 26 Jun 2007 18:39:18 -0600 Subject: [Mailman-Users] post formatting and timing In-Reply-To: References: Message-ID: <4681B1B6.4020206@pauahtun.org> Hi All-- Mark Sapiro wrote: > > I don't know if there is a standard that says your MUA 'should' > recognize a single in the decoded text as a line break, but of > five MUA's I just tried, four - Ultrafunk Popcorn 1.76, Mozilla > Thunderbird 2.0.0.4, MS Outlook Express 6 and Mutt 1.4.2.1i - all > rendered in the decoded text as a line break. The fifth - > Qualcomm Eudora 5.2 (very old) - didn't decode the base64 encoded text > at all, it just displayed the raw base64 encoded data. > I think something else is going on, besides just the only line ending. I'm using two versions of T-Bird, 1.5 and 2.0 something, and both display the message concerned the same way, all crammed together on a single line. I think there must be some encoding issue. It probably is some configuration issue with T-Bird, but I've not been able to find it. Metta, Ivan -- Ivan Van Laningham God N Locomotive Works http://www.pauahtun.org/ http://www.python.org/workshops/1998-11/proceedings/papers/laningham/laningham.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours From l.h. at raqtweak.com Wed Jun 27 03:16:14 2007 From: l.h. at raqtweak.com (L. H.) Date: Wed, 27 Jun 2007 03:16:14 +0200 Subject: [Mailman-Users] Member only list? In-Reply-To: References: <671DC105EC01483CBC5FB4F5C5A6C561@WORKSTATION> Message-ID: <7C0C352F71F14C209C10F870CA34ECA4@WORKSTATION> Hi Mark / mailman user list, Hope you still remember me. Sorry, been VERY busy... Below is a brief summary of our previous exchange of mails. Beneath it are my finding whilst debugging some more... > >> What is the reason why the post is held? You will find the reason in > >> the admindb interface, in the notice to the admin and in Mailman's > >> vette log. > > > >It says, "dear moderator, the following message awaits your approval", or > >something like that... You know, the standard "moderator approval > request". > > And it also gives the subject of the post and the reason it was held > such as "post by non member", "implicit destination", "too big". or > some such. > > If you don't currently have the notice, you can find the held message > entries with reasons in Mailman's vette log. What are the reasons the > posts are held? 1) OPEN List Config settings: # Set misc settings generic_nonmember_action = 0 default_member_moderation = no subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 2) MEMBER posting only # Set misc settings default_member_moderation = no generic_nonmember_action = 2 subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 3) CLOSED (all posts req mod approval) # Set misc settings default_member_moderation = yes member_moderation_action = 1 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 Now, in ALL cases, I end up with an email like this: ============ Subject: Your message to 53-debuglist awaits moderator approval Your mail to '53-debuglist' with the subject hiya Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://www.test.com/mailman/confirm/53-debuglist/6a91ccdb4acaf7e5bd237e3059b 90d1439c8423d ============ (of course I did make member, etc. NO mail is sent to list admin! Only THIS mail is sent to the sender...) Furthermore, as you can see from the configs above, I am also trying to create 3 options for subscribing: Open (no approval of verification req, verification req, approval by mod required) However, in ALL cases, I get an email to confirm my address. NO mod approvals, no nothing. Also, in "open" mode (no verification), I DO get a verification request. I am working on the www.rackstar.net project. This used to have majordomo, which sucks. I am replacing it with mailman, which is a LOT better. However, I can NOT use the interface mailman offers for the above, because the rackstar interface has to do this. How I do it now is create a text file, and use config_list to generate the configuration. This must be possible... Right? Hope you have a solution for me. Thanks! Leslie From l.h. at raqtweak.com Wed Jun 27 03:29:00 2007 From: l.h. at raqtweak.com (L. H.) Date: Wed, 27 Jun 2007 03:29:00 +0200 Subject: [Mailman-Users] Member only list? In-Reply-To: <8DA2765A-2291-4E80-9038-A5F27FF7B8CE@music.memphis.edu> References: <671DC105EC01483CBC5FB4F5C5A6C561@WORKSTATION> <7C0C352F71F14C209C10F870CA34ECA4@WORKSTATION> <8DA2765A-2291-4E80-9038-A5F27FF7B8CE@music.memphis.edu> Message-ID: <08427EFAC8BA42619F24D7B697F8257C@WORKSTATION> Hi Dan, > > The reason it is being held: > > > > Message has implicit destination > > Have you read http://www.python.org/cgi-bin/faqw-mm.py? > req=show&file=faq01.009.htp > regarding this message? Thanks for this link. It is not an umbrella list (or am I mistaking umbrella for something else here? Please elaborate), and the domain is fine... Do you think if I enfore "require_explicit_destination = 0", it will work? From msapiro at value.net Wed Jun 27 03:52:32 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 18:52:32 -0700 Subject: [Mailman-Users] Member only list? In-Reply-To: <08427EFAC8BA42619F24D7B697F8257C@WORKSTATION> Message-ID: L. H. wrote apparently in response to an off list message: > >> > The reason it is being held: >> > >> > Message has implicit destination >> >> Have you read http://www.python.org/cgi-bin/faqw-mm.py? >> req=show&file=faq01.009.htp >> regarding this message? > >Thanks for this link. > >It is not an umbrella list (or am I mistaking umbrella for something else >here? Please elaborate), and the domain is fine... Reread item 2) (one sentence) in FAQ 1.9. The problem is the list is not explicitly addressed in the To: or Cc: headers of the post. >Do you think if I enfore "require_explicit_destination = 0", it will work? That is one way to avoid THIS hold. The other is to make sure that the post is actually explicitly addressed to the list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Wed Jun 27 04:22:05 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Wed, 27 Jun 2007 11:22:05 +0900 Subject: [Mailman-Users] post formatting and timing In-Reply-To: References: Message-ID: <877ipq3zn6.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > I don't know if there is a standard that says your MUA 'should' > recognize a single in the decoded text as a line break, Since it's in UTF-8, Unicode does, Technical Annex #14. Conformance is required by Unicode 4.0. Of course if the MUA doesn't claim conformance to Unicode there's no requirement, and AFAIK there's nothing in RFC 2822 or the MIME RFCs that requires conformance to any text standard beyond ASCII. However, most Unicode requirements are considered "best current practice". From l.h. at raqtweak.com Wed Jun 27 04:31:59 2007 From: l.h. at raqtweak.com (L. H.) Date: Wed, 27 Jun 2007 04:31:59 +0200 Subject: [Mailman-Users] Member only list? In-Reply-To: References: <08427EFAC8BA42619F24D7B697F8257C@WORKSTATION> Message-ID: <466C7E70671A47DCB0FDD204423FA631@WORKSTATION> > >> > The reason it is being held: > >> > > >> > Message has implicit destination > >> > >> Have you read http://www.python.org/cgi-bin/faqw-mm.py? > >> req=show&file=faq01.009.htp > >> regarding this message? > > Reread item 2) (one sentence) in FAQ 1.9. > > The problem is the list is not explicitly addressed in the To: or Cc: > headers of the post. Right! That was it. Since the rackstar system is designed for virtual hosting, I made it so each list gets a unique name. So that multiple sites can have a list called "info". Rackstar will internally name them 53-info and 69-info, etc. I did setup aliases to forward info at domain.com to 53-info at domain.com But, apparently, it did not take. How do I make it so it does take that? Next up: 1) OPEN List # Set misc settings generic_nonmember_action = 0 default_member_moderation = no subscribe_policy = 0 max_message_size = 50 reply_goes_to_list = 1 ---> NO verification required, but does need mod approval for subscribing ---> STILL requires mod approval of the message (non member) 3) CLOSED (all posts req mod approval) # Set misc settings default_member_moderation = yes member_moderation_action = 1 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 ---> MEMBER POSTS: Messages are PROCESSED, not held for approval. ---> NON MEMBER POST: Approval. So this is good. ---> MOD APPROVAL required for subscribing. Good. Etc etc. So I guess I am asking, (and god I've googled!!), how do I, using config_list, create the following scenario's 1) EVERYONE can post to the list. Members or non menmers 2) only members can post 3) any message, member or no member, requires mod approva. 4) anyone can sign up, no verification or approval required. 5) verification required, no approval required 6) verification + approval required I hope someone can help me out. I've been searching like crazy.... ;) From carconni at earthlink.net Wed Jun 27 05:21:26 2007 From: carconni at earthlink.net (carconni) Date: Tue, 26 Jun 2007 20:21:26 -0700 Subject: [Mailman-Users] moved lists and now they don't work Message-ID: <2A5A9F0D-21E5-4AD2-9EBB-2514B6654113@earthlink.net> Hi, I'm still having trouble... I removed everything in /private/var/mailman/archives/public/ but Mailman didn't replace the symlinks and when I tried to create the symlinks, Mailman got really confused. My lists are down and I don't know how to recover them. corp-admin2:/private/var/mailman/archives/public root# ls -l corp-admin2:/private/var/mailman/archives/public root# I've run check permissions dozen's of times: corp-admin2:/private/var/mailman/archives/public root# /usr/share/ mailman/bin/check_perms -f No problems found corp-admin2:/private/var/mailman/archives/public root# yet my error logs show permission errors. I've tried changing owners from mailman:mailman to root:mailman and back again - I've made directories world readable but I still get these errors... Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221 +37c9faaaa7ce90d565375941efb6b3a61c9ad826 Jun 26 19:13:28 2007 (10311) Archive file access failure: /private/var/mailman/archives/private/customer-us.mbox/ customer-us.mbox [Errno 13] Permission denied: '/private/var/mailman/ archives/private/customer-us.mbox/customer-us.mbox' corp-admin2:/private/var/mailman/archives/private root# cd customer-us corp-admin2:/private/var/mailman/archives/private/customer-us root# ls -l total 5200 drwxrwsr-x 8 root mailman 272 Jun 26 14:33 2007-June -rw-rw-r-- 1 root mailman 2654504 Jun 26 14:33 2007-June.txt drw-rw---- 2 root mailman 68 Jun 26 14:33 database -rw-rw-r-- 1 root mailman 479 Jun 18 13:30 index.html Jun 26 19:13:28 2007 (10311) Uncaught runner exception: [Errno 13] Permission denied: '/private/var/mailman/archives/private/customer- us.mbox/customer-us.mbox' Jun 26 19:13:28 2007 (10311) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 199, in ArchiveMail self.__archive_to_mbox(msg) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 168, in __archive_to_mbox mbox = self.__archive_file(afn) File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 156, in __archive_file return Mailbox.Mailbox(open(afn, 'a+')) IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/customer-us.mbox/customer-us.mbox' Jun 26 19:23:03 2007 (10314) SHUNTING: 1182910982.1765511 +4636bcd0509b8d4fc66200d2a26b32dc929f0e06 Jun 26 19:23:13 2007 (10314) Uncaught runner exception: [Errno 13] Permission denied: '/private/var/mailman/archives/private/ops' Jun 26 19:23:13 2007 (10314) Traceback (most recent call last): File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 352, in save_attachment makedirs(fsdir) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 339, in makedirs os.makedirs(dir, 02775) File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 154, in makedirs OSError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/ops' Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 +d396922f361992f9d2b65e96d4763591331f5010 drwxrwsr-x 9 root mailman 306 Jun 26 18:49 ops drwxrwsr-x 3 root mailman 102 Jun 18 13:30 ops.mbox corp-admin2:/private/var/mailman/archives/private/ops root# ls -l total 40 drwxrwxrwx 23 root mailman 782 Jun 18 13:30 2006-April -rwxrwxrwx 1 root mailman 6277 Jun 18 13:30 2006-April.txt -rwxrwxrwx 1 root mailman 1444 Jun 18 13:30 2006-April.txt.gz drwxrwxrwx 8 mailman mailman 272 Jun 25 18:53 attachments drwxrwxrwx 7 root mailman 238 Jun 18 13:30 database -rwxrwxrwx 1 root mailman 1040 Jun 18 13:30 index.html -rwxrwxrwx 1 root mailman 864 Jun 18 13:30 pipermail.pck Its funny, I was more worried about moving postfix and everyone's mailboxes....I thought mailman would be a piece of cake. If anyone understands what happening here - I'd really appreciate it. On Jun 18, 2007, at 10:08 PM, Mark Sapiro wrote: > carconni wrote: > >> >> I had to move lists. We had a hardware failure and they had to move >> to our new mail server. The mail server migration went fine and we >> thought mailman moved okay as well but we were wrong. >> >> Earlier today I tried to create a new list and and got an error so my >> boss said to check permissions. I ran the /usr/share/mailman/bin/ >> check_perms -f in every mailman file I could find but Im still >> getting permission errors. I even gave global permissions to all the >> archives but no luck. >> > > > It doesn't matter where your current directory is. You just run > > /usr/share/mailman/bin/check_perms -f > > as root until it reports no errors. > > > >> Right now, lists have stopped - they just aren't working and I just >> can't figure out what the problem is. The more we tried to fix it, >> the worse it got. Unfortunately my company heavily relies on them so >> I figured before I set out to manually configure mail aliases, does >> anyone know a way around this mess? >> >> from var/mailman/logs/error: (the permissions and ownership for the >> client-list is -rw-r--r-- 1 root mailman 479 Jun 18 13:30 / >> private/var/mailman/archives/private/client-list/index.html) >> > > > It should be group writable - i.e. -rw-rw-r-- 1 root mailman > > > >> Jun 18 19:24:34 2007 (10816) SHUNTING: 1182219873.5167899 >> +ceff885a98ff1c83a23f7e83b4d94678813ee808 >> Jun 18 19:25:36 2007 (10819) Uncaught runner exception: [Errno 1] >> Operation not permitted: '/private/var/mailman/archives/public/ >> client- >> list' >> Jun 18 19:25:36 2007 (10819) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >> 133, in _dispose >> mlist.Save() >> File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save >> self.CheckHTMLArchiveDir() >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >> in CheckHTMLArchiveDir >> breaklink(pubdir) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >> in breaklink >> os.unlink(link) >> OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >> archives/public/client-list' >> > > > I'm guessing when you backed up and moved from the old machines, you > wound up with files in /private/var/mailman/archives/public/ > > There should only be symlinks in that directory. Every > /private/var/mailman/archives/public/ and > /private/var/mailman/archives/public/ is a symlink to > the corresponding /private/var/mailman/archives/private/ and > /private/var/mailman/archives/private/ directory. > > Either fixing that or simply removing everything in the > /private/var/mailman/archives/public/ will allow Mailman to recreate > the proper symlinks. > > > >> Jun 18 19:25:36 2007 (10819) SHUNTING: 1182219935.3121431 >> +07ef8a32317dde697d0042ee151b8fd11d41b398 >> Jun 18 19:25:36 2007 (10816) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/client- >> list/ >> index.html' >> Jun 18 19:25:36 2007 (10816) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >> _dispose >> mlist.ArchiveMail(msg) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >> in ArchiveMail >> h.close() >> File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >> in close >> self.write_TOC() >> File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >> 1048, in write_TOC >> toc = open(os.path.join(self.basedir, 'index.html'), 'w') >> IOError: [Errno 13] Permission denied: '/private/var/mailman/ >> archives/ >> private/client-list/index.html' >> >> Jun 18 19:25:36 2007 (10816) SHUNTING: 1182219935.3121431 >> +1f5997710b510ce2af03c4b18e68bca2a9a7cf5d >> Jun 18 19:25:53 2007 (10819) Uncaught runner exception: [Errno 1] >> Operation not permitted: '/private/var/mailman/archives/public/ >> client- >> list' >> Jun 18 19:25:53 2007 (10819) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >> 133, in _dispose >> mlist.Save() >> File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save >> self.CheckHTMLArchiveDir() >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >> in CheckHTMLArchiveDir >> breaklink(pubdir) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >> in breaklink >> os.unlink(link) >> OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >> archives/public/client-list' >> >> Jun 18 19:25:53 2007 (10819) SHUNTING: 1182219952.298547 >> +a97ef5907aa7d67744b62971add1b089b4336b32 >> Jun 18 19:25:53 2007 (10816) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/client- >> list/ >> index.html' >> Jun 18 19:25:53 2007 (10816) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >> _dispose >> mlist.ArchiveMail(msg) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >> in ArchiveMail >> h.close() >> File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >> in close >> self.write_TOC() >> File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >> 1048, in write_TOC >> toc = open(os.path.join(self.basedir, 'index.html'), 'w') >> IOError: [Errno 13] Permission denied: '/private/var/mailman/ >> archives/ >> private/client-list/index.html' >> >> Jun 18 19:25:53 2007 (10816) SHUNTING: 1182219952.298547 >> +542a885011bac44ed8f869a06f7c64ebe07acaf9 >> Jun 18 19:27:07 2007 (10819) Uncaught runner exception: [Errno 1] >> Operation not permitted: '/private/var/mailman/archives/public/ >> client- >> list' >> Jun 18 19:27:07 2007 (10819) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >> 133, in _dispose >> mlist.Save() >> File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save >> self.CheckHTMLArchiveDir() >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235, >> in CheckHTMLArchiveDir >> breaklink(pubdir) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55, >> in breaklink >> os.unlink(link) >> OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ >> archives/public/client-list' >> >> Jun 18 19:27:07 2007 (10819) SHUNTING: 1182220026.5520279 >> +b4a5f31a903a595b30aad7c8b13e6b37e44b3b25 >> Jun 18 19:27:07 2007 (10816) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/client- >> list/ >> index.html' >> Jun 18 19:27:07 2007 (10816) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >> _dispose >> mlist.ArchiveMail(msg) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216, >> in ArchiveMail >> h.close() >> File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313, >> in close >> self.write_TOC() >> File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line >> 1048, in write_TOC >> toc = open(os.path.join(self.basedir, 'index.html'), 'w') >> IOError: [Errno 13] Permission denied: '/private/var/mailman/ >> archives/ >> private/client-list/index.html' >> >> Jun 18 19:27:07 2007 (10816) SHUNTING: 1182220026.5520279 >> +eddee6c8cd6b87769edeaa60fe9c23f1e3e19640 >> >> >> >> ------------------------------------------------------ >> 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/ >> msapiro%40value.net >> >> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? >> req=show&file=faq01.027.htp >> > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > From msapiro at value.net Wed Jun 27 05:35:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 20:35:35 -0700 Subject: [Mailman-Users] Member only list? In-Reply-To: <466C7E70671A47DCB0FDD204423FA631@WORKSTATION> Message-ID: L. H. wrote: >> >> The problem is the list is not explicitly addressed in the To: or Cc: >> headers of the post. > >Right! >That was it. Since the rackstar system is designed for virtual hosting, I >made it so each list gets a unique name. So that multiple sites can have a >list called "info". Rackstar will internally name them 53-info and 69-info, >etc. > >I did setup aliases to forward info at domain.com to 53-info at domain.com >But, apparently, it did not take. How do I make it so it does take that? The alias works to direct the envelope to the desired address, but it doesn't rewrite the contents of the To: header in the post. Your MTA may be able to do that or it may not. Given your situation, I think the easiest solution is to just set require_explicit_destination off. >Next up: >1) OPEN List ># Set misc settings >generic_nonmember_action = 0 >default_member_moderation = no >subscribe_policy = 0 >max_message_size = 50 >reply_goes_to_list = 1 > >---> NO verification required, but does need mod approval for subscribing >---> STILL requires mod approval of the message (non member) And what is the reason for which the message is held? >3) CLOSED (all posts req mod approval) ># Set misc settings >default_member_moderation = yes >member_moderation_action = 1 >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' >generic_nonmember_action = 1 >subscribe_policy = 2 >max_message_size = 50 >reply_goes_to_list = 1 > >---> MEMBER POSTS: Messages are PROCESSED, not held for approval. >---> NON MEMBER POST: Approval. So this is good. >---> MOD APPROVAL required for subscribing. Good. > > >Etc etc. > >So I guess I am asking, (and god I've googled!!), how do I, using >config_list, create the following scenario's > >1) EVERYONE can post to the list. Members or non menmers >2) only members can post >3) any message, member or no member, requires mod approva. This (1-3) was your question in the original post in this thread. The settings you indicated in that post (see, e.g. ) are appropriate for what you want. As we now see, there was a special circumstance in your installation which caused posts to be held for implicit destination. We can't anticipate all these things which is why when a post is unexpectedly held, we need to know the reason why it is being held. This reason is available in the 'your message is held for approval' notice to the poster, in the notice to the moderator, in the admindb interface and in Mailman's vette log. So for what reason is the post held? Tell us that, and we can tell you what to change. >4) anyone can sign up, no verification or approval required. >5) verification required, no approval required >6) verification + approval required 4-6 are tricky because they depend on the mm_cfg.py setting if any for ALLOW_OPEN_SUBSCRIBE. If you have ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py, the config_list settings for subscribe_policy for cases 4-6 are respectively 0, 1 and 3. If you don't have ALLOW_OPEN_SUBSCRIBE = Yes in mm_cfg.py, the settings for subscribe_policy for cases 5 and 6 are respectively 0 and 2, and case 4 cannot be set via subscribe_policy. Case 4 can be set via mlist.subscribe_policy = 0 -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 05:55:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 20:55:36 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: <2A5A9F0D-21E5-4AD2-9EBB-2514B6654113@earthlink.net> Message-ID: carconni wrote: > >I'm still having trouble... > >I removed everything in /private/var/mailman/archives/public/ but >Mailman didn't replace the symlinks and when I tried to create the >symlinks, Mailman got really confused. My lists are down and I don't >know how to recover them. > >corp-admin2:/private/var/mailman/archives/public root# ls -l >corp-admin2:/private/var/mailman/archives/public root# > > >I've run check permissions dozen's of times: > >corp-admin2:/private/var/mailman/archives/public root# /usr/share/ >mailman/bin/check_perms -f >No problems found >corp-admin2:/private/var/mailman/archives/public root# > >yet my error logs show permission errors. I've tried changing owners >from mailman:mailman to root:mailman and back again - I've made >directories world readable but I still get these errors... Are you running SeLinux or some other kind of security policy that is denying access? >Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221 >+37c9faaaa7ce90d565375941efb6b3a61c9ad826 >Jun 26 19:13:28 2007 (10311) Archive file access failure: > /private/var/mailman/archives/private/customer-us.mbox/ >customer-us.mbox [Errno 13] Permission denied: '/private/var/mailman/ >archives/private/customer-us.mbox/customer-us.mbox' > > corp-admin2:/private/var/mailman/archives/private root# cd customer-us And what if you cd customer-us.mbox ls -la > corp-admin2:/private/var/mailman/archives/private/customer-us root# >ls -l > total 5200 > drwxrwsr-x 8 root mailman 272 Jun 26 14:33 2007-June > -rw-rw-r-- 1 root mailman 2654504 Jun 26 14:33 2007-June.txt > drw-rw---- 2 root mailman 68 Jun 26 14:33 database > -rw-rw-r-- 1 root mailman 479 Jun 18 13:30 index.html > >Jun 26 19:13:28 2007 (10311) Uncaught runner exception: [Errno 13] >Permission denied: '/private/var/mailman/archives/private/customer- >us.mbox/customer-us.mbox' >Jun 26 19:13:28 2007 (10311) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >_dispose > mlist.ArchiveMail(msg) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 199, >in ArchiveMail > self.__archive_to_mbox(msg) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 168, >in __archive_to_mbox > mbox = self.__archive_file(afn) > File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 156, >in __archive_file > return Mailbox.Mailbox(open(afn, 'a+')) >IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/customer-us.mbox/customer-us.mbox' > > >Jun 26 19:23:03 2007 (10314) SHUNTING: 1182910982.1765511 >+4636bcd0509b8d4fc66200d2a26b32dc929f0e06 >Jun 26 19:23:13 2007 (10314) Uncaught runner exception: [Errno 13] >Permission denied: '/private/var/mailman/archives/private/ops' >Jun 26 19:23:13 2007 (10314) Traceback (most recent call last): > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >_oneloop > self._onefile(msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >_onefile > keepqueued = self._dispose(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >130, in _dispose > more = self._dopipeline(mlist, msg, msgdata, pipeline) > File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >153, in _dopipeline > sys.modules[modname].process(mlist, msg, msgdata) > File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 91, >in process > send_digests(mlist, mboxfp) > File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 132, >in send_digests > send_i18n_digests(mlist, mboxfp) > File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 306, >in send_i18n_digests > msg = scrubber(mlist, msg) > File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 227, >in process > url = save_attachment(mlist, part, dir, filter_html=False) > File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 352, >in save_attachment > makedirs(fsdir) > File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 339, >in makedirs > os.makedirs(dir, 02775) > File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >python2.3/os.py", line 153, in makedirs > File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >python2.3/os.py", line 153, in makedirs > File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >python2.3/os.py", line 153, in makedirs > File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >python2.3/os.py", line 154, in makedirs >OSError: [Errno 13] Permission denied: '/private/var/mailman/archives/ >private/ops' > >Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 >+d396922f361992f9d2b65e96d4763591331f5010 > > > drwxrwsr-x 9 root mailman 306 Jun 26 18:49 ops > drwxrwsr-x 3 root mailman 102 Jun 18 13:30 ops.mbox > > corp-admin2:/private/var/mailman/archives/private/ops root# ls -l > total 40 > drwxrwxrwx 23 root mailman 782 Jun 18 13:30 2006-April > -rwxrwxrwx 1 root mailman 6277 Jun 18 13:30 2006-April.txt > -rwxrwxrwx 1 root mailman 1444 Jun 18 13:30 2006-April.txt.gz > drwxrwxrwx 8 mailman mailman 272 Jun 25 18:53 attachments > drwxrwxrwx 7 root mailman 238 Jun 18 13:30 database > -rwxrwxrwx 1 root mailman 1040 Jun 18 13:30 index.html > -rwxrwxrwx 1 root mailman 864 Jun 18 13:30 pipermail.pck > >Its funny, I was more worried about moving postfix and everyone's >mailboxes....I thought mailman would be a piece of cake. If anyone >understands what happening here - I'd really appreciate it. Assuming the mailman group has sufficient permission on the whole path, I think it is likely some security policy that is denying access. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From carconni at earthlink.net Wed Jun 27 06:13:39 2007 From: carconni at earthlink.net (carconni) Date: Tue, 26 Jun 2007 21:13:39 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: References: Message-ID: <13990069-5A62-43D8-B526-6BC197337A13@earthlink.net> Hi, I know you guys aren't excited to hear this but it's running on an xserve. I think there may have been an error in how I was told to move mailman... does this look right? corp-admin2:/private/var/mailman/archives/private root# ls -la ops.mbox/ total 80 drwxrwsr-x 3 root mailman 102 Jun 18 13:30 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 37806 Jun 18 13:30 ops.mbox corp-admin2:/private/var/mailman/archives/private root# ls -la ops total 8 drwxrwsr-x 3 root mailman 102 Jun 26 19:56 . drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. -rw-rw-r-- 1 root mailman 1040 Jun 26 19:55 index.html On Jun 26, 2007, at 8:55 PM, Mark Sapiro wrote: > carconni wrote: >> >> I'm still having trouble... >> >> I removed everything in /private/var/mailman/archives/public/ but >> Mailman didn't replace the symlinks and when I tried to create the >> symlinks, Mailman got really confused. My lists are down and I don't >> know how to recover them. >> >> corp-admin2:/private/var/mailman/archives/public root# ls -l >> corp-admin2:/private/var/mailman/archives/public root# >> >> >> I've run check permissions dozen's of times: >> >> corp-admin2:/private/var/mailman/archives/public root# /usr/share/ >> mailman/bin/check_perms -f >> No problems found >> corp-admin2:/private/var/mailman/archives/public root# >> >> yet my error logs show permission errors. I've tried changing owners >> from mailman:mailman to root:mailman and back again - I've made >> directories world readable but I still get these errors... > > > Are you running SeLinux or some other kind of security policy that is > denying access? > > >> Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221 >> +37c9faaaa7ce90d565375941efb6b3a61c9ad826 >> Jun 26 19:13:28 2007 (10311) Archive file access failure: >> /private/var/mailman/archives/private/customer-us.mbox/ >> customer-us.mbox [Errno 13] Permission denied: '/private/var/mailman/ >> archives/private/customer-us.mbox/customer-us.mbox' >> >> corp-admin2:/private/var/mailman/archives/private root# cd >> customer-us > > > And what if you > > cd customer-us.mbox > ls -la > > >> corp-admin2:/private/var/mailman/archives/private/customer-us root# >> ls -l >> total 5200 >> drwxrwsr-x 8 root mailman 272 Jun 26 14:33 2007-June >> -rw-rw-r-- 1 root mailman 2654504 Jun 26 14:33 2007-June.txt >> drw-rw---- 2 root mailman 68 Jun 26 14:33 database >> -rw-rw-r-- 1 root mailman 479 Jun 18 13:30 index.html >> >> Jun 26 19:13:28 2007 (10311) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/customer- >> us.mbox/customer-us.mbox' >> Jun 26 19:13:28 2007 (10311) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in >> _dispose >> mlist.ArchiveMail(msg) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 199, >> in ArchiveMail >> self.__archive_to_mbox(msg) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 168, >> in __archive_to_mbox >> mbox = self.__archive_file(afn) >> File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 156, >> in __archive_file >> return Mailbox.Mailbox(open(afn, 'a+')) >> IOError: [Errno 13] Permission denied: '/private/var/mailman/ >> archives/ >> private/customer-us.mbox/customer-us.mbox' >> >> >> Jun 26 19:23:03 2007 (10314) SHUNTING: 1182910982.1765511 >> +4636bcd0509b8d4fc66200d2a26b32dc929f0e06 >> Jun 26 19:23:13 2007 (10314) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/ops' >> Jun 26 19:23:13 2007 (10314) Traceback (most recent call last): >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in >> _oneloop >> self._onefile(msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in >> _onefile >> keepqueued = self._dispose(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >> 130, in _dispose >> more = self._dopipeline(mlist, msg, msgdata, pipeline) >> File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line >> 153, in _dopipeline >> sys.modules[modname].process(mlist, msg, msgdata) >> File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 91, >> in process >> send_digests(mlist, mboxfp) >> File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 132, >> in send_digests >> send_i18n_digests(mlist, mboxfp) >> File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 306, >> in send_i18n_digests >> msg = scrubber(mlist, msg) >> File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 227, >> in process >> url = save_attachment(mlist, part, dir, filter_html=False) >> File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 352, >> in save_attachment >> makedirs(fsdir) >> File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 339, >> in makedirs >> os.makedirs(dir, 02775) >> File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >> python2.3/os.py", line 153, in makedirs >> File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >> python2.3/os.py", line 153, in makedirs >> File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >> python2.3/os.py", line 153, in makedirs >> File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ >> python2.3/os.py", line 154, in makedirs >> OSError: [Errno 13] Permission denied: '/private/var/mailman/ >> archives/ >> private/ops' >> >> Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 >> +d396922f361992f9d2b65e96d4763591331f5010 >> >> >> drwxrwsr-x 9 root mailman 306 Jun 26 18:49 ops >> drwxrwsr-x 3 root mailman 102 Jun 18 13:30 ops.mbox >> >> corp-admin2:/private/var/mailman/archives/private/ops root# ls -l >> total 40 >> drwxrwxrwx 23 root mailman 782 Jun 18 13:30 2006-April >> -rwxrwxrwx 1 root mailman 6277 Jun 18 13:30 2006-April.txt >> -rwxrwxrwx 1 root mailman 1444 Jun 18 13:30 2006- >> April.txt.gz >> drwxrwxrwx 8 mailman mailman 272 Jun 25 18:53 attachments >> drwxrwxrwx 7 root mailman 238 Jun 18 13:30 database >> -rwxrwxrwx 1 root mailman 1040 Jun 18 13:30 index.html >> -rwxrwxrwx 1 root mailman 864 Jun 18 13:30 pipermail.pck >> >> Its funny, I was more worried about moving postfix and everyone's >> mailboxes....I thought mailman would be a piece of cake. If anyone >> understands what happening here - I'd really appreciate it. > > > Assuming the mailman group has sufficient permission on the whole > path, > I think it is likely some security policy that is denying access. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From msapiro at value.net Wed Jun 27 06:50:59 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 21:50:59 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: <13990069-5A62-43D8-B526-6BC197337A13@earthlink.net> Message-ID: carconni wrote: > >I know you guys aren't excited to hear this but it's running on an >xserve. I think there may have been an error in how I was told to >move mailman... > >does this look right? > >corp-admin2:/private/var/mailman/archives/private root# ls -la ops.mbox/ >total 80 >drwxrwsr-x 3 root mailman 102 Jun 18 13:30 . >drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. This is the permission on /private/var/mailman/archives/private. You need g+sx. Also, in order for public archive access to work, you probably need o+x. If you look again at , you will see [msapiro at sb7 var]$ ls -ld mailman/archives/private drwxrws--x 74 root mailman 4096 May 4 09:30 mailman/archives/private/ -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 07:53:36 2007 From: msapiro at value.net (Mark Sapiro) Date: Tue, 26 Jun 2007 22:53:36 -0700 Subject: [Mailman-Users] moved lists and now they don't work In-Reply-To: Message-ID: Mark Sapiro wrote: >>drw-rw---- 736 root mailman 25024 Jun 26 19:55 .. > > >This is the permission on /private/var/mailman/archives/private. You >need g+sx. Also, in order for public archive access to work, you >probably need o+x. > >If you look again at >, >you will see > >[msapiro at sb7 var]$ ls -ld mailman/archives/private >drwxrws--x 74 root mailman 4096 May 4 09:30 mailman/archives/private/ It looks like there is a bug in check_perms. check_perms checks archives/private to be sure it isn't o+r and also warns if it is o+x although on most systems, it has to be for public archives to work, but check_perms doesn't check for any user or group permissions on archives/private nor does it even check to make sure it is o-w. Sorry for all the trouble. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Jesus.Olivan at uab.es Wed Jun 27 13:06:58 2007 From: Jesus.Olivan at uab.es (=?ISO-8859-1?Q?Jes=FAs_Oliv=E1n?=) Date: Wed, 27 Jun 2007 13:06:58 +0200 Subject: [Mailman-Users] rare problem Message-ID: <468244D2.60108@uab.es> Hi! i'm using mailman 2.1.5 on a Solaris box, and i've got a very rare issue... if i try to post a list using a non-suscribed email address, and this email address is included in non-suscribers allowed senders, it accepts my post... but if i use a regular expression like this ^[A-Za-z0-9.\-_%]+@[A-Za-z0-9.-]*mynet.com$ and try to post using a from line using more than 30 characters (from line splits in two in mail header then) and an accent. Then, mailman doesn't accept this mail and return it to me, although this email address is under my.net.com domain. Anyone can help, plz? =) From msapiro at value.net Wed Jun 27 16:06:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 07:06:03 -0700 Subject: [Mailman-Users] Member only list? In-Reply-To: <542AEC14194043CEAF9BBAF7A5F8E7F8@WORKSTATION> Message-ID: L. H. wrote: > >One minor thing. >This config: > ># Set misc settings >require_explicit_destination = 0 >default_member_moderation = 1 >member_moderation_action = 1 >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' >generic_nonmember_action = 1 > >Should make it so that mod approval for posts is required, for both member >and non member posts... > >NON member posts works. It requires mod approval. >MEMBER posts just get rejected. That's because the correspondence between values and actions for member_moderation_action is different than that for generic_nonmember_action. member_moderation_action has no 'accept' action because it doesn't make sense. Therefore, the values for member_moderation_action are 0==Hold, 1==Reject and 2==Discard. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Wed Jun 27 16:31:30 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 07:31:30 -0700 Subject: [Mailman-Users] rare problem In-Reply-To: <468244D2.60108@uab.es> Message-ID: Jes?s Oliv?n wrote: > >i'm using mailman 2.1.5 on a Solaris box, and i've got a very rare issue... > >if i try to post a list using a non-suscribed email address, and this >email address is included in non-suscribers allowed senders, it accepts >my post... but if i use a regular expression like this >^[A-Za-z0-9.\-_%]+@[A-Za-z0-9.-]*mynet.com$ and try to post using a from >line using more than 30 characters (from line splits in two in mail >header then) and an accent. Then, mailman doesn't accept this mail and >return it to me, although this email address is under my.net.com domain. First, while it is not the issue you are asking about, your regexp is probably more liberal than you want. I suggest something like ^[A-Za-z0-9.\-_%]+@([A-Za-z0-9.-]*\.)?mynet\.com$ to preclude matching things like user at xyz.aaamynet.com and user at host.mynetxcom As far as your question is concerned, the sender address is retrieved from the From: header using Python email library methods and functions. If there is a bug there, we'd have to see an exact copy of the split From: header to check that out. Also, when your MUA folds the from header into multiple lines, it should not be folding inside the email address. If by chance, it is, then it is your MUA that is at fault. In any case, I don't understand why this would affect only a regexp match and not a string match. The address that is being checked is the same in both cases. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jreddy at bnl.gov Wed Jun 27 19:57:29 2007 From: jreddy at bnl.gov (John Reddy) Date: Wed, 27 Jun 2007 13:57:29 -0400 Subject: [Mailman-Users] archive processing problem (mmarch w/ MIME) In-Reply-To: <46672875.1030608@bnl.gov> References: <46672875.1030608@bnl.gov> Message-ID: <4682A509.70603@bnl.gov> Just as a follow-up to this problem from earlier this month. Turns out the cause of this headache was related to a migration my group had performed. We built a completely new server for mailman. As part of the migration, the admin performing the move copied files from the old server to the new server by way of rsync. In the mix, /var/lib/mailman/pythonlib, which the debian package installs as a symlink to /usr/lib/mailman/pythonlib got erased by the rsync process. Without /var/lib/mailman/pythonlib available in the expected location, mmarch failed on any MIME encoding. Thanks to everyone who tried helping figure out the problem -John Reddy On 6/6/2007 5:34 PM John Reddy said the following: > I've checked the FAQ and Googled this before coming here to ask for > advice. Background: Running Debian 4.0, x86_64, MTA is Postfix, > packaged Debian Mailman (version listed "2.1.9-7"), Python version 2.4.4. > > I'm having a problem where the archives are not ingesting MIME email for > various mailing lists that I maintain. A message goes to the mailing > list, is processed properly and gets reflected to the recipients. All > email to the list winds up in > /var/lib/mailman/archives/private/listname.mbox/listname.mbox. However, > messages that have MIME encoding don't make it to > -- John Reddy jreddy at bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs From b19141 at britaine.ctd.anl.gov Wed Jun 27 20:52:29 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Wed, 27 Jun 2007 13:52:29 -0500 (CDT) Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line Message-ID: <200706271852.l5RIqTUn027506@britaine.ctd.anl.gov> I am running Mailman 2.1.9. I have a list where one posting has a "Subject:" line: Change in Procedure for Computers on list with possible Antivirus Problems The next posting in the thread has: Change in Procedure for Computers on list with possible AntivirusProblems A subsequent posting (not treated in the list archives as the same thread) has Change in Procedure for Computers on list with possibleAntivirusProblems The next posting in the thread has: Change in Procedure for Computers on list withpossibleAntivirusProblems The final posting in this thread has the same "Subject:" line as immediately above. I am not subscribed to this list and cannot post to it, so I do not know if a subsequent posting to this thread will remove another blank character in the "Subject:" line. What I see in the list mbox file are these lines (with line numbers): ------ 184232 Subject: Change in Procedure for Computers on list with possible Antivirus 184233 Problems ------ 184331 Subject: RE: Change in Procedure for Computers on list with possible 184332 AntivirusProblems ------ 184456 Subject: Re: Change in Procedure for Computers on list with 184457 possibleAntivirusProblems ------ 184566 Subject: RE: Change in Procedure for Computers on list 184567 withpossibleAntivirusProblems ------ 184735 Subject: RE: Change in Procedure for Computers on list 184736 withpossibleAntivirusProblems ------ Note that the original subject is split into two lines. What might be causing this? Is this a problem with Mailman, or is it a problem with the sender's Mail User Agent (probably Outlook), or a problem with the sender's mail system: X-MimeOLE: Produced By Microsoft Exchange V6.5 As the mbox file has the blanks removed, I have to believe that it is not Mailman that is removing the blanks. ---------------------------------------------------------------------- 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 douglas at music.columbia.edu Wed Jun 27 20:19:15 2007 From: douglas at music.columbia.edu (douglas repetto) Date: Wed, 27 Jun 2007 14:19:15 -0400 Subject: [Mailman-Users] no archives, no logs after system failure Message-ID: <4682AA23.8050806@music.columbia.edu> Hello, Our server recently had hard drive problems, and the system was copied to another drive where it seems to be more or less happy. But we're having a strange Mailman problem (Mailman 2.1.5 on OSX Server 10.4.10): the lists are running, mail is being delivered, but no archiving is taking place and nothing is being written to the log files. The last change date for all log files is the day the original drive died, as is the date of the last archived messages to our lists. Otherwise all seems to be well... Can someone help me with some ideas of where to start looking? I've run out of ideas at this point. Permissions seem to be fine. Nothing is in our system logs indicating a problem. I run: roar:/var/mailman/logs root# /usr/share/mailman/bin/mailmanctl stop Shutting down Mailman's master qrunner roar:/var/mailman root# /usr/share/mailman/bin/mailmanctl start Starting Mailman's master qrunner. With no problems, but as mentioned, the stop/start does not appear in the logs. Any ideas? thanks, douglas -- ............................................... http://artbots.org .....douglas.....irving........................ http://dorkbot.org .......................... http://music.columbia.edu/cmc/music-dsp .......... repetto....... http://works.music.columbia.edu/organism ............................... http://music.columbia.edu/~douglas From jeffrey at goldmark.org Wed Jun 27 22:10:13 2007 From: jeffrey at goldmark.org (Jeffrey Goldberg) Date: Wed, 27 Jun 2007 15:10:13 -0500 Subject: [Mailman-Users] Mail from GioMBG > hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security In-Reply-To: <200706270226.41152.root@home.9records.com> References: <200706270226.41152.root@home.9records.com> Message-ID: <40E653A3-BAD7-420C-8FC1-902E66280530@goldmark.org> On Jun 26, 2007, at 7:26 PM, Gio MBG Canepa root wrote: > MANY Thanks Jeffrey! > SINCERLY! > I have resolved with this hack into my: > /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf > Simply I have commented: > SecRule REQUEST_BASENAME > as > # SecRule REQUEST_BASENAME > I think that is the minor hack to prevent this kind of apache > +mod_security+mailman error and to alowed the .shtml file extension > in my html... > YES You have just resolved not one but the 2 unique most bad > problem into my newest monshine (fedora7)! > MANY THANKs! Thank you. I think that the lesson here is that any time you get an error from the webs erver, look at the error logs. Once you posted the logs as Mark requested, the answer to the problem was clear. But prior to seeing the log entry, nobody could have help. I'm pleased things are now working. Cheers, -j From mwelch at redwoodalliance.org Wed Jun 27 22:47:13 2007 From: mwelch at redwoodalliance.org (Michael Welch) Date: Wed, 27 Jun 2007 13:47:13 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: <877ipq3zn6.fsf@uwakimon.sk.tsukuba.ac.jp> References: <877ipq3zn6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <200706272119.l5RLJib6013897@nlpi029.prodigy.net> Hi everyone. Just as a followup, Katrina on the Eudora list I am on came up with a UTF-8 decoder plug-in. http://windharp.de/software/utf8iso.htm Stephen J. Turnbull wrote at 07:22 PM 06/26/2007: >Mark Sapiro writes: > > > I don't know if there is a standard that says your MUA 'should' > > recognize a single in the decoded text as a line break, > >Since it's in UTF-8, Unicode does, Technical Annex #14. Conformance >is required by Unicode 4.0. > >Of course if the MUA doesn't claim conformance to Unicode there's no >requirement, and AFAIK there's nothing in RFC 2822 or the MIME RFCs >that requires conformance to any text standard beyond ASCII. However, >most Unicode requirements are considered "best current practice". - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 mwelch at redwoodalliance.org www.redwoodalliance.org From hopkins.jenny at gmail.com Thu Jun 28 00:04:26 2007 From: hopkins.jenny at gmail.com (Jenny Hopkins) Date: Wed, 27 Jun 2007 23:04:26 +0100 Subject: [Mailman-Users] lurker behaving strangely In-Reply-To: References: <9713998d0706200517u322abceap1a52110f86d48c5e@mail.gmail.com> <9713998d0706200602v6c1c1161vbdf41bc7c4954665@mail.gmail.com> <9713998d0706201143oc677ffp44173e6e76e5ec82@mail.gmail.com> Message-ID: <9713998d0706271504m459e3bc2r452d066493ab2d1c@mail.gmail.com> On 21/06/07, Brad Knowles wrote: > Please do let us know how things turn out. We don't provide official > support for third-party add-ons, but it can be useful for us to > provide links to where people can get support, in case someone else > in the future follows the same logic that you did. > > -- As a follow-up to my problem with the lurker archives disappearing randomly: I found random mails were disappearing as they were being flagged as deleted in the lurker database, and each time I rebuilt the database from the mailman archives it would happen. I found a lurker-users list where it was suggested a web crawler could be triggering the delete action. I disabled the delete line in the lurker config and (touch wood) it has been stable for 3 days now. Many thanks for the suggestions. Jenny From douglas at music.columbia.edu Thu Jun 28 00:41:06 2007 From: douglas at music.columbia.edu (douglas repetto) Date: Wed, 27 Jun 2007 18:41:06 -0400 Subject: [Mailman-Users] no archives, no logs after system failure In-Reply-To: <4682AA23.8050806@music.columbia.edu> References: <4682AA23.8050806@music.columbia.edu> Message-ID: <4682E782.7030103@music.columbia.edu> Partially answering my own question: I've just realized that when the system was copied over some essential links were replaced by normal files. So I ended up with both a /private/var and a /var (normally on OSX server /var points to /private/var). So my logs/archives/etc are being stored in /private/var, rather than /var. For future reference I finally figures this out by running: lsof -u mailman which showed me that mailman was busy writing to long files on /private/var, as expected. But seeing the explicit path /private/var instead of the normal /var got me thinking, and lead me to the problem. best, douglas douglas repetto wrote: > Hello, > > Our server recently had hard drive problems, and the system was copied > to another drive where it seems to be more or less happy. > > But we're having a strange Mailman problem (Mailman 2.1.5 on OSX Server > 10.4.10): the lists are running, mail is being delivered, but no > archiving is taking place and nothing is being written to the log files. > The last change date for all log files is the day the original drive > died, as is the date of the last archived messages to our lists. > Otherwise all seems to be well... > > Can someone help me with some ideas of where to start looking? I've run > out of ideas at this point. Permissions seem to be fine. Nothing is in > our system logs indicating a problem. I run: > > roar:/var/mailman/logs root# /usr/share/mailman/bin/mailmanctl stop > Shutting down Mailman's master qrunner > roar:/var/mailman root# /usr/share/mailman/bin/mailmanctl start > Starting Mailman's master qrunner. > > With no problems, but as mentioned, the stop/start does not appear in > the logs. > > Any ideas? > > > thanks, > douglas > -- ............................................... http://artbots.org .....douglas.....irving........................ http://dorkbot.org .......................... http://music.columbia.edu/cmc/music-dsp .......... repetto....... http://works.music.columbia.edu/organism ............................... http://music.columbia.edu/~douglas From stephen at xemacs.org Thu Jun 28 03:12:33 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 28 Jun 2007 10:12:33 +0900 Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: <200706271852.l5RIqTUn027506@britaine.ctd.anl.gov> References: <200706271852.l5RIqTUn027506@britaine.ctd.anl.gov> Message-ID: <87ir983mri.fsf@uwakimon.sk.tsukuba.ac.jp> Barry Finkel writes: > I am running Mailman 2.1.9. I have a list where one posting has a > "Subject:" line: > > Change in Procedure for Computers on list with possible Antivirus Problems > > The next posting in the thread has: > > Change in Procedure for Computers on list with possible AntivirusProblems What is happening, I guess, is that Mailman is folding that header to keep it within some number of characters, maybe 76 or so. RFC 2822 specifies that this may be done by inserting a linebreak (CRLF) before whitespace. The RFC implies that the right thing to do in that case is to remove the CRLF only, but some MUAs also remove a space. I suspect that is what is happening to this case. Can you post a copy of the "raw" header as received by Mailman and as sent by Mailman? From msapiro at value.net Thu Jun 28 03:36:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 18:36:24 -0700 Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: <200706271852.l5RIqTUn027506@britaine.ctd.anl.gov> Message-ID: Barry Finkel wrote: >I am running Mailman 2.1.9. I have a list where one posting has a >"Subject:" line: > > Change in Procedure for Computers on list with possible Antivirus Problems > >The next posting in the thread has: > > Change in Procedure for Computers on list with possible AntivirusProblems > >A subsequent posting (not treated in the list archives as the same >thread) has > > Change in Procedure for Computers on list with possibleAntivirusProblems First of all, threading in Mailman's pipermail archive is not based on Subject: at all. It is based on In-Reply-To: and References: headers so if a reply is not added to the thread, it is because the replier's MUA didn't add an In-Reply-To: or References: header, or it added one or both of these referencing an off-list post not in the archive. The Subject: issue you observe has nothing to do with whether or not a reply is properly threaded in the archive. >The next posting in the thread has: > > Change in Procedure for Computers on list withpossibleAntivirusProblems > >The final posting in this thread has the same "Subject:" line as >immediately above. I am not subscribed to this list and cannot >post to it, so I do not know if a subsequent posting to this thread >will remove another blank character in the "Subject:" line. It may or may not. >What I see in the list mbox file are these lines (with line numbers): > >------ >184232 Subject: Change in Procedure for Computers on list with possible Antivirus >184233 Problems >------ >184331 Subject: RE: Change in Procedure for Computers on list with possible >184332 AntivirusProblems >------ >184456 Subject: Re: Change in Procedure for Computers on list with >184457 possibleAntivirusProblems >------ >184566 Subject: RE: Change in Procedure for Computers on list >184567 withpossibleAntivirusProblems >------ >184735 Subject: RE: Change in Procedure for Computers on list >184736 withpossibleAntivirusProblems >------ > >Note that the original subject is split into two lines. > >What might be causing this? Is this a problem with Mailman, or is it >a problem with the sender's Mail User Agent (probably Outlook), or >a problem with the sender's mail system: All of the above, or at least the first two. >As the mbox file has the blanks removed, I have to believe that >it is not Mailman that is removing the blanks. The basic issue revolves around the rules for folding and unfolding long header lines. The original standard was RFC 822 , sec 3.1.1. The current recommendation is RFC 2822 , sec 2.2.3. While careful reading of these two standards shows they are almost the same with respect to folding and exactly the same with respect to unfolding, the RFC 822 rules can result in the insertion of extra white space (the oposite of what you see here). Further, many MUAs and other mail processing software (such as the Python email library used by Mailman) don't follow the rules exactly, perhaps because in trying to compensate for too much white space they remove too much. Also, the rules really work best with structured headers where white space occurs between syntactic fields, and not so well with free form text headers like Subject:. Aside: I just read Stephen's reply in which he says "The RFC implies that the right thing to do in that case is to remove the CRLF only, but some MUAs also remove a space." And, I add "or a tab". This whitespace removal in unfolding is the crux of the issue. Part of the problem is Mailman will unfold and refold the header in the process of adding the subject_prefix. This process will lengthen the header, perhaps causing it to be folded when it wasn't before or folded in a different place. Also, Mailman tends to fold with and MUAs tend to remove the in unfolding. Also, If a subject is folded, and then the white space removed in unfolding, that makes the joined 'word' long so the next time it will tend to fold at the preceding the long 'word' and than that can be lost in unfolding. Mailman could behave in a completely RFC compliant manner (it doesn't), and there would still be the problem because MUAs don't behave in a completely compliant manner. Also note that the actual removal of whitespace is done by the MUA, not Mailman, but that doesn't let Mailman completely off the hook, because in some cases, Mailman may replace with and the MUA may be more likely to remove . See the (multiple) threads with subject "Subject Lines Wrapped After Commas, (Like This?)" starting at for a different but related discussion. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 28 05:13:29 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 20:13:29 -0700 Subject: [Mailman-Users] no archives, no logs after system failure In-Reply-To: <4682E782.7030103@music.columbia.edu> Message-ID: douglas repetto wrote: > >Partially answering my own question: I've just realized that when the >system was copied over some essential links were replaced by normal >files. So I ended up with both a /private/var and a /var (normally on >OSX server /var points to /private/var). So my logs/archives/etc are >being stored in /private/var, rather than /var. Partially or completely? I am unable to see an unresolved issue remaining. Is there one? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From douglas at music.columbia.edu Thu Jun 28 05:24:14 2007 From: douglas at music.columbia.edu (douglas repetto) Date: Wed, 27 Jun 2007 23:24:14 -0400 Subject: [Mailman-Users] no archives, no logs after system failure In-Reply-To: References: Message-ID: <468329DE.2080508@music.columbia.edu> Sorry, I should have said that the mailman part of the question is solved. Now I have to deal with a few other issues as a result, like the fact that some mail was lost (or is floating around somewhere in an imap database and doesn't want to come home)! It turned out to not be a Mailman problem at all. Thanks, douglas Mark Sapiro wrote: > douglas repetto wrote: >> Partially answering my own question: I've just realized that when the >> system was copied over some essential links were replaced by normal >> files. So I ended up with both a /private/var and a /var (normally on >> OSX server /var points to /private/var). So my logs/archives/etc are >> being stored in /private/var, rather than /var. > > > Partially or completely? I am unable to see an unresolved issue > remaining. Is there one? > -- ............................................... http://artbots.org .....douglas.....irving........................ http://dorkbot.org .......................... http://music.columbia.edu/cmc/music-dsp .......... repetto....... http://works.music.columbia.edu/organism ............................... http://music.columbia.edu/~douglas From mark at bradakis.com Thu Jun 28 05:24:42 2007 From: mark at bradakis.com (Mark J. Bradakis) Date: Wed, 27 Jun 2007 21:24:42 -0600 Subject: [Mailman-Users] Taboo body? Message-ID: <468329FA.2080409@bradakis.com> I've poked around a bit in various list related archives, but haven't found a definitive answer. Has anyone implemented some sort of add-on, filter or whatever to give mailman something like the majordomo 'global taboo body' rejection capability? All the predefined content filters seem to just pass or delete attachments, and not actually work on basic message body text. Will I have to just roll my own? mjb. From kaiser at bssnews.org Thu Jun 28 06:16:13 2007 From: kaiser at bssnews.org (Kaiser Ahmed) Date: Thu, 28 Jun 2007 10:16:13 +0600 Subject: [Mailman-Users] Need help very badly Message-ID: <019601c7b93b$10b45050$1f00a8c0@kaiser> Hi, I am a new user of mailman. I setup my server and tried to create a mailing list. The following massage occurred. I don't know how to solve it. Please suggest me the steps to be taken to solve this issue. Thanking you, Kaiser Ahmed System Engineer BSS, Dhaka. --------------------------------------------------------------------------- Bug in Mailman version 2.1.5 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/create.py", line 55, in main process_request(doc, cgidata) File "/usr/lib/mailman/Mailman/Cgi/create.py", line 187, in process_request mlist.Create(listname, owner, pw, langs, emailhost) File "/usr/lib/mailman/Mailman/MailList.py", line 457, in Create self.InitVars(name, admin, crypted_password) File "/usr/lib/mailman/Mailman/MailList.py", line 372, in InitVars baseclass.InitVars(self) File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/english_news.mbox' -------------------------------------------------------------------------------- Python information: Variable Value sys.version 2.3.4 (#1, Nov 4 2004, 14:06:56) [GCC 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------------------- Environment variables: Variable Value HTTP_REFERER http://mail.bssnews.org/mailman/create SERVER_SOFTWARE Apache/2.0.52 (Red Hat) SCRIPT_NAME /mailman/create SERVER_SIGNATURE Apache/2.0.52 (Red Hat) Server at mail.bssnews.org Port 80 REQUEST_METHOD POST SERVER_PROTOCOL HTTP/1.0 QUERY_STRING CONTENT_LENGTH 146 HTTP_CONNECTION keep-alive SERVER_NAME mail.bssnews.org REMOTE_ADDR 202.84.38.126 HTTP_VIA 1.1 gateway.bss-bd.com:8080 (squid/2.5.STABLE6) SERVER_PORT 80 SERVER_ADDR 202.84.38.126 DOCUMENT_ROOT /var/www/html PYTHONPATH /usr/lib/mailman SCRIPT_FILENAME /usr/lib/mailman/cgi-bin/create SERVER_ADMIN root at localhost HTTP_HOST mail.bssnews.org HTTP_CACHE_CONTROL no-cache, max-age=259200 REQUEST_URI /mailman/create 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, */* GATEWAY_INTERFACE CGI/1.1 HTTP_X_FORWARDED_FOR 192.168.0.31 REMOTE_PORT 51774 HTTP_ACCEPT_LANGUAGE en-us CONTENT_TYPE application/x-www-form-urlencoded HTTP_ACCEPT_ENCODING gzip, deflate From msapiro at value.net Thu Jun 28 06:50:03 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 21:50:03 -0700 Subject: [Mailman-Users] Need help very badly In-Reply-To: <019601c7b93b$10b45050$1f00a8c0@kaiser> Message-ID: Kaiser Ahmed wrote: > >I am a new user of mailman. I setup my server and tried to create a mailing list. The following massage occurred. I don't know how to solve it. Please suggest me the steps to be taken to solve this issue. >--------------------------------------------------------------------------- >Bug in Mailman version 2.1.5 > >We're sorry, we hit a bug! >If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! > >Traceback: > >Traceback (most recent call last): > File "/usr/lib/mailman/scripts/driver", line 87, in run_main > main() > File "/usr/lib/mailman/Mailman/Cgi/create.py", line 55, in main > process_request(doc, cgidata) > File "/usr/lib/mailman/Mailman/Cgi/create.py", line 187, in process_request > mlist.Create(listname, owner, pw, langs, emailhost) > File "/usr/lib/mailman/Mailman/MailList.py", line 457, in Create > self.InitVars(name, admin, crypted_password) > File "/usr/lib/mailman/Mailman/MailList.py", line 372, in InitVars > baseclass.InitVars(self) > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars > os.mkdir(self.archive_dir()+'.mbox', 02775) >OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/english_news.mbox' The mailman group is unable to create the /var/lib/mailman/archives/private/english_news.mbox' directory. The most likely cause of this is insufficient permission on the /var/lib/mailman/archives/private/' directory (There is a bug in check_perms so it doesn't catch this). The minimum permissions on the /var/lib/mailman/archives/private/' directory are 02770 and group mailman, although on most systems, the permissions need to be 02771 for public archives to work. -- 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 Jun 28 07:01:38 2007 From: brad at shub-internet.org (Brad Knowles) Date: Thu, 28 Jun 2007 00:01:38 -0500 Subject: [Mailman-Users] Taboo body? In-Reply-To: <468329FA.2080409@bradakis.com> References: <468329FA.2080409@bradakis.com> Message-ID: On 6/27/07, Mark J. Bradakis wrote: > I've poked around a bit in various list related archives, but haven't found > a definitive answer. Has anyone implemented some sort of add-on, filter > or whatever to give mailman something like the majordomo > 'global taboo body' rejection capability? All the predefined content > filters seem to just pass or delete attachments, and not actually work on > basic message body text. Will I have to just roll my own? The spam filters give you the ability to do full-blown Python regular expressions, and take any of various different actions on the message as a result -- reject, hold for moderation, discard, whatever. Is that not sufficient? -- Brad Knowles , Consultant & Author LinkedIn Profile: Slides from Invited Talks: 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 From msapiro at value.net Thu Jun 28 07:31:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Wed, 27 Jun 2007 22:31:27 -0700 Subject: [Mailman-Users] Taboo body? In-Reply-To: Message-ID: Brad Knowles wrote: >On 6/27/07, Mark J. Bradakis wrote: > >> I've poked around a bit in various list related archives, but haven't found >> a definitive answer. Has anyone implemented some sort of add-on, filter >> or whatever to give mailman something like the majordomo >> 'global taboo body' rejection capability? All the predefined content >> filters seem to just pass or delete attachments, and not actually work on >> basic message body text. Will I have to just roll my own? > >The spam filters give you the ability to do full-blown Python regular >expressions, and take any of various different actions on the message >as a result -- reject, hold for moderation, discard, whatever. > >Is that not sufficient? Probably not. He's asking if anyone has implemented the ability to match on the message body. The spam filters only match on the headers. Implementation of a custom handler to take action on a message based on pattern matches on the message body would not be difficult, but I don't know if anyone has done it. I have vague recollections of prior list posts about this, but it seems like Mark has searched the archives and not found anyone who has done it. A custom handler could emulate the code in SpamDetect.py, but walk the message parts and collect the payloads of the text parts instead of the part headers. See for information on implementing custom handlers. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From kaiser at bssnews.org Thu Jun 28 08:01:16 2007 From: kaiser at bssnews.org (Kaiser Ahmed) Date: Thu, 28 Jun 2007 12:01:16 +0600 Subject: [Mailman-Users] Need help very badly References: Message-ID: <027a01c7b949$bd5a2060$1f00a8c0@kaiser> Thanks a lot. I have done successfully by changing the permission of /var/lib/mailman/archives/private/ directory . Best regards, Kaiser ----- Original Message ----- From: "Mark Sapiro" To: "Kaiser Ahmed" ; Sent: Thursday, June 28, 2007 10:50 AM Subject: Re: [Mailman-Users] Need help very badly > Kaiser Ahmed wrote: > > > >I am a new user of mailman. I setup my server and tried to create a mailing list. The following massage occurred. I don't know how to solve it. Please suggest me the steps to be taken to solve this issue. > >--------------------------------------------------------------------------- > >Bug in Mailman version 2.1.5 > > > >We're sorry, we hit a bug! > >If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! > > > >Traceback: > > > >Traceback (most recent call last): > > File "/usr/lib/mailman/scripts/driver", line 87, in run_main > > main() > > File "/usr/lib/mailman/Mailman/Cgi/create.py", line 55, in main > > process_request(doc, cgidata) > > File "/usr/lib/mailman/Mailman/Cgi/create.py", line 187, in process_request > > mlist.Create(listname, owner, pw, langs, emailhost) > > File "/usr/lib/mailman/Mailman/MailList.py", line 457, in Create > > self.InitVars(name, admin, crypted_password) > > File "/usr/lib/mailman/Mailman/MailList.py", line 372, in InitVars > > baseclass.InitVars(self) > > File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars > > os.mkdir(self.archive_dir()+'.mbox', 02775) > >OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/english_news.mbox' > > > The mailman group is unable to create the > /var/lib/mailman/archives/private/english_news.mbox' directory. The > most likely cause of this is insufficient permission on the > /var/lib/mailman/archives/private/' directory (There is a bug in > check_perms so it doesn't catch this). > > The minimum permissions on the /var/lib/mailman/archives/private/' > directory are 02770 and group mailman, although on most systems, the > permissions need to be 02771 for public archives to work. > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > From stephen at xemacs.org Thu Jun 28 11:45:25 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 28 Jun 2007 18:45:25 +0900 Subject: [Mailman-Users] Taboo body? In-Reply-To: References: Message-ID: <87fy4c2z0q.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > Implementation of a custom handler to take action on a message based on > pattern matches on the message body would not be difficult, but I > don't know if anyone has done it. If you need something that's somewhat automatically extensible, the SpamBayes package is written in Python, and might be a very time-saving addition. I wonder if maybe Skip hasn't already done this? Also, remember that if possible you'd really like to stop this stuff at the MTA, and not permit it as far as Mailman. Of course, your rules for the lists may be stricter than for personal mail, or differ by list, etc, which would change the balance of judgment here. From barry at python.org Thu Jun 28 13:35:00 2007 From: barry at python.org (Barry Warsaw) Date: Thu, 28 Jun 2007 07:35:00 -0400 Subject: [Mailman-Users] Taboo body? In-Reply-To: <87fy4c2z0q.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87fy4c2z0q.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <3C5ACAD3-EB5E-4265-8663-D673349774DD@python.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Jun 28, 2007, at 5:45 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > >> Implementation of a custom handler to take action on a message >> based on >> pattern matches on the message body would not be difficult, but I >> don't know if anyone has done it. > > If you need something that's somewhat automatically extensible, the > SpamBayes package is written in Python, and might be a very > time-saving addition. I wonder if maybe Skip hasn't already done > this? There are some really old patches laying around somewhere (on SF perhaps?) that did a prototype integration of Spambayes and Mailman, hooking Mailman's moderation page to Spambayes training. It would probably need a fair bit of work to update, but it might serve as a good starting point. IIRC, the actual handler code wasn't very big. - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iQCVAwUBRoOc5XEjvBPtnXfVAQLknQP/b/MB/ZwaSoaDUXiCqmiwuLJdrQBSVNJD NDIUQTOaIMqmVwS7k0aMwsps0M6BGXYhFnTwka4mX/3jGj+sF2CDBD90g0Gcb554 p2BIyUi3Um5Q2YX0wEZLGnhmxqmwA6eov+o0NThA3WKl+/jLMi+HlHmDzTh/IKw7 QW4O2S/no1s= =7zlg -----END PGP SIGNATURE----- From ostrowb at tblc.org Thu Jun 28 17:40:50 2007 From: ostrowb at tblc.org (Ben Ostrowsky) Date: Thu, 28 Jun 2007 11:40:50 -0400 Subject: [Mailman-Users] A script for changing subscriber/owner email domains In-Reply-To: <3C5ACAD3-EB5E-4265-8663-D673349774DD@python.org> References: <87fy4c2z0q.fsf@uwakimon.sk.tsukuba.ac.jp> <3C5ACAD3-EB5E-4265-8663-D673349774DD@python.org> Message-ID: <69FDF3BECCCBAB41ABBCD23E235852940478764D@EXCHANGE.tblc.local> I didn't know any other way to do this, so I wrote a script. Hope it's not politically incorrect around here to have used Perl. ;) Share and enjoy! Ben #!/usr/bin/perl -w # Change all Mailman email addresses from one domain to another. # Example: change_subscriber_domain tblc.lib.fl.us tblc.org my $from = $ARGV[0]; my $to = $ARGV[1]; print "Old domain name: $from\n"; print "New domain name: $to\n\n"; open FH, "/usr/lib/mailman/bin/find_member --owners $from\$ |"; while () { if (/^([^@]*).(.*) found in:/) { my $old = "$1\@$2"; my $new = "$1\@$to"; print "$old\n\t=> $new\n"; $old =~ s/(['"])/\\$1/g; $new =~ s/(['"])/\\$1/g; system "/usr/lib/mailman/bin/clone_member --remove --admin --quiet $old $new\n"; print "--------------------\n"; } } From pdbogen at gmail.com Thu Jun 28 18:07:22 2007 From: pdbogen at gmail.com (Patrick Bogen) Date: Thu, 28 Jun 2007 11:07:22 -0500 Subject: [Mailman-Users] A script for changing subscriber/owner email domains In-Reply-To: <69FDF3BECCCBAB41ABBCD23E235852940478764D@EXCHANGE.tblc.local> References: <87fy4c2z0q.fsf@uwakimon.sk.tsukuba.ac.jp> <3C5ACAD3-EB5E-4265-8663-D673349774DD@python.org> <69FDF3BECCCBAB41ABBCD23E235852940478764D@EXCHANGE.tblc.local> Message-ID: <6fbe3da00706280907q625a2c98padf7f09d7fd1bee3@mail.gmail.com> On 6/28/07, Ben Ostrowsky wrote: > I didn't know any other way to do this, so I wrote a script. Hope it's > not politically incorrect around here to have used Perl. ;) It's probably more correctly done with a withlist script (which would by python), for what it's worth. -- - Patrick Bogen From prieheck at iwu.edu Thu Jun 28 18:18:25 2007 From: prieheck at iwu.edu (Pat Riehecky) Date: Thu, 28 Jun 2007 11:18:25 -0500 Subject: [Mailman-Users] Simple way to change archive settings Message-ID: <1183047505.16629.24.camel@thales.iwu.edu> I know that this falls under the withlist command, but I am not really python savvy so.... How exactly would I go about deleting the archives for about 15 lists and setting their archive attributes to off? Pat From msapiro at value.net Thu Jun 28 20:13:24 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 11:13:24 -0700 Subject: [Mailman-Users] Simple way to change archive settings In-Reply-To: <1183047505.16629.24.camel@thales.iwu.edu> Message-ID: Pat Riehecky wrote: >I know that this falls under the withlist command, but I am not really >python savvy so.... > >How exactly would I go about deleting the archives for about 15 lists >and setting their archive attributes to off? Actually, withlist is not the best tool for this. It is most easily done in a shell script that processes a few commands for each list. If the 15 lists are all the lists in the installation, you can get their names in the shell script from `bin/list_lists --bare` Otherwise, you could read the 15 names from a file. To set archiving off, you just do bin/config_list -i file $list where file contains the single line archive = 0 and $list contains the list name. To remove the existing archives you can do rm -rf archives/private/${list}/* rm -f archives/private/${list}.mbox/${list}.mbox rm -f archives/public/${list}.mbox You may or may not want to leave a stub index.html file in archives/private/${list}/ to say something about the list not having archives. You may or may not want to do rm -f archives/private/${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 Thu Jun 28 20:27:39 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Thu, 28 Jun 2007 13:27:39 -0500 (CDT) Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: Mail from '"Stephen J. Turnbull" ' dated: Thu, 28 Jun 2007 10:12:33 +0900 Message-ID: <200706281827.l5SIRdX9001145@britaine.ctd.anl.gov> Barry Finkel writes: > > I am running Mailman 2.1.9. I have a list where one posting has a > > "Subject:" line: > > > > Change in Procedure for Computers on list with possible Antivirus Problems > > > > The next posting in the thread has: > > > > Change in Procedure for Computers on list with possible AntivirusProblems "Stephen J. Turnbull" replied: >What is happening, I guess, is that Mailman is folding that header to >keep it within some number of characters, maybe 76 or so. RFC 2822 >specifies that this may be done by inserting a linebreak (CRLF) before >whitespace. The RFC implies that the right thing to do in that case >is to remove the CRLF only, but some MUAs also remove a space. I >suspect that is what is happening to this case. > >Can you post a copy of the "raw" header as received by Mailman and as >sent by Mailman? I am not sure I have this information. What I see (and posted) from the list .mbox file - is that what was received by Mailman or what was sent? ---------------------------------------------------------------------- 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 msapiro at value.net Thu Jun 28 21:00:14 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 12:00:14 -0700 Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: <200706281827.l5SIRdX9001145@britaine.ctd.anl.gov> Message-ID: Barry Finkel wrote: > >"Stephen J. Turnbull" replied: > >>Can you post a copy of the "raw" header as received by Mailman and as >>sent by Mailman? > >I am not sure I have this information. What I see (and posted) from >the list .mbox file - is that what was received by Mailman or what was >sent? It's essentially the message as sent by Mailman to the list, but without the msg_header and msg_footer if any. To get the incoming message, you'd have to go to the poster's sent messages or get a Cc or Bcc from the poster. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From puckett_chuck at hotmail.com Thu Jun 28 21:37:23 2007 From: puckett_chuck at hotmail.com (Chuck Puckett) Date: Thu, 28 Jun 2007 14:37:23 -0500 Subject: [Mailman-Users] Formatted email Message-ID: When I send a message to my Mailman lists (for which I'm a member), I get the original formatted message. (I put pictures and dress it up: it's announcing theatre events, good to spice it up). Some (all?) of my membership apparently have the formatting stripped, and just get plain text. Does mailman strip formatting? If so, why does it appear formatted to me? And can I let the formatting pass on through? I see no obvious properties that seem to control this ("plain" on the Membership Management refers to a digest, which is not what I'm intending, nor wish to have used in that manner). Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) From msapiro at value.net Thu Jun 28 22:07:53 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 13:07:53 -0700 Subject: [Mailman-Users] Problem with mailman and exim. In-Reply-To: <1182871648.13237.10.camel@alberto-laptop> References: <1182871648.13237.10.camel@alberto-laptop> Message-ID: <46841519.2060707@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alberto V. I. wrote: > > I create mailman list and then I receive the notificacion to admin > email, then I create anyother list without problems, beeing notified by > mailman, but I cannot receive mails to list, If I send any mail to list, > I obtain no result. > > I followed : /usr/share/doc/mailman/README.Exim4.Debian > I did everything but/except : > "and list all your Mailman domains in"POSTFIX_STYLE_VIRTUAL_DOMAINS". > All the rest things are made, do I need to use virtual domains? I have no idea what is in this Debian document, but the best instructions for Mailman/Exim integration are documents linked from As far as POSTFIX_STYLE_VIRTUAL_DOMAINS is concerned, this is only applicable if you are using Postfix and have set MTA = 'Postfix' in mm_cfg.py. What is in your exim_main.log and/or your exim_reject.log for the posts you attempt to send to your Mailman lists? - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhBUZVVuXXpU7hpMRAt+1AJ4wzhQ4Ced1FcEs+4iTz9r+XnHuJACg9Rxj 8+0cy1vakXGzziBICIQVuHY= =HH4z -----END PGP SIGNATURE----- From msapiro at value.net Thu Jun 28 22:30:21 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 13:30:21 -0700 Subject: [Mailman-Users] Formatted email In-Reply-To: Message-ID: Chuck Puckett wrote: >When I send a message to my Mailman lists (for which I'm a member), I get >the original formatted message. (I put pictures and dress it up: it's >announcing theatre events, good to spice it up). > > > >Some (all?) of my membership apparently have the formatting stripped, and >just get plain text. Does mailman strip formatting? If so, why does it >appear formatted to me? There are two possibilities. Posibility one is you are looking at your sent message or a Cc: or Bcc: that you sent to yourself. Possibility two is that the list is actually sending the post out as received from you, but it is multipart/alternative with a text/plain part and a text/html part and those users who don't see the formatting have their MUAs set to display the text/plain alternative or have MUAs that don't recognize MIME email. >And can I let the formatting pass on through? I see >no obvious properties that seem to control this ("plain" on the Membership >Management refers to a digest, which is not what I'm intending, nor wish to >have used in that manner). The controls are under Content filtering (Is that not obvious?). The simplest thing, especially if this is an announce list and you do all the posting, is to set filter_content to No. Then Mailman will send the post as received with only the possible addition of msg_header and msg_footer if any. If your list is already set this way, then the issue is probably possibility two above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From puckett_chuck at hotmail.com Thu Jun 28 22:54:26 2007 From: puckett_chuck at hotmail.com (Chuck Puckett) Date: Thu, 28 Jun 2007 15:54:26 -0500 Subject: [Mailman-Users] Formatted email In-Reply-To: References: Message-ID: Mark, Hmmm. Not sure that Content Filtering is the obvious place, at least for me. I tend to separate (in my mind) content from format. And never been to that particular page before, so didn't really think about it. In any case: filter_content is already set to No. pass_mime_types has multipart/mixed, /alternative and text/plain. Instructions say "Leave this field blank to skip this filter test", which might lead one to blank out the field. But I suspect this is default, yes? I've certainly never touched anything on this page. convert_html_to_plaintext is set to Yes, and that looks suspicious. Seems like I'd want it No, and pass_mime_types blanked out, if I understand commentary (which is doubtful). But the top guy is set to NO, so that implies rest of the settings are probably ignored. I mean, the people that are getting these messages are overwhelmingly Windows/likely Outlook users. I don't think most of them would know MIME from MISSOURI. Is there something they'd need to do that's not done by default? Btw: I never copy myself to CC: or BCC: I just send to the list, and I get a nicely formatted message. Chuck Puckett, Esq., BS, ~MS, ThD www.puckettpublishing.com "The unexamined life is not worth living." (Socrates) "The unexamined faith is not worth believing." (Chuck) "Anger is a wind that blows out the lamp of the mind." (Arabian proverb) "I don't want to steal the show... I only want to borrow it for a while." (Chuck) -----Original Message----- From: Mark Sapiro [mailto:msapiro at value.net] Sent: Thursday, June 28, 2007 3:30 PM To: Chuck Puckett; mailman-users at python.org Subject: Re: [Mailman-Users] Formatted email Chuck Puckett wrote: >When I send a message to my Mailman lists (for which I'm a member), I get >the original formatted message. (I put pictures and dress it up: it's >announcing theatre events, good to spice it up). > > > >Some (all?) of my membership apparently have the formatting stripped, and >just get plain text. Does mailman strip formatting? If so, why does it >appear formatted to me? There are two possibilities. Posibility one is you are looking at your sent message or a Cc: or Bcc: that you sent to yourself. Possibility two is that the list is actually sending the post out as received from you, but it is multipart/alternative with a text/plain part and a text/html part and those users who don't see the formatting have their MUAs set to display the text/plain alternative or have MUAs that don't recognize MIME email. >And can I let the formatting pass on through? I see >no obvious properties that seem to control this ("plain" on the Membership >Management refers to a digest, which is not what I'm intending, nor wish to >have used in that manner). The controls are under Content filtering (Is that not obvious?). The simplest thing, especially if this is an announce list and you do all the posting, is to set filter_content to No. Then Mailman will send the post as received with only the possible addition of msg_header and msg_footer if any. If your list is already set this way, then the issue is probably possibility two above. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Thu Jun 28 23:46:25 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 14:46:25 -0700 Subject: [Mailman-Users] Formatted email In-Reply-To: Message-ID: Chuck Puckett wrote: > >In any case: filter_content is already set to No. pass_mime_types has >multipart/mixed, /alternative and text/plain. Instructions say "Leave this >field blank to skip this filter test", which might lead one to blank out the >field. But I suspect this is default, yes? I've certainly never touched >anything on this page. > >convert_html_to_plaintext is set to Yes, and that looks suspicious. Seems >like I'd want it No, and pass_mime_types blanked out, if I understand >commentary (which is doubtful). But the top guy is set to NO, so that >implies rest of the settings are probably ignored. That is correct. if filter_content is No, no content filtering is done and the rest settings on the page are irrelevant. >I mean, the people that are getting these messages are overwhelmingly >Windows/likely Outlook users. I don't think most of them would know MIME >from MISSOURI. Is there something they'd need to do that's not done by >default? You are receiving the post as sent from Mailman. It is sent to everyone else in the same way. It is possible, but very unlikely that something in the mail delivery system is altering the message that these users see. Much, much more likely is that their actual MUA (mail reader, mail client) is not displaying the formatting. Many MUA's will not load images in formatted email by default for security/privacy reasons. I have no idea what the MS Outlook defaults are or how to change them. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 29 05:18:47 2007 From: msapiro at value.net (Mark Sapiro) Date: Thu, 28 Jun 2007 20:18:47 -0700 Subject: [Mailman-Users] post formatting and timing In-Reply-To: <4681B1B6.4020206@pauahtun.org> References: <4681B1B6.4020206@pauahtun.org> Message-ID: <46847A17.9000105@value.net> Ivan Van Laningham wrote: > > I think something else is going on, besides just the only line > ending. I'm using two versions of T-Bird, 1.5 and 2.0 something, and > both display the message concerned the same way, all crammed together on > a single line. I think there must be some encoding issue. It probably > is some configuration issue with T-Bird, but I've not been able to find it. I can't find any relevant configuration setting in T-Bird, and I don't see the problem in T-Bird 2.0.0.4 with a utf-8 charset base64 encoded message I received through a test list. The message contained the following ---------------------------------- This should be a unicode encoded message. Throw in a few ?funny? chars To get encoding ---------------------------------- The lines of dashes are separate lines and in between are a line of text, an empty line, a second line of text, a second empty line and a third line of text. I'm sending this in utf-8 charset (I hope), and it should come from the list encoded base64, and I expect it will display as described in my T-Bird 2.0.0.4. What do you see? -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From Jesus.Olivan at uab.es Fri Jun 29 09:23:26 2007 From: Jesus.Olivan at uab.es (=?ISO-8859-1?Q?Jes=FAs_Oliv=E1n?=) Date: Fri, 29 Jun 2007 09:23:26 +0200 Subject: [Mailman-Users] rare problem In-Reply-To: References: Message-ID: <4684B36E.3000006@uab.es> I've applied changes in my regexp like u said, thanks! and this is the From line you requested: From: =?ISO-8859-1?Q?123456789-123456789-12345678=E99-123456789-123456789?= =?ISO-8859-1?Q?-123456789-123456789-?= This one comes from a mail that has not beed accepted by mailman, although address in from is allowed by regexp in Allowed senders. Thanks for your help. Mark Sapiro escribi?: > Jes?s Oliv?n wrote: > >> i'm using mailman 2.1.5 on a Solaris box, and i've got a very rare issue... >> >> if i try to post a list using a non-suscribed email address, and this >> email address is included in non-suscribers allowed senders, it accepts >> my post... but if i use a regular expression like this >> ^[A-Za-z0-9.\-_%]+@[A-Za-z0-9.-]*mynet.com$ and try to post using a from >> line using more than 30 characters (from line splits in two in mail >> header then) and an accent. Then, mailman doesn't accept this mail and >> return it to me, although this email address is under my.net.com domain. >> > > > First, while it is not the issue you are asking about, your regexp is > probably more liberal than you want. I suggest something like > > ^[A-Za-z0-9.\-_%]+@([A-Za-z0-9.-]*\.)?mynet\.com$ > > to preclude matching things like > > user at xyz.aaamynet.com > > and > > user at host.mynetxcom > > As far as your question is concerned, the sender address is retrieved > from the From: header using Python email library methods and > functions. If there is a bug there, we'd have to see an exact copy of > the split From: header to check that out. > > Also, when your MUA folds the from header into multiple lines, it > should not be folding inside the email address. If by chance, it is, > then it is your MUA that is at fault. > > In any case, I don't understand why this would affect only a regexp > match and not a string match. The address that is being checked is the > same in both cases. > > From b19141 at britaine.ctd.anl.gov Fri Jun 29 16:05:11 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Fri, 29 Jun 2007 09:05:11 -0500 (CDT) Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: Mail from '"Stephen J. Turnbull" ' dated: Thu, 28 Jun 2007 10:12:33 +0900 Message-ID: <200706291405.l5TE5BTt029976@britaine.ctd.anl.gov> Barry Finkel writes: >> I am running Mailman 2.1.9. I have a list where one posting has a >> "Subject:" line: >> >> Change in Procedure for Computers on list with possible Antivirus Problems >> >> The next posting in the thread has: >> >> Change in Procedure for Computers on list with possible AntivirusProblems and "Stephen J. Turnbull" replied: >What is happening, I guess, is that Mailman is folding that header to >keep it within some number of characters, maybe 76 or so. RFC 2822 >specifies that this may be done by inserting a linebreak (CRLF) before >whitespace. The RFC implies that the right thing to do in that case >is to remove the CRLF only, but some MUAs also remove a space. I >suspect that is what is happening to this case. > >Can you post a copy of the "raw" header as received by Mailman and as >sent by Mailman? Below are pieces of two messages. I have the original message from the archives of the sender followed by the relevant lines of the list .mbox file (including line numbers). ======================================================================= -----Original Message----- From: ... Sent: Tuesday, June 26, 2007 2:30 PM To: ... Subject: RE: Change in Procedure for Computers on list with possible AntivirusProblems Not a question ... ======================================================================= 184331 Subject: RE: Change in Procedure for Computers on list with possible 184332 AntivirusProblems 184333 Date: Tue, 26 Jun 2007 14:29:52 -0500 184342 From: ... 184343 To: ... 184358 184359 Not a question ... ======================================================================= ======================================================================= -----Original Message----- From: ... Sent: Tuesday, June 26, 2007 3:50 PM To: ... Cc: ... Subject: RE: Change in Procedure for Computers on list withpossibleAntivirusProblems Hi ... ======================================================================= 184735 Subject: RE: Change in Procedure for Computers on list 184736 withpossibleAntivirusProblems 184737 Date: Tue, 26 Jun 2007 15:50:20 -0500 184747 From: ... 184748 To: ... 184751 Cc: ... 184765 184766 Hi ... ======================================================================= ======================================================================= In both cases, I do not see that Mailman has removed any blanks from the "Subject:" line. ---------------------------------------------------------------------- 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 rsk at gsp.org Fri Jun 29 16:44:43 2007 From: rsk at gsp.org (Rich Kulawiec) Date: Fri, 29 Jun 2007 10:44:43 -0400 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing Message-ID: <20070629144443.GA7171@gsp.org> Two related suggestions. (1) LHS (left-hand-side) rules Any incoming mail message whose putative sender matches: do-not-reply@ do.not.reply@ donotreply@ no-reply@ no.reply@ noreply@ and which is directed to any of the Mailman standard aliases can be rejected (not bounced [1]) with SMTP status 550 (extended status 5.7.1) since either: (a) it's a forgery, therefore there's no point in letting Mailman attempt to emit a reply -- or even in accepting the message to begin with. (a) it's not a forgery, therefore there's no point in trying to reply to it. (Nor is there any point in permitting it to subscribe to a list or send any traffic to one.) Arguably, this could be done in some MTAs by configuring rejection of those LHS patterns on a per-local-user basis; but I'll argue that doing this in Mailman itself would be more useful, since many (perhaps most) sites don't use per-local-user configuration (and perhaps don't know how). Moreover, any site running multiple mailing lists would need to set this up for every Mailman alias for every mailing list -- so it seems simpler to handle it inside Mailman itself. My guess is that this should be a switchable feature, named something like "reject-noreplies". (Not that I can envision a need to switch it off, but I think it'd be more conversative to have that option.) (2) sender rules Any incoming mail message whose putative sender matches the list below can also be rejected (SMTP status 550, extended status 5.7.1) because these addresses will never send traffic to any mailing list nor subscribe to any mailing list. There's thus no point in expending the bandwidth/CPU necessary to process them, nor in forwarding them on to list admins for possible approval -- any message from these addresses to any Mailman-related address is invariably a phish attempt. I'm sure this list is incomplete; I built it by looking at incoming attempts received locally in 2007. It's not meant to be complete, only illustrative. Again, this could be done at the MTA level by blocking on a per-local-user basis, but (as above) I think wiring it into Mailman would make it useful to people who do not have their MTAs so configured. And this should probably also be switchable feature, perhaps named "reject-obvious-phishes". More comments below this list. acc-overview at paypal.com account-update at amazon.com account.issue at paypal.com account.protection at ebay.com account.support at chaseonline.com account at amazon.com account at bankofamerica.com account at capitalone.com account at chase.com account at ebay.com account at paypal.com accounts at amazon.com accounts at bscu.org accounts at chaseonline.com accounts at downeysavings.com accounts at mybankfirstunited.com accounts at paypal.com accounts at regions.com accounts at searscard.com accounts at wellsfargo.com accounts_support at paypal.com accountservice at bankofamerica.us accountupdate at chase.com admin at bankofhanover.com admin at paypal.com administrator at paypal.com ads at servicecu.org alertingservice at searscard.com alertsrobots at bankofamerica.com assistance at paypal.com auto-confirm at amazon.com aw-confirm at ebay.com aw-confirm at paypal.com aw.confirm at paypal.com aw.confirm at regions.com banking at chase.com bankofamericaalerts at alerts.bankofamerica.com bankofamericaalerts at bankofamerica.com billing at ebay.com billing at paypal.com boa at bankofamerica.com cardpayments at citibank.com cards at paypal.com cgi-bin at paypal.com chase at chase.com chase at chaseonline.com chase at notify.chase.com chase at service.com chasecardservices at notify.chase.com chaseco at chase.com chaseonline at chase.com chaseonlinealerts at alerts.chase.com chaseonlinealerts at chase.com checkout at ebay.com closed at paypal.com confirm145 at paypal.com confirmer at paypals.com contact at paypal.com customcare at paypal.com customecare at paypal.com customer-service at westernunion.com customer-services at bankofamerica.com customer.service at capitalone.com customer.service at chase.com customer.support at capitalone.com customer.support at chase.com customer.support at paypal.com customer at bankofamerica.com customer at paypal.com customer at redwood-bank.com customercare at amazon.com customercare at paypal.com customers at amazon.com customerservice at bankofamerica.com customerservice at paypal.com customerservice at wachovia.com customersupport at citibank.co.uk dncu at dncu.org do-not-replay at azfcu.org do-not-replay at chase.com do-not-replay at xfcu.org do-not-reply at azfcu.org do-not-reply at bankofamerica.com do-not-reply at chase.com do-not-reply at customers.cacu.net do-not-reply at germanamericanbancorp.com do-not-reply at lacapfcu.org do-not-reply at paypal.com do-not-reply at regions.com financial at regions.com flafstar-bank at security.org fraud at paypal.com fraud_help at chase.com info at azfcu.org info at bankofamerica.com info at ebay.com info at paypal.com info at westernunion.com member at ebay.com member at paypal.com memsvc at vacu.org mesage.center at chase.com message.center at chase.com message at ebay.com message at northforkbank.com messages at ebay.com militarybankalerts at alerts.bankofamerica.com militarybankalerts at bankofamerica.com mychase at chase.com no-reply at chase.com no-reply at ebay.com no-reply at maybank.org no.reply at ebay.com no.reply at paypal.com noreply at bankofamerica.com noreply at germanamericanbancorp.com noreply at westernunion.com notice.alert at bankofamerica.com notice at azfcu.org notice at bankofamerica.com notice at chase.com notice at chaseonline.com notice at ebay.com notice at paypal.com notice at wellsfargo.com notices.alert at bankofamerica.com office at paypal.com office at westernunion.com online-banking at chase.com online-support at online-bankofamerica.com online-survey at chase.com online.bank at regions.com online.banking at regions.com online.services at wachovia.com online at bankofamerica.com online at paypals.com onlineaccount at capitalone.com onlinebanking.alert at bankofamerica.com onlinebanking at alert.bankofamerica.com onlinebanking at bankofamerica.com onlinebanking at wellsfargo.com onlinesecurity at bankofamerica.com onlinesecurity at wachovia.com onlineservice at bankofamerica.com onlineservice at capitalone.com onlineservice at paypal.com onlineservice at wachovia.com onlineservice at wellsfargo.com onlineservices at bankofamerica.com onlineservices at wachovia.com onlinesrvices at wachovia.com onlinesupport at pafcu.org onlineupdate at paypal.com payment at paypal.com paymentprotector at cuna.org paypal-acc at paypal.com paypal-account at paypal.com paypal-service at paypal.com paypal at onlinesecure.com powersellersinfo at ebay.com privacy at regions.com pw-confirm at chase.com renew at azfcu.org renew at tscu.org resolution-center at paypal.com reward at chaseonline.com reward at downeysavings.com rewards at chase.com rewards at westernunion.com secure-acc at amazon.com secure-acc at paypal.com secure-bank at regions.com secure-cc at capitalone.com secure-cc at paypal.com secure-login at chase.com secure-login at regions.com secure at boa.com secure at paypal.com secure at wachovia.com secure at watermarkcu.org secure at wellsfargo.com security.alert at bankofamerica.com security at amazon.com security at baefcu.org security at bankofamerica.com security at bankofhanover.com security at boa.com security at capitalone.com security at cefcu.net security at chase.com security at comchoicecu.org security at dncu.org security at ebay.com security at ncua.gov security at paypal.com security at regions.com security at security.com security at transwestcu.com security at visa.com security at wellsfargo.com security_alert at citizensbank.com service-account at paypal.com service-bank at regions.com service.account at capitalone.com service.customer at paypal.com service at amazon.com service at azfcu.org service at bankofamerica.com service at bankofamerlca.com service at bankofhanover.com service at capitalone.com service at chase.com service at chaseonline.chase.com service at chaseonline.com service at chesterfieldfcu.net service at cscu.org service at downeysavings.com service at ebay.com service at mandtbank.com service at midamericabank.com service at mybankfirstunited.com service at ncua.gov service at paypal.com service at paypal.it service at paypals.com service at regions.com service at secure.regions.com service at visa.com service at wachovia.com service at wamu.com service at warrenfcu.com service at wellsfargo.com service at westernunion.com service_banking at chase.com servicecenter at bankofamerica.us servicecenter at firstinterstatebank.com services at bankofamerica.com services at chesterfieldfcu.net services at downeysavings.com services at ebay.com services at paypal.com services at watermarkcu.org sitesecurity at citibank.com store-news at amazon.com support at amazon.com support at capitalone.com support at chase.com support at ebay.com support at flagstar.com support at online-bankofamerica.com support at paypal.com support at wamu.com support at wellsfargo.com support at yahoo.com survery at twcu.org survey at arizonafederal.org survey at azfcu.org survey at bankofhanover.com survey at cuna.org survey at downeysavings.com survey at tyndallcreditunion.com suspension at ebay.com unsuspend at paypal.com update-accounts at paypal.com update.profile at amazon.com update at boa.com update at paypal.com update at wellsfargo.com updating at capitalone.com web-info at cuna.org web-service at mybankfirstunited.com webmaster at paypal.com westernunionalerts at westernunion.com westernunionresponse at westernunion.com In both these cases, the check can be carried out by doing some simple string-matching. The second list will need ongoing (and careful) maintenance -- and one way to achieve that might be to enlist the cooperation of the domains in question. However, note that (a) under-inclusion is no worse than the current situation and (b) over-inclusion is unlikely given even a modicum of scrutiny applied to prospective list entries. ---Rsk [1] The difference between a reject and a bounce: a reject is performed by emitting the appropriate SMTP status code and closing the connection; that is, the message is refused while the SMTP connection is open from the sending side. A bounce is performed by accepting the message (again, emitting the appropriate SMTP status code), then performing further processing, deciding not to accept the message, and attemping to "return" the message to the putative sender. The simplest way of putting this is "reject good, bounce bad", since bounces invariably result in outscatter (aka "backscatter"), which is a form of spam, which in turn will cause sufficiently egregious emitters to be (correctly) blacklisted. Note as well that various mitigating strategies designed to blunt the effects of bounce-instead-of-reject policies lose entirely due to rampant forgery, DNS redirection, an estimated 100M+ fully-compromised systems, and widespread failure of end-user ISPs to control outbound SMTP abuse. So saying that it's immensely preferable to reject rather than bounce is an understatement. From b19141 at britaine.ctd.anl.gov Fri Jun 29 17:02:48 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Fri, 29 Jun 2007 10:02:48 -0500 (CDT) Subject: [Mailman-Users] Problem/Question Regarding Bounce Processing Message-ID: <200706291502.l5TF2ml2001588@britaine.ctd.anl.gov> I have a question/problem with Mailman bounce processing. We have Mailman lists here that are re-built every morning from our Human Resources database. When mail is sent to one of these lists, and one or more of the e-mail addresses therein have problems, I see in my morning report (and/or in the Mailman bounce log) that specific addresses have had bounces. I do not see the rejection messages that are sent to listname-bounce so I do not know what the problem might have been. I assume that the rejection message is discarded after it has been processed, the bounce log appended, and the e-mail address bounce score increased. I would like to be able to correct those bad addresses that come from our HR Database when they are first seen as bad, but I cannot correct them if I do not know what the nature of the bounce was. And I really do not want to have to send test mail to each of the failed addresses in order to get a rejection message. I know that I can add an additional address in the /var/lib/mailman/data/aliases file to the listname-bounce: alias line, but I do not want to do this manually every time I create a new list. Are there any suggestions on what I can do? Thanks. ---------------------------------------------------------------------- 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 msapiro at value.net Fri Jun 29 17:31:17 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 08:31:17 -0700 Subject: [Mailman-Users] rare problem In-Reply-To: <4684B36E.3000006@uab.es> References: <4684B36E.3000006@uab.es> Message-ID: <468525C5.8050105@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jes?s Oliv?n wrote: > I've applied changes in my regexp like u said, thanks! > > and this is the From line you requested: > > From: =?ISO-8859-1?Q?123456789-123456789-12345678=E99-123456789-123456789?= > =?ISO-8859-1?Q?-123456789-123456789-?= > > This one comes from a mail that has not beed accepted by mailman, > although address in from is allowed by regexp in Allowed senders. The problem is a bug in some versions of the Python email library. This problem will occur whether the 'address' in *_these_nonmembers is a regexp or a string. It also does not depend on the 'real name' being RFC 2047 encoded. All that is required is that the 'real name' be long enough that the From: header folds into two lines. In this case, the email.Utils function getaddresses() returns a spurious extra 'address' based on the first line of the folded header and this is the 'address' we check against *_these_nonmembers instead of checking the real address. This bug exists in Mailman through 2.1.9. I will work around it for Mailman 2.1.10. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhSXFVVuXXpU7hpMRAkRpAKDYF1Lk1dsNRfVAgX8QomeswrkadwCfbmVN Yk6i/KOIfDCFHUrUGUhurq4= =dH8a -----END PGP SIGNATURE----- From msapiro at value.net Fri Jun 29 17:51:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 08:51:27 -0700 Subject: [Mailman-Users] Problem/Question Regarding Bounce Processing In-Reply-To: <200706291502.l5TF2ml2001588@britaine.ctd.anl.gov> References: <200706291502.l5TF2ml2001588@britaine.ctd.anl.gov> Message-ID: <46852A7F.5010200@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barry Finkel wrote: > I have a question/problem with Mailman bounce processing. > We have Mailman lists here that are re-built every morning from our > Human Resources database. When mail is sent to one of these lists, and > one or more of the e-mail addresses therein have problems, I see in my > morning report (and/or in the Mailman bounce log) that specific > addresses have had bounces. I do not see the rejection messages that > are sent to > > listname-bounce > > so I do not know what the problem might have been. I assume that the > rejection message is discarded after it has been processed, the > bounce log appended, and the e-mail address bounce score increased. > I would like to be able to correct those bad addresses that come from > our HR Database when they are first seen as bad, but I cannot correct > them if I do not know what the nature of the bounce was. And I really > do not want to have to send test mail to each of the failed addresses > in order to get a rejection message. I'm not sure what the issue is. Do these bad addresses never get removed because you are continuously removing and re-adding them, thus resetting their bounce score every day? Or do you just want to see the 'first' bounce from a new member so you can delete that address faster than normal bounce processing does? You are correct about what Mailman does. The only actual bounce DSN that is not simply discarded after processing is the one that caused the score to reach threshold and disables delivery. That one is sent to the list owner with the disable notice if bounce_notify_owner_on_disable is Yes. If the problem is that bad addresses are never getting disabled and removed because you are continuously rebuilding the list and resetting scores, you could try using bin/sync_members to update the list from the HR data. This will not reset scores or options for existing members. If that is not the issue, and you just want to see the first bounce for a new member, and you don't want to do this in the MTA and you don't want to modify Mailman code, the only way is to set bounce_score_threshold to 1.0 or less so that everyone is disabled on the first bounce and then re-enable those that shouldn't be disabled so soon. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhSp/VVuXXpU7hpMRAuL9AKDp3+Y9vHOgnIP0ZqAopwCStxUpaACgwo4L h+nLERWMfWEEW4RdRm3RkPI= =847S -----END PGP SIGNATURE----- From msapiro at value.net Fri Jun 29 18:00:07 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 09:00:07 -0700 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <20070629144443.GA7171@gsp.org> References: <20070629144443.GA7171@gsp.org> Message-ID: <46852C87.10305@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rich Kulawiec wrote: > Two related suggestions. > [1] The difference between a reject and a bounce: a reject is performed > by emitting the appropriate SMTP status code and closing the connection; > that is, the message is refused while the SMTP connection is open from > the sending side. Exactly, which is why Mailman can't do this. It has to be done in the incoming MTA. Mailman doesn't see the message until the MTA has already accepted it. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhSyHVVuXXpU7hpMRAlcXAKDGo+YS4KQLzIWOe9ftDLVv2zW+MACdFnQJ dIabTI1fLUvo0sgxf8R98hk= =lcgV -----END PGP SIGNATURE----- From msapiro at value.net Fri Jun 29 18:14:27 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 09:14:27 -0700 Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: <200706291405.l5TE5BTt029976@britaine.ctd.anl.gov> References: <200706291405.l5TE5BTt029976@britaine.ctd.anl.gov> Message-ID: <46852FE3.5060801@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barry Finkel wrote: > > Below are pieces of two messages. I have the original message > from the archives of the sender followed by the relevant lines of > the list .mbox file (including line numbers). > > ======================================================================= > -----Original Message----- > From: ... > Sent: Tuesday, June 26, 2007 2:30 PM > To: ... > Subject: RE: Change in Procedure for Computers on list with possible > AntivirusProblems This is some rendering of the Subject:, but it is not the actual Subject: header. If it were, the Subject: of the outgoing message would be simply Subject: RE: Change in Procedure for Computers on list with possible since a header continuation must begin with at least one whitespace character. You need to get the 'message source' from the sender. > Not a question ... > ======================================================================= > 184331 Subject: RE: Change in Procedure for Computers on list with possible > 184332 AntivirusProblems And here we see Mailman has sent the post with the subject folded with a as the whitespace character. > 184333 Date: Tue, 26 Jun 2007 14:29:52 -0500 > 184342 From: ... > 184343 To: ... > > 184358 > 184359 Not a question ... > > ======================================================================= > ======================================================================= > -----Original Message----- > From: ... > Sent: Tuesday, June 26, 2007 3:50 PM > To: ... > Cc: ... > Subject: RE: Change in Procedure for Computers on list > withpossibleAntivirusProblems And someones MUA has dropped the in unfolding (and this has happened more than once) I think it would be better if Mailman folded using rather than since with a standards compliant unfolding would leave a in the middle of the subject which may be worse than dropping it. But, the fact remains that there are many commonly used MUAs that drop a whitespace character in unfolding and there's not much we can do about that. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhS/jVVuXXpU7hpMRAm5XAKCdZAzuN7TYt4lD9KTmsvffUqnS7wCeKUew V6Pn0pu0CJwDfJNv9aA7pno= =HqSS -----END PGP SIGNATURE----- From b19141 at britaine.ctd.anl.gov Fri Jun 29 18:39:28 2007 From: b19141 at britaine.ctd.anl.gov (Barry Finkel) Date: Fri, 29 Jun 2007 11:39:28 -0500 (CDT) Subject: [Mailman-Users] Problem/Question Regarding Bounce Processing In-Reply-To: Mail from 'Mark Sapiro ' dated: Fri, 29 Jun 2007 08:51:27 -0700 Message-ID: <200706291639.l5TGdSZV004238@britaine.ctd.anl.gov> Barry Finkel wrote: >> I have a question/problem with Mailman bounce processing. >> We have Mailman lists here that are re-built every morning from our >> Human Resources database. When mail is sent to one of these lists, and >> one or more of the e-mail addresses therein have problems, I see in my >> morning report (and/or in the Mailman bounce log) that specific >> addresses have had bounces. I do not see the rejection messages that >> are sent to >> >> listname-bounce >> >> so I do not know what the problem might have been. I assume that the >> rejection message is discarded after it has been processed, the >> bounce log appended, and the e-mail address bounce score increased. >> I would like to be able to correct those bad addresses that come from >> our HR Database when they are first seen as bad, but I cannot correct >> them if I do not know what the nature of the bounce was. And I really >> do not want to have to send test mail to each of the failed addresses >> in order to get a rejection message. And Mark Sapiro replied: >I'm not sure what the issue is. Do these bad addresses never get removed >because you are continuously removing and re-adding them, thus resetting >their bounce score every day? Or do you just want to see the 'first' >bounce from a new member so you can delete that address faster than >normal bounce processing does? > >You are correct about what Mailman does. The only actual bounce DSN that >is not simply discarded after processing is the one that caused the >score to reach threshold and disables delivery. That one is sent to the >list owner with the disable notice if bounce_notify_owner_on_disable is Yes. > >If the problem is that bad addresses are never getting disabled and >removed because you are continuously rebuilding the list and resetting >scores, you could try using bin/sync_members to update the list from the >HR data. This will not reset scores or options for existing members. > >If that is not the issue, and you just want to see the first bounce for >a new member, and you don't want to do this in the MTA and you don't >want to modify Mailman code, the only way is to set >bounce_score_threshold to 1.0 or less so that everyone is disabled on >the first bounce and then re-enable those that shouldn't be disabled >so soon. I am sorry that I was not clear in my posting. In a "normal" list, where persons subscribe and unsubscribe, I am content with the Mailman bounce processing, where Mailman will set "nomail" for addresses that continually bounce. When there is a bad e-mail address in our HR Database, that address needs to be corrected so that future mailings to that address, either via a Mailman list or via an ad-hoc mailing list derived from the HR Database, will reach the intended recipient. With the Mailman lists, I (as Mailman admin) do not see the rejection message; neither do the individual list owner(s). So, without my daily report I do not know that a bounce has occurred, and I do not know the nature of the bounce. As I did this morning, I had to send test mail to the address to get a rejection message to see what the failure was. If there is a bounce, can I be assurred that the bounce was due to the mailbox not existing? ---------------------------------------------------------------------- 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 jwblist3 at olympus.net Fri Jun 29 19:01:12 2007 From: jwblist3 at olympus.net (John W. Baxter) Date: Fri, 29 Jun 2007 10:01:12 -0700 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <20070629144443.GA7171@gsp.org> Message-ID: On 6/29/07 7:44 AM, "Rich Kulawiec" wrote: > Two related suggestions. > > > (1) LHS (left-hand-side) rules > > Any incoming mail message whose putative sender matches: > > do-not-reply@ > do.not.reply@ > donotreply@ > no-reply@ > no.reply@ > noreply@ > > and which is directed to any of the Mailman standard aliases can > be rejected (not bounced [1]) with SMTP status 550 (extended status > 5.7.1) since either: > > (a) it's a forgery, therefore there's no point in letting > Mailman attempt to emit a reply -- or even in accepting > the message to begin with. > (a) it's not a forgery, therefore there's no point in trying > to reply to it. (Nor is there any point in permitting it > to subscribe to a list or send any traffic to one.) > > Arguably, this could be done in some MTAs by configuring rejection > of those LHS patterns on a per-local-user basis; but I'll argue that > doing this in Mailman itself would be more useful, since many (perhaps > most) sites don't use per-local-user configuration (and perhaps don't > know how). Moreover, any site running multiple mailing lists would > need to set this up for every Mailman alias for every mailing list -- > so it seems simpler to handle it inside Mailman itself. > > My guess is that this should be a switchable feature, named something > like "reject-noreplies". (Not that I can envision a need to switch it > off, but I think it'd be more conversative to have that option.) At least here, this good idea would have to be implemented in the MTA which receives the message, as the message is not presented to Mailman until after the receiving MTA has accepted the message (in fact, here, it's not even presented to Mailman by the same MTA or on the same machine). Thus rejection is not possible based on what Mailman does. (Further, in the present Mailman, the presentation is by pipe, so doing something like Exim's recipient verification callout doesn't work.) There have indeed been discussions about making the MTA able to get information from Mailman in time to do SMTP-time rejection. It's not simple to do in the general case. --John From msapiro at value.net Fri Jun 29 19:20:35 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 10:20:35 -0700 Subject: [Mailman-Users] Problem/Question Regarding Bounce Processing In-Reply-To: <200706291639.l5TGdSZV004238@britaine.ctd.anl.gov> References: <200706291639.l5TGdSZV004238@britaine.ctd.anl.gov> Message-ID: <46853F63.1010407@value.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Barry Finkel wrote: > > I am sorry that I was not clear in my posting. In a "normal" list, > where persons subscribe and unsubscribe, I am content with the Mailman > bounce processing, where Mailman will set "nomail" for addresses that > continually bounce. > > When there is a bad e-mail address in our HR Database, that address > needs to be corrected so that future mailings to that address, either > via a Mailman list or via an ad-hoc mailing list derived from the HR > Database, will reach the intended recipient. With the Mailman lists, I > (as Mailman admin) do not see the rejection message; neither do the > individual list owner(s). So, without my daily report I do not know > that a bounce has occurred, and I do not know the nature of the > bounce. As I did this morning, I had to send test mail to the address > to get a rejection message to see what the failure was. If there is a > bounce, can I be assurred that the bounce was due to the mailbox not > existing? No. The bounce can be for many reasons, including such things as 'full mailbox'. You are correct in thinking that you have to see the actual DSN to know what the reason is. I am still not clear on what happens with the HR based list and whether the issue is that you need to see a bounce DSN as soon as possible in order to identify problems in the HR database, or if the issue is that bouncing members never get disabled. As I tried to say in my previous reply, if you need to see the first bounce, the only way to do that with Mailman settings is to set bounce_score_threshold to 1.0 or less so that everyone is disabled on the first bounce and set bounce_notify_owner_on_disable to Yes so that the list owner receives a notice which will contain the bounce DSN. Then the list owner has to notify HR if the DSN shows the address is no good or re-enable delivery if the DSN is for some other reason. If the issue is that bouncing members never get disabled, you need to revise the way you update the list from the HR database to use a method like bin/sync_members so that bounce scores are not reset in this process. In the first case, it is a balance between the extra effort to re-enable 'transient' bounce disables vs. the effort to extract the fact of the bounce from the bounce log and send a test email that determines which approach is better. - -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGhT9jVVuXXpU7hpMRAgoUAKDymAF/J6dmJNO3onu9fMd1FeKZWgCg0F5o WbNWQ8NlQg3buysOvanjwrw= =Uo2D -----END PGP SIGNATURE----- From rsk at gsp.org Fri Jun 29 20:23:36 2007 From: rsk at gsp.org (Rich Kulawiec) Date: Fri, 29 Jun 2007 14:23:36 -0400 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <20070629144443.GA7171@gsp.org> References: <20070629144443.GA7171@gsp.org> Message-ID: <20070629182335.GB10401@gsp.org> Mark, John -- reading both your messages (and applying significantly more coffee) has induced enlightenment. Yep, this is just not going to work the way I'd suggested. Bad me. No biscuit. So let me modify these as follows and see if this is any better: > (1) LHS (left-hand-side) rules Present to list-owner for disposition as done today, but mark it prominently as "noreply address, almost certainly a forgery". > (2) sender rules Present to list-owner for disposition as done today, but mark it prominently as "probable phish". Granted, in both cases, the message still has be to processed, but perhaps marking it (both on the "Subject" line and inside the message body) will make it easier/faster for list-owners to deal with. ---Rsk p.s. As as aside, I strongly recommend against callbacks/SAV. It's inherently abusive, it's a deliberate attempt to bypass site security policies [and thus illegal in some jurisdictions, but ask your attorney for clarification 'cause IANAL], it provides a spam support service, and -- as we've already seen -- it can be used to conduct quite effective DoS/DDoS attacks. And on top of that, far more effective, efficient, and difficult-to-abuse anti-spam methods exist. I'm working [yeah, alright, for some values of "work"] on a "stupid anti-spam techniques" FAQ that will cover this in considerably more depth, so I don't intend this to be by any means a full explanation. However, this topic has been repeatedly discussed on Spam-L in depth, so I'll refer anyone interested to that list's archives until I can manage to get that FAQ cranked out. From donald.teed at gmail.com Fri Jun 29 21:09:25 2007 From: donald.teed at gmail.com (D G Teed) Date: Fri, 29 Jun 2007 16:09:25 -0300 Subject: [Mailman-Users] Making list owner (listname-owner) appear in Return Path Message-ID: We are doing well in our migration from MJ2 to mailman. The default of sending emails with the -bounce address doesn't fit with our needs. We'd like it to work the way it did with MJ2, where the listname-owner type of address was in the Return-Path. Typically we set our list owner to be some administrative email address which several of us can check for interesting items or bulk delete after some time. In other cases, the owner of some fund raising campaign wants to receive bounce notifications to see immediately what addresses are not current. I think my answer is to edit SMTPDirect.py to set the Sender and Return Path, but I'm not sure what variable I need to use there. Is 'mlist.owner[:]' what I'll need? I'd want the specific list owner, not the site mailman owner. None of these are publicly subscribe-able lists, so the features of bounce processing are not valuable to us. Any suggestions? --Donald From msapiro at value.net Fri Jun 29 21:43:18 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 12:43:18 -0700 Subject: [Mailman-Users] Making list owner (listname-owner) appear in ReturnPath In-Reply-To: Message-ID: D G Teed wrote: > >I think my answer is to edit SMTPDirect.py to set the >Sender and Return Path, but I'm not sure what variable >I need to use there. Is 'mlist.owner[:]' what I'll need? >I'd want the specific list owner, not the site mailman owner. What you need is mlist.GetOwnerEmail() which will get the list-owner at example.com address. You don't want mlist.owner[:] because that is a list and you can't have a list of addresses as the SMTP MAIL FROM address (envelope sender). Any mail returned to the list-owner at example.com address gets delivered to the owner(s) and moderator(s). >None of these are publicly subscribe-able lists, so the features >of bounce processing are not valuable to us. There are lots of reasons why addresses on even non-public lists become undeliverable, but presumably, you are willing to deal with these manually. If I understand what you want, you can accomplish it by finding the code # Calculate the non-VERP envelope sender. envsender = msgdata.get('envsender') if envsender is None: if mlist: envsender = mlist.GetBouncesEmail() else: envsender = Utils.get_site_email(extra='bounces') at the beginning of process() in SMTPDirect.py and changing it to # Calculate the non-VERP envelope sender. if mlist: envsender = mlist.GetOwnerEmail() else: envsender = Utils.get_site_email(extra='owner') The else: clause comes into play for messages that don't come from a list, e.g. monthly password reminders. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From msapiro at value.net Fri Jun 29 21:56:58 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 12:56:58 -0700 Subject: [Mailman-Users] Making list owner (listname-owner) appear inReturnPath In-Reply-To: Message-ID: Mark Sapiro wrote: > >If I understand what you want, you can accomplish it by finding the code > > # Calculate the non-VERP envelope sender. > envsender = msgdata.get('envsender') > if envsender is None: > if mlist: > envsender = mlist.GetBouncesEmail() > else: > envsender = Utils.get_site_email(extra='bounces') > >at the beginning of process() in SMTPDirect.py and changing it to > > # Calculate the non-VERP envelope sender. > if mlist: > envsender = mlist.GetOwnerEmail() > else: > envsender = Utils.get_site_email(extra='owner') Actually, the above change is a bad idea. It should really be # Calculate the non-VERP envelope sender. envsender = msgdata.get('envsender') if envsender is None: if mlist: envsender = mlist.GetOwnerEmail() else: envsender = Utils.get_site_email(extra='owner') You shouldn't ignore the envsender in the message metadata. It exists to prevent bounce loops. I was thinking they wouldn't occur if the bounces were sent to the list owner directly, but of course, a list owner's address can be undeliverable for many reasons and loops can still occur. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From jwblist3 at olympus.net Fri Jun 29 22:25:15 2007 From: jwblist3 at olympus.net (John W. Baxter) Date: Fri, 29 Jun 2007 13:25:15 -0700 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <20070629182335.GB10401@gsp.org> Message-ID: On 6/29/07 11:23 AM, "Rich Kulawiec" wrote: > p.s. As as aside, I strongly recommend against callbacks/SAV. It's > inherently abusive, it's a deliberate attempt to bypass site security > policies [and thus illegal in some jurisdictions, but ask your attorney > for clarification 'cause IANAL], I wasn't referring to sender verification callbacks (which we do not use). I was referring to recipient verification callforwards, where the edge MTA doesn't know valid recipients but some internal (or even customer) MTA does. Exim can configure these easily (but that doesn't help because Mailman doesn't act like an MTA). I don't know about any other MTAs in this regard. --John From msapiro at value.net Fri Jun 29 22:35:51 2007 From: msapiro at value.net (Mark Sapiro) Date: Fri, 29 Jun 2007 13:35:51 -0700 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules tofrustrate spam/phishing In-Reply-To: <20070629182335.GB10401@gsp.org> Message-ID: Rich Kulawiec wrote: > >So let me modify these as follows and see if this is any better: > >> (1) LHS (left-hand-side) rules > >Present to list-owner for disposition as done today, but mark it >prominently as "noreply address, almost certainly a forgery". > >> (2) sender rules > >Present to list-owner for disposition as done today, but mark it >prominently as "probable phish". > >Granted, in both cases, the message still has be to processed, but >perhaps marking it (both on the "Subject" line and inside the >message body) will make it easier/faster for list-owners to deal with. Referring back to your original idea where you wanted the messages refused at SMTP time, it seems that what you really want is for messages that match your rules to be discarded. You can use header_filter_rules for this, but maintaining them would be a pain. If I were trying to do it, I would use the KNOWN_SPAMMERS list in mm_cfg.py. For example just listing a few of yours KNOWN_SPAMMERS = [ ('from', '^(.*[\s<])?do-not-reply@'), ('from', '^(.*[\s<])?acc-overview at paypal.com([\s>].*)?'), ] This list applies installation wide and will discard any message to a list or list-owner address that contains a matching header. The entries are 2-tuples ('a', 'b') where a is the case-insensitive name of a header and b is a Python regexp to match case-insensitively against the values of all headers of that type in the message. This doesn't address mail to the other (e.g., -request or -bounces) list addresses, but it's a start, and using KNOWN_SPAMMERS frees you from maintaining rules per list. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From stephen at xemacs.org Sat Jun 30 06:09:41 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 30 Jun 2007 13:09:41 +0900 Subject: [Mailman-Users] Blank Characters Removed from "Subject:" Line In-Reply-To: <46852FE3.5060801@value.net> References: <200706291405.l5TE5BTt029976@britaine.ctd.anl.gov> <46852FE3.5060801@value.net> Message-ID: <87ir9613sq.fsf@uwakimon.sk.tsukuba.ac.jp> Mark Sapiro writes: > But, the fact remains that there are many commonly used MUAs that drop a > whitespace character in unfolding and there's not much we can do about that. I wonder if they're better with RFC 2047. That is, suppose we rendered Subject: Pretend this is a long field as Subject: Pretend this is =?US-ASCII?Q?a=20?= =?US-ASCII?Q?long=20field?= Of course, that would be just unbearably ugly if your MUA doesn't do MIME headers. Maybe the best course would be to use two spaces at the beginning of a folded physical line. From stephen at xemacs.org Sat Jun 30 15:36:19 2007 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Sat, 30 Jun 2007 22:36:19 +0900 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <20070629144443.GA7171@gsp.org> References: <20070629144443.GA7171@gsp.org> Message-ID: <87ved5zhrg.fsf@uwakimon.sk.tsukuba.ac.jp> Rich Kulawiec writes: > Any incoming mail message whose putative sender matches: > > do-not-reply@ > > and which is directed to any of the Mailman standard aliases can > be rejected (not bounced [1]) with SMTP status 550 (extended status > 5.7.1) since either: > > (a) it's a forgery, therefore there's no point in letting > Mailman attempt to emit a reply -- or even in accepting > the message to begin with. > (a) it's not a forgery, therefore there's no point in trying > to reply to it. You have to be careful, though. For several years on one of my lists I had a subscriber whose address was something like (I don't recall exactly) "nobody at not-a-real-address.somewhere.net", which was a perfectly valid address and at which he/she/it did receive mail and from which he/she/it would reply. From rsk at gsp.org Sat Jun 30 22:37:44 2007 From: rsk at gsp.org (Rich Kulawiec) Date: Sat, 30 Jun 2007 16:37:44 -0400 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: References: <20070629182335.GB10401@gsp.org> Message-ID: <20070630203744.GA19133@gsp.org> On Fri, Jun 29, 2007 at 01:25:15PM -0700, John W. Baxter wrote: > I wasn't referring to sender verification callbacks (which we do not use). > I was referring to recipient verification callforwards, where the edge MTA > doesn't know valid recipients but some internal (or even customer) MTA does. > Exim can configure these easily (but that doesn't help because Mailman > doesn't act like an MTA). I don't know about any other MTAs in this regard. Ah, understood. *Those* I highly approve of, since they at least help mitigate accept-then-bounce issues due to non-existent recipient addresses at the final/internal/destination MTA. Whether it's done by callforwards, or LDAP lookups, or script-generated virtual user tables, or aliases, or whatever, I'm all for it. ---Rsk From rsk at gsp.org Sat Jun 30 22:45:53 2007 From: rsk at gsp.org (Rich Kulawiec) Date: Sat, 30 Jun 2007 16:45:53 -0400 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules to frustrate spam/phishing In-Reply-To: <87ved5zhrg.fsf@uwakimon.sk.tsukuba.ac.jp> References: <20070629144443.GA7171@gsp.org> <87ved5zhrg.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: <20070630204553.GA20162@gsp.org> On Sat, Jun 30, 2007 at 10:36:19PM +0900, Stephen J. Turnbull wrote: > You have to be careful, though. For several years on one of my lists > I had a subscriber whose address was something like (I don't recall > exactly) "nobody at not-a-real-address.somewhere.net", which was a > perfectly valid address and at which he/she/it did receive mail and > from which he/she/it would reply. Agreed, care is needed in order to avoid false positives. ("nobody", by the way, is often aliased thus in stock sendmail installations on various 'nix boxes: nobody: /dev/null so while there's nothing wrong with it per se -- and it's not a special address per RFC 2142 -- I find myself wondering how many people have hardwired it into various anti-spam setups. ;-) ) I should probably mention that I'm not a fan of noreply at example.com and similar addresses, which seem to be often used these days for one-way mailing lists: I think *all* messages should be replyable. But I figure that, as a practical matter, as long as so many sites are using that convention, we might as well leverage it to our advantage. ---Rsk From rsk at gsp.org Sat Jun 30 22:53:39 2007 From: rsk at gsp.org (Rich Kulawiec) Date: Sat, 30 Jun 2007 16:53:39 -0400 Subject: [Mailman-Users] specific (1) LHS and (2) sender rules tofrustrate spam/phishing In-Reply-To: References: <20070629182335.GB10401@gsp.org> Message-ID: <20070630205339.GA20335@gsp.org> On Fri, Jun 29, 2007 at 01:35:51PM -0700, Mark Sapiro wrote: > If I were trying to do it, I would use the KNOWN_SPAMMERS list in > mm_cfg.py. For example just listing a few of yours > > KNOWN_SPAMMERS = [ > ('from', '^(.*[\s<])?do-not-reply@'), > ('from', '^(.*[\s<])?acc-overview at paypal.com([\s>].*)?'), > ] That's *very* handy to know. I'm going to do some limited experiments with it over the next week or two, and will be back with results. Thanks! ---Rsk