HDTenEightyP/NetNews huggingface dataset:
From: Hunter Goatley <goathunter@WKUVX1.BITNET>
Newsgroups: vmsnet.mail.mx
Subject: RE: bitnet node  & decnet network
Date: Wed, 07 Oct 1992 07:31:36 EDT
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

mbieniec@PLUNLO51.BITNET writes:
>
>My problem is:
>One vax with Jnet and MX (this one is bitnet node) and several vaxes
>in DecNet (some connected to Ethernet cable others by leased telepnone
>lines). I assume that each user of any computer has his own
>mail address  on his own local computer.
>What is the proper way of using mail in such configuration?

I've got the same setup.

>1. What parts of MX should be installed on the bitnet node and what
>parts on th others?

The BITNET node should run MX_JNET, MX_ROUTER, MX_LOCAL, and
MX_DNSTMP.

>2. How to configure MX for both types of nodes ( path,rewrite
>rules, and mx_logicals.dat file )

Just run MX_CONFIG.COM on both types of nodes.  That'll do most of the
work for you.  On the Jnet side, I have the following rewrite rule and
path for my VAXstation:

  Rewrite "<{user}@HUNTER>" => "<{user}@HUNTER.DNET>"
  Rewrite "<{user}@HUNTER.DNET>" => "<{user}@HUNTER.DNET>"

Domain-to-path mappings:
  Domain="WKUVX1", Path=Local
  Domain="WKUVX1.BITNET", Path=Local
  Domain="HUNTER.DNET", Path=DECnet_SMTP, Route="HUNTER"
  Domain="*.BITNET", Path=Jnet
  Domain="*.*", Path=Jnet, Route="UKCC"
  Domain="*", Path=Jnet

Note that UKCC.BITNET is my Internet gateway---I don't use INTERBIT
for anything.

On my VAXstation, the entire CONFIG.MCP file looks like this:

>! MX_DEVICE:[MX]CONFIG.MCP;1
>! Created: 11-JUL-1992 19:42:02.66 by MXCONFIG
>!
>DEFINE PATH "HUNTER.DNET" LOCAL
>DEFINE PATH "WKUVX1.BITNET" DECNET_SMTP/ROUTE=WKUVX1
>DEFINE PATH * DECNET_SMTP/ROUTE=WKUVX1
>!
>!  If sending to myself via MX, don't send it to WKUVX1
>!
>DEFINE REWRITE_RULE "<goathunter@WKUVX1.BITNET>" "<goathunter@HUNTER.DNET>"
>!
>! Done with routing information.
>!
>DEFINE ALIAS "Postmaster" "goathunter@HUNTER.DNET"
>DEFINE ALIAS "POSTMAST" "goathunter@HUNTER.DNET" ! for BITNET compatibility
>!
>SET LOCAL/ACCOUNTING
>SET DECNET_SMTP/ACCOUNTING
>SET LOCAL/HEADERS=(TOP=(NORESENT_TO,NORESENT_DATE,NORESENT_FROM,NOMESSAGE_ID))

I chose the .DNET just to signal that it was DECnet.  There are, of
course, many other options.

>3. To use or not to use SMTP-over-DecNet ?

I did.  It's nice.  It works well, and it gives you automatic retries
in case a node goes down for some reason.

>4. Jnet may be also installed on each computer in DecNet.
>   Should I do it or not?

I don't see any point in it, unless you want the users to have things
like SEND and SEND/FILE.  Of course, then each node would have to be
connected to BITNET or clustered anyway.  Right?

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251
From: Brian Tillman, Smiths Industries, VAX Support, x8425
Newsgroups: vmsnet.mail.mx
Subject: Temporary files
Date: 13 Oct 92 14:52:34 GMT
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

In my MX_LOCAL_DIR are come files whose names are of the form
LCL_BBE89AA0_009618BC_2780009C.TMP.  They seem to contain old messages that I
received over ten days ago.

What is the purpose of these files and why might MX have left them around?

-----------------------------+--------------------------------
 Brian Tillman               | Internet: tillman@swdev.si.com
 Smiths Industries, Inc.     |           tillman_brian@si.com
 4141 Eastern Ave., MS129    | Hey, I said this stuff myself.
 Grand Rapids, MI 49518-8727 | My company has no part in it.
-----------------------------+--------------------------------
From: mcsbc3ktp@dct.ac.uk (Kirk Potter)
Newsgroups: vmsnet.mail.misc
Subject: Re: <None>
Date: 12 Oct 92 13:33:59 GMT
Organization: Dundee Institute of Technology

