HDTenEightyP/NetNews huggingface dataset:
X-Envelope-to: medlib-l@ubvm.cc.buffalo.edu
X-VMS-To: THENIC::IN%"medlib-l@ubvm.cc.buffalo.edu"
Newsgroups: bit.listserv.medlib-l
Date:         Fri, 21 Aug 1992 14:24:00 CST
From:         TOM%JASON.DECNET@RELAY.THE.NET
Subject:      COPYRIGHT
X-To:         medlib-l@ubvm.cc.buffalo.edu

Despite the AAP's accusation that libraries are abusing the fair use
concept by making photocopies for interlibrary lending, our library
is very diligent about using the Cop
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Fri, 14 Aug 1992 09:19:26 EDT
From:         James Brady <BRADY@PORTLAND.BITNET>
Subject:      Nursing resources on the internet

I'm not sure if this is the right group to be asking this question of
but a patron has asked for information on the availability of electronic
meetings- lists, special interest groups, newsgroups, bulletin boards
etc., for the following: 1. Nursing home personnel. Owners, administrators,
nursing staff, etc.  2. Nursing educators or issues related to nursing
education aimed at the Nursing faculty.  3. Are there nursing education
subgroups? For example, nutrition or gerontology. 4. Finally, are there
groups for students enrolled in nursing programs?  Please respond to me
personally or to the list if you think others might be interested.

Thanks in advance.

       James Brady
       Head of Special Services
       U. of Southern Maine Library
       Portland

       Brady@Portland.Bitnet
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Mon, 17 Aug 1992 16:36:46 CDT
Comments:     Converted from PROFS to RFC822 format by PUMP V2.2
From:         "Mary E. Helms --UNMCVM(MHELMS)" <MHELMS@UNMCVM.BITNET>
Subject:      Online '92 in Chicago

Anyone out there planning on attending Online '92 in Chicago this October
25-28? I am looking for someone to share a hotel room (female, non-smoking
please!). The meeting will be at the Palmer House ($159/double).  I am open to
sharing at a different hotel. Any leads are most appreciated.Thanks.

Mary Helms
University of Nesbraska Medical Center
McGoogan Library
phone: 402-559-7099
e-mail: mhelms@unmcvm.bitnet    or    mhelms@unmcvm.unmc.edu
From: backon@vms.huji.ac.il
Newsgroups: bit.listserv.medlib-l
Subject: Re: OMIM Instruction
Date: 16 Aug 92 09:42:13 GMT
Distribution: world
Organization: The Hebrew University of Jerusalem

In article <15171374@UMICHUM.BITNET>, Ruth Riley <USERGF16@UMICHUM.BITNET> writes:
> Hi, Ruth Riley here at the University of Michigan Taubman Medical
> Library.  I am wondering if anyone has incorporated instruction in the
> use of OMIM (Online Mendelian Inheritance in Man) into their medical
> school curriculum. Thanks.
>
> ruth.riley@um.cc.umich.edu (internet)
> usergf16@umich.um (bitnet)


I'm a clinician (internal medicine) at a university-affiliated hospital. I've
demonstrated OMIM to two staff geneticists, one pediatric ophthalmologist, and
a pediatric neurologist. To put it mildly, they were somewhat flabbergasted.
I've also demonstrated it to a research immunologist who was interested in
HLA antigens.

I think that OMIM has an important role in clinical teaching and should be
introduced to residents in pediatrics and genetics.

Josh

Dr. Josh Backon
backon@VMS.HUJI.AC.IL









Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"JLW%PSULIAS.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 19:55:16 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Channel Keyword "logging" and BITNET_DOMAINS.COM
X-To:         JLW@PSULIAS, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Setting logging on the various channels produced by BITNET_DOMAINS.COM is
trivial if you use the defaults feature of PMDF. See section 3.2.5.7 (page
3-51) in the V4.1 manual for details. The defaults feature is also available
and documented in V4.0 in section 3.2.5.8 on page 3-42.

This mechanism is preferrabled to having BITNET_DOMAINS.COM put stuff on
every single channel it produces.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TANNER@Cerritos.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 02:40:06 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: V4.1-10 mailserv questions
X-To:         TANNER@Cerritos.EDU, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> * Where do I define the COMMAND_LIMIT, MAXBLOCKS and MAXLINES options?

You put them all in a per-channel option file. The usual format PMDF uses
is used here.

> * What is the format of the MAILSERV_ACCESS file?

This isn't a file per se -- it is a mapping in the PMDF mappings file. The
format is currently undocumented. I hope to post the format to this list at
some point in the future.

> * Mailserv appears to reply to the envelope From: rather than the header From:
>   field.  I modified the V4.0 mailserv to use the header field and had much
>   better control over processing UUCP return addresses.

