Strange mail routing issue

HCL Domino Domino Forum
1

Hi All,

We have different servers in 2 locations, same NNN.

M1 and M2.

If user sends a mail From M1 to M2

 Mails delivering fine.

If user sends a mail From M2 to M1

Mails are pending in the M2 Server.

Internal M2 mails working fine. The internet mails are configured to send directly from the server. This also working perfectly.

Can any one help me on this.

Regards,

Menon JayK.

2

Subject: Strange mail routing issue

Out of top of my head I can think of two quite simple solutions:

  1. Your M2 server doesn’t know where M1 is (M1 however does know where M2 is so it sends emails there). In Domino Administrator go to Configuration Tab, then Server, Connections and find in M2 connections find documents pointing to M1. You should have one which inside on Replication tab has Mail routing task. Also make sure that in this document on Basic tab you have a good IP address for M1 server. Maybe you have a mistake there (like 110 instead of 10).

  2. In Domino Directory your M1 users documents might say that their email databases are located on M2. M2 then wouldn’t send them to M1 but instead it would look for the databases on itself. In this case M1 users could send emails but they wouldn’t be able to receive any from M2, but also from the internet probably. I’m not sure how it would work for internal mail between two M1 users and for internet mail if M1 is the one server that receives internet mail and sends it further. To check this simply find one user to whom you can’t send email from M2 and in Domino Administrator go to People&Groups tab, then Domino Directories, Your domain’s address book, people and locate the user. Open his/her document and make sure that mail server is M1 and not M2.

Now as I have said, these are simple solution so they might not work, but it’s worth to check them if you haven’t already.

3

Subject: Strange mail routing issue

I’ve came across a problem similar to this before. Very strange but true.

What I did was:

Delete the server document and recreate it back. Configure it to the same configuration and the problem disappeared.

Perhaps this solution may assist…

syahril

INTERXS SDN BHD