>>>>> "CW" == Chan Wilson <email@example.com> writes:
CW> Okay, I'm back from vacation, and have applied Jason's jumbo patch,
CW> plus a few other tidbits. I'm going to check through the mail I've got
CW> saved, and figure out what needs to be finished up for a release.
I'd like to know what everyone would like for me to do with these items on
my todo list, some of which I've been sort of working on:
Move skip_headers out of resend; make it configurable. (resend,
majordomo.cf, config_parse.pl) Make global_delete_headers and
delete_headers, one a per-list config. These delete headers from the
original message before passing it on.
Add global_banned_users and banned_users config variables, which are regexp
arrays. These address the deficiency that exists because majordomo itself
does not check taboo_headers. Banned users are not permitted to do
anything to a list from which they are banned.
Add regexp arrays for restrictions for everything that allows
open/closed/list restrictions (who, lists, info) so people can limit these
to their domains. Sort of like noadvertise. (config_parse.pl, majordomo)
Limit number of unapproved subscribe requests that can appear in a single
message. (majordomo.cf, majordomo)
Add :include: directive to any regexp list, to permit external definition
of long lists of regexps. (config_parse.pl? resend, majordomo?)
I'd be happy to just wait until 1.95/2.0/whatever, but I think that the
first (skip_headers) would go a ways toward completing the move of
configurable data out of the executables. I know that these are not all
mutually exclusive (you can get banned_users functionality with restriction
lists, for example), so I'm just looking for more input.
I'd also like to know just what "beta" means in this context. Is it "code
freeze", or something less restrictive?
Jason L. Tibbitts III - firstname.lastname@example.org - 713/743-8684 - 221SR1
System Manager: University of Houston High Performance Computing Center
1994 PC800 "Kuroneko" DoD# 1723