In article <1992Oct8.183333.530@dct.ac.uk>, mcsdc1sjt@dct.ac.uk writes:
> Stop me if I am in the wrong area,
> 
> I am trying to lock out a pest from me mailbox on the standard VMS mail system.
> Is there a command or a routine to do this?
> 
> 
> Thanks in advance. Gonzo
-- 

Use ACL's on the file MAIL.MAI and don't allow WRITE access to this user...

That should work...

#############################################################################
# Kirk P at D.I.T. (Dundee Institute of Technology, Dundee, Scotland, U.K.) #
#                                                                           #
# Janet    : mcsbc3ktp@uk.ac.dct                                            #
# Internet : mcsbc3ktp%dct.ac.uk@nsfnet-relay.ac.uk                         #
#                                                                           #
#############################################################################
Newsgroups: vmsnet.mail.misc
From: miser@milton.u.washington.edu (Robert Fulwell)
Subject: Strange address.
Reply-To: miser@u.washington.edu
Organization: University of Washington, Seattle
Date: Wed, 14 Oct 1992 20:54:44 GMT

I have no idea where to ask this question so I thought I might try here.

I recently received this address to reach my brother in Britain (Kent County
Council) and it doesn't seem to be working.

 MHS!KCC/S=TIM/O=SERVER@ATTMAIL.COM.
	       ^Is this an 'oh' or a zero?

What can I do to make this work?

Thanks a lot for you help.

Rob.
From: mcsdc1sjt@dct.ac.uk
Newsgroups: vmsnet.mail.misc
Subject: <None>
Date: 8 Oct 92 17:33:33 GMT
Organization: Dundee Institute of Technology

Stop me if I am in the wrong area,

I am trying to lock out a pest from me mailbox on the standard VMS mail system.
Is there a command or a routine to do this?


Thanks in advance. Gonzo
Newsgroups: vmsnet.mail.misc
From: hps@kaua.jach.hawaii.edu (Henry Stilmack)
Subject: Re: Strange address.
Organization: UK/Canada/Netherlands Joint Astronomy Centre
Date: Thu, 15 Oct 1992 19:30:35 GMT

In article <1992Oct14.205444.14922@u.washington.edu>, miser@milton.u.washington.edu (Robert Fulwell) writes:
|> I have no idea where to ask this question so I thought I might try here.
|> 
|> I recently received this address to reach my brother in Britain (Kent County
|> Council) and it doesn't seem to be working.
|> 
|>  MHS!KCC/S=TIM/O=SERVER@ATTMAIL.COM.
|> 	          ^Is this an 'oh' or a zero?

It's an "OH" - what you have here (looks like) an X.400 address passed through an
SMTP mailer via a UUCP connection. Yucckk! The "S" is the "SYSTEM" field, and the
"O" is the "ORGANIZATION" field of the X.400 address spec.

|> 
|> What can I do to make this work?

You don't say what OS/mailer combination you are using. The (supposed - I've
never sent to anyone on this net) general way to mail from Internet to ATTMail is
to send to   user@attmail.com. I'd try that, using whatever syntax your mailer
needs to get to attmail.

|> 
|> Thanks a lot for you help.
|> 
|> Rob.
|> 

You're welcome.
-- 
______________________________________________________________________________
Henry Stilmack                               )  
Computing Systems Manager                    )  "Haven't you heard,
UK/Netherlands/Canada Joint Astronomy Centre )   it's a battle of words -
660 N. A'ohoku Place, Hilo, HI 96720         )   and most of them are lies..."
hps@jach.Hawaii.Edu       808-969-6546       )    
------------------------------------------------------------------------------
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF-MR: cannot put NBS bodypart file - file does not contain
From: Ned Freed <ned@innosoft.com>
Date: 09 Oct 1992 01:17:14 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 09 Oct 1992 01:17:14 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPQ6B8YY8Y8WX0UH@YMIR.CLAREMONT.EDU>
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

> Our MR_LOCAL queue had stopped moving.  There was one file with a name
> starting with Q and all the others started with ZZ.  I had to manually
> hold it to get the queue moving again.

This should not be happening. The file delivery was attempted on should have
been renamed so that it no longer appears at the front of the queue. PMDF sorts
messages and attempts delivery on messages with the fewest delivery attempts
first.

Moreover, any subsequent immediate delivery jobs should not see this message at
all no matter what its name is; it should be too old to be considered.

I have no explanation other than to suggest you have seriously busted PMDF
somehow.

> I've attached the problem file and the log file showing how the MR_LOCAL
> channel was dying.

Someone has posted a message containing a bogus part; it is labelled as
an NBS part but it is not. PMDF-MR has absolutely no interaction with
any of this -- the part is purely a bag of bits.

