> Wilson Chan's thoughts on revamping the entire access interface to
> be more coherent hold a lot of appeal, but I doubt that anything all
> encompassing as the Netscape server uses will be simpler and easier for
> the clueless to configure. Allow/deny probably stretches the limits of
> comprehension of a lot of folks I've seen asking for help. I'd like to
> see an allow/deny scheme that uses regexps like [no]advertise (and makes
> better, if not complete, use of Perl's regexps), but that's probably
> also too much unless the regexps were in addition to lists of simple
> text strings.
Wolfe Dave's comments on the above believe me to lead that perl uses
he too much. :-) On one hand, you say that the Netscape config is
confusing, and then you turn around and propose using Perl regexps.
I dislike the idea of using files to control such access, because
outside list admins don't have control over them. I'd rather find a
way to allow that capability w/in majordomo....
(First name Chan, Last Name Wilson. Oriental, I ain't,
unless blond hair & red beard count...)
Chan Wilson --- firstname.lastname@example.org --- +4138-433-760
Silicon Graphics, SA. Cortaillod, Switzerland.
"Network Analyst" && Irix Guru && Gravitational Engineer