HDTenEightyP/NetNews huggingface dataset:
From: munroe@dmc.com (Dick Munroe)
Newsgroups: vmsnet.mail.mx
Subject: Rewriting of From lines...
Date: 25 Jan 93 10:06:55 EST
Organization: Doyle, Munroe Consultants, Inc., Hudson, MA

I have a customer who has noticed that MX (3.1C) modifies the From: lines of
his messages, e.g.,

        From: foo@bar.baz (Name)

turns into:

        From: <foo@bar.baz>
His specific complaint is that information is being lost in the translation,
the "(Name)" goes away.  I haven't poured over the RFCs enough to know if this
sort of rewriting is reasonable, but why would MX be rewriting the From:
portion of the envelope?  The other question is: should MX be preserving the
rest of the information in the line instead of just dropping it?
-- 
Dick Munroe				Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.		UUCP: ...uunet!thehulk!munroe
267 Cox St.				Office: (508) 568-1618
Hudson, Ma.				FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.
From: "Anthony J. Rzepela" <rzepela@hal.hahnemann.edu>
Newsgroups: vmsnet.mail.mx
Subject: Q: MX over DEC UCX 2.0 - summarize?
Date: Sun, 24 Jan 1993 02:40:30 EST
Organization: Mx-List<==>Vmsnet.Mail.Mx Gateway
X-Gateway-Source-Info: Mailing List

Hi all,

I read this list on a utility that currently has ~300 postings stored,
so I have done *some* checking, and I see questions about using MX over
specific TCP/IP packages, and I noted the following reply from Matt -

        >What tcp/ip packages does the current version of MX support?
               :
               :
    DEC VMS/ULTRIX Connection V1.2 and later
       (as of V2.0 called TCP/IP Services for VMS)
               :
               :

         -Matt

At our site, we are abandoning the recently abandoned CMU-Tek, with which
we successfully used MX 3.0 for more than a year.  Now we are on UCX 2.0
(CSLG license).  For the sole reason that we have published user manuals and
done training using MX, we do not want to abandon it as our VMS system mailer.

UCX, as of 2.0, ships with an SMTP<-->VAXMail interface, and unless someone can
warn me of a hidden hell with UCX' SMTP mail, the manuals/training thing
will remain the only reason.

Can someone answer:

* Do I have to use the MX SMTP server? Can't MX communicate with the UCX
  SMTP server?

* To test it, do I have to install from scratch? The MX CONFIG programs don't
  seem able to give me a working MX that will fly with UCX.

(NB: I *have* been trying different things, testing, and RTFMing.  I'm
not supplying excessive detail because I'm just looking for general
advice and/or warnings.)


From reading the docs, it seems to me that there should be a way to
just have MX handle the VMSMail interface, and let SMTP service, routing,
et al., be handled by UCX, but am I wrong?

This is not only for the sake of a few manuals, but also
compatibility with other University systems, so I can't exactly
just drop MX.

Any thoughts appreciated.
---------------------------------------------------------------------
Anthony Rzepela    <rzepela@cvi.hahnemann.edu>


Newsgroups: vmsnet.mail.misc
From: madison@tgv.com (Matt Madison)
Subject: Re: Mail-11 => SMTP gatewaying per RFC-1405
Reply-To: madison@tgv.com
Organization: The Foundation for Dinner Peas
Distribution: world,local
Date: Thu, 21 Jan 1993 20:04:13 GMT

In article <1993Jan21.110451.4275@arizona.edu>, leonard@telcom.arizona.edu (Aaron Leonard) writes:
>Today RFC-1405, "Mapping between X.400(1984/1988) and Mail-11
>(DECnet mail)" was published.  In section A3.2, "Mail-11 mapped in
>RFC822", this RFC recommends that Mail-11 => SMTP gatewayed
>addresses be rewritten as
>  "Mail-11-address"@gateway-address
>
>So that, in my example above, jones@frobbitz.com would have received
>the message from
>  "BUGS::LEONARD"@Gate.Arizona.EDU
>
>Would anyone care to comment on the desireability, or lack thereof,
>of changing our rewrite rule to comply with this aspect of RFC-1405?

The biggest reason NOT to do this is because most UNIX systems won't be able to deal with
that form of address.  The quotes often get stripped, leading to syntactically-invalid
addresses.

-Matt
--
Matthew Madison | madison@tgv.com    | +1 408 427 4366
TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
Newsgroups: vmsnet.mail.misc
Subject: Mail-11 => SMTP gatewaying per RFC-1405
From: leonard@telcom.arizona.edu (Aaron Leonard)
Date: 21 Jan 93 11:04:49 MST
Reply-To: Leonard@Arizona.EDU
Distribution: world,local
Organization: University of Arizona Telecommunications

We operate an e-mail gateway that relays mail between
Mail-11 (DECnet) and SMTP (among others.)  (Our gateway
runs PMDF on a VMS platorm.) 

Let's say that our gateway has a DECnet nodename of
GATE and an Internet domain name of Gate.Arizona.EDU.
When a mail message is sent via Mail-11 thru our gateway 
to an SMTP destination, we rewrite its From: address
as USER%Host.DECnet@Gate.Arizona.EDU.  For example, if Mail-11
user BUGS::LEONARD uses our gateway to send mail to
SMTP user <jones@frobbitz.com>, he'll address his message
to
  GATE::IN%"jones@frobbitz.com"
The SMTP user will receive this message with a From: address of
  LEONARD%BUGS.DECnet@Gate.Arizona.EDU

This approach works well.

Today RFC-1405, "Mapping between X.400(1984/1988) and Mail-11
(DECnet mail)" was published.  In section A3.2, "Mail-11 mapped in
RFC822", this RFC recommends that Mail-11 => SMTP gatewayed
addresses be rewritten as
  "Mail-11-address"@gateway-address

So that, in my example above, jones@frobbitz.com would have received
the message from
  "BUGS::LEONARD"@Gate.Arizona.EDU

Would anyone care to comment on the desireability, or lack thereof,
of changing our rewrite rule to comply with this aspect of RFC-1405?

Aaron

Aaron Leonard (AL104), <Leonard@Arizona.EDU>
University of Arizona Network Operations, Tucson AZ 85721
Newsgroups: vmsnet.mail.pmdf
Subject: REF: Re: NOTES channel and FWD:
From: Kim Wohlert erik mainz a/s <kw@skade.mainz.dk>
Date: 25 Jan 1993 15:03:29 +0000 (WET)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 15:03:29 +0000 (WET)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXBONST769D4BDF@INNOSOFT.COM>
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

>> 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
Newsgroups: vmsnet.mail.pmdf
Subject: Lost header lines in BSMTP bounce?
From: John Payne <payne%ithaca.bitnet@ymir.claremont.edu>
Date: 25 Jan 1993 12:58:32 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 12:58:32 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXJWZW1C28ZFHWN@YMIR.CLAREMONT.EDU>
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

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.
Newsgroups: vmsnet.mail.pmdf
Subject: RE: WordPerfect Office 3.1
From: "McMahon,Brian D" <mcmahon%grin1.bitnet@ymir.claremont.edu>
Date: 25 Jan 1993 09:09:23 -0500 (cdt)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 09:09:23 -0500 (cdt)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXE1QVWKI8ZF23Z@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> > We've been looking into purchasing WP Office 3.1 and one of our questions
> > is how/if this will interface with PMDF (4.1-7).  Whilst I wade through
> > the WP Office manuals I thought I'd see if anyone has any input on the
> > viability of this idea.
>
> If you're referring to the VMS implementation, there is a foreign protocol
> interface to VMS MAIL that PMDF can talk to. This interface does work, but
> a fair amount of richness is lost (attachments, formatting, etc.).

If you feel like spending {money|time|hair off your head}, you might also
check into the Messy Router Gateway for WP Office.  It might help with some
of the formatting problems.  We do not run WP Office, so I will make no
guarantees.  Caveat emptor.

Brian McMahon (BDM13)    <MCMAHON@GRIN1.BITNET>    <MCMAHON@AC.GRIN.EDU>
Postmaster / Acad. Software Support   Grinnell College Computer Services
Grinnell, Iowa 50112 USA   Voice: +1 515 269 4901   Fax: +1 515 269 4936
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Trying to use  *** DELIVER ***
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 22 Jan 1993 17:22:41 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 22 Jan 1993 17:22:41 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTTSKTPB8I8ZF7G1@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"csc_ted@uhdvx3.dt.uh.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> I have set up the PMDF DELIVER (4.0) the way the manual describes.
> a. Set forward to in%"~csc_test"

Actually there's a typo in the 4.0 manual; this should be "in%""~csc_test""".
However, that's not the only problem here.

> b. set the USE_

Dunno how to interpret this.

> String copied: "%MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4"
> Error message: "%MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4"
> MAIL_IO_WRITE returning.
> %MAIL-E-SENDERR, error sending to user CSC_TEST at UHDVX4
> MAIL_IO_WRITE called.
>TOP_OF_STACK called.
>  returning       ERROR_MSG
> Error text.
>copy_descr_to_vstring called.
> String copied: "%MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as
>  output"
> Error message: "%MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as
>  output"
> MAIL_IO_WRITE returning.
> %MAIL-E-OPENOUT, error opening SYS$USERS:[000000]TEST.DIR as output
> MAIL_IO_WRITE called.
> TOP_OF_STACK called.
> returning       ERROR_MSG
> Error text.
> copy_descr_to_vstring called.
>String copied: "-RMS-E-PRV, insufficient privilege or file protection violation"
> Error message: "-RMS-E-PRV, insufficient privilege or file protection violation"
> MAIL_IO_WRITE returning.
> -RMS-E-PRV, insufficient privilege or file protection violation

PMDF is merely using VMS MAIL to deliver mail to this user.  (It's not using
DELIVER since the forwarding address was not correct.)  VMS MAIL is having a
problem doing the delivery; it's VMS MAIL which is reporting these errors. You
need to first get delivery to this address working via vanilla VMS MAIL from a
non-privileged account.

It looks like the mail was sent to in%"csc_ted@dt3.dt.uh.edu" which was
forwarded to csc_test@uhdvx4 which translated to UHDVX4::CSC_TEST.  So, you
need to get mail to UHDVX4::CSC_TEST working (from vanilla VMS MAIL,
unprivileged account) first.  Then also fix the forwarding address
("in%""~...""").

Dan
From: j.lance Wilkinson, 814-865-1818
Newsgroups: vmsnet.mail.pmdf
Subject: Looking for VMS-based X.500 Client Software
Date: 26 Jan 93 22:06:00 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Jan 1993 17:06 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: IPMDF%PSULIAS.BITNET@ymir.claremont.edu
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTZ6YG2KV68ZFTL0@YMIR.CLAREMONT.EDU>
X-Organization: Penn State University / University Libraries
X-Vms-To: INFO_VAX
X-Vms-Cc: IPMDF
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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."-------+
Newsgroups: vmsnet.mail.pmdf
Subject: %STR-F-INSVIRMEM error using Process Symbiont
From: Jack Pernice <pern@db1.cc.rochester.edu>
Date: 21 Jan 1993 14:02:45 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Jan 1993 14:02:45 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTS0Y26FJM8ZEVEM@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"IPMDF@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


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
Newsgroups: vmsnet.mail.pmdf
Subject: Trouble reaching UNC?
From: skipper%medcolpa.bitnet@ymir.claremont.edu
Date: 25 Jan 1993 10:26:15 -0500
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 10:26:15 -0500
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXEN9XASY8ZFH22@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Newsgroups: vmsnet.mail.pmdf
Subject: RE:  trying to reach a Bitnet address
From: John C Klensin <klensin@infoods.mit.edu>
Date: 27 Jan 1993 12:48:13 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 27 Jan 1993 12:48:13 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GU0C6OJOHE8ZG1EF@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ANNA%clarku.bitnet@MITVMA.MIT.EDU"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Mail-System-Version: <MultiNet-MM(335)+TOPSLIB(156)+PMDF(4.2)@INFOODS.UNU.EDU>

>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?

Idiots!

Anna,
  Fixing this is a two-step process and I would strongly encourage you
to take both steps.

(1) Either edit the xmailer.nodes file to replace :net.EARN with
:net.BITNET globally before using it or (I suspect this will work, but
am not sure) go into your PMDF.CNF file and insert a rewrite rule to
change any occurrences of string.EARN it encounters into string.BITNET.

I would recommend checking the xmailer.nodes to be sure that it doesn't
contain such bogons as net.GULFNET also; if so, you will need to patch
those too.

(2) Figure out your xmailer.nodes file is coming from.  If it is a copy
of BITNIC's XMAILER NAMES, send, or have your BITREP send (if you are
not that person) a strong note to CREN protesting changes in the content
and semantics of these key files without consultation and approval (or
at least advanced warning) to members.

It might be worthwhile pointing out that this sort of thing doesn't
inspire institutional conviction that CREN dues are worth paying if
there are other options (see the last few days of flaming on FUTURE-L
for the context of that remark).

  john
Newsgroups: vmsnet.mail.pmdf
Subject: trying to reach a Bitnet address
From: "Anna Tomecka, x7733" <anna%clarku.bitnet@ymir.claremont.edu>
Date: 27 Jan 1993 11:15 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 27 Jan 1993 11:15 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GU0921Q0KY8ZFZB5@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.bitnet"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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
Newsgroups: vmsnet.mail.pmdf
Subject: RE: WordPerfect Office 3.1
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 24 Jan 1993 12:52:41 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 24 Jan 1993 12:52:41 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTWBW2X5EQ8ZEYJZ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"AL@mom.spie.org"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> We've been looking into purchasing WP Office 3.1 and one of our questions
> is how/if this will interface with PMDF (4.1-7).  Whilst I wade through
> the WP Office manuals I thought I'd see if anyone has any input on the
> viability of this idea.

If you're referring to the VMS implementation, there is a foreign protocol
interface to VMS MAIL that PMDF can talk to. This interface does work, but
a fair amount of richness is lost (attachments, formatting, etc.).
Unfortunately, there is no API we can use to build our own interface on
VMS.

WP Office on PCs doesn't have either the VMS MAIL interface or an API, but
there is hope since the next release of the product is supposed to have an API.
We are already involved in building a gateway using this interface.
I don't know if this API will be available on VMS; I doubt it. There may
eventually be some other API on VMS; we'll just have to wait for WPCorp to
figure out what they are doing in this area before we'll be able to do
anything.

				Ned