search cancel

Finding several unexpected failures in the emailgtw log for some email addresses

book

Article ID: 202937

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Finding failures for [email protected] in the emailgtw log.  This is not a valid email address, so errors are caused in the logs.  We cannot find why an email is trying to be sent to [email protected]  We have searched through the nas and cannot find an Auto Operator with [email protected] in it.

Oct 21 10:08:51:171 emailgtw: RCPT TO:<[email protected]>
Oct 21 10:08:56:183 emailgtw: 550 5.7.54 SMTP; Unable to relay recipient in non-accepted domain
Oct 21 10:08:56:183 emailgtw: RCPT TO:<[email protected]>
Oct 21 10:09:01:198 emailgtw: 501 5.1.3 Invalid address
Oct 21 10:09:01:198 emailgtw: RSET
Oct 21 10:09:06:213 emailgtw: 250 2.0.0 Resetting
Oct 21 10:09:06:213 emailgtw: (send_it) smtp_send failed - 554 One or more recipients failed

Another error:

Nov  5 10:35:27:095 emailgtw: (get_nimuser_addr) error from hub is: invalid argument, retry count is 1
Nov  5 10:35:27:095 emailgtw: (ht_find_profile) did not find '[email protected]<company.com>'
Nov  5 10:35:27:095 emailgtw: (get_profile_addr) profile [email protected]<company.com> not found
Nov  5 10:35:27:095 emailgtw: (get_nimuser_addr) looking up [email protected]<company.com>
Nov  5 10:35:27:095 emailgtw: (ht_find_profile) did not find '[email protected]<company.com>'
Nov  5 10:35:27:095 emailgtw: (get_nimuser_addr) did not find [email protected]<company.com>, checking hub

Environment

Release : 20.1

Component : UIM - EMAILGTW

emailgtw - any version

Cause

- space in the email address in the nas AO Profile email action

- invalid email address for an employee that is no longer with the company

Resolution

There were 2 issues:

1) A nas AO profile had a space in the email address and that was causing the [email protected] error in the log. In he nas.cfg the AO profile action = EMAIL had “NimBUS [email protected]<company>.com”.  It was corrected to “[email protected]<company>.com”

2) A nas AO profile was trying to send to a defunct email address, for an employee that no longer works for the company.

After the corrections, the errors stopped in the emailgtw.log.