home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: dan@innosoft.com (Daniel C. Newman)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: Limiting access to outgoing mail.
- Message-ID: <01GOKRXC7ASI9TCNH3@INNOSOFT.COM>
- Date: 9 Sep 92 17:05:16 GMT
- Organization: The Internet
- Lines: 22
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 09 Sep 1992 10:05:16 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GOKRY15FGI96VY3E@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"Don.Rainwater@UC.EDU"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- > I'd like to be able to limit access to non-local (off-node) email.
- > I'm thinking that I can define a rights id, say 'NO_OUTMAIL' for example,
- > and set the appropriate image with an ACL such that anyone holding that id
- > cannot send internet mail messages. My questions are simple: Will this
- > work? and, which image(s) should be set this way?
-
- This won't work since the users only run VMS MAIL or DECWindows MAIL. They
- don't run the actual images which send outbound mail. Instead, you probably
- want to associated this rightlist identifier with, say, your TCP/IP channel.
- You do this by merely specifying the rightlist id as a channel keyword; e.g.,
-
- mtcp_local single smtp mx no_outmail
-
- Then, only processes with the no_outmail rightslist id can queue mail to
- the mtcp_local channel. Be sure to grant this rightslist id to whatever
- accounts PMDF may run under!
-
- In PMDF V4.2, there will be a mapping file table which you can use to do very
- elaborate channel access schemes which will even allow you to reject incoming
- mail.
-
- Dan
-