From majordomo-users-owner@greatcircle.com Mon Sep 1 22:51:10 2008 Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 51C7F498368 for ; Mon, 1 Sep 2008 22:51:10 -0700 (PDT) Received: from cloud.ccsf.cc.ca.us (localhost [127.0.0.1]) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2) with ESMTP id m825e3QK059797; Mon, 1 Sep 2008 22:40:03 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2/Submit) with ESMTP id m825e33X059794; Mon, 1 Sep 2008 22:40:03 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Date: Mon, 1 Sep 2008 22:40:03 -0700 (PDT) From: "Joe R. Jah" To: Ed Kasky cc: majordomo-users@greatcircle.com Subject: Re: bounce / bounce-remind not working properly In-Reply-To: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> Message-ID: <20080901110926.S58509@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200809/1 X-Sequence-Number: 5791 On Sun, 31 Aug 2008, Ed Kasky wrote: > Date: Sun, 31 Aug 2008 12:48:26 -0700 > From: Ed Kasky > To: majordomo-users@greatcircle.com > Subject: bounce / bounce-remind not working properly > > I just realized that the bounce / bounce-remind scripts are not doing > everything they should be doing. The message from bounce-remind says: > > "The comment for each address shows the date it was moved, > and the first list it was removed from." > > However it does not contain the list or the date, just the email address that > was moved to the bounces list. > > Majordomo 1.94.5 > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2 > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > Where is it supposed to keep that information? > > Ed http://www.greatcircle.com/majordomo/FAQ.html#3.2 Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Tue Sep 2 05:53:06 2008 Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id F12B84D00E2 for ; Tue, 2 Sep 2008 05:53:05 -0700 (PDT) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id m82CfnhI006961 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 Sep 2008 05:41:55 -0700 Message-Id: <200809021241.m82CfnhI006961@yoda.wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 02 Sep 2008 05:41:50 -0700 To: "Joe R. Jah" From: Ed Kasky Subject: Re: bounce / bounce-remind not working properly Cc: majordomo-users@greatcircle.com In-Reply-To: <20080901110926.S58509@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> <20080901110926.S58509@cloud.ccsf.cc.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Received-SPF: pass (yoda.wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Archive-Number: 200809/2 X-Sequence-Number: 5792 At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=> >On Sun, 31 Aug 2008, Ed Kasky wrote: > > > Date: Sun, 31 Aug 2008 12:48:26 -0700 > > From: Ed Kasky > > To: majordomo-users@greatcircle.com > > Subject: bounce / bounce-remind not working properly > > > > I just realized that the bounce / bounce-remind scripts are not doing > > everything they should be doing. The message from bounce-remind says: > > > > "The comment for each address shows the date it was moved, > > and the first list it was removed from." > > > > However it does not contain the list or the date, just the email > address that > > was moved to the bounces list. > > > > Majordomo 1.94.5 > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2 > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > > > Where is it supposed to keep that information? > > > > Ed > >http://www.greatcircle.com/majordomo/FAQ.html#3.2 That much I get. It's the following in the faq and the instructions that is not happening: "The majordomo maintainer then runs (out of cron) the 'bounce-remind' script periodically, which sends mail to all the people on the bounces list, saying essentially "you were removed from list 'foo' because mail to you bounced. To subscribe yourself back to the list, send the following commands ...". There's no facility yet for trimming the bounces list, but it's easy to write one because the date the person was added to the bounces list is included" The date is included in the email from 'bounce' but not 'bounce-remind' to the user. Should the date be included somewhere in the bounces list? Ed ........................................................................... Randomly Generated Quote (1026 of 1434): Readers may be divided into four classes: 1. Sponges, who absorb all that they read and return it in nearly the same state, only a little dirtied. 2. Sand-glasses, who retain nothing and are content to get through a book for the sake of getting through the time. 3. Strain-bags, who retain merely the dregs of what they read. 4. Mogul diamonds, equally rare and valuable, who profit by what they read, and enable others to profit by it also. -Samuel Taylor Coleridge, poet, critic (1772-1834) From majordomo-users-owner@greatcircle.com Tue Sep 2 20:39:57 2008 Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 9B3E34D00F6 for ; Tue, 2 Sep 2008 20:39:55 -0700 (PDT) Received: from cloud.ccsf.cc.ca.us (localhost [127.0.0.1]) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2) with ESMTP id m833SdrT089939; Tue, 2 Sep 2008 20:28:39 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2/Submit) with ESMTP id m833SdRQ089936; Tue, 2 Sep 2008 20:28:39 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Date: Tue, 2 Sep 2008 20:28:39 -0700 (PDT) From: "Joe R. Jah" To: Ed Kasky cc: majordomo-users@greatcircle.com Subject: Re: bounce / bounce-remind not working properly In-Reply-To: <200809021241.m82CfnhI006961@yoda.wrenkasky.com> Message-ID: <20080902200449.I86065@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> <20080901110926.S58509@cloud.ccsf.cc.ca.us> <200809021241.m82CfnhI006961@yoda.wrenkasky.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200809/3 X-Sequence-Number: 5793 On Tue, 2 Sep 2008, Ed Kasky wrote: > Date: Tue, 02 Sep 2008 05:41:50 -0700 > From: Ed Kasky > To: Joe R. Jah > Cc: majordomo-users@greatcircle.com > Subject: Re: bounce / bounce-remind not working properly > > At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=> > > On Sun, 31 Aug 2008, Ed Kasky wrote: > > > > > Date: Sun, 31 Aug 2008 12:48:26 -0700 > > > From: Ed Kasky > > > To: majordomo-users@greatcircle.com > > > Subject: bounce / bounce-remind not working properly > > > > > > I just realized that the bounce / bounce-remind scripts are not doing > > > everything they should be doing. The message from bounce-remind says: > > > > > > "The comment for each address shows the date it was moved, > > > and the first list it was removed from." > > > > > > However it does not contain the list or the date, just the email address that > > > was moved to the bounces list. > > > > > > Majordomo 1.94.5 > > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2 > > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > > > > > Where is it supposed to keep that information? > > > > > > Ed > > > > http://www.greatcircle.com/majordomo/FAQ.html#3.2 > > > That much I get. It's the following in the faq and the instructions that is > not happening: > > "The majordomo maintainer then runs (out of cron) the 'bounce-remind' script > periodically, which sends mail to all the people on the bounces list, saying > essentially "you were removed from list 'foo' because mail to you bounced. To > subscribe yourself back to the list, send the following commands ...". There's > no facility yet for trimming the bounces list, but it's easy to write one > because the date the person was added to the bounces list is included" > > The date is included in the email from 'bounce' but not 'bounce-remind' to the > user. > > Should the date be included somewhere in the bounces list? Yes it should, but you and/or your list owners must first run the bounce command to populate the bounces list in the right format: someone@somewhere.com (20080822 somelist) someoneelse@somewherelse.com (20080818 someotherlist) ... The bounce-remind only lists what is in the bounces list. Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Tue Sep 2 21:35:41 2008 Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 4B9EF4D00FF for ; Tue, 2 Sep 2008 21:35:40 -0700 (PDT) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id m834OHu3027766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 2 Sep 2008 21:24:23 -0700 Message-Id: <200809030424.m834OHu3027766@yoda.wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 02 Sep 2008 21:24:17 -0700 To: "Joe R. Jah" From: Ed Kasky Subject: Re: bounce / bounce-remind not working properly Cc: majordomo-users@greatcircle.com In-Reply-To: <20080902200449.I86065@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> <20080901110926.S58509@cloud.ccsf.cc.ca.us> <200809021241.m82CfnhI006961@yoda.wrenkasky.com> <20080902200449.I86065@cloud.ccsf.cc.ca.us> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=====================_203558937==.ALT" Received-SPF: pass (yoda.wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Archive-Number: 200809/4 X-Sequence-Number: 5794 --=====================_203558937==.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 08:28 PM Tuesday, 9/2/2008, Joe R. Jah wrote -=> >On Tue, 2 Sep 2008, Ed Kasky wrote: > > > Date: Tue, 02 Sep 2008 05:41:50 -0700 > > From: Ed Kasky > > To: Joe R. Jah > > Cc: majordomo-users@greatcircle.com > > Subject: Re: bounce / bounce-remind not working properly > > > > At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=> > > > On Sun, 31 Aug 2008, Ed Kasky wrote: > > > > > > > Date: Sun, 31 Aug 2008 12:48:26 -0700 > > > > From: Ed Kasky > > > > To: majordomo-users@greatcircle.com > > > > Subject: bounce / bounce-remind not working properly > > > > > > > > I just realized that the bounce / bounce-remind scripts are not doing > > > > everything they should be doing. The message from bounce-remind says: > > > > > > > > "The comment for each address shows the date it was moved, > > > > and the first list it was removed from." > > > > > > > > However it does not contain the list or the date, just the > email address that > > > > was moved to the bounces list. > > > > > > > > Majordomo 1.94.5 > > > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2 > > > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > > > > > > > Where is it supposed to keep that information? > > > > > > > > Ed > > > > > > http://www.greatcircle.com/majordomo/FAQ.html#3.2 > > > > > > That much I get. It's the following in the faq and the > instructions that is > > not happening: > > > > "The majordomo maintainer then runs (out of cron) the > 'bounce-remind' script > > periodically, which sends mail to all the people on the bounces > list, saying > > essentially "you were removed from list 'foo' because mail to you > bounced. To > > subscribe yourself back to the list, send the following commands > ...". There's > > no facility yet for trimming the bounces list, but it's easy to write one > > because the date the person was added to the bounces list is included" > > > > The date is included in the email from 'bounce' but not > 'bounce-remind' to the > > user. > > > > Should the date be included somewhere in the bounces list? > >Yes it should, but you and/or your list owners must first run the bounce >command to populate the bounces list in the right format: > >someone@somewhere.com (20080822 somelist) >someoneelse@somewherelse.com (20080818 someotherlist) >... > >The bounce-remind only lists what is in the bounces list. That's the problem... A command of "bounce this-list user@fubar.com" will mail the following message to Majordomo@This.COM: approve passwd1 unsubscribe this-list user@fubar.com approve passwd3 subscribe bounces user@fubar.com (930401 this-list) This part works fine. However, the bounces list is not getting populated with the date and list in ()'s as in your example above. It is only getting populated with the email address. ........................................................................... Randomly Generated Quote (468 of 1434): Better to light one candle than to curse the darkness. -- motto of the Christopher Society --=====================_203558937==.ALT Content-Type: text/html; charset="us-ascii" At 08:28 PM Tuesday, 9/2/2008, Joe R. Jah wrote -=>
On Tue, 2 Sep 2008, Ed Kasky wrote:

