home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!munnari.oz.au!comp.vuw.ac.nz!zl2tnm!toyunix!don
- Newsgroups: comp.os.vms
- Subject: Re: Alternative callable editors in MAIL? [source+question]
- Message-ID: <6844364@zl2tnm.gen.nz>
- From: don@zl2tnm.gen.nz (Don Stokes)
- Date: 30 Dec 92 15:41:14 GMT
- Sender: news@zl2tnm.gen.nz (GNEWS Version 2.0 news poster.)
- References: <1992Dec30.044645.11200@cnplss5.cnps.philips.nl>
- Distribution: world
- Organization: The Wolery
- Lines: 26
-
- hd@cnplss5.cft.philips.nl (Henk Davids) writes:
- > Now a question: the comment in the C module says that MAIL is an installed
- > module. In fact, it is not. Neither are the shareable images that MAIL will
- > call. How then does MAIL get its privileges (SYSPRIV) to write into other
- > peoples' mail files?
-
- MAIL is unprivileged. It calls the callable mail routines in MAILSHR.EXE.
-
- MAILSHR too is unprivileged; the MAILSHR routines in turn call MAILSHRP.EXE.
- MAILSHRP is a protected sharable image, ie one that can provide user
- written system services. These execute in exec or kernel mode; once in
- exec or kernel mode, the $SETPRV system service will let you enable and
- disable privileges to your heart's content. Thus, MAIL (and more importantly,
- callable MAIL) can write to protected mail files without being given
- privileges explicitly.
-
- HOWEVER, some external mail add-ons, eg internet mailers need privileges
- to deliver mail, and don't use the protected sharable image mechanism to
- obtain these. These packages require MAIL (or anything using callable
- MAIL) to be installed for the add-on to work. (Normal delivery is unaffected
- of course.)
-
- --
- Don Stokes, ZL2TNM (DS555) don@zl2tnm.gen.nz (home)
- Network Manager, Computing Services Centre don@vuw.ac.nz (work)
- Victoria University of Wellington, New Zealand +64-4-495-5052
-