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: Deliver and MM-32
- Message-ID: <01GNU6ASL5PE94E5N5@INNOSOFT.COM>
- Date: 21 Aug 92 17:04:49 GMT
- Organization: The Internet
- Lines: 14
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 21 Aug 1992 09:04:49 -0800 (PST)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GNU6BNYEPU95NVJA@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"dsroberts@beckman.com"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- > We just noticed a problem with this today. DELIVER seems to have stopped
- > working with MultiNet MM as of PMDF 4.1. Perhaps a logical needs to be set or
- > something?
-
- If it was working before and has now stopped, then someone has probably changed
- something on your system (e.g., gotten rid of the batch queue for DELIVER
- processing, cut over to the PMDF Process Symbiont and not set up a queue other
- than MAIL$BATCH for DELIVER processing to occur in, defined one of the MultiNet
- or PMDF logicals which inhibit delivery of any mail to MM, set a PMDF switch
- in the PMDF_ option file to inhibit any delivery to MultiNet MM). The bottom
- line is that if it was working before and isn't now, it probably means that
- somebody changed something on your system.
-
- Dan
-