Errors-to: epmdf@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"info-pmdf@ymir.claremont.edu"
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT
Date:         Sat, 21 Nov 92 01:35:25 GMT
From:         Mark Draughn <SYSMARK@MINNA.IIT.EDU>
Subject:      Sudden switchover to JNET protocol...
Newsgroups: bit.listserv.pmdf-l

In the past few days I've been getting messages from POSTMASTER complaining
about foreign protocols such as EDU% and COM%.  Then just today, I got a message

in which the VMS From: address began with BITNET% and suddenly it all began to
make sense.  Somehow local mail delivery for JNET mail was being routed through
the JNET local delivery system, not PMDF.

I checked the appropriate LMD.LOG file and found this:

>$ ! LMD.COM - Command file for the Jnet Local Mail Delivery Daemon
>$ ! This version invokes the PMDF server BN_SLAVE instead of the server
>$ ! provided with Jnet.  This version is for Jnet V3.5.
>$ !
>$ set noon
>$ !
>$ ! Uncomment these to make ALL-IN-1 messages repliable
>$ ! define/system/exec/nolog mail$protocol__jnet jan_jmailprot
>$ ! define/system/exec/nolog mail$protocol__profs jan_profsprot
>$ ! define/system/exec/nolog mail$protocol__zip jan_zipprot
>$ ! define/nolog jan_mailprot _JNET%
>$ ! define/nolog jan_profsmailprot _PROFS%
>$ ! define/nolog jan_zipmailprot _ZIP%
>$ !
>$ set default jan_sys:
>$ define sys$scratch jan_sys:
>$ !
>$ if f$search("JAN_SPOOL:FANOUT.RSC*") .nes. "" .and. -
>        f$search("JAN_SYS:FANOUT.PAR") .eqs. "" then create jan_sys:fanout.par
>$ if f$search("JAN_SYS:FANOUT.PAR") .nes. "" then run -
>        /noaccounting /process_name="Fanout_Daemon" /error=jan_log:fanout.err -
>        /output=jan_log:fanout.err jan_sys:fno ! /priority=n
>%RUN-S-PROC_ID, identification of created process is 2020012E
>$ run /noaccounting /process_name="Profs_Daemon" /error=jan_log:profs.err -
>        /output=jan_log:profs.err jan_sys:profsin ! /priority=n
>%RUN-S-PROC_ID, identification of created process is 2020012F
>$ !
>$ if f$search("PMDF_ROOT:[EXE]BN_SLAVE.EXE") .eqs. "" then goto old_server_1
>$ new_server:
>$ if f$logical ("PMDF_RESTART_BN_SLAVE") .nes. "" then -
>  deassign/system PMDF_RESTART_BN_SLAVE
>$ if f$trnlnm("PMDF_DISABLE_BN_SLAVE") .nes. "" then goto old_server_2
>$ define/user jan_sys jan_spool, jan_root:[sys]
>$ define/user pmdf_channel "bit_local"
>$ pmdf_jan_node = f$edit(f$logical("JAN_LOCAL_NODE"),"COLLAPSE")
>$ define/user pmdf_output pmdf_root:[log]bn_slave_IITVAX1.log
>$ run pmdf_root:[exe]bn_slave.exe
>%PAS-F-HALT, HALT procedure called
>%TRACE-F-TRACEBACK, symbolic stack dump follows
>module name     routine name                     line       rel PC    abs PC
>                                                           0005006B  0005006B
>                                                           000BE0C3  000BE0C3
>BN_SLAVE        CHECK_REPLY                      3497      00000044  00001AB4
>BN_SLAVE        BN_SLAVE                         4115      00001490  00003AFC
>$ if $status .eq. %X20B4 then goto new_server
>$ !
>$ old_server_1:
>$ mail NL: _SYSTEM /noself -
>  /subj="JMAILPROT started instead of PMDF as Jnet LMD server"
>$ !
>$ old_server_2:
>$ ! define jan_mailprot "BITNET%"
>$ loop:
>$ show time
>  19-NOV-1992 21:18:12
>$ mail/protocol=jan_jmailprot
>%MAIL-E-NOSUCHUSR, no such user YYYY at node KARL
>%MAIL-E-NOSUCHUSR, no such user WALLAU at node KARL
>%MAIL-E-NOSUCHUSR, no such user ASDFASDF at node KARL

The log file has this message:

>19-NOV-92  21:18:07: Unexpected fatal internal MM_ error
> -- no addressees

This is PMDF V4.1.  Any ideas what could cause this?
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU