Date:  Wed, 25 Oct 2006 14:44:42 -0700
From:  Dustin Krysak <chaos (at mark) digitalcollision.com>
Subject:  [coba-e:07721] Re: revisited: Majordomo how to fix
To:  coba-e (at mark) bluequartz.org
Message-Id:  <453FDACA.1070507 (at mark) digitalcollision.com>
In-Reply-To:  <200610252034.k9PKYXwX016140 (at mark) srv1.nickelnetworks.com>
References:  <200610252034.k9PKYXwX016140 (at mark) srv1.nickelnetworks.com>
X-Mail-Count: 07721



Paul Aviles wrote:
> Dustin, I am late in answering (as always..:-) but I have majordomo working
> since the very first relase of BQ and even before. Can you try adding a new
> user to the site, then manually add it to the mailing list and see if the
> entries inside /etc/mail/ get modified? Also, there are config files under
> /usr/local.. (somethig..) not in front of a server and can't remember now,
> but should be the config files for majordomo for each site there.  Are those
> being updated properly? Can you also close the registration and make it
> require approval and see if the list owner gets an email?
>
> Regards,
>
> Paul Aviles
> Nickel Networks
Also in one of my previous posts I had cat n grepped my aliases.majordomo

and did not see the "488-testlist-list" - well in digging deeper, it is 
obviously used in one of the aliases:

488-testlist:   "|/usr/local/majordomo/wrapper resend -l testlist -C 
/usr/local/majordomo/sites/site22/majordomo.cf 488-testlist-list, nobody"

Dustin