HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"service@innosoft.com"
X-VMS-Cc: IN%"info-pmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 26 Jan 93 17:47:01 GMT
From:         John Emanuel Perkins <PERKINS@KSUVXA.KENT.EDU>
Subject: Pmdf 4.1 / J-Net 3.6: What changes need to be made to.......
Newsgroups: bit.listserv.pmdf-l


Referencing Pages 6-17 through 6-19, section 6.12 of the PMDF 4.1 Reference
Manual (Routing to systems not running NJE):

Given the senario:

  With J-Net 3.5 and PMDF 4.1, with the modifications made as per the
  instructions in this section, The Former BITNET node name KENTPHYS, still
  known to NJE Systems, is properly receiving mail on Internet node
  KSUVXD.KENT.EDU.

  An Update to J-Net 3.6, maintaining the same configuration files and PMDF
  4.1, the Mail Forwarding Mechanism now fails.

The question:  Is there a patch or some other change that is known to be
required to restore the forwarding mechanism, or is this something I should
ask Wingra (Formerly Joiner)?

Thanks in advance for any assistance!

John Perkins

--
John Emanuel Perkins
System Software Specialist
VAX System Manager
Kent State University

perkins@kentvms         (BITNET)
ksuvxa::perkins         (DECNET)
perkins@ksuvxa.kent.edu (Internet)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 00:57:47 GMT
From:         "Dave Mulvihill - Tech. Support X-6993"
              <DPMSYS@RITVAX.ISC.RIT.EDU>
Subject:      Notes channel questions
Newsgroups: bit.listserv.pmdf-l


The NOTES_CHANNEL options allows you to define retention times for the
topic headers in the .subjects file.  Does this only control retention
of headers or will it purge of the related notes in the conference too?

Assuming future development of this channel will allow bidirectional
operations, are there plans to have some sort of learn command to allow
the channel to connect to an existing NOTES conference?

Also the current channel doesn't handle posting to a conference which
is set /REPLY_ONLY very gracefully.

I get the following ACCVIO:

$ define/user option_file        pmdf_root:[table]notes_local_option.
$ run pmdf_root:[exe]notes_master.exe

14-JAN-93  13:43:40: Error adding note to notefile VMS
%NOTES-E-CONF_REPLY_ONLY, conference is set to REPLIES only.  No privilege to ad
d new topics
%NOTES-E-CONF_REPLY_ONLY, conference is set to REPLIES only.  No privilege to ad
d new topics
%NOTES-E-CONF_REPLY_ONLY, conference is set to REPLIES only.  No privilege to ad
d new topics
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000CC, PC
=000CA8EA, PSL=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000CA8EA  000CA8EA
                                                           000C8485  000C8485
                                                           000C940F  000C940F
                                                           000C8485  000C8485
                                                           000C7E1B  000C7E1B
NOTES_MASTER    RETURN_BAD_MESSAGES              5345      0000029C  00005714
NOTES_MASTER    DOSUBMIT                         6220      00001AA9  000044C5
NOTES_MASTER    NOTES_MASTER                     6508      00000019  00002905
$ goto out1
$ out1:
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@INNOSOFT.COM", IN%"NED@SIGURD.INNOSOFT.COM"  "Ned Freed"
Autoforwarded: false
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Importance: normal
Priority: non-urgent
UA-content-id: 1171CBC31A00
X-Hop-count: 1
Date:         Mon, 25 Jan 93 21:26:34 GMT
From:         "Kim Wohlert erik mainz a/s" <kw@SKADE.MAINZ.DK>
Subject:      REF: Re: NOTES channel and FWD:
Newsgroups: bit.listserv.pmdf-l

>> We use the PMDF NOTES channel at eisner.decus.org to populate a
>> conference from the info-multinet list.  Lately we've reveived
>> a number of items with subjects that look like:
>>       FWD: RE: some earlier subject

