From: CRDGW2::CRDGW2::MRGATE::"SMTP::CUNYVM.CUNY.EDU::POSTMAST%YMIR.BITNET" 9-AUG-1989 01:03 To: MRGATE::"ARISIA::EVERHART" Subj: PMDF - ALL-IN-1 channel Resent-From: @CUNYVM.CUNY.EDU:postmast@YMIR.BITNET Received: from YMIR.BITNET by CUNYVM.CUNY.EDU (IBM VM SMTP R1.2.1MX) with BSMTP id 8765; Wed, 09 Aug 89 01:00:15 EDT Resent-Message-Id: <7054EAACF1DF2000A3@YMIR.BITNET> Message-Id: <7063A7E353DF20006B@YMIR.BITNET> Received: from JNET-DAEMON by YMIR.BITNET; Tue, 8 Aug 89 19:33 PDT Received: From SBCCMAIL(SKAPUR) by YMIR with Jnet id 5278 for IPMDF@YMIR; Tue, 8 Aug 89 19:32 PDT Resent-Date: Tue, 8 Aug 89 20:45 PDT Date: Tue, 8 Aug 89 16:32 EDT From: Sanjay Kapur Subject: PMDF - ALL-IN-1 channel Resent-To: INFO-PMDF-LIST2@YMIR.BITNET To: ipmdf@YMIR.BITNET, allin1-l@SBCCVM.BITNET, jnet-l@MARIST.BITNET Errors-To: postmast@YMIR.BITNET Reply-To: Sanjay Kapur X-Envelope-To: Everhart%Arisia.decnet@crd.ge.com, STODOLA@curie.rm.fccc.edu, pmdf-users@icdc.llnl.gov, mark%jrs@ics.uci.edu, byrd@mscf.med.upenn.edu, jzj@msr.EPM.ORNL.GOV, wlb@ncifcrf.GOV, @RELAY.CS.NET:steve@nemo.math.okstate.edu, pmdf-local@netnews.upenn.edu, BOOTH%NHRC.nosc.mil@nosc.mil, x_borge_k%use.uio.uninett@nta-vax.arpa, SHERMAN@NUSC.NAVY.MIL, LOCKREY@PNLG.PNL.GOV, rdiaz@PRESTO.IG.COM, INFO_PMDF%CCAVAX.CAMB.COM@RELAY.CS.NET, pmdf-list%sh.ac.nz@RELAY.CS.NET, infopmdf%rtpark.rtp.ge.com@RELAY.CS.NET, INFOPMDF%DELPHI.INTEL.COM@RELAY.CS.NET, gregg%ihlpb.att.com@relay.cs.net, AC012125%wkuvx1.wku.edu@RELAY.CS.NET, vasoll%a.cs.okstate.edu@RELAY.CS.NET, rvs%bu-it.bu.edu@relay.cs.net, MICRO2.SCHWER%CRVAX.SRI.COM@RELAY.CS.NET, CHR%UTRC%utrcgw.utc.com@RELAY.CS.NET, vms-pmdf%ulowell.edu@RELAY.CS.NET, infopmdf%cl.uh.edu%uhvax1.uh.edu@relay.cs.net, newman%gibbs.rutgers.edu@relay.cs.net, pmdfnotes%sleepy.egr.msu.edu@relay.cs.net, SYSMAN%hilbert%gte-labs.csnet@RELAY.CS.NET, RMALOUF%SBMSRC.SUNYSB.EDU@RELAY.CS.NET, long@sh.cs.net X-Vms-To: IN%"ipmdf@ymir.bitnet",IN%"allin1-l@sbccvm",IN%"jnet-l@marist" We have developed an ALL-IN-1 to PMDF gateway. We have replaced Message Router with PMDF and we do not run Message Router. The gateway should not interfere with Message Router but I have not tested it. We are running PMDF 3.0, ALL-IN-1 2.3 and VMS 5.1. If a user wants to read their VMSmail in ALL-IN-1, they need to have their mail forwarded to an address of the following form: in%"user@allin1" When VMSmail (or PMDF mail) comes for the user, the allin1 PMDF channel batch job starts and creates a file that is executed under the ALL-IN-1 manager's username in a spawned process. This command file invokes ALL-IN-1, reads in the message to be delivered, creates a new cabinet document out of it, modifies its cabinet attributes and does a PUT_PENDING on the document. If the from address is FROM_USER@HOST.DOMAIN then the return address in ALL-IN-1 will be _IN%"FROM_USER@HOST.DOMAIN". This address is replyable if appropriate SPECIAL.COM and SPECIAL.CMU files exist in OA$LIB. The ALL-IN-1 to PMDF gateway has been working at our site for the last two weeks without problems. If a) you are interested in this software, b) want to test the software, remove all bugs in the gateway, c) you know PMDF and ALL-IN-1 and d) have the C, PASCAL and FORTRAN compilers, please send me a mail message. Sanjay Kapur Computing Center State University of New York at Stony Brook Stony Brook, NY 11794-2400 skapur@ccmail.sunysb.edu (our Internet link is down today) skapur@sbccmail.bitnet