This is incorrect. MAILSERV uses the Reply-To: header, if one is present, to
control this. Otherwise the From: address is used. If that doesn't exist or is
illegal the envelope From: is used. And if that's illegal the message is junked
without any response.

This usage seems entirely appropriate to me for replies from MAILSERV.

> * If I request a file /MODE=BLOCK/ENCODING=UUENCODE I get back (1) a foreign
>  file format message and (2) a FDL message that contains:

> Content-transfer-encoding: X-UUENCODE
> Comments: These headers describe a message previously delivered in foreign fil
   e
>  format.

>   Has the file been decoded automatically from uuencode format to foreign file
>   format for me, or is it not being uuencoded at all?

The message was encoded and then decoded before you got it. In any case, PMDF
does not support direct transmission of binary files without encoding, so the
file had to be encoded for you to even get a response.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Date-warning: Date header was inserted by NAUVAX.UCC.NAU.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@SIGURD.INNOSOFT.COM"
X-VMS-Cc: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 17:48:58 GMT
From:         Chris Michels <cvm@NAUVAX.UCC.NAU.EDU>
Subject:      RE: Changing To: header on alias list
X-To:         NED@SIGURD.INNOSOFT.COM
X-cc:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>There should be no reason to put the actual recipient in the To: header.
>This information is available in the message envelope up until the instant
>of final delivery, and all the mechanisms that need this information can
>reference it. Once the message is delivered it is abundantly clear who it
>is to and this information becomes superfluous.
>
>So the answer is "no, there is no way to do this because there is no reasn
>we know of to work this way". If you have a reason for wanting things to
>work differently please elaborate on it further and we'll see what we can
>do.
>
>                                Ned

The reason I want to change the To: header is this:  I want to use MIT's
BULLETIN program to "archive" messages sent to the distribution list.  I do
this by adding an 'archive' user to the alias.  BULLETIN extracts the messages
from the archive user's mail file and puts them in the proper folder.  The
problem is that BULLETIN requires the message be addressed to the user or it
will not extract it from the mail file.

For example,  I have a list called 'netgroup' in this list I place a user
called 'netgroup_ar'.  I then create a folder in bulletin that uses the
netgroup_ar user's mail as the source for messages to go in the folder.
Bulletin requires that the message be addresseed to netgroup_ar not netgroup.

If anyone knows of another simple way to accomplish this, please let me know.
Otherwise, I would like the mail to be addressed to the user not the alias.
Thanks.

--------------------------------------------------------------------------
Chris Michels -- Systems Programmer             cvm@nauvax.ucc.nau.edu
Northern Arizona University -- Flagstaff, AZ    cvm@nauvax.bitnet
Phone: (602) 523-6495                           N7YIU
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DAN@INNOSOFT.COM"
X-VMS-Cc: IN%"robin_goldstone@macgate.csuchico.edu",
          IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>
Date:         Fri, 21 Aug 92 03:34:17 GMT
From:         John C Klensin <KLENSIN@INFOODS.MIT.EDU>
Subject:      RE: deliver and 'vacation' processing
X-To:         DAN@INNOSOFT.COM
X-cc:         robin_goldstone@macgate.csuchico.edu, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>By the way, be sure that your VACATION.COM keeps a record of addresses that
>have been sent a vacation message to.  Use this list to then prevent sending
>repeated messages to.  If you don't do this, then you can create some nasty
>mailing loops whereby you keep on sending mail to a mailing list....

If you must use vacation things at all, you will be a *lot* less
unpopular if you figure out which lists you are subscribed to and
take precautions to *not* send little notes to them.  In addition to
whatever you set up that is specific to the sending patterns of each
particular list, note that any mail that is not addressed to you under
whatever normal individual names you maintain has reasonable odds of
being addressed to a list; excluding all of these from automatic
message generation is not a bad idea.  Doing this in a simple way
may exclude notification of senders of messages on which you are a "cc"
recipient, which is not necessarily a bad idea either.

If you want to get a tad more sophisticated about this, use the
rebuild facilities (1,2,3) to grab ENVELOPE-FROM: Many Internet list
exploders use names that match owner-*  or *request@ in that field and
can thus be indentified.

At the moment, I can't think of a simple heuristic that will capture all
LISTSERV stuff, but there probably is one.

Suggestion:  If someone works out a good set of generic DELIVER rules to
simulate a "vacation" function without driving list members and
maintainers it would be really nice to make them available so that each
person who has this idea doesn't have to re-invent it (or come back to
a mailbox full of abuse).

    john
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Utah Valley Community College
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, 17 Aug 92 21:14:40 GMT
Comments:     Warning -- original Sender: tag was news@PARK.UVCC.EDU
From:         coleve@CC.UVCC.EDU
Subject:      RE: Problem with printer channel?
X-To:         ipmdf-newsgate@mccall.UUCP
Newsgroups: bit.listserv.pmdf-l

