From majordomo-users-owner@greatcircle.com Fri Dec 18 08:13:03 2009 X-Greylist: delayed 1982 seconds by postgrey-1.24 at mycroft; Fri, 18 Dec 2009 08:13:02 PST Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id EE76E690063 for ; Fri, 18 Dec 2009 08:13:02 -0800 (PST) Received: from brainiac.com (eno [70.181.43.244]) (authenticated bits=0) by zappa.brainiac.com (8.13.8/8.13.8) with ESMTP id nBIFdv7c000836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 18 Dec 2009 10:39:58 -0500 Date: Fri, 18 Dec 2009 10:39:57 -0500 From: Joe Hartley To: majordomo-users@greatcircle.com Subject: Digestion problem Message-Id: <20091218103957.55552b13.jh@brainiac.com> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.12; i686-pc-linux-gnu) X-Face: e<}kWVz7AOU%7Y[y%"Y%)jByI[9dsnKP{\??7E"4vTGx4){g\C&LaBmH1{dDNf0U_mPBv#c qp\nRqr]T^L:p_H=Tel/;Z$7-C/klmyQ*kB\{},N]n-7*sJ(dYlf(,?f2hekl"0$nD+~T-ZwNK~`oa n"I7[)O/_NOgn@]?b%=6SRU!]O5k9|OA]PF!qIvs>7sE3}Vr*eC|r""6/**uf3ak}Hm.HK$Cri^yyT BzeM Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200912/1 X-Sequence-Number: 5902 I've recently moved my majordomo lists to a new server running CentOS 5.4. Majordomo made the transition well enough, except for one problem that I am having with digests. The incoming messages are correctly written to the digest work directory, but when the digest is created, the first three files are routinely ignored, and the digest is built from messages 004 upward. After that, each message to the list is sent to the digest list individually, presumably because it's over a day older than the 001 message. Manually clearing the digest work directory doesn't fix the problem; the messages start getting written to the directory from 001 as expected, then behave as above. I migrated my server by rsyncing the /usr/local/majordomo and /usr/local/majordomo-work directories to the new server and recompiling wrapper. Overall it seems to be fine. The non-digest lists work as expected, it's just the digestion that is the issue. This is happening on both the lists I have digests for, though one is not terribly active so I don't know if its "breaking point" is the 003 message or not. Has anyone seen this behavior before? Does anyone know if there's a message counter variable stored somewhere that I don't know about that came over with the migration? Thanks in advance for any clues toward solving this issue. -- ====================================================================== Joe Hartley - UNIX/network Consultant - jh@brainiac.com Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Sat Dec 19 22:30:56 2009 X-Greylist: delayed 7202 seconds by postgrey-1.24 at mycroft; Sat, 19 Dec 2009 22:30:55 PST Received: from mail.sonny.com (unknown [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9E51D69001D for ; Sat, 19 Dec 2009 22:30:55 -0800 (PST) Received: from [127.0.0.1] (solara.sonny.com [192.168.1.14]) by minute.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0KUX00J21OJBHA@minute.sonny.com> for majordomo-users@greatcircle.com; Sat, 19 Dec 2009 22:30:48 -0600 (CST) Date: Sat, 19 Dec 2009 22:30:29 -0600 From: Daniel Liston Subject: Re: Digestion problem In-reply-to: <20091218103957.55552b13.jh@brainiac.com> To: Joe Hartley Cc: majordomo-users@greatcircle.com Message-id: <4B2DA865.2030809@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) References: <20091218103957.55552b13.jh@brainiac.com> X-Archive-Number: 200912/2 X-Sequence-Number: 5903 It took me awhile to find this gem, but please let me know if it helps in your situation. In the digest file, please make this "diff" modification: 176c176 foreach (@files) { --- foreach (sort @files) { For any novices following this thread, the above means: Change line 176 from the line before --- to match the line after it. Short version, add the word/command "sort " before @files in parenthesis. Dan Liston Joe Hartley wrote: > I've recently moved my majordomo lists to a new server running CentOS 5.4. > Majordomo made the transition well enough, except for one problem that I > am having with digests. > > The incoming messages are correctly written to the digest work directory, > but when the digest is created, the first three files are routinely > ignored, and the digest is built from messages 004 upward. After that, > each message to the list is sent to the digest list individually, > presumably because it's over a day older than the 001 message. > > Manually clearing the digest work directory doesn't fix the problem; > the messages start getting written to the directory from 001 as expected, > then behave as above. > > I migrated my server by rsyncing the /usr/local/majordomo and > /usr/local/majordomo-work directories to the new server and recompiling > wrapper. Overall it seems to be fine. The non-digest lists work as > expected, it's just the digestion that is the issue. This is happening on > both the lists I have digests for, though one is not terribly active so > I don't know if its "breaking point" is the 003 message or not. > > Has anyone seen this behavior before? Does anyone know if there's a > message counter variable stored somewhere that I don't know about that > came over with the migration? > > Thanks in advance for any clues toward solving this issue. > From majordomo-users-owner@greatcircle.com Sun Dec 20 08:26:55 2009 Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189]) by mycroft.greatcircle.com (Postfix) with ESMTP id 8E77F690053 for ; Sun, 20 Dec 2009 08:26:54 -0800 (PST) Received: from brainiac.com (eno [70.181.43.244]) (authenticated bits=0) by zappa.brainiac.com (8.13.8/8.13.8) with ESMTP id nBKGQqNH017153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 20 Dec 2009 11:26:53 -0500 Date: Sun, 20 Dec 2009 11:26:52 -0500 From: Joe Hartley To: majordomo-users@greatcircle.com Subject: Re: Digestion problem Message-Id: <20091220112652.095f7df5.jh@brainiac.com> In-Reply-To: <4B2DA865.2030809@sonny.org> References: <20091218103957.55552b13.jh@brainiac.com> <4B2DA865.2030809@sonny.org> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.12.12; i686-pc-linux-gnu) X-Face: e<}kWVz7AOU%7Y[y%"Y%)jByI[9dsnKP{\??7E"4vTGx4){g\C&LaBmH1{dDNf0U_mPBv#c qp\nRqr]T^L:p_H=Tel/;Z$7-C/klmyQ*kB\{},N]n-7*sJ(dYlf(,?f2hekl"0$nD+~T-ZwNK~`oa n"I7[)O/_NOgn@]?b%=6SRU!]O5k9|OA]PF!qIvs>7sE3}Vr*eC|r""6/**uf3ak}Hm.HK$Cri^yyT BzeM Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archive-Number: 200912/3 X-Sequence-Number: 5904 On Sat, 19 Dec 2009 22:30:29 -0600 Daniel Liston wrote: > It took me awhile to find this gem, but please let me know if it helps in > your situation. In the digest file, please make this "diff" modification: > > 176c176 > foreach (@files) { > --- > foreach (sort @files) { Brilliant - that did the trick! Another post to the list caused the digest to go out with the 3 older messages as well as the new one, and all the files in the majordomo-work area were cleared out. Many thanks for digging this one up, I really appreciate it and all the continued time you put into this fine piece of software. -- ====================================================================== Joe Hartley - UNIX/network Consultant - jh@brainiac.com Without deviation from the norm, "progress" is not possible. - FZappa From majordomo-users-owner@greatcircle.com Tue Dec 22 00:50:40 2009 X-Greylist: delayed 552 seconds by postgrey-1.24 at mycroft; Tue, 22 Dec 2009 00:50:40 PST Received: from kuller.raad.tartu.ee (kuller.raad.tartu.ee [194.126.106.100]) by mycroft.greatcircle.com (Postfix) with ESMTP id 39BB84B0059 for ; Tue, 22 Dec 2009 00:50:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 52F3A39875 for ; Tue, 22 Dec 2009 10:41:27 +0200 (EET) X-Virus-Scanned: amavisd-new at post.raad.tartu.ee Received: from kuller.raad.tartu.ee ([127.0.0.1]) by localhost (kuller.raad.tartu.ee [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MIb-Akq4+Vy4 for ; Tue, 22 Dec 2009 10:41:22 +0200 (EET) Received: from raad.tartu.ee (lv.raad.tartu.ee [194.126.106.110]) by kuller.raad.tartu.ee (Postfix) with ESMTP id 4E52839823 for ; Tue, 22 Dec 2009 10:41:22 +0200 (EET) Received: from INFO/SpoolDir by raad.tartu.ee (Mercury 1.48); 22 Dec 09 10:41:22 +0200 Received: from SpoolDir by INFO (Mercury 1.48); 22 Dec 09 10:41:19 +0200 Received: from [127.0.0.1] (172.26.1.2) by raad.tartu.ee (Mercury 1.48) with ESMTP; 22 Dec 09 10:41:19 +0200 Message-ID: <4B30862E.8080305@raad.tartu.ee> Date: Tue, 22 Dec 2009 10:41:18 +0200 From: Toomas Aas User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: majordomo-users@greatcircle.com Subject: Using variables in intro Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archive-Number: 200912/4 X-Sequence-Number: 5905 Hello! I'm creating a custom intro for a list, and would like to include some variables in the intro, such as e-mail address of the particular subscription request. Is this possible? I looked at the source and saw that when creating the default intro it uses $subscriber as the placeholder for this, but when I used this in my custom intro it is written verbatim. -- Toomas Aas