SMTP of UCX and MX conflict
k...@ycvax.york.cuny.edu
>
>The UNIX machine does not receive the incoming mail for some reason. We would
>like it to receive mail.
>
>What I would like to do is to configure YCVAX locally ( using either MX or UCX)
>as a forwarder. YCVAX has been named as forwarder for the UNIX machine
>somewhere in the Internet nameserver. However, locally I have done nothing to
>this effect.
>
>Hope it is not as vague as in my previous statement.
>
> You will need to at least have a PATH definition for the UNIX system
> that specifies it should go SMTP. Turning on MX Router debugging (by
> define/sys/exec mx_router_debug true) would then show you what MX
> Router is doing with the mail.
> Hunter
Should I add a path in config.mcp like
DEFINE PATH "sun1.york.cuny.edu" SMTP
BTW the ip address of ycvax.york.cuny.edu is 198.61.16.1
the ip address of sun1.york.cuny.edu is 198.61.16.3
I am including the mail received from postmaster when I tried to send mail to
sun1.
Here is the mail:
From: MX%"Postm...@ycvax.york.cuny.edu" 20-DEC-1993 19:41:15.37
To: KAM
CC:
Subj: SMTP delivery error
Return-Path: <>
Date: Mon, 20 Dec 1993 19:41:09 EST
From: SMTP delivery agent <Postm...@ycvax.york.cuny.edu>
To: <k...@ycvax.york.cuny.edu>
Subject: SMTP delivery error
Note: this message was generated automatically.
A problem occurred during SMTP delivery of your message.
Error occurred sending to the following user(s):
<kam...@sun1.york.cuny.edu> (via sun1.york.cuny.edu):
%MX_SMTP-F-TRANSACTION_FAI, transaction failed
Transcript:
Rcvd: 220 ycvax MX V3.3 VAX SMTP server ready at Mon, 20 Dec 1993 19:41:07 EST
Sent: HELO ycvax
Rcvd: 250 Hello, ycvax
Sent: MAIL FROM:<k...@ycvax.york.cuny.edu>
Rcvd: 250 MAIL command accepted.
Sent: RCPT TO:<kam...@sun1.york.cuny.edu>
Rcvd: 250 Recipient okay (at least in form)
Sent: DATA
Rcvd: 354 Start mail input; end with <crlf>.<crlf>
Rcvd: 554 Received too many times by this host.
Sent: QUIT
Rcvd: 221 ycvax Service closing transmission channel
========================================================================
Message follows.
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:41:03 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:59 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:53 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:48 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:44 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:39 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:35 EST
Received: from ycvax by ycvax (MX V3.3 VAX) with SMTP; Mon, 20 Dec 1993 19:40:30 EST
Received: by ycvax.york.cuny.edu (MX V3.3 VAX) id 23236; Mon, 20 Dec 1993 19:40:26 EST
Date: Mon, 20 Dec 1993 19:40:25 EST
From: k...@ycvax.york.cuny.edu
To: kam...@sun1.york.cuny.edu
Message-ID: <009774F8.87...@ycvax.york.cuny.edu>
Subject: ldsklfj
This is from ycvax
Hunter Goatley, WKU
>
>Should I add a path in config.mcp like
>
>DEFINE PATH "sun1.york.cuny.edu" SMTP
>
>BTW the ip address of ycvax.york.cuny.edu is 198.61.16.1
> the ip address of sun1.york.cuny.edu is 198.61.16.3
>
To be safe, you should also include DEFINE PATH lines for both of
these using the numeric IP address:
MCP> DEFINE PATH 198.61.16.1 LOCAL
MCP> DEFINE PATH 198.61.16.3 SMTP
>I am including the mail received from postmaster when I tried to send mail to
>sun1.
[...]
> Rcvd: 220 ycvax MX V3.3 VAX SMTP server ready at Mon, 20 Dec 1993 19:41:07 EST
> Sent: HELO ycvax
> Rcvd: 250 Hello, ycvax
Adding the DEFINE PATH will keep MX from delivering it to itself.
Also, as documented in the MX release notes
(SYS$HELP:MX033.RELEASE_NOTES), you need to change your UCX
configuration to list your fully-qualified domain name (FQDN) first;
right now, you have YCVAX defined first, which is what UCX tells you
to do. Info included below.
Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goath...@ALPHA.WKU.EDU (or goath...@WKUVX1.BITNET)
-------------------------------------------------------------------------------
1.3 VMS/ULTRIX Connection Notes
If you are using DEC VMS/ULTRIX Connection (UCX) V1.2
through V2.0, you should review your UCX configuration
to ensure that you are using your fully-qualified
domain name (FQDN) as your primary local host name
in your UCX host table. If you followed the UCX
documentation when configuring UCX with UCX$CONFIG,
it is highly likely that you did not specify your FQDN
as your primary host name.
If your abbreviated host name is listed as the primary
in your UCX host table, then messages sent from the
local system will go out with an unreplyable return
address. To check your local host name, use the UCX
utility:
$ UCX
UCX> SHOW HOST/LOCAL x.x.x.x ! use your IP address here
To ensure that your FQDN is the primary host name for
your address, use the UCX commands:
UCX> SET NOHOST x.x.x.x ! use your IP address here
UCX> SET HOST "full.qual.dom.name"/ADDR=x.x.x.x/ALIAS="abbrev"
You will be asked for confirmation on the SET NOHOST
command. Substitute your FQDN and IP address in the
SET HOST command, and if you would still have your
shortened host name in the host table, use the /ALIAS
qualifier, as shown.
Once you have updated your host table, you
should review the file SYS$MANAGER:UCX$INET_SET_
INTERFACES.COM and replace all instances of your
abbreviated host name with your FQDN.
Note: Remember that UCX is case sensitive with regard
to host names!