HDTenEightyP/NetNews huggingface dataset:
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: PMDF 3.2 - job enqueue error
Date: 18 Nov 92 19:50:25 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 18 Nov 1992 12:50:25 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRAQ4UOUIQ8ZHXE7@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"gomide%BRFAPQ.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

     Support to do this was added to PMDF V3.0.  There are two possibilities as
to what might be going wrong here.  But first an explanation as to how PMDF
submits batch jobs:

(1) If the process has SYSPRV & CMKRNL privileges (required by $SNDJBC) PMDF
    first checks to see if there already is pending job and if not then submits
    a batch job with $SNDJBC.  The $GETQUI call to check for a pending job
    requires either SYSPRV or OPER privileges.

(2) If the process lacks SYSPRV or CMKRNL then PMDF cannout use $SNDJBC to
    submit the batch job.  It resorts to spawning a subprocess which submits
    the job using the DCL SUBMIT command.  In this case, no check is made to
    see if there already is a pending batch job.

     Now, from within VMS MAIL, (1) should always be used since the necessary
privileges are made available by PMDF's protected shareable image PMDFDISP.EXE.
If this image isn't properly installed then none of your users would be able to
send any PMDF mail whatsoever from within VMS MAIL.  I suspect, therefore, that
you are not seeing superfluous jobs queued from VMS MAIL.  You can double check
this by doing the following:

       $ STOP/QUEUE/NEXT MAIL$BATCH
       $ MAIL/SUBJECT="Test 1" SYS$LOGIN:LOGIN.COM IN%SYSTEM
       $ MAIL/SUBJECT="Test 2" SYS$LOGIN:LOGIN.COM IN%SYSTEM
       $ SHOW QUEUE/FULL/ALL MAIL$BATCH

Do you see one or two pending L channel jobs in the MAIL$BATCH queue?

     My guess is that the superfluous pending jobs are being created by PMDF
channel programs which are running under an account which lacks either SYSPRV
or CMKRNL or both and is therefore following (2) above.  To isolate this
problem, you'll have to determine which all accounts may be running PMDF
channels and what privileges that they have.  (For instance, do you use
DECnet, PhoneNet, or PSI channels and if so does your PMDF server account
lack these privileges?)

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: MAILSERV crashes when mapping file used
From: rollo.ross@levels.unisa.edu.au
Date: 16 Nov 1992 17:57:18 +1030
Organization: University of South Australia
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 17:57:18 +1030
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR75HZX3F68ZHGLQ@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@ymir.claremont.edu"
X-Vms-Cc: CCAJR
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

	I have been trying to use the "MAILSERV_ACCESS" mapping to control
access to a mailing list. Everything I try causes MAILSERV to crash like this:

>$ run pmdf_root:[exe]mailserv.exe
>Debugging enabled.
>  Command limit set to 2147483647
>  Maximum blocks per message set to 2147483647
>  Maximum lines per message set to 2147483647
>  MAILSERV reply address is: mailserv-reply@Levels.UniSA.Edu.Au
>
>Starting processing of PMDF_ROOT:[QUEUE.mailserv]ZZ01GR87M48MDG9I489P.00
>  Message is from: CCAJR@Levels.UniSA.Edu.Au
>  Command: send/list sinelist
>  CLI$DCL_PARSE returned status of 196609
>Processing SEND/LIST command.
>  Access check: SENDLIST|SINELIST|CCAJR@Levels.UniSA.Edu.Au
>Access violation, reason mask=01, virtual address=00248568, PC=000D56A0,
>								PSL=03C00000
>Symbolic stack dump follows
>module name     routine name                     line       rel PC    abs PC

>                                                           000D56A0  000D56A0
>MAILSERV        SEND_LIST_ROUTINE                5729      000003CA  00008DCA
>                                                           7FF7677B  7FF7677B
>                                                           00010F7A  00010F7A
>MAILSERV        PROCESS_COMMAND                  6843      000000E9  0000E5A1
>MAILSERV        PROCESS_MESSAGE                  6990      000006E5  0000EE75
>MAILSERV        MAILSERV                         7172      000000D6  0000F96E
>$ goto out1

	My MAPPINGS. file contains only:
>MAILSERV_ACCESS
>
>    SENDLIST|SINELIST|*    $Y

	The crash even happens for messages asking for a SEND/LIST of a
mailing list other than SINELIST. The crash goes away when I remove the
MAPPINGS. file and recompile, but then I'm blocked by the default action of
not allowing SEND/LIST.

	I am using a compiled configuration, and I am remembering to install
it on all nodes in the cluster after using CNBUILD. It's PMDF 4.1, of course.

                                    Rollo Ross, Network Manager (CLW campuses)

