Re: [cobalt-users] Help Installing Majordomo

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

"Jolley, Carl" wrote:

> 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

You really don't have to do that.

> and used virtusertable to redirect via
> a "catch-all" e-mail from www.domain.com to domain.com

This should simply create a loop since the catchall from domain.com to
www.domain.com is installed by the Raq whenever you setup email for a
site and enter a domain alias for receiving email.

> 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).

It shouldn't have anything to do with who does DNS.  At one time, as the
Internet expanded, it became quite common to direct all undiferentiated
traffice to just "domain.com" to a particular host, often
"www.domain.com" using CNAMEs, there's no reason to do it.  Generally
CNAMEs require twice the DNS traffic as do A records, so it's arguable
that they should only be used to point to domains over which you have no
control.  For example, if you outsource usenet news for your users, you
might create a CNAME to point news.yourdomain.com to news.provider.com,
so if your news provider ever changes the IP# news.yourdomain.com will
still work.

There is a requirement that any system pointed to by an MX record must
be represented by an A record, for example, if you're using an MX record
to direct mail to joe@xxxxxxxxxx to the server www.domain.com, then
www.domain.com must be represented to by an A record.

> 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

That's the problem for many of us, especially those of us who host lists
commercially.

> 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.

I don't think it's got anything to do with that...

I think it's part of the listname.config file; for example, from the
config file for one of our lists:

 # resend_host          [word] (undef) <resend>
 # The host name that is appended to all address strings specified
 # for resend.
 resend_host         = email-lists.com

Presumably if you can make changes to listname.config that don't get
overwritten by the gui you can fix this.  Let us know if you try it and
if it works for you; if you do, you might want to also change the
reply_to field, so domain.com will appear in the reply_to instead of
www.domain.com.

> 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

That's a bit scary for us, since /usr/local is installed in the "/"
partition; ours is less than 3/4 of a gig in size, and we archive a lot
of list digests for clients.  You might want to move them to /home/local
or /home/majordomo or something, and create a symbolic link.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net, P. O. Box 52672, Riverside, CA  92517
voice: +1 909 778-9980  *  fax: +1 909 548-9484