HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Open file quota problem
From: "Kevin V. Carosso" <kvc@summer.innosoft.com>
Date: Thu, 9 Apr 1992 18:52 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Fri, 10 Apr 1992 22:21 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIP5CBQ55C8WX5J4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"GHC@NIHKLMB.BITNET"
X-Vms-Cc: info-pmdf

> can accept that. The question is what do others find as an
> acceptable limit on the open files.  As a temporary measure I have
> raised the limit to 30, but I am only shooting in the dark.  BTW -
> we are using a subprocess quota of 2, pmdf 4.0 and vms 5.3-1.

I find a FILLM lower than 100 to be unnecessarily low.

	/Kevin Carosso
	 Innosoft
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Open file quota problem
From: "Mike Sullenberger (415) 926-2294" <mls@slac.stanford.edu>
Date: Tue, 7 Apr 1992 10:28 PDT
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 10:31 PST
Cc: IPMDF@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIK9OJ2RFK8WWOJV@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"GHC@NIHKLMB.BITNET"
X-Vms-Cc: IN%"IPMDF@YMIR.CLAREMONT.EDU"

>The question is what do others find as an
>acceptable limit on the open files.  As a temporary measure I have
>raised the limit to 30, but I am only shooting in the dark.  BTW -
>we are using a subprocess quota of 2, pmdf 4.0 and vms 5.3-1.

I don't know your situation, but here where we use X-windows alot we have 
increased FILLM to 100.

Mike Sullenberger
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Question about XMAILER.NAMES, DOMAIN.NAMES, and BITEARN.NODES
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Thu, 9 Apr 1992 03:38 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Thu, 9 Apr 1992 03:39 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIMNULW2KW8WWXG8@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"JWMANLY@amhchn.amherst.edu"
X-Vms-Cc: ipmdf

> Now I have a question about the DOMAIN.NAMES and XMAILER.NAMES files.  
> Amherst College (domain AMHERST.EDU) is connected to both BITNET and 
> Internet.  I was looking at our entries in the files above, and found the 
> following:

> DOMAIN.NAMES:

> :nick.AMHERST.EDU :mailer.SMTPUSER@AMHERST  BSMTP  3   :served.YES
> :site.Amherst College
> :gatemast.BITMGR@AMHERST        :interconnect.NO

This is wrong. Your :interconnect field should be either YES or MX, depending
on whether or not all your hosts are directly accessible. If they are not
(and few sites are these days) it should be set to MX.

> XMAILER.NAMES:

> :nick.AMHERST :alias.AMHERST :net.BITNET :mailer. :netsoft.JNET

This is also wrong. You need to register a legitimate mailer in the :mailer
field.

> Do these look right?  Shouldn't we have ":interconnect.YES" in DOMAIN.NAMES 
> since we ARE on the Internet?  If so, who do we contact about getting
> the necessary changes made?

See above. You contact BITNIC to make the change to XMAILER NAMES and
DOMAINS@BITNIC (I think) to make the change to DOMAIN NAMES. Some of this
is documented in the PMDF manual.

> And what is the relationship between these files and the BITEARN.NODES
> database maintained by BITNIC.  Do they ostensibly contain any of the same
> data?  If so, does either one refer to the other directly, or are there
> serious consequences if the two get out of synch?

The XMAILER NAMES file is generated from the BITEARN NODES database; it has no 
existence other than that. You should get a copy of the various procedures
for updating this file and follow them. I'm sure others will help out as
well; this has been discussed many times on this list.

			Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF 3.2 and TWG TCP?IP don't like each other.
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Tue, 7 Apr 1992 05:03 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 05:04 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIJYA5DNF48WWO8B@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"tech@cs.athabascau.ca"
X-Vms-Cc: ipmdf

> I brought up Win TCP/IP version 5.2 and tried to compile the PMDF 3.2
> Wollongong drivers which failed.  I brought over the old libraries from 5.1
> but they won't compile either.
 
You might try running the original programs. Since they are not linked against
any shareable image there should be no real problem running them.

I don't understand why the old libraries would not work. They worked before;
something must have changed.

