Outbound Gateway Logs?

Question asked by TJ - 2/1/2024 at 7:19 AM

Unanswered

Hi everyone, I run a SM Ent. instance on a publicly accessible server and I run a free version inside my firewall at another location which is just a relay for internal processes to send email.

The internal, free SM version (both running the 8776) is setup as an Outbound Gateway with the SmarrterMail Gateway enabled, I've made some security changes on my main, public instance and now when I save/check the details on the Outbound Gateway, I get an error message saying "Server received a bad response from the gateway server" - but I can't find anything in either servers logs.

Does anyone have any idea where some more information could be getting logged to for the Gateway setup (on either the gateway or the main server it connects to)?

Thanks in advance, TJ

6 Replies

Reply to Thread

Manuel Martins Replied

2/2/2024 at 5:02 AM

Hi TJ,

We connect to Gateway using 587 Port with TLS and it works fine for us.

Problably you have a problem with the firewall on the Gateway server... are you using NAT or Transparent Bridge ?

Check Firewall security permissions.

TJ Replied

2/2/2024 at 6:54 AM

Thanks Manuel, switching the port & encryption didn't help, but as I first mentioned, I'd like to know where this error is logged to hopefully get more details on the issue itself...

Does anyone know where outbound gateway errors like this would be logged?

Thanks, TJ

Douglas Foster Replied

2/2/2024 at 7:29 AM

All of the flow to an outbound gateway is logged in the Delivery log. Errorlig may have exception data as well

Manuel Martins Replied

2/2/2024 at 7:39 AM

Look in Delivery LOG

Look for connections from the Primary Server IP to the Gateway IP

XXX.XXX.XXX.XXX - Gateway IP

YYY.YYY.YYY.YYY - Primary Server IP

[2024.02.02] 14:33:51.994 [78342444] Initiating connection to XXX.XXX.XXX.XXX

[2024.02.02] 14:33:51.994 [78342444] Connecting to XXX.XXX.XXX.XXX:587 (Id: 1)

[2024.02.02] 14:33:51.994 [78342444] Binding to local IP YYY.YYY.YYY.YYY (Id: 1)

[2024.02.02] 14:33:52.037 [78342444] Connection to XXX.XXX.XXX.XXX:587 from YYY.YYY.YYY.YYY:64217 succeeded (Id: 1)

TJ Replied

2/2/2024 at 11:58 AM

Thanks guys, I can see the connection information in the delivery log and I can see the email being delivered to the main SM instance (and delivered to my external test account), but that "Server received a bad response from the gateway server" error message is no where to be found...

Douglas Foster Replied

2/4/2024 at 2:02 PM

You have probably exposed a limitation of the logging system. I had an inbound gateway and decided to enable SmarterMail gateway mode for sender authentication. But I got the server or password wrong, and suddenly every message was being rejected. Fortunately, I found the mistake pretty quickly because I also controlled the upstream server, but I found nothing in SM that documented the login failure. (The SmarterMail gateway mode does not have a "verify during save" option, but this has now been requested, based on my brief unhappy experience.) Inability to verify sender should cause the message to be accepted for best-effort delivery attempt rather than unconditional rejection.

Back to Community Threads

Please leave this box unchecked

6 Replies

Reply to Thread

Tags

Related Knowledge Base Articles