HDTenEightyP/NetNews huggingface dataset:
From: klensin@infoods.mit.edu (John C Klensin)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: deliver and 'vacation' processing
Date: 20 Aug 92 23:27:25 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 19:27:25 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: robin_goldstone@macgate.csuchico.edu, IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNT7H9SW8295NSZT@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"DAN@INNOSOFT.COM"
X-Vms-Cc: IN%"robin_goldstone@macgate.csuchico.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>

>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
From: andrewr@itd.adelaide.edu.au
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mail User agents
Date: 13 Aug 92 22:14:58 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Aug 1992 08:14:58 +1000
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNJDXWT3KY94DXYO@INNOSOFT.COM>
X-Vms-To: IN%"KNAPKE%BUTLERU.bitnet@UICVM.UIC.EDU" "David J. Knapke
X-Vms-Cc: IN%"info-pmdf@INNOSOFT.COM"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
X-Mts: smtp

In message <01GNIXWQBL7M8Y4XA1@BUTLERU.BITNET> you write:

+ >        We use Novell servers, as they appear as AppleShare File
+ >Servers, so you have both Mac's and PC's accessing the same post
+ >office sitting on the Novell server.
+
+ You certainly cannot connect 350-400 mac's to a file server.  The cost
+ of installing 3 (100 Mac users per server) additional Novell file servers
+ would be slightly prohibitive.

	OK, in our case we have 14 Novell file servers scattered
around campus, with a cc:Mail post office on each. I would be hesitant
to put 350-400 Macs on any one machine no matter what it was. And
Novell file servers can be used for things other than just mail, but
then so can most of the other solutions presented.

	Andrew.

/*
 * Andrew Rutherford                 andrewr@itd.adelaide.edu.au
 * +61 8 228 5669            Real Programmers always confuse Christmas and
 * Room 1060, Adelaide Uni      Halloween because OCT 31 == DEC 25 !
 */
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mail User agents
From: andrewr@itd.adelaide.edu.au
Date: 14 Aug 1992 08:29:26 +1000
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 14 Aug 1992 08:29:26 +1000
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNJEGYE7XE94DXYO@INNOSOFT.COM>
X-Vms-To: IN%"KVC@SUMMER.INNOSOFT.COM"  "Kevin V. Carosso"
X-Vms-Cc: IN%"info-pmdf@INNOSOFT.COM"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
X-Mts: smtp

In message <01GNIZNYGI108WZVZS@SUMMER.INNOSOFT.COM> Kevin writes:

+ This is the major reason in my mind why the PC mail solutions are all inadequate.
+ They all try to base the mail transport on file services, which simply cannot
+ scale adequately.  With mail services you need connectivity to millions of
+ hosts, not dozens.  SMTP based on a host to host wire protocol easily handles
+ a million hosts today (Internet).  Try doing that if SMTP were replaced with
+ something like BSMTP on NFS.  And even if you did it, who'd manage the
+ 100,000 post offices? In a worldwide network it could never work.  A large
+ multi-national corporation isn't much different.

	The real problem is that you can usually rely on VMS or Unix
machines to be up 24 hours a day to receive mail, and you can connect
to them from anywhere, whereas PC's and Mac's are usually only on
during office hours, and you can't connect to them from elsewhere to
check your mail. Thus the SMTP direct to your desk concept won't work,
as the basic assumptions about machine avalibility aren't held.
	So the concept employed is that there is one central place
that stays up all day, and you can access from all over the place. The
problem now is that PC and Mac users expect a GUI as opposed to the
CUI's we all use for VMS/Unix based mail. So the software companies
are forced to have some wonderful interface that'll knock your socks
off, and is necesarily different from the type that gets shunted over
SMTP.
	In summary, I agree that the current state of affairs is
woeful, but given the time, locality, and user expectation
constraints, I don't think it's going to get a lot better in the near
future. And you're never going to get micro software houses to
standardise on one mail format, unless it is almost forced on them
from the outside.
	I'm sure I can here a flamethrower warming up...

	Andrew.

/*
 * Andrew Rutherford                 andrewr@itd.adelaide.edu.au
 * +61 8 228 5669            Real Programmers always confuse Christmas and
 * Room 1060, Adelaide Uni      Halloween because OCT 31 == DEC 25 !
 */
From: knapke%butleru.bitnet@uicvm.uic.edu (David J. Knapke 317/283-9420)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mail User agents
Date: 13 Aug 92 13:08:59 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Aug 1992 08:08:59 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNITW0WNCY94DUAV@INNOSOFT.COM>
X-Vms-To: IN%"andrewr@itd.adelaide.edu.au"
X-Vms-Cc: IN%"info-pmdf@innosoft.com"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


>+ cc:Mail looked pretty good as well, but we are not sure how we are going to
>+ serve it to close to 400 Macs.  On the DOS side, its easy, we have Novell

>        We use Novell servers, as they appear as AppleShare File
>Servers, so you have both Mac's and PC's accessing the same post
>office sitting on the Novell server.