> Date: Tue, 02 Sep 2008 05:41:50 -0700
> From: Ed Kasky <ed@esson.net>
> To: Joe R. Jah <jjah@cloud.ccsf.cc.ca.us>
> Cc: majordomo-users@greatcircle.com
> Subject: Re: bounce / bounce-remind not working properly
>
> At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=>
> > On Sun, 31 Aug 2008, Ed Kasky wrote:
> >
> > > Date: Sun, 31 Aug 2008 12:48:26 -0700
> > > From: Ed Kasky <ed@esson.net>
> > > To: majordomo-users@greatcircle.com
> > > Subject: bounce / bounce-remind not working properly
> > >
> > > I just realized that the bounce / bounce-remind scripts are not doing
> > > everything they should be doing.  The message from bounce-remind says:
> > >
> > > "The comment for each address shows the date it was moved,
> > > and the first list it was removed from."
> > >
> > > However it does not contain the list or the date, just the email address that
> > > was moved to the bounces list.
> > >
> > > Majordomo 1.94.5
> > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2
> > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46
> > >
> > > Where is it supposed to keep that information?
> > >
> > > Ed
> >
> > http://www.greatcircle.com/majordomo/FAQ.html#3.2
>
>
> That much I get.  It's the following in the faq and the instructions that is
> not happening:
>
> "The majordomo maintainer then runs (out of cron) the 'bounce-remind' script
> periodically, which sends mail to all the people on the bounces list, saying
> essentially "you were removed from list 'foo' because mail to you bounced. To
> subscribe yourself back to the list, send the following commands ...". There's
> no facility yet for trimming the bounces list, but it's easy to write one
> because the date the person was added to the bounces list is included"
>
> The date is included in the email from 'bounce' but not 'bounce-remind' to the
> user.
>
> Should the date be included somewhere in the bounces list?

Yes it should, but you and/or your list owners must first run the bounce
command to populate the bounces list in the right format:

someone@somewhere.com (20080822 somelist)
someoneelse@somewherelse.com (20080818 someotherlist)
...

The bounce-remind only lists what is in the bounces list.

That's the problem...

A command of "bounce this-list user@fubar.com" will mail the following message to Majordomo@This.COM: 
   approve passwd1 unsubscribe this-list user@fubar.com
   approve passwd3 subscribe bounces user@fubar.com (930401
this-list)
This part works fine.  However, the bounces list is not getting populated with the date and list in ()'s as in your example above.  It is only getting populated with the email address.

...........................................................................
Randomly Generated Quote (468 of 1434):
Better to light one candle than to curse the darkness.
                -- motto of the Christopher Society
