From majordomo-users-owner@greatcircle.com Sun Jan 4 12:00:50 2009 X-Greylist: delayed 489 seconds by postgrey-1.24 at mycroft; Sun, 04 Jan 2009 12:00:49 PST Received: from scoprion.bogend.ca (scorpion.bogend.com [139.142.40.60]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7B38B5900D1 for ; Sun, 4 Jan 2009 12:00:49 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id 9F02421C4E6 for ; Sun, 4 Jan 2009 13:37:47 -0600 (CST) X-Virus-Scanned: amavisd-new at bogend.ca Received: from scoprion.bogend.ca ([127.0.0.1]) by localhost (scorpion.bogend.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id XqKWooMwsq-4 for ; Sun, 4 Jan 2009 13:37:39 -0600 (CST) Received: from webmail.flybynightscotch.com (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id 5CDE321C4CA for ; Sun, 4 Jan 2009 13:37:39 -0600 (CST) Received: from 139.142.74.8 (SquirrelMail authenticated user buz) by webmail.flybynightscotch.com with HTTP; Sun, 4 Jan 2009 13:37:39 -0600 (CST) Message-ID: <4571.139.142.74.8.1231097859.squirrel@webmail.flybynightscotch.com> Date: Sun, 4 Jan 2009 13:37:39 -0600 (CST) Subject: Digesting problem From: "Howard R. Hamilton" To: majordomo-users@greatcircle.com User-Agent: SquirrelMail/1.4.8-4.0.1.el5.0.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200901/1 X-Sequence-Number: 5824 Greetings! I have been running a mailing list with majordomo since 2002 (it actually started in 1994 but I was only a subscriber and contributor before that). The list was actually composed of a moderated list, an un-moderated list and a digest of the moderated list. Everything was working fine until I had to move it to a different server (old server was being retired, and the domain was retiring with it.) The old system was on BSD linux, and the new system is on Oracle (Red Hat derived) linux. Since the move, the system has not been able to create digests properly. There are two main symptoms, the size of the digests (set at 28k, and varies from 2k to 15-20k) and the ordering of the email messages (they seem to be put out in a semi-random order). The size problem can be very irritating, because it will start putting out a digest with every new message that occurs. Since I am away from a computer for several days at a time, and the list gets 10-30 emails a day, there can be a lot of single email digests of 2-4K in size. When this problem occurs, I will find numerous emails in the digest storage area of varying age, and will notice that most of those emails stay around for several digest creations. If I trigger digest creation two or three times ("echo mkdigest list passwd | mail majordomo") it will clean out all of the emails in the storage area and then start "sort-of" working (all emails go out, but digest size still varies from 5-15k) for a few days. Unfortunately, those digests never get mailed out, even though they were created and are available from the archive. Has anyone else ever experienced a problem like this, and how did you solve it? BUZ -- ___ Howard R. Hamilton | Life is best when a o__ o__ | |\ howard.hamilton@bogend.ca | little exercise is /| /\ | |X\ www.canfirearms.ca | followed by a glass / > o <\ | |XX\ (306) 286-3379 | of a good red wine. From majordomo-users-owner@greatcircle.com Mon Jan 5 05:57:59 2009 Received: from scoprion.bogend.ca (scorpion.bogend.com [139.142.40.60]) by mycroft.greatcircle.com (Postfix) with ESMTP id DBE98510060 for ; Mon, 5 Jan 2009 05:57:58 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id B879221C499; Mon, 5 Jan 2009 07:43:01 -0600 (CST) X-Virus-Scanned: amavisd-new at bogend.ca Received: from scoprion.bogend.ca ([127.0.0.1]) by localhost (scorpion.bogend.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EnKGKXetMZYn; Mon, 5 Jan 2009 07:43:00 -0600 (CST) Received: from webmail.flybynightscotch.com (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id 5E08A21C48B; Mon, 5 Jan 2009 07:43:00 -0600 (CST) Received: from 139.142.74.8 (SquirrelMail authenticated user buz) by webmail.flybynightscotch.com with HTTP; Mon, 5 Jan 2009 07:43:00 -0600 (CST) Message-ID: <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> In-Reply-To: <4961A361.7060005@sonny.org> References: <4571.139.142.74.8.1231097859.squirrel@webmail.flybynightscotch.com> <4961A361.7060005@sonny.org> Date: Mon, 5 Jan 2009 07:43:00 -0600 (CST) Subject: Re: Digesting problem From: "Howard R. Hamilton" To: "Daniel Liston" Cc: majordomo-users@greatcircle.com, "Howard R. Hamilton" User-Agent: SquirrelMail/1.4.8-4.0.1.el5.0.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200901/2 X-Sequence-Number: 5825 Greetings! Thank you for the quick reply. I am running running Majordomo 1.94.5. The server is up to date on all apps till September 2008 (last major upgrade of all systems then). When I moved the list to the new server, I copied the configuration scripts for the lists exactly, but did a new install of the majordomo software and ran it on a test list for a couple days first. The wrapper file was recompiled during the installation. I created a new UID/GID for majordomo as per the install instructions and set UID/GID to this for all of the majordomo components before do the make / make install. I have only dabbled in Perl a bit, but when I implemented the change suggested below, emacs' syntax highlighting indicated an unclosed single apostrophe in the previous function that might also be a problem. The offending line looks like this: &config'writeconfig($listdir, $opt_l); Is that correct syntax for Perl, or should I close that single apostrophe at the end of that line. It is the last line in that function. Thanks again. BUZ > Hello Howard, > > What version of majordomo are you running? I imagine your new server is also > using new versions of perl, sendmail, etc. Did you maintain the same UID/GID > for the majordomo user, and all/any of it's files, directories, and workspace > when you migrated to the new machine? Did you keep the original scripts and > config files or did you install new? I would assume the wrapper had to be > recompiled to be compatible with the new OS. The numeric uid/gid would come > into play here too. > > Lastly, I do not know the root cause, but there is a simple cure for at least > part of your digest problems if you are running version 1.94.5 of majordomo's > digest script. In diff format; > > 176c176 > - foreach (@files) { > --- > + foreach (sort @files) { > > This translated into english means > change line 176 of the digest file from the matching line starting with a - > to look like the line starting with the +. The plus and minus only indicate > what comes out and what goes back in. They are not part of the line itself. > > If you are running some other version of majordomo, you may find a similar > solution, but the line numbers might not match. > > On new sendmail versions owner/group/other permissions must be set correctly > for everything to work properly too. > > Dan Liston > > Howard R. Hamilton wrote: >> Greetings! >> >> I have been running a mailing list with majordomo since 2002 (it actually >> started in 1994 but I was only a subscriber and contributor before that). >> The >> list was actually composed of a moderated list, an un-moderated list and a >> digest of the moderated list. Everything was working fine until I had to >> move >> it to a different server (old server was being retired, and the domain was >> retiring with it.) >> >> The old system was on BSD linux, and the new system is on Oracle (Red Hat >> derived) linux. Since the move, the system has not been able to create >> digests properly. There are two main symptoms, the size of the digests (set >> at 28k, and varies from 2k to 15-20k) and the ordering of the email messages >> (they seem to be put out in a semi-random order). >> >> The size problem can be very irritating, because it will start putting out a >> digest with every new message that occurs. Since I am away from a computer >> for several days at a time, and the list gets 10-30 emails a day, there can >> be >> a lot of single email digests of 2-4K in size. >> >> When this problem occurs, I will find numerous emails in the digest storage >> area of varying age, and will notice that most of those emails stay around >> for >> several digest creations. If I trigger digest creation two or three times >> ("echo mkdigest list passwd | mail majordomo") it will clean out all of the >> emails in the storage area and then start "sort-of" working (all emails go >> out, but digest size still varies from 5-15k) for a few days. >> Unfortunately, >> those digests never get mailed out, even though they were created and are >> available from the archive. >> >> Has anyone else ever experienced a problem like this, and how did you solve >> it? >> >> BUZ >> > From majordomo-users-owner@greatcircle.com Mon Jan 5 13:21:11 2009 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 21ADB59011A for ; Mon, 5 Jan 2009 13:21:09 -0800 (PST) Received: from magnum.sonny.com (magnum.sonny.com [192.168.1.68]) by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002)) with ESMTP id <0KD00002EOJ1QX@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 05 Jan 2009 15:18:37 -0600 (CST) Date: Mon, 05 Jan 2009 15:21:53 -0600 From: Daniel Liston Subject: Re: Digesting problem In-reply-to: <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> To: majordomo-users@greatcircle.com Cc: "Howard R. Hamilton" Message-id: <496279F1.3000100@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.18 (X11/20081119) References: <4571.139.142.74.8.1231097859.squirrel@webmail.flybynightscotch.com> <4961A361.7060005@sonny.org> <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> X-Archive-Number: 200901/3 X-Sequence-Number: 5826 Howard, This line (or similar) occurs in digest, resend, majordomo, and config_parse.pl so I would NOT add closing a apostrophe. I am sure if you check the old server you will find the same syntax, yet everything was working. Have you verified your maxsize/maxlines etc. in the config file for your digest? Without "fixing what isn't broken", are you seeing expected results now? Dan Liston Howard R. Hamilton wrote: > Greetings! > > Thank you for the quick reply. > > I am running running Majordomo 1.94.5. The server is up to date on all apps > till September 2008 (last major upgrade of all systems then). When I moved > the list to the new server, I copied the configuration scripts for the lists > exactly, but did a new install of the majordomo software and ran it on a test > list for a couple days first. The wrapper file was recompiled during the > installation. I created a new UID/GID for majordomo as per the install > instructions and set UID/GID to this for all of the majordomo components > before do the make / make install. > > I have only dabbled in Perl a bit, but when I implemented the change suggested > below, emacs' syntax highlighting indicated an unclosed single apostrophe in > the previous function that might also be a problem. The offending line looks > like this: > > &config'writeconfig($listdir, $opt_l); > > Is that correct syntax for Perl, or should I close that single apostrophe at > the end of that line. It is the last line in that function. > > Thanks again. > > BUZ > >> Hello Howard, >> >> What version of majordomo are you running? I imagine your new server is also >> using new versions of perl, sendmail, etc. Did you maintain the same UID/GID >> for the majordomo user, and all/any of it's files, directories, and workspace >> when you migrated to the new machine? Did you keep the original scripts and >> config files or did you install new? I would assume the wrapper had to be >> recompiled to be compatible with the new OS. The numeric uid/gid would come >> into play here too. >> >> Lastly, I do not know the root cause, but there is a simple cure for at least >> part of your digest problems if you are running version 1.94.5 of majordomo's >> digest script. In diff format; >> >> 176c176 >> - foreach (@files) { >> --- >> + foreach (sort @files) { >> >> This translated into english means >> change line 176 of the digest file from the matching line starting with a - >> to look like the line starting with the +. The plus and minus only indicate >> what comes out and what goes back in. They are not part of the line itself. >> >> If you are running some other version of majordomo, you may find a similar >> solution, but the line numbers might not match. >> >> On new sendmail versions owner/group/other permissions must be set correctly >> for everything to work properly too. >> >> Dan Liston >> >> Howard R. Hamilton wrote: >>> Greetings! >>> >>> I have been running a mailing list with majordomo since 2002 (it actually >>> started in 1994 but I was only a subscriber and contributor before that). >>> The >>> list was actually composed of a moderated list, an un-moderated list and a >>> digest of the moderated list. Everything was working fine until I had to >>> move >>> it to a different server (old server was being retired, and the domain was >>> retiring with it.) >>> >>> The old system was on BSD linux, and the new system is on Oracle (Red Hat >>> derived) linux. Since the move, the system has not been able to create >>> digests properly. There are two main symptoms, the size of the digests (set >>> at 28k, and varies from 2k to 15-20k) and the ordering of the email messages >>> (they seem to be put out in a semi-random order). >>> >>> The size problem can be very irritating, because it will start putting out a >>> digest with every new message that occurs. Since I am away from a computer >>> for several days at a time, and the list gets 10-30 emails a day, there can >>> be >>> a lot of single email digests of 2-4K in size. >>> >>> When this problem occurs, I will find numerous emails in the digest storage >>> area of varying age, and will notice that most of those emails stay around >>> for >>> several digest creations. If I trigger digest creation two or three times >>> ("echo mkdigest list passwd | mail majordomo") it will clean out all of the >>> emails in the storage area and then start "sort-of" working (all emails go >>> out, but digest size still varies from 5-15k) for a few days. >>> Unfortunately, >>> those digests never get mailed out, even though they were created and are >>> available from the archive. >>> >>> Has anyone else ever experienced a problem like this, and how did you solve >>> it? >>> >>> BUZ >>> > > From majordomo-users-owner@greatcircle.com Mon Jan 5 15:26:02 2009 Received: from scoprion.bogend.ca (scorpion.bogend.com [139.142.40.60]) by mycroft.greatcircle.com (Postfix) with ESMTP id 39DA059015F for ; Mon, 5 Jan 2009 15:26:00 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id BE1D921C490; Mon, 5 Jan 2009 17:28:01 -0600 (CST) X-Virus-Scanned: amavisd-new at bogend.ca Received: from scoprion.bogend.ca ([127.0.0.1]) by localhost (scorpion.bogend.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tG1aXJkMUnxt; Mon, 5 Jan 2009 17:28:00 -0600 (CST) Received: from webmail.flybynightscotch.com (localhost.localdomain [127.0.0.1]) by scoprion.bogend.ca (Postfix) with ESMTP id F04CD21C48D; Mon, 5 Jan 2009 17:27:59 -0600 (CST) Received: from 139.142.74.8 (SquirrelMail authenticated user buz) by webmail.flybynightscotch.com with HTTP; Mon, 5 Jan 2009 17:27:59 -0600 (CST) Message-ID: <3899.139.142.74.8.1231198079.squirrel@webmail.flybynightscotch.com> In-Reply-To: <496279F1.3000100@sonny.org> References: <4571.139.142.74.8.1231097859.squirrel@webmail.flybynightscotch.com> <4961A361.7060005@sonny.org> <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> <496279F1.3000100@sonny.org> Date: Mon, 5 Jan 2009 17:27:59 -0600 (CST) Subject: Re: Digesting problem From: "Howard R. Hamilton" To: "Daniel Liston" Cc: majordomo-users@greatcircle.com, "Howard R. Hamilton" User-Agent: SquirrelMail/1.4.8-4.0.1.el5.0.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Archive-Number: 200901/4 X-Sequence-Number: 5827 Greetings Again! I cleaned up all of the old letters before the small change, and have just had enough traffic for a single digest, but it was both the right size and in the proper order, so I am hoping that the problem is solved. Thanks again for your help. BUZ > Howard, > > This line (or similar) occurs in digest, resend, majordomo, and > config_parse.pl > so I would NOT add closing a apostrophe. I am sure if you check the old > server > you will find the same syntax, yet everything was working. > > Have you verified your maxsize/maxlines etc. in the config file for your > digest? > > Without "fixing what isn't broken", are you seeing expected results now? > > Dan Liston > > Howard R. Hamilton wrote: >> Greetings! >> >> Thank you for the quick reply. >> >> I am running running Majordomo 1.94.5. The server is up to date on all apps >> till September 2008 (last major upgrade of all systems then). When I moved >> the list to the new server, I copied the configuration scripts for the lists >> exactly, but did a new install of the majordomo software and ran it on a >> test >> list for a couple days first. The wrapper file was recompiled during the >> installation. I created a new UID/GID for majordomo as per the install >> instructions and set UID/GID to this for all of the majordomo components >> before do the make / make install. >> >> I have only dabbled in Perl a bit, but when I implemented the change >> suggested >> below, emacs' syntax highlighting indicated an unclosed single apostrophe in >> the previous function that might also be a problem. The offending line >> looks >> like this: >> >> &config'writeconfig($listdir, $opt_l); >> >> Is that correct syntax for Perl, or should I close that single apostrophe at >> the end of that line. It is the last line in that function. >> >> Thanks again. >> >> BUZ >> >>> Hello Howard, >>> >>> What version of majordomo are you running? I imagine your new server is >>> also >>> using new versions of perl, sendmail, etc. Did you maintain the same >>> UID/GID >>> for the majordomo user, and all/any of it's files, directories, and >>> workspace >>> when you migrated to the new machine? Did you keep the original scripts >>> and >>> config files or did you install new? I would assume the wrapper had to be >>> recompiled to be compatible with the new OS. The numeric uid/gid would >>> come >>> into play here too. >>> >>> Lastly, I do not know the root cause, but there is a simple cure for at >>> least >>> part of your digest problems if you are running version 1.94.5 of >>> majordomo's >>> digest script. In diff format; >>> >>> 176c176 >>> - foreach (@files) { >>> --- >>> + foreach (sort @files) { >>> >>> This translated into english means >>> change line 176 of the digest file from the matching line starting with a - >>> to look like the line starting with the +. The plus and minus only >>> indicate >>> what comes out and what goes back in. They are not part of the line >>> itself. >>> >>> If you are running some other version of majordomo, you may find a similar >>> solution, but the line numbers might not match. >>> >>> On new sendmail versions owner/group/other permissions must be set >>> correctly >>> for everything to work properly too. >>> >>> Dan Liston >>> >>> Howard R. Hamilton wrote: >>>> Greetings! >>>> >>>> I have been running a mailing list with majordomo since 2002 (it actually >>>> started in 1994 but I was only a subscriber and contributor before that). >>>> The >>>> list was actually composed of a moderated list, an un-moderated list and a >>>> digest of the moderated list. Everything was working fine until I had to >>>> move >>>> it to a different server (old server was being retired, and the domain was >>>> retiring with it.) >>>> >>>> The old system was on BSD linux, and the new system is on Oracle (Red Hat >>>> derived) linux. Since the move, the system has not been able to create >>>> digests properly. There are two main symptoms, the size of the digests >>>> (set >>>> at 28k, and varies from 2k to 15-20k) and the ordering of the email >>>> messages >>>> (they seem to be put out in a semi-random order). >>>> >>>> The size problem can be very irritating, because it will start putting out >>>> a >>>> digest with every new message that occurs. Since I am away from a >>>> computer >>>> for several days at a time, and the list gets 10-30 emails a day, there >>>> can >>>> be >>>> a lot of single email digests of 2-4K in size. >>>> >>>> When this problem occurs, I will find numerous emails in the digest >>>> storage >>>> area of varying age, and will notice that most of those emails stay around >>>> for >>>> several digest creations. If I trigger digest creation two or three times >>>> ("echo mkdigest list passwd | mail majordomo") it will clean out all of >>>> the >>>> emails in the storage area and then start "sort-of" working (all emails go >>>> out, but digest size still varies from 5-15k) for a few days. >>>> Unfortunately, >>>> those digests never get mailed out, even though they were created and are >>>> available from the archive. >>>> >>>> Has anyone else ever experienced a problem like this, and how did you >>>> solve >>>> it? >>>> >>>> BUZ >>>> >> >> > From majordomo-users-owner@greatcircle.com Tue Jan 6 18:31:46 2009 X-Greylist: delayed 1687 seconds by postgrey-1.24 at mycroft; Tue, 06 Jan 2009 18:26:36 PST Received: from sbh2.songbird.com (sbh2.songbird.com [72.52.113.2]) by mycroft.greatcircle.com (Postfix) with ESMTP id ABA96590172 for ; Tue, 6 Jan 2009 18:26:36 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by sbh2.songbird.com (8.13.8/8.13.8) with ESMTP id n071wT92011461 for ; Tue, 6 Jan 2009 17:58:29 -0800 Date: Tue, 6 Jan 2009 17:58:28 -0800 From: kent@songbird.com To: majordomo-users@greatcircle.com Subject: Re: Digesting problem Message-ID: <20090107015827.GR28110@lark.songbird.com> Mail-Followup-To: majordomo-users@greatcircle.com References: <4571.139.142.74.8.1231097859.squirrel@webmail.flybynightscotch.com> <4961A361.7060005@sonny.org> <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2029.139.142.74.8.1231162980.squirrel@webmail.flybynightscotch.com> User-Agent: Mutt/1.5.11 X-Archive-Number: 200901/5 X-Sequence-Number: 5828 On Mon, Jan 05, 2009 at 07:43:00AM -0600, Howard R. Hamilton wrote: [...] > I have only dabbled in Perl a bit, but when I implemented the change suggested > below, emacs' syntax highlighting indicated an unclosed single apostrophe in > the previous function that might also be a problem. The offending line looks > like this: > > &config'writeconfig($listdir, $opt_l); This is obsolete perl syntax. More modern perl would write that line as: config::writeconfig($listdir,$opt_l); However, it still works with the apostrophe. > Is that correct syntax for Perl, or should I close that single apostrophe at > the end of that line. It is the last line in that function. Don't touch it :-) Kent