> I changed the command procedure to use the TWGLIB library instead of LIBNET 
> and LIBNETACC but that produced a tiff with some incompatible symbols which 
> I hacked by declaring RES and H_ERROR noshare and by changing the function 
> call DN_SKIP to DN_SKIPNAME.  Now it compiles but it crashes somewhere in
> gethostbyname().
 
The arguments to DN_SKIP and DN_SKIPNAME are not the same. I hope you paid
attention to this detail.

A crash in gethostbyname sounds a lot like an old Wollongong bug. I have not
seen it in V5.2; it sounds like you're running with old and buggy libraries
if this is happening.

> Where have I gone wrong?  Will this ever compile or should I quit now?  I 
> don't think the boss will be too impressed if I tell him I want a cool 
> thousand dollars for PMDF 4.0.
 
We don't support PMDF V3.2 except to upgrade; the advice I've offered above
is just friendly advice and nothing more. We went to some trouble in PMDF V4.0 
to make it compatible with Wollongong V5.2; the changes in the TCP support 
were fairly substantial overall.

I cannot speak to your price issues in this forum, but I think you might want
to send mail to sales@innosoft.com before quoting numbers.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Problems with versions hitting 32767....
From: smith@nyumed.bitnet
Date: Fri, 10 Apr 1992 21:20 EST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Fri, 10 Apr 1992 18:31 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIOXBP27XC8WWEVG@YMIR.CLAREMONT.EDU>
X-Organization: NYU Medical Center, 550 First Ave., New York
X-Vms-To: in%"ipmdf@ymir.bitnet"

 
Just had PMDF fail because the L_LOCAL.LOG file hit the max.  PMDF mailled lots
of warnings, but could not deliver them because....
 
How about a different strategy here.  When the version limit hits 32000 how
about re-naming all the versions of the log back to version 1 automatically.
If the program is smart enough to figure out that it is that big, doing a
coupole of renames to recify the problem should be a snap.  If getting 32000
as a versioin number is an issue, then a courtesy message to the postmaster
could be sent as well.
 
Comments?
Newsgroups: vmsnet.mail.pmdf
Subject: RE: switching batch queues
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Tue, 7 Apr 1992 14:41 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 14:43 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIKIHB96PS8WWQIH@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"PETER@EMBL-Hamburg.DE"
X-Vms-Cc: IPMDF

> I am trying to switch the queue for a channel, dynamically to another CPU.
> Up to now I have been running the mtcp channels from only one of the two CPUs
> in the cluster that run Multinet.

Perfectly reasonable.

> I initialised a new queue "nodename_mails" on the second CPU, edited pmdf.cnf
> with a "queue nodename_mails" on the channel and reinstalled (CRDB/SYSMAN
> "install replace") AND did an install_replace on pmdf_submit_master.

I assume you mean CNBUILD, not CRDB. CRDB has nothing to do with the
configuration file.

> To my surprise, the periodic job _or_ "@pmdf_root:[exe]submit_master mtcp_xxx"
> appear to start up the _old_ queue, whereas the immediate job seems to start
> the _new_ queue!

Well, sure. The periodic jobs run in the MAIL$BATCH queue. That's the way they
are supposed to work. Channel queue assignments do not affect them except to
make them start their work jobs in the queue that's appropriate to the channel.

If you want to move the periodic jobs you'll have to delete them and restart
them with the proper logical name assignments in effect.

Finally, if you take a look at the parameters SUBMIT_MASTER accepts, you'll see
that one of them is the queue name. SUBMIT_MASTER will submit jobs to whatever
queue you tell it to use; it has no knowledge of the relationship between
channels and queues itself. Adding such knowledge would slow SUBMIT_MASTER down
tremendously and simply is not worth doing. If no queue is specified
SUBMIT_MASTER uses MAIL$BATCH by default.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Interpretation of delivery failure
From: "Sue Ake (814) 863-2524" <sue@a1.psupen.psu.edu>
Date: Fri, 10 Apr 1992 14:41 EST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Fri, 10 Apr 1992 12:07 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIOJWP5FA88WX1ZF@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Content-Type: TEXT
Posting-Date: Fri, 10 Apr 1992 14:45 EST
Importance: normal
Priority: non-urgent
X-Hop-Count: 1
A1-Type: MAIL


Ned,