--=====================_203558937==.ALT-- From majordomo-users-owner@greatcircle.com Tue Sep 2 22:29:35 2008 Received: from cloud.ccsf.cc.ca.us (cloud.ccsf.cc.ca.us [147.144.1.212]) by mycroft.greatcircle.com (Postfix) with ESMTP id 7E7A9510017 for ; Tue, 2 Sep 2008 22:29:34 -0700 (PDT) Received: from cloud.ccsf.cc.ca.us (localhost [127.0.0.1]) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2) with ESMTP id m835IIvV009949; Tue, 2 Sep 2008 22:18:18 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Received: from localhost (jjah@localhost) by cloud.ccsf.cc.ca.us (8.14.2/8.14.2/Submit) with ESMTP id m835IIfn009946; Tue, 2 Sep 2008 22:18:18 -0700 (PDT) (envelope-from jjah@cloud.ccsf.cc.ca.us) Date: Tue, 2 Sep 2008 22:18:18 -0700 (PDT) From: "Joe R. Jah" To: Ed Kasky cc: majordomo-users@greatcircle.com Subject: Re: bounce / bounce-remind not working properly In-Reply-To: <200809030424.m834OHu3027766@yoda.wrenkasky.com> Message-ID: <20080902221049.V8325@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> <20080901110926.S58509@cloud.ccsf.cc.ca.us> <200809021241.m82CfnhI006961@yoda.wrenkasky.com> <20080902200449.I86065@cloud.ccsf.cc.ca.us> <200809030424.m834OHu3027766@yoda.wrenkasky.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200809/5 X-Sequence-Number: 5795 On Tue, 2 Sep 2008, Ed Kasky wrote: > Date: Tue, 02 Sep 2008 21:24:17 -0700 > From: Ed Kasky > To: Joe R. Jah > Cc: majordomo-users@greatcircle.com > Subject: Re: bounce / bounce-remind not working properly > > At 08:28 PM Tuesday, 9/2/2008, Joe R. Jah wrote -=> > > On Tue, 2 Sep 2008, Ed Kasky wrote: > > > > > Date: Tue, 02 Sep 2008 05:41:50 -0700 > > > From: Ed Kasky > > > To: Joe R. Jah > > > Cc: majordomo-users@greatcircle.com > > > Subject: Re: bounce / bounce-remind not working properly > > > > > > At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=> > > > > On Sun, 31 Aug 2008, Ed Kasky wrote: > > > > > > > > > Date: Sun, 31 Aug 2008 12:48:26 -0700 > > > > > From: Ed Kasky > > > > > To: majordomo-users@greatcircle.com > > > > > Subject: bounce / bounce-remind not working properly > > > > > > > > > > I just realized that the bounce / bounce-remind scripts are not doing > > > > > everything they should be doing. The message from bounce-remind says: > > > > > > > > > > "The comment for each address shows the date it was moved, > > > > > and the first list it was removed from." > > > > > > > > > > However it does not contain the list or the date, just the email > > address that > > > > > was moved to the bounces list. > > > > > > > > > > Majordomo 1.94.5 > > > > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with bounce.2 > > > > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > > > > > > > > > Where is it supposed to keep that information? > > > > > > > > > > Ed > > > > > > > > http://www.greatcircle.com/majordomo/FAQ.html#3.2 > > > > > > > > > That much I get. It's the following in the faq and the instructions that > > is > > > not happening: > > > > > > "The majordomo maintainer then runs (out of cron) the 'bounce-remind' > > script > > > periodically, which sends mail to all the people on the bounces list, > > saying > > > essentially "you were removed from list 'foo' because mail to you bounced. > > To > > > subscribe yourself back to the list, send the following commands ...". > > There's > > > no facility yet for trimming the bounces list, but it's easy to write one > > > because the date the person was added to the bounces list is included" > > > > > > The date is included in the email from 'bounce' but not 'bounce-remind' to > > the > > > user. > > > > > > Should the date be included somewhere in the bounces list? > > > > Yes it should, but you and/or your list owners must first run the bounce > > command to populate the bounces list in the right format: > > > > someone@somewhere.com (20080822 somelist) > > someoneelse@somewherelse.com (20080818 someotherlist) > > ... > > > > The bounce-remind only lists what is in the bounces list. > > That's the problem... > > A command of "bounce this-list user@fubar.com" will mail the following message > to Majordomo@This.COM: > approve passwd1 unsubscribe this-list user@fubar.com > approve passwd3 subscribe bounces user@fubar.com (930401 this-list) > > This part works fine. However, the bounces list is not getting populated with > the date and list in ()'s as in your example above. It is only getting > populated with the email address. Set not to strip addresses in bounces.config: strip = no Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jjah@cloud.ccsf.cc.ca.us From majordomo-users-owner@greatcircle.com Wed Sep 3 05:03:24 2008 Received: from yoda.wrenkasky.com (esson.net [216.102.129.43]) by mycroft.greatcircle.com (Postfix) with ESMTP id 3D2064D00BF for ; Wed, 3 Sep 2008 05:03:23 -0700 (PDT) Received: from EDS.esson.net (eds.wrenkasky.com [10.10.10.11]) (authenticated bits=0) by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id m83Bpve9027612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 3 Sep 2008 04:52:02 -0700 Message-Id: <200809031152.m83Bpve9027612@yoda.wrenkasky.com> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 03 Sep 2008 04:51:59 -0700 To: "Joe R. Jah" From: Ed Kasky Subject: Re: bounce / bounce-remind not working properly Cc: majordomo-users@greatcircle.com In-Reply-To: <20080902221049.V8325@cloud.ccsf.cc.ca.us> References: <200808311948.m7VJmX6D028216@yoda.wrenkasky.com> <20080901110926.S58509@cloud.ccsf.cc.ca.us> <200809021241.m82CfnhI006961@yoda.wrenkasky.com> <20080902200449.I86065@cloud.ccsf.cc.ca.us> <200809030424.m834OHu3027766@yoda.wrenkasky.com> <20080902221049.V8325@cloud.ccsf.cc.ca.us> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Received-SPF: pass (yoda.wrenkasky.com: 10.10.10.11 is authenticated by a trusted mechanism) X-Archive-Number: 200809/6 X-Sequence-Number: 5796 At 10:18 PM Tuesday, 9/2/2008, Joe R. Jah wrote -=3D> >On Tue, 2 Sep 2008, Ed Kasky wrote: > > > Date: Tue, 02 Sep 2008 21:24:17 -0700 > > From: Ed Kasky > > To: Joe R. Jah > > Cc: majordomo-users@greatcircle.com > > Subject: Re: bounce / bounce-remind not working properly > > > > At 08:28 PM Tuesday, 9/2/2008, Joe R. Jah wrote -=3D> > > > On Tue, 2 Sep 2008, Ed Kasky wrote: > > > > > > > Date: Tue, 02 Sep 2008 05:41:50 -0700 > > > > From: Ed Kasky > > > > To: Joe R. Jah > > > > Cc: majordomo-users@greatcircle.com > > > > Subject: Re: bounce / bounce-remind not working properly > > > > > > > > At 10:40 PM Monday, 9/1/2008, Joe R. Jah wrote -=3D> > > > > > On Sun, 31 Aug 2008, Ed Kasky wrote: > > > > > > > > > > > Date: Sun, 31 Aug 2008 12:48:26 -0700 > > > > > > From: Ed Kasky > > > > > > To: majordomo-users@greatcircle.com > > > > > > Subject: bounce / bounce-remind not working properly > > > > > > > > > > > > I just realized that the bounce /=20 > bounce-remind scripts are not doing > > > > > > everything they should be doing. The=20 > message from bounce-remind says: > > > > > > > > > > > > "The comment for each address shows the date it was moved, > > > > > > and the first list it was removed from." > > > > > > > > > > > > However it does not contain the list or the date, just the email > > > address that > > > > > > was moved to the bounces list. > > > > > > > > > > > > Majordomo 1.94.5 > > > > > > bounce is Revision: 1.11, 2000/01/07 14:09:24 patched with= bounce.2 > > > > > > bounce-remind is Revision: 1.9, 1996/12/09 16:49:46 > > > > > > > > > > > > Where is it supposed to keep that information? > > > > > > > > > > > > Ed > > > > > > > > > > http://www.greatcircle.com/majordomo/FAQ.html#3.2 > > > > > > > > > > > > That much I get. It's the following in=20 > the faq and the instructions that > > > is > > > > not happening: > > > > > > > > "The majordomo maintainer then runs (out of cron) the= 'bounce-remind' > > > script > > > > periodically, which sends mail to all the people on the bounces= list, > > > saying > > > > essentially "you were removed from list=20 > 'foo' because mail to you bounced. > > > To > > > > subscribe yourself back to the list, send the following commands= ...". > > > There's > > > > no facility yet for trimming the bounces=20 > list, but it's easy to write one > > > > because the date the person was added to the bounces list is= included" > > > > > > > > The date is included in the email from=20 > 'bounce' but not 'bounce-remind' to > > > the > > > > user. > > > > > > > > Should the date be included somewhere in the bounces list? > > > > > > Yes it should, but you and/or your list owners must first run the= bounce > > > command to populate the bounces list in the right format: > > > > > > someone@somewhere.com (20080822 somelist) > > > someoneelse@somewherelse.com (20080818 someotherlist) > > > ... > > > > > > The bounce-remind only lists what is in the bounces list. > > > > That's the problem... > > > > A command of "bounce this-list=20 > user@fubar.com" will mail the following message > > to Majordomo@This.COM: > > approve passwd1 unsubscribe this-list user@fubar.com > > approve passwd3 subscribe bounces user@fubar.com (930401 this-list) > > > > This part works fine. However, the bounces=20 > list is not getting populated with > > the date and list in ()'s as in your example above. It is only getting > > populated with the email address. > >Set not to strip addresses in bounces.config: > >strip =3D no Et Voil=E0! After all this time, that is one setting I didn't know existed. Thanks! Ed ........................................................................... Randomly Generated Quote (1344 of 1434): What you don't know can hurt you, only you won't know it. From majordomo-users-owner@greatcircle.com Tue Sep 9 10:53:45 2008 X-Greylist: delayed 10737 seconds by postgrey-1.24 at mycroft; Tue, 09 Sep 2008 10:53:43 PDT Received: from mail-gx0-f15.google.com (mail-gx0-f15.google.com [209.85.217.15]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2CEAF4D0106 for ; Tue, 9 Sep 2008 10:53:42 -0700 (PDT) Received: by gxk8 with SMTP id 8so11148968gxk.14 for ; Tue, 09 Sep 2008 10:53:41 -0700 (PDT) Received: by 10.100.225.19 with SMTP id x19mr17331694ang.152.1220970711650; Tue, 09 Sep 2008 07:31:51 -0700 (PDT) Received: by 10.70.80.11 with HTTP; Tue, 9 Sep 2008 07:31:51 -0700 (PDT) Message-ID: <21d95d450809090731i2bade25kc49e96b92ba1f906@mail.gmail.com> Date: Tue, 9 Sep 2008 09:31:51 -0500 From: "Randall Belk" To: majordomo-users@greatcircle.com Subject: Majordomo and gmail MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4968_16495652.1220970711622" X-Archive-Number: 200809/7 X-Sequence-Number: 5797 ------=_Part_4968_16495652.1220970711622 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I maintain a majordomo server for an organization that recently switched to Google Apps for email. With their old email provider they would send an email to one of the lists and as the emails were sent out by the server they would get their own email back. They came to depend on this "Feature" as confirmation that everything was working. Gmail looks at an incoming message and determines (by message-id I think) if this is a message that originated within the destination account and drops it if it did. The result is that everybody thinks the server isn't working when actually it is because they don't get a mail back. I'm pretty sure gmail is keying on the id because I can change other parameters of the message (title, add footer, reply-to, etc) but the message still gets dropped because the id is the same. Has anyone dealt with this issue in the past? After allot of thinking and searching I haven't come up with a nice solution. I think mailman and maybe majordomo 2 both have an 'ack' feature, but I would hate to have to change systems entirely just to get it. Randall ------=_Part_4968_16495652.1220970711622 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

I maintain a majordomo server for an organization that recently switched to Google Apps for email.

With their old email provider they would send an email to one of the lists and as the emails were sent out by the server they would get their own email back.  They came to depend on this "Feature" as confirmation that everything was working.

Gmail looks at an incoming message and determines (by message-id I think) if this is a message that  originated within the destination account and drops it if it did.  The result is that everybody thinks the server isn't working when actually it is because they don't get a mail back.  I'm pretty sure gmail is keying on the id because I can change other parameters of the message (title, add footer, reply-to, etc) but the message still gets dropped because the id is the same.

Has anyone dealt with this issue in the past?  After allot of thinking and searching I haven't come up with a nice solution.  I think mailman and maybe majordomo 2 both have an 'ack' feature, but I would hate to have to change systems entirely just to get it.

Randall
------=_Part_4968_16495652.1220970711622-- From majordomo-users-owner@greatcircle.com Wed Sep 10 19:18:56 2008 X-Greylist: delayed 357 seconds by postgrey-1.24 at mycroft; Wed, 10 Sep 2008 19:18:55 PDT Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 745454D00C2 for ; Wed, 10 Sep 2008 19:18:55 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by moroni.ourldsfamily.com (8.13.7/8.13.7) with ESMTP id m8B2Cr0G013403 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2008 20:12:55 -0600 Date: Wed, 10 Sep 2008 20:12:53 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@portapc To: Randall Belk cc: majordomo-users@greatcircle.com Subject: Re: Majordomo and gmail In-Reply-To: <21d95d450809090731i2bade25kc49e96b92ba1f906@mail.gmail.com> Message-ID: References: <21d95d450809090731i2bade25kc49e96b92ba1f906@mail.gmail.com> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Archive-Number: 200809/8 X-Sequence-Number: 5798 If the majordomo system is running on Linux, you could use procmail to check for the header and then either remove or change the ID. A simple recipe to do that might look something like: :0 fw * ^From:.*@gmail.com |sed -e 's/^IDHeader:[ ]*/IDHeader: [add text here] /' I'm not completely sure this would work, but it has as much a chance as anything I can thing of. Hopefully, Karl On Tue, 9 Sep 2008, Randall Belk wrote: > I maintain a majordomo server for an organization that recently switched to > Google Apps for email. > With their old email provider they would send an email to one of the lists > and as the emails were sent out by the server they would get their own email > back. They came to depend on this "Feature" as confirmation that everything > was working. > > Gmail looks at an incoming message and determines (by message-id I think) if > this is a message that originated within the destination account and drops > it if it did. The result is that everybody thinks the server isn't working > when actually it is because they don't get a mail back. I'm pretty sure > gmail is keying on the id because I can change other parameters of the > message (title, add footer, reply-to, etc) but the message still gets > dropped because the id is the same. > > Has anyone dealt with this issue in the past? After allot of thinking and > searching I haven't come up with a nice solution. I think mailman and maybe > majordomo 2 both have an 'ack' feature, but I would hate to have to change > systems entirely just to get it. > > Randall > From majordomo-users-owner@greatcircle.com Wed Sep 10 22:08:26 2008 Received: from moroni.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2C1674D00AA for ; Wed, 10 Sep 2008 22:08:24 -0700 (PDT) Received: from portapc.local ([172.20.20.23]) by moroni.ourldsfamily.com (8.13.7/8.13.7) with ESMTP id m8B58DQp028396 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2008 23:08:15 -0600 Date: Wed, 10 Sep 2008 23:08:13 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@portapc To: Randall Belk cc: majordomo-users@greatcircle.com Subject: Re: Majordomo and gmail In-Reply-To: <21d95d450809101951q5928ced7o94a79811e16650f8@mail.gmail.com> Message-ID: References: <21d95d450809090731i2bade25kc49e96b92ba1f906@mail.gmail.com> <21d95d450809101951q5928ced7o94a79811e16650f8@mail.gmail.com> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Archive-Number: 200809/9 X-Sequence-Number: 5799 I don't think you'll have to generate a new ID, just change the existing ID. At least that's they theory. Karl On Wed, 10 Sep 2008, Randall Belk wrote: > Thanks Karl, > I had actually come up with a similar solution that I'm implementing now. I > set up a auto-responder using procmail that will respond to any email that > comes from the gmail domain. Then I subscribe the address of the responder > to all of the lists. So when someone sends to a list, MJ will forward it to > the responder, and if it is a gmail account, the responder will send > an acknowledgment to the sender otherwise it will discard it. > > Your way actually looks simpler, I may play with it a little. If I used > your method I could avoid having to subscribe the responder to all of the > lists which would be great. I'm not clear on how to generate a new ID > though. I'll poke around and see what I can come up with. > > Randall > > On Wed, Sep 10, 2008 at 9:12 PM, Karl Pearson wrote: > >> If the majordomo system is running on Linux, you could use procmail to >> check for the header and then either remove or change the ID. A simple >> recipe to do that might look something like: >> >> :0 fw >> * ^From:.*@gmail.com >> |sed -e 's/^IDHeader:[ ]*/IDHeader: [add text here] /' >> >> I'm not completely sure this would work, but it has as much a chance as >> anything I can thing of. >> >> Hopefully, >> >> Karl >> >> >> >> On Tue, 9 Sep 2008, Randall Belk wrote: >> >> I maintain a majordomo server for an organization that recently switched >>> to >>> Google Apps for email. >>> With their old email provider they would send an email to one of the lists >>> and as the emails were sent out by the server they would get their own >>> email >>> back. They came to depend on this "Feature" as confirmation that >>> everything >>> was working. >>> >>> Gmail looks at an incoming message and determines (by message-id I think) >>> if >>> this is a message that originated within the destination account and >>> drops >>> it if it did. The result is that everybody thinks the server isn't >>> working >>> when actually it is because they don't get a mail back. I'm pretty sure >>> gmail is keying on the id because I can change other parameters of the >>> message (title, add footer, reply-to, etc) but the message still gets >>> dropped because the id is the same. >>> >>> Has anyone dealt with this issue in the past? After allot of thinking and >>> searching I haven't come up with a nice solution. I think mailman and >>> maybe >>> majordomo 2 both have an 'ack' feature, but I would hate to have to change >>> systems entirely just to get it. >>> >>> Randall >>> >>> > --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Sun Sep 14 14:17:50 2008 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 73D634D00E8 for ; Sun, 14 Sep 2008 14:17:49 -0700 (PDT) Received: from mail.ourldsfamily.com ([127.0.0.1]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id m8ELHmUe001453 for ; Sun, 14 Sep 2008 15:17:48 -0600 Received: from localhost (karlp@localhost) by mail.ourldsfamily.com (8.14.2/8.14.2/Submit) with ESMTP id m8ELHl7Q001450 for ; Sun, 14 Sep 2008 15:17:48 -0600 X-Authentication-Warning: mail.ourldsfamily.com: karlp owned process doing -bs Date: Sun, 14 Sep 2008 15:17:47 -0600 (MDT) From: karlp@ourldsfamily.com To: majordomo-users@greatcircle.com Subject: owner-group getting emails Message-ID: User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: ClamAV 0.92.1/8238/Sun Sep 14 11:22:28 2008 on mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200809/10 X-Sequence-Number: 5800 What would cause the owner of groups (me) to get emails to the group? Situation: Mail server crashed; re-installed on new server. after getting DNS working, things are much happier, but little things are amiss, like the subject line. I don't know how busy the groups are, but it seems some are putting email to owner-groupname in my inbox... Majordomo 1.94.5 Fedora 8 Sendmail v8.14.2 TIA, --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Sun Sep 14 22:54:30 2008 X-Greylist: delayed 7203 seconds by postgrey-1.24 at mycroft; Sun, 14 Sep 2008 22:54:30 PDT Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 0F9B04D00CB for ; Sun, 14 Sep 2008 22:54:29 -0700 (PDT) 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 <0K7700E1PXISO6@mail.sonny.com> for majordomo-users@greatcircle.com; Sun, 14 Sep 2008 22:54:28 -0500 (CDT) Date: Sun, 14 Sep 2008 22:54:26 -0500 From: Daniel Liston Subject: Re: owner-group getting emails In-reply-to: To: majordomo-users@greatcircle.com Message-id: <48CDDC72.4040003@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.16 (X11/20080723) References: X-Archive-Number: 200809/11 X-Sequence-Number: 5801 Does owner-group exist in your aliases file? Are you using multiple aliases files? Do any of your group config files refer to owner-group? Is owner-group directly subscribed to any of the groups? Since you are on a new machine, these little details are important. Dan Liston karlp@ourldsfamily.com wrote: > What would cause the owner of groups (me) to get emails to the group? > > Situation: Mail server crashed; re-installed on new server. after > getting DNS working, things are much happier, but little things are > amiss, like the subject line. I don't know how busy the groups are, but > it seems some are putting email to owner-groupname in my inbox... > > Majordomo 1.94.5 > Fedora 8 > Sendmail v8.14.2 > > TIA, > > --- > _/ _/ _/ _/_/_/ ____________ __o > _/ _/ _/ _/ _/ ____________ _-\<._ > _/_/ _/ _/_/_/ (_)/ (_) > _/ _/ _/ _/ ...................... > _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com > --- > http://consulting.ourldsfamily.com > --- From majordomo-users-owner@greatcircle.com Mon Sep 15 09:55:26 2008 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id 985984D00BF for ; Mon, 15 Sep 2008 09:55:25 -0700 (PDT) Received: from portapc.local ([172.20.20.23]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id m8FGtL7e023030; Mon, 15 Sep 2008 10:55:24 -0600 Date: Mon, 15 Sep 2008 10:55:21 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@portapc To: Daniel Liston cc: majordomo-users@greatcircle.com Subject: Re: owner-group getting emails In-Reply-To: <48CDDC72.4040003@sonny.org> Message-ID: References: <48CDDC72.4040003@sonny.org> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: ClamAV 0.92.1/8248/Mon Sep 15 09:28:54 2008 on mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200809/12 X-Sequence-Number: 5802 Okay, each group owner is in the aliases file. I just copied them from the old server's hard disk, and when I run newaliases, they come up okay. In the .config files, the sender is listed as owner-groupname. The owner is not subscribed to any group as owner-groupname@myhost.com. In fact, I'm not subscribed to any of the groups I'm getting email for... Karl On Sun, 14 Sep 2008, Daniel Liston wrote: > Does owner-group exist in your aliases file? Are you using multiple > aliases files? Do any of your group config files refer to owner-group? > Is owner-group directly subscribed to any of the groups? Since you are > on a new machine, these little details are important. > > Dan Liston > > karlp@ourldsfamily.com wrote: >> What would cause the owner of groups (me) to get emails to the group? >> >> Situation: Mail server crashed; re-installed on new server. after getting >> DNS working, things are much happier, but little things are amiss, like the >> subject line. I don't know how busy the groups are, but it seems some are >> putting email to owner-groupname in my inbox... >> >> Majordomo 1.94.5 >> Fedora 8 >> Sendmail v8.14.2 >> >> TIA, >> >> --- >> _/ _/ _/ _/_/_/ ____________ __o >> _/ _/ _/ _/ _/ ____________ _-\<._ >> _/_/ _/ _/_/_/ (_)/ (_) >> _/ _/ _/ _/ ...................... >> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >> --- >> http://consulting.ourldsfamily.com >> --- > --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Mon Sep 15 10:13:57 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2F9504D00CE for ; Mon, 15 Sep 2008 10:13:56 -0700 (PDT) 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 <0K7800F6BYJB4G@mail.sonny.com> for majordomo-users@greatcircle.com; Mon, 15 Sep 2008 12:13:59 -0500 (CDT) Date: Mon, 15 Sep 2008 12:13:55 -0500 From: Daniel Liston Subject: Re: owner-group getting emails In-reply-to: To: majordomo-users@greatcircle.com Message-id: <48CE97D3.4060807@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.16 (X11/20080723) References: <48CDDC72.4040003@sonny.org> X-Archive-Number: 200809/13 X-Sequence-Number: 5803 Sendmail uses the owner- prefix to notify, or as last resort, for delivery to the group name when there are problems, even outside of majordomo list configuration. Could this be what is happening based on the crash or not quite perfect (dns problems) rebuild, and you are still seeing side effects of mail that was still queued up? Do the sendmail or majordomo log files have any hints or indications of failed deliveries that might apply to your current situation? What about the "Received:" headers of the messages you are receiving? Do these show original recipient vs. final delivery being your mailbox? Dan Liston Karl Pearson wrote: > Okay, each group owner is in the aliases file. I just copied them from > the old server's hard disk, and when I run newaliases, they come up okay. > > In the .config files, the sender is listed as owner-groupname. > > The owner is not subscribed to any group as owner-groupname@myhost.com. > In fact, I'm not subscribed to any of the groups I'm getting email for... > > Karl > > > > On Sun, 14 Sep 2008, Daniel Liston wrote: > >> Does owner-group exist in your aliases file? Are you using multiple >> aliases files? Do any of your group config files refer to owner-group? >> Is owner-group directly subscribed to any of the groups? Since you are >> on a new machine, these little details are important. >> >> Dan Liston >> >> karlp@ourldsfamily.com wrote: >>> What would cause the owner of groups (me) to get emails to the group? >>> >>> Situation: Mail server crashed; re-installed on new server. after >>> getting DNS working, things are much happier, but little things are >>> amiss, like the subject line. I don't know how busy the groups are, >>> but it seems some are putting email to owner-groupname in my inbox... >>> >>> Majordomo 1.94.5 >>> Fedora 8 >>> Sendmail v8.14.2 >>> >>> TIA, >>> >>> --- >>> _/ _/ _/ _/_/_/ ____________ __o >>> _/ _/ _/ _/ _/ ____________ _-\<._ >>> _/_/ _/ _/_/_/ (_)/ (_) >>> _/ _/ _/ _/ ...................... >>> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >>> --- >>> http://consulting.ourldsfamily.com >>> --- >> > > --- > _/ _/ _/ _/_/_/ ____________ __o > _/ _/ _/ _/ _/ ____________ _-\\<._ > _/_/ _/ _/_/_/ (_)/ (_) > _/ _/ _/ _/ ...................... > _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com > --- > http://consulting.ourldsfamily.com > --- > From majordomo-users-owner@greatcircle.com Mon Sep 15 10:41:58 2008 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id DDC374D00CE for ; Mon, 15 Sep 2008 10:41:57 -0700 (PDT) Received: from portapc.local ([172.20.20.23]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id m8FHfu3k011646; Mon, 15 Sep 2008 11:41:57 -0600 Date: Mon, 15 Sep 2008 11:41:56 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@portapc To: Daniel Liston cc: majordomo-users@greatcircle.com Subject: Re: owner-group getting emails In-Reply-To: <48CE97D3.4060807@sonny.org> Message-ID: References: <48CDDC72.4040003@sonny.org> <48CE97D3.4060807@sonny.org> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.92.1/8249/Mon Sep 15 10:31:36 2008 on mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200809/14 X-Sequence-Number: 5804 I'm not sure about the failures because I've not watched the MD log before, but Here's a line that is causing me some concern: Sep 15 11:31:50 ourldsfamily.com majordomo[30210] {cathyvhunt } ABORT chown(8, 512, "/opt/majordomo-1.94.5/lists/ldsmmpacificso.new"): Operation not permitted And, there's an empty group in the lists folder named ldsmmpacificso.new and I didn't create it. I'm looking at permissions now. A HA!!! For some reason the group on the lists folder, and some of the lists, was still 512, from the old system. Drat! I hate when that happens. I'll be watching now... But, any other thoughts will be more than welcome. Karl On Mon, 15 Sep 2008, Daniel Liston wrote: > Sendmail uses the owner- prefix to notify, or as last resort, for delivery > to the group name when there are problems, even outside of majordomo list > configuration. Could this be what is happening based on the crash or not > quite perfect (dns problems) rebuild, and you are still seeing side effects > of mail that was still queued up? Do the sendmail or majordomo log files > have any hints or indications of failed deliveries that might apply to your > current situation? What about the "Received:" headers of the messages you > are receiving? Do these show original recipient vs. final delivery being > your mailbox? > > Dan Liston > > Karl Pearson wrote: >> Okay, each group owner is in the aliases file. I just copied them from the >> old server's hard disk, and when I run newaliases, they come up okay. >> >> In the .config files, the sender is listed as owner-groupname. >> >> The owner is not subscribed to any group as owner-groupname@myhost.com. In >> fact, I'm not subscribed to any of the groups I'm getting email for... >> >> Karl >> >> >> >> On Sun, 14 Sep 2008, Daniel Liston wrote: >> >>> Does owner-group exist in your aliases file? Are you using multiple >>> aliases files? Do any of your group config files refer to owner-group? >>> Is owner-group directly subscribed to any of the groups? Since you are >>> on a new machine, these little details are important. >>> >>> Dan Liston >>> >>> karlp@ourldsfamily.com wrote: >>>> What would cause the owner of groups (me) to get emails to the group? >>>> >>>> Situation: Mail server crashed; re-installed on new server. after getting >>>> DNS working, things are much happier, but little things are amiss, like >>>> the subject line. I don't know how busy the groups are, but it seems some >>>> are putting email to owner-groupname in my inbox... >>>> >>>> Majordomo 1.94.5 >>>> Fedora 8 >>>> Sendmail v8.14.2 >>>> >>>> TIA, >>>> >>>> --- >>>> _/ _/ _/ _/_/_/ ____________ __o >>>> _/ _/ _/ _/ _/ ____________ _-\<._ >>>> _/_/ _/ _/_/_/ (_)/ (_) >>>> _/ _/ _/ _/ ...................... >>>> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >>>> --- >>>> http://consulting.ourldsfamily.com >>>> --- >>> >> >> --- >> _/ _/ _/ _/_/_/ ____________ __o >> _/ _/ _/ _/ _/ ____________ _-\\<._ >> _/_/ _/ _/_/_/ (_)/ (_) >> _/ _/ _/ _/ ...................... >> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >> --- >> http://consulting.ourldsfamily.com >> --- >> > --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Mon Sep 15 16:24:41 2008 Received: from mail.ourldsfamily.com (ourldsfamily.com [198.60.114.90]) by mycroft.greatcircle.com (Postfix) with ESMTP id A51764D00D4 for ; Mon, 15 Sep 2008 16:24:40 -0700 (PDT) Received: from portapc.local ([172.20.20.23]) by mail.ourldsfamily.com (8.14.2/8.14.2) with ESMTP id m8FNOcNa022771; Mon, 15 Sep 2008 17:24:39 -0600 Date: Mon, 15 Sep 2008 17:24:38 -0600 (MDT) From: Karl Pearson X-X-Sender: karlp@portapc To: Daniel Liston cc: majordomo-users@greatcircle.com Subject: Re: owner-group getting emails In-Reply-To: Message-ID: References: <48CDDC72.4040003@sonny.org> <48CE97D3.4060807@sonny.org> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.92.1/8252/Mon Sep 15 16:27:12 2008 on mail.ourldsfamily.com X-Virus-Status: Clean X-Archive-Number: 200809/15 X-Sequence-Number: 5805 Update: I found that I had left the alias in /etc/aliases for nobody pointing to root. In my old system I pointed it at /tmp/ZZ/nobody.alias so I could take a peek in there once in a while. I hadn't been 'peeking' for so long, I had forgotten about it. I changed it to: nobody: /dev/null so that problem seems to be gone. Now if I can only figure out why Dovecot/Apache doesn't want to authorize webmail access. Oh, and thanks Dan. You've been there for the 12-15 years I've been doing this (on the side, sometimes poorly). Karl On Mon, 15 Sep 2008, Karl Pearson wrote: > I'm not sure about the failures because I've not watched the MD log before, > but Here's a line that is causing me some concern: > > Sep 15 11:31:50 ourldsfamily.com majordomo[30210] {cathyvhunt > } ABORT chown(8, 512, > "/opt/majordomo-1.94.5/lists/ldsmmpacificso.new"): Operation not permitted > > And, there's an empty group in the lists folder named ldsmmpacificso.new and > I didn't create it. I'm looking at permissions now. A HA!!! For some reason > the group on the lists folder, and some of the lists, was still 512, from the > old system. Drat! I hate when that happens. > > I'll be watching now... > > But, any other thoughts will be more than welcome. > > Karl > > On Mon, 15 Sep 2008, Daniel Liston wrote: > >> Sendmail uses the owner- prefix to notify, or as last resort, for delivery >> to the group name when there are problems, even outside of majordomo list >> configuration. Could this be what is happening based on the crash or not >> quite perfect (dns problems) rebuild, and you are still seeing side effects >> of mail that was still queued up? Do the sendmail or majordomo log files >> have any hints or indications of failed deliveries that might apply to your >> current situation? What about the "Received:" headers of the messages you >> are receiving? Do these show original recipient vs. final delivery being >> your mailbox? >> >> Dan Liston >> >> Karl Pearson wrote: >>> Okay, each group owner is in the aliases file. I just copied them from the >>> old server's hard disk, and when I run newaliases, they come up okay. >>> >>> In the .config files, the sender is listed as owner-groupname. >>> >>> The owner is not subscribed to any group as owner-groupname@myhost.com. In >>> fact, I'm not subscribed to any of the groups I'm getting email for... >>> >>> Karl >>> >>> >>> >>> On Sun, 14 Sep 2008, Daniel Liston wrote: >>> >>>> Does owner-group exist in your aliases file? Are you using multiple >>>> aliases files? Do any of your group config files refer to owner-group? >>>> Is owner-group directly subscribed to any of the groups? Since you are >>>> on a new machine, these little details are important. >>>> >>>> Dan Liston >>>> >>>> karlp@ourldsfamily.com wrote: >>>>> What would cause the owner of groups (me) to get emails to the group? >>>>> >>>>> Situation: Mail server crashed; re-installed on new server. after >>>>> getting DNS working, things are much happier, but little things are >>>>> amiss, like the subject line. I don't know how busy the groups are, but >>>>> it seems some are putting email to owner-groupname in my inbox... >>>>> >>>>> Majordomo 1.94.5 >>>>> Fedora 8 >>>>> Sendmail v8.14.2 >>>>> >>>>> TIA, >>>>> >>>>> --- >>>>> _/ _/ _/ _/_/_/ ____________ __o >>>>> _/ _/ _/ _/ _/ ____________ _-\<._ >>>>> _/_/ _/ _/_/_/ (_)/ (_) >>>>> _/ _/ _/ _/ ...................... >>>>> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >>>>> --- >>>>> http://consulting.ourldsfamily.com >>>>> --- >>>> >>> >>> --- >>> _/ _/ _/ _/_/_/ ____________ __o >>> _/ _/ _/ _/ _/ ____________ _-\\<._ >>> _/_/ _/ _/_/_/ (_)/ (_) >>> _/ _/ _/ _/ ...................... >>> _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com >>> --- >>> http://consulting.ourldsfamily.com >>> --- >>> >> > > --- > _/ _/ _/ _/_/_/ ____________ __o > _/ _/ _/ _/ _/ ____________ _-\\<._ > _/_/ _/ _/_/_/ (_)/ (_) > _/ _/ _/ _/ ...................... > _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com > --- > http://consulting.ourldsfamily.com > --- > --- _/ _/ _/ _/_/_/ ____________ __o _/ _/ _/ _/ _/ ____________ _-\\<._ _/_/ _/ _/_/_/ (_)/ (_) _/ _/ _/ _/ ...................... _/ _/ arl _/_/_/ _/ earson KarlP@ourldsfamily.com --- http://consulting.ourldsfamily.com --- From majordomo-users-owner@greatcircle.com Thu Sep 18 08:22:22 2008 X-Greylist: delayed 903 seconds by postgrey-1.24 at mycroft; Thu, 18 Sep 2008 08:22:20 PDT Received: from paoakoavas09.cable.comcast.com (paoakoavas09.cable.comcast.com [208.17.35.58]) by mycroft.greatcircle.com (Postfix) with ESMTP id C8865510061 for ; Thu, 18 Sep 2008 08:22:20 -0700 (PDT) Received: from ([10.52.116.30]) by paoakoavas09.cable.comcast.com with ESMTP id KP-NTF18.60443870; Thu, 18 Sep 2008 11:07:00 -0400 Received: from PACDCEXCMB04.cable.comcast.com ([24.40.15.86]) by PAOAKEXCSMTP01.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 18 Sep 2008 11:07:00 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C919A0.28FB4E0A" Subject: Default User ID Date: Thu, 18 Sep 2008 11:06:42 -0400 Message-ID: <5179391446F07840B1BADBA758DE1B1E07F460DD@PACDCEXCMB04.cable.comcast.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Default User ID thread-index: AckZoCgC7z4SerWlRnOoMz3+olI8kQ== From: "Schow, Brandon" To: X-OriginalArrivalTime: 18 Sep 2008 15:07:00.0306 (UTC) FILETIME=[334F3320:01C919A0] X-Archive-Number: 200809/16 X-Sequence-Number: 5806 This is a multi-part message in MIME format. ------_=_NextPart_001_01C919A0.28FB4E0A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I'm a new user trying to install Majordomo on an OpenSuSE computer. I haven't been having much luck. =20 Everything went fine until I got to the part of the process where the wrapper config test is performed. I had been using the default user, and got an error message saying not to do that. =20 So I created a new group called 'majordomo' and a user to go with it. I made sure that the group existed, and that the user has been assigned to it. I edit the Makefile to refer to the numerical IDs of the group and user that I've created, instead of the default values. =20 I then run 'make install' again. Again, I get to the wrapper config test. And again, despite the Makefile saying otherwise, it insists that I'm using the default uid and gid. I thought 'well, I'm trying to install into the folder I had originally created with make install...maybe I should try a different folder'. So I alter 'make install' to create an entirely different folder for Majordomo, with the uid and gid set to the username and the majordomo group I made. =20 And it /still/ insists that I'm trying to use the default uid of 123 and the root group (45 0). What do I have to alter to make the installation files recognize the user I'm telling them to? ------_=_NextPart_001_01C919A0.28FB4E0A Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello, I’m a new user trying to install = Majordomo on an OpenSuSE computer. I haven’t been having much = luck.

 

Everything went fine until I got to the part of the = process where the wrapper config test is performed. I had been using the default = user, and got an error message saying not to do = that.

 

So I created a new group called = ‘majordomo’ and a user to go with it. I made sure that the group existed, and that the = user has been assigned to it. I edit the Makefile to refer to the numerical IDs = of the group and user that I’ve created, instead of the default = values.

 

I then run ‘make install’ again. Again, I = get to the wrapper config test. And again, despite the Makefile saying = otherwise, it insists that I’m using the default uid and gid. I thought = ‘well, I’m trying to install into the folder I had originally created with make = install…maybe I should try a different folder’. So I alter ‘make = install’ to create an entirely different folder for Majordomo, with the uid and = gid set to the username and the majordomo group I = made.

 

And it /still/ insists that I’m trying to use = the default uid of 123 and the root group (45 0). What do I have to alter to make = the installation files recognize the user I’m telling them = to?

------_=_NextPart_001_01C919A0.28FB4E0A-- From majordomo-users-owner@greatcircle.com Thu Sep 18 10:47:33 2008 Received: from mail.sonny.com (mail.sonny.com [70.58.223.141]) by mycroft.greatcircle.com (Postfix) with ESMTP id 2866B51003A for ; Thu, 18 Sep 2008 10:47:31 -0700 (PDT) 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 <0K7E00H5FK3487@mail.sonny.com> for majordomo-users@greatcircle.com; Thu, 18 Sep 2008 12:47:28 -0500 (CDT) Date: Thu, 18 Sep 2008 12:47:29 -0500 From: Daniel Liston Subject: Re: Default User ID In-reply-to: <5179391446F07840B1BADBA758DE1B1E07F460DD@PACDCEXCMB04.cable.comcast.com> To: "Schow, Brandon" , majordomo-users@greatcircle.com Message-id: <48D29431.2080808@sonny.org> MIME-version: 1.0 Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 8BIT User-Agent: Thunderbird 2.0.0.16 (X11/20080723) References: <5179391446F07840B1BADBA758DE1B1E07F460DD@PACDCEXCMB04.cable.comcast.com> X-Archive-Number: 200809/17 X-Sequence-Number: 5807 I assume you have downloaded the 1.94.5 tar or compressed file into your home directory and extracted it there. I also assume your sendmail (or compatible) MTA is configured and working. My current configuration has a link to perl in /bin from /usr/bin, in case any of the other scripts assume /bin/perl. Perhaps it is in the order you followed the install steps. 1. create a majordom user and group in /etc/passwd and /etc/group. 1a. add "Tmajordom" to /etc/sendmail.cf note1: only 8 characters allowed on older linux or solaris 2. make note of the uid:gid of this user, and the $HOME directory 3. locate your perl and gcc tools, you need this in the next step 4. edit Makefile 4a. PERL = /usr/bin/perl 4b. CC = /usr/bin/gcc 4c. W_HOME = /usr/lib/majordomo # <$HOME from above in step 2> 4d. MAN = $(W_HOME)/man # /usr/man or /usr/local/man is better 4e. W_USER = 91 # what I used, use your info from step 2 4f. W_GROUP = 91 # what I used, use your info from step 2 4g. The following defaults are fine; FILE_MODE = 644 EXEC_MODE = 755 HOME_MODE = 751 4h. Linux is POSIX so these are fine too; WRAPPER_OWNER = root WRAPPER_GROUP = $(W_GROUP) WRAPPER_MODE = 4755 POSIX = -DPOSIX_UID=$(W_USER) -DPOSIX_GID=$(W_GROUP) TMPDIR = /var/tmp # make sure this target directory exists 5. copy sample.cf to majordomo.cf 5a. edit majordomo.cf. I only list lines needing changes $whereami = "example.com"; # change to your domain $whoami_owner = "owner-majordomo\@$whereami"; $homedir = "/usr/lib/majordomo"; # same as 4c. $listdir = "/var/lib/majordomo/lists"; $digest_work_dir = "/var/lib/majordomo/digest"; $log = "/var/lib/majordomo/log"; $sendmail_command = "/usr/sbin/sendmail"; $filedir = "/var/lib/majordomo/archive"; $filedir_suffix = ""; $max_which_hits = 1; # for security purposes $TMPDIR = "/var/lib/majordomo/tmp"; note6: Only the root user in bash or sh shell can do this (No csh or ksh) 6. make wrapper # is this where your process dies now? 7. make install 8. make install-wrapper 9. edit /etc/aliases to add/modify; majordomo: "|/usr/lib/majordomo/wrapper majordomo" owner-majordomo: postmaster, # better to use YOUR uid here majordomo-owner: owner-majordomo 10. If you got past steps 6, 7, and 8 (#perl problem#) cd then ./wrapper config-test You should do this test as root, again as majordomo, and finally as yourself (or any other end user). In redhat, sendmail uses smrsh for security and this needs a link from /usr/lib/majordomo/wrapper to /etc/smrsh/wrapper. More inline; Schow, Brandon wrote: > Everything went fine until I got to the part of the process where the > wrapper config test is performed. I had been using the default user, and > got an error message saying not to do that. There is nothing wrong with user 123 in group 45, as long as your password shadow and group files support this. > > So I created a new group called ‘majordomo’ and a user to go with it. I > made sure that the group existed, and that the user has been assigned to > it. I edit the Makefile to refer to the numerical IDs of the group and > user that I’ve created, instead of the default values. In my recipe above I use 91 for both of these. In the comment immediately above, all that really matters is that password and group files match what you enter in the Makefile. > > I then run ‘make install’ again. Again, I get to the wrapper config > test. And again, despite the Makefile saying otherwise, it insists that > I’m using the default uid and gid. I thought ‘well, I’m trying to Are you running 'make install' as the root user? Are you in an sh or bash shell? The notes specify csh is not supported for this operation. > install into the folder I had originally created with make install…maybe > I should try a different folder’. So I alter ‘make install’ to create an > entirely different folder for Majordomo, with the uid and gid set to the > username and the majordomo group I made. Maybe you missed the "edit majordomo.cf" step. > > And it /still/ insists that I’m trying to use the default uid of 123 and > the root group (45 0). What do I have to alter to make the installation > files recognize the user I’m telling them to? Either the Makefile still has 123 and 45 or the password and group files do.