HDTenEightyP/NetNews huggingface dataset:
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Trent University, Peterborough
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:         Thu, 24 Dec 92 23:27:07 GMT
Comments:     Warning -- original Sender: tag was news@TRENTU.CA
From:         gmacdougall@TRENTU.CA
Subject:      MAILSERV
Newsgroups: bit.listserv.pmdf-l



        I just set up a mailing-list and have been interested in the recent
thread on MAILSERV and command access. The recent info on the mapping file
seemed helpful until I tried to implement it. I'm running PMDF 4.1 on VMS 5.4
with dead simple non-compiled pmdf.cnf file (Single off campus Multinet
Channel). Can somebody please point me at the correct documentation, section
3.4.1 Locating and Loading the mapping file - says "This file is read once
during program initialization and loaded into an internal string table."
Unfortunately this doesn't make sense to me. I have created a mappings file
which is pointed to by pmdf_mappings_file but the contents do not seem to
affect the behaviour of my mailserv.
        I do have the mailserv working as far as subscribe, unsubscribe and
use of the mailing list goes but I am trying to get send/list and subscribe
for a third party working for sysop types.

        thanks inadvance,

                                                        George MacDougall
                                                        gmacdougall@trentu.ca

        Computing and Telecommunications Department - (705) 748-1602
        Trent University - Peterborough, Ontario - K9J 6S2
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir"
X-VMS-Cc: AE
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 28 Dec 92 14:43:53 -0400
From:         Aidan Evans <AE@AC.DAL.CA>
Subject:      Spontaneous change to MM mail delivery
Newsgroups: bit.listserv.pmdf-l

  All of a sudden, at 5:48:22 a.m. (-0400) on Dec. 26, my mail began to be
delivered using MultiNet MM instead of VMS mail.  I assume this is when it
happened because that is the creation date on the files $HDRS$MAIL.TXT and
MAIL.TXT in my SYS$LOGIN directory which I understand are the MM mail files.
The last mail message that was delivered via VMS mail was just nine seconds
earlier, at 5:48:13.  Both the :13 and the :22 messages were from the PMDF
message bouncer job (it doesn't run here until 3:30 a.m., and it had a lot of
messages to process).
  So far as I know I did nothing explicit to cause this change.  I'm pretty
sure I was home asleep at the time.  I'd like to know what happened and how I
can prevent it from happening again.

Aidan Evans (AE@AC.Dal.CA), Computer Facilities & Operations,
University Computing & Information Services, Dalhousie University,
Halifax, N.S., Canada, B3H 4H8
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"HARRIS@si-bas.si.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 25 Dec 92 00:11:59 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Talking about MCI, how about a SprintMail PMDF interface?
Newsgroups: bit.listserv.pmdf-l

We'd have to know more about the protocols Sprint uses before we'd be
able to make an intelligent reply to this. At least one other site is
already pursuing the available protocol question. I suggest that you find
out from Sprint what standard (or nonstandard) protocols they support for
accessing their service.

