RE: [cobalt-users] Help Installing Majordomo

["Jolley, Carl" <Carl.Jolley@xxxxxxx>]

-----Original Message-----
From: Jeff Lasman [mailto:jblists@xxxxxxxxxxxxx]
Sent: Friday, June 28, 2002 5:06 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] Help Installing Majordomo


"Jolley, Carl" wrote:

> All the functions of majordomo are based on sending e-mail
> commands to majordomo. With the majordomo install on a Raq
> if you can't send e-mail commands to majordomo, it's not installed.

Prior to a specific upgrade (sorry, don't remember which one) the RaQ
would under some circumstances rewrite the list's config files, making
it impossible to keep changes made by email or by majorcool.

I've been told this problem has been fixed.

> My Raq3 has was pre-installed with  the appropriate
> "flavor" of the majordomo wrapper. The pre-installed version of majordomo
> works just fine and gives me access to _all_ the majordomo functionality.

Were you able to create archives and digests?

Were you able to eliminate the "hostname" in the return addresses (often
"www")?

We ended up installing our own Majordomo, which runs fine, for use by
all the RaQ domains.

It does have to be maintained according to Majordomo instructions,
however.  We install majordomo at /home/majordomo.

We do this for ourselves, and for others, for which we charge.
------------------------------------

I'm able to create digests and archives just fine also to use them.
In one case in order to allow the 'www' part to be dropped I set up an
alternate name via DNS and used virtusertable to redirect via
a "catch-all" e-mail from www.domain.com to domain.com I had to
do it this way rather than using an entry in /etc/aliases.majordomo
since the domain record for domain.com was set up as an "A"
record instead of a cname for www.domain.com (someone else does
the DNS). But with this mechanism the list can be mailed to at
either list@xxxxxxxxxxxxxx or list@xxxxxxxxxxx The majordomo generated
replys when it expands hostname however still come back as
list@xxxxxxxxxxxxxxx This seems to be primarily due to the fact that
the form of the alias for a virtual domain, e.g. /home/sites/site2 is
a symbolic link of the form www.domain.com. This is constructed by
the GUI as hostname.domainname and I don't believe that you can leave
the hostname null even though you can specify domain.com as an HTTP
host name alias for the virtual web server. My majordomo files are
installed at /usr/local/majordomo. Down in that directory I have
separate entries for each of the virtual hosts, i.e.
/usr/local/majordomo/www.domain1.com/lists and
/usr/local/majordomo/www.domain2.com/lists, etc. The digest directories
also occurs in this same scheme, i.e. 
/usr/local/majordomo/www.domain1.com/digest