MX SMTP delivery broken under Multinet V3.3-BETA ???
Gunnlaugur Kristjansson
I am having problems with SMTP delivery on Multinet V3.3-BETA.
I have been trying to debug it but can't see anything wrong except
that some messages don't get through and everything is very slow.
I am running MX v3.3 (not MM) and the error I get is:
Last error: %SYSTEM-W-NOMSG, Message number 00008100
I have tried to reinstall MX but the problem seems to be the same.
Any ideas?
Best regards,
gulli
--
---------------------------------------------------------------------------
Gunnlaugur Kristjansson Email......: gu...@vedur.is
Systems Analyst PSImail....: 274011724200::gulli
Data Processing Division DECUS mail.: EDCHUB::KRISTJANSSON
Icelandic Meteorological Office COMPUSERVE.: 72461,2160
Bustadavegi 9 Telephone..: +354 1 600600
IS150 Reykjavik Telefax....: +354 1 28121
Iceland.
---------------------------------------------------------------------------
Carl J Lydick
=Hi.
=
=I am having problems with SMTP delivery on Multinet V3.3-BETA.
=I have been trying to debug it but can't see anything wrong except
=that some messages don't get through and everything is very slow.
=I am running MX v3.3 (not MM) and the error I get is:
=
= Last error: %SYSTEM-W-NOMSG, Message number 00008100
=
=
=I have tried to reinstall MX but the problem seems to be the same.
=Any ideas?
Have you tried enabling logging of SMTP sessions?
$ DEFINE/SYS/EXEC MX_SMTP_DEBUG TRUE
then try sending an SMTP message and look at the contents of
MX_SMTP_DIR:MX_SMTP_LOG.LOG. That should give you some additional information.
--------------------------------------------------------------------------------
Carl J Lydick | INTERnet: CA...@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
understanding of astronomy is purely at the amateur level (or below). So
unless what I'm saying is directly related to VAX/VMS, don't hold me or my
organization responsible for it. If it IS related to VAX/VMS, you can try to
hold me responsible for it, but my organization had nothing to do with it.
Gunnlaugur Kristjansson
>
> I am having problems with SMTP delivery on Multinet V3.3-BETA.
> I have been trying to debug it but can't see anything wrong except
> that some messages don't get through and everything is very slow.
> I am running MX v3.3 (not MM) and the error I get is:
>
> Last error: %SYSTEM-W-NOMSG, Message number 00008100
>
>
> I have tried to reinstall MX but the problem seems to be the same.
> Any ideas?
>
Hi again.
I would like to add to this the contents of one of the log files
that MX-SMTP writes out. (I did define/system MX_SMTP_DEBUG TRUE)
It's still a puzzle to me :-(
gulli
--
21-DEC-1993 18:10:45.56 Processing queue entry number 13855 on node HAGL
21-DEC-1993 18:10:46.35 Recipient: <BLO...@IFREMER.FR>, route=isgate.is
21-DEC-1993 18:10:46.35 Recipient: <charp...@ATLAS.CNES.FR>, route=isgate.is
21-DEC-1993 18:10:46.35 SMTP_SEND: looking up host name isgate.is
21-DEC-1993 18:10:46.51 SMTP_SEND: Attempting to start session with isgate.is. [130.208.165.63]
21-DEC-1993 18:10:46.67 SMTP_SEND: Connected
21-DEC-1993 18:10:46.97 SMTP_SEND: Rcvd: 220 isgate.is Sendmail 5.65c/ISnet/14-10-91 ready at Tue Dec 21 18:10:46 1993
21-DEC-1993 18:10:47.03 SMTP_SEND: Sent: HELO hagl.vedur.is
21-DEC-1993 18:10:47.24 SMTP_SEND: Rcvd: 250 Hello hagl.vedur.is, pleased to meet you
21-DEC-1993 18:10:47.24 SMTP_SEND: Sent: MAIL FROM:<gu...@vedur.is>
21-DEC-1993 18:10:47.58 SMTP_SEND: Rcvd: 250 <gu...@vedur.is>... Sender ok
21-DEC-1993 18:10:47.58 SMTP_SEND: Sent: RCPT TO:<BLO...@IFREMER.FR>
21-DEC-1993 18:10:47.79 SMTP_SEND: Rcvd: 250 <BLO...@IFREMER.FR>... Recipient ok
21-DEC-1993 18:10:47.80 SMTP_SEND: Sent: RCPT TO:<charp...@ATLAS.CNES.FR>
21-DEC-1993 18:10:48.01 SMTP_SEND: Rcvd: 250 <charp...@ATLAS.CNES.FR>... Recipient ok
21-DEC-1993 18:10:48.34 SMTP_SEND: Sent: DATA
21-DEC-1993 18:10:48.62 SMTP_SEND: Rcvd: 354 Enter mail, end with "." on a line by itself
21-DEC-1993 18:10:48.62 SMTP_SEND: Sent: X-ListName: "Buoy quality control." <buo...@vedur.is>
21-DEC-1993 18:10:48.63 SMTP_SEND: Sent: Warnings-To: <>
21-DEC-1993 18:10:48.63 SMTP_SEND: Sent: Errors-To: gu...@vedur.is
21-DEC-1993 18:10:48.64 SMTP_SEND: Sent: Sender: gu...@vedur.is
21-DEC-1993 18:10:48.64 SMTP_SEND: Sent: Received: from vedur.is by hagl.vedur.is (MX V3.3 VAX) with SMTP; Tue, 21 Dec
21-DEC-1993 18:10:48.64 SMTP_SEND: Sent: 1993 11:23:56 GMT
21-DEC-1993 18:10:48.65 SMTP_SEND: Sent: Received: from isgate.is by vedur.is (4.1/smail2.5/27-06-89); Tue, 21 Dec 93
21-DEC-1993 18:10:48.65 SMTP_SEND: Sent: 11:22:35 GMT
21-DEC-1993 18:10:48.71 SMTP_SEND: Sent: Received: from eldborg.rhi.hi.is by isgate.is (5.65c/ISnet/14-10-91); Tue, 21
21-DEC-1993 18:10:48.77 SMTP_SEND: Sent: Dec 1993 11:22:34 GMT
21-DEC-1993 18:10:48.78 SMTP_SEND: Sent: Received: from hekla.rhi.hi.is by eldborg.rhi.hi.is (5.65c/RHI/10-11-93); Tue,
21-DEC-1993 18:10:48.78 SMTP_SEND: Sent: 21 Dec 1993 11:22:33 GMT
21-DEC-1993 18:10:48.78 SMTP_SEND: Sent: Received: by hekla.rhi.hi.is (AIX 3.2/UCB 5.64/client-1.3) id AA21200; Tue, 21
21-DEC-1993 18:10:48.82 SMTP_SEND: Sent: Dec 1993 11:22:32 GMT
21-DEC-1993 18:10:48.82 SMTP_SEND: Sent: Date: Tue, 21 Dec 1993 11:22:32 GMT
21-DEC-1993 18:10:48.83 SMTP_SEND: Sent: Message-ID: <931221112...@hekla.rhi.hi.is>
21-DEC-1993 18:10:48.84 SMTP_SEND: Sent: To: buo...@vedur.is
21-DEC-1993 18:10:48.85 SMTP_SEND: Sent: From: ECMW...@rhi.hi.is
21-DEC-1993 18:10:48.87 SMTP_SEND: Sent: Reply-To: buo...@vedur.is
21-DEC-1993 18:10:48.87 SMTP_SEND: Sent: Subject: ECMWF buoy stats (wind)
21-DEC-1993 18:10:48.87 SMTP_SEND: Sent:
21-DEC-1993 18:10:48.88 SMTP_SEND: Sent: Posted: Thu, Dec 16, 1993 5:08 AM EST Msg: KGJD-6019-4429
21-DEC-1993 18:10:48.88 SMTP_SEND: Sent: From: ECMWF.OPS
21-DEC-1993 18:10:48.88 SMTP_SEND: Sent: To: buoy.qc
21-DEC-1993 18:10:48.89 SMTP_SEND: Sent: Subj: ECMWF buoy stats (wind)
21-DEC-1993 18:10:48.89 SMTP_SEND: Sent:
21-DEC-1993 18:10:48.89 SMTP_SEND: Sent:
21-DEC-1993 18:10:48.90 SMTP_SEND: Sent:
21-DEC-1993 18:10:48.90 SMTP_SEND: Sent: BUOY MONITORING STATISTICS
21-DEC-1993 18:10:48.90 SMTP_SEND: Sent: MONITORING CENTRE : ECMWF
21-DEC-1993 18:10:48.91 SMTP_SEND: Sent: ELEMENT MONITORED : WIND (DEGREES AND M/S)
21-DEC-1993 18:10:48.91 SMTP_SEND: Sent: AREA : GLOBAL
21-DEC-1993 18:10:49.02 SMTP_SEND: Sent: PERIOD : 15 NOV - 15 DEC 1993
21-DEC-1993 18:10:49.05 SMTP_SEND: Sent: STANDARD OF COMPARISON: FIRST-GUESS FIELD
21-DEC-1993 18:10:49.05 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.08 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.10 SMTP_SEND: Sent: 97 IN DRIFTER CODE, 213 IN SHIP CODE
21-DEC-1993 18:10:49.10 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.10 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.13 SMTP_SEND: Sent: (* DENOTES OBSERVATIONS IN SHIP CODE)
21-DEC-1993 18:10:49.13 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.16 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.16 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.17 SMTP_SEND: Sent: IDENT LAT LONG NOBS NGROSS BIASF BIASD STDF STDD RMSVEC
21-DEC-1993 18:10:49.17 SMTP_SEND: Sent:
21-DEC-1993 18:10:49.18 SMTP_SEND: Sent: 13531 33.6 -19.2 9 0 -0.4 -2 1.3 16 2.1
21-DEC-1993 18:10:49.18 SMTP_SEND: Sent: 13533 32.1 -28.0 8 0 -0.7 8 0.9 24 3.0
A lot of similar lines deleted...
21-DEC-1993 18:18:22.10 SMTP_SEND: Sent: * 62129 53.1 2.2 741 0 1.4 9 1.9 14 3.9
21-DEC-1993 18:18:22.10 SMTP_SEND: Sent: * 62130 53.0 1.7 53 0 0.6 4 2.4 20 3.9
21-DEC-1993 18:18:22.11 SMTP_SEND: Sent: * 62131 58.1 0.1 89 1 0.7 -1 2.3 16 3.6
21-DEC-1993 18:19:25.52 SMTP_SEND: Sent: * 62132 56.5 2.1 72 0 1.0 1 1.9 13 3.0
21-DEC-1993 18:19:25.72 SMTP send failed, sts=0C27804A, sts2=00008100
21-DEC-1993 18:19:25.72 Recipient status=0C27804A for <BLO...@IFREMER.FR>
21-DEC-1993 18:19:25.72 Recipient status=0C27804A for <charp...@ATLAS.CNES.FR>
21-DEC-1993 18:19:27.94 2 rcpts need retry, next try 21-DEC-1993 18:49:27.94
21-DEC-1993 18:19:28.07 *** End of processing pass ***
Dan Wing
>21-DEC-1993 18:10:49.18 SMTP_SEND: Sent: 13531 33.6 -19.2 9 0 -0.4 -2 1.3 16 2.1
>21-DEC-1993 18:10:49.18 SMTP_SEND: Sent: 13533 32.1 -28.0 8 0 -0.7 8 0.9 24 3.0
>
>A lot of similar lines deleted...
>
>21-DEC-1993 18:18:22.10 SMTP_SEND: Sent: * 62129 53.1 2.2 741 0 1.4 9 1.9 14 3.9
>21-DEC-1993 18:18:22.10 SMTP_SEND: Sent: * 62130 53.0 1.7 53 0 0.6 4 2.4 20 3.9
>21-DEC-1993 18:18:22.11 SMTP_SEND: Sent: * 62131 58.1 0.1 89 1 0.7 -1 2.3 16 3.6
>21-DEC-1993 18:19:25.52 SMTP_SEND: Sent: * 62132 56.5 2.1 72 0 1.0 1 1.9 13 3.0
>21-DEC-1993 18:19:25.72 SMTP send failed, sts=0C27804A, sts2=00008100
>21-DEC-1993 18:19:25.72 Recipient status=0C27804A for <BLO...@IFREMER.FR>
>21-DEC-1993 18:19:25.72 Recipient status=0C27804A for <charp...@ATLAS.CNES.FR>
>21-DEC-1993 18:19:27.94 2 rcpts need retry, next try 21-DEC-1993 18:49:27.94
>21-DEC-1993 18:19:28.07 *** End of processing pass ***
Error 0C27804A translates to:
%MX-E-NOCOMPLETE, message transmission could not be completed
How much data are you trying to send the remote system? I noticed the
transmissions began at about 18:10:49, and continued for a long time (8
minutes?) and then there were a couple of lines close together, and then
about three seconds elapsed between two transmissions, and then you got the
"SMTP send failed" line......
I would try enabling MultiNet's outgoing SMTP -- do this by hand (to
prevent the incoming SMTP agent from starting up). Then you should be able
to send the message to SMTP%"user@host" and see if MultiNet can get it
through -- if it does make it, then the problem is with MX. Right now, it
appears to me (especially after sending 8 minutes worth of data) you might
be filling up the destination system's spool area and it can't handle it
very well... Just a guess, though...
-Dan Wing, Systems Administrator, University Hospital, Denver
dw...@uh01.colorado.edu or wi...@eisner.decus.org
Carl J Lydick
=21-DEC-1993 18:19:25.72 SMTP send failed, sts=0C27804A, sts2=00008100
Status 0C27804A is:
%MX-E-NOCOMPLETE, message transmission could not be completed
I can't, on a system running VMS v5.4-2 and Multinet, find a message definition
for status 00008100.
Gunnlaugur Kristjansson
A little bit more info.
I talked to the system admin on the destination system and it it seems
that it is my node that is closing the connection. His log file says
something like "Unexpected closure of connection from node hagl.vedur.is"
(not exact wording but it does not say much more).
The problem started with the next message that was sent AFTER I installed
Multinet v3.3-BETA. Multinet came up about 15-dec-1993 22:38 and the
first message that is not going out is at 16-dec-1993 00:07. Since then
all long messages get in trouble. Sometimes they get through. And the size
of the messages is 80-100KB. I have been sending such messages every
day for about 2 years now, so I do not think it is a size problem.
The only part that has changed recently is Multinet.
I have not tried to enable Multinet's SMTP yet and test that. Is
there a way to control the routing of messages as can be done in MX?
I route all messages that are not local through a node called
isgate.is. It's that node that hagl.vedur.is is talking to and failing.
> -Dan Wing, Systems Administrator, University Hospital, Denver
> dw...@uh01.colorado.edu or wi...@eisner.decus.org
Best regards,
gulli
--
Gunnlaugur Kristjansson
> I route all messages that are not local through a node called
> isgate.is. It's that node that hagl.vedur.is is talking to and failing.
Now I tried to use a local node as route and it worked perfectly.
So, here is the layout.
VMS/MULTINET/MX SUN SPARC/2
------------- ---------------
hagl.vedur.is ragnar.vedur.is
------------- ---------------
! !
---------------------------------------------------------
!
-------------
PC-ROUTE
-------------
/
\
/
------------
PC-ROUTE
------------
!
-----------------------------------------------------------
! !
---------- ------------------
CISCO isgate.is
---------- ------------------
/ SUN SPARC/2
\
Out to the rest
of the Internet.
If MX is set up in such a way that it uses isgate.is as route
path "*" SMTP /route="isgate.is"
then large messages don't get through. If a local machine such as
ragnar.vedur.is is used as route
path "*" SMTP /route="ragnar.vedur.is"
then the messages get through. ragnar.vedur.is uses isgate.is as route
so the messages always go via isgate.is in the end. Now no messages are
waiting wherever I look. So isgate.is is doing its job.
The only thing that changed in the begining was that I installed
Multinet v3.3-BETA on hagl.vedur.is. Then the troubles started.
With changing the route the problem is not solved, just put aside
for the time being.
I havesome log files which could be of interest if needed, but there are no
messages that indicate what is going on. Just about the only conclusion
I can get from reading the log files is that SMTP decided that this had been
going on long enough and just quits.
Best regards,
gulli
--
Dan Wing
No; I was only recommending enabling MultiNet's outgoing SMTP for testing
so you could either duplicate the prblem (demonstrating a problem with
MultiNet, so you could call the TGV guys and tell them about it) or you
could fail to duplicate the problem, in which case you would have found
a problem with MX and MultiNet V3.3-beta.
Please note, though, that MX doesn't directly talk to MultiNet (or any
other TCP/IP package) -- MX talks to NETLIB which interfaces with your
underlying TCP/IP package. So if there is an interoperability problem, it
will effect MX, NEWSRDR, and probably any other software that uses NETLIB
to interface with the underlying TCP/IP package.
I'm betting, though, that the problem is something within MultiNet, and not
NETLIB (or MX). My main feeling the problem is likely with MultiNet is
that you're running a beta-test version of MultiNet V3.3.
Dan Wing
>
>path "*" SMTP /route="isgate.is"
>
>then large messages don't get through. If a local machine such as
>ragnar.vedur.is is used as route
>
>path "*" SMTP /route="ragnar.vedur.is"
>
>then the messages get through. ragnar.vedur.is uses isgate.is as route
>so the messages always go via isgate.is in the end. Now no messages are
>waiting wherever I look. So isgate.is is doing its job.
Well, if when you're using isgate.is for all your mail, it (or some
interaction between your node and isgate.is) causes the SMTP to fail, I
wouldn't say "isgate.is is doing its job" -- it may be, but it also may
be having some sortof weird problem; maybe MultiNet V3.3-beta isn't waiting
long enought for a TCP acknowledgement...??
>The only thing that changed in the begining was that I installed
>Multinet v3.3-BETA on hagl.vedur.is. Then the troubles started.
>With changing the route the problem is not solved, just put aside
>for the time being.
Are isgate.is and ragnar.vedur.is running the same version of Sendmail,
with similar configurations and the same amount of space on their spool
areas?
>I havesome log files which could be of interest if needed, but there are no
>messages that indicate what is going on. Just about the only conclusion
>I can get from reading the log files is that SMTP decided that this had been
>going on long enough and just quits.
Again, I'd encourage you to send one of those big mail messages to
<system%hagl.v...@isgate.is> and <system%hagl.v...@ragnar.vedur.is>
and see if one of them fails -- try this with both MX and using MultiNet's
outgoing SMTP agent.