HDTenEightyP/NetNews huggingface dataset:
Newsgroups: vmsnet.mail.pmdf
Subject: Help needed with setting up the 'd' channel
From: "A. Mahendra Rajah, System Manager" <mahendra@meena.cc.uregina.ca>
Date: 16 Nov 1992 08:20 -0600
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 08:20 -0600
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR7JWRGJWY8ZG6D4@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
X-Vms-Cc: MAHENDRA
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Hello all:

    We have a few VAXstations on our LAVC that do not run PMDF. Internet
    mail to these systems are forwarded by the PMDF host
    Meena.CC.URegina.CA using the decnet channel as follows:

!
! Rewrite rules for the D (MAIL-11) channel
!
ponna                   $U%ponna@DECNET-MAIL
regie1                  $U%regie1@DECNET-MAIL
regie2                  $U%regie2@DECNET-MAIL
Lang                    $U%Lang@DECNET-MAIL

d 733 nox_env_to header_733
DECNET-MAIL
ponna           ponna
regie1          regie1
regie2          regie2
Lang            Lang


    The trouble with this is that on all out-going mail from these
    systems, the From: field shows up as just user@host (e.g.
    User@Lang) which is not replyable. What we would like to have is
    the From: address to be User%Lang@Meena.CC.URegina.CA. Please
    explain how this can be accomplished?

    Thanks.

    -- mahendra (A. Mahendra Rajah :: Mahendra @ Meena.CC.URegina.CA)
From: gomide@fpsp.fapesp.br
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF 3.2 - job enqueue error
Date: 18 Nov 92 20:22:17 GMT
Reply-To: gomide%BRFAPQ.BITNET@ymir.claremont.edu
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: Wed, 18 Nov 1992 16:29 BSC (-0300 C)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRALRDEWHE8ZHY6M@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.bitnet"
X-Vms-Cc: GOMIDE
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Comments: @FAPQ.FAPESP.BR - @FAPQ%FPSP.HEPNET - @BRFAPQ.BITNET - .BR gateway

Dear Sirs,

I'm running pmdf 3.2 with VMS 5.4-2. When a new mail arrives, pmdf
enqueues another job on the corresponding queue, without recognizing
that there are already other jobs for the same channel pending on that
queue. This creates a big overhead of JOB CONTROL. Is there a patch to
correct this? For reasons not stated here I can not install pmdf 4.x
right now.