As for using one mailbox to serve multiple local users, the concept of an
MTA-level mailbox is hardly new. PMDF has them (they're called channels),
Message Router has them (they're called mailboxes), and I'm quite sure
that the concept was understood even when these products were developed.
(PMDF in particular traces its use of channels back to MMDF.)

Multi-use mailboxes at the UA level are rarer but by no means unheard of.
Again, PMDF has them (username+use-specific-string@localhost), they'd
be easy to do if anyone wanted to in Message Router, and so on. And again,
the concept is not original; PMDF's facilities for this are copied from
similiar facilities in the Andrew Messaging System. I have no idea where they
got the idea from...

                                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:         Sun, 27 Dec 92 02:46:42 GMT
From:         Jeremy Begg <JEREMY@VSM.COM.AU>
Subject:      Empty reply address from All-In-One/PMDF-MR
Newsgroups: bit.listserv.pmdf-l

Hello there, I was wondering if anyone had seen this before.

I sent a mail message to a friend of mine at another site where they use
All-In-One (the office system), and requested a delivery-receipt.  A little
while later I received the following acknowlegement:

>Return-path: <>
>Received: from HERMES.UCS.ADELAIDE.EDU.AU by vsm.com.au (PMDF #2424 ) id
> <01GSI3AKMNQ80001XL@vsm.com.au>; Sat, 19 Dec 1992 13:52:15 CST
>Received: from state.systems.site by hermes.ucs.adelaide.edu.au (PMDF
> #3414 ) id <01GSI39SZTE80008EB@hermes.ucs.adelaide.edu.au>; Sat,
> 19 Dec 1992 13:51:35 CST
>Received: from mr.ss.site by state.site (PMDF #12099) id
> <01GSI3B80GIC0010YH@state.site>; Sat, 19 Dec 1992 13:52 +0000
>Received: with PMDF-MR; Sat, 19 Dec 1992 13:41 +0000
>Date: 19 Dec 1992 13:52 +0000
>Date-warning: Date header was inserted by mr.ss.site
>From: <>
>Subject: Service Message
>To: JEREMY@vsm.com.au
>Message-id: <01GSI3B80GIC0010YH@state.site>
>X-Envelope-to: JEREMY
>Content-transfer-encoding: 7BIT
>
>Content-type: REPORT
>
>Report on your message to: /R=A1/U=the user/@mr.ss.site
>Arrival-date: Sat, 19 Dec 1992 13:30 +0000
>Delivery-date: Sat, 19 Dec 1992 13:41 +0000

(I have replaced the site name by the word "site" in all addresses above, and
the person's A1 username by "the user".)

I would have expected the reply address for this message to be some sort of
postmaster address for the site, is this configurable in All-In-One or PMDF-PR?

Thanks,

        Jeremy Begg

  +----------------------------------------------------------+
  | VSM Software Services,  |  E-Mail:  jeremy@vsm.com.au    |
  | P.O.Box 801, Unley,     |   Phone:  +61 8 4145074 (pager)|
  | South Australia 5061    |     FAX:  +61 8 3734911        |
  +----------------------------------------------------------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"xu@neuro.psycha.upenn.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 2 Jan 93 21:33:31 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: A Simple Question
Newsgroups: bit.listserv.pmdf-l

As far as we know PMDF V4.0 works fine with VMS 5.5 and UCX 2.0. PMDF V4.1
is the current supported version, however; if you encounter any problems
with V4.0 you will have to upgrade to V4.1 to resolve them. V4.1 has been
available for over 6 months now.

UCX 2.0 comes with its own SMTP server. This has to be disabled so that
PMDF's SMTP server can run properly. You don't want to use the UCX SMTP
server in any case since it does not integrate properly with the rest of
PMDF. Once it is disabled everything should be fine; PMDF's server works
correctly with UCX V2.0.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"emv@msen.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 2 Jan 93 06:14:28 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: MIME support for fax
Newsgroups: bit.listserv.pmdf-l

I'm not sure whether or not PMDF-FAX meets your requirements for "faxes
through e-mail"; perhaps I'd best just say what it is that PMDF-FAX does
do.

PMDF-FAX is a set of channel programs for PMDF that provide facilities for
converting text, PostScript, and various other formats into Group 3 FAX,
as well as a set of programs that take these Group 3 FAX files and use
them to drive a variety of FAX modems. Facilities for receiving FAXes from
the modems that are capable of FAX receive and conversion of these materials
into various formats (PostScript, TIFF, GIF, PCL, etc.) are also provided.
Received FAXes can be printed, delivered to files, or automatically forwarded
on as mail messages.

None of this really involves "faxes through e-mail", however. PMDF-FAX can
and has been used to convert mail messages into FAX images which were then
sent via e-mail to another sort of FAX gateway, but usage of this sort is
quite rare. Most people want a way to convert mail messages into real
FAXes and vice versa, and that's what PMDF-FAX is aimed at.

MIME is used throughout to provide type information, multipart facilities,
and so forth. PMDF-FAX was developed with MIME in mind from the outset.
Tricky stuff like automatic defragmentation of message/partial objects is
supported and works quite well (this is actually a feature of PMDF rather
than being specific to PMDF-FAX). And of course the MIME transfer encodings
provide an effective means of dealing with binary message bodyparts.

All of this functionality has been available for some time in the form of
a commercial product -- we released a fully MIME compliant version of
PMDF and PMDF-FAX right at the time MIME appeared as a proposed standard.
Of course development is ongoing: a new version of PMDF and PMDF-FAX is
currently in field test, and it displays the usual feature-creep you'd
expect (support for more formats, better conversion facilities, improved
PostScript fonts, support for more modems, etc. etc. etc.).

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 31 Dec 92 01:36:07 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      mailserv `unauthorized' rejection msgs
Newsgroups: bit.listserv.pmdf-l

I have set up a number of mailserv managed mailing lists and on some am
trying to restrict the list of people allowed to issue the `subscribe'
command.  I am unsure about one point.  Which address does PMDF use
when checking against the file I specify?  Is it the From:-header,
Sender:-header, envelope-from, ... ?  The rejection message says only
        You are not authorized...
It would be helpful if it included the actual address it was trying to
match, as in
        You (bob@camb.com) are not authorized...

Needless to say, this question was prompted by a problem I have where
I thought I'd set things up correctly, but only some of the people I
wanted to authorize are able to issue the subscribe command.  The others
get the `not authorized' msg.

Thanks - Bob Tinkelman <bob@camb.com>
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"bob@camb.com"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 21 Dec 92 21:03:24 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Hung vn_xxxx jobs
Newsgroups: bit.listserv.pmdf-l

PMDF wakes UUCP by writing to a mailbox. If the mailbox is full PMDF will
indeed hang at this point. This is expected bahavior. You should be able to
clear the condition by restarting UUCP from ground zero and killing all the
PMDF jobs that are hung.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 2 Jan 93 06:25:03 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      RE: mailserv `unauthorized' rejection msgs
Newsgroups: bit.listserv.pmdf-l

> The proper choices of addresses for authorization checking are all
> described in RFC822. Specifically, the Sender: address is used if
> present, and failing that the From: address is used.

I figured out my error.  I was trying to be fancy and
  (1) have the mailserv_access mapping refer to a mailing list, and
  (2) use subaddresses in the mailing list.

It seems that if the authorization file contains bob+other-stuff@camb.com
then bob@camb.com doesn't match and isn't considered authorized.  I guess
this is expected behavior.

Is there a reasonable way for me to use subadresses in a mailing list and
still use that list as the basis of authorization tests?  (My first
thought was to run a daily batch job that converts the mailing list into
an authorization list, stripping the subaddressing, but I really don't
want to get into parsing rfc822 addresses.)
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"
X-VMS-Cc: IORI
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 23 Dec 92 11:22:23 +0000
From:         "Remo Iori - C.I.S.C.A. - Trento" <IORI@ITNCISCA.BITNET>
Subject:      mail.delivery question
Newsgroups: bit.listserv.pmdf-l


Hi,
We are setting up a 'special distribution list' (only 8 users, so far) on
our Vax; a special account (eg: DISTRIBUTOR) has got a mail.delivery file
as the following:

!from to subj | when action  param.     ! note
!=======================================================
*     *   *     A    J       "FAST"     ! submit this proc. on queue FAST
*     *   *     A    V                  ! deliver a copy of the message
*     *   *     A    L                  ! save the batch log
*     *   *undeliver*  T   Q            ! don't forward to the list if this
                                        ! message is a warning of problems
                                        ! occurred during delivery
*     *   *     A    F ""in%""""userA@vax.domain.it"""""   ! send to userA
*     *   *     A    F ""in%""""userB@vm.domain.de"""""    ! send to userB
etc.

Each user, from different sites in Europe, send message to the DISTRIBUTOR
and then the message is forwarded to the rest of the list; any suggestion
to admit only the registered users having access to this service ? (We
would like to filter 'occasionaly' message received by DISTRIBUTOR, e.g.
advertisement, greetings ecc.)

Thanks in advance
Remo Iori
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"mats@rigel.efd.lth.se"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 2 Jan 93 06:06:33 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: AT&T
Newsgroups: bit.listserv.pmdf-l

There is a huge bug in ATTMail that causes it to reject MIME messages.
ATT is aware of the problem but (obviously) has not fixed it yet.

The only workaround I know of for this in PMDF is to configure a special
channel for connecting to attmail.com that uses a header option file
to strip the relevant MIME header (Content-type:).

I don't know who to contact at ATT to complain about this -- doubtless someone
else on this list will know the specifics. Any additional information about
this problem that has come up since the last time it was discussed on this
list would also be appreciated.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%INFO-PMDF
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 2 Jan 93 06:40:05 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      RE: mailserv `unauthorized' rejection msgs
Newsgroups: bit.listserv.pmdf-l

> You'll have to strip the subaddresses from the actual authorization list
> entries or arrange it so users use the proper subaddress when submitting
> to the list.

What do you think of offering an option to allow
        Sender: bob@camb.com
to match an authorization list entry of the form
        bob+subaddress@camb.com

If such an option were available, I think I'd use it.  Does it imply
some sort of hole in the security of authorizations?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Lund Institute of Technology,Lund, Sweden
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:         Thu, 31 Dec 92 01:36:18 GMT
Comments:     Warning -- original Sender: tag was news@LTH.SE
From:         mats akerberg <mats@RIGEL.EFD.LTH.SE>
Subject:      AT&T
Newsgroups: bit.listserv.pmdf-l

Hi!

I have a problem when I'm sending mail to a friend
that have a X.400 adress.

What I get is this:

Not-Delivered-To: mhs!fws/S=zirbess/O=fws due to 13 Conversion Not Performed
 unable to transfer

But when I send from my DECstation It work's OK!

I guess the error is with AT&T (I send to @mhs.attmail.com)!

Is there a workaround or?????
Where do I bash on AT&T?

                  /Mats

____
  Mats Akerberg, System Manager (mats@rigel.efd.lth.se)
  Lund Institute of Technology ,School of Electrical Engineering and
  Computer Sciences. Snail: Box 118  S-221 00 Lund Sweden
  Phone: + 46 46-109847 FAX: + 46 46-104013
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"gmacdougall@TrentU.CA"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 24 Dec 92 23:57:07 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: MAILSERV
Newsgroups: bit.listserv.pmdf-l

>       I just set up a mailing-list and have been interested in the recent
> thread on MAILSERV and command access. The recent info on the mapping file
> seemed helpful until I tried to implement it. I'm running PMDF 4.1 on VMS 5.4
> with dead simple non-compiled pmdf.cnf file (Single off campus Multinet
> Channel). Can somebody please point me at the correct documentation, section
> 3.4.1 Locating and Loading the mapping file - says "This file is read once
> during program initialization and loaded into an internal string table."
> Unfortunately this doesn't make sense to me. I have created a mappings file
> which is pointed to by pmdf_mappings_file but the contents do not seem to
> affect the behaviour of my mailserv.

I don't know how to make the sentence,

   This file is read once during program initialization and loaded...

any clearer without expending four or five sentences.  Only possible rewording
I can imagine is to say "image activation" in place of "program
initialization".  All that is being stated here is that the mapping file is
loaded when a program begins running.

>       I do have the mailserv working as far as subscribe, unsubscribe and
> use of the mailing list goes but I am trying to get send/list and subscribe
> for a third party working for sysop types.

What are the errors you're getting?  You've doubled check to insure that you
do not have a compiled configuration (issuing the command "$ DIRECTORY
PMDF_CONFIG_DATA reveals no files)?  Also, did you make sure that the mapping
file is world readable?  You can test the mappings with PMDF TEST/MAPPING

   $ pmdf test/mapping
   Enter mapping name: MAILSERV_ACCESS
   Input string: SENDLIST|dan|ned@sigurd.innosoft.com
   Output string:
   Output flags: [0,89]
   Input string:

The output flags indicate the ASCII index of any metacharacters (e.g.,
$Y = 89).

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: in%"info-pmdf@innosoft.com"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 25 Dec 92 02:47:15 GMT
Comments:     Warning -- original Sender: tag was TINKELMAN@EISNER.DECUS.ORG
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      PMDF NOTES channel and NOTES's send/author
Newsgroups: bit.listserv.pmdf-l

I just set up a NOTES conference fed by a PMDF NOTES channel.  Attached is an
example of a note posted to that channel.  Everything seems to be working as
advertised.  [Thanks.  It's nice when that happens.]

I have what's probably an enhancement request, though if it turns out I can do
what I want with PMDF 4.1 that'd be wonderful.

NOTES has the ability to send mail to a note's author using SEND/AUTHOR or
FORWARD/AUTHOR.  The way that the NOTES are posted the author is SYSTEM.  What
I'd like is some way to make mail sent to ``/AUTHOR'' get sent to the person
who sent the original mail.

Would NOTES allow you to set the author field to the IN% construct that's
currently placed in the personal name field?  If so, I'd really like a way to
tell PMDF to do that.  If not, is there some other mechanism that could be
provided to support this funcationality?

Thanks - Bob Tinkelman <bob@camb.com>



            <<< EISNER::DUA3:[NOTES$READONLY]INFO-MULTINET.NOTE;1 >>>
                               -< info-multinet >-
================================================================================
Note 42.0       Diskkeeping products and NFS export of VMS disks.        1 reply
EISNER::SYSTEM "IN%"sonneveld@research.ptt.nl""      29 lines  24-DEC-1992 16:53
--------------------------------------------------------------------------------
Received: from TGV.COM (HQ.TGV.COM) by Eisner.DECUS.Org (PMDF #2354 ) id
 <01GSF2NUZ1J4000PBH@Eisner.DECUS.Org>; Thu, 17 Dec 1992 10:01:36 -0500 (EST)
Received: from MVB.SAIC.COM ([139.121.19.1]) by TGV.COM via INTERNET ; Thu,
 17 Dec 92 06:46:06 PST
Date: 17 Dec 1992 09:49:45 +0000 (GMT)
From: sonneveld@research.ptt.nl (Rolf E. Sonneveld)
Subject: Diskkeeping products and NFS export of VMS disks.
To: INFO-MULTINET@TGV.COM
Message-id: <1992Dec17.114945.1@research.ptt.nl>
Organization: PTT Research, The Netherlands
Content-transfer-encoding: 7BIT
X-Newsgroups: vmsnet.networks.tcp-ip.multinet
X-Gateway-Source-Info: USENET

        Hello, all

        Can the use of diskkeeping and -caching products like
        PerfectDisk and I/O-Express on disks that are (partially)
        exported by Multinet NFS potentially result in corrupted
        files and data?

        Thanks,

        Rolf E. Sonneveld
        PTT Research
        The Netherlands
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: NYU Medical Center, 550 First Ave., New York, 10016
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: in%"ipmdf@ymir.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 3 Jan 93 14:08:31 GMT
From:         SMITH@NYUMED.BITNET
Subject:      POP server and All-in-1 Mail...
Newsgroups: bit.listserv.pmdf-l

A while back we switched from VMS mail to All-in-1 mail with PMDF-MR, etc. We
like the X-windows interface and the multi-part capability.

However, it would be good to be able to use Eudora from home to get mail over
the weekend.  When we still ran VMS mail this was not a problem since the
Multinet POP server linked to the VMS-mail for each user.

Will the PMDF POP product allow you to get mail from an All-in-1 mail account?
If not, is there a solution possible? probable? desirable?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU