>>>>> "SP" == Sean Proske <sean@wwd.org> writes:
SP> Is the reason that no info file is sent to new list owners simply
SP> because one has not yet been written, or has it also not been coded
SP> for?
Both.
SP> Also, is it possible to use the access_rules variable to prevent
SP> non-subscribers from being able to post to the list? If so, how?
You don't even have to do that, if you don't want to get into access_rules
stuff (which is seriously underdocumented right now). Mj2 supports
restrict_post just like Mj1 did (if you're familiar with Mj1); you just do:
configset listname restrict_post = listname
Anyway, the access_rules stanza looks like:
post
deny
!@MAIN
SP> As for my prior suggestion as to Majordomo's cron jobs... in light of
SP> this successful experiment with putting commands in a text file, 1 per
SP> line as I have done for the makemap to rebuild vut databases, I think I
SP> have a workaround that would enable administrators to simply create 1
SP> cron job and never have to edit it regardless of how many new domains
SP> get set up.
That's reasonable. I'll add it to the TODO list.
- J<
References:
|
|