I just figured out the question that I mentioned in my last message:

	... where did the first "received:" line below get generated?  
	Is it a problem with my configuration?

	-> Received: from PSUPEN.BITNET (SMTPUSER) by CORNELLC (Mailer R2.08A)
	  (stuff deleted)

I didn't have gateway_user_name = "mailer" in my bitnet_domains_driver.com so, 
by default, it ended up as "smtpuser".

I guess if I look long enough, I can actually find what's wrong!

Sue Ake
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Question about $BITNET$xxx.00 files
From: "Daniel C. Newman" <dan@hmcvax.claremont.edu>
Date: Tue, 7 Apr 1992 12:05 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 12:11 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIKD6UDK8W8WWPJU@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"JWMANLY@amherst.edu"
X-Vms-Cc: IPMDF

> 1) What are all these $BITNET$xxxxx.00 files in the PMDF_ROOT:[QUEUE]
>    directory?  They seem to be scattered around in little clumps in terms
>    of creation time, but other than that I can't detect a pattern by looking
>    at them or their contents.  I assume these are files of messages which 
>    never made it out of the system, but at what point are they created?  What
>    kind of circumstances, specifically, need to arise for them to appear?
>
>    For example, if the JNET system were shut down when someone sent a message
>    to a BITNET address through PMDF, could that result in such a file?

These files get left behind by Jnet -- they represent messages we were handing
off to Jnet.  If you are running PMDF V4.0, you can simply delete them.  A
duplicate of the message was kept in the appropriate pmdf_root:[queue...]
subdirectory until the message was successfully sent.  If you are running
PMDF V3.2 or earlier, then you have to hand inspect each of the files and
figure out which pmdf_root:[queue...] subdirectory to rename the message
to (with a name of the form ZZxxx.00).

> 2) Assuming they are messages which never made it out, what is required
>    to get them sent on their way?  (The message contents and headers look
>    fine, so I suspect they would just go out normally.)  Do I just need
>    to rename them into one of the channel subdirectories?  (If so, which
>    one?)

See above.

Dan
From: tinkelman@camb.com (Bob Tinkelman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF 4.0 install
Date: 11 Apr 92 21:26:46 GMT
Article-I.D.: camb.1992Apr11.172647.39944
Organization: Cambridge Computer Associates, Inc.

In article <01GIN6ABEX1Y9BVCNP@HMCVAX.CLAREMONT.EDU>, "Ned Freed, Postmaster"
<ned@hmcvax.claremont.edu> writes:
> If you install PMDF V4.0 in a separate directory and tell it not to start up
> you should be able to get by without disturbing your existing configuration.
>...                                 You are also responsible for moving all
> the files from the old copy to the new one that need to be moved -- this
> includes configuration files, messages in the queues, and any log files you
> want to save. Getting this right can be tricky, which is why we really
> recommend you install over the existing version, thus doing the upgrade "in
> place".

There's a middle ground that I like.  I make a copy of the directory tree
using BACKUP (eg. [pmdf.032...] to [pmdf.040...]) and then do a `new' install
over the copy, specifying purge.  PMDF will replace the old pmdf_startup.com
file, but we don't edit that here.  You also need to heed Dan's warning
regarding installing the same modules from different directories.  However,
if you totally mess up, you can continue using the old (untouched) version
of PMDF.
-- 
Bob Tinkelman, Cambridge Computer Associates, Inc., 212-425-4900, bob@camb.com
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF accounting stats
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Mon, 6 Apr 1992 16:17 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Mon, 6 Apr 1992 16:20 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIJ7KJQZZ48WWA83@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"MITCHELL@uthscsa.edu"
X-Vms-Cc: IPMDF

Actually, the notion of generating overall processing tallies for PMDF is not
a new idea at all. We definitely plan to implement this in the future. However,
it needs to be done by maintaining a general table of this information
internal to PMDF. A user callback is definitely NOT the right answer to
saving this sort of information.

The issues involved are very complex. For example, there are cluster
synchronization issues that need to be addressed. I think I have an overall
scheme that will solve these problems, but it will not see implementation
in the V4.1 time frame.

All of this coincides with standards efforts to design an SNMP MIB for
mail systems. There's a funny coincidence here -- I'm on the committee to
design this creature ;-)

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: Open file quota problem
From: Gerson H Cohen <ghc@nihklmb.bitnet>
Date: Tue, 7 Apr 1992 11:59 EDT
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 09:01 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIK6JH9UTC8WWDVN@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF
X-Vms-Cc: GHC

I have just been informed about a problem relating to the open file
quota which has been occuring recently on this machine.  A user was
doing a repl/edit/extr on a 100 line mail message and tried to spawn
out of the editor (TPU) to go into mail a second time in order to
examine a second message.  He was unable to select a folder or do
anything useful in mail, getting an acp quota error which appears to
be related to the fact that he was left with a quota of only 5.  We
start with 20 and by the time mail is up and going, replying to an
internet message, we are usually left with 5 to 7 as a file limit.
I checked the open files (show dev/fi) on the drives most likely to
be involved and the quota reported is pretty close to what I would
calculate from the investigation.  Some 3 to 5 files relate to
shareable images which pmdf is pulling in, some are data files and I
can accept that. The question is what do others find as an
acceptable limit on the open files.  As a temporary measure I have
raised the limit to 30, but I am only shooting in the dark.  BTW -
we are using a subprocess quota of 2, pmdf 4.0 and vms 5.3-1.
 
Gerson Cohen
ghc@vger.niddk.nih.gov
Newsgroups: vmsnet.mail.pmdf
Subject: RE: I lost the signoff formula for the list (sigh).
From: "Daniel C. Newman" <dan@hmcvax.claremont.edu>
Date: Tue, 7 Apr 1992 11:11 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 11:14 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIKB6GKVLS8WWP82@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"COLEVE@CC.UVCC.EDU"
X-Vms-Cc: IPMDF

> I appear to have forgotton or misplaced the formula for signing off from
> this mailing list....

> Perhaps a reminder for my benefit might help others, too.

> Please, Sir, what is the incantation?

Send mail to qpmdf@ymir.claremont.edu (qpmdf@ymir.bitnet) requesting to
be removed from the list.  There is no magic incantation -- qpmdf is read
by Ned or myself and we merely remove the entry from the mailing list file.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: switching batch queues
From: peter@embl-hamburg.de
Date: Tue, 7 Apr 1992 07:31 +0200
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Mon, 6 Apr 1992 23:39 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIJMWGWPV48WWNES@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
X-Vms-Cc: PETER
Comments: ---- EMBL Hamburg is no longer in BITnet ---- use EMBL-Hamburg.DE ----

I am trying to switch the queue for a channel, dynamically to another CPU.
Up to now I have been running the mtcp channels from only one of the two CPUs
in the cluster that run Multinet.

(As a result of the "os_smtp_write: network read failed: broken pipe" error that
 I reported earlier, I had a backlog of some 200 files in one of my MTCP_xxx
 channels [queue.MTCP_xxx])

I initialised a new queue "nodename_mails" on the second CPU, edited pmdf.cnf
with a "queue nodename_mails" on the channel and reinstalled (CRDB/SYSMAN
"install replace") AND did an install_replace on pmdf_submit_master.

To my surprise, the periodic job _or_ "@pmdf_root:[exe]submit_master mtcp_xxx"
appear to start up the _old_ queue, whereas the immediate job seems to start
the _new_ queue!

What did I miss?


regards
Peter Bendall
European Molecular Biology Laboratory,
Hamburg Outstation.
 Tel:      +49  40 - 890 801 33 : Internet          Peter@EMBL-Hamburg.de
 FAX:      +49  40 - 890 801 49 : EAN-Mail          Peter@Hamburg.embl.dbp.de
                                :         (S=Peter;OU=Hamburg;P=embl;A=dbp;C=de)
Newsgroups: vmsnet.mail.pmdf
Subject: TGV address?
From: "Zvonko Orsolic, University of Belgrade" <zvonko@yubgef51.bitnet>
Date: Tue, 14 Apr 1992 15:52 -0200
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 14 Apr 1992 07:00 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GITUD0XMN48WXHGJ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.bitnet"
X-Vms-Cc: ZVONKO

I am searching for e-mail address and fax number of TGV Incorporated.
If TGV doesn't exist any more, I need the same information for the
current manufacturer of "Multinet".
 
According to the papers I have, Multinet info and orderings should be
maintained by <service@tgv.com>. Unfortunately, the only answer from
that address is
 
> 550 Host 'tgv.com' Unknown
 
What happened to TGV?
 
Regards
 
Zvonko Orsolic
University of Belgrade
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Pmdf Statistics
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Thu, 9 Apr 1992 22:02 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Thu, 9 Apr 1992 22:02 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GINQFAPFQO8WW6GR@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"UCCXJPS@vms.ucc.okstate.edu"
X-Vms-Cc: IPMDF

Determine the channel used to connect to the remote site and enable logging
on that channel. Then you can count or otherwise analyze the records written
to the PMDF log file.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF.CNF for a 2node hetero cluster.
From: "Daniel C. Newman" <dan@innosoft.com>
Date: Tue, 7 Apr 1992 12:22 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Tue, 7 Apr 1992 12:27 PST
Cc: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIKDPNFAXC8WWPPY@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"MAHENDRA@Meena.CC.URegina.CA"
X-Vms-Cc: SERVICE,IN%"info-pmdf@ymir.claremont.edu"

>
>   We now have the license to run PMDF on two nodes (say A and B) of our
>   cluster. Since the SYSUAF and VMSMAIL_PROFILE_DATA files reside in
>   each node's Sys$specific directory, these are heterogeneous clusters,
>   right?? Node A runs Jnet and has Mail$Batch executing in it. Node B
>   is not licensed for Jnet. Both nodes are on Internet running
>   MultiNet.
>
>   I want to
>
>   (1)  run just one copy of PMDF, and

Sorry, this just won't work for you.

>   (2)  allow user's on node B to use the IN% contruct to send and
>        receive Internet/Bitnet mail,
>
>   Should I be using TWO different PMDF.CNF files, one for each node, so
>   that I can specify the right name for the local host on the L
>   channel?? Is there a better way - must be - but my finicky brain
>   cannot see it through. Please help.

Well, you have to treat these two systems as though they are entirely separate
systems and use entirely different PMDF directory trees, with separate
MAIL$BATCH queues on each system.  All of this difficulty is caused by your
specific SYSUAF's and VMSMAIL_PROFILE_DATAs which cause you to require a
distinct local channel (and PMDF_ROOT:[QUEUE.L] directories) for each system.

Install PMDF separately on each system.  On the system not running Jnet, do
not configure it to use BITNET but instead use the files

     pmdf_root:[table]gateway.rules
     pmdf_root:[table]bgateway.rules

produced by executing pmdf_root:[table]bitnet_domains_driver.com on the Jnet
system.  Copy these files to pmdf_root:[table] on the non Jnet system and
include them in the rewrite rules section of pmdf_root:[table]pmdf.cnf:

    <pmdf_root:[table]gateway.rules
    <pmdf_root:[table]bgateway.rules

You can use your TCP/IP network to route mail between the two systems.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Problems with versions hitting 32767....
From: "Ned Freed, Postmaster" <ned@hmcvax.claremont.edu>
Date: Fri, 10 Apr 1992 22:07 PST
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Fri, 10 Apr 1992 22:07 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIP4VTOOLS8WX6W8@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SMITH@NYUMED.BITNET"
X-Vms-Cc: IPMDF

This scheme has already been implemented in PMDF V4.1, along with many other
changes to file version handling in PMDF. This amounts to a complete and
total reworking of all the logic in this area.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: sendhead keyword (again)
From: Robin Goldstone <robin_goldstone@macgate.csuchico.edu>
Date: 10 Apr 92 13:55:06 U
Organization: The Internet
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Resent-Date: Fri, 10 Apr 1992 13:55 PST
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-Id: <01GIONO8IIKG8WX2G7@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"

I just installed PMDF 4.0 and I cannot get the 'sendhead' keyword to work. 
Someone else posted this problem a few months ago but I never saw a resolution.
 Sendhead should cause the copy of returned mail sent to Postmaster to not
contain the original message body.  But it does not work.  I (postmaster) still
get the whole message.  

I have sendhead on the local channel and also my ctcp channel.  Here is the
relevant part of pmdf.cnf:

l 822 bidirectional logging headeromit sendhead notices 1 2
oavax.csuchico.edu

ctcp_local single_sys smtp mx logging sendhead notices 1 2
CTCP-DAEMON

Does anyone know what my problem might be?  

Robin Goldstone, CSU Chico