Messaging Gateway does not log destination IP when faiing to deliver a message
search cancel

Messaging Gateway does not log destination IP when faiing to deliver a message

book

Article ID: 402368

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

When looking at the Message Audit Logs (MAL) or the MTA logs in Messaging Gateway (SMG), a failure to deliver a message is logged in both the MTA logs at Information level and in the Message Audit Logs as a TRANSFAIL even but neither contain the IP address or hostname of the system SMG failed to deliver the message to.

Current logging

2025 Jun  2 11:06:00 -03 (info) ecelerity: [79115] ML-DELIVERY_ATTEMPT: Message ID: 00/BB-13579-B279D386, Audit ID ac1062c0-1fc9b7000001350b-7e-683d972bdc37, Delivery attempted, sender: [email protected], recipient: [email protected]
2025 Jun  2 11:06:00 -03 (info) ecelerity: [79115] ML-TRANSFAIL: Message ID: 00/BB-13579-B279D386, Audit ID ac1062c0-1fc9b7000001350b-7e-683d972bdc37, Temporary delivery failure, sender: [email protected], recipient: [email protected], Detail: 451 4.4.2 [internal] connection closed by remote host

Requested change

2025 Jun  2 11:06:00 -03 (info) ecelerity: [79115] ML-DELIVERY_ATTEMPT: Message ID: 00/BB-13579-B279D386, Audit ID ac1062c0-1fc9b7000001350b-7e-683d972bdc37, Delivery attempted, sender: [email protected], recipient: [email protected], destination: 10.0.0.1
2025 Jun  2 11:06:00 -03 (info) ecelerity: [79115] ML-TRANSFAIL: Message ID: 00/BB-13579-B279D386, Audit ID ac1062c0-1fc9b7000001350b-7e-683d972bdc37, Temporary delivery failure, sender: [email protected], recipient: [email protected], destination: 10.0.0.1, Detail: 451 4.4.2 [internal] connection closed by remote host

Resolution

This will be addressed in a future SMG release as an enhancement to the product.