HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"andrewr@itd.adelaide.edu.au"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 14 Sep 92 11:20:33 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Problems with cc:Mail channel.
Newsgroups: bit.listserv.pmdf-l

>       OK, Thanks. The problem is that the documentation I have
> (PMDF-REF-4.1) has minimal information on this.

You might want to check the online documentation -- it may be more
complete even in the early release you have.

>       When I try this, I get the following error message:

> $ @PMDF_ROOT:[EXE]MASTER CC_LOCAL POLL
> %DCL-I-SUPERSEDE, previous value of OPTION_FILE has been superseded
> %PAS-F-ARRINDVAL, array index value is out of range
> ...

>       Now, according to "help errors supersede", this message
> indicates a success state after redefining the logical name
> OPTION_FILE, and requires no user action.

Correct. This error is irrelevant.

> As such, the first thing of
> note is the Pascal error message.

Correct. This is a problem that was fixed in -10 or thereabouts.

>       I'm hesitant to do this until the above problem is resolved,
> which it probably is in the current release.

It is.

>       ident="V4.1-A"

>       Not sure what the latest release from our supplier is, will
> contact service as requested if they don't dave -10 or greater.

Interesting -- I don't know of an instance where we used a letter as a
dash number. Be that as it may, this is definitely a very early version
and you need a more recent one.

                                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.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 10 Sep 92 21:49:47 GMT
From:         Francesco Gennai <FRANZ@VM.CNUCE.CNR.IT>
Subject:      RE: Mail system to use with PathWorks?
Newsgroups: bit.listserv.pmdf-l

>  .....   .. .  . ..
>I would appreciate any comments.  If you wish to avoid a lengthy
>argument on the list, feel free to mail opinions directly to me, and I
>will summarise in a couple of weeks.
>
>Thanks in advance,
>
>Alistair Grant
>   . . .  .......  . . .
I'm interested in this argument, so I would like have the discussion
on the list.

Regards,

Francesco Gennai.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"alistair@mits.com.au"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 13 Sep 92 02:48:11 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: Mail system to use with PathWorks?
Newsgroups: bit.listserv.pmdf-l

> We are currently in the process of connecting all our PC's to the
> network using PathWorks, and I am trying to determine the most
> appropriate mail system to put in place.  It must be able to integrate
> with VMS Mail.
>
> 1.    The unsupported mail client.  This is a DOS application and
>       most of our users use Windows, so this is a bit clunky.

I assume you mean PATHworks mail.  I don't think it is considered "unsupported".
It works fine with PMDF with no additional software requirements.  However,
if they want a Windows application, this won't do it.

> 2.    Microsoft Mail as licensed with MS Office.  Has anyone
>       integrated this with PMDF?

PMDF does not currently have a direct gateway to MS Mail.  If you are using the
MS Mail PC product (as opposed to the completely different MS Mail Mac product)
then your best bet would be to purchase an MS Mail <-> SMTP gateway from
Microsoft.  If you use the Mac product then purchase the SMTP gateway from
Star Nine (details available if you need them).

> 3.    DEC's Mailworks.

This works very well with PMDF.  You will, however, need Message Router and
PMDF-MR.  MR when purchased as part of the MAILworks WAN Server package does
not add much to the cost, but you will need to install and manage it.

You might also look into cc:Mail from Lotus.  PMDF does have a gateway to
cc:Mail.

Unfortunately, like MS Mail, the disadvantage to running cc:Mail  is that you
will need to manage PC based "Post Offices".  Personally I find a solution that
uses the VMS machine for all mailboxes (like MAILworks) with only the client on
the PC to be preferable.  Management is centralized, the reliability is higher,
and you get all the advantages (backup, clusters, shadowing, striping, etc...)
of VMS behind the user's data.

        /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%"ipmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 12 Sep 92 07:54:23 GMT
From:         "Daniel C. Newman" <DAN@SIGURD.INNOSOFT.COM>
Subject:      FAX pop-up form and VMS MAIL keypad keys: problem resolved
Newsgroups: bit.listserv.pmdf-l

Several sites have reported a problem whereby the FAX pop-up form disrupts the
ability to use the VMS MAIL keypad keys.  Thanks to Concordia University
(Riverforest, Illinois), we've managed to finally track this problem down.

The only workaround at present is to keep your terminal set /PERM/APPLICATION.
Of course, this is not practical for sites who need to keep their terminals set
/NUMERIC.

Here's what goes wrong.  When you enter VMS MAIL, MAIL uses a $QIO SETMODE
operation to _temporarily_ enable the application keypad (/APPLICATION) and
thereby allow keypad commands to be used.  Now, when the pop-up form is
invoked, SMG$ is used to create a virtual display and keyboard.  When creating
the keyboard, SMG$ incorrectly does a $QIO SENSECHAR and notes the _permanent_
keypad setting and not the temporary one.  Then, when the pop-up form exits and
SMG$ deletes the display and keyboard, it resets what was the _permanent_
keypad setting.  So if, before entering MAIL, the keypad was set /APPLICATION
then everything is okay and the keypad will still function within VMS MAIL.
However, if the keypad was set /NUMERIC before MAIL was invoked, then SMG$
will restore this setting thereby losing MAIL's temporary /APPLICATION setting.

Clearly, this is a SMG$ bug.  We'll fix this in PMDF V4.2 by doing the obvious:
undoing what SMG$ does after SMG$ is shut down.  Unfortunately, it is not
possible for us to patch this in 4.1 as it involves a piece of code not shipped
with PMDF.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: St. Peter's College, US
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DAN@INNOSOFT.COM"
X-VMS-Cc: IPMDF@YMIR.CLAREMONT.EDU,TERRY
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Sep 92 09:47:38 GMT
From:         "Terry Kennedy, Operations Mgr" <TERRY@SPCVXA.SPC.EDU>
Subject:      RE: Limiting access to outgoing mail.
Newsgroups: bit.listserv.pmdf-l

> I shall summarize below the new support so that anyone spotting any missing
> functionality, blunders, or whatnot can bring them to our attention now,
> well in time for the next release.  And of course, further ideas are always
> welcome.
>
>    from_channel|from_address|to_channel|to_address     $Y/$N

  I'd like to be able to specify keywords to override the channel parameters
or the PMDF defaults as well. That way, I can set holdexquota as a channel
keyword and noexquota for a particular "problem" user. Likewise, I can set
sendpost/nosendpost for delivery errors to this address.

  What do you think?

        Terry Kennedy           Operations Manager, Academic Computing
        terry@spcvxa.bitnet     St. Peter's College, Jersey City, NJ USA
        terry@spcvxa.spc.edu    +1 201 915 9381
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"k2@bl.physik.tu-muenchen.de"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 11 Sep 92 23:37:28 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Problem with reprocess and defragment channel
Newsgroups: bit.listserv.pmdf-l

Just replace "reprocess.snoopy.bl.physik.tu-muenchen.de" and
"defragment.snoopy.bl.physik.tu-muenchen.de" with shorter names.
The actual names used are irrelevant; the key issue is that the
channel have some sort of host name associated with it.

For instance, defragment.tu-muenchen.de should work just fine.
These channels are internal reprocessing channels used only
by the local PMDF.  The outside world never sends mail to them
directly.

Dan
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, I_BBOARD, IPMDF
X-VMS-Cc: JLW
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 9 Sep 92 00:34:16 GMT
From:         "J.Lance Wilkinson, 814-865-1818" <JLW@PSULIAS>
Subject:      Looking for Callable Notes information
Newsgroups: bit.listserv.pmdf-l

I recently poured through the VAX NOTES UTILITY conference on the VS0133 DECUS
CD-ROM, and found several threads concerning Callable Notes.  It seems that the
most extensive work posted originated with the original author of the NUPDATE
program Terry Kennedy posted onto the I-BBOARD list a few months ago, a
gentleman named John Jones from Quad/Grapics (?).  However, of course the
DECUSERVE conference dies off with April '91, since that's the time frame
for cutoff on the Spring '91 library.  The bulk of the information seems to
come in a thread from December '89; the last posting from Mr. Jones appears in
May of '90, and the last reference to him appears in March of '91.

Is there any chance anybody's done more on this since then?  Or if Mr. Jones is
out there, have *you* done any more since then?  There was a note from you
early in the discussions I perused, indicating a 600+ line file you offered to
interested parties, detailing what you already had determined.

My specific application involves a problem with a function/output item pair
noted in a postscript matrix Mr. Jones posted in September '90:
NOTES$ENTRY_GET_CLASS() and NOTES$K_CLASS_NAME.  What I'm trying to do is to
enhance his NUPDATE.C program so that, when scanning all entries in all
classes, it includes the relevant class name in reporting entries having unseen
notes.  I'll of course settle for solving this one problem, but of course I'm
interested if anybody has gleaned more information since his postings to
DECUSERVE as included on the VS0133 CD.

+-"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          |
| 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-Organization: Indiana University of Pennsylvania
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: NetMail%"NED@INNOSOFT.COM"
X-VMS-Cc: IN%"info-pmdf@ymir.claremont.edu"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 12 Sep 92 05:15:06 GMT
From:         "Mark_Strawcutter" <MJSTRAW@GROVE.IUP.EDU>
Subject:      RE: Digested lists and the Notes channel
Newsgroups: bit.listserv.pmdf-l

>There currently isn't any way of undigestifying messages before passing
>them to NOTES. I asked about this publicly when I originally developed
>the channel and the general repsonse was that undigestifying was Wrong
>and possibly even Evil.

Boy, I must have missed that discussion.  I couldn't disagree more.

>                        Since I'm not a VAX NOTES user I don't have any
>real opinion myself, so I elected not to provide such an option (I do have
>lots of other things to do...). I have since encountered (as expected)
>people who think such a thing would be nice to do, but too late for
>anything in V4.1. It is on the list for V4.2.

It really is a nice fit to VAXnotes.  The TOC at the beginning of the
digest becomes x.0 and each article is x.n.  If the whole digest was one
big note, if you wanted to look at article 15 you'd have to scroll down
thru all the preceeding text.  With it undigested you can "next reply"
thru quickly or count the TOC lines and go right to it.

----------
Mark J Strawcutter                           BitNet:    MJSTRAW@IUP
Director, Systems and Communications         DNS (mx):  mjstraw@grove.iup.edu
Indiana University of Pennsylvania           Voice:     (412) 357-4000
Indiana, PA   15705                          "you can't nail jello to a tree"
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"BOWMAN_BRETT_E@LILLY.COM"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 12 Sep 92 01:24:25 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Digested lists and the Notes channel
Newsgroups: bit.listserv.pmdf-l

There currently isn't any way of undigestifying messages before passing
them to NOTES. I asked about this publicly when I originally developed
the channel and the general repsonse was that undigestifying was Wrong
and possibly even Evil. Since I'm not a VAX NOTES user I don't have any
real opinion myself, so I elected not to provide such an option (I do have
lots of other things to do...). I have since encountered (as expected)
people who think such a thing would be nice to do, but too late for
anything in V4.1. It is on the list for V4.2.

If you saw the code necessary to do a good job of this you'd understand
why it is far from trivial. We're talking roughly 2000 lines of code
here to handle all the cases (MIME digest format plus all the older
formats). Fortunately this code exists in PMDF for other reasons; it is
only necessary to fit a bunch of calls into the NOTES channel to make
use of it.

                                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"
X-VMS-Cc: DPMSYS
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 6 Sep 92 07:00:46 GMT
From:         "Dave Mulvihill - Technical Support x-6993" <DPMSYS@RITVAX>
Subject:      Tracking down problem with PMDF-MR
Newsgroups: bit.listserv.pmdf-l


I keep getting OPCOM broadcasts such as the following from the PMDF symbiont:

%%%%%%%%%%%  OPCOM   4-SEP-1992 15:04:25.93  %%%%%%%%%%%
Message from user SYSTEM on VAXA
%PMDF-W-PRCSMBWRN, PMDF process symbiont non-fatal warning

%%%%%%%%%%%  OPCOM   4-SEP-1992 15:04:25.95  %%%%%%%%%%%
Message from user SYSTEM on VAXA
%PMDF-W-MRLSUBERR, Error submitting PMDF-MR master for local mailbox "MAILGATE",
    status = 178028674
-PMDF-E-HOST, Illegal host/domain in address "!AD"

Is this just the symbiont letting me know about every message returned due
to incorrectly formed To: address ?  Or is there an actual problem here?

Mail is not accumulating in the queue and I can't find any hard errors
in the log files for MR_LOCAL.  (debug and logging are on)  If its just
letting me know that its bouncing a particular message back due to incorrect
address, I rather not bother my operations staff with this.  Can I turn off
that particular broadcast?

Dave Mulvihill      (Postmaster)        Allin1: MULVIHILL DP
Systems Programmer                      Email:  dpmsys@ritvax.BITNET
Information Systems & Computing                 dpmsys@ritvax.isc.rit.edu
VAX/VMS, ULTRIX Technical Support
Rochester Institute of Technology, Rochester NY, 14623 (716) 475-6993
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Date-warning: Date header was inserted by NAUVAX.UCC.NAU.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Mon, 14 Sep 92 20:32:08 GMT
From:         Chris Michels <cvm@NAUVAX.UCC.NAU.EDU>
Subject:      Notifying POP3 users of new mail.
Newsgroups: bit.listserv.pmdf-l

I am trying to determine if the following is feasible and how to get PMDF to do
it.  We are running PMDF 4.1-?  and Multinet 3.1b.  We are using this machine
as a POP server for several PC users running FTP software's PC/TCP.  Every time
a message is delivered on the local channel, I would like to lookup the user it
is being delivered to in a table.  If the user is a PC POP user I would like to
use tcp/ip to send a message to his or her PC to inform the user that they have
new mail.

In PMDF 4.0 it seemed fairly simple to add this to MASTER.COM.  But with PMDF
4.1 I am not sure how or where to call the program that would send the message.
At the point that my program will be called I need to know the username of
the message recipient.  It would also be useful to also have the subject and
sender's address.  I could setup DELIVER for each user to run this program, but
that will add extra overhead to the process of delivering the message.  I would
prefer it be done in MASTER.COM.  Any suggestions?

--------------------------------------------------------------------------
Chris Michels -- Systems Programmer             cvm@nauvax.ucc.nau.edu
Northern Arizona University -- Flagstaff, AZ    cvm@nauvax.bitnet
Phone: (602) 523-6495                           N7YIU
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.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sun, 6 Sep 92 11:52:47 GMT
From:         Ned Freed <NED@INNOSOFT.COM>
Subject:      RE: Tracking down problem with PMDF-MR
Newsgroups: bit.listserv.pmdf-l

> I keep getting OPCOM broadcasts such as the following from the PMDF symbiont:

> %%%%%%%%%%%  OPCOM   4-SEP-1992 15:04:25.93  %%%%%%%%%%%
> Message from user SYSTEM on VAXA
> %PMDF-W-PRCSMBWRN, PMDF process symbiont non-fatal warning

> %%%%%%%%%%%  OPCOM   4-SEP-1992 15:04:25.95  %%%%%%%%%%%
> Message from user SYSTEM on VAXA
> %PMDF-W-MRLSUBERR, Error submitting PMDF-MR master for local mailbox "MAILGATE
   ",
>     status = 178028674
> -PMDF-E-HOST, Illegal host/domain in address "!AD"

This is an indication that the local mailbox name associated with your MR
notification mailbox does not match the name you told PMDF-MR was being used.
The mailbox name is specified via the user keyword on the mr_local channel. It
apparently isn't MAILGATE, so the symbiont doesn't know what channel the
notification request matches and therefore issues this error.

> Is this just the symbiont letting me know about every message returned due
> to incorrectly formed To: address ?  Or is there an actual problem here?

The symbiont has no knowledge of return message or anything like this.
This is a configuration problem.

> Mail is not accumulating in the queue and I can't find any hard errors
> in the log files for MR_LOCAL.  (debug and logging are on)  If its just
> letting me know that its bouncing a particular message back due to incorrect
> address, I rather not bother my operations staff with this.  Can I turn off
> that particular broadcast?

Your mail is not accumulating because the periodic job is taking care of
pending messages. You are not getting immediate processing of messages queued
to the PMDF-MR mailbox in Message Router.

This message indicates a problem that should be fixed and cannot be disabled.
You can always get rid of notification mailboxes if you don't need the
immediate processing.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Electronic Data Systems, Unigraphics Division, Cypress CA
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:         Mon, 14 Sep 92 06:24:32 GMT
From:         Harrison Spain <spain@MDCBBS.COM>
Subject:      I need a simple E-Mail to FAX solution
Newsgroups: bit.listserv.pmdf-l

We have PMDF and rely on it heavily to route all our mail from unix to VMS,
distribution lists, mail to the Internet via DECUS UUCP etc.  We are looking
for a FAX via E-Mail solution so we would love to consider the PMDF FAX
software.

Here is my problem.  We only run PMDF on a single node MAILER and only route
those mail messages through MAILER that *have* to.  Since installing PMDF on
every node is prohibitive, I'm not sure that the PMDF FAX solution is the right
way to go.

We would prefer to keep things *very* simple and each solution we see out there
is either way too complicated or requires that the software be installed on
each and every system.

Today we "borrow" a FAX solution (built into MR I think) that you can use by
sending your mail message to a single address (we define an address called
FAX), include the phone number(s) in the top of the mail message (the subject
can be anything), and off it goes.  What could be easier?

Help me figure out a way to make PMDF FAX as easy to use :-).

 |    Harrison Spain             |    Voice: (714) 952-6114                   |
 |    VMS Platform Manager       |      Fax: (714) 952-5758                   |
 |    EDS Unigraphics            |     UUCP: {uunet,uupsi}!mdcbbs!spain       |
 |    10824 Hope St.             |      PSI: PSI%31060099980018::SPAIN        |
 |    Cypress, CA  90630         | Internet: spain@mdcbbs.com                 |
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-type: MULTIPART/MIXED; BOUNDARY="Boundary (ID pe9VeG8h3Bj4hfGLRAwJlA)"
X-Mailer: Network Courier V2.1b
Date:         Sun, 13 Sep 92 18:20:42 GMT
From:         khatri@PCMAIL.INRE.ASU.EDU
Subject:      Question about TEST/REWRITE
Newsgroups: bit.listserv.pmdf-l


--Boundary (ID pe9VeG8h3Bj4hfGLRAwJlA)--
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"tkslen@ubvms.cc.buffalo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 9 Sep 92 05:56:06 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: GATES.RULES file does not look right.
Newsgroups: bit.listserv.pmdf-l

> As you can see it has multiple entries for each node.  Could I have answered
> one ...

Those multiple entries are indeed correct.  If you look carefully, you will
see that the multiple entries are not duplicates and do quite different things
depending upon the source of the address ($E$F -- envelope, forward pointing
address; $S..$Q -- fail of host not from source route, fail if not sending
to specified channel; etc.).

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