>> These don't get matched up with the earlier notes with subjects
>>       RE: some earlier subject
>
>> Would it be reasonable for the NOTES channel to treat FWD in the
>> same manner as it treats RE?
>
>Sounds reasonable to me; I'll go ahead and implement this for our next
>release.
>
>                                Ned

Sounds great.

Could I suggest that you make the options (Re:, FWD: etc.) completely
configuable in order to accomodate national conventions and fashions.

Regards

Kim
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Organization: Penn State University / University Libraries
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: INFO_VAX
X-VMS-Cc: IPMDF
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 26 Jan 93 22:38:18 GMT
From:         "J.Lance Wilkinson, 814-865-1818" <JLW@PSULIAS.BITNET>
Subject:      Looking for VMS-based X.500 Client Software
Newsgroups: bit.listserv.pmdf-l

Well, I had pretty good luck a few months ago when I was looking for an NNTP
client for VMS by asking here on INFO-VAX.  How about an X.500 client for VMS
-- any implementations?

Another site (non-VMS) here on campus has implemented a rudimentary X.500
server, and we want to see if it:

        (1) has our information correctly posted
        (2) can be accessed to the benefit of our users
        (3) might eventually be incorporated into things like our Email
                (PMDF/VAX Mail)

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Williams College Center for Computing
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.BITNET"
X-VMS-Cc: JANDERSON
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 28 Jan 93 16:05:07 GMT
From:         "Jim Anderson - Systems Manager - x2082"
              <JANDERSON@WILLIAMA.BITNET>
Subject:      Moving and existing installation
Newsgroups: bit.listserv.pmdf-l


  I'm in need of freeing up some space on my system disk.  First, can PMDF
reside somewhere other than the system disk?  Two, is the move as simple as
doing a backup to the new location and then editting the startup com to point
to the new device?  And three, what is the need for keeping all the "sources"
online.  What's the feeling on deleting them and if the need for them ever
arises, pulling them back off the disktribution by hand?

Jim

********************************************************************************
Jim Anderson                                            Williams College
Systems Manager                                         Center for Computing
janderson@williams.edu (Internet)                       Jesup Hall
janderson@williams.bitnet                               Williamstown, MA 01267
                                                        413-597-2082
********************************************************************************


********************************************************************************
Jim Anderson                                            Williams College
Systems Manager                                         Center for Computing
janderson@williams.edu (Internet)                       Jesup Hall
janderson@williams.bitnet                               Williamstown, MA 01267
                                                        413-597-2082
********************************************************************************
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:         Thu, 21 Jan 93 21:08:34 GMT
From:         Jack Pernice <PERN@DB1.CC.ROCHESTER.EDU>
Subject:      %STR-F-INSVIRMEM error using Process Symbiont
Newsgroups: bit.listserv.pmdf-l


VMS V5.4-2
PMDF V4.1-12

We're using the PMDF Process Symbiont.  The queues are running on a fairly
busy machine.  The queues themselves are fairly busy with up to 2000+
processes per day.  Yesterday I found the symbiont queues stopped.  They
restarted without problem.  I found the following information in the
operator log:

%%%%%%%%%%%  OPCOM  20-JAN-1993 12:06:07.19  %%%%%%%%%%%
Message from user SYSTEM on DB1
%PMDF-F-PRCSMBFTL, PMDF process symbiont fatal internal error

%%%%%%%%%%%  OPCOM  20-JAN-1993 12:06:08.78  %%%%%%%%%%%
Message from user SYSTEM on DB1
%STR-F-INSVIRMEM, insufficient virtual memory

I checked the System Messages Manual.  The explanation implies a programming
issue rather then a change to any SYSTEM or UAF parameters.  Is there anything
I can do to prevent this?

Thanks,

Jack Pernice                             BitNet:    PERN@UORDBV
VMS Systems                              InterNet:  pern@db1.cc.rochester.edu
University of Rochester                  Voice:     (716) 275-7160
Rochester, NY  14620
USA
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DPMSYS@ritvax.isc.rit.edu" "Dave Mulvihill - Tech. Support
          X-6993"