You certainly cannot connect 350-400 mac's to a file server.  The cost
of installing 3 (100 Mac users per server) additional Novell file servers
would be slightly prohibitive.

David J. Knapke                       Knapke@ButlerU.BITNET
Computer Center                          Assistant Director
Butler University                     Information Resources
Indianapolis, IN  46208                      (317) 283-9420
USA                                     Fax: (317) 283-9740
From: mitchell%uthscsa.bitnet@ymir.claremont.edu (Scott J. Mitchell)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: two minor points
Date: 13 Aug 92 15:13:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 13 Aug 1992 10:13 -0500 (CDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNIYIOC1K294E51Z@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Original_To: BITNET%"ipmdf@ymir"

I did something boneheaded to my mail account yesterday, and missed Ned's
first response to my remark about the multipart nondelivery notices.  From
the ensuing discussion I gather it was somewhat heated.  I think that most
of us who post suggestions here consider the following points to be implicit
in what we write, but perhaps I should have been explicit:

    1.  It's well known that an apparently trivial modification may
        in fact be very difficult to implement (and sometimes vice
        versa).  Clearly, an option to control the notice format falls
        into this class, and having found that out I wouldn't dream
        of pressing the issue any further.

    2.  I don't know anyone familiar with Innosoft who considers them
        anything less than a model for all other software concerns.
        By pointing out a fly in the ointment--a microbe, really--I
        didn't mean to express a lack of enthusiasm for the MIME
        implementation, with which Innosoft is doing almost singlehandedly
        what the entire X.400 community has been struggling to pull
        off for eight years.

So please add these as footnotes to my original comment, which still seems
perfectly reasonable to me.  Now, can someone send me a copy of that
message?  I hate to miss an instance of Ned's writing, even if it means
getting a whole can of whup-ass poured on me.

Scott Mitchell
University of Texas Health Science Center at San Antonio
mitchell@uthscsa.edu
mitchell@uthscsa.bitnet
From: kvc@summer.innosoft.com (Kevin V. Carosso)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Mail User agents
Date: 13 Aug 92 06:13:13 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Aug 1992 22:13:13 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNID78MJWI94E362@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KNAPKE%BUTLERU.BITNET@ymir.claremont.edu"
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> We finally making efforts (and aparently have money too, wow) to have a
> complete mail solution.  We have both Macs and IBM compatibles on people's
> desk, very few VTs.  We would like a mail system that generally stores mail
> on a host, getting people to backup is not fun around here.
>
> I have looked at a couple of packages, but have not found the product that
> fits the mold here just yet.  Believe it or not, talking with Digital,
> MailWorks (A1 mail) seems to be most intersting to us.

I think A1MAIL is probably your best bet here.  All of the traditional PC based
solutions are not going to use the VAX as a mail server.  They can use the VAX
as a gateway (e.g. something like PMDF's cc:Mail channel) but you're going to
have to set up and run PC based post offices, as well as dedicated PC's for
gateways.  PMDF can help somewhat in tying them together, but you will be managing
PC servers, PC post-offices, and PC gateways, requiring multiple single-tasking
dedicated DOS machines.  Just an ugly solution.  All of this can be handled easily
by a VMS system with A1MAIL.  I'm sure that A1MAIL with PMDF-MR and other MR
gateways can provide connectivity (all on one single platform) to anything you
might need to talk to.

>                                                       A couple of questions
> that the Rep couldn't answer though, what transports/protocals can you run
> with the MailWorks client (both environments)??

Not sure of your question.  If you means where can you send mail, then
through Message Router you can get to:

    any PMDF    using PMDF-MR (SMTP/BITnet/VMS MAIL/PMDF-FAX/etc...)
    X.400       using MRX
    VMS MAIL    using PMDF-MR (or MRGATE -- better with PMDF-MR)
    SNADS       using MR/S
    PROFS       using MR/P

If you mean what is the transport between PC/Mac and A1MAIL server then the
answer is DECnet.  They may also support TCP/IP, but I'm not sure.

	/Kevin Carosso
	 Innosoft
From: tom.adriaansen@uci.kun.nl (Th.W.A. Adriaansen, System Manager)
Newsgroups: vmsnet.mail.pmdf
Subject: OPENVMS 1.0 and PMDF 4.x
Date: 19 Aug 92 10:18:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Aug 1992 11:18 +0100 (MET)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNQZO32YMA95NM2C@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.bitnet"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Comments: EARN/BITnet: ADRIAANS@HNYKUN52, DECnet: KUNRC1::ADRIAANS

Hi,

We are thinking of migrating our VAX 6210 to a VAX 6510 or VAX 4400 (new type),
and DEC told me that the VAX 4400 has to run OPENVMS V1.0.

Now I'm curious if PMDF V4.x runs under OPENVMS V1.0.
Is there anyone out there who has any experience with this?
Is there anyone out there who already runs OPENVMS V1.0 with PMDF V4.x?

M.vr.Gr.
Tommy,

 ...................
 .            _+_  .  Tom Adriaansen : System Manager / Postmaster (.KUN).NL
 .           (***) .  Address        : University Computer Centre (KUN/UCI)
 ............/===\..                 : Geert Groote Plein Zuid 41
 . KKKKKUUUUUNNNNN .                 : 6525 GA Nijmegen, The Netherlands
 . KKK  UUUUU NNNN .  Phone          : +31-(80)-617958  (bgg 617957/617959)
 . K    UUUUU  NNN .  FAX            : +31-(80)-617979
 . KKK  UUUUU   NN .  E-MAIL         : Internet : Tom.Adriaansen@UCI.KUN.NL
 . KKKKK UUU     N .                 : X400     : G=Tom; S=Adriaansen; OU=UCI;
 ...................                 :          : O=KUN; P=SURF; A=400NET; C=NL
From: 8004slb@vms.csd.mu.edu (Sandy Berger)
Newsgroups: vmsnet.mail.pmdf
Subject: Problems with QM RETURN command
Date: 18 Aug 92 05:13:28 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Aug 1992 00:13:28 -0500 (CDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNPCT4JE3M95NHAF@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
X-Vms-Cc: 8004SLB
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I'm having problems getting the QM RETURN command to work.  It keeps telling me
that the files I see in the various channel queues via the DIR command do not
exist.  I changed the line in QM.COM that is 2 lines after the CMD_RETURN label
from

	$ fext = heldext
to
	$ fext = outext

and this seems to fix the problem.  Is this a correct fix or am I missing
something here?  I'm running PMDF V4.1-6.

		--Sandy Berger
		  Marquette University


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

MM      MM   UU      UU     Sanford L. Berger            Software Specialist
MMM    MMM   UU      UU     Marquette University         Technical Services
MMMM  MMMM   UU      UU     Computer Services Division
MM MMMM MM   UU      UU     517 N. 14th Street
MM      MM   UU      UU     Milwaukee, WI  53233
MM      MM    UUU  UUU      Phone: (414) 288-3770
MM      MM     UUUUUU       FAX:   (414) 288-3300

Marquette    University     INTERNET: 8004SLB@VMS.CSD.MU.EDU
                            BITNET:   8004SLB%VMS.CSD.MU.EDU@CUNYVM
                            CIS: 70675,1212          GEnie: SBERGER
                            America Online: BERGER   AppleLink: BERGER.SLB
From: j.lance Wilkinson, 814-865-1818
Newsgroups: vmsnet.mail.pmdf
Subject: Channel Keyword "logging" and BITNET_DOMAINS.COM
Date: 17 Aug 92 17:30:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Aug 1992 12:30 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNOM2JI54Y95NERA@YMIR.CLAREMONT.EDU>
X-Organization: Penn State University / University Libraries
X-Vms-To: IPMDF
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

A user queried what had happened recently on a MAILSERV list posting that
didn't get delivered everywhere there were subscribers.  In an effort to figure
out what had happened, I started looking at MAIL.LOG (bad idea; the file hadn't
been cycled since March...;-() and then looked at my PMDF.CNF to find out that
there wasn't any "logging" keyword on my MAILSERV channel.  Then I noticed the
file PMDF_ROOT:[TABLE]GATES.CHANS didn't have "logging" on its entries, either.

The question is would "logging" on the channels built by BITNET_DOMAINS.COM in
the GATES.CHANS file be of any benefit?  If so, could BITNET_DOMAINS.COM be
updated to incorporate them (obviously, this needs to be an optional action,
by default not done to support the thousands of users who don't use it now)?

Currently using VMS v5.5, Multinet v3.0 rev H, PMDF v4.0-25 (although v4.1
finally arrived last week...;-)

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services             AT&T:      (814) 865-1818          |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
From: ghc@vger.niddk.nih.gov (Gerson H Cohen)
Newsgroups: vmsnet.mail.pmdf
Subject: Gopher and WAIS - a report
Date: 21 Aug 92 19:06:32 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Aug 1992 15:06:32 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNUCOHN52A95NUPS@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF
X-Vms-Cc: GHC
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: V4.1-10 mailserv questions
Date: 18 Aug 92 00:38:09 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Aug 1992 17:38:09 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNP32LL9K295NGGY@YMIR.CLAREMONT.EDU>
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

> * 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 file
>  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
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Deliver and MM-32
Date: 20 Aug 92 16:12:06 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Aug 1992 09:12:06 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNSSWAA14Y95NR04@YMIR.CLAREMONT.EDU>
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

If you're talking about MM-32 as shipped by TGV as part of Multinet the
answer is yes; integrated DELIVER fully supports it. Integrated DELIVER
detects whether you're using VMS MAIL or Multinet MM and modifies the
actions it performs accordingly.

				Ned
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: cc:Mail connectivity
Date: 11 Aug 92 20:03:19 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 11 Aug 1992 13:03:19 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GNMX3IHBK295NBSF@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"skapur%SBCCMAIL.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I don't think A1MAIL with no MR or X.400 means much of anything. It might be
a replacement for plain VMS MAIL but that's about all it would be. As far as
I know it includes no transports of its own.

If this is not the case I'd be interested to know why.

				Ned