Computer Centre,  University of South Australia, The Levels, SA 5095, Australia
Ph +61 8 302 3158 Fax 302 3385 DTE 505282622004  Rollo.Ross@Levels.UniSA.Edu.Au
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: forwarding mail for testing
Date: 16 Nov 92 23:04:07 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 16:04:07 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR84BPTV368ZHH02@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 will find absolutely no easy way to do this in PMDF since it is, after all,
a violation of the relevant standards.  (That is, it is intentionally
difficult.)  The only way you'll be able to do this is to write your own PMDF
channel.

Dan
Newsgroups: vmsnet.mail.pmdf
Subject: Routing outgoing mail through another host
From: "Khatri, Shah" <shah.khatri@asu.edu>
Date: 23 Nov 1992 15:55:00 -0700 (MST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 23 Nov 1992 15:55:00 -0700 (MST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRHUIDUNC28ZILXX@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"  "'smtp:ipmdf@ymir.bitnet'"
Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID porh2ldsY8DGdhxh2e5UUQ)"
X-Mailer: Microsoft Mail V3.0


--Boundary (ID porh2ldsY8DGdhxh2e5UUQ)--
Newsgroups: vmsnet.mail.pmdf
Subject: Asociated U*ix Mail
From: peter@embl-hamburg.de
Date: 19 Nov 1992 09:02:43 +0100
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 09:02:43 +0100
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRBIQ2W1HE8ZHVGR@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


Hi!

We have arranged that U*ix-only users incoming mail can be redirected from a
site based address like "unixuser@embl-hamburg.de" using ALIASES.

Incoming mail to these system addresses like "user@unixmachine.embl-hamburg.de
are also catered for by our MX entries _in_most_cases_


Can a(n) U*ix guru tell me what procedure I should direct the U*ix user to use
to send his mail via my network-hub so that it gets the site-based-address
through my REVERSE Database?
Or does the U*ix machine need CMDF or something?
Or is it trivial to make Sendmail use a substitute _site_ From: Address?

regards

Peter Bendall
European Molecular Biology Laboratory,
Hamburg Outstation.

 Date:     19-NOV-1992 08:47:44.30
 From:     Peter Bendall        : WIN-Mail        PSI%(0262)45050150057::PETER
 Dept:     Computer Group       :
 Tel:      +49  40 - 899 02 133 : Internet        Peter@EMBL-Hamburg.de
 FAX:      +49  40 - 899 02 149 : EAN-Mail        Peter@Hamburg.embl.dbp.de
                                :       (S=Peter;OU=Hamburg;P=embl;A=dbp;C=de)
.----.------------------------------------------------------------------.----.
|    |             This space intentionally left blank !                |    |
`----`------------------------------------------------------------------'----'
From: dan@innosoft.com (Daniel C. Newman)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Help needed with setting up the 'd' channel
Date: 16 Nov 92 17:53:09 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 10:53:09 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR7TGLDSLE8ZHGEN@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"MAHENDRA@Meena.CC.URegina.CA"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

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

Add $E$F's to each of the rewrite rules so that they only work on forward
pointing envelope addresses.

  ponna                   $E$F$U%ponna@DECNET-MAIL
  regie1                  $E$F$U%regie1@DECNET-MAIL
  regie2                  $E$F$U%regie2@DECNET-MAIL
  Lang                    $E$F$U%Lang@DECNET-MAIL

Then remove the ponna, regie1, regie2, and Lang from the D channel.  Also,
get rid of the header_733 unless you really need that for some reason:

  d 733 nox_env_to
  DECNET-MAIL

The problem with what you had is that for mail passing from, say, PONNA through
your PMDF system to the outside world, the PONNA rewrite rule was being
invoked and rewriting the reverse pointing PONNA addresses to user@ponna
(which is what that rule says to do).  As it turns out, you only need rules
for PONNA, et. al. for inbound mail for those systems at which point you
do want to see the address user@ponna.  And thus the addition of the $E$F to
the rewrite rules for PONNA, et. al.  (so that the rules only fire for
inbound mail for those systems and then only affect envelope addresses).

Dan
From: crw@icf.hrb.com (Craig R. Watkins)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: MAILSERV crashes when mapping file used
Date: 16 Nov 92 16:15:31 GMT
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 16 Nov 1992 11:15:31 -0500 (EST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR7NY3C5SY8ZHFUL@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"Rollo.Ross@Levels.UniSA.Edu.au"
X-Vms-Cc: IN%"ipmdf@YMIR.CLAREMONT.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>	I am using a compiled configuration, and I am remembering to install
>it on all nodes in the cluster after using CNBUILD. It's PMDF 4.1, of course.

This is probably a bug that I've seen.  It's been fixed in the more recent
releases of 4.1 and I suspect someone from Innosoft will be up shortly
to give you the details.

In the meantime, a reasonable workaround is to NOT compile your tables.
This bug does not occur with un-compiled tables.

Craig R. Watkins                crw@icf.hrb.com
HRB Systems, Inc.               +1 814 238-4311
"I say it here; it comes out there." -- Albert Brooks "Broadcast News"
Newsgroups: vmsnet.mail.pmdf
Subject: Multinet TCP/IP parameter settings
From: s.ross@cgnet.com
Date: 20 Nov 1992 13:51:04 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Nov 1992 13:51:04 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: service@tgv.com
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRDKSN3IDU9AMLKW@INNOSOFT.COM>
X-Vms-To: IN%"ipmdf@innosoft.com"
X-Vms-Cc: IN%"service@tgv.com"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

Lately some hosts have been unable to connect to our Multinet TCP/IP
channel.  Currently the multinet/configure utility shows the
following parameters:

SERVER-CONFIG>sho smtp /full
Service "SMTP":
        TCP socket (AF_INET,SOCK_STREAM), Port 25
        Socket Options = SO_KEEPALIVE
        INIT() = TCP_Init
        LISTEN() = TCP_Listen
        CONNECTED() = TCP_Connected
        SERVICE() = Run_Program
        Program = "PMDF_ROOT:[EXE]MTCP_SLAVE.EXE"
        Working Set = 400
        Max Servers = 2
        Backlog = 2

We are interested in increasing the last two, Max Servers and Backlog to
allow more SMTP slave processes to be running simultaneously and to allow
more calling machines to be queued while waiting for one of the processes
already running to finish.

We have a 9600 bps compressed SLIP line to the internet and we're running
PMDF 4.1-13 and Multinet 3.0.

Can anyone recommend appropriate settings for these parameters that allow
more calls to come in at once?  Is it better to increase Max Servers or
Backlog or both?

Thanks in advance for any recommendations!

Steve Ross
CGNet Services International
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Bad return address
From: Chris Michels <cvm@msmail.ucc.nau.edu>
Date: 20 Nov 1992 10:32:00 -0800 (PST)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 20 Nov 1992 10:32:00 -0800 (PST)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: info-pmdf <info-pmdf@YMIR.CLAREMONT.EDU>
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRDBU762IA8ZI51T@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"KVC@SUMMER.INNOSOFT.COM"  "Kevin V. Carosso"
X-Vms-Cc: IN%"info-pmdf@YMIR.CLAREMONT.EDU"  "info-pmdf"
Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID LZ5u61FqnocRTl91uoljyQ)"
X-Mailer: Microsoft Mail V3.0


--Boundary (ID LZ5u61FqnocRTl91uoljyQ)--
Newsgroups: vmsnet.mail.pmdf
Subject: Memory leak in process symbiont?
From: c.chaundy@its.unimelb.edu.au
Date: 19 Nov 1992 10:39:29 +1100
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 19 Nov 1992 10:39:29 +1100
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRAXUMB6QA8ZI06H@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

We are using the PMDF process symbiont under V4.1-13 to run three PMDF
server queues and have been having a problem where occasionally the queues
stop.  The error messages that appear in the operator log file are:

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:46.69  %%%%%%%%%%%
Message from user SYSTEM on MUWAYB
%PMDF-F-PRCSMBFTL, PMDF process symbiont fatal internal error

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:48.55  %%%%%%%%%%%
Message from user SYSTEM on MUWAYB
%STR-F-INSVIRMEM, insufficient virtual memory

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:48.65  %%%%%%%%%%%
Message from user JOB_CONTROL on MUWAYB
%JBC-E-INVMSG, invalid mailbox message received

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:48.74  %%%%%%%%%%%
Message from user JOB_CONTROL on MUWAYB
-SYSTEM-W-ENDOFFILE, end of file

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:57.42  %%%%%%%%%%%
Message from user JOB_CONTROL on MUWAYB
%JBC-E-SYMDEL, unexpected symbiont process termination

%%%%%%%%%%%  OPCOM  19-NOV-1992 00:39:57.48  %%%%%%%%%%%
Message from user JOB_CONTROL on MUWAYB
-STR-F-INSVIRMEM, insufficient virtual memory

The page file quota for the PMDF server processes is about 24000, so
it would appear that there is a memory leak somewhere.

The worst thing is that whenever this occurs, it stops all three of the
server queues and this is on our main mail processing node so a vast
amount of mail queues up very quickly, so we regard this as a serious
problem.

Regards, Chris Chaundy (Technical Manager, Networks)

Information Technology Services, Thomas Cherry Building,
The University of Melbourne, Parkville, Victoria 3052 Australia
Phone:    +61 3 344 7045                Fax:   +61 3 347 4803
Internet: C.Chaundy@its.unimelb.EDU.AU 	(X.121 505233430003)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Additional mailing list security
From: c.chaundy@its.unimelb.edu.au
Date: 17 Nov 1992 15:25:23 +1000
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Nov 1992 15:25:23 +1000
Resent-From: epmdf@YMIR.CLAREMONT.EDU
CC: ipmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR8DOGDKXU8ZHISC@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"fineberg@wupost.wustl.edu"
X-Vms-Cc: IN%"ipmdf@ymir.claremont.edu"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

>Date: 15 Nov 1992 03:19:03 -0600
>From: fineberg@wupost.wustl.edu (Charles M. Fineberg)
>Subject: RE: Additional mailing list security
>
>c.chaundy@its.unimelb.edu.au writes:
>>With the MAPPINGS file now in PMDF, it is possible to control who add
>>subscribe and unsubscribe users from MAILSERV mailing lists, get copies
>>of the list, etc., but has anyone implemented a system where only a
>>restricted group of users may actually mail to particular lists?
>
>Hmm.  When I read the 4.1 docs it seemed trivial to limit who could post
>to a list, but allowing mailed list ownership didn't seem to be there at
>all.  So what did my denseness ignore?  That is where in the manual is
>the reference to controlling who may add and delete users?

It did not get into the manuals, but was described in some mail from Dan
a few months back.  It is all done with the MAPPINGS. file for the name
MAILSERV_ACCESS (for MAILSERV commands with special characters such as
SEND/LIST, the slash is simply omitted).  BTW, controlling who can post
to lists did not make it into early printings of the manuals either :-(.

Chris Chaundy (Technical Manager, Networks)

Information Technology Services, Thomas Cherry Building,
The University of Melbourne, Parkville, Victoria 3052 Australia
Phone:    +61 3 344 7045                Fax:   +61 3 347 4803
Internet: C.Chaundy@its.unimelb.EDU.AU 	(X.121 505233430003)
Newsgroups: vmsnet.mail.pmdf
Subject: RE: Logging feature missing?
From: Ned Freed <ned@innosoft.com>
Date: 17 Nov 1992 04:55:41 -0700 (PDT)
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 17 Nov 1992 04:55:41 -0700 (PDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GR8V8SCYYQ8ZHH1G@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"SKIPPER%MEDCOLPA.BITNET@ymir.claremont.edu"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

I don't know what you're missing. The entry you have should be sufficient
to enable logging. You might want to check file protections and for possible
corruption of the file. You can test and see if logging is enabled on a
particular chanel with PMDF TEST; for any given address it will print out
the associated channel information including LOGGING (channel flags #3) if
it is enabled. If it isn't enabled you need to investigate why -- things
like whether you've compiled your configuration, installed the resulting
image properly, used the defaults block in the proper place (before any
channels), etc. etc.

				Ned
Newsgroups: vmsnet.mail.pmdf
Subject: RE: RE: PMDF 3.2 - job enqueue error
From: gomide@fpsp.fapesp.br
Date: Thu, 19 Nov 1992 11:08 BSC (-0300 C)
Reply-To: gomide%BRFAPQ.BITNET@ymir.claremont.edu
Organization: The Internet
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: Thu, 19 Nov 1992 11:08 BSC (-0300 C)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GRBOAGVTLU8ZHYKM@YMIR.CLAREMONT.EDU>
X-Vms-To: IN%"DAN@INNOSOFT.COM,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

>
> Date: 18 Nov 1992 12:50:25 -0700 (PDT)
> From: "Daniel C. Newman" <DAN@INNOSOFT.COM>
>
> ...
>        $ STOP/QUEUE/NEXT MAIL$BATCH
>        $ MAIL/SUBJECT="Test 1" SYS$LOGIN:LOGIN.COM IN%SYSTEM
>        $ MAIL/SUBJECT="Test 2" SYS$LOGIN:LOGIN.COM IN%SYSTEM
>        $ SHOW QUEUE/FULL/ALL MAIL$BATCH
>
> Do you see one or two pending L channel jobs in the MAIL$BATCH queue?
>
>      My guess is that the superfluous pending jobs are being created by PMDF
> channel programs which are running under an account which lacks either SYSPRV
> or CMKRNL or both and is therefore following (2) above.  To isolate this
> problem, you'll have to determine which all accounts may be running PMDF
> channels and what privileges that they have.  (For instance, do you use
> DECnet, PhoneNet, or PSI channels and if so does your PMDF server account
> lack these privileges?)
>
> Dan

Thank you for answering. It follows that your guess is correct. I
tested the job enqueue with the above script, and no L channel job was
generated. I have several decnet, phonenet, psi and uucp channels,
with a good deal of activity on them. The account PMDF lacked sysprv
and cmkrnl privileges - I have just granted those privileges to the
account PMDF.

Thank you,
--
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]
--