PMDF-MR has no choice but to offer these parts to Message Router; there is no
way to check from for legality. And if they fail Message Router is placed in an
inconsistent and unrecoverable state. The entire transaction has to be aborted.
Experience has also shown that sometimes things will work on a subsequent
attempt -- I have no idea why this happens, but it has been reported to occur.
(I have never been able to duplicate it locally; they are either legal or
illegal in any test I've done.)

It is therefore impossible to do anything other than what PMDF-MR is doing now;
the message should eventually time out and bounce, and in the meantime it
should not block the queue in any way.

				Ned
From: ned@sigurd.innosoft.com (Ned Freed)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: How to remove X-ENVELOPE-TO when using MAILLIST
Date: 8 Oct 92 20:59:02 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 08 Oct 1992 13:59:02 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPPIKS7EGI8WX0E7@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"S503@HEC.CA"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>    And we are beginning to use the MAIL SERVER Channel

>    One of my users told me the following:

>    When he send a message to a list, the message is delivered correctly
>    but on the header, you will see a line named X-ENVELOPE-TO which
>    give the list of many dozens of username...

This has nothing to do with the use of MAILSERV.

>    Is there a way to (1) remove that line from the header

It should be removed for locally delivered messages. This is done by the
nox_env_to channel keyword, which is attached to the local channel by default
by the PMDF configuration generator. The effect of this keyword is also fully
documented.

>                   or (2) preferably, substitute the name of the list
>                          instead of the list of all users subscribed to
>                          that list
>                          example:        X-ENVELOPE-TO: my-list-L

This would be a very bad idea. This header is used to reconstruct envelope
addresses and is used by some parts of PMDF for this purpose. Putting the
list address in the header would lead to all sorts of message loops.

					Ned
Newsgroups: vmsnet.mail.pmdf
Subject: API kit availability
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 07 Oct 1992 16:46:38 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Oct 1992 16:46:38 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPOA52XM9E8WWVFU@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

The API kit may also be retrieved from INNOSOFT.COM (anonymous FTP).
Innosoft's link has better performance than that at YMIR.CLAREMONT.EDU

Dan
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: File create errors.
Date: 15 Oct 92 18:52:14 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 15 Oct 1992 11:52:14 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPZ678CJKI8WXT3N@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SETH@speech.mit.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> 	I would make the following observation though. Many times,
> especially when using the CMU name resolver, users would get 'bounce'
> messages from PMDF indicating that there was a delivery failure. We
> still get ocassional messages like the one mentioned above, only to
> find that the mail was later delivered without incident. These messages
> frequently cause the sender some understandable disquiet, and also
> stimulate a resend (by the user) of the (appparently) offending mail
> message. Is there a way to suppress these messages, perhaps at least
> until n delivery attempts have been made? This seems like it would be
> a handy feature. The PostMaster could (optionally) continue to receive
> ALL the messages, to alert her to a potential problem.

I'd have to see one of these "bounce" messages.  If the message was indeed
bounced then it was definitely removed from PMDF's queues thus making it
physically impossible for PMDF to send later despite the "bounce".  I see only
two possible interpretations for what may have actually happened.  First,
perhaps the remote system told PMDF that it rejected the mail (e.g., no such
user) but delivered it anyhow.  This is clearly out of PMDF's control.  The
other possibility is that the message wasn't bounced and the user was actually
sent a "unable to deliver your message for X days; will continue trying for Y
more days" message and misconstrued the message to mean that they had to try
resending the message themselves.

Without knowing what really happened -- i.e., which sort of "bounce" is really
occurring -- I cannot advise you as to which channel keywords to play with.
In general, the keywords you might be interested in are the sendpost,
errsendpost, etc. keywords.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: Stuck BITNET Mail
From: postmaster%frmeu51.bitnet@ymir.claremont.edu
Date: 08 Oct 1992 09:18:32 +0200
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 08 Oct 1992 09:18:32 +0200
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPOS28U6XU8WWRJ8@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.BITNET"
X-Vms-Cc: POSTMASTER
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


Rick Millhollin wrote :

>I've got four files in my BIT_GATEWAY queue that appear to be stuck.

I have frequently this problem with file sent by an user when this user use
a /self and DELIVERY. If he does not use /self the mail is normally sent.
The machine here is very loaded (a microvax) and DELIVERY is very long to
execute the task. I don't know if this help in catching the problem.

B. de Batz (FRANCE)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Tracking Messages
From: John C Klensin <klensin@infoods.mit.edu>
Date: 08 Oct 1992 20:25:10 -0400 (EDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 08 Oct 1992 20:25:10 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: GREENBJB%SNYONEVA.BITNET@ymir.claremont.edu, IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPPS4ZLK8C8WWZ1A@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"NED@SIGURD.INNOSOFT.COM"
X-Vms-Cc: IN%"GREENBJB@SNYONEVA.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>

>PMDF tries to make this happen as much as possible but cannot guarantee it.
>There are many cases where it isn't possible. Here are a few of them:

Ned,
  You left out one very important one:  With current versions of NJE
support on many hosts, generation of these messages is optional.  As I
understand it, the trend is probably to *not* generate them, i.e., fewer
sites are sending them back now than used to.   If the messages are not
generated in the first place, they aren't going to get to the end user
no matter what PMDF does :-(.

>> I need to understand the details of these messages better so I know why we
>> sometimes get them and sometimes don't.
   You are at the mercy of almost everything downstream from you, and
well as the issues about your own configuration that Ned reviewed.
Sometimes you will get them, sometimes you won't.  The only thing you
can guarantee if you want to is *not* getting them.  Otherwise, treat it
as a great mystery of life and forget "understand[ing] the details".

   -john
From: mls@slac.stanford.edu (Mike Sullenberger (415) 926-2294)
Newsgroups: vmsnet.mail.pmdf
Subject: WATERLOO.EDU changed to UWATERLOO.CA ???
Date: 12 Oct 92 19:39:29 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 12 Oct 1992 11:39:29 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPUYVMSHC28WVZYX@INNOSOFT.COM>
X-Vms-To: IN%"info-pmdf@innosoft.com"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


     It seems that WATERLOO.EDU has changed to UWATERLOO.CA, and that the DNS is
not completely up to date and/or consistent.  I have seen many cases of MX
records pointing NOT to real hosts but another MX record.  As far as I can tell
from the RFC's this is not correct. Is that true? And what does PMDF to about
this situation?

Example:

$ mu nsl
> set q=mx
> electro.com.
Non-authoritative answer:
electro.com     preference = 200, mail exchanger = watcgl.waterloo.edu

Authoritative answers can be found from:
ELECTRO.COM     nameserver = NS.UU.NET
ELECTRO.COM     nameserver = UUCP-GW-1.PA.DEC.COM
...
> set q=a
> watcgl.waterloo.edu.

*** No address (A) records available for watcgl.waterloo.edu.

> set q=mx
> watcgl.waterloo.edu.
Non-authoritative answer:
watcgl.waterloo.edu     preference = 0, mail exchanger = watserv2.uwaterloo.ca

Authoritative answers can be found from:
WATERLOO.EDU    nameserver = MAYTAG.WATERLOO.EDU
WATERLOO.EDU    nameserver = WATSERV1.WATERLOO.EDU
...

> set q=a
> watcgl.uwterloo.ca.
Non-authoritative answer:
Name:    watcgl.uwaterloo.ca
Address:  129.97.140.64

Mike Sullenberger
Newsgroups: vmsnet.mail.pmdf
Subject: API availability
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 07 Oct 1992 09:16:00 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Oct 1992 09:16:00 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPNUEHP2WY8WWSCB@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Several people experienced problems FTPing the API kit.  Just my luck that
the system serving the disks decided to have some disk problems this
morning.  Those problems seem tobe fixed now.  The API kit is in the
same place -- [.API]API.BKP.  In addition to ymir.claremont.edu, you
can also use hmcvax.claremont.edu.  After I've rebooted the Innosoft
cluster (this evening), the API kit will also be available from
thor.innosoft.com which has an Internet link with better performance.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Stuck BITNET Mail
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 07 Oct 1992 17:25:44 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 07 Oct 1992 17:25:44 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPOBHROHVM8WWVMY@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"RICKM@OREGON.UOREGON.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

You can try deleting the QUEUE_CACHE.DAT file and rebuilding it from
scratch. That's the only thing I know of you have not done.

Two other sites have reported that this has happened to them. We have never
seen it here, and our experience includes a machine that processes 3000-4000
messages per days.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Adding header tags?
From: Ned Freed <ned@innosoft.com>
Date: 06 Oct 1992 21:55:58 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 06 Oct 1992 21:55:58 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPN7OT4TOY8WWN5C@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ICSRXP%ASUACAD.BITNET@AMERICAN.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Is there a way to add a header tag on mail coming from a channel
> (e.g. MTCP_)?  More specifically, I would like to map an alias to a Usenet
> newsgroup.  For example, if mail is sent to email.general@asu.edu
> (running PMDF v4.1),  I would like it to be sent to our news machine
> (helpdesk.inre.asu.edu) with a tag added "Newsgroup: asu.email.questions".

This sort of thing is most easily done by customizing the generic reprocessing
channel into something that does what you want. This functionality isn't
generally available in PMDF; reprocessing channels were added specifically
to do this sort of thing.

Some knowledge of PMDF and Pascal is required to do this, of course. We are
putting the finishing touches on an API for PMDF that will make it much
easier to do this sort of thing in the future.

				Ned