HDTenEightyP/NetNews huggingface dataset:
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"AE@AC.DAL.CA"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 1 Oct 92 05:49:29 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: MAILSERV mailing list distribution file format
Newsgroups: bit.listserv.pmdf-l


>   The PMDF System Manager's Guide (May 1992) says in 11.6.2.3, the first
> paragraph (page 11-16) "the mailing list distribution file has the same format
> as the alias file, see also section 3.3".

The intended meaning of that sentence is

    ... the mailing list distribution file has the same format as the mailing
    lists used by the alias file.  See Section 3.3.2.2

I've reworded the documentation so as to avoid further confusion.

>   I have a user with a mailing list who would like people who do a SEND/LIST
> to see the real names of subscribers to the list as well as their addresses.
> Is this possible?  I have tried
>
>       SUBSCRIBE listname xxx (comment)
>       SUBSCRIBE listname "something" <xxx@yyy>
>
> and these show up in the file as
>
>       XXX (COMMENT) (subscribed by ...)
>       "something" <XXX@YYY> (subscribed by ...)
>
> I guess what I'm really asking is, when the SUBSCRIBE documentation says
>
>       SUBSCRIBE list-name [address]
>
> can "address" be anything that's allowed on an RFC-822 "To:" line or a liberal
> subset thereof?

You may use any legal RFC 822 address.  So yes, comments and personal name
fields may be used in an address in the address part of a SUBSCRIBE command.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"NED@SIGURD.INNOSOFT.COM"
X-VMS-Cc: ipmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 2 Oct 92 07:00:01 GMT
Comments:     Warning -- original Sender: tag was E7OPDAN@TOE.TOWSON.EDU
From:         Dan@TOE.TOWSON.EDU
Subject:      RE: no headers and stuck in queue
Newsgroups: bit.listserv.pmdf-l

>There are all sorts of reasons why a delivery job might abort, leaving a
>message that only gets picked up by the periodic job. You'll have to track this
>down on a case by case basis; there are simply too many possibilities to
>consider otherwise. It is important to know where the messages are coming from
>as well as where they are going.

>Since messages in the BIT_GATEWAY queue never come from VMS MAIL under normal
>circumstances, this is not likely to a problem with VMS MAIL.

I'll keep my eye on it and look a little more closely at the files which are
queued.

>Does your INFOREP use DELIVER? This and the headeromit keyword is the only
>way to get this effect out of PMDF. If neither of these is involved I suspect
>the mail is coming from something other than PMDF.

My INFOREP does not use DELIVER and I have headerbottom on the local channel.
The problem is not consistent.  In most cases, she does get the headers.  If I
am only running DECnet (VMS 5.4-3), Jnet 3.5, UCX 1.3-7(A?) and PMDF 4.1-6 what,

other than PMDF with the BN_SLAVE process, could be delivering the mail.  No
other user seems to have this problem (though that doesn't necessarily mean it
doesn't happen).

Thanks.

Dan

   Daniel A. Dinkin
   Network Services Manager                   BITNET: dan@towsonvx.bitnet
   IR Academic Computing                    Internet: dan@toe.towson.edu
   Towson State University                            dan@midget.towson.edu
   Towson, Maryland 21204                UMSA DECnet: toe::e7opdan
   (410)830-3320

     Any thoughts in this message are purely random and my employer had
           nothing to do with them... especially if I was right.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"tkslen@ubvmsb.cc.buffalo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 6 Oct 92 05:24:22 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: REPOST (for lack of any answer) Problems with % addressing.
Newsgroups: bit.listserv.pmdf-l

As far as I know this is the first time this message has appeared on
info-pmdf.

In answer to your question, there is no way for PMDF to check the validity
of what appears as a node name. These things can be logical names, they can
be internal names, and they can potentially be entries in the DNS (DEC's, not
Internet). The exact rules for checking them are in a constant state of flux
and it simply isn't reasonable for us to try to validate them.

As for the illegal device error, it is returned in a variety of situations,
including several which correspond to "network unavailable" errors. It is
therefore classified as a temporary failure, since no additional information
is available.

I have tried to write code to implement such checking three times now and I
have hit a brick wall of one sort or another every time. I will continue to
try, however, and once VMS provides the requisite level of service (I have
high hopes for SYS$IPC) we'll look into doing our own checking again.

                                Ned
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"martinea@ireq.hydro.qc.ca"
X-VMS-Cc: info-pmdf
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 1 Oct 92 10:20:13 GMT
From:         "Kevin V. Carosso" <KVC@SUMMER.INNOSOFT.COM>
Subject:      RE: Summary: Mail system to use with PathWorks
Newsgroups: bit.listserv.pmdf-l

> I am looking at Microsoft mail for internal use but I also need a gateway
> to VMSmail. Is there such a thing?

The simplest solution is probably to use an SMTP capable mailer on VMS
such as PMDF and a MS MAIL to SMTP gateway.  If you are referring to MS MAIL
on the Mac then you can get a gateway from a company called Star*Nine or
Cayman.  They are actually the same product, Cayman repackaged Star*Nine's
code.  If you mean MS MAIL on PC (a completely different package from their
Mac system) then you can get an SMTP gateway from Microsoft themselves.

If you need details on how to contact Star*Nine let me know and I'll dig up
the phone number when I'm in the office.

        /Kevin Carosso
         Innosoft
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Return-path: uucp@mccall.UUCP
Errors-to: epmdf@YMIR.BITNET
Organization: Inland Steel Company; East Chicago, IN
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:         Fri, 2 Oct 92 11:12:03 GMT
From:         Tom Allebrandi <allebrandi@INLAND.COM>
Subject:      RE: Summary: Mail system to use with PathWorks
Newsgroups: bit.listserv.pmdf-l

In article <BvE5JC.2p4@ireq.hydro.qc.ca>, martinea@ireq.hydro.qc.ca (Alain
 Martineau) writes:
>       I am looking at Microsoft mail for internal use but I also need a gatewa
   y to
> VMSmail. Is there such a thing ?
> thanks.

If you ask Microsoft, they will tell you to get their X.400 gateway.
The problem with that is that I believe you then need Message Router
and MRGATE to move the X.400 mail to and from VMSmail. (If I am wrong
about this please correct me!)

As luck would have it, I am currently designing an MS Mail <-> VMSmail
gateway for our company. We hope to go straight to the MS Mail Post
Office via the Application Programming Interface (API).

I don't yet know if the gateway, presuming that we build it, will
be available outside of our Company. Drop me a mail message in
a few weeks when I should know more.

--- Tom
Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"tkslen@ubvmsb.cc.buffalo.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 6 Oct 92 06:44:26 GMT
From:         Ned Freed <NED@SIGURD.INNOSOFT.COM>
Subject:      RE: REPOST (for lack of any answer) performance problem with
              local channel
Newsgroups: bit.listserv.pmdf-l

>   A) Does anyone have any suggestions on what I could do to improve my local
>      queue's performance?

There were major improvements in local channel processing in V4.1. Every test I
have been able to run has shown that things improved, sometimes by a factor of
five or more.

For this reason I can only conclude that you have some sort of site-specific
bottleneck that is causing trouble. It is quite possible that V4.1 has a very
different resource utilization mix than V4.0. For example, the simple fact that
you can now have many more jobs hitting on a single mail file a lot faster may
cause bottlenecks in the delivery processing inside of VMS MAIL. I have seen
this happen here -- there are situations where some sort of deadlock develops
on a single mail file that require waiting until something times out and lets
processing continue. And it is quite possible this is aggravated by the
improved throughput of PMDF V4.1.

Insofar as courses of action go, there isn't much I can suggest here except to
analyze what resources are being used using whatever tools you have available.
Since I don't have any way of knowing what you have handy I cannot suggest
anything more specific than that.

If you want to try the stab-in-the-dark approach, you can always fiddle around
with the FDL file for QUEUE_CACHE.DAT. Something like more global buffers might
help, but it is just a complete stab in the dark. The recommended approach is
to evaluate performance using appropriate tools for such exercises.

>  B) Why do I still see some files get left behind (as I explained in #4)?

It is probably caused by something that cannot poke its entries into the
queue cache. This could well be a quota or privilege problem somewhere. As I
have described many times on this list, the thing to do is to find out what
is generating the stuck entries (where they are going is unimportant) and
check that environment very carefully to see if it is properly set up. It
is possible to enable various sorts of logging for this in PMDF, but until I
know the source of these jobs I cannot suggest a next step.

>  C) Why doesn't a BIT_GATEWAY job get started by POST.COM when there are
>     messages waiting to be delivered?

This is also indicative of a privilege or quota problem. These jobs almost
always originate from the BN_SLAVE process running under Jnet, so that is the
environment that needs to be checked. In this particular case setting
slave_debug on the bit_local channel and OS_DEBUG to 1 in the PMDF option file
should give you enough logging to figure out what is or isn't happening.

                                Ned
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:         Mon, 5 Oct 92 04:59:07 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: Disappearing FAX message pages
Newsgroups: bit.listserv.pmdf-l

> I'm not sure what I did to make this happen, but I've broken our
> ps_to_g3 channel in a strange way.  No error messages are generated,
> but FAXes go out with a cover page only, and with no attached pages.
> [The cover page correctly advertises ``1 page, including this one'',
> but I don't know why there are not attached message pages.]
>
> I just sent a one line message to our text.fax domain address.  It
> produced a PostScript msg which was then processed by the ps_to_g3
> channel, whose log file contained:
>
>> Initializing PostScript interpreter for message body processing.
>> PostScript interpreter initialized.
>> Initializing the G3 file.
>> G3 file initialized.
>> Processing message body.
>> Invoking the PostScript interpreter to process the message body.
>> Message body processing completed.

Try enabling both master_debug and slave_debug for the channel and then look at
the debugging output.  (I cannot tell from this portion of the log file if you
had both enabled or not.)

When both master_ and slave_debug are enabled, every line read from the message
body and fed to the PostScript interpreter will be logged.  If you see nothing
logged for message body processing, then the message body was most likely
empty.  (What did the message body look like in the PS_TO_G3 channel queue
before the channel ran?)

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"KWOLTERS@LUCY.WELLESLEY.EDU"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Fri, 2 Oct 92 10:10:10 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject:      RE: PMDF on a cluster
Newsgroups: bit.listserv.pmdf-l

> Hi.  I apologize if this is a stupid question, but
> What special considerations (if any) need to be
> taken when running PMDF on a cluster.  We have
> been running V3.2 on a single machine for a
> while and are now setting up a cluster.  I did
> not see anything in the System Manager's Guide
> discussing it.

While not an exhaustive list, here's some of the considerations:

(1) You need a PMDF directory tree per "homogeneous" cluster where homogeneous
    means same SYSUAF.DAT & VMSMAIL_PROFILE.DATA.  Within a homogeneous cluster
    you can use a single PMDF directory tree and configuration file.  You
    might consider re-running PMDF_ROOT:[EXE]CONFIGURE.COM and in the fifth
    part, when it asks "include other cluster members", answer YES.

(2) You can make MAIL$BATCH a generic queue which feeds specific queues on
    specific cluster members.  However, if you only have certain resources
    available on a strict subset of the cluster (e.g., Jnet only on one node)
    then you need to restrict the applicable channels (e.g., bit_ channels)
    to only process on a batch queue on that node.  This is done with the
    "queue" channel keyword.  (Actually, for BITNET you set the bitnet_queue
    symbol in BITNET_DOMAINS_DRIVER.COM and re-run that command procedure.)

(3) You should execute SYS$STARTUP:PMDF_STARTUP.COM on all (licensed) cluster
    members.  You only need to run SYS$STARTUP:PMDF_SUBMIT_JOBS on one machine
    if you use a generic MAIL$BATCH queue, or, if you do not use a generic
    batch queue, then you should run it on the node where MAIL$BATCH is
    processed.  (This isn't crucial.)

(4) If you use a compiled configuration, then when you recompile it you must
    be sure to re-install it on all cluster members.

Dan
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
Organization: Duke University Medical Center, Durham NC, USA
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: DMPM,IN%"ipmdf@ymir"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Wed, 30 Sep 92 16:08:19 GMT
From:         "James Dryfoos - Postmaster" <DMPM@DUKEMC>
Subject: Multiple addresses in reply_to field. How does PMDF handle for
              VMS mail.
Newsgroups: bit.listserv.pmdf-l

If I am correct, PMDF will use the Reply_to field over the from field
to setup the actual from field in VMS mail (when delivering to local system).
What happens when there are multiple addresses such as below?

Reply-to: vitale@athena.cas.vanderbilt.edu, LIBJCW@SUVM.BITNET,
 EBLEN@TWU.BITNET, Philip.A.Thompsen@m.cc.utah.edu, BESANCON@USMCP6.BITNET

-Jim

   =======================================================================
      James D. Dryfoos -- Postmaster    |  dmpm@mc.duke.edu
      Duke University Medical Center    |  dmpm@dukemc.bitnet
      Box 2914 DUMC                     |  (919) 684-6421 - office
      Durham, NC 27710 Earth            |  (919) 684-8675 - fax
   =======================================================================

Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"DMPM%DUKEMC.BITNET@ymir.claremont.edu"
X-VMS-Cc: IPMDF
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Thu, 1 Oct 92 03:44:38 GMT
From:         "Daniel C. Newman" <DAN@INNOSOFT.COM>
Subject: RE: Multiple addresses in reply_to field. How does PMDF handle
              for VMS mail.
Newsgroups: bit.listserv.pmdf-l

> If I am correct, PMDF will use the Reply_to field over the from field
> to setup the actual from field in VMS mail (when delivering to local system).
> What happens when there are multiple addresses such as below?
>
> Reply-to: vitale@athena.cas.vanderbilt.edu, LIBJCW@SUVM.BITNET,
>  EBLEN@TWU.BITNET, Philip.A.Thompsen@m.cc.utah.edu, BESANCON@USMCP6.BITNET

     Give it a try with PMDF SEND.  Create a file containing a message header
with this Reply-to: header line and then send yourself a message using that
file and PMDF SEND's /HEADER qualifier:

  $ create msg.hdr
  Reply-to: vitale@athena.cas.vanderbilt.edu, LIBJCW@SUVM.BITNET,
   EBLEN@TWU.BITNET, Philip.A.Thompsen@m.cc.utah.edu, BESANCON@USMCP6.BITNET
  ^Z
  $ PMDF SEND/HEADER msg.hdr dmpm

     Note that the syntax for a Reply-to: header line is

  Reply-to: 1#address

which means that there must be at least one address.  Thus, there may indeed
be several addresses in a Reply-to: header line.

    PMDF, if there is no Resent-reply-to: or Resent-from: header lines, will
stuff all of the Reply-to: addresses into the VMS MAIL From: line.  VMS MAIL
doesn't mind and there is no where else to put them.  (Using the VMS MAIL CC:
line would be improper.)  Now, of course, if you REPLY to such a message from
within VMS MAIL, VMS MAIL will only use the first address appearing in the VMS
MAIL From: line.  This is just another facet of VMS MAIL's lack of a REPLY/ALL
command.

Dan
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%"NED@SIGURD.INNOSOFT.COM"
X-VMS-Cc: IN%"info-pmdf@innosoft.com",TINKELMAN
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Tue, 29 Sep 92 21:44:17 GMT
From:         Bob Tinkelman <bob@CAMB.COM>
Subject:      RE: DELIVER to NEWMAIL folder
Newsgroups: bit.listserv.pmdf-l

> The problem with FOLDER seems to indicate that FOLDER is not installed with
> enough privileges to properly set the From: address. I cannot duplicate the
> problem here. But several bugs in FOLDER have been fixed recently, and so have
> a bunch of bugs in VMS MAIL that relate to privilege checking (this is in VMS
> V5.5-2), so there may well be an unrelated fix (in either PMDF or VMS) that
> has corrected this.

The problem was that FOLDER wasn't installed.  I'd apparently made an
editing error when editing pmdfimage.dat after the most recent installation.
My error.  Thanks for the pointer.

Which (again) brings up what I consider to be a minor itch in the install
process, the editing of pmdfimage.dat.  I always edit pmdfimage.dat to
comment out the lines that are needed only for the old stand-alone DELIVER,
and to uncomment the line related to FORWARD.  Would it be possible for the
install procedure to look at the old version of pmdfimage.dat and see which
images were installed, and which weren't, and use that in generating the new
pmdfimage.dat?

Thanks - Bob
From: tkslen@UBVMSB.CC.BUFFALO.EDU
Newsgroups: bit.listserv.pmdf-l
Subject: REPOST (for lack of any answer) Problems with % addressing.
Date: 6 Oct 92 08:26:30 GMT
Organization: University at Buffalo
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 NETNEWS@AMERICAN.EDU

Every so often I find a mail message in my local queue addressed to:

user%node  where "node" is greater than seven characters
(e.g. joe%abcdefgh)
   or
user%node.decnet  where "node" is less than seven characters
(e.g. joe%abc.decnet)

I know addressing like this is frowned upon, but since pmdf will still accept
it I feel this problem should be resolved.  Reading the manual tells me that
if pmdf can't rewrite the address then it will treat the address as
user%node@localhost.  The only problem with this is, if "node" is not a valid
decnet nodename then vms can give strange error messages.  For example,

$ set ho node.decnet
%RMS-F-SYN, file specification syntax error
$ set host s.s
%RMS-F-SYN, file specification syntax error
$ set ho abcdefg
%SYSTEM-F-NOSUCHNODE, remote node is unknown
$ set ho abcdefgh
%RMS-F-NOD, error in node name

When I look at one of the L_MASTER.LOG files I find the following error
when trying to deliver either style of nodename address"

%MAIL-E-LOGLINK, error creating network link to node ABC.DECNET
-SYSTEM-F-IVDEVNAM, invalid device name
or
%MAIL-E-LOGLINK, error creating network link to node ABCDEFGH
-SYSTEM-F-IVDEVNAM, invalid device name

As you can see, mail thinks these wierd addresses are a device name.
Is there anyway pmdf can check the validity of the nodename?

Thanks,
  Lenny Miceli
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: University at Buffalo
X-Envelope-to: pmdf-l@irlearn.BITNET
X-VMS-To: IN%"pmdf-l@irlearn"
X-VMS-Cc: TKSLEN
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Date:         Fri, 2 Oct 92 04:51:26 GMT
From:         TKSLEN@UBVMS
Subject:      Problems with % addressing.
Newsgroups: bit.listserv.pmdf-l

Every so often I find a mail message in my local queue addressed to:

user%node  where "node" is greater than seven characters
(e.g. joe%abcdefgh)
   or
user%node.decnet  where "node" is less than seven characters
(e.g. joe%abc.decnet)

I know addressing like this is frowned upon, but since pmdf will still accept
it I feel this problem should be resolved.  Reading the manual tells me that
if pmdf can't rewrite the address then it will treat the address as
user%node@localhost.  The only problem with this is, if "node" is not a valid
decnet nodename then vms can give strange error messages.  For example,

$ set ho node.decnet
%RMS-F-SYN, file specification syntax error
$ set host s.s
%RMS-F-SYN, file specification syntax error
$ set ho abcdefg
%SYSTEM-F-NOSUCHNODE, remote node is unknown
$ set ho abcdefgh
%RMS-F-NOD, error in node name

When I look at one of the L_MASTER.LOG files I find the following error
when trying to deliver either style of nodename address"

%MAIL-E-LOGLINK, error creating network link to node ABC.DECNET
-SYSTEM-F-IVDEVNAM, invalid device name
or
%MAIL-E-LOGLINK, error creating network link to node ABCDEFGH
-SYSTEM-F-IVDEVNAM, invalid device name

As you can see, mail thinks these wierd addresses are a device name.
Is there anyway pmdf can check the validity of the nodename?

Thanks,
  Lenny Miceli