Re: [cobalt-users] RaQ4 mailing list - majordomo?

[baltimoremd@xxxxxxxxxxxxxxx]

On Tue, 6 Mar 2001, Carrie Bartkowiak wrote:

> Simple/stupid question:
> In a vsite's settings, there's an option for a mailing list.
> My question is: is this a "majordomo" mailing list or something different?

It's majordomo

> 
> The reason I'm asking:
> One of my clients has used this 'mailing list' feature to create a list. Now
> I'm getting all sorts of bounce messages, subscribe messages, etc. being
> sent to a majordomo list at his domain.

The Cobalt default sends all admintriva messages(the ones you are getting)
to admin(so that makes you the target).

There is an easy way out, if you've kept up to date with the updates, and
that's to make a change in /etc/mail/aliases.majordomo

Search for the site number in question and replace admin with the site
users logon name in every instance for that site.

Save the file, and the site admin will get all the obnoxious messages.
Luckily, the GUI no longer overwrites this file, so you only need make the
change once.

> He's told me he's either getting messages hours and hours late (he's CCing
> them to him home addy for comparison) or not getting them at all.

Don't think it's majordomo related, my users get messages in under 45
seconds from when they are created.

> 
> I have NO experience with majordomo, frankly with all the trouble everyone
> has posted to the list I don't WANT any experience with majordomo. 

It's not that bad, the only thing I left to finger out is the archive and
digest stuff, since the Cobalt Way is "different".


> 
> I've come up with over 1,300 archive posts dealing with majordomo and quite
> frankly, I'm lost. Most of them deal with editing the  majordomo config
> files found in /etc/mail. I'm not going to give this client the root access
> to edit this file so he can get his mailing list working. If he can do it
> through the GUI or through email commands that's cool - but I don't support
> Majordomo, I don't claim to support majordomo, and I'm not going to go
> delving into these files everytime someone uses the GUI to set up a list and
> consequently it doesn't work as it's supposed to.

All of that applied before the RaQ4 update.  Now, the changes I posted
above will get you out of the woods.


The site admin should send email to majordomo@xxxxxxxxxxxxx with the word
help in the body of the message....that will send him/her a help file.

The "undocumented" commands for use by list owners are:

    approve <passwd> {subscribe|unsubscribe} <list> [<address>]
	This is so that you can approve subscription or unsubscription
	actions that need approval by the list owner.  Note that this
	is just a standard "subscribe" or "unsubscribe" command prefixed
	with "approve <password>" (where you substitute the password for
	your list, which is listed above, for "<password>").

    approve <passwd> who <list>
	This allows you to get the list of addresses for your
	anonymous list.  Without the password, even the list owner can
	not see who is on the list.

    passwd <list> <old_passwd> <new_passwd>
	This is so you can change the password for your list, if you
desire.

    newintro <list> <password>
	This is so that you can replace the information file that people
	get when they do "intro <list>" or "subscribe <list>".  It reads
	everything after the "newintro" command to end-of-message or the
	word "EOF" on a line by itself as the new intro for the list.

    newinfo <list> <password>
	This replaces the information file that people get when they do
	"info <list>".  (This file is also sent by "subscribe <list>" if
	the intro file doesn't exist.)  This reads everything after the
	"newinfo" command to end-of-message or the word "EOF" on a line
	by itself as the new info for the list.

    config <list> <password>
        Retrieves a self-documenting configuration file for
        the list <list>.  The <password> can be the password
        contained in the file <list>.passwd or the
        admin_password in the configuration file.

    newconfig <list> <password>
   	Validates and installs a new configuration file.  It reads
	everything after the "newconfig" command to end-of-message or
	the word "EOF" on a line by itself as the new info for the
	list.  The config file is expected to be a complete config
	file as returned by "config".  Incremental changing of the
	config file is not yet supported.  As soon as the config file
	is validated and installed its settings are available for
	use. This is useful to remember if you have multiple commands
	in your mail message since they will be subject to the
	settings of the new config file.  If there is an error in the
	config file (incorrect value...), the config file will not be
	accepted and the error message identifying the problem line(s)
	will be returned to the sender.  Note that only the error
	messages are returned to the sender not the entire config
	file, so it would be a good idea to keep a copy of your
	outgoing email message.

    writeconfig <list> <password> 
	Write a new config file in standard form. Writeconfig forces a
	rewrite of the config file with all default values in place (or
	current values if the config file already exists).  It is
	useful to use after an upgrade of majordomo since it will add
	the new keywords for people to change. It also updates the
	documentation in the file if that has changed.

thom
././././././././././././././././././././././././././././././././././././././
baltimoremd@xxxxxxxxxxxxxxx             Thom LaCosta K3HRN Webmaster  
                      
http://www.baltimoremd.com/             Baltimore's Home Page 
http://www.baltimorehon.com/            Home of the Baltimore Lexicon
http://www.zerobeat.net                 Home of The QRP Web Ring
                                        and Drake Mail List Pages