In article <01GNNMC2FAKY8WXYL0@ucsvc.ucs.unimelb.edu.au>,
 c.chaundy@its.unimelb.edu.au writes:
> Prior to PMDF V4.1, we had a simplistic printer channel setup which just
> read the list of files to be processed in MASTER.COM and took the 'to'
> address and used the /note switch to print the message out on SYS$PRINT.
>
> With V4.1, I want to upgrade to use the standard PMDF printer channel and
> wondered how it reacted if the mailbox part of the 'to' address was not a
> AVPL to avoid having to re-educate users and make bulk changes to a huge
> number of directory channel files - I got the answer - *badly*.
 [...]
> Apart from the fact that I will have to move to AVPL pairs (it would have
> been nice to default mailboxes that are not AVPL pairs to just 'Attention:'),
> I assume this other behaviour is most definitely a bug in the printer channel.
>

 I'm trying a rewrite rule like:
    HARDCOPY.UVCC.EDU        /AT=$U@HARDCOPY.UVCC.EDU

seems to do the job...
--
-- Vern Cole -- Systems Manager -- Utah Valley Community College --
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 10:01:02 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject: Help. Cannot install PMDF 4.1 -- %MOUNT-F-NOTLABELMT,
              tape is not labeled
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

When trying to instal PMDF 4.1-10 I get

%MOUNT-F-NOTLABELMT, tape is not labeled
%VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected event.

I cannot mount it with /ov=id either.

????????

Did I get a blank tape?

-Jim Dryfoos
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"
X-VMS-Cc: IN%"MITCHELL@UTHSCSA.BITNET", IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>
Date:         Thu, 13 Aug 92 02:26:05 GMT
From:         John C Klensin <KLENSIN@INFOODS.MIT.EDU>
Subject:      RE: two minor points
X-To:         NED@SIGURD.INNOSOFT.COM
X-cc:         MITCHELL@UTHSCSA, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

>Finally, it is the current recommended practice. (See RFC1343 (number may be
>wrong here) for details and an explanation.) It is very likely to become
>standard practice in the near future, and any other format is likely to be
>strongly deprecated.

Ned,
  Unless I've missed something fairly major here, this statement, which
you have repeated a couple of times, is going a bit far.  To clarify the
context, RFC1343 is Nathaniel's "UA Configuration" piece, you are
presumably talking about RFC1344, his "implications for gateways" piece.
True?
  If so, it is the "current recommended practice" because Nathaniel
recommended it in a personal opinion document that was published as an
RFC.  That document is not on the standards track and neither the fact
that no alternatives have been published nor the fact that there was
relative silence when an earlier draft was exposed for WG comment make
it significantly more than one person's opinion.
  Now, I think it would be reasonable for you to say, e.g., "this looks
like a good idea, and other people think it would be a good idea too,
and we have put it into PMDF in order that, when the issue does come up
on the standards track, we can argue for it on the basis of
implementation experience and existing practice".
   But that is a rather different sort of statement.

    john
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"robin_goldstone@macgate.csuchico.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 20:39:34 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: mailing list automation
X-To:         robin_goldstone@macgate.csuchico.edu, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> Our campus currently has a mailing list set up that any user can send to, whic
   h
> will in turn be re-distributed to everyone on the campus e-mail system.  This
> list, called USERS, is managed by PMDF as follows:
>
> In VMS mail, there is a forwarding address which forwards USERS to IN%USERS
>
> In the PMDF alias file, there is an entry for USERS:
> USERS: <dua1:[local]users.dis
>
> So when people send to USERS on the VAX, it re-directs to all the people in th
   e
> users.dis file.
>
> I have been asked to make a change in this procedure, such that messages sent
> to USERS get stored on the VAX, and sent out at midnight i.e. deferred
>delivery.  I won't go into details about why they want to do this, it is
> political.
>
> How can I implement this?  I have looked at DELIVER  but I don't really have
> any experience using it, so I am not sure it will do what I need. The messages
> need to be sent back out, retaining their original headers and everything else
   .
>  If not DELIVER, then what?  Can I define a new channel, that uses a different
> batch queue, that I can stop and then start every night at midnight?  I would
> have to be able to set up a re-write rule based on the left hand side of the
> address to do this.  Is that possible?

    The best way to do this is with a reprocessing channel which runs in a batch
queue of its own.  Have a periodic job start that batch queue up around midnight
and stop it at 4 AM (or whenever).

-- aliases.; ---

users: users-list@reprocess.acme.com
users-list: <dua1:[local]users.dis

-----------------

Then add to your PMDF.CNF file the following rewrite rule

        reprocess.acme.com    $U@reprocess.acme.com

