HDTenEightyP/NetNews huggingface dataset:
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:         Fri, 9 Oct 92 21:46:54 GMT
From:         Jack Pernice <PERN@UORDBV>
Subject:      MAILSERV and SEND/ENCODING
Newsgroups: bit.listserv.pmdf-l

VMS V5.5-2HW on a VS400 model 90
PMDF V4.1-7

We're having a problem with the MAILSERV channel with regard to encoding.

A user sends a request for a file with encoding specified.  MAILSERV responds
with an error:

Remote user sends:

        SEND/ENCODING=UUENCODE [TEST]VMSU2055.RELEASE_NOTES


MAILSERV replies:

        Illegal encoding specified in command: SEND/ENCODING=UUENCODE
        [TEST]VMSU2055.RELEASE_NOTES
        Use the HELP command to get a list of legal MAILSERV commands.

You get a similar MAILSERV response with:

        ENCODING UUENCODE
        SEND [TEST]VMSU2055.RELEASE_NOTES


Here's the relevent portion of a MAILSERV_MASTER.LOG w/ master_debug:

$ run pmdf_root:[exe]mailserv.exe
Debugging enabled.
  Command limit set to 2147483647
  Maximum blocks per message set to 2147483647
  Maximum lines per message set to 2147483647
  MAILSERV reply address is: mailserv-reply@ehsct7.biophysics.rochester.edu

Starting processing of PMDF_ROOT:[QUEUE.mailserv]ZZ01GPQVRKR0HG984IVM.00
  Message is from: PERN@db1.cc.rochester.edu
  Command: ENCODING UUENCODE
  CLI$DCL_PARSE returned status of 196609
Processing ENCODING command.
  CLI$DISPATCH returned status of 0
  Error in command. Ignoring remainder of message.
  Making response header.
  Closing the output message.
  Finished with this message.
$ goto out1


I went poking through the sources and found references to X-UUENCODE so I tried
that.

I got:
        Unrecognized keyword - check validity and spelling
         \X-UUENCODE\
        Use the HELP command to get a list of legal MAILSERV commands.


It seems as if the CLI is parsing the string correctly since it recognizes the
proper keyword ("Illegal encoding specified" vs "Unrecognized keyword").
Are all encodings implemented?

Thanks,
Jack Pernice                             BitNet:    PERN@UORDBV
VMS Systems                              InterNet:  pern@db1.cc.rochester.edu
University of Rochester                  Voice:     (716) 275-7160
Rochester, NY  14620
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 8 Oct 92 01:35:43 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      API kit availability
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ECF_STBO%JHUVMS.BITNET@ymir.claremont.edu"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 7 Oct 92 12:37:48 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: REPOST (for lack of any answer) performance problem with
              local channel
Newsgroups: bit.listserv.pmdf-l

> have some problems with the process symbiont. It sits in a 6000 page working
> set for some reason.

This is a bug.

> A couple of times since I've installed 4.1 the queue has
> stopped for reasons I can't determine. I find no dump file in sys$system...

Same bug.  The process symbiont would grow larger and larger and
eventually die with "insufficient virtual memory".  We can send you a new
executable.

The process symbiont only creates a dump file if you tell it to (no it isn't
documented, but we will ask you to turn it on if necessary).  It did,
however, cause OPCOM to report the fatal condition as it died.  You should've
seen that if you had a terminal enabled for OPCOM messages somewhere.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: from SUNY College at Oneonta, NY 13820
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 8 Oct 92 19:43:05 GMT
From:         Jim Greenberg <GREENBJB@SNYONEVA>
Subject:      Tracking Messages
Newsgroups: bit.listserv.pmdf-l

PMDFers,

Can you point me to a section in the 4.1 manual that might discuss how, why and
when you get messages back from each node (hop) when you send mail.  You know
what messages I mean, the ones that say things like:

        MAIL>
(SNYONEVA) - Sent file 6718 on link SNYBUFVA to SNYBUFVA BROWNRN
MAIL>
(SNYBUFVA) - File (6718) spooled to BROWNRN -- origin SNYONEVA(GREENBJB)
10/08/9
2 10:17:15 EDT

I need to understand the details of these messages better so I know why we
sometimes get them and sometimes don't.

Thanks.


Jim Greenberg
SUNY College at Oneonta

P.S.  Are any of you running PROCESS software with PMDF and JNET?  I have
a few questions about this set up.

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Thu, 8 Oct 92 23:52:12 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: How to remove X-ENVELOPE-TO when using MAILLIST
Newsgroups: bit.listserv.pmdf-l

>    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
From: gareth@LUCIFER.LATROBE.EDU.AU (Chief Smeghead)
Newsgroups: bit.listserv.pmdf-l
Subject: %SYSTEM-F-PROTOCOL, network protocol error
Date: 7 Oct 92 17:27:58 GMT
Organization: La Trobe University
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
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
Comments:     Warning -- original Sender: tag was news@LUGB.LATROBE.EDU.AU


PMDF Guru's.

I have this anoying problem with the UCX/PMDF server. I have searched
the UCX manuals and the PMDF manuals but cannot find the answer.

Upon shutting down my VAX's (VAXstation 3100's) I get the following OPCOM
message...

%%%%%%%%%%%  OPCOM   5-OCT-1992 09:00:33.60  %%%%%%%%%%%
Message from user SYSTEM on ATR1
UCX/PMDF server, UCX_SMTPD exit with: %SYSTEM-F-PROTOCOL, network protocol error

Software:
         VMS V5.4
         UCX V1.3A
         PMDF V4.1

Any help appreciated.

Many thanks,

Gareth.
--
gareth@lucifer.latrobe.edu.au
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Arizona State University
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:         Wed, 7 Oct 92 10:30:17 GMT
Comments:     Warning -- original Sender: tag was NETNEWS@AMERICAN.EDU
From:         Ron Page <icsrxp%asuacad.bitnet@AMERICAN.EDU>
Subject:      Adding header tags?
Newsgroups: bit.listserv.pmdf-l

I haven't found a way to do it, so I thought I'd ask before giving up.

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".

Thanks for your advice.
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:         Wed, 7 Oct 92 08:59:45 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Reverse-rewriting an empty From:-header
Newsgroups: bit.listserv.pmdf-l

> I sometimes see ``service messages'' from Message Router which produce
> mail with empty From:-headers.  My first thought was to rewrite such
> empty From:-headers so that the mail came from the postmaster.

> (1) Is this a good idea?

This should be handled in the FROM_MR.TXT file. There is a special hook ($E)
for handling empty addresses.

The envelope address should be left blank. This is perfectly legal and
proper for service messages.

> (2) If so, can I do it with the REVERSE mapping?  I haven't been able to
>     figure it out so far.

Nope, it is not possible to create an address out of nothing using the
reversal database.

> (3) Is there some way to prevent this ``empty From:-header'' situation
>     from arising in the first place?

Use the $E rule properly.

> (4) What's the prospect on standardization on the format of these
>     Service messages?

Practically none. Message Router does not do return of contents. The Internet
world pretty much demands return of content, and this demand is very likely to
extend to any future standardization of error message return formats. It
certainly applies now to the current format recommended by Nathaniel
Borenstein's RFC that covers this.

The prospects are slightly brighter if you don't consider the return of
content issue, but given the fact that the IETF people dealing with
mail are currently stuck dealing with SMTP extensions, I would not hold my
breath waiting for something to come out in this area.

                                        Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"TERRY@spcvxa.spc.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 9 Oct 92 05:43:25 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: "MESSAGE DAMAGED IN TRANSIT" messages
Newsgroups: bit.listserv.pmdf-l

These occur when a message is partially written to the PMDF queue. This
is usually attributable to a system failure during the writing process.
In this particular case a system failure is very likely the culprit; there
have been a bunch of power failures at the Claremont Colleges
lately.


We'll look into having a more elaborate message in the future. No promises;
this is detected in a heavily used inner loop and it is extremely difficult
to add much functionality there.

                        Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: NYU Medical Center, 550 First Ave., New York, 10016
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"'Terry Kennedy,
          Operations Mgr' <TERRY@spcvxa.spc.edu>",in%"ipmdf@ymir.bitnet"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 10 Oct 92 19:35:59 GMT
From:         SMITH@NYUMED
Subject:      RE: "MESSAGE DAMAGED IN TRANSIT" messages
Newsgroups: bit.listserv.pmdf-l


We have been getting these too.  Does this mean that the message may be missing
a comma somewhere? or does it mean that the entire thing got trashed?  In the
first case, it may be quite helpful to get whatevermessage is available
rather than just the warning.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Thu, 8 Oct 92 03:53:00 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Stuck BITNET Mail
Newsgroups: bit.listserv.pmdf-l

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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"SMITH%NYUMED.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 10 Oct 92 20:31:19 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: "MESSAGE DAMAGED IN TRANSIT" messages
Newsgroups: bit.listserv.pmdf-l

As I stated previously, it means that something interrupted the process
of writing the message into the PMDF queue. The entry is incomplete and
improprly formed; the message you see is simply an indication of this.

It has nothing to do with commas; I don't even know what this means.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Fri, 16 Oct 92 08:34:31 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: File create errors.
Newsgroups: bit.listserv.pmdf-l

>       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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"IMHW400@INDYVAX.IUPUI.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 16 Oct 92 08:49:32 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Looping mail
Newsgroups: bit.listserv.pmdf-l

This sort of things has to be tracked down intelligently by examining the
addresses on the messages themselves. You need to look at what the addresses
say and how they are handled. Use PMDF TEST to check out the addresses as
far as PMDF is concerned. Then look at any forwarding in VMS MAIL. You
also need to check any SET TRANSPORT settings you have, especially on whatever
account you run PMDF under (usually SYSTEM).

Since PMDF things don't seem to have changed the problem is most likely
somewhere in VMS MAIL itself, where checking to see if something has
changed is nearly impossible.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Fri, 16 Oct 92 08:28:55 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: File create errors.
Newsgroups: bit.listserv.pmdf-l

> %MAIL-E-SENDERR, error sending to user audiodev@cbgrle.mit.edu at
> -PMDF-E-FCRT, File create error, Pascal status = 2, VMS statuses = 99684 and 0
> -PMDF-I-TEXT, cannot create channel queue entry

This error, 99684, corresponds to

   $ exit 99684
   %RMS-F-IFI, invalid internal file identifier (IFI) value

Your users are probably
mixing foreign protocols in a single VMS MAIL session; e.g., sending mail to
IN% and then SMTP% or vice versa.  They must only use one of these in any given
MAIL session.   Also, if someone has set their forwarding to xx% then this
problem may be triggered.  The only work around is to only use one foreign
protocol interface if at all possible.  Given that you have PMDF, there's no
need for them to be using things like SMTP%, JNET%, etc.  If you'd prefer to
not re-educate your users, you can always define executive mode logicals of
the form

   $ define/system/exec mail$protocol_smtp pmdf_mailshr
   $ define/system/exec mail$protocol_jnet pmdf_mailshr

etc.

Both TGV and Innosoft is aware of this problem and have tracked it down to a
bug in RMS.  Despite being reported numerous times, DEC has refused to fix this
bug.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"C.Chaundy@its.unimelb.EDU.AU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 9 Oct 92 03:01:34 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: Stuck BITNET Mail
Newsgroups: bit.listserv.pmdf-l

If you move a message from one directory to another you have to wait for
the channel to notice that the message is gone and delete the queue entry and
then for SYNCH_CACHE to run and update the cache with a new entry. We're going
to provide a REBUILD_CACHE tool in the future to make this somewhat easier.

Keep in mind, however, that moving messages from one queue to another isn't
supported because of the possible incompatibility of header formats and the
impossibility of reversing the rewriting that's done. It usually works, but
there are cases where it doesn't.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"gareth@lucifer.latrobe.edu.au"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 10 Oct 92 13:52:08 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: %SYSTEM-F-PROTOCOL, network protocol error
Newsgroups: bit.listserv.pmdf-l

> Upon shutting down my VAX's (VAXstation 3100's) I get the following OPCOM
> message...
>
> %%%%%%%%%%%  OPCOM   5-OCT-1992 09:00:33.60  %%%%%%%%%%%
> Message from user SYSTEM on ATR1
> UCX/PMDF server, UCX_SMTPD exit with: %SYSTEM-F-PROTOCOL, network protocol
error

That is normal, the detached process that handles incoming SMTP connections
under UCX has exited because you've run the UCX$SHUTDOWN procedure.  Because
of problems we used to have with reliability of that detached process, it runs
in a DCL procedure which restarts the server automatically and sends that
notice to OPCOM.  You should ignore it.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
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
Date:         Wed, 7 Oct 92 11:35:51 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Adding header tags?
Newsgroups: bit.listserv.pmdf-l

> 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
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Cambridge Computer Associates, Inc.
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@innosoft.com"
X-VMS-Cc: TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 16 Oct 92 06:16:01 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      PMDF under T6.0
Newsgroups: bit.listserv.pmdf-l

If anyone is running PMDF under a field test of VMS 6.0 and would be
willing to chat with me off line, either via e-mail or analog phone, I
would appreciate it.
--
Bob Tinkelman <bob@camb.com> 1-718-776-6811
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: POSTMASTER
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 8 Oct 92 09:18:32 +0200
From:         POSTMASTER@FRMEU51
Subject:      Stuck BITNET Mail
Newsgroups: bit.listserv.pmdf-l


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)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU