🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

2 total messages Started by Richard H. Ault Tue, 15 Dec 1992 22:32
MX delivery to black hole
#334
Author: Richard H. Ault
Date: Tue, 15 Dec 1992 22:32
155 lines
5511 bytes
We are running MX 3.1C, UCX 1.3, and VMS 5.5-2 on new MV3100's.  Accounts were
moved from a functioning system on an MVII which didn't have the problems I'm
now encountering (I think, that system was only on 5.5-2 for two weeks prior to
the shift and the problem is only occuring on some low use accounts).

The symptoms:

Local VMS mail (node::user) works for all users and hosts.

Inbound mail works for all users.

Outbound mail addressed mx%"..." goes down a hole.  For a mail addressed to a
another user on another local node with debug on all I see is one entry in the
router log that looks like:

15-DEC-1992 15:37:26.32 %PROCESS, Processing entry number 32360
15-DEC-1992 15:37:26.43 %PROCESS, Status from READ_INFO was 00000001
15-DEC-1992 15:37:26.43 %PROCESS, Message originated in VMS Mail.
15-DEC-1992 15:37:26.44 %PROCESS,  will run domain expander on envelope
 addresses.
15-DEC-1992 15:37:26.44 %PROCESS,  will run domain expander on message headers.
15-DEC-1992 15:37:26.73 %PROCESS, Finished VMSmail-origin preprocessing.
15-DEC-1992 15:37:26.73 %PROCESS, Marking this entry as finished.

I can't find any entries in any other logs including Local that refer to this
message, the user who sent it or the user it was addressed to.

A user with sysprv shows this problem as well.

MCP show all shows:

Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;7

MX version id is: MX V3.1C

Domain-to-path mappings:
  Domain="queens.edu", Path=Local
  Domain="jtk.queens.edu", Path=Local
  Domain="jtk", Path=Local
  Domain="[152.36.64.252]", Path=Local
  Domain="*.BITNET", Path=SMTP, Route="cunyvm.cuny.edu"
  Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net"
  Domain="*", Path=SMTP

Aliases:
  LocalName="Postmaster", Address="ault@jlp.queens.edu"
  LocalName="POSTMAST", Address="ault@jlp.queens.edu"

SMTP agent settings:
  Retry interval:                    0 00:30:00.00
  Maximum number of retries:      96
  Number of DNS failure retries:  12
  Accounting:                     disabled
  Default router:                 (none)

LOCAL agent settings:
  DECnet delivery retry interval:    0 00:30:00.00
  Maximum number of retries: 96
  Accounting disabled.
  Top headers:
    FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID,
    RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT,
    ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM,
    RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER
  Bottom headers:
    (none)

ROUTER agent settings:
  Automatic percent-hack handling: enabled

JNET agent settings:
  Automatic percent-hack handling: enabled
  BSMTP replies:                   disabled
  Accounting:                      disabled
  Lenient about gatewaying mail:   no
  No mailer username set.

DECnet_SMTP agent settings:
  Retry interval:    0 00:30:00.00
  Maximum number of retries: 96
  Accounting disabled.

SITE agent settings:
  Retry interval:    0 00:30:00.00
  Maximum number of retries: 96

X25_SMTP agent settings:
  Retry interval:    0 00:30:00.00
  Maximum number of retries: 96
  Accounting disabled.

(queens.edu is defined in the DNS as a mail alias for jtk.queens.edu)

 and ucx$ucp show host gives:

     LOCAL database

Host address    Host name

127.0.0.1       LOCALHOST, localhost
152.36.64.251   jlp.queens.edu, jlp, JLP, admin, ADMIN
152.36.64.2     jr.queens.edu, jr, JR
152.36.64.252   jtk.queens.edu, jtk, JTK, james, JAMES, JTK.QUEENS.EDU
152.36.64.1     max.queens.edu, max, MAX
128.109.193.1   ncnoc.concert.net

     BIND database

Server:   128.109.193.1    ncnoc.concert.net

Host address    Host name

192.101.21.1    ncnoc.concert.net
128.109.193.1   ncnoc.concert.net
128.109.131.3   reggae.concert.net
152.36.64.4     pc004.queens.edu
152.36.64.5     pc005.queens.edu
152.36.64.6     pc006.queens.edu
152.36.64.7     pc007.queens.edu
152.36.64.251   jlp.queens.edu
152.36.64.1     max.queens.edu
152.36.64.252   jtk.queens.edu
152.36.64.3     pc003.queens.edu
152.36.64.2     jr.queens.edu

finally sh log mx* gives:

(LNM$SYSTEM_TABLE)

  "MX_DEVICE" = "JTK$DKA300:"
  "MX_DIR" = "MX_DEVICE:[MX]"
  "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]"
  "MX_EXE" = "MX_ROOT:[EXE]"
  "MX_FLQ_DEBUG" = "ON"
  "MX_LOCAL_DEBUG" = "ON"
  "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]"
  "MX_MAILSHR" = "MX_EXE:MX_MAILSHR"
  "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP"
  "MX_MLF_DIR" = "MX_ROOT:[MLF]"
  "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]"
  "MX_MSG" = "MX_EXE:MX_MSG"
  "MX_NODE_NAME" = "jtk.queens.edu"
  "MX_ROOT" = "MX_DEVICE:[MX.]"
  "MX_ROUTER_DEBUG" = "ON"
  "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]"
  "MX_SHR" = "MX_EXE:MX_SHR"
  "MX_SITE_DEBUG" = "ON"
  "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION"
  "MX_SMTP_DEBUG" = "ON"
  "MX_SMTP_DIR" = "MX_ROOT:[SMTP]"
  "MX_SMTP_SERVER_DEBUG" = "ON"
  "MX_VMSMAIL_FROM_FORMAT" = "<!AS@queens.edu>"
  "MX_VMSMAIL_LOCALHOST" = "@jtk.queens.edu"

Any suggestions, comments, any other information I should gather?  HELP!!
Re: MX delivery to black hole
#337
Author: Andreas Moravec
Date: Fri, 18 Dec 1992 14:33
13 lines
1295 bytes
In article <00965227.60447620.32361@jtk.queens.edu>,
 "Richard H. Ault" <ault@queens.edu> writes:
>We are running MX 3.1C, UCX 1.3, and VMS 5.5-2 on new MV3100's.  Accounts were

just a guess: don't you need a special version of UCX 1.3 (1.3A-number)
in combination with VMS 5.5-x ? (or UCX 2.0)
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       KOSMA = Koelner Observatorium fuer SubMillimeter-Astronomie
 Andreas Moravec               TEL      +49 (221) 470 3558
 I. Physikalisches Institut    FAX      +49 (221) 470 5162
 Universitaet zu Koeln         TELEX    888 2291 UNIK D
 Zuelpicher Str. 77            INTERNET Moravec@Ph1.Uni-Koeln.De
 5000 Koeln 41, Germany        X.400    S=Moravec;OU=Ph1;P=Uni-Koeln;A=DBP;C=DE
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads