HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SYSTEM@usp.ac.fj"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 21 Jan 93 19:18:08 GMT
From:         "Kevin V. Carosso" <KVC@INNOSOFT.COM>
Subject: RE: TCP/IP Services for VMS v2.0
Newsgroups: bit.listserv.pmdf-l

> We just upgraded our gateway machine to VMS 5.5 and so are now running
> DEC TCP/IP Services for VMS v2.0 instead of Ultrix Connection v1.3.
>
> Boom! There went our PMDF TCP channels.  Since down here we're usually one
> of the last kids on the block to get stuff, I fugure it's safe to ask...

This seem to be a frequently asked question, so I'll send this to the entire
list.

The PMDF SMTP server works just fine with DEC TCP/IP Services V2.0.  No
changes are required.  The problem is that you must shutdown DEC's SMTP
server because the two servers cannot listen on the same port number.

The commands in the UCX Management Utility are:

    $ ucx
    UCX> disable service smtp
    UCX> set noservice smtp

This shuts down DEC's SMTP server and allows our server to run.  Remember
that you must start our server with:

    $ @pmdf_root:[exe]start_ucx_smtpd

You should only need to disable the DEC SMTP service once -- it should be
remembered across reboots.  Of course you need to run START_UCX_SMTPD.COM
during your system startup just like always.

The next release of PMDF supports defining our server as a UCX service if
you choose.  You can also continue to do it the way you do now.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"csc_ted@uhdvx3.dt.uh.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 23 Jan 93 02:37:50 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject: RE: Trying to use *** DELIVER ***
Newsgroups: bit.listserv.pmdf-l

> username is CSC_TEST
>
> a.    I have the USE_MAIL_DELIVERY set to 1
> b.    MAIL.DELIVER has one line--->   * * * A P  SYSTEM
> c.    set forward in%"~CSC_TEST"
>
>
> messages goto the D channel and stay there....
> is there something else i should be doing I am including teh D_MASTER.LOG
> file.

The messages go to the D channel because the forwarding address is incorrect.
The sit in the D channel because VMS MAIL to that remote address is busted.
(VMS MAIL/account problem -- has nothing to do with PMDF.)  See my earlier
reply to you where this is all discussed at much more length.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"JEREMY@vsm.com.au"
X-VMS-Cc: info-pmdf, clyde
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 05:03:01 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: Telex channels for PMDF
Newsgroups: bit.listserv.pmdf-l

> instead.  If PMDF had Telex, they would probably have purchased it.  Perhaps
> there's a whole market that Innosoft are missing out on?

Perhaps, but we have to weigh many things when we consider what we choose to
support with PMDF.  Like everyone else, our resources are limited.  We have
to make sure we don't lose focus on what we do best and thereby risk
disappointing larger interests of current and future PMDF customers.  We
know we can't do everything, but we'll continue to make these decisions
as best we can when we must.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"@cunyvm.cuny.edu:jlw@psulias.bitnet"  "jlw"
X-VMS-Cc: IN%"info-pmdf@INNOSOFT.COM"
MIME-version: 1.0
Content-type: MESSAGE/RFC822
Date:         Wed, 27 Jan 93 03:46:09 GMT
From:         "Craig R. Watkins" <CRW@ICF.HRB.COM>
Subject:      RE: Looking for VMS-based X.500 Client Software
Newsgroups: bit.listserv.pmdf-l

Content-type: TEXT/PLAIN; CHARSET=US-ASCII
>Well, I had pretty good luck a few months ago when I was looking for an NNTP
>client for VMS by asking here on INFO-VAX.  How about an X.500 client for VMS
>-- any implementations?

ISODE is available from ftp.uu.net. "Patches" for a VMS port done by Peter Kay
are available from cc-vms1.massey.ac.nz.

ISODE is an implementation of the ISO protocols which includes a few X.500
user agents.  Two of which, DISH and SD, are ported to VMS.  Transports
supported include most popular TCP/IP's and PSI (X.25).  To build and install
this you need a fairly good understand of OSI protocols and/or lots of time
(and GCC).

DISH is a powerful X.500 UA which is not user friendly and requires a good
understanding of X.500 to use.  SD is friendly screen-oriented front-end
but is somewhat limited.

>Another site (non-VMS) here on campus has implemented a rudimentary X.500
>server, and we want to see if it:
>
>        (1) has our information correctly posted

You could use DISH for this.  I have used DISH to do lookups at Penn State.
I have not been successful with SD because of the X.500 structure at PSU,
but this could probably be solved with some tailoring of SD.


>        (2) can be accessed to the benefit of our users

You may be able to tailor SD.  It might not be too bad if you have
a good background in X.500.

>        (3) might eventually be incorporated into things like our Email
>                (PMDF/VAX Mail)

This should be done for you in the future.  ISODE is the basis for
PMDF-X.400 and most likely will the basis for X.500 directory services
in the future.

Craig
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@SIGURD.INNOSOFT.COM"  "Ned Freed"
X-VMS-Cc: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 15 Jan 93 16:03:28 +0200
Reply-To:     Manu.Mahonen@funet.Fi
From:         Manu Mahonen FUNET <Manu.Mahonen@KORALLI.FUNET.FI>
Subject:      Problems when upgrading PMDF from versio v4.0 to v4.1
Newsgroups: bit.listserv.pmdf-l


We are facing a serious problem, wwhen we are trying to update our
PMDF to v.4.1.

The symptoms are follows:

1) We can install v.4.1 and as far as we knows all goes well at installation.

2) We try to use v.4.0 configuration information. Is it OK?

3) But when we try to use the new version of PMDF then *ALL* channel
programs will die.

For example bn_slave and smtp.

Here is what happens with smtp:

===============================
koralli ~ 1> telnet figbox smtp
Trying 128.214.6.7 ...
Connected to figbox.funet.fi.
Escape character is '^]'.
%PAS-F-HALT, HALT procedure called%TRACE-F-TRACEBACK, symbolic stack
dump followsmodule name     routine name                     line
rel PC    abs PC
                                                           0009566B
0009566B
000D96C3  000D96C3TCP_SLAVE       INIT                             3570
     00000235  00002155TCP_SLAVE       TCP_SLAVE
3629      00000014  00002284Connection closed by foreign host.
Exit 1
koralli ~ 2>
===============================

Now I can't figure out what's wrong. Could You help me, please?


        Manu


:-----------------------------------------------------------------------!
: Manu Mahonen                  Finnish University and research NETwork !
: Phone:   +358 0 457 2240      PL 405                                  !
: Telefax: +358 0 457 2302      SF-02101 Espoo FINLAND                  !
: Internet: Manu.Mahonen@funet.FI                                       !
: X.400:    c=fi; admd=fumail; o=funet; s=Mahonen; g=Manu               !
------------------------------------------------------------------------!
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"csc_ted@uhdvx3.dt.uh.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 23 Jan 93 01:49:04 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject: RE: Trying to use *** DELIVER ***
Newsgroups: bit.listserv.pmdf-l

> I have set up the PMDF DELIVER (4.0) the way the manual describes.
> a. Set forward to in%"~csc_test"

Actually there's a typo in the 4.0 manual; this should be "in%""~csc_test""".
However, that's not the only problem here.

> b. set the USE_

Dunno how to interpret this.

> String copied: "%MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4"
> Error message: "%MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4"
> MAIL_IO_WRITE returning.
> %MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4
> MAIL_IO_WRITE called.
>TOP_OF_STACK called.
>  returning       ERROR_MSG
> Error text.
>copy_descr_to_vstring called.
> String copied: "%MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as
>  output"
> Error message: "%MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as
>  output"
> MAIL_IO_WRITE returning.
> %MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as output
> MAIL_IO_WRITE called.
> TOP_OF_STACK called.
> returning       ERROR_MSG
> Error text.
> copy_descr_to_vstring called.
>String copied: "-RMS-E-PRV, insufficient privilege or file protection violation
   "
> Error message: "-RMS-E-PRV, insufficient privilege or file protection violatio
   n"
> MAIL_IO_WRITE returning.
> -RMS-E-PRV, insufficient privilege or file protection violation

PMDF is merely using VMS MAIL to deliver mail to this user.  (It's not using
DELIVER since the forwarding address was not correct.)  VMS MAIL is having a
problem doing the delivery; it's VMS MAIL which is reporting these errors. You
need to first get delivery to this address working via vanilla VMS MAIL from a
non-privileged account.

It looks like the mail was sent to in%"csc_ted@dt3.dt.uh.edu" which was
forwarded to csc_test@uhdvx4 which translated to UHDVX4::CSC_TEST.  So, you
need to get mail to UHDVX4::CSC_TEST working (from vanilla VMS MAIL,
unprivileged account) first.  Then also fix the forwarding address
("in%""~...""").

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: BHP Research - Melbourne Laboratories
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf-newsgate@mccall.UUCP"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 18 Jan 93 15:58:11 +1000
From:         matthews@VULCAN.RESMEL.BHP.COM.AU
Subject:      a1mail / message router and pmdf-mr
Newsgroups: bit.listserv.pmdf-l


We recently upgraded vms from v5.4-3 to v5.5-2, as well as pathworks ( v4.1 to
v4.1-2) and a1mail (v1.1 to v1.1c), before the upgrade our pmdf/pmdf-mr
software successfully transported binary attached message from/to
a1mail/message-router, since the upgrades, our pmdf users can only receive
contents-type of TEXT/PLAIN for the cover note (which is ok) and
APPLICATION/VMS-RMS for the attached articles no matter what those articles
have been tagged with. The messages seem to be have the correct tag stored in
the header after it has been accepted and placed in MR's message area (MA and
FOREIGN). Any ideas on where to look would be greatly appreciated.

Ian

--


            Ian R. Matthews
   /\/\     VAX Systems & Network Administrator
  / / /\    BHP Research - Melbourne Laboratories
 / / /  \   245 Wellington Rd, Mulgrave, 3170
/ / / /\ \  AUSTRALIA          A.C.N. 004 028 077
\ \/ / / /  Phone   :  +61-3-566-7212
 \  / / /   E-mail  :  matthews@vulcan.resmel.bhp.com.au
  \/\/\/    PSImail :  PSI%0505235633005::MATTHEWS
            Fax     :  +61-3-561-6709
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"MAC@gvg34.gvg.tek.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 21 Jan 93 20:52:33 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Aliases and FAXen
Newsgroups: bit.listserv.pmdf-l

> We have been happily using PMDF-FAX for sometime now.  I now am being asked
> to add lots of aliases to make sending FAXes easier.  The rub is that the
> users would like to use an alias and override some of the attribute pairs
> when then send the message.  This would allow specifying a unique ``please
> deliver this to'' without having to remember the phone number.  Can I do
> this?  How do I do this?

Short of writing your own code, there's no way to do this at present.  I'll
give it some thought though.  Changes I want to make to the 4.2 pop-up FAX
form would allow this but only for aliases in the user's personal alias
database and, possibly, the system-wide alias database.   (If you enter
only the name of an alias then the alias can be retrieved and presented
on the form and can then be edited.... I haven't fully thought this out
though.)

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 21 Jan 93 19:12:56 GMT
From:         RAMELLA@DARWIN.CMH.MCMASTER.CA
Newsgroups: bit.listserv.pmdf-l

 Up here in CANADA  i'm, having trouble getting prices on the modems that
PMDF-FAX supports. Can someone give me the cost of these modems.
Thank in advance
                                       Mark Ramella
--------------------------------------------------------------------------------
   RAMELLA@DARWIN.CMH.MCMASTER.CA                    CHEDOKE-McMASTER HOSPITALS
(416)521-2100 ext. 5153
--------------------------------------------------------------------------------
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"matthews@vulcan.resmel.bhp.com.au"
X-VMS-Cc: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 04:06:14 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: a1mail / message router and pmdf-mr
Newsgroups: bit.listserv.pmdf-l
              18 Jan 1993 15:58:11 +1000"
              <1993Jan18.155811.289@vulcan.resmel.bhp.com.au>

> We recently upgraded vms from v5.4-3 to v5.5-2, as well as pathworks ( v4.1 to
> v4.1-2) and a1mail (v1.1 to v1.1c), before the upgrade our pmdf/pmdf-mr
> software successfully transported binary attached message from/to
> a1mail/message-router, since the upgrades, our pmdf users can only receive
> contents-type of TEXT/PLAIN for the cover note (which is ok) and
> APPLICATION/VMS-RMS for the attached articles no matter what those articles
> have been tagged with.

The rules PMDF uses are simple: a DECBODY7 Message Router bodypart is converted
into an APPLICATION/RMS MIME part. Nothing else will receive this treatment.

I therefore can only conclude that for some reason parts are being sent as
DECBODY7 where previously they were sent as something else. This is totally
under the control of the posting agent; in this case MailWorks. You'll have to
look there for additional information.

I note in passing that DECBODY7 and APPLICATION/VMS-RMS are the only reasonable
things to use for binary attachments. I therefore don't see anything wrong with
how things are working now, unless you're talking about non-binary attachments
being handled this way.

> The messages seem to be have the correct tag stored in
> the header after it has been accepted and placed in MR's message area (MA and
> FOREIGN). Any ideas on where to look would be greatly appreciated.

I believe this indicates that the part is a DECBODY7. PMDF-MR will convert this
to APPLICATION/VMS-RMS; always has, always will.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SKIPPER@MEDCOLPA.BITNET"
X-VMS-Cc: IN%"ipmdf@YMIR.CLAREMONT.EDU"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 26 Jan 93 02:08:59 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Trouble reaching UNC?
Newsgroups: bit.listserv.pmdf-l
              25 Jan 1993 10:26:15 -0500" <01GTXKQSZUSY8WVZ30@ccc.medcolpa.edu>

> Quick question.  I have a user who is trying to reach a user with the
> email address of user@UNC.  PMDF is rewriting this as UNC.BITNET and
> sending it to MAILER@UNC.  This fails with a "invalid domain" type
> message.

I don't understand what you mean by "invalid domain" here. If you mean that
PMDF is giving you this error, then your configuration is busted. UNC is a
perfectly valid BITNET system; its table entry is correct and all of that.

If you're getting some message back from UNC with this in it, then they're
the ones with the problem, not you. I would recommend contacting the
postmaster there if you want to take further steps to resolve this.

>  Upon looking into this, I can easily duplicate the error.
> Interestingly, user@UNCA or user@UNCG will work with no problem.  I am
> running the current version of XMAILER.NAMES and DOMAIN.NAMES.

Not only are these completely different systems, there is every indication
that that they are VAXen whereas UNC is an IBM of some sort. Nothing in the
tables indicates that there is any connection between these systems other
than the fact that they are at the same institution.

> Any idea what is happening?  If more information is needed, I will gladly
> provide it.  Replies can be directed to the net or to me directly.

In general, queries like this cannot be answered usefully unless you include
the _exact_ and _complete_ text of the error message. We can do little aside
from handwaving without more specifics. Please include them initially in the
future.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: PTT Research, The Netherlands
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir.claremont.edu"
X-VMS-Cc: SONNEVELD
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Mailer: PMDF V4.1
X-Favourite-Drink: Hot chocolate
X-Phone-Number: +31 70 332 5362
X-Fax-Number: + 31 70 332 6477
Date:         Wed, 20 Jan 93 15:11:20 +0100
Comments:     This mail was sent by PMDF V4.1
From:         "Rolf E. Sonneveld" <R.E.Sonneveld@RESEARCH.PTT.NL>
Subject:      Is this setup (with redundancy in mail handling) possible?
Newsgroups: bit.listserv.pmdf-l

        Hello, all

        In the first half of  1993  I want to create some  redundancy
        mechanism's for the sending and receiving of  mail.  At  this
        moment, there's one node which  has  research.ptt.nl  on  the
        local channel. All other hosts deliver outgoing mail  to  the
        central host, which rewrite the address to:

        Initials.Surname@research.ptt.nl

        All  incoming  mail  is  delivered  via the central mailhost,
        which has the alias tables, and distributes the  mail  accor-
        ding to the alias found.

        Now I want to have two 'backup' systems for the central host,
        one  running PMDF, one running sendmail. The questions I have
        is:

        1. is  it  possible to use the reverse database on the second
           PMDF  system,  which  then  can send out the mail directly
           without  sending  it  first  to the central system? Or are
           there  any  objections against this setup? I think there's
           no problem, but someone else might foresee some huge pro-
           blems?

        2. Is  it  possible  for  the second PMDF system to have also
           research.ptt.nl  on  the  local  channel?  The problems is
           otherwise,  I  think,  that  PMDF does no alias lookup for
           incoming  mail,  isn't it? I want to list this system with
           the second MX preference for our domain.

        3. The same questions, but then for the sendmail system.

        4. Is  there  any site running this kind of redundancy wihtin
           their message handling?

        Any help appreciated! I'll summarize to the net if I receive
        any private answers.

        Rolf E. Sonneveld
        PTT Research
        The Netherlands
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"Manu.Mahonen@koralli.funet.fi"  "Manu Mahonen FUNET"
X-VMS-Cc: IN%"NED@SIGURD.INNOSOFT.COM"  "Ned Freed",
          IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 02:36:31 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Problems when upgrading PMDF from versio v4.0 to v4.1
Newsgroups: bit.listserv.pmdf-l
              15 Jan 1993 16:03:28 +0200"
              <199301151403.AA14551@koralli.funet.fi>

> 1) We can install v.4.1 and as far as we knows all goes well at installation.

> 2) We try to use v.4.0 configuration information. Is it OK?

It should be. However, if you did something that was illegal but undetected
in V4.0 it may be just plain illegal in V4.1. Another, more likely possibility
is that you need to run PMDF CNBUILD/NOIMAGE/OPTION/MAXIMUM to resize your
configuration.

> 3) But when we try to use the new version of PMDF then *ALL* channel
> programs will die.

This is indicative of a configuration problem.

> For example bn_slave and smtp.

> Here is what happens with smtp:

Unfortunately you did not include an example where a reasonable error message
is produced. Practically any other example will produce a better message than
this. What do you get when you try to seen mail from VMS MAIL or run PMDF
MMTEST? Without a better message (PMDF MMTEST in particular will usually
indicate the exact line where the problem occurs -- it is intended for
diagnosing just this sort of thing) I cannot be more specific about what's
wrong.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 16:14:50 GMT
From:         Lori Gavin <GAVINL1@JAGUAR.UOFS.EDU>
Subject:      RE: WordPerfect Office 3.1
Newsgroups: bit.listserv.pmdf-l


We run WP Office and PMDF together and they work great.  (I assume you are
getting the VMS version of office.)  Office has a vmsmail gateway that works
well, but the smtp agent (with Multinet) was not delivering mail into Office
correctly.  PMDF was the missing peice we needed, and now we have mail from
Office to the intenet and back again with no problems.

                   Lori
                                              UUUUUU         UUUUUU
 ----------------------------------            UUUU           UUUU
|  Lori Gavin                      |           UUUU       SSSSSSSSSSSSSSS
|  VAX System Manager              |           UUUU      SSSSSSSSSSSSSSSSS
|  University of Scranton          |           UUUU      SSSS UUUU     SSSS
|                                  |           UUUU      SSSS UUUU
|                                  |           UUUU      SSSSSSSSSSSSSSSSS
|INTERNET: GAVINL1@JAGUAR.UOFS.EDU |           UUUUUUUUUUUSSSSSSSSSSSSSSSSS
|   Phone: (717)941-6133           |            UUUUUUUUUUUUUUUUU      SSSS
 ----------------------------------                      SSSS          SSSS
                                                         SSSSSSSSSSSSSSSSSS
                                                          SSSSSSSSSSSSSSSS


SYS$LOGIN:SIGNATURE.TXT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU