At 11:04 AM 9/30/00, Jason L Tibbitts III wrote:
>1) The help file for createlist is a bit out of date;
Yep. Fixed in CVS.
>3) We have several instances where a config variable takes a string like
> "ORQ" instead of an enum_array of
> I started this dumbness with default_flags, but I think it needs to
> change. I'd like to just break backwards compatibility with this
> instead of writing a bunch of specialized parsing functions.
It would be extra ugly to upgrade the software and find that your
existing lists don't function anymore. What happens if it finds the
flag-style settings? Which configs are involved?
>5) I wonder if we couldn't get a volunteer to go over all of the config
> variables and rate them according to "expert level".
> This just involves reading the variable descriptions and rating the
> variable from 1 to, say, 5, with 5 being access_rules and 1 being
I wonder if we would all agree on which one goes in which category?
On my system, list owners get these in a boilerplate, and all the
others are set up for them by a config-generation script. I'll start
the ball rolling by suggesting that THESE are the level 1 options:
>configset listname category
>configset listname comments
>configset listname description
>configset listname description_long
>configset listname maxlength
>configset listname message_footer_frequency
>configset listname message_fronter_frequency
>configset listname moderate
>configset listname moderator
>configset listname moderator_group
>configset listname owners
>configset listname post_limits
>configset listname subject_prefix
>configset listname subscribe_policy
>7) I recently received a complaint about Majordomo1 to the effect that the
> default admin_body checks were dumb. We need to review these for Mj2.
Agreed. I chopped many of them out to save time and added X-Loop long ago.
This may vary greatly from site to site, and the default should probably
be less checks so the server doesn't waste time on stuff that users don't do.