From majordomo-users-owner@greatcircle.com Tue Feb 5 09:38:52 2008 X-Greylist: delayed 3322 seconds by postgrey-1.24 at mycroft; Tue, 05 Feb 2008 09:38:51 PST Received: from mail.kitusa.com (mail.kitusa.com [63.245.131.67]) by mycroft.greatcircle.com (Postfix) with ESMTP id 11BEE498302 for ; Tue, 5 Feb 2008 09:38:50 -0800 (PST) Received: from HPa300n [63.245.157.26] by mail.kitusa.com with ESMTP (SMTPD-9.23) id A2100E0C; Tue, 05 Feb 2008 10:42:56 -0600 From: "Greg Monaco" To: Cc: "'Duncan Cunningham'" , Subject: FW: MAJORDOMO ABORT (archive2.pl) Date: Tue, 5 Feb 2008 10:42:43 -0600 Message-ID: <032a01c86816$365e5460$0501a8c0@HPa300n> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-index: AchoFRGp4hFtLACgTMmzMMS+kZJMHwAAA/VQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Archive-Number: 200802/1 X-Sequence-Number: 5709 I periodically get this message from majordomo and do not have a clue as to what may be going on. Greg Monaco -----Original Message----- From: majordomo@greatplains.net [mailto:majordomo@greatplains.net] Sent: Tuesday, February 05, 2008 10:35 AM To: Majordomo-Owner@greatplains.net Subject: MAJORDOMO ABORT (archive2.pl) -- MAJORDOMO ABORT (archive2.pl)!! shlock: '/usr/local/etc/majordomo/Archives/gpnnet' does not exist From majordomo-users-owner@greatcircle.com Tue Feb 5 15:03:25 2008 X-Greylist: delayed 2737 seconds by postgrey-1.24 at mycroft; Tue, 05 Feb 2008 15:03:24 PST Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id F07A34983D4 for ; Tue, 5 Feb 2008 15:03:24 -0800 (PST) Received: from KASKY2.esson.net (kasky.priority.usc.edu [128.125.120.92]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.2/8.14.2) with ESMTP id m15MHe0i007954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Feb 2008 14:17:46 -0800 Message-Id: <7.0.1.0.2.20080205141340.023c7b68@esson.net> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Tue, 05 Feb 2008 14:21:05 -0800 To: "Greg Monaco" , From: Ed Kasky Subject: Re: FW: MAJORDOMO ABORT (archive2.pl) Cc: "'Duncan Cunningham'" , In-Reply-To: <032a01c86816$365e5460$0501a8c0@HPa300n> References: <032a01c86816$365e5460$0501a8c0@HPa300n> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (yoda.wrenkasky.com: 128.125.120.92 is authenticated by a trusted mechanism) X-Virus-Scanned: ClamAV 0.92/5699/Tue Feb 5 10:26:26 2008 on yoda.wrenkasky.com X-Virus-Status: Clean X-Archive-Number: 200802/2 X-Sequence-Number: 5710 At 08:42 AM Tuesday, 2/5/2008, Greg Monaco wrote -=> >I periodically get this message from majordomo and do not have a clue as to >what may be going on. > >Greg Monaco > >-----Original Message----- >From: majordomo@greatplains.net [mailto:majordomo@greatplains.net] >Sent: Tuesday, February 05, 2008 10:35 AM >To: Majordomo-Owner@greatplains.net >Subject: MAJORDOMO ABORT (archive2.pl) > >-- > > >MAJORDOMO ABORT (archive2.pl)!! > >shlock: '/usr/local/etc/majordomo/Archives/gpnnet' does not exist MD is telling you that the archive script is trying to write to /usr/local/etc/majordomo/Archives/gpnnet but it does not exist. I am assuming you at one time had archiving set up for a list called gpnnet? If you do and want the list to be archived, this can be resolved by making sure that the dir path exists and that MD can write to it. If not, you should remove the alias that archives. In a sendmail setting, the aliases will look something like this - to get rid of the archiving, you would get rid of the test-archive reference in line 2 and remove the last alias altogether: test: "|/usr/local/majordomo/demime '== /usr/local/majordomo/wrapper resend -l test test-list,nobody'" test-list: :include:/usr/local/majordomo/lists/test, test-archive, test-digestify test-digestify: "|/usr/local/majordomo/digest -r -C -l test-digest test-digest-outgoing" test-digest: test test-digest-outgoing: :include:/usr/local/majordomo/lists/test-digest test-archive: "|/usr/local/majordomo/wrapper archive -f /usr/local/majordomo/archives/test/test -a -M" I hope that is not too much information.... Ed Kasky ~~~~~~~~~ Randomly Generated Quote (225 of 576): "When you come to a roadblock, take a detour." - Mary Kay Ash From majordomo-users-owner@greatcircle.com Thu Feb 7 10:18:05 2008 X-Greylist: delayed 300 seconds by postgrey-1.24 at mycroft; Thu, 07 Feb 2008 10:18:03 PST Received: from fmailhost02.isp.att.net (fmailhost02.isp.att.net [207.115.11.52]) by mycroft.greatcircle.com (Postfix) with ESMTP id BFE45498360 for ; Thu, 7 Feb 2008 10:18:03 -0800 (PST) Received: from [127.0.0.1] (adsl-068-209-223-242.sip.jan.bellsouth.net[68.209.223.242]) by isp.att.net (frfwmhc02) with ESMTP id <20080207181302H0200aofn7e>; Thu, 7 Feb 2008 18:13:02 +0000 X-Originating-IP: [68.209.223.242] Message-ID: <47AB4A24.4060204@bellsouth.net> Date: Thu, 07 Feb 2008 12:12:52 -0600 From: Adam Williams User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: messages bouncing with Message too long (>40000 chars) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200802/3 X-Sequence-Number: 5711 on a mail list I have, messages w/ attachments bounce with the error Message too long (>40000 chars). However, in /usr/local/majordomo/lists/listname.config I have maxlength = 0 so it should let a message of any size go through, right? So why is it bouncing messages >40000 characters? From majordomo-users-owner@greatcircle.com Thu Feb 7 14:01:00 2008 X-Greylist: delayed 809 seconds by postgrey-1.24 at mycroft; Thu, 07 Feb 2008 14:00:59 PST Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2A1E4498429 for ; Thu, 7 Feb 2008 14:00:58 -0800 (PST) Received: from js.berklix.net (p549A5410.dip.t-dialin.net [84.154.84.16]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id m17LlFnx037280; Thu, 7 Feb 2008 21:47:26 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m17Ll5Oe017085; Thu, 7 Feb 2008 22:47:05 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m17LmE7h054480; Thu, 7 Feb 2008 22:48:31 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802072148.m17LmE7h054480@fire.js.berklix.net> To: Adam Williams cc: majordomo-users@greatcircle.com Subject: Re: messages bouncing with Message too long (>40000 chars) From: "Julian Stacey" Organization: http://berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://berklix.com/free/ X-URL: http://berklix.com In-reply-to: Your message "Thu, 07 Feb 2008 12:12:52 CST." <47AB4A24.4060204@bellsouth.net> Date: Thu, 07 Feb 2008 22:48:14 +0100 X-Archive-Number: 200802/4 X-Sequence-Number: 5712 Reference: > From: Adam Williams > Date: Thu, 07 Feb 2008 12:12:52 -0600 > Message-id: <47AB4A24.4060204@bellsouth.net> Adam Williams wrote: > on a mail list I have, messages w/ attachments bounce with the error > Message too long (>40000 chars). However, in > /usr/local/majordomo/lists/listname.config I have > > maxlength = 0 > > so it should let a message of any size go through, right? So why is it > bouncing messages >40000 characters? I dont know the code, but as a C programmer from Way back, if I was debugging it, I would be suspiciously looking for a signed int declarator in the source, that might somehow still be just living in a 16 bit segment world. Which suspicion you might check, if not a programmer, by seeing if messages a little less than 2^15 get through ie 32767 (allow a bit less for header & footer too perhaps ? Or maybe its a simple answer eg some other variable name needed ? -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com From majordomo-users-owner@greatcircle.com Thu Feb 7 14:15:40 2008 Received: from fmailhost02.isp.att.net (fmailhost02.isp.att.net [207.115.11.52]) by mycroft.greatcircle.com (Postfix) with ESMTP id A4A83498428 for ; Thu, 7 Feb 2008 14:15:39 -0800 (PST) Received: from [127.0.0.1] (adsl-068-209-223-242.sip.jan.bellsouth.net[68.209.223.242]) by isp.att.net (frfwmhc02) with ESMTP id <20080207221538H0200aqgoqe>; Thu, 7 Feb 2008 22:15:38 +0000 X-Originating-IP: [68.209.223.242] Message-ID: <47AB830E.10609@bellsouth.net> Date: Thu, 07 Feb 2008 16:15:42 -0600 From: Adam Williams User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Julian Stacey CC: majordomo-users@greatcircle.com Subject: Re: messages bouncing with Message too long (>40000 chars) References: <200802072148.m17LmE7h054480@fire.js.berklix.net> In-Reply-To: <200802072148.m17LmE7h054480@fire.js.berklix.net> Content-Type: multipart/alternative; boundary="------------020603000503040008040704" X-Archive-Number: 200802/5 X-Sequence-Number: 5713 This is a multi-part message in MIME format. --------------020603000503040008040704 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Julian Stacey wrote: > Reference: > >> From: Adam Williams >> Date: Thu, 07 Feb 2008 12:12:52 -0600 >> Message-id: <47AB4A24.4060204@bellsouth.net> >> > > Adam Williams wrote: > >> on a mail list I have, messages w/ attachments bounce with the error >> Message too long (>40000 chars). However, in >> /usr/local/majordomo/lists/listname.config I have >> >> maxlength = 0 >> >> so it should let a message of any size go through, right? So why is it >> bouncing messages >40000 characters? >> > > I dont know the code, but as a C programmer from Way back, if I was > debugging it, I would be suspiciously looking for a signed int > declarator in the source, that might somehow still be just living > in a 16 bit segment world. Which suspicion you might check, if not > a programmer, by seeing if messages a little less than 2^15 get > through ie 32767 (allow a bit less for header & footer too perhaps ? > > Or maybe its a simple answer eg some other variable name needed ? > > I figured it out a little while after posting. The list was named REPP.museum and there existed /usr/local/majordomo/lists/REPP.museum.config and /usr/local/majordomo/lists/repp.musuem.conf. I deleted REPP.museum.config and changed the maxlength = in repp.museum.config and all is well now. --------------020603000503040008040704 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Julian Stacey wrote: 
Reference:
  
From:		Adam Williams <adam_williams@bellsouth.net> 
Date:		Thu, 07 Feb 2008 12:12:52 -0600 
Message-id:	<47AB4A24.4060204@bellsouth.net> 
    

Adam Williams wrote:
  
on a mail list I have, messages w/ attachments bounce with the error 
Message too long (>40000 chars).  However, in 
/usr/local/majordomo/lists/listname.config I have

maxlength = 0

so it should let a message of any size go through, right?  So why is it 
bouncing messages >40000 characters?
    

I dont know the code, but as a C programmer from Way back, if I was
debugging it, I would be suspiciously looking for a signed int
declarator in the source, that might somehow still be just living
in a 16 bit segment world. Which suspicion you might check, if not
a programmer, by seeing if messages a little less than 2^15 get
through ie 32767 (allow a bit less for header & footer too perhaps ?

Or maybe its a simple answer eg some other variable name needed ?
I figured it out a little while after posting.  The list was named REPP.museum and there existed /usr/local/majordomo/lists/REPP.museum.config and /usr/local/majordomo/lists/repp.musuem.conf.  I deleted REPP.museum.config and changed the maxlength = in repp.museum.config and all is well now.
--------------020603000503040008040704-- From majordomo-users-owner@greatcircle.com Thu Feb 7 14:31:40 2008 Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mycroft.greatcircle.com (Postfix) with ESMTP id 09A9D498428 for ; Thu, 7 Feb 2008 14:31:39 -0800 (PST) Received: from js.berklix.net (p549A72D7.dip.t-dialin.net [84.154.114.215]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id m17MVaCs037492; Thu, 7 Feb 2008 22:31:37 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m17MX3tr017435; Thu, 7 Feb 2008 23:33:03 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m17MWrup055456; Thu, 7 Feb 2008 23:32:58 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200802072232.m17MWrup055456@fire.js.berklix.net> To: Adam Williams cc: majordomo-users@greatcircle.com Subject: Re: messages bouncing with Message too long (>40000 chars) In-reply-to: <47AB830E.10609@bellsouth.net> References: <200802072148.m17LmE7h054480@fire.js.berklix.net> <47AB830E.10609@bellsouth.net> Comments: In-reply-to Adam Williams message dated "Thu, 07 Feb 2008 16:15:42 -0600." Date: Thu, 07 Feb 2008 23:32:53 +0100 From: "Julian H. Stacey" X-Archive-Number: 200802/6 X-Sequence-Number: 5714 Adam Williams wrote: > > I dont know the code, but as a C programmer from Way back, if I was > > debugging it, I would be suspiciously looking for a signed int > > declarator in the source, that might somehow still be just living > > in a 16 bit segment world. Which suspicion you might check, if not > > a programmer, by seeing if messages a little less than 2^15 get > > through ie 32767 (allow a bit less for header & footer too perhaps ? > > > > Or maybe its a simple answer eg some other variable name needed ? > > > > > I figured it out a little while after posting. The list was named > REPP.museum and there existed > /usr/local/majordomo/lists/REPP.museum.config and > /usr/local/majordomo/lists/repp.musuem.conf. I deleted > REPP.museum.config and changed the maxlength = in repp.museum.config and > all is well now. Ah good ! ( My soul too deeply scared by decades of Intel segment, pathological ;-) Julian -- Julian Stacey. BSD Unix Linux Net Consultant, Munich. http://berklix.com