Problem with mail routing

HCL Domino Domino Forum
1

Hi there,

I am having a problem with mail routing among servers at a client.

They have a server (mail1) that has mailboxes and does SMTP routing to external domains and receives emails from external domains.

I have recently added a new server (webmail) for web access and it is not allowed to route external emails. When a user sends external emails from iNotes on webmail, I want the email to go to mail1 then to the external address.

The problem is that when I send an email from the webmail server, it gets stuck in the mail.box of webmail and fails with message “no route found to ”.

In the server document for mail1, Basics tab, Routing tasks enabled are Mail Routing and SMTP Mail Routing

In the server document for webmail, Basics tab, the only Routing tasks enabled is Mail Routing

In the connection documents from mail1 to webmail, Routing task is set to “-None-”

At one point, I even created a connection document from webmail to mail1, set Routing task to “Mail Routing” and router type to push only, but it did not work.

Btw, when external emails are sent to a user, they get delivered to mail1, replicated to webmail and show up on iNotes, so replication is being done correctly…

Does anyone have any suggestions please?

2

Subject: Thank you

Thank you D Porter.

I will try it out and let you know.

3

Subject: Finally got it to work

Hi. After lots of frustration, I finally got it to work.

First, I found this in the server log of webmail/acme:

10/05/2017 10:39:02 AM Router: Connection from server MAIL1/ACME not used; Server not in local domain.

10/05/2017 11:57:20 AM Router: Transferring mail to domain 192.168.2.20 (host 192.168.2.20 [192.168.2.20]) via SMTP
10/05/2017 11:57:20 AM Router: No messages transferred to 192.168.2.20 (host 192.168.2.20) via SMTP
10/05/2017 11:57:20 AM Router: Error transferring message 002BB1C0 via SMTP to 192.168.2.20 554 Relay rejected for policy reasons.

I excluded webmail/acme from anti relay checks in the configuration document of mail1/acme and this got rid of the second error.

As for the first error, an internet search indicated that the problem is with connection, server or configuration documents, especially the domain or ip that may be wrong.

I double and triple checked the connection, server and configuration documents on mail1 and they were all correct.

Also, if I type “trace mail1” or “trace mail1/acme” from the console of webmail1, it returns the correct IP and connects successfully to mail1.

The administration server is mail1 and it replicates the names.nsf to all other servers. So, any changes are done on the names.nsf of mail1 and this is then pushed to all the other servers.

I realised that when I open the names.nsf on webmail1 and check the server doc of mail1 (Ports, Notes Network Ports, Net Address), there is a host name (mail1.acme.mu)

If I open the server doc of mail1 on the names.nsf on mail1 there is an IP address in Ports, Notes Network Ports, Net Address. (192.168.2.20)

There are no replication errors, any new documents I create on mail1’s names are correctly replicated.

I even modified the server doc and replicated but to no effect.

In the end, I shut down webmail1. Copied the names.nsf from mail1 to webmail1 (at OS level) and started webmail1.

It then got the correct value in Ports, Notes Network Ports, Net Address and mail routing is now working.

I also removed the ip of mail1 from the relay field in webmail1’s config document and it is working.

4

Subject: Two options

You have two options.

Option 1:

  • Create a notes mail connection document from the webmail server to the mail1 server.

  • Create an SMTP connection document from mail1 server to the IP that you have in the config document for the field Relay host for messages leaving the local internet domain. The destination server can be anything but set the domain to Internet (or something like it)

  • Create a Foreign SMTP Domain document with the Internet Domain field set to . and the Domain name field to Internet (as above)

Option 2:

  • In the config document for webmail set the field Relay host for messages leaving the local internet domain to the IP of mail1 and make sure mail1 permits relaying from the IP of webmail.