HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF to/from MRGATE & MR (NO PMDF_MR)
From: sysprgd@roads.sa.gov.au
Date: 21 Jan 93 15:14:40 CST
Organization: DEPARTMENT of ROAD TRANSPORT


I am looking for a quick/simple(?) method to handle mail between PMDF on one
node of a non-homogeneous cluster and DEC's MRGATE and All-in-1 Mail (not IOS) 
based on another node of the cluster.

The main difficulty I face (until I can relocate the MR component to the node
with PMDf and install PMDF-MR [hooray! but not in the shorter term...]) is the 
rewriting of the from addresses of the mail entering PMDF from MRGATE. The 
from address typically looks like

	"RTWKV::MRGATE::\"AM::SYSPRGD\""@Roads.SA.Gov.AU

when it reaches it's destination. 
RTWKV = cluster alias
AM = All-in-1 Mail MR mailbox

I would have thought the best method would be to attempt to rewrite the from 
address to something more like

		sysprgd@mrgate.Roads.SA.Gov.AU

which is then easy to handle on the incoming side.

Any examples, ideas or suggestions more than welcome!!

Thanks,

	Mike.
_______________________________________________________________________________
	Mike de Laine
	Email:	mike@roads.sa.gov.au Phone: +61 8 343 2469 Fax: +61 8 343 2768 
___   ___  ___  ___   ___  ___  ___  ___  ___  ___  ___  ___  ___  ___ ___  ___
	Post :	Dept. of Road Transport, Information Technology,
		PO Box 1, Walkerville, South Australia, 5081.
_______________________________________________________________________________
Newsgroups: vmsnet.mail.pmdf
Subject: RE: NOTES channel and FWD:
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 22 Jan 1993 13:36:52 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 22 Jan 1993 13:36:52 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTTKQ2JDN68ZDW7Q@INNOSOFT.COM>
X-Vms-To: IN%"bob@camb.com"  "Bob Tinkelman"
X-Vms-Cc: IN%"ipmdf@INNOSOFT.COM"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> 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
Newsgroups: vmsnet.mail.pmdf
Subject: RE: %STR-F-INSVIRMEM error using Process Symbiont
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 21 Jan 1993 11:44:58 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Jan 1993 11:44:58 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTS2TR28N68ZEW4E@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"PERN@db1.cc.rochester.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

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

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF v4.1 installation
From: "j.lance Wilkinson, 814-865-1818"
Date: 25 Jan 1993 15:32 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 15:32 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXPLMT6YA8ZFHXF@YMIR.CLAREMONT.EDU>
X-Organization: Penn State University / University Libraries
X-Vms-To: IPMDF
X-Vms-Cc: JLW
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

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

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

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

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

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

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

+-"Never Underestimate the bandwidth of a station wagon full of mag tapes"--+
| J.Lance Wilkinson ("Lance")            BitNet:    JLW@PSULIAS.BITNET      |
| Systems Design Specialist - Lead       InterNet:  JLW@PSULIAS.PSU.EDU     |
| Library Computing Services         AT&T:(814) 865-1818 FAX:(814)863-3560  |
| E8 Pattee Library                      "I'd rather be dancing..."         |
| Penn State University         A host is a host from coast to coast,       |
| University Park, PA 16802     And no one will talk to a host that's close |
| <POSTMAST@PSULIAS.BITNET>     Unless the host that isn't close            |
| <POSTMAST@PSUCES.BITNET>      Is busy, hung or dead.                      |
+------"He's dead, Jim. I'll get his tricorder. You take his wallet."-------+
Newsgroups: vmsnet.mail.pmdf
Subject: RE: WordPerfect Office 3.1
From: Lori Gavin <gavinl1@jaguar.uofs.edu>
Date: 22 Jan 1993 10:57:06 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 22 Jan 1993 10:57:06 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTT8QRTP768ZEXYR@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


