From majordomo-users-owner@greatcircle.com  Wed Apr  1 09:21:39 2009
Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.245])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 2133369009B
	for <majordomo-users@greatcircle.com>; Wed,  1 Apr 2009 09:21:38 -0700 (PDT)
Received: by rv-out-0708.google.com with SMTP id c5so88575rvf.50
        for <majordomo-users@greatcircle.com>; Wed, 01 Apr 2009 09:21:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=+A70sLbdddtYU/QcT3ynXzAhOGscSJmw9PdGYAJzGGg=;
        b=Q7NHp42FD/LOvRjBjeBRSfqKnGPoRGeHy43XuKxEMEqEYA/fxXpKM+hceNkvANvY3D
         E1KJjegfu41VUOkBiih1F/HHs9wLwQtHHNlZ6iJI6FI14hKKiQ0u3pWEdopo9ttWZkGD
         UYGudO7JSRKUq/V+CAB1PRjTozuUOxUUVStq4=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=nqWjooBPukQrijQuOCaEci3yvNfuT9FkUZ50qbYQAzlOqL94E+Hz5GQAVTAK2C/jOc
         yaxsrnxQrhReX5Na3aS5/KW7Ub114IvoXLY8s6MASlX6Y4jp3ivehUfIZwszf7+cg95f
         TgzdflkK5GLuQCNoh7SIRu10lEltkLaIjHN5s=
MIME-Version: 1.0
Received: by 10.114.178.13 with SMTP id a13mr5319534waf.88.1238602537985; Wed, 
	01 Apr 2009 09:15:37 -0700 (PDT)
Date: Wed, 1 Apr 2009 21:45:37 +0530
Message-ID: <f9efafcb0904010915q3d35b78p5198bfe4341071b8@mail.gmail.com>
Subject: problem in approving mails
From: Ranbir Sanasam <san.ranbir@gmail.com>
To: majordomo-users@greatcircle.com
Content-Type: multipart/alternative; boundary=001636417f834b674a046680a014
X-Archive-Number: 200904/1
X-Sequence-Number: 5846

--001636417f834b674a046680a014
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

I am new to majordomo. I have installed majordomo-1.94.5 on our mail
server.. As per the config-test, it seems to be  working properly. But, the
problem is the following.

I want to create a group mailing list say test@<domain name>. All mails to
this group should go to its owner for approval before it gets delivered. As
per the manual, i have make the following entries

majordomo: "|/usr/local/majordomo-1.94.5/wrapper majordomo"
owner-majordomo: xyz
majordomo-owner: xyz

test_majordemo: "|/usr/local/majordomo-1.94.5/wrapper  resend -l
test_majordemo test_majordemo-list"
test_majordemo-list: abc
owner-test_majordemo: xyz
test_majordemo-owner: xyz
test_majordemo-approval: xyz
test_majordemo-request: "|/usr/local/majordomo-1.94.5/wrapper majordomo -l
test_majordemo"

Now the problem is : when i send some test mail to test_majordemo@<domain
name>, instead of going to xyz user for approval, it is directly delivering
to abc user.

in the approver home directory, we have the following information in the
.majordomo file

test_majordemo@<domain name>       test_majordemo.pass       majordomo@<domain
name>


We are running our mail server on Debian etch with sendmail MTA.

Any help would be appreciated.

Regards
-ranbir

--001636417f834b674a046680a014
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<br><br>I am new to majordomo. I have installed majordomo-1.94.5 on our =
mail server.. As per the config-test, it seems to be=A0 working properly. B=
ut, the problem is the following.<br><br>I want to create a group mailing l=
ist say test@&lt;domain name&gt;. All mails to this group should go to its =
owner for approval before it gets delivered. As per the manual, i have make=
 the following entries<br>
