HDTenEightyP/NetNews huggingface dataset:
From: MITCHELL@UTHSCSA (Scott J. Mitchell)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: two minor points
Date: 13 Aug 92 17:11:55 GMT
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.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Original_To:  BITNET%"ipmdf@ymir"
X-To:         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
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.CLAREMONT.EDU"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 14 Aug 92 14:40:50 GMT
From:         The PMDF Postmaster <MAC@GVG34.GVG.TEK.COM>
Subject:      RE: Install bug
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

>Accounts of the form [nnn,0] have implicit privileges -- GRPPRV, I
>believe.  It is a very bad idea for the PMDF account to have such
>access; it is certainly not needed and it can lead to trouble. We
>therefore don't allow the use of an account of this sort as the PMDF
>account.

Well, okay, but this is the first installation since we started using
PMDF that complained about a zero member.  I believe our first PMDF
installation was version 2.4.  I would have liked a bit more complete
error message during the installation since this was changed behavior,
but as with all complaints/suggestions about PMDF this is a nit.

Bill MacAllister
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"Tom.Adriaansen@UCI.KUN.NL"
X-VMS-Cc: IN%"ipmdf@ymir.claremont.edu",PETER
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 19 Aug 92 14:10:53 GMT+0200
From:         PETER@EMBL-HAMBURG.DE
Subject:      RE: OPENVMS 1.0 and PMDF 4.x
X-To:         Tom.Adriaansen@UCI.KUN.NL
X-cc:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

  > We are thinking of migrating our VAX 6210 to a VAX 6510 or VAX 4400 (new typ
   e),
  > 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.

Theres a discussion running in VAXnotes (in german{!}) on our local DECUS Vax
where a Deccie has just said that:

"... there is no difference between VMS (XX-001-zzz) and  Open VMS (XX-005-zzz)
except in the unbundling of licences for some of the normally included layered
products.

"Further, "at the present time", the H-Kits are the same - the System
looks for both PAKs"

I'd say that they are the same, and the answer ought to be yes!
(within the limitation of my ability to read foreign!)

regards
Peter Bendall
European Molecular Biology Laboratory,
Hamburg Outstation.

 Date:
 From:     Peter Bendall        : WIN-Mail          PSI%(0262)45050150057::PETER
 Dept:     Computer Group       :
 Tel:      +49  40 - 899 02 133 : Internet          Peter@EMBL-Hamburg.de
 FAX:      +49  40 - 899 02 149 : EAN-Mail          Peter@Hamburg.embl.dbp.de
                                :         (S=Peter;OU=Hamburg;P=embl;A=dbp;C=de)
----.------------------------------------------------------------------.----.
|    |   Note EMBLs changed internal and external telephone numbers.    |    |
|    |      Telephone connection from DESYnet will now be 19-133        |    |
`----`------------------------------------------------------------------'----'

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"
X-VMS-Cc: 8004SLB
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 06:42:23 GMT
From:         Sandy Berger <8004SLB@VMS.CSD.MU.EDU>
Subject:      Problems with QM RETURN command
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

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
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.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 19:30:25 GMT
From:         Robin Goldstone <robin_goldstone@MACGATE.CSUCHICO.EDU>
Subject:      mailing list automation
X-To:         ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

Our campus currently has a mailing list set up that any user can send to, which
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 the
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?

Any suggestions are appreciated.
Robin Goldstone, CSU Chico
robin@csuchico.edu
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:         Thu, 20 Aug 92 22:24:04 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 <01GNORGF042Q94E6PA@INNOSOFT.COM>, dan@innosoft.com (Daniel C.
 Newman) writes:
>>> 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...
>
> Sure, that will work provided you don't mind rendering illegal all formerly
> legal printer channel addresses.  The legal address
>
>    "/at=Dan Newman/ms=broom closet/"@hardcopy.uvcc.edu
>
> will be rewritten to the illegal address
>
>    /AT="/at=Dan Newman/ms=broom closet/"@HARDCOPY.UVCC.EDU

Hmmmm. Good point.
     How about:
     HARDCOPY.UVCC.EDU        /AT=$U@PRINTER.UVCC.EDU
     PRINTER.UVCC.EDU             $U@PRINTER.UVCC.EDU

That way you can do it both ways, correct?

--
-- Vern Cole -- Systems Manager -- Utah Valley Community College --
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"KLENSIN@INFOODS.MIT.EDU"  "John C Klensin"
X-VMS-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-Mts: smtp
Date:         Mon, 17 Aug 92 08:23:18 +1000
From:         andrewr@ITD.ADELAIDE.EDU.AU
Subject:      RE: Mail User agents
X-To:         John C Klensin <KLENSIN@INFOODS.MIT.EDU>
X-cc:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l
              <713977262.781166.KLENSIN@INFOODS.MIT.EDU>

In message <713977262.781166.KLENSIN@INFOODS.MIT.EDU> you write:

+ >>    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

+ >That's why "store and forward" methods like POP have been very popular for
+ >PCs and MACs of late.  There some very nice looking POP client programs
+ >available to overcome the issue of not having your personal computer
+ >turned on all the time.

+ Jack,
+   While not disagreeing with anything you've said, I think a
+ terminology clarification would be helpful before this discussion goes
+ down the path of a parallel discussion about these mail-receiving
+ protocols...
+   Strictly speaking, one could easily construct "store and forward", and
+ a solution to the shut-off workstation problem with SMTP alone.  You
+ would set up MX records for the workstations that would deposit the mail
+ somewhere else if the workstation was off, e.g.,
+      workstation MX 0  workstation
+      workstation MX 10 postoffice

        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
are about to start using PMDF to interface with it.

        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 !
 */
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: IN%"Ipmdf@YMIR.BITNET"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 13 Aug 92 22:05:10 GMT
From:         "David J. Knapke 317/283-9420" <KNAPKE@BUTLERU>
Subject:      RE: Mail User agents
X-To:         MAC@gvg34.gvg.tek.com
X-cc:         Ipmdf@YMIR
Newsgroups: bit.listserv.pmdf-l


>The guy working on ccMail here downloaded the following document from the
>ccMail BBS yesterday.

>Bill MacAllister

>================================================
>DEC updates E-Mail, Provides cc:Mail Integration
>================================================

>BOSTON, MASSACHUSETTS, U.S.A., 1992 JUN 10 -- Digital Equipment has
>announced a new release of its local area network electronic mail
>integration product, MailWorks Postmaster, that ties DEC's mail systems
>in
>with Lotus Development's PC-based cc:Mail.

....rest deleted.....

As I understand if from our local Dec Reps, there are now two MailWorks
products (thank you DEC).  One is a new product that is competing head
to head with folks like cc:Mail and MicroSoft mail, the other is what we
had been calling All-in-1 mail (not All-in-1 Integrated Office System).
There supposedly is no tools know (yet of course) that integrate MailWorks
(PC based mail system) with MailWorks (the A-1 mail system).

Is thes congruent with what others have heard??  I'm confused and I spent
most of yesterday with people who are supposed to know, so...WHY ARE YOU
DOING THIS DEC????



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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: MCC, MIS/Telecomm
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
Mail-System-Version: <VAX-MM(284)+TOPSLIB(151)+PONY(256)@Maximillion.mcc.com>
X-Phone: (512) 338-3316
X-FAX: (512) 338-3888
Date:         Thu, 20 Aug 92 16:50:15 GMT
From:         Bob Paver <PAVER@MAXIMILLION.MCC.COM>
Subject:      Deliver and MM-32
X-To:         info-pmdf@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.

Thanks,

Bob
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Bob Paver  ---->  paver@mcc.com  OR  cs.utexas.edu!milano!paver

Microelectronics and Computer Technology Corp (MCC)
3500 West Balcones Center Drive
Austin, Texas 78759-6509             (512) 338-3316
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SROSS@CGNET.COM"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 17 Aug 92 10:05:35 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: listserv WELCOME message
X-To:         SROSS@CGNET.COM, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

It's a bug.  The welcome message code was added at the last minute to
satisfy a particular application; it was not tested very well as a result
of this. This problem will be rectified in a subsequent release of PMDF.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-VMS-Cc: IPMDF,GHC
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 18 Aug 92 18:45:50 GMT
From:         Gerson H Cohen <GHC@VGER.NIDDK.NIH.GOV>
Subject:      RE: Changing To: header on alias list
X-To:         cvm@NAUVAX.UCC.NAU.EDU
X-cc:         IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

> 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

I don't know if it is corect that "BULLETIN requires the message be
addressed to the user or it will not extract it from the mail file" but
I use the simpler mechanism of a bulletin channel to feed mail for a
pseudo user on our vax directly into a bulletin folder via the pmdf
alias file.  Details on request [but documented in the Bulletin files].

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
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, 16 Aug 92 16:41:41 +1000
Comments:     Warning -- original Sender: tag was
              CHRIS@UCSVC.UCS.UNIMELB.EDU.AU
From:         C.Chaundy@ITS.UNIMELB.EDU.AU
Subject:      Problem with printer channel?
X-To:         info-pmdf@YMIR
Newsgroups: bit.listserv.pmdf-l

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*.  But what
was worse was instead of generating a bounce message to the postmaster and
the originator, it generated a message to the postmaster and the recipient!
Of course, the recipient address was illegal (no AVPL) so a groovy little
mail loop started up :-).

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.

Chris Chaundy (Technical Manager, Networks)

Information Technology Services, Thomas Cherry Building,
The University of Melbourne, Parkville, Victoria 3052 Australia
Phone:    +61 3 344 7045                Fax:   +61 3 347 4803
Internet: C.Chaundy@its.unimelb.EDU.AU  (X.121 505233430003)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Mon, 17 Aug 92 10:19:50 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: cc:Mail connectivity
X-To:         skapur@SBCCMAIL, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: SUNY at Buffalo, Systems group
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, 13 Aug 92 20:29:00 GMT
Comments:     Warning -- original Sender: tag was NETNEWS@AMERICAN.EDU
From:         tkslen@UBVMS.CC.BUFFALO.EDU
Subject:      vms v5.5-1 and pmdf v4.1-1 problems.
X-To:         ipmdf-newsgate@mccall.UUCP
Newsgroups: bit.listserv.pmdf-l


I am upgrading to vms v5.5-1 and pmdf v4.1-1 this monday.  Does anyone know of
any problems/gotchas with the combination of these two?

Thanks,
  Lenny Miceli
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ned@innosoft.com"
X-VMS-Cc: IN%"info-pmdf@innosoft.com" KNOVAK
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 13 Aug 92 03:20:44 GMT
From:         SROSS@CGNET.COM
Subject:      listserv authorization / open and closed lists
X-To:         ned@INNOSOFT.COM
X-cc:         info-pmdf@INNOSOFT.COM
Newsgroups: bit.listserv.pmdf-l

Ned,
        I am interested in creating a "closed" listserver, meaning that
only designated people are allowed to SUBCRIBE/UNSUBSCRIBE others from
the list.  Does the code in PMDF4.1-10 allow this type of operation?
I'm hoping that the "authorization" functions you've talked about will
allow this.

Forgive me if I missed the posting of the details of the authorization
process, but if the complete documentation is not yet available, I
would very much appreciate a summary of how I could set up the scenario
mentioned above.

Thanks,
Steve Ross, CGNET Services International
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:         Fri, 21 Aug 92 18:04:17 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: PMDF-FAX installation and [ghostscript]fontmap.
X-To:         bob@camb.com, IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l

in V4.2 we'll make the installation dio what we do with things like master.com:
rename the previous master.com to master.old.

Dabn
From: DAN@INNOSOFT.COM (Daniel C. Newman)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: FTP site for PMDF patches?
Date: 12 Aug 92 18:21:49 GMT
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"Don.Rainwater@UC.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
X-To:         Don.Rainwater@UC.EDU, IPMDF@YMIR

> I thought I saw a posting a couple of weeks ago that said there would be an
> FTP site coming up soon for PMDF 4.1 patches.  Was I imagining things?

Yes, there was such a posting -- I made it.  We have not yet set up this new
archive.

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