× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Lotus Domino (r) Server (Release 6.5.5FP1 for OS/400) 04/23/2007 11:17:13
OS/400 Version 5.4 Cumulative Package 7002

Jim W Grant
Sr. Vice-President, Chief Information Officer
Web: www.pdpgroupinc.com
Email: JWGrant@xxxxxxxxxxxxxxx
Office: (410)584-0339
Fax: (410)584-0339





"Patrick Trapp" <ptrapp@xxxxxxxxxxxx>
Sent by: domino400-bounces+jwgrant=pdpgroupinc.com@xxxxxxxxxxxx
04/23/2007 11:04 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>


To
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>
cc

Fax to

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.