<br>majordomo: &quot;|/usr/local/majordomo-1.94.5/wrapper majordomo&quot;<b=
r>owner-majordomo: xyz<br>majordomo-owner: xyz <br><br>test_majordemo: &quo=
t;|/usr/local/majordomo-1.94.5/wrapper=A0 resend -l test_majordemo test_maj=
ordemo-list&quot;<br>
test_majordemo-list: abc<br>owner-test_majordemo: xyz<br>test_majordemo-own=
er: xyz<br>test_majordemo-approval: xyz<br>test_majordemo-request: &quot;|/=
usr/local/majordomo-1.94.5/wrapper majordomo -l test_majordemo&quot;<br>
<br>Now the problem is : when i send some test mail to test_majordemo@&lt;d=
omain name&gt;, instead of going to xyz user for approval, it is directly d=
elivering to abc user.<br><br>in the approver home directory, we have the f=
ollowing information in the .majordomo file<br>
<br>test_majordemo@&lt;domain name&gt; =A0=A0=A0=A0=A0 test_majordemo.pass=
=A0=A0=A0=A0=A0=A0 majordomo@&lt;domain name&gt;<br><br><br>We are running =
our mail server on Debian etch with sendmail MTA.<br><br>Any help would be =
appreciated.<br><br>
Regards<br>-ranbir<br>

--001636417f834b674a046680a014--

From majordomo-users-owner@greatcircle.com  Wed Apr  1 10:54:54 2009
Received: from mail.sonny.com (mail.sonny.com [70.58.223.141])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 179016900A9
	for <majordomo-users@greatcircle.com>; Wed,  1 Apr 2009 10:54:51 -0700 (PDT)
Received: from [192.168.1.68] (magnum.sonny.com [192.168.1.68])
 by mail.sonny.com (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTPA id <0KHF0025KOFFAT@mail.sonny.com> for
 majordomo-users@greatcircle.com; Wed, 01 Apr 2009 12:54:51 -0500 (CDT)
Date: Wed, 01 Apr 2009 12:55:31 -0500
From: Daniel Liston <dliston@sonny.org>
Subject: Re: problem in approving mails
In-reply-to: <f9efafcb0904010915q3d35b78p5198bfe4341071b8@mail.gmail.com>
To: Ranbir Sanasam <san.ranbir@gmail.com>
Cc: majordomo-users@greatcircle.com
Message-id: <49D3AA93.2090603@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.19 (X11/20090105)
References: <f9efafcb0904010915q3d35b78p5198bfe4341071b8@mail.gmail.com>
X-Archive-Number: 200904/2
X-Sequence-Number: 5847

All good information, but what is in test_majordemo.config that
will make messages go anywhere but abc?  Do you have moderate=yes
and moderator=xyz?

Ranbir Sanasam wrote:
> Hi,
> 
> I am new to majordomo. I have installed majordomo-1.94.5 on our mail 
> server.. As per the config-test, it seems to be  working properly. But, 
> the problem is the following.
> 
> I want to create a group mailing list say test@<domain name>. All mails 
> to this group should go to its owner for approval before it gets 
> delivered. As per the manual, i have make the following entries
> 
> majordomo: "|/usr/local/majordomo-1.94.5/wrapper majordomo"
> owner-majordomo: xyz
> majordomo-owner: xyz
> 
> test_majordemo: "|/usr/local/majordomo-1.94.5/wrapper  resend -l test_majordemo test_majordemo-list"
> test_majordemo-list: abc
> owner-test_majordemo: xyz
> test_majordemo-owner: xyz
> test_majordemo-approval: xyz
> test_majordemo-request: "|/usr/local/majordomo-1.94.5/wrapper majordomo -l test_majordemo"
> 
> Now the problem is : when i send some test mail to 
> test_majordemo@<domain name>, instead of going to xyz user for approval, 
> it is directly delivering to abc user.
> 
> in the approver home directory, we have the following information in the 
> .majordomo file
> 
> test_majordemo@<domain name>       test_majordemo.pass       
> majordomo@<domain name>
> 
> 
> We are running our mail server on Debian etch with sendmail MTA.
> 
> Any help would be appreciated.
> 
> Regards
> -ranbir

From majordomo-users-owner@greatcircle.com  Mon Apr  6 07:32:59 2009
X-Greylist: delayed 2148 seconds by postgrey-1.24 at mycroft; Mon, 06 Apr 2009 07:32:58 PDT
Received: from chewbacca.dahl-stamnes.net (38.80-203-206.nextgentel.com [80.203.206.38])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 71036590172
	for <majordomo-users@greatcircle.com>; Mon,  6 Apr 2009 07:32:58 -0700 (PDT)
Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [194.213.166.140])
	by chewbacca.dahl-stamnes.net (8.13.1/8.13.1) with ESMTP id n36Dv8jI017679
	for <majordomo-users@greatcircle.com>; Mon, 6 Apr 2009 15:57:09 +0200
Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [127.0.0.1])
	by jedi.dahl-stamnes.net (8.13.4/8.13.4) with ESMTP id n36Dv8k6009865
	for <majordomo-users@greatcircle.com>; Mon, 6 Apr 2009 15:57:08 +0200
Received: from localhost (localhost [[UNIX: localhost]])
	by jedi.dahl-stamnes.net (8.13.4/8.13.4/Submit) id n36Dv8JV009864
	for majordomo-users@greatcircle.com; Mon, 6 Apr 2009 15:57:08 +0200
From: =?iso-8859-1?q?J=F8rn_Dahl-Stamnes?= <mr.domo@dahl-stamnes.net>
Reply-To: mr.domo@dahl-stamnes.net
To: majordomo-users@greatcircle.com
Subject: Service unavailable...
Date: Mon, 6 Apr 2009 15:57:08 +0200
User-Agent: KMail/1.8
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200904061557.08353.mr.domo@dahl-stamnes.net>
X-Archive-Number: 200904/3
X-Sequence-Number: 5848

I have replaced my old mail server with a new one running Fedora Core 4. I =
did=20
a clean install but when I try the lists I get:

  =A0 =A0----- The following addresses had permanent fatal errors -----
  "|/usr/local/majordomo/wrapper resend -l xxx xxx-list"
=A0   =A0 (reason: Service unavailable)
=A0 =A0   (expanded from: <xxx@dahl-stamnes.net>)

  =A0 =A0----- Transcript of session follows -----
  Message delivered to mailing list <xxx@dahl-stamnes.net>
  smrsh: "wrapper" not available for sendmail programs (stat failed)
  554 5.0.0 Service unavailable

I have search for solution on Internet, but nothing works.

Any suggestions what's wrong?

=2D-=20
J=F8rn Dahl-Stamnes
homepage: http://www.dahl-stamnes.net/dahls/

From majordomo-users-owner@greatcircle.com  Mon Apr  6 09:56:27 2009
X-Greylist: delayed 2178 seconds by postgrey-1.24 at mycroft; Mon, 06 Apr 2009 09:56:26 PDT
Received: from yoda.wrenkasky.com (esson.net [216.102.129.43])
	by mycroft.greatcircle.com (Postfix) with ESMTP id CEFC159029D
	for <majordomo-users@greatcircle.com>; Mon,  6 Apr 2009 09:56:26 -0700 (PDT)
Received: from KASKY2.esson.net (kasky.priority.usc.edu [128.125.120.92])
	(authenticated bits=0)
	by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id n36GJsji015860
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 6 Apr 2009 09:20:00 -0700
Message-Id: <7.0.1.0.2.20090406091527.024239b8@esson.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 06 Apr 2009 09:20:34 -0700
To: mr.domo@dahl-stamnes.net, majordomo-users@greatcircle.com
From: Ed Kasky <ed@esson.net>
Subject: Re: Service unavailable...
In-Reply-To: <200904061557.08353.mr.domo@dahl-stamnes.net>
References: <200904061557.08353.mr.domo@dahl-stamnes.net>
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: 128.125.120.92 is authenticated by a trusted mechanism)
X-Virus-Scanned: clamav-milter 0.95 at yoda.wrenkasky.com
X-Virus-Status: Clean
X-Archive-Number: 200904/4
X-Sequence-Number: 5849

