Rackshack has majordomo lists available however

I have tried to execute a number of the advanced majordomo commands with no success.

I am interested in limiting the number of posts a subscriber can send per day/week etc.

None of these seem to work only the very basic command set.... am i doing something wrong or are the advanced domo commands not available?

Thanks

In Him,
JMb

Cobalt's GUI interface to Majordomo is extremely limited in what it allows you to control on a given Majordomo list.

However, if you send an email to

Majordomo@<your_domain>

with this in the body:

config <name_of_your_list> <password_for_your_list>

you'll get back a reply listing the configuration for the list.


If you want to change the configuration for a given list, you can either:

(1) send an email to
Majordomo@<your_domain>
in the body
newconfig <name_of_your_list> <password_for_your_list>

<your_new_config_elements_go_here>
<EOF>

or...

(2) Manually edit the Majordomo config file for the list (login via SSH, etc.)

Where is the majordomo config file for a virtual site anyway???

Originally posted by qhasxeem
Where is the majordomo config file for a virtual site anyway???

On my RaQ3, the name of the config file, for a list named "mylist", used on the virtual domain "mydomain.com" would be:

mylist.config

( Format is: <Name_Of_List>.config )

Which would be located in the dir:

/usr/local/majordomo/www.mydomain.com/lists

( Format is: /usr/local/majordomo/www.<Domain_Name>/lists )

The other file located in that dir, a file named "mylist" (without a file extension) in this case, would be a text file containing the names (e-mail addr.'s) of the subscribers to the list "mylist".

NOTE #1: Once you edit the config file, any changes or updates you make via the RaQ GUI will usually change everything in the config file back to the (RaQ) defaults! (Undoing all of your manual changes made to the config file previously.)

NOTE #2: As with any "manual" change to any RaQ's config file, it's always a good idea to make a backup of the original file before making a "manual" change to the file, so you have something to "fall back on" in the event something goes wrong! ;)

Thanks that worked. :D