Easiest fix Jim is to add a retry interval with problem Domains until they
beef up their infrastructure.
Setup a programs doc in the NAB to do a -c "route domain.com"
with a retry interval that is say 1 minute.
Program name:
server
Enabled/disabled:
Enabled
Command line:
-c "route domain"
Run at times:
each day
Server to run on:
myserver/domain
Repeat interval of:
1 minutes
Comments:
Days of week:
Sun, Mon, Tue, Wed, Thu, Fri, Sat
Sean
domino400-request@xxxxxxxxxxxx
Sent by: domino400-bounces+seanmurphy=bedbath.com@xxxxxxxxxxxx
04/23/2007 12:00 PM
Please respond to
domino400@xxxxxxxxxxxx
To
domino400@xxxxxxxxxxxx
cc
Subject
Domino400 Digest, Vol 5, Issue 70
Send Domino400 mailing list submissions to
domino400@xxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/domino400
or, via email, send a message with subject or body 'help' to
domino400-request@xxxxxxxxxxxx
You can reach the person managing the list at
domino400-owner@xxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Domino400 digest..."
Today's Topics:
1. Mail routing Issue (JWGrant@xxxxxxxxxxxxxxx)
2. Re: Mail routing Issue (Patrick Trapp)
3. Re: Mail routing Issue (JWGrant@xxxxxxxxxxxxxxx)
4. Re: Mail routing Issue (rob@xxxxxxxxx)
5. Re: Mail routing Issue (JWGrant@xxxxxxxxxxxxxxx)
6. Re: Mail routing Issue (rob@xxxxxxxxx)
----------------------------------------------------------------------
message: 1
date: Mon, 23 Apr 2007 10:56:46 -0400
from: JWGrant@xxxxxxxxxxxxxxx
subject: Mail routing Issue
Hello all;
We have been experiencing an issue with sending mail to one of our clients
mail domain. Our client mail servers are extremely taxed (fortune 10
company) and
periodically we see our mail server connect to the remote mail server and
the remote mail server refuses the connection.
Here is an excerpt from our mail server log;
04/23/2007 09:00:05 Router: No messages transferred to
"CLIENTDOMAIN.COM" (host mx1.imr.CLIENTDOMAIN.COM) via SMTP: The server is
not responding. The server may be down or you may be experiencing network
problems. Contact your system administrator if this problem persists.
We have telneted via port 25 to the remote mail server and sometimes it
works other times the server refuses the connection.
Initial blame was that we were specifying an invlauid email address (very
lame reponse), we assured them that this was not the case. They then
shifted
blame for the issue to our Lotus Notes MTA not being RFC1123 compliant. We
provided the logs and showed them that out MTA was in fact
moving to alternate MX records.
They since have come back and communicated the following;
"One issue we've seen previously with Lotus Notes is that it will often
try only one A record from each entry in a given MX list. We've run into
this specific issue a few times in the past specifically with Lotus Notes
MTAs. One option we've considered in the past for this situation is to
restructure the MX list for CLIENTDOMAIN.com so that it includes each of
the hosts as a separate entry. I'd be happy to pursue that with our
internal mail infrastructure team, although it will have to go through
change control which will take a minimum of about four weeks.
One suggestion as a possible bandaid in the meantime would be to establish
a separate routing entry in your system for CLIENTDOMAIN.com directing it
to the MX list for "imr.CLIENTDOMAIN.com". The domain
imr.CLIENTDOMAIN.com resolves via the same type of MX list we'll be
suggesting for updating CLIENTDOMAIN.com's to use."
We have been experiencing severe mail delays in routing mail to this
domain. We have resorted to running an agent every 15 minutes to bounce
our mail server in order to force our MTA to attempt to deliver the queued
messages again.
I do not believe that the issue is with our server but with our clients
servers.
Any suggestions for a work around would be great.
Thanks in advance
Jim Grant
------------------------------
message: 2
date: Mon, 23 Apr 2007 10:04:18 -0500
from: "Patrick Trapp" <ptrapp@xxxxxxxxxxxx>
subject: Re: Mail routing Issue
No ideas right off, but it might help to know what versions you are
running of the operating system and Domino.
Patrick
JWGrant@xxxxxxxxxxxxxxx
Sent by: domino400-bounces+ptrapp=nex-tech.com@xxxxxxxxxxxx
04/23/2007 09:56 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
To
<domino400@xxxxxxxxxxxx>
cc
Subject
Mail routing Issue
Hello all;
We have been experiencing an issue with sending mail to one of our clients
mail domain. Our client mail servers are extremely taxed (fortune 10
company) and
periodically we see our mail server connect to the remote mail server and
the remote mail server refuses the connection.
Here is an excerpt from our mail server log;
04/23/2007 09:00:05 Router: No messages transferred to
"CLIENTDOMAIN.COM" (host mx1.imr.CLIENTDOMAIN.COM) via SMTP: The server is
not responding. The server may be down or you may be experiencing network
problems. Contact your system administrator if this problem persists.
We have telneted via port 25 to the remote mail server and sometimes it
works other times the server refuses the connection.
Initial blame was that we were specifying an invlauid email address (very
lame reponse), we assured them that this was not the case. They then
shifted
blame for the issue to our Lotus Notes MTA not being RFC1123 compliant. We
provided the logs and showed them that out MTA was in fact
moving to alternate MX records.
They since have come back and communicated the following;
"One issue we've seen previously with Lotus Notes is that it will often
try only one A record from each entry in a given MX list. We've run into
this specific issue a few times in the past specifically with Lotus Notes
MTAs. One option we've considered in the past for this situation is to
restructure the MX list for CLIENTDOMAIN.com so that it includes each of
the hosts as a separate entry. I'd be happy to pursue that with our
internal mail infrastructure team, although it will have to go through
change control which will take a minimum of about four weeks.
One suggestion as a possible bandaid in the meantime would be to establish
a separate routing entry in your system for CLIENTDOMAIN.com directing it
to the MX list for "imr.CLIENTDOMAIN.com". The domain
imr.CLIENTDOMAIN.com resolves via the same type of MX list we'll be
suggesting for updating CLIENTDOMAIN.com's to use."
We have been experiencing severe mail delays in routing mail to this
domain. We have resorted to running an agent every 15 minutes to bounce
our mail server in order to force our MTA to attempt to deliver the queued
messages again.
I do not believe that the issue is with our server but with our clients
servers.
Any suggestions for a work around would be great.
Thanks in advance
Jim Grant
midrange.com