At 06:57 AM Monday, 4/6/2009, J=F8rn Dahl-Stamnes wrote -=3D>
>I have replaced my old mail server with a new=20
>one running Fedora Core 4. I did
>a clean install but when I try the lists I get:
>
>      ----- The following addresses had permanent fatal errors -----
>   "|/usr/local/majordomo/wrapper resend -l xxx xxx-list"
>       (reason: Service unavailable)
>       (expanded from: <xxx@dahl-stamnes.net>)
>
>      ----- Transcript of session follows -----
>   Message delivered to mailing list <xxx@dahl-stamnes.net>
>   smrsh: "wrapper" not available for sendmail programs (stat failed)
>   554 5.0.0 Service unavailable
>
>I have search for solution on Internet, but nothing works.
>
>Any suggestions what's wrong?

 From the Majordomo FAQ:

"2.11 - I get "sh: wrapper not available for sendmail programs"
You're on a system which uses smrsh. (sendmail=20
restricted shell). You have to configure smrsh to=20
allow it to execute the wrapper. Normally this is=20
done by creating a symlink in /var/adm/sm.bin (in=20
some it's /etc/smrsh) to Majordomo's wrapper program. "

A quick google on the error will should have=20
given you plenty of information and some more=20
specific instructions on how to fix it.

Also, for future reference, it helps if we know=20
your system configuration so that we can provide=20
more specific advice.  For example, your OS,=20
version of MD, wehter or not you have root access=20
to the machine and exactly what you've tried.

HTH...

Ed Kasky
~~~~~~~~~
Randomly Generated Quote (963 of 1229):
The crucial disadvantage of aggression, competitiveness, and
skepticism as national characteristics is that these qualities
cannot be turned off at five o'clock. -Margaret Halsey, (1910-1997)


From majordomo-users-owner@greatcircle.com  Mon Apr  6 10:54:21 2009
Received: from chewbacca.dahl-stamnes.net (38.80-203-206.nextgentel.com [80.203.206.38])
	by mycroft.greatcircle.com (Postfix) with ESMTP id B2719690087
	for <majordomo-users@greatcircle.com>; Mon,  6 Apr 2009 10:54:20 -0700 (PDT)
Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [194.213.166.140])
	by chewbacca.dahl-stamnes.net (8.13.1/8.13.1) with ESMTP id n36HrOkR019784;
	Mon, 6 Apr 2009 19:53:24 +0200
Received: from jedi.dahl-stamnes.net (jedi.dahl-stamnes.net [127.0.0.1])
	by jedi.dahl-stamnes.net (8.13.4/8.13.4) with ESMTP id n36HrOlS012623;
	Mon, 6 Apr 2009 19:53:24 +0200
Received: from localhost (localhost [[UNIX: localhost]])
	by jedi.dahl-stamnes.net (8.13.4/8.13.4/Submit) id n36HrLHe012621;
	Mon, 6 Apr 2009 19:53:21 +0200
From: =?iso-8859-1?q?J=F8rn_Dahl-Stamnes?= <mr.domo@dahl-stamnes.net>
Reply-To: mr.domo@dahl-stamnes.net
To: Ed Kasky <ed@esson.net>
Subject: Re: Service unavailable...
Date: Mon, 6 Apr 2009 19:53:21 +0200
User-Agent: KMail/1.8
Cc: majordomo-users@greatcircle.com
References: <200904061557.08353.mr.domo@dahl-stamnes.net> <7.0.1.0.2.20090406091527.024239b8@esson.net>
In-Reply-To: <7.0.1.0.2.20090406091527.024239b8@esson.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200904061953.21817.mr.domo@dahl-stamnes.net>
X-Archive-Number: 200904/5
X-Sequence-Number: 5850

On Monday 06 April 2009 18:20, Ed Kasky wrote:
> At 06:57 AM Monday, 4/6/2009, J=F8rn Dahl-Stamnes wrote -=3D>
>
> >I have replaced my old mail server with a new
> >one running Fedora Core 4. I did
> >a clean install but when I try the lists I get:
> >
> >      ----- The following addresses had permanent fatal errors -----
> >   "|/usr/local/majordomo/wrapper resend -l xxx xxx-list"
> >       (reason: Service unavailable)
> >       (expanded from: <xxx@dahl-stamnes.net>)
> >
> >      ----- Transcript of session follows -----
> >   Message delivered to mailing list <xxx@dahl-stamnes.net>
> >   smrsh: "wrapper" not available for sendmail programs (stat failed)
> >   554 5.0.0 Service unavailable
> >
> >I have search for solution on Internet, but nothing works.
> >
> >Any suggestions what's wrong?
>
>  From the Majordomo FAQ:
>
> "2.11 - I get "sh: wrapper not available for sendmail programs"
> You're on a system which uses smrsh. (sendmail
> restricted shell). You have to configure smrsh to
> allow it to execute the wrapper. Normally this is
> done by creating a symlink in /var/adm/sm.bin (in
> some it's /etc/smrsh) to Majordomo's wrapper program. "

Thanks. The trick was to create a link /usr/adm/sm.bin (not /var/adm/sm.bin=
).

=2D-=20
J=F8rn Dahl-Stamnes
homepage: http://www.dahl-stamnes.net/dahls/

From majordomo-users-owner@greatcircle.com  Mon Apr  6 11:26:53 2009
Received: from yoda.wrenkasky.com (esson.net [216.102.129.43])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 04AE4690087
	for <majordomo-users@greatcircle.com>; Mon,  6 Apr 2009 11:26:52 -0700 (PDT)
Received: from KASKY2.esson.net (kasky.priority.usc.edu [128.125.120.92])
	(authenticated bits=0)
	by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id n36IQdob021052
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 6 Apr 2009 11:26:45 -0700
Message-Id: <7.0.1.0.2.20090406112622.02441c58@esson.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 06 Apr 2009 11:27:17 -0700
To: mr.domo@dahl-stamnes.net
From: Ed Kasky <ed@esson.net>
Subject: Re: Service unavailable...
Cc: majordomo-users@greatcircle.com
In-Reply-To: <200904061953.21817.mr.domo@dahl-stamnes.net>
References: <200904061557.08353.mr.domo@dahl-stamnes.net>
 <7.0.1.0.2.20090406091527.024239b8@esson.net>
 <200904061953.21817.mr.domo@dahl-stamnes.net>
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: 128.125.120.92 is authenticated by a trusted mechanism)
X-Virus-Scanned: clamav-milter 0.95 at yoda.wrenkasky.com
X-Virus-Status: Clean
X-Archive-Number: 200904/6
X-Sequence-Number: 5851