X-VMS-Cc: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 00:57:58 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Notes channel questions
Newsgroups: bit.listserv.pmdf-l
              14 Jan 1993 16:21:26 -0500 (EST)"
              <01GTIEBXKEDE91WRI4@ritvax.isc.rit.edu>

> The NOTES_CHANNEL options allows you to define retention times for the
> topic headers in the .subjects file.  Does this only control retention
> of headers or will it purge of the related notes in the conference too?

Purging notes out of conferences is up to VAX NOTES, not PMDF. I assume that
this is a solved problem since the ability to do this is an essential part of
practically any use for VAX NOTES I can think of. Does anyone on the
list have some advice on how to do this?

> Assuming future development of this channel will allow bidirectional
> operations, are there plans to have some sort of learn command to allow
> the channel to connect to an existing NOTES conference?

This certainly isn't a planned enhancement since it does not make sense.
Consider: You're connecting a new source of traffic to the conference, which by
definition cannot be associated with any previous traffic. Any duplication of
subject information is therefore coincidental and meaningless.

> Also the current channel doesn't handle posting to a conference which
> is set /REPLY_ONLY very gracefully.

> I get the following ACCVIO:

This is a known bug that was fixed in PMDF 4.1-14. Contact sales@innosoft.com
if you need to arrange to obtain this or any other update.

                                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.bitnet"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 27 Jan 93 16:47:13 GMT
From:         "Anna Tomecka, x7733" <ANNA@CLARKU.BITNET>
Subject:      trying to reach a Bitnet address
Newsgroups: bit.listserv.pmdf-l

Hi,

I was wondering if somebody could help, please.  I cannot send a message to
the following address, user@frccub11.bitnet.  Get an error message of invalid
node or domain.  It's a valid Bitnet address.  I just rebuilt my config
database.  When I look into the xmailer.nodes file, the node is there and
designated as net.EARN as opposed to net.BITNET what I think it should be, or
shouldn't it?  How can reach that node?  Thanks for your suggestions.

Anna
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Organization: Penn State University / University Libraries
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF
X-VMS-Cc: JLW
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 25 Jan 93 23:21:42 GMT
From:         "J.Lance Wilkinson, 814-865-1818" <JLW@PSULIAS.BITNET>
Subject:      PMDF v4.1 installation
Newsgroups: bit.listserv.pmdf-l

Yeah, I know.  People have been leaning on me for nearly a year to move from
v4.0 to v4.1.  Well, finally the v4.0 -only homebrew channel we'd been using to
support All-in-1 is no longer required (our few All-in-1 users have chosen to
look at not using All-in-1 for Email), and we can move to v4.1 with impunity.

Running VMS v5.5-2, Multinet v3.0 Rev H (soon to install v3.2), Jnet v3.5.

We have v4.1-10 in hand to install.

(1) Any compatibility problems with using the current PMDF v4.0 SMTP handler
        if we move to Multinet v3.2 before I get PMDF v4.1 installed? (Note:
        DIFFERENT staff are responsible for installations here -- I have PMDF
        and JNET, another has Multinet and VMS; out installation might not be
        compatible).

(2) Any compatibility problems with using the PMDF v4.1-10 SMTP handler as
        linked in the install kit with Multinet v3.2?  Just relink?  Higher
        PMDF patch release?

(3) Any need for a higher patch release of PMDF v4.1?  What's the current
        revision and where is a list of the fixes that current revision
        supplies?

(4) How close am I to v4.2?  Is moving to v4.1 advisable with v4.2 just around
        the corner?

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
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: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 21 Jan 93 21:27:18 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Aliases and FAXen
Newsgroups: bit.listserv.pmdf-l

> We have been happily using PMDF-FAX for sometime now.  I now am being asked
> to add lots of aliases to make sending FAXes easier.  The rub is that the
> users would like to use an alias and override some of the attribute pairs
> when then send the message.  This would allow specifying a unique ``please
> deliver this to'' without having to remember the phone number.  Can I do
> this?  How do I do this?

Oh, I forgot to mention that going into 4.2 is a special header line
(controlled via a logical) which can specify default attributes to apply
to FAX addresses.  So, if you had the system-wide alias

     tek-fax:   /fn=012-345-6789/o=Tektronix/@text-fax

and a user has this magic logical set to "/at=Mrocheck Freed/tn=555-1212/"
then the PMDF-FAX would pick up all four attributes, fn, o, at, tn.

All that remains would be a painless means for your users to set these
logicals.  (DCL script?)  This mechanism is actually intended for more static
information (stn, sfn, setup, fsi, tti, etc.) but can be used for in this
situation too.

Dan
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"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 25 Jan 93 10:26:15 -0500
From:         SKIPPER@MEDCOLPA.BITNET
Subject:      Trouble reaching UNC?
Newsgroups: bit.listserv.pmdf-l

Good Morning all!

Quick question.  I have a user who is trying to reach a user with the
email address of user@UNC.  PMDF is rewriting this as UNC.BITNET and
sending it to MAILER@UNC.  This fails with a "invalid domain" type
message.  Upon looking into this, I can easily duplicate the error.
Interestingly, user@UNCA or user@UNCG will work with no problem.  I am
running the current version of XMAILER.NAMES and DOMAIN.NAMES.

Any idea what is happening?  If more information is needed, I will gladly
provide it.  Replies can be directed to the net or to me directly.

Thanks in advance.

/tom

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
L. Thomas Skipper (Tom)                             M     M   CCCCCC  PPPPPPP
VAX Systems & Networking Manager                    MM   MM  C        P      P
Medical College of Pennsylvania                     M M M M  C        P      P
College Computer Center                             M  M  M  C        PPPPPPP
2900 Queen Lane                                     M     M  C        P
Philadelphia, Pennsylvania 19129                    M     M   CCCCCC  P

BITNET:  SKIPPER@MEDCOLPA  Internet: SKIPPER@CCC.MEDCOLPA.EDU
PHONE:   (215)991-8180          -OR- SKIPPER@SINGER.ASRI.EDU
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.bitnet"
X-VMS-Cc: PAYNE
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 25 Jan 93 22:43:31 GMT
From:         John Payne <PAYNE@ITHACA.BITNET>
Subject:      Lost header lines in BSMTP bounce?
Newsgroups: bit.listserv.pmdf-l

Hello-

When an undeliverable BSMTP message arrives through our BITNET
gateway, the bounce message consistently loses the first line
or two of the original headers.  I've included an example below.

We just installed PMDF 4.1-13, JNET 3.6 and VMS 5.5-1.

I'm using the old PMDF 4.0 configuration:  I recompiled and installed
the old PMDF.CNF with no modifications, and other than these bounce
header trims, things seem to be working okay.

By the way, this trimming only appears on the bit_gateway channel, as
far as I can tell.  Bounces on the local channel and regular NJE
channel don't show this anomaly.  Anyone recognize what I've missed?

Thanks.

-John

John Payne
Academic Systems Coordinator            payne@ithaca.bitnet
Academic Computing Services             payne@ithaca.edu
Ithaca College, Ithaca, NY 14850


-----Here's an example of a bounced BSMTP message I created-----

From:   IN%"postmaster@ITHACA.BITNET"  "PMDF Mail Server" 25-JAN-1993 11:26:01.4
   3
To:     IN%"postmaster@ITHACA.BITNET", IN%"PAYNE@ITHACA.BITNET"
CC:
Subj:   Undeliverable mail: SMTP delivery failure

Return-path: <postmaster@ITHACA.BITNET>
Received: from CORNELLC (MAL@CORNELLC) by ITHACA.BITNET (PMDF #2677 ) id
 <01GTXMYFPOWW8WX6RA@ITHACA.BITNET>; Mon, 25 Jan 1993 11:25:38 EST
Date: 25 Jan 1993 11:25:38 -0500 (EST)
From: PMDF Mail Server <postmaster@ITHACA.BITNET>
Subject: Undeliverable mail: SMTP delivery failure
To: postmaster@ITHACA.BITNET, PAYNE@ITHACA.BITNET
Message-id: <01GTXMYL90UK8WX6RA@ITHACA.BITNET>
X-Envelope-to: PAYNE, postmaster
Content-transfer-encoding: 7BIT

Your message could not be delivered to:

Addressee: bogusid@ithaca.bitnet
Reason: unknown or illegal user: bogusid@ITHACA.BITNET


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

 Jan 93 11:25:46 EST
Received: from ITHACA.BITNET (PAYNE) by CORNELLC (Mailer R2.08A) with BSMTP id
 1903; Mon, 25 Jan 93 11:25:09 EST
Received: from ITHACA.BITNET by ITHACA.BITNET (PMDF #2677 ) id
 <01GTXMUPQW5C8Y58A2@ITHACA.BITNET>; Mon, 25 Jan 1993 11:23:14 EST
Date: 25 Jan 1993 11:23:14 -0500 (EST)
From: John Payne <PAYNE@ITHACA.BITNET>
Subject: Testing SMTP bounces
To: bogusid%ithaca.bitnet@cornellc.cit.cornell.edu
Message-id: <01GTXMUPQW5E8Y58A2@ITHACA.BITNET>
X-Envelope-to: bogusid%ithaca.bitnet@cornellc.cit.cornell.edu
X-VMS-To: IN%"@cornellc.cit.cornell.edu:bogusid@ithaca.bitnet"
MIME-version: 1.0
Content-transfer-encoding: 7BIT

This is an undeliverable message.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"PERN@db1.cc.rochester.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 00:58:20 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: %STR-F-INSVIRMEM error using Process Symbiont
Newsgroups: bit.listserv.pmdf-l

> VMS V5.4-2
> PMDF V4.1-12
>
> We're using the PMDF Process Symbiont.  The queues are running on a fairly
> busy machine.  The queues themselves are fairly busy with up to 2000+
> processes per day.  Yesterday I found the symbiont queues stopped.  They
> restarted without problem.  I found the following information in the
> operator log:
>
> %%%%%%%%%%%  OPCOM  20-JAN-1993 12:06:07.19  %%%%%%%%%%%
> Message from user SYSTEM on DB1
> %PMDF-F-PRCSMBFTL, PMDF process symbiont fatal internal error
>
> %%%%%%%%%%%  OPCOM  20-JAN-1993 12:06:08.78  %%%%%%%%%%%
> Message from user SYSTEM on DB1
> %STR-F-INSVIRMEM, insufficient virtual memory

This was fixed in 4.1-13.  I'll e-mail you the new image.  Be sure to put it
into sys$common:[sysexe] and STOP/QUEUE/RESET the queue and then restart it.

Dan
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"  "Bob Tinkelman"
X-VMS-Cc: IN%"ipmdf@INNOSOFT.COM"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 22 Jan 93 21:59:37 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: NOTES channel and FWD:
Newsgroups: bit.listserv.pmdf-l
              21 Jan 1993 21:32:17 -0500 (EST)" <01GTSMV4UGS894E6D6@camb.com>

> We use the PMDF NOTES channel at eisner.decus.org to populate a
> conference from the info-multinet list.  Lately we've reveived
> a number of items with subjects that look like:
>       FWD: RE: some earlier subject

> These don't get matched up with the earlier notes with subjects
>       RE: some earlier subject

> Would it be reasonable for the NOTES channel to treat FWD in the
> same manner as it treats RE?

Sounds reasonable to me; I'll go ahead and implement this for our next
release.

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