and then add the following channel block

        reprocess queue REPROCESS_BATCH
        reprocess.acme.com

    If you already have a reprocessing channel, then just add
"reprocess.acme.com" to the list of hosts identified with the channel and add
the "queue REPROCESS_BATCH" keyword to the first line of the channel block.
(At present you can have only one reprocessing channel; this restriction can,
however, be lifted very easily....)

    In place of "REPROCESS_BATCH" use whatever batch queue name you want to.
It's up to you to set up a batch job which runs starts and stops that queue.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF
X-VMS-Cc: GHC
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 21 Aug 92 21:44:44 GMT
From:         Gerson H Cohen <GHC@VGER.NIDDK.NIH.GOV>
Subject:      Gopher and WAIS - a report
X-To:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

Thanks to all who have responded with information on where to find WAIS.
I now have a working version of Gopher and WAIS.

Gopher may be gotten from boombox.micro.umn.unc with full sources and
ready to go under MultiNet in the directory pub/gopher/VMS/vmsclient.v06.

WAIS may be gotten from several sources (I presume that Gopher may also,
but I wasn't looking for them) but I chose mcclb0.med.nyu.edu at the
kind invitation of Ross Smith.  The directory [anonymous] contains a
compressed backup of a fully working WAIS with _sources_.  I picked up
a neat menu driver for wais [called waismenu] from aarvark.ucs.uoknor.edu,
a twg site.  This menu has the nearest thing I have seen to documentaion
for WAIS.

I hope that this is useful to others.

Gerson

-
Dr Gerson H Cohen
National Institutes of Health
Bldg 2, Room 312
Bethesda, MD  20892
'Phone: (301)496-4295
Internet: ghc@vger.niddk.nih.gov
BITNet:   ghc@nihklmb
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Columbia University
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:         Wed, 19 Aug 92 01:24:39 GMT
Comments:     Warning -- original Sender: tag was usenet@NEWS.COLUMBIA.EDU
From:         Wei Dong Wu <wdw3@CUNIXB.CC.COLUMBIA.EDU>
Subject:      question
X-To:         ipmdf-newsgate@mccall.UUCP
Newsgroups: bit.listserv.pmdf-l


Is it possible for a machine that only has internet connection to send
mail to .bitnet address using PMDF alone (without Jnet) through
gateway machines?

Sorry if this is FAQ. BTW is there a FAQ for this group?


Weidong Wu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"andrewr@itd.adelaide.edu.au"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Mail-System-Version: <VAX-MM(312)+TOPSLIB(155)+PMDF(4.1)@INFOODS.MIT.EDU>
Date:         Mon, 17 Aug 92 10:33:10 GMT
From:         John C Klensin <KLENSIN@INFOODS.MIT.EDU>
Subject:      RE: Mail User agents
X-To:         andrewr@itd.adelaide.edu.au
X-cc:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

>       This doesn't get around one of the problems I was raising,
>which is that these "mainframe derived" schemes only allow for the
>user to read their mail from one physical location, their PC. This is
>not acceptable in our institution, which is why we've gone cc:Mail and

Absolutely, it does not solve that problem.  And, in general, it is a
bad idea for several other reasons as well.  Whether cc:Mail is a right
solution in an "anyone can log in from nearly anyplace and be able to
access their mail, etc" environment is really a separate question: there
seems to be a strong feeling around here that such arrangements should
require much stronger and safer user authentication than most of these
micro-based products offer.  But that is really a separate issue whose
answer depends more on your alternatives and your user community than it
does on the technical issues.

   john
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Date-warning: Date header was inserted by NAUVAX.UCC.NAU.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 00:57:04 GMT
From:         Chris Michels <cvm@NAUVAX.UCC.NAU.EDU>
Subject:      Changing To: header on alias list
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

We have several simple distribution lists in PMDF that are implemented as
aliases.  The To: header line in the message shows the name of the alias.
Can I get PMDF to put the address of the user on the To: header instead?

----------------------------------------------------------------------
Chris Michels -- Systems Programmer             cvm@nauvax.ucc.nau.edu
Northern Arizona University -- Flagstaff, AZ    cvm@nauvax.bitnet
Phone: (602) 523-6495                           N7YIU
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"PAVER@Maximillion.mcc.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 20 Aug 92 19:20:11 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Deliver and MM-32
X-To:         PAVER@Maximillion.mcc.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> Does DELIVER work with MM-32 under PMDF 4.1? I read the manual, but
> it only talks about using Deliver with VMS mail.

DELIVER works with VMS MAIL and MultiNet V3.1 MM.  It does not work with
any other version of MM.  The support for MultiNet MM was new to PMDF V4.1
and MultiNet V3.1

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU