Exchange2003, Can not send to multi-record SMTP server

I have a problem with my exchange 2003 Server. When I try to send e-mails to customers from a Danish ISP Cybercity I get this message after a few days:


"Could not deliver the message in the time limit specified.  Please retry or contact your administrator."

 

The user I am sending to is on c-mi.dk

 

When looking at the Cybercity configuration I see this:

 

> c-mi.dk
Server:  temp.premitech.net
Address:  192.168.101.64

 

Non-authoritative answer:
c-mi.dk MX preference = 100, mail exchanger = mailgate.cybercity.dk
c-mi.dk MX preference = 10, mail exchanger = ywuser.cybercity.dk

 

mailgate.cybercity.dk   internet address = 212.242.40.53
mailgate.cybercity.dk   internet address = 212.242.40.4
mailgate.cybercity.dk   internet address = 212.242.40.52
ywuser.cybercity.dk     internet address = 212.242.40.146
ywuser.cybercity.dk     internet address = 212.242.40.82

 


When I test it I get this :
   ywuser.cybercity.dk. - 212.242.40.82  [Could not connect: Could not connect to mail server (connection refused by remote mailserver).  NOTE: Per the RFCs, mailservers are allowed to continuously retry this server until it is back online, and not try other MX records (RFC2821 3.9).]
   ywuser.cybercity.dk. - 212.242.40.146  [Could not connect: Could not connect to mail server (connection refused by remote mailserver).  NOTE: Per the RFCs, mailservers are allowed to continuously retry this server until it is back online, and not try other MX records (RFC2821 3.9).]
   ywuser.cybercity.dk. - 212.242.40.147  [Could not connect: Could not connect to mail server (connection refused by remote mailserver).  NOTE: Per the RFCs, mailservers are allowed to continuously retry this server until it is back online, and not try other MX records (RFC2821 3.9).]
   mailgate.cybercity.dk. - 212.242.40.52  [Successful connect: Got a good response [250 Ok]]
   mailgate.cybercity.dk. - 212.242.40.53  [Successful connect: Got a good response [250 Ok]]
   mailgate.cybercity.dk. - 212.242.40.4  [Successful connect: Got a good response [250 Ok]]

 

Apparently  my exchange server does not try all the servers, but keeps trying the first server. Is there anywhere in the exchange configuration that you can change this?

 
hwendtAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
This isn't your problem.

The remote server isn't giving the right failure message to your server - it is giving temporary error instead of a permanent error. Therefore it isn't going to try any other MX records as it hasn't been told that the first one is no longer valid. That is as per the RFCs.

Therefore there is nothing you can do to your Exchange server to force it to try the next servers as it would do that automatically if it was told that the primary server was unavailable.

Simon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.