Link to home
Create AccountLog in
Avatar of intouchsystems
intouchsystemsFlag for United Kingdom of Great Britain and Northern Ireland

asked on

How to route certain emails through a different gateway on Lotus Domino

Hi

I have a requirement to route emails to a certain domain via a different gateway on our IBM Domino server.

Do you know if this is possible at all?

For example.. acme.com needs to go through gateway 192.168.109.254 to an Exchange server on a different site, where as all other email is currently routed though gateway 192.168.109.253.

Do you know what setings I need to configure in the Domino directory, from a IBM Domino/Notes side of things, we are running version 9
ASKER CERTIFIED SOLUTION
Avatar of Sjef Bosman
Sjef Bosman
Flag of France image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of intouchsystems

ASKER

Thanks sjef, do you know of any guides I can follow to try and set this up?

I found this one  - http://www-01.ibm.com/support/docview.wss?uid=swg21420527 which sounds similar to what I need, but when I created it, mail to the domain I need just sits there and doesn't send
Did you kick the router after the change? Or did you restart it? Otherwise it'll take some time (up to 30 minutes?) until it finds the new domain by itself.

Everything is in the Admin Help database, here's a starting point:
http://www-12.lotus.com/ldd/doc/domino_notes/rnext/help6_admin.nsf/f4b82fbb75e942a6852566ac0037f284/7a26e60b625823cf85256c1d003a4d1d?OpenDocument

which also says that you "must also set up a corresponding SMTP Connection document". Maybe that's the missing link? If it is, I'm terribly sorry for the omission...
Ok I think I have this setup now, however when I try and send emails to this domain they are just stuck there, I am getting the following error in the log:

12/07/2013 09:47:20   Router: No messages transferred to 10.180.100.60 (host 10.180.100.60) via SMTP: SMTP Authentication is required by local server but failed
12/07/2013 09:47:20   Router: Failed to connect to SMTP host 10.180.100.60 because SMTP Authentication is required by local server but failed
http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.help.domino.admin.doc%2FDOC%2FH_ENABLING_SMTP_OUTBOUND_AUTHENTICATION_TO_RELAY_HOSTS_OVER.html

If the other server requires authentication (which I find strange), you can set a username and password in the Configuration document. Unfortunately, there's only one such possibility for the whole server.

Can you check why the other server requires authentication? Is it within your company? Maybe they can configure their mail server to accept mails from your IP-address?
Hi Sjef

We already have authentication details in this field as we relay all our email via our ISP. I did wonder if us having this information in would have any effect on this?

I have asked the guys at the other end (within our company, but different country) to allow anonymous authentication on their server.

Maybe this is the problem :

http://smtp25.blogspot.co.uk/2007/12/530-571-client-was-not-authenticated_25.html
Yes, your server is more or less anonymous, although it probably shares some credentials with the other end. Plus, it has a fixed internal IP-address, so I'd expect in-company traffic to be trusted. Maybe they have to create a 2nd connector to allow your server to connect? I know nothing about Exchange, so don't ask me ;-)
Well I set this up, but unfortunately it looks like the server will not connect due to an authentication problem:

15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: Attempting to Connect: Host 10.180.100.60, Port 587, SSL Port 0, Connecting Domain koyo_mail.kbe.co.uk
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: Connection successful
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 220 NRBHEXCASHUB02.nrb.inside Microsoft ESMTP MAIL Service ready at Mon, 15 Jul 2013 10:41:17 -0400
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: CommandEHLO: EHLO koyo_mail.kbe.co.uk
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-NRBHEXCASHUB02.nrb.inside Hello [192.168.109.83]
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-SIZE 25600000
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-PIPELINING
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-DSN
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-ENHANCEDSTATUSCODES
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-STARTTLS
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-AUTH GSSAPI NTLM
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-8BITMIME
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-BINARYMIME
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250 CHUNKING
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: CommandSTARTTLS: STARTTLS
15/07/2013 15:41:18   [140C:001C-23F4] SMTPClient: ReceiveResponse: 220 2.0.0 SMTP server ready
15/07/2013 15:41:24   [140C:001C-23F4] SMTPClient: CommandEHLO: EHLO koyo_mail.kbe.co.uk
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-NRBHEXCASHUB02.nrb.inside Hello [192.168.109.83]
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-SIZE 25600000
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-PIPELINING
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-DSN
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-ENHANCEDSTATUSCODES
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-AUTH GSSAPI NTLM LOGIN
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-8BITMIME
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250-BINARYMIME
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 250 CHUNKING
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: SMTP Authentication is required by local server.  Username: -blank-
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: Attempting to Disconnect:
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: CommandQUIT:
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: ReceiveResponse: 221 2.0.0 Service closing transmission channel
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: Connection terminated successfully
15/07/2013 15:41:25   [140C:001C-23F4] SMTPClient: Disconnecting - SMTP Authentication User Name is missing for host 10.180.100.60.
15/07/2013 15:41:25   Router: No messages transferred to 10.180.100.60 (host 10.180.100.60) via SMTP: SMTP Authentication is required by local server but failed

Not being able to see the Exchange configuration is a little frustrating, as they are saying there is no option to put a username and password in.. Any Exchange exterts able to shed any light on this?

For ref: 192.168.109.83 is our Domino server, 10.180.100.60 is the Exchange server
Did some searching for you: http://social.technet.microsoft.com/Forums/exchange/en-US/711f8e4f-d428-4160-ae4c-33f9446d1846/only-allow-certain-ips-for-incoming-smtp-connection

They talk about an anonymous connection, maybe that's what the receiving end needs in Exchange?
Hi Sjef

I managed to solve the problem. It was sending email out on port 587 and it was this which was requiring authentication. I changed it to port 25 and all the emails sent straight through.

Anonymous authentication was ticked at the Exchange end but this did not seem to make a difference. thanks for your assistance anyway.
Sheesh... And I thought the smarthost required SSL to be used... Should have thought of other possibilities.

So the other end did in fact accept plain SMTP? Or did your server not allow a connection on port 25? Someone must have done that for a good reason, don't you think, so please check the connection to your other gateway.

Well done!