Re: [cobalt-users] Majordomo vSite List Owners

["Gregory Ogorek" <greg@xxxxxxxxxxxxxx>]

> "Gregory Ogorek" <greg@xxxxxxxxxxxxxx> wrote:
> > I have all the RaQ products and they all behave the same.  When a vsite
> > owner creates a list, the SERVER admin gets all the bounced and error
> > messages.  The vsite admin gets nothing.
> >
> > How can they manage their lists if they don't know that 50 of the 200
> > members don't exist?
> >
> > I'm having to go in and physically change the "admin" of the list owner
to
> > the actual username of the vsite admin.  I was wondering if there was a
> > group name or something similar to use.
> >
> > My goal:  When a vsite admin creates a list, any and all messages go
> either
> > to the vsite admin(s) or to the vsite admin(s) and server admin.
>
> The solution you don't want to hear is to install your own copy of
majordomo
> or rewrite Cobalt's scripts that build the alias files.  I was recently
told
> by a list member that a Sun employee is making modifications to some
Cobalt
> features, including the specific Majordomo problem you describe.  I don't
> know that the list member wants his/her name here so perhaps this person
> will see the post or you can contact Sun to let them know that this is on
> your wishlist.
>

Thanks Steve.  I've talked to Sun/Cobalt and I can't get this answered.

I'm editing /et/aliases.majordomo and substituting the admin username for
the actual username of the siteadmin in the list owner line.  Is there a
better way to do this?  Like an alias to the site admin for the specific
site?  This way I wouldn't have to figure out the siteadmin for each list
entry.

But, even if I install my own version of majordomo.  Does this mean that the
GUI is now moot?


GregO