home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!wupost!darwin.sura.net!paladin.american.edu!auvm!INNOSOFT.COM!DAN
- Errors-to: epmdf@YMIR.BITNET
- X-Envelope-to: PMDF-L@IRLEARN.BITNET
- X-VMS-To: IN%"fineberg@wupost.wustl.edu"
- X-VMS-Cc: IPMDF
- MIME-version: 1.0
- Content-type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-transfer-encoding: 7BIT
- Message-ID: <01GR8DFGAS4I8ZGF26@YMIR.CLAREMONT.EDU>
- Date: Tue, 17 Nov 92 06:47:04 GMT
- Sender: PMDF Distribution List <PMDF-L@IRLEARN.BITNET>
- From: "Daniel C. Newman" <DAN@INNOSOFT.COM>
- Subject: RE: Additional mailing list security
- Newsgroups: bit.listserv.pmdf-l
- Lines: 17
-
- >>With the MAPPINGS file now in PMDF, it is possible to control who add
- >>subscribe and unsubscribe users from MAILSERV mailing lists, get copies
- >>of the list, etc., but has anyone implemented a system where only a
- >>restricted group of users may actually mail to particular lists?
- >
- > Hmm. When I read the 4.1 docs it seemed trivial to limit who could post
- > to a list, but allowing mailed list ownership didn't seem to be there at
- > all. So what did my denseness ignore? That is where in the manual is
- > the reference to controlling who may add and delete users?
-
- This information did not make it into the printed documentation. Look in your
- on-line docs (4.1-10 or later). It should be under the MAILSERV documentation.
- This additional documentation (complete with crucial typo) was posted to
- info-pmd back in September (or thereabouts) by Ned. Let mek know (anyone)
- who wants this information e-mailed to them.
-
- Dan
-