Re: Mail routing Issue

[JWGrant@xxxxxxxxxxxxxxx]

We have not tested from another email account but we have tested 
connecting to the remote 
mail server via telnet port 25 and our connection gets rejected 
periodically as well.






AJ.McCartan@xxxxxxxxxxx 
Sent by: domino400-bounces+jwgrant=pdpgroupinc.com@xxxxxxxxxxxx
04/23/2007 01:32 PM
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






Have you tested their Domino theory by sending mail from another 
non-domino account? 
- If you have a unix box internally running standard sendmail,

or if you get desperate - cause this is really tedious way to prove a 
point

Create an account on external service (gmail yahoo whatever), then create 
a forwarder to the problem customers account

Have a willing volunteer email to the original recipient as well as the 
other external mail account.  Whenever they send a message to 
bigcompany.com
See which email gets there first. 
If the isp mail gets there first  than maybe you are to blame. 
If not then I suggest that maybe bigcompany.com has some explaining to do.

aj mccartan
enterprise messaging
(602)534-6799




Gary.Wade@xxxxxxxxxxxxxxxx 
Sent by: domino400-bounces+aj.mccartan=phoenix.gov@xxxxxxxxxxxx
04/23/2007 10:15 AM
Please respond to
Lotus Domino on the iSeries / AS400 <domino400@xxxxxxxxxxxx>


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

Subject
Re: Mail routing Issue






We've received several instances over the last month like yours and 
looking through our firewall logs we've found most being rejected by the 
recipient's location either their firewall or a sub-service so we call 
them and have them contact their IT people and generally that resolves the 


problem.  Just FYI



JWGrant@xxxxxxxxxxxxxxx 
Sent by: domino400-bounces+gary.wade=cityoforlando.net@xxxxxxxxxxxx
04/23/2007 10: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