Yours,
--
Alberto Courrege Gomide | Fundacao de Amparo `a Pesquisa - (11)831-3357
Software Supervisor     | Rua Pio XI, 1500 - CEP 05468-901 - Sao Paulo
<gomide@fapq.fapesp.br> | FAX (11)261-4167 Telex (11)82014 - Brazil
(ACG8) - .BR Domain Technical Contact. |        [this space for rent]
--
Newsgroups: vmsnet.mail.pmdf
Subject: RE: ccMail question
From: Andrew Rutherford <andrewr@itd.adelaide.edu.au>
Date: 20 Nov 1992 10:30:47 +1030
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Nov 1992 10:30:47 +1030
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRCB3X565E8ZHU1N@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"DAN@INNOSOFT.COM"  "Daniel C. Newman"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7BIT

In message <01GRC1RSC9TE9AMIDG@INNOSOFT.COM> you write:

+ The problem is that cc:Mail has some limitations on the length of lines in
+ messages.  So you have two choices: do nothing in which case PMDF has to stuf
+ f
+ the message into a cc:Mail file attachment which doesn't have the line length
+ limitation, or tell PMDF that there is a line length limitation in which case
+ PMDF will wrap the lines using the MIME quoted printable encoding.

	This file attachment approacg does create a slight problem -
it creates a file attachment with no name associated with it. This
makes it impossible to associtae a default action with the file. As
such, I have filter I whipped up on the PC that does the
import/export, which looks for a file attachment without a name and
calles it "MAIL.TXT", or .tx1, .tx2, etc, if mail.txt is already
taken. This makes it possible to associate a default action (in most
cases this is fire up Notepad) with the attachment, otherwise you have
to fiddle around (save it as something, then fire up an app manually
to read it).
	I don't use cc:Mail myself, so I (and all the regular cc:Mail
users) might be missing something - is there an easier way of handling
this?
	The real fix, of course, is for Lotus to fix the import/export
routines to handle more than 80 characters, so I don't see this as
Innosoft's problem. After having a godd look at what it's capable of,
including restrictions mentioned in the manual an those not mentioned,
Ned and co. have done remarkably well given the interface they've got
to deal with, IMHO. It's not nice, with things like "No text item can
be larger than 20K" all over the place...

Cya,
	Andrew.

/*
 * Andrew Rutherford                 andrewr@itd.adelaide.edu.au
 * +61 8 228 5669            Real Programmers always confuse Christmas and
 * Room 1060, Adelaide Uni      Halloween because OCT 31 == DEC 25 !
 */
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Sudden switchover to JNET protocol...
From: Ned Freed <ned@innosoft.com>
Date: 23 Nov 1992 10:18:44 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 23 Nov 1992 10:18:44 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRHKALYQ3M8ZIFZ8@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SYSMARK@minna.iit.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

This is a problem caused by a bug in the BN_SLAVE program coupled with your
use of nosendpost on the bit_local channel. The combination of the two
produces an attempt to enqueue a message with no recipients. This is an
illegal condition and causes the BN_SLAVE program to exit. The solution is
to use something weaker than nosendpost; errsendpost would be an excellent
candidate for this.

Note that use of nosendpost in this fashion can cause the silent loss of
any message that has no valid originator or recipient specified. While there
is nothing wrong with this per se it may or may not be a good idea.

The underlying problem here will be corrected in PMDF V4.2.

				Ned
From: martinez@iris-dcp.es
Newsgroups: vmsnet.mail.pmdf
Subject: Help: mapping file for VMS addresses
Date: 17 Nov 92 16:52:08 +0100
Organization: REDIRIS, Red Nacional de I+D


I wouldd like to see all occurrences of   PSI%NETWORK1...   being replaced by
      PSI$NETWORK2...   in addresses.

According to the manual, I have created a PMDF_MAPPING_FILE that reads

...

PMDF-TO-VMSMAIL

   PSI$%IBERPAC.*                        PSI$%ARTIX.$0$>

...

but doesn't seem to work. Am I on the right way?
Any help appreciated.

Thanks. Ignacio
--------------------------------------------------------------------------------
Ignacio Martinez     e-mail:  martinez@rediris.es
RedIRIS/FUNDESCO              C=es;ADMD=mensatex;PRMD=iris;O=rediris;S=martinez
Alcala, 61           tel:     + 34 1 4351214
28014  Madrid        fax:     + 34 1 5781773
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Alias, reply address problem.
From: "Daniel C. Newman" <dan@innosoft.com>
Date: 19 Nov 1992 16:06:27 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 16:06:27 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRCB90WNYA9LUY0J@INNOSOFT.COM>
X-Vms-To: IN%"ipmdf@INNOSOFT.COM"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> Below is an error I got replying to a message I received. I realize why I got
> the error.  In PMDF on our vax (DUKEMC) I have put in an alias for dryfo001 and
> pointed it to dryfo001@deneb.mc.duke.edu (my workstation).
>
> This has worked fine for some time.  However, just found a case where it does
> not.  Someone sent me mail from a Bitnet node (DUKEMVS) to dryfo001@dukemc.  My
> alias forward sent it to me at deneb.mc.duke.edu, but the return address was
> setup so that it would only work we replying through the PMDF system (which it
> was not) -- i.e. user@node.bitnet.  Normal SMTP internet mail works fine as my
> reply goes directly to the sender and not through PMDF.  I suspect I need a
> rewrite rule or something to prevent this?  Am I doing something I am not
> supposed to? On systems connected to the PMDF system, I want replies to go
> through our Bitnet connection, but for cirumstances such as this, we need to go
> through an SMTP/Bitnet gateway or back through the PMDF system?

The problem, as I see it, is that the machine you sent the message to doesn't
know what to do with the host name "dukevms.bitnet".  What's the alternative?
Send it "dukevms"?  That's not the correct either in this case.  The best
solution is to configure deneb.mc.duke.edu to know what to do with addresses of
the form user@node.bitnet.  If deneb.mc.duke.edu is on BITNET then it needs to
send it out BITNET.  If it isn't on BITNET then it needs to gateway the mail
through a machine which is on BITNET.  While you can work around this instance
of the problem with PMDF on DUKEMC, it will not fix the problem for when mail
arrives on deneb.mc.duke.edu from other hosts.

To "fix" things via PMDF on DUKEMC, you can add a second wtcp_ channel on
DUKEMC which will force routes into addresses and thereby produce return
addresses of the form user%host@mc.duke.edu.  However, this will be done to
_all_ of your mail from DUKEMC to deneb.mc.duke.edu.  This may, for all I know,
be desireable to you as it will put your workstation's mail load onto DUKEMC.
However, the cleanest solution would be to train sendmail on deneb.mc.duke.edu
to know what to do with BITNET addresses.

Add the rewrite rule

    deneb.mc.duke.edu     $U%deneb.mc.duke.edu@WTCP-ROUTE

and then add the channel block

    wtcp_route smtp single_sys exproute nox_env_to
    WTCP-ROUTE

The key thing here is the "exproute" keyword which causes the local host to get
stuffed into the address as a route.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: "Illegal host/domain name" errors
From: "Steven L. Jobes" <jobes@mayo.edu>
Date: 19 Nov 1992 15:17:10 -0600 (CST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 15:17:10 -0600 (CST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRC5CKB4SY8ZHVGL@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"info-pmdf@YMIR.CLAREMONT.EDU"
Autoforwarded: false
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Importance: normal
Priority: non-urgent
Sensitivity: Private
Ua-Content-Id: 116B9BD10800
X-Hop-Count: 1

This morning, I saw a half dozen inbound messages bounce with "illegal
host/domain name" errors.  All were addressed to user%rocvm@mrp.mayo.edu for
delivery to OfficeVision through PMDF-MR and MRP.  These were legal addresses;
in fact, subsequent attempts to send to the same addresses succeeded.  Section
15.3.7 says that such errors can occur, even with legal addresses, if the
network transport is unable to accept the message.  The VAX's pagefile space
was critically low during this time.  Since then, I've added another pagefile
and rebooted.  Do you think the pagefile problem explains these failed
deliveries?  Thank you.
..............................................................................
Steven L. Jobes                                                 jobes@mayo.edu
Network Management, Mayo Foundation, Rochester, MN 55905          507-284-4047
..............................................................................
Newsgroups: vmsnet.mail.pmdf
Subject: Errors in MAILSERV command processing
From: "Sue Ake (814) 863-2524" <sue@a1.psupen.psu.edu>
Date: 20 Nov 1992 08:09 -0500 (EST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Nov 1992 08:09 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRD3986CK28ZI80T@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Posting-Date: 20 Nov 1992 08:12 -0500 (EST)
Importance: normal
Priority: non-urgent
X-Hop-Count: 1
A1-Type: MAIL


I was using mailserv when it was unsupported in version 4.0.  Now that I've
upgraded to 4.1 and it is supported, I received the following message when I
tried to subscribe to one of my mailing lists:

	Mailing lists are not enabled, command: subscribe inservice-l
	Subsequent commands ignored because of previous error.
	Ignored:
	Use the HELP command to get a list of legal MAILSERV commands.

So, how do "enable" mailing lists in version 4.1?

Sue
------------------------------------------------------------------------------
Susan Ake                                       Internet: SUE@PSUPEN.PSU.EDU
Systems Project Analyst, Computer Services      BITNET:   SUE@PSUPEN
College of Agricultural Sciences                FAX:      (814) 863-7209
The Pennsylvania State University               Voice:    (814) 863-2524
------------------------------------------------------------------------------
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: ccMail question
Date: 18 Nov 92 22:52:37 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Nov 1992 15:52:37 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRAWIDBFSI8ZI0JR@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"MAC@gvg47.gvg.tek.com"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> We are seeing some of the messages that PMDF leaves for ccMail to deliver
> that contain what looks like some form of line wrapping that uses the ``=''
> as the continuation character.  There message also appear to have hex
> quoting for some characters like maybe =20 means a space and maybe =9 means
> a tab.  I know this is a marginal description of the problem.  I will
> enclose a part of one of these message at the end of this message.  What is
> going on?  Any help greatly appreciated.

You're seeing line wrapping which uses the quoted printable MIME encoding.
The "=xx" means "ASCII character with hex value xx".  You see some =20 at
the end of lines because PMDF wrapped the line and was now afraid that if
it left a naked space at the end of the line some other mailer would strip
it away.  The =9 are tabs.

Send your PMDF.CNF to service@innosoft.com and some sort of indication as
to how this message originally entered PMDF.  It probably came in on some
channel with a "linelength" keyword specified.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: Working with MR "flags" like sensitivity in PMDF-MR
From: "Brett E. Bowman" <bowman_brett_e@lilly.com>
Date: 19 Nov 1992 15:48:12 +0000 (GMT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 15:48:12 +0000 (GMT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
X-MX-Warning: Warning -- Invalid "To" header.
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRBTV2LYKY9AMKSV@INNOSOFT.COM>
X-Vms-To: IN%"@mr.lilly.com:ipmdf%innosoft.com@in"
Autoforwarded: false
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Importance: normal
Priority: non-urgent
Sensitivity: Private
Ua-Content-Id: 116B9AA40F00
X-Hop-Count: 2

Our company is evaluating migrating users to DEC's Mailworks.  We currently use
a gateway machine to connect to the Internet and exchange mail between the
Internet and our internal mail network using PMDF and PMDF-MR.

We have a mechanism in place to control who can send messages out onto the
Internet.  Before people can get access, them are required to read and
acknowledge a statement about use of the Internet and about not sending
confidential information over it.  For the most part, this system seems to work
fairly well.  However, we occasionally have people who are "authorized" that
"accidentally" send messages to the wrong address (Internet rather than
intra-company).

A1Mail has a feature of being able to specify a "Sensitivity" for a message.
Are there any plans for PMDF-MR to be able to do something with this flag?
(Such as only allowing messages where sensitivity is not COMPANY_CONFIDENTAIL
to be sent out onto the Internet.)  We are looking at starting to use PMDF for
some of the internal mail routing, also, so it would be best if something could
be applied based upon the routing rather than just applying to everything
coming through PMDF-MR.

						Brett E. Bowman
						Eli Lilly & Company
						BBOWMAN@Lilly.Com
Newsgroups: vmsnet.mail.pmdf
Subject: RE: strange Return address...
From: "Kevin V. Carosso" <kvc@summer.innosoft.com>
Date: 20 Nov 1992 00:30:17 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Nov 1992 00:30:17 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRCTGR6HSI8ZI827@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SKIPPER%MEDCOLPA.BITNET@ymir.claremont.edu"
X-Vms-Cc: info-pmdf
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

> From: "NAME = Hayne Margulies\\"" <"mcplib::margulies"@shrsys.hslc.org>

The other system generated that, I have no idea why, though I suspect it
is due to weird characters in a VMS MAIL personal name.  The doubled-up
backshlashes look wrong to me (isn't it supposed to be a single backslash
to quote the double-quote that follows that is inside of the matching pair
of double-quotes?

>  IN%"'NAME = Hayne Margulies\\\\'' <'mcplib::margulies'@shrsys.hslc.org>"

Anyway, PMDF saw that horrible thing and quoted it up still further for
VMS MAIL.  If you quote the double-quote that's inside the matching pair
of quotes with a single backslash, like this:

   IN%"'NAME = Hayne Margulies\'' <'mcplib::margulies'@shrsys.hslc.org>"

then PMDF seems to like it.  I suspect MX botched it when it tried
to quote up the funny-looking personal name field.

	/Kevin Carosso
	 Innosoft
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: forwarding mail for testing
Date: 16 Nov 92 23:09:46 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 16:09:46 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR84K6LMOY8ZH17U@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"cvm@NAUVAX.UCC.NAU.EDU"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>>> I am trying to evaluate MS-Mail.  To help do this I would like to have
>>> all mail that is sent to my VMS mail account also sent to my MS-Mail
>>> account. I am currently using the W action of deliver to do this, but it
>>> does not keep the original headers intact.  Any suggestions on how I can
>>> accomplish this?  I use deliver for other purposes also.  Could I
>>> eliminate the W action in my MAIL.DELIVERY file, change my forwarding
>>> address in VMS mail to be: in%"~cvm,cvm@msmail.ucc.nau.edu" and still
>>> have deliver work?
>>
>>Use the P action instead of W or F.  The problem with W and F is that they
>>use VMS MAIL to forward the message and this is too much of a disruption to
>>the headers.  If you use the P action, then PMDF SEND will be used instead
>>of VMS MAIL:
>>
>>  * * * A P "cvm@msmail.ucc.nau.edu"
>>
>>Dan
>
> The P action keeps the headers intact but it does not leave the
> originator of the message as the sender.  What I really need is a an
> action that uses PMDF SEND to send the mail and makes the From: field be
> the original sender of ther message.

You might consider making cvm into an alias by adding the following to
pmdf_root:[table]aliases.;

   cvm: _cvm,cvm@msmail.ucc.nau.edu

and not bother with DELIVER.  If you have a compiled configuration, then
you will have to recompile it and re-install it before this change will
take effect.  You might also make cvm in VMS MAIL forward to IN%CVM


   MAIL> set forward/user=cvm in%cvm

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: RE: "Illegal host/domain name" errors
From: Ned Freed <ned@innosoft.com>
Date: 19 Nov 1992 15:12:43 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 15:12:43 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRC9DRWGKY8ZI4QY@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"jobes@mayo.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I'd have to see the errors in question, and in particular where they
occurred, before I could possibly comment on why they happened. Generally
speaking, this sort of thing usually occurs as a result of nameserver
glitching, and is unrelated to resource starvation issues.

				Ned
From: robinson@ucbeh.san.uc.edu
Newsgroups: vmsnet.mail.pmdf
Subject: PMDF-FAX questions
Date: 23 Nov 92 08:57:28 EST
Distribution: world
Organization: Univ. of Cincinnati

At the University of Cincinnati we are considering replacing our current
fax gateway and I have a couple of questions about PMDF-FAX.  We have a
Gammalink fax modem on our present set-up.  How much modification to the
source code is required to support a modem other than those listed in the
PMDF System Manager's Guide?  Has anyone done this?  Also, is there a
limit in PMDF-FAX to the number of digits in the phone number?  Our
system doesn't allow more than 20 digits which prevents our users from
sending international faxes as we have an authorization code we must 
enter when calling long distance and it puts us over the limit.
  
Apologies if this isn't the correct group for this type of question.
Thanks for any info.
-- 
Jim Robinson                         University of Cincinnati
Jim.Robinson@UC.Edu       
Newsgroups: vmsnet.tpu
From: fairfield@slacvx.slac.stanford.edu
Subject: Re: EVE with option /DISPLAY + /SECTION
Organization: Stanford Linear Accelerator Center
Date: Wed, 18 Nov 1992 19:06:05 GMT

In article <Bxx0G7.9rG@ireq.hydro.qc.ca>, ratel@ireq.hydro.qc.ca (Gilles Ratel 8720) writes:
> SUBJECT: EVE WITH OPTION /DISPLAY + /SECTION
>          VAX/VMS V5.5-1
>          DW-MOTIF  (Producer:DEC) (Availability: F (Layered Products))
> 
> Hello,
> 
> I have a new section file
>   create by: DECTPU V3.1  1992-08-17 8:37  (i.e. look SHOW SUMMARY)
> 
> If I writes command:
>   $ EDIT/TPU/SECTION=MV4$0:[RATEL]VT200_EVE
> 
>   O.K.
> 
> or command:
>   $ EDIT/TPU/DISPLAY=DECWINDOWS
> 
>   O.K. (without section file)
> 
> But with:
>   $ EDIT/TPU/SECTION=MV4$0:[RATEL]VT200_EVE/DISPLAY=DECWINDOWS
> or
>   $ DEFINE TPU$SECTION=MV4$0:[RATEL]VT200_EVE
>   $ EDIT/TPU/DISPLAY=DECWINDOWS
> 
>   I have warning:
> ----
> X Toolkit Warning: I18NOpenFile: Couldn't open file EVE$WIDGETS - MrmNOT_FOUND
> Could not open the specified UID file(s)
> ----
>      ?????
>      and section file is not effective !

    On our V5.5-1 system, there is a file SYS$COMMON:[SYSLIB]EVE$WIDGETS.UID.
The error message seems to be complaining about that file.  Make sure you've
got it on your system _in_ the correct directory.

-- 
 Dr. Kenneth H. Fairfield    |  Internet: Fairfield@Slac.Stanford.Edu
 SLAC, P.O.Box 4349, MS 98   |  DECnet:   45537::FAIRFIELD (45537=SLACVX)
 Stanford, CA   94309        |  BITNET    Fairfield@Slacvx
 ----------------------------------------------------------------------------
 These opinions are mine, not SLAC's, Stanford's, nor the DOE's...