At 10:53 AM Monday, 4/6/2009, J=F8rn Dahl-Stamnes wrote -=3D>
>On Monday 06 April 2009 18:20, Ed Kasky wrote:
> > At 06:57 AM Monday, 4/6/2009, J=F8rn Dahl-Stamnes wrote -=3D>
> >
> > >I have replaced my old mail server with a new
> > >one running Fedora Core 4. I did
> > >a clean install but when I try the lists I get:
> > >
> > >      ----- The following addresses had permanent fatal errors -----
> > >   "|/usr/local/majordomo/wrapper resend -l xxx xxx-list"
> > >       (reason: Service unavailable)
> > >       (expanded from: <xxx@dahl-stamnes.net>)
> > >
> > >      ----- Transcript of session follows -----
> > >   Message delivered to mailing list <xxx@dahl-stamnes.net>
> > >   smrsh: "wrapper" not available for sendmail programs (stat failed)
> > >   554 5.0.0 Service unavailable
> > >
> > >I have search for solution on Internet, but nothing works.
> > >
> > >Any suggestions what's wrong?
> >
> >  From the Majordomo FAQ:
> >
> > "2.11 - I get "sh: wrapper not available for sendmail programs"
> > You're on a system which uses smrsh. (sendmail
> > restricted shell). You have to configure smrsh to
> > allow it to execute the wrapper. Normally this is
> > done by creating a symlink in /var/adm/sm.bin (in
> > some it's /etc/smrsh) to Majordomo's wrapper program. "
>
>Thanks. The trick was to create a link /usr/adm/sm.bin (not=
 /var/adm/sm.bin).

It varies from system to system...

Glad it helped.

Ed Kasky
~~~~~~~~~
Randomly Generated Quote (579 of 1229):
I cannot believe in a God who wants to be praised all the time.
-Friedrich Nietzsche, philosopher (1844-1900)


From majordomo-users-owner@greatcircle.com  Mon Apr  6 13:13:41 2009
Received: from yoda.wrenkasky.com (esson.net [216.102.129.43])
	by mycroft.greatcircle.com (Postfix) with ESMTP id E593469008F
	for <majordomo-users@GreatCircle.COM>; Mon,  6 Apr 2009 13:13:40 -0700 (PDT)
Received: from KASKY2.esson.net (kasky.priority.usc.edu [128.125.120.92])
	(authenticated bits=0)
	by yoda.wrenkasky.com (8.14.3/8.14.3) with ESMTP id n36KDRoK025352
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 6 Apr 2009 13:13:33 -0700
Message-Id: <7.0.1.0.2.20090406131246.02463608@esson.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 06 Apr 2009 13:14:07 -0700
To: mr.domo@dahl-stamnes.net
From: Ed Kasky <ed@esson.net>
Subject: Re: Service unavailable...
Cc: majordomo-users@GreatCircle.COM
In-Reply-To: <200904062032.33276.mr.domo@dahl-stamnes.net>
References: <200904061557.08353.mr.domo@dahl-stamnes.net>
 <200904061953.21817.mr.domo@dahl-stamnes.net>
 <7.0.1.0.2.20090406112622.02441c58@esson.net>
 <200904062032.33276.mr.domo@dahl-stamnes.net>
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: 128.125.120.92 is authenticated by a trusted mechanism)
X-Virus-Scanned: clamav-milter 0.95 at yoda.wrenkasky.com
X-Virus-Status: Clean
X-Archive-Number: 200904/7
X-Sequence-Number: 5852

At 11:32 AM Monday, 4/6/2009, J=F8rn Dahl-Stamnes wrote -=3D>
>On Monday 06 April 2009 20:27, you wrote:
> > It varies from system to system...
>
>That was something I found out by doing a search after I got your mail.
>A string on the smrsh told me the path. But I have to create the directory,
>since there was no adm under /usr.
>
> > Glad it helped.
>
>Thanks!

You're welcome -

And you never said what OS you're running.  For=20
RH and Fedora, I used the following to get my install working:

http://www.faqs.org/docs/securing/chap22sec182.html

Ed Kasky
~~~~~~~~~
Randomly Generated Quote (250 of 1229):
(1) Everything depends. (2) Nothing is always. (3) Everything is sometimes.


From majordomo-users-owner@greatcircle.com  Thu Apr 23 04:46:32 2009
Received: from rpc7149.teradata.com (nat13.teradata.com [153.65.16.13])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 32D895902E0
	for <Majordomo-Users@greatcircle.com>; Thu, 23 Apr 2009 04:46:31 -0700 (PDT)
Received: from susday7659.TD.teradata.com (localhost.localdomain [127.0.0.1])
	by rpc7149.teradata.com (8.13.8/8.13.8) with ESMTP id n3NBkUIv024921
	for <Majordomo-Users@greatcircle.com>; Thu, 23 Apr 2009 07:46:31 -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_01C9C409.24973B9C"
Subject: Majordomo list auto deletion bonzo
Date: Thu, 23 Apr 2009 07:46:29 -0400
Message-ID: <AE55119BF3F6A64283D2E238629870A801DD1131@susday7659.TD.teradata.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Majordomo list auto deletion bonzo
Thread-Index: AcnECSPMP7bLjTVbQhym41Aqadd9rg==
From: "Sharma, Vikas" <Vikas.Sharma@Teradata.com>
To: <Majordomo-Users@greatcircle.com>
X-imss-version: 2.053
X-imss-result: Passed
X-imss-scanInfo: M:P L:E SM:0
X-imss-tmaseResult: TT:0 TS:0.0000 TC:00 TRN:0 TV:5.6.1016(16598.005)
X-imss-scores: Clean:87.84936 C:2 M:3 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Archive-Number: 200904/8
X-Sequence-Number: 5853

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9C409.24973B9C
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Guys,

I have a problem with one of the majordomo list. Somewhere in majordomo,
it has been configured that after 300 days of inactivity of particular
majordomo list, the list will be removed.

Can you please guide me how can we exclude that list to be deleted from
majordomo?

This is the message received from majordomo:

This list was last used on 20080625 (yyyymmdd)


If the list is NOT used within 14 Days,
it will be automatically removed from the server.


> thanks and=20
> regards,=20
> Vikas=20
>=20
>=20
>=20

------_=_NextPart_001_01C9C409.24973B9C
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Majordomo list auto deletion bonzo</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Hi Guys,</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">I have a problem with one of =
the majordomo list. Somewhere in majordomo, it has been configured that =
after 300 days of inactivity of particular majordomo list, the list will =
be removed.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">Can you please guide me how can =
we exclude that list to be deleted from majordomo?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Comic Sans MS">This is the message received =
from majordomo:</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"MS Sans Serif">This list was last used on =
20080625 (yyyymmdd)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"MS Sans Serif">If the list is NOT used within =
14 Days,</FONT>

<BR><FONT SIZE=3D2 FACE=3D"MS Sans Serif">it will be automatically =
removed from the server.</FONT>
</P>
<BR>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans MS">thanks =
and</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS"><BR>
</FONT><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Comic Sans =
MS">regards,</FONT><FONT SIZE=3D2 FACE=3D"Comic Sans MS"></FONT>=20

<BR><SPAN LANG=3D"en-gb"><FONT SIZE=3D4 FACE=3D"Monotype =
Corsiva">Vikas</FONT><FONT SIZE=3D2 FACE=3D"Monotype =
Corsiva"></FONT></SPAN><SPAN LANG=3D"en-us"> </SPAN>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C9C409.24973B9C--

From majordomo-users-owner@greatcircle.com  Thu Apr 23 06:15:49 2009
X-Greylist: delayed 2729 seconds by postgrey-1.24 at mycroft; Thu, 23 Apr 2009 06:15:48 PDT
Received: from zappa.brainiac.com (ZAPPA.BRAINIAC.com [68.15.48.189])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 784A66900D4
	for <Majordomo-Users@greatcircle.com>; Thu, 23 Apr 2009 06:15:48 -0700 (PDT)
Received: from brainiac.com (eno [70.181.43.244])
	(authenticated bits=0)
	by zappa.brainiac.com (8.13.1/8.13.1) with ESMTP id n3NCUHgd000682
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <Majordomo-Users@greatcircle.com>; Thu, 23 Apr 2009 08:30:18 -0400
Date: Thu, 23 Apr 2009 08:30:17 -0400
From: Joe Hartley <jh@brainiac.com>
To: <Majordomo-Users@greatcircle.com>
Subject: Re: Majordomo list auto deletion bonzo
Message-Id: <20090423083017.1c485597.jh@brainiac.com>
In-Reply-To: <AE55119BF3F6A64283D2E238629870A801DD1131@susday7659.TD.teradata.com>
References: <AE55119BF3F6A64283D2E238629870A801DD1131@susday7659.TD.teradata.com>
X-Mailer: Sylpheed 2.5.0 (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: 200904/9
X-Sequence-Number: 5854

On Thu, 23 Apr 2009 07:46:29 -0400
"Sharma, Vikas" <Vikas.Sharma@Teradata.com> wrote:
> I have a problem with one of the majordomo list. Somewhere in majordomo,
> it has been configured that after 300 days of inactivity of particular
> majordomo list, the list will be removed.

I've never heard of this as part of majordomo 1.94.  I have a couple of lists
that have been inactive for years, but would still work if someone emailed
the appropriate address.

There's a few bits of data missing here.  Is this on a server you own, or
a list that's hosted by a service?  Which version of majordomo is it?

My guess here is that it's a list hosted somewhere, and this is something
set up by the hosting company.

-- 
======================================================================
       Joe Hartley - UNIX/network Consultant - jh@brainiac.com
 Without deviation from the norm, "progress" is not possible. - FZappa

From majordomo-users-owner@greatcircle.com  Thu Apr 23 06:30:41 2009
X-Greylist: delayed 629 seconds by postgrey-1.24 at mycroft; Thu, 23 Apr 2009 06:30:33 PDT
Received: from hermes1.dur.ac.uk (hermes1.dur.ac.uk [129.234.8.20])
	by mycroft.greatcircle.com (Postfix) with ESMTP id 054566900DD
	for <Majordomo-Users@greatcircle.com>; Thu, 23 Apr 2009 06:30:32 -0700 (PDT)
Received: from smtphost4.dur.ac.uk (smtphost4.dur.ac.uk [129.234.4.18])
	by hermes1.dur.ac.uk (8.13.8/8.13.7) with ESMTP id n3NDJqlb018602;
	Thu, 23 Apr 2009 14:19:56 +0100
Received: from claus.dur.ac.uk (claus.dur.ac.uk [129.234.2.31])
	by smtphost4.dur.ac.uk (8.13.8/8.13.7) with ESMTP id n3NDJeND031781
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Thu, 23 Apr 2009 14:19:40 +0100
Received: from claus.dur.ac.uk (localhost [127.0.0.1])
	by claus.dur.ac.uk (8.14.2/8.11.1) with ESMTP id n3NDJekc007080;
	Thu, 23 Apr 2009 14:19:40 +0100
Received: from localhost (dcl0tdl@localhost)
	by claus.dur.ac.uk (8.14.2/8.14.2/Submit) with ESMTP id n3NDJevf007076;
	Thu, 23 Apr 2009 14:19:40 +0100
Date: Thu, 23 Apr 2009 14:19:39 +0100 (BST)
From: David Lee <t.d.lee@durham.ac.uk>
To: "Sharma, Vikas" <Vikas.Sharma@Teradata.com>
cc: Majordomo-Users@greatcircle.com
Subject: Re: Majordomo list auto deletion bonzo
In-Reply-To: <AE55119BF3F6A64283D2E238629870A801DD1131@susday7659.TD.teradata.com>
Message-ID: <alpine.LFD.2.00.0904231417010.32287@claus.dur.ac.uk>
References: <AE55119BF3F6A64283D2E238629870A801DD1131@susday7659.TD.teradata.com>
User-Agent: Alpine 2.00 (LFD 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-MailScanner-ID: n3NDJeND031781
X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean
X-DurhamAcUk-MailScanner-ID: n3NDJqlb018602
X-Archive-Number: 200904/10
X-Sequence-Number: 5855

On Thu, 23 Apr 2009, Sharma, Vikas wrote:

> I have a problem with one of the majordomo list. Somewhere in majordomo, it
> has been configured that after 300 days of inactivity of particular
> majordomo list, the list will be removed.
> 
> Can you please guide me how can we exclude that list to be deleted from
> majordomo?
> 
> This is the message received from majordomo:
> 
> This list was last used on 20080625 (yyyymmdd)
> 
> 
> If the list is NOT used within 14 Days,
> it will be automatically removed from the server.

I suspect that this is not part of the core majordomo software, but is 
something alongside, added by the site hosting the list.

I recommend that you contact the people who host your majordomo list.

-- 

:  David Lee                                I.T. Service          :
:  Senior Systems Programmer                Computer Centre       :
:  UNIX Team Leader                         Durham University     :
:                                           South Road            :
:  http://www.dur.ac.uk/t.d.lee/            Durham DH1 3LE        :
:  Phone: +44 191 334 2752                  U.K.                  :