Index: [Article Count Order] [Thread]

Date:  Wed, 25 Oct 2006 14:24:23 -0700
From:  Dustin Krysak <chaos (at mark) digitalcollision.com>
Subject:  [coba-e:07719] Re: revisited: Majordomo how to fix
To:  coba-e (at mark) bluequartz.org
Message-Id:  <453FD607.7060903 (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: 07719

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
Good day Paul... Thanks for the reply...

Here are the steps I took.

-logged in a bq admin.
-created the domain.
-added the site administrator "listadmin"
-logged out.
-logged in as listadmin.
-created the mailing list (testlist).
-set listadmin as a local subscriber and as the list administrator.
-logged out.

Then sent a message to : majordomo (at mark) list.domain.com

with (in the body):

subscribe testlist

Now I ssh'd into the BQ server.

cd /etc/mail

[root (at mark) bq mail]# cat aliases.majordomo | grep listadmin
488-testlist-owner:     listadmin
488-testlist-approval:  listadmin
owner-488-testlist:     listadmin

[root@bq mail]# cat virtusertable | grep listadmin
listadmin (at mark) list.domain.com  listadmin



Now based on my error, the system is looking for:

488-testlist-list

Which as we can see did not show up in my grep results. Is that the cause of evil?

Then I looked at the majordomo.cf located in the vsites majordomo directory, and did see the proper domain in there, etc.

Then if I went into the lists directory and looked at the appropriate config files, I had:

[root@bq lists]# cat testlist
(it had all the proper addresses including the FQDN email address of the listadmin.)

[root (at mark) bq lists]# cat testlist.administrator 
(it had the proper address - the FQDN email address of the listadmin.)


[root (at mark) bq lists]# cat testlist.config 
#AUTOSTART
admin_passwd = ****
approve_passwd = ****
administrivia = no
advertise << END
/.*/
END
noadvertise << END
END
who_access = list
subject_prefix = [$LIST] 
message_headers << END
X-Majordomo-Version: $VERSION
END
subscribe_policy = open
unsubscribe_policy = open
restrict_post = testlist:testlist.administrator
maxlength = 512000
reply_to = $SENDER
#AUTOSTOP


Does anything seem out of sorts?



Dustin