MajorCool: A Web Interface To Majordomo (This is a copy of the MajorCool master documentation set)

Introduction Usage System Requirements Installation Configuration Future Direction Licensing, FAQs, & Credits

Because MajorCool is of little use on its own, its licensing restrictions mirror that of Majordomo. In brief summary, MajorCool is:

• Copyrighted.
• Free to use.
• As-is. No warranty or guarantees.

Where can I get the latest version of MajorCool?

http://ncrinfo.ncr.com/pub/contrib/unix/MajorCool/ is the definitive site. Always check there for the latest version. A quick way to get there from within the application is to click on the MajorCool banner graphic and follow the link within.

Where can I ask questions about MajorCool?

It is preferable that support for MajorCool be obtained via the Majordomo-users mailing list at GreatCircle.COM. The many others who have successfully implemented the application can assist you in this forum. Hopefully, the knowledge base will continue to grow along with that of Majordomo's.

If you request assistance on the Majordomo list, please make the debugging process easier by identifying:

• MajorCool version, including:
  • the chosen siteaddr() function -- eg, custom-made or one selected from the distribution
  • any config options that might be relevant to your problem/question
• Majordomo version
• Perl version
• Web server vendor/version
• Web browser vendor/version (if behavior is browser-dependent)

To subscribe to the list, send an appropriate subscribe command to Majordomo@GreatCircle.COM.

Why isn't there a separate mailing list just for MajorCool?

Although MajorCool is different from Majordomo, the two are tightly integrated. As Majordomo evolves, so too will MajorCool (hopefully). More importantly, it is planned that MajorCool will eventually be included in the distribution as an integral component of future Majordomo releases.

Do I really need a Web server on my mail machine?

Yes. MajorCool requires direct file-system level access to the Majordomo lists and config files -- you cannot install it on a separate machine. If you prefer to provide your Web access from a location other than the target mail server, I suggest looking at the MailServ interface.

When "browsing", why...
...doesn't MajorCool show any of the lists that I have on my server?
...aren't any of my recently-added lists showing up in the pull-down?
...isn't my updated list description getting displayed?

In BROWSE mode, available lists and some of their attributes are taken from the Key Cache file rather than directly from the Majordomo lists directory. Go back and check the Key Cache:

• Does it exist?
• Is it where you told the cf file it would be?
• Is it non-empty?
• Are the permissions such that it is readable by the Web process?
• Have lists been changed since the Cache was last updated?

After any changes (config updates or list additions/deletions), you must remember to re-run the Cache program. The burden of this task can be minimized by adding a cron job or applying the contributed auto-cache patch to Majordomo.

Why do I get the "not" symbol (red circle with slash) on some/all of my lists when I use BROWSE mode?

1. If 'QuickView' was selected, this is normal. Subscription tests have been disabled for faster access, and without knowing the state of each subscription, the values cannot be changed.
2. If the optional web_access keyword was implemented, some list owners may have elected to exclude their lists from MajorCool access.
3. In all other cases, a list is marked with that symbol to indicate that it is "not configured": you have implemented owner keyword support without assigning a value to the owner variable in the list.config file. Or maybe you added the value but the Key Cache file has not been updated yet? Remember: the owner support is completely optional; if you don't add the owner keyword to Majordomo, you won't have to modify all your config files. The main value of the owner addition is the ability to automate alias creation.

   I'm trying to access the (User's Guide|Admin Guide|FAQ) listed in the Local Majordomo/MajorCool Notes Help section, but the URL is giving me errors.

   The site.info file was included in the distribution for example purposes only. The URLs are behind the NCR firewall and not generally accessible. In actuality, both Guides (Admin and User) are copies of the documentation that came with Majordomo). If you use the sample site.info file, you should tailor it to display information specific to your site rather than continue to reference unreachable NCR locations.

   When I press the 'GO' button on the BROWSE screen, the browser spins but eventually stops without leaving the initial BROWSE screen. I am using Netscape browser and Apache server.

   There is a bug in Apache 1.3.x (and earlier betas) that broke "server push" scripts. As of 1.3.2, that bug has been fixed. Your options are: upgrade/patch the server, disable server-push special effects ($opt_multipart) in the MajorCool config file, or use a non-Netscape browser.

MajorCool development was started in Feb'96 by Matt Bateman of NCR Corporation (before leaving for greener pastures [literally -- Oregon is so much more verdant than Southern California]). With Matt's departure, the torch was passed to Bill Houle, where the code was folded, spindled, mutilated, and prepared for release back to the Majordomo community in April of that year. (Even if you manage to locate Matt, please don't ask him technical questions about MajorCool -- the current version bears very little resemblance to his initial prototype.)

In addition to the many users who reported bugs and offered ideas for improvement, we would also like to thank the following people who directly contributed to the development of MajorCool:

Rick Hernandez <rick@sparc.sandiegoca.ncr.com>
Tom Moore <tom.moore@daytonoh.ncr.com>
Dave A. Roger <daroger@tisc.com>
Marisa Giancarla <marisa@andromedia.com>
Tom White <tom@net.msstate.edu>
Karsten Mueller <karsten@zora.nadir.org>
Ricardo Marek <ricky@ornet.co.il>
Steve Snodgrass <ssnodgra@fore.com>

Send some words of encouragement to Ben Stassert & Ash <{dasb,dszd0g}@dasb.fhda.edu> and Rick Perry <perry@news.ee.vill.edu>, whose detail and diligence helped to shore up the security of the program.

Special praise to Gunnar Helliesen <gunnar@bitcon.no> who spurred me to think about Majordomo virtual host support (resulting in the addition of the multiple configuration file feature) and was nice enough to help me test the beta implementation on his server.

Credit power-user Martin.Fogel@ElSegundoCA.NCR.COM for requesting numerous features which I initially thought "who the heck would need to do that?!?" yet in the end turned out to be well worth implementing.

Extra special thanks to Cary.Canning and Robin.Cooper.Wood (both @SanDiegoCA.NCR.COM). Cary's User-Interface Design Review led to the creation of the Menu-style interface, which was complemented quite nicely by Robin's graphic touch.