Domino doesn't send mail (but OS find mx)

HI

We have a big problem in our Domino server.

The Domino server cannot send mail to specific domain (not all domain, just a few).

Email still block in the Domino router (mail.box & mail1.box)

with these message:

Router: Failed to connect to SMTP host POLYGON.CA because : 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

I investigate the OS (of Domino server) but evething is find

nslookup

Default Server: srv-dc01.domain.local

Address: 192.168.100.26

set type=mx

polygon.ca

Server: srv-dc01.domain.local

Address: 192.168.100.26

Non-authoritative answer:

polygon.ca MX preference = 30, mail exchanger = mail3.polygon.ca

polygon.ca MX preference = 5, mail exchanger = mail.polygon.ca

polygon.ca MX preference = 20, mail exchanger = mail2.polygon.ca

mail3.polygon.ca internet address = 199.243.85.42

mail.polygon.ca internet address = 69.70.21.61

mail2.polygon.ca internet address = 206.47.108.37

Does any have a clue?

Subject: Domino doesn’t send mail (but OS find mx)

add SMTPclientdebug=1 in notes.ini and check for the errors

also tracert the IP address

Subject: Domino doesn’t send mail (but OS find mx)

It seems that your domino server can’t build up an SMTP connection to one of those 3 servers.

You can invoke the command “tell router show queues” on the cosnole to see what the last error is on the message the domino server wants to send.

But i guess the 3 mail servers of polycon.ca are not accessible for the domino server.

You can try that by useing a telnet command to the 3 polygon.ca servers to see if its possible to get a connection.

Subject: RE: Domino doesn’t send mail (but OS find mx)

Thanks for your quick response Sjaak!

The tellnet respond for all 3 servers.

I don’t think the problem is from the OS or DNS because all tests from Windows server (of the Domino) respond correctly.

Subject: Domino doesn’t send mail (but OS find mx)

Just an idea.

We had the same problem a few weeks a go.

Problem was that the fully qualified host name in the server document was wrong or not known on the OS level.

Check that please !

Regards,

Peter