[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] Re: Cobalt - Digest Config problem?
- Subject: [cobalt-users] Re: Cobalt - Digest Config problem?
- From: mbowman@xxxxxxxxxx
- Date: Mon Dec 2 12:39:01 2002
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Ok i added majordomo to /etc/mail/trusted-users and restarted sendmail
I modified my aliases.majordomo to the following
majordomo_site23: "|/usr/local/majordomo/wrapper -v site23 -f
www.sithlord.net majordomo"
owner-majordomo_site23: admin
majordomo_site23-owner: owner-majordomo_site23
imperialfleet_site23: "|/usr/local/majordomo/wrapper -v site23 -f
www.sithlord.net resend -l imperialfleet,imperialfleet_site23-list"
imperialfleet_site23-list:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet,imperialfleet_site23-digestify
imperialfleet_site23-request: "|/usr/local/majordomo/wrapper -v site23 -f
www.sithlord.net request-answer imperialfleet"
imperialfleet_site23-approval: lvader@xxxxxxxxxxxx
owner-imperialfleet_site23: lvader@xxxxxxxxxxxx
imperialfleet_site23-owner: owner-imperialfleet_site23
imperialfleet_site23-digestify: "|/usr/local/majordomo/wrapper digest -r -C
-l imperialfleet-digest imperialfleet_site23-digest-list"
imperialfleet_site23-digest: imperialfleet_site23,
imperialfleet_site23-digest-owner: lvader@xxxxxxxxxxxx
imperialfleet_site23-digest-request: "|/usr/local/majordomo/wrapper -v
site23 -f www.sithlord.net majordomo -l imperialfleet-digest"
imperialfleet_site23-digest-approval: imperialfleet_site23-approval
imperialfleet_site23-digest-list:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet-digest
I get this....
----- The following addresses had permanent fatal errors -----
"|/usr/local/majordomo/wrapper -v site23 -f www.sithlord.net resend -l
imperialfleet,imperialfleet_site23-list"
(reason: 9)
(expanded from: <imperialfleet@xxxxxxxxxxxx>)
----- Transcript of session follows -----
Message delivered to mailing list <imperialfleet@xxxxxxxxxxxx>
554 5.3.0 "|/usr/local/majordomo/wrapper -v site23 -f www.sithlord.net
resend -l imperialfleet,imperialfleet_site23-list"... unknown mailer error
9
I also copied this to the Cobalt Users List, in an effort to get some help
from any Cobalt Majordomo users.
Thanks
Matthew K Bowman,
Systems Administrator; Hostmaster; Miva Administrator
Universal Digital Communications, Mansfield Ohio.
Daniel Liston
<dliston@sonny To: mbowman@xxxxxxxxxx,
majordomo-users@xxxxxxxxxxxxxxx
.org> cc:
Subject: Re: Cobalt - Digest
Config problem?
11/29/2002
10:44 PM
I can't see "bold" print in my email client, but I will take a guess at
where you are looking for additional information.
mbowman@xxxxxxxxxx wrote:
> Dan - thanks for the posting on the Archive/Digest HOW-TO.
You (and everyone else) are very welcome. I have other docs on installing
from the greatcircle tarball vs. rpm or pkg bundles, and one on hosting
virtual domain's mailing lists.
> I'm trying to adopt the info from that into a Majordomo installation on a
> Cobalt RaQ Server. I am including extracts from the
> HOW-To with my setup which I hope would benefit other users for future
use.
> Items in bold are issues that I probably need to get fixed.
>
>> Assumptions:
>> Majordomo version 1.94.4
>
>We have majordomo-1.94.4-raqC13
I have not worked with this version directly, but have helped others
with it in the past. I think most if not all the directions in the
archive/digest document will be valid.
>> Sendmail version 8.8 (or higher)
>
>We have sendmail-8.10.2-C1
Same comment as above.
>> You have created a majordomo user and majordomo group.
>> The majordomo $HOME directory is /usr/local/majordomo and is owned by
user
>> majordomo and group majordomo.
>
>! Cobalt doesn't have the majordomo user/group by setup default. In
No entry in /etc/passwd for majordomo? I might have to think on this
awhile.
> /usr/local/majordomo, Files are owned by 'mail'
> except for wrapper which is owned by root. I haven't changed Cobalt's
> variation of it. I have created a majordomo user and
> group but haven't changed any file permissions as yet.
Be careful here. Majordomo's wrapper is very dependent on the uid:gid
and $HOME directory that are compiled into it. Wrapper should be owned
by root and even have the suid flag set on it.
>> The smrsh directory (if used) is /etc/smrsh and holds a link owned by
root
>> to /usr/local/majordomo/wrapper.
>
>/etc/smrsh doesn't exist on this server
No problem. You won't have to bother with creating a link to wrapper then.
>> There are no group or world "writable" directories in the path to
>> /usr/local/majordomo, including / (root).
>
>! Sometimes /etc/mail/aliases.majordomo gets set to 664 I have to run
> chmod 644 aliases.majordomo regularly
If you have to do this very often, you may consider making a cron job
to do it for you.
>> Sendmail "trusts" majordomo. (a Tmajordomo line in sendmail.cf or a
>> majordomo line in sendmail.ct).
>
>! Doesn't exist in Cobalt's variation. Should it??
See if you sendmail.cf has a line beginning with Ft. This will be the
file to add the majordomo user to.
>> Sendmail.cf only recognizes one aliases file. (/etc/aliases)
>
>It recognises both /etc/aliases and /etc/aliases.majordomo
I made a change to my document regarding this.
>> Sendmail.mc uses the "always_add_domain" feature.
>
>! Doesn't exist in Cobalt's variation .Should it??
I added a comment about this too. Only required for majordomo-1.94.5.
>> Majordomo's config file is /etc/majordomo.cf (can be a root owned link
to
>> /usr/local/majordomo/majordomo.cf)
>
>It is /usr/local/majordomo/majordomo.cf on this server
I wonder if all the scripts $cf variables have also been modified to use
that location, or it is covered by $ENV{"MAJORDOMO_CF}.
>> The majordomo.cf variables are defined statically.
>> (no `/bin/dnsdomainname` in the $whereami variable).
>> You already have a working list that utilizes resend.
>> (wrapper resend -l <listname> <listname>-outgoing).
>
>See my aliases.majordomo below
>
> The listname is imperialfleet.
>
> [root www.sithlord.net]# ls -l
> total 16
> drwxr-x--- 3 mail site23 4096 Nov 29 09:58 digests
> drwxr-x--- 2 mail site23 4096 Jun 3 23:56 files
> drwxr-x--- 2 mail site23 4096 Nov 29 10:14 lists
> -rw-r----- 1 mail site23 240 Nov 29 10:12 log
> [root www.sithlord.net]# pwd
> /usr/local/majordomo/www.sithlord.net
> [root lists]# ls -l
> total 40
> -rw-rw---- 1 mail site23 38 Oct 22 08:28 imperialfleet
> -rw-rw---- 1 mail site23 38 Nov 29 10:12
imperialfleet-digest
> -rw-rw---- 1 mail site23 16226 Nov 29 10:03
imperialfleet-digest.config
> -rw-rw---- 1 mail site23 16192 Oct 22 08:59
imperialfleet.config
>
>
> Here are the lines from my aliases.majordomo
>
> majordomo_site23: "|/usr/local/majordomo/wrapper -v site23 -f
www.sithlord.net majordomo"
> owner-majordomo_site23: admin
> majordomo_site23-owner: owner-majordomo_site23
# I added this separation line between majordomo and your list(s) aliases
> imperialfleet_site23: "|/usr/local/majordomo/wrapper -v site23 -f
www.sithlord.net resend -l imperialfleet,imperialfleet_site23-list"
> imperialfleet_site23-list:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet,imperialfleet-digestify
> imperialfleet_site23-request: "|/usr/local/majordomo/wrapper -v site23
-f www.sithlord.net request-answer imperialfleet"
> imperialfleet_site23-approval: lvader@xxxxxxxxxxxx
> owner-imperialfleet_site23: lvader@xxxxxxxxxxxx
> imperialfleet_site23-owner: owner-imperialfleet_site23
> imperialfleet-digestify: "|/usr/local/majordomo/wrapper digest -r
-C -l imperialfleet-digest imperialfleet-digest-outgoing"
> imperialfleet-digest: imperialfleet_site23,
> imperialfleet-digest-owner: lvader@xxxxxxxxxxxx
> imperialfleet-digest-request: "|/usr/local/majordomo/wrapper majordomo
-l imperialfleet-digest"
> imperialfleet-digest-approval: imperialfleet_site23-approval
> imperialfleet-digest-outgoing:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet-digest
>
> imperialfleet_site23-list is the equivalent of test-outgoing. It appears
> that Cobalt's majordomo install doesn't use -outgoing just -list.
Either I misunderstood your directory structure, or your aliases still need
some work. The way I see it right now, probably both. It also appears
that
your list and domain are hosted by a server other than your own, or you are
treating your own domain (and list) as if it were on a hosted domain. Why
is the _site23 on the majordomo alias and the imperialfleet aliases, but
not
on the imperialfleet-digest aliases. I have never seen
arguments/parameters
for "wrapper" before either. Should -v site23 and -f www.sithlord.net be
listed after "wrapper" for those digest aliases too? I would think the
-digest aliases would look more like this; (be careful of line wrapping)
imperialfleet_site23-list:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet,imperialfleet_site23-digestify
imperialfleet_site23-digestify: "|/usr/local/majordomo/wrapper digest -r -C
-l imperialfleet-digest imperialfleet_site23-digest-list"
imperialfleet_site23-digest: imperialfleet_site23,
imperialfleet_site23-digest-owner: lvader@xxxxxxxxxxxx
imperialfleet_site23-digest-request: "|/usr/local/majordomo/wrapper -v
site23 -f www.sithlord.net majordomo -l imperialfleet-digest"
imperialfleet_site23-digest-approval: imperialfleet_site23-approval
imperialfleet_site23-digest-list:
:include:/usr/local/majordomo/www.sithlord.net/lists/imperialfleet-digest
If the above suggestions turn out to be correct, you can ignore the rest
of these comments.
Regardless, even the aliases above look strangely incorrect. If I were
hosting the sithlord.net domain, following the examples from the archive
document I posted, using -list in place of -outgoing and a directory
called files instead of archives, my aliases file would look something
like this;
sithlord.net-majordomo: "|/usr/local/majordomo/wrapper majordomo
-C /usr/local/majordomo/sithlord.net/majordomo.cf"
sithlord.net-majordomo-owner: admin@xxxxxxxxxxxx
#
sithlord.net-imperialfleet: "|/usr/local/majordomo/wrapper resend
-C /usr/local/majordomo/sithlord.net/majordomo.cf
-l imperialfleet sithlord.net-imperialfleet-list,nobody"
sithlord.net-imperialfleet-owner: lvader@xxxxxxxxxxxx,
sithlord.net-imperialfleet-list:
:include:/usr/local/majordomo/sithlord.net/lists/imperialfleet,
sithlord.net-imperialfleet-digestify
sithlord.net-imperialfleet-digestify: "|/usr/local/majordomo/wrapper digest
-r -C /usr/local/majordomo/sithlord.net/majordomo.cf
-l imperialfleet-digest sithlord.net-imperialfleet-digest-list"
sithlord.net-imperialfleet-request: "|/usr/local/majordomo/wrapper
majordomo
-C /usr/local/majordomo/sithlord.net/majordomo.cf
-l imperialfleet"
sithlord.net-imperialfleet-approval: lvader@xxxxxxxxxxxx,
sithlord.net-imperialfleet-digest-request: "|/usr/local/majordomo/wrapper
majordomo
-C /usr/local/majordomo/sithlord.net/majordomo.cf
-l imperialfleet-digest"
sithlord.net-imperialfleet-digest-approval: lvader@xxxxxxxxxxxx,
and the virtusertable something like this;
majordomo@xxxxxxxxxxxx sithlord.net-majordomo
majordomo-owner@xxxxxxxxxxxx sithlord.net-majordomo-owner
owner-majordomo@xxxxxxxxxxxx sithlord.net-majordomo-owner
#
imperialfleet@xxxxxxxxxxxx sithlord.net-imperialfleet
owner-imperialfleet@xxxxxxxxxxxx sithlord.net-imperialfleet-owner
imperialfleet-owner@xxxxxxxxxxxx sithlord.net-imperialfleet-owner
imperialfleet-list@xxxxxxxxxxxx error:nouser User
unknown
imperialfleet-request@xxxxxxxxxxxx
sithlord.net-imperialfleet-request
imperialfleet-approval@xxxxxxxxxxxx
sithlord.net-imperialfleet-approval
imperialfleet-digest@xxxxxxxxxxxx
sithlord.net-imperialfleet
owner-imperialfleet-digest@xxxxxxxxxxxx
sithlord.net-imperialfleet-owner
imperialfleet-digest-owner@xxxxxxxxxxxx
sithlord.net-imperialfleet-owner
imperialfleet-digest-list@xxxxxxxxxxxx error:nouser User
unknown
imperialfleet-digest-request@xxxxxxxxxxxx
sithlord.net-imperialfleet-digest-request
imperialfleet-digest-approval@xxxxxxxxxxxx
sithlord.net-imperialfleet-digest-approval
The virtusertable assumes the same owner for the list and the digest.
The "trick" to these configurations, is the sithlord.net/majordomo.cf
would contain an extra variable and look something like this;
$whereami = "sithlord.net";
$datadir = "/usr/local/majordomo/sithlord.net";
$listdir = "$datadir/lists";
$digest_work_dir = "$datadir/digests";
$filedir = "$datadir/files";
$log = "$datadir/log";
> Now to the testing part.
> The regular list worked fine. I can subscribe and unsubscribe to the
> imperialfleet-digest.
> I can no longer post to the imperialfleet list. Here is the error:
> Message delivered to mailing list <imperialfleet@xxxxxxxxxxxx>
> 554 5.3.0 "|/usr/local/majordomo/wrapper -v site23 -f www.sithlord.net
> resend -l imperialfleet,imperialfleet_site23-list"... unknown mailer
error 9
Since subscribing and unsubscribing work, your emails to the majordomo
address must be working. I am still confused by the -v and -f args to
the wrapper though. Let me know if any of the above helps before I
start to dig into your new problem. Check your aliases for typos with
an eagle eye. One incorrect character can cause great pain.
I am not understanding the significance of the _site23 on the aliases.
This might be something for you to watch carefully while you are
checking for typos.
Dan Liston