We run WP Office and PMDF together and they work great.  (I assume you are
getting the VMS version of office.)  Office has a vmsmail gateway that works
well, but the smtp agent (with Multinet) was not delivering mail into Office
correctly.  PMDF was the missing peice we needed, and now we have mail from
Office to the intenet and back again with no problems.

                   Lori
                                              UUUUUU         UUUUUU
 ----------------------------------            UUUU           UUUU
|  Lori Gavin                      |           UUUU       SSSSSSSSSSSSSSS
|  VAX System Manager              |           UUUU      SSSSSSSSSSSSSSSSS
|  University of Scranton          |           UUUU      SSSS UUUU     SSSS
|                                  |           UUUU      SSSS UUUU
|                                  |           UUUU      SSSSSSSSSSSSSSSSS
|INTERNET: GAVINL1@JAGUAR.UOFS.EDU |           UUUUUUUUUUUSSSSSSSSSSSSSSSSS
|   Phone: (717)941-6133           |            UUUUUUUUUUUUUUUUU      SSSS
 ----------------------------------                      SSSS          SSSS
                                                         SSSSSSSSSSSSSSSSSS
                                                          SSSSSSSSSSSSSSSS


SYS$LOGIN:SIGNATURE.TXT
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Lost header lines in BSMTP bounce?
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 25 Jan 1993 11:16:16 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 11:16:16 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@SIGURD.INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTXMOJRO8I95MPWF@SIGURD.INNOSOFT.COM>
X-Vms-To: IN%"PAYNE%ITHACA.BITNET@YMIR.CLAREMONT.EDU"  "John Payne"
X-Vms-Cc: IN%"ipmdf@SIGURD.INNOSOFT.COM"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

This is an old bug (it happened in PMDF V4.0 as well) that will be fixed
in the next release. It isn't patchable; fixing it required rewriting most
of the BSMTP handling code from scratch.

				Ned
From: perkins@ksuvxa.kent.edu (John Emanuel Perkins)
Newsgroups: vmsnet.mail.pmdf
Subject: Pmdf 4.1 / J-Net 3.6:  What changes need to be made to.......
Date: 26 Jan 93 12:51:39 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Jan 1993 08:51:39 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTYWT61ZKI8ZFCDA@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"service@innosoft.com"
X-Vms-Cc: IN%"info-pmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


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

Given the senario:

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

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

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

Thanks in advance for any assistance!

John Perkins

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

perkins@kentvms         (BITNET)
ksuvxa::perkins         (DECNET)
perkins@ksuvxa.kent.edu (Internet)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Trouble reaching UNC?
From: Ned Freed <ned@sigurd.innosoft.com>
Date: 25 Jan 1993 17:46:11 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 25 Jan 1993 17:46:11 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTY0F05K028ZFLNG@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SKIPPER@MEDCOLPA.BITNET"
X-Vms-Cc: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

I don't understand what you mean by "invalid domain" here. If you mean that
PMDF is giving you this error, then your configuration is busted. UNC is a
perfectly valid BITNET system; its table entry is correct and all of that.

If you're getting some message back from UNC with this in it, then they're
the ones with the problem, not you. I would recommend contacting the
postmaster there if you want to take further steps to resolve this.

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

Not only are these completely different systems, there is every indication
that that they are VAXen whereas UNC is an IBM of some sort. Nothing in the
tables indicates that there is any connection between these systems other
than the fact that they are at the same institution.

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

In general, queries like this cannot be answered usefully unless you include
the _exact_ and _complete_ text of the error message. We can do little aside
from handwaving without more specifics. Please include them initially in the
future.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF-FAX question
From: brad.thomas@uwyo.edu
Date: 26 Jan 1993 10:52:43 -0700
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Jan 1993 10:52:43 -0700
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTYY22FPPU8ZFQ6A@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT


We are considering various FAX solutions for the campus e-mail network. The
problem that we have with most of them is handling inbound FAXs. Several
PC FAX vendors support the use of Direct Inward Dialing (DID), usually via an
EXACOM DID module. The DID module passes to the FAX server the "actual" phone
number that was dialed. The server then uses this to route the FAX to the
correct e-mail user. This solution is fine except that it does not address all
possible e-mail systems on campus and the cost for some of the PC software is
very high.

Is there any way to currently use a DID type line with PMDF-FAX, or are there
plans for such. We like the way PMDF-FAX works but dont want to have to someone
there to manually route the incoming FAXs.

Thanks

-------------------------------------------------------------------------------
|   ####   ###  ##    |   Brad Thomas                                         |
|   ####   ###  ##    |   System Programmer                                   |
|   ####   ###  ##    |   Network Development Group                           |
|   ####   ###  ##    |   University of Wyoming                               |
|    ###    #   #     |   Brad.Thomas@UWyo.Edu                                |
|     ###### ###      |   bthomas@drifter.uwyo.edu                            |
-------------------------------------------------------------------------------
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Trying to use  *** DELIVER ***
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 22 Jan 1993 18:02:17 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 22 Jan 1993 18:02:17 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTTTYEOU7M8ZF7RU@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

> username is CSC_TEST
>
> a.	I have the USE_MAIL_DELIVERY set to 1
> b.	MAIL.DELIVER has one line--->   * * * A P  SYSTEM
> c.	set forward in%"~CSC_TEST"
>
>
> messages goto the D channel and stay there....
> is there something else i should be doing I am including teh D_MASTER.LOG
> file.

The messages go to the D channel because the forwarding address is incorrect.
The sit in the D channel because VMS MAIL to that remote address is busted.
(VMS MAIL/account problem -- has nothing to do with PMDF.)  See my earlier
reply to you where this is all discussed at much more length.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: NOTES channel and FWD:
From: Bob Tinkelman <bob@camb.com>
Date: 21 Jan 1993 21:32:17 -0500 (EST)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Jan 1993 21:32:17 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTSK5CEPUQ94DNLW@INNOSOFT.COM>
X-Vms-To: IN%INFO-PMDF
X-Vms-Cc: TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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?
From: crw@icf.hrb.com (Craig R. Watkins)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Looking for VMS-based X.500 Client Software
Date: 27 Jan 93 02:49:22 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Jan 1993 21:49:22 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
X-MX-Warning: Warning -- Invalid "To" header.
CC: info-pmdf@INNOSOFT.COM
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTZHU255SY8WVZ9J@INNOSOFT.COM>
X-Vms-To: IN%"@cunyvm.cuny.edu:jlw@psulias.bitnet"  "jlw"
X-Vms-Cc: IN%"info-pmdf@INNOSOFT.COM"
Mime-Version: 1.0
Content-Type: MESSAGE/RFC822

Content-type: TEXT/PLAIN; CHARSET=US-ASCII
>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?

ISODE is available from ftp.uu.net. "Patches" for a VMS port done by Peter Kay
are available from cc-vms1.massey.ac.nz.

ISODE is an implementation of the ISO protocols which includes a few X.500
user agents.  Two of which, DISH and SD, are ported to VMS.  Transports
supported include most popular TCP/IP's and PSI (X.25).  To build and install
this you need a fairly good understand of OSI protocols and/or lots of time
(and GCC).

DISH is a powerful X.500 UA which is not user friendly and requires a good
understanding of X.500 to use.  SD is friendly screen-oriented front-end
but is somewhat limited.

>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

You could use DISH for this.  I have used DISH to do lookups at Penn State.
I have not been successful with SD because of the X.500 structure at PSU,
but this could probably be solved with some tailoring of SD.


>        (2) can be accessed to the benefit of our users

You may be able to tailor SD.  It might not be too bad if you have
a good background in X.500.

>        (3) might eventually be incorporated into things like our Email
>                (PMDF/VAX Mail)

This should be done for you in the future.  ISODE is the basis for
PMDF-X.400 and most likely will the basis for X.500 directory services
in the future.

Craig
From: david@ittpub.nl (David P. Morgan)
Newsgroups: vmsnet.mail.pmdf
Subject: Internet mail/X.400 ?
Date: 21 Jan 93 19:30:11 WET+0100
Organization: ITT Publitec R+D BV, Amsterdam


I couldn't find anywhere more suitable to post this ...

Does anyone know how one can send from Internet to X.400 and vice versa ?
Is there a gateway which is available to all and how would the addresses
be mapped to one another ?

thanks in advance

--------------------------------------------------------------------------------
David P. Morgan                        Internet: david@ittpub.nl        |ucannot
ITT Publitec R+D BV                    UUCP:     ...!sun4nl!ittpub!david|readdis
Amsterdam                              PSI:      020412905761212::DAVID |onavt52
Newsgroups: vmsnet.mail.pmdf
Subject: WordPerfect Office 3.1
From: al@mom.spie.org
Date: 21 Jan 1993 11:40:21 -0700 (PDT)
Organization: SPIE - The International Society for Optical Engineering
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Jan 1993 11:40:21 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTS2CIQNJ68ZEVS2@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@ymir.claremont.edu"
X-Vms-Cc: AL
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.

Muchas gracias for any info.
Xref: sparky vmsnet.mail.pmdf:2896 news.software.anu-news:1771
From: rainwatr@ucbeh.san.uc.edu
Newsgroups: vmsnet.mail.pmdf,news.software.anu-news
Subject: Invalid username "."
Date: 27 Jan 93 08:31:05 EST
Reply-To: Don.Rainwater@UC.Edu
Distribution: world
Organization: Univ. of Cincinnati Center for IT Services

	I'm having a minor problem with trying to send a mail message from
within a detached job (running from DEC Scheduler).  The particular job that
I'm looking at is the arbitron job for ANU News.  Here's the tail of the
arbitron log file:

	<user> hasn't logged in this month
	<user> hasn't logged in this month
	<user> hasn't logged in this month
	<user> hasn't logged in this month
	<user> hasn't logged in this month
	<user> doesn't read news
	$ mail arbitron.out "in%""netsurvey@decwrl.dec.com""",usenet
	%MAIL-E-USERSPEC, invalid user specification '.'
	$       exit $status
	  SYSTEM       job terminated at  4-JAN-1993 18:43:30.73


	The arbitron program is completing normally, but the MAIL command
is failing.  I can cut that exact MAIL command straight from the log file
and paste it onto the command line and it works just fine.  Of course, this
all worked just fine up until about a month ago. :)

	Versions: VMS 5.5-2, PMDF 4.1, ANU News 6.0.3.  Thanks for any
information.
--
Don Rainwater, Systems Manager, Univ. of Cincinnati Center for IT Services
Don.Rainwater@UC.Edu
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF-FAX question
From: "Daniel C. Newman" <dan@sigurd.innosoft.com>
Date: 26 Jan 1993 11:56:53 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 26 Jan 1993 11:56:53 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GTZ2WZME428ZFO0J@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"Brad.Thomas@UWyo.Edu"
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 are considering various FAX solutions for the campus e-mail network. The
> problem that we have with most of them is handling inbound FAXs. Several
> PC FAX vendors support the use of Direct Inward Dialing (DID), usually via an
> EXACOM DID module. The DID module passes to the FAX server the "actual" phone
> number that was dialed. The server then uses this to route the FAX to the
> correct e-mail user. This solution is fine except that it does not address all
> possible e-mail systems on campus and the cost for some of the PC software is
> very high.
>
> Is there any way to currently use a DID type line with PMDF-FAX, or are there
> plans for such. We like the way PMDF-FAX works but dont want to have to someone
> there to manually route the incoming FAXs.

To the best of my knowledge there is still only one DID capable, external FAX
modem.  That is the FaxBox line from DCE corporation.  These modems are,
however, pricy (e.g., a FaxBox/30 costs ~ $2,500 and that's without the DID
module).

PMDF-FAX does support the DCE FaxBox line and 4.2 supports the DID routing
capabilities of the FaxBox.

DCE is in Stamford, Connecticut.  There phone number is (203) 358-3940.

Dan
Newsgroups: vmsnet.tpu