Symptoms

OpenManage Enterprise leverages the Simple Mail Transfer Protocol (SMTP) configuration to perform various email actions. Emailing alerts through an alert policy.Forwarding report data as an email.Sending email notifications when certain tasks are completed. Administrators will notice that these email actions are no longer working after the following operations: After successfully migrating from version 3.10.x to version 4.0/4.1Restoring from a 4.x backup file Report task showing failure to send report email to recipients. Failed to send report to email recipients The event-processing service log shows an exception error when an alert policy triggers an email action. [WARN ] 2024-02-01 17:54:07.153 [EMAIL-child-action-worker-0] - Entered resolveFQDNByResolveConf() - host name: mail.domain.tld [WARN ] 2024-02-01 17:54:07.337 [EMAIL-child-action-worker-0] - List of IP addresses: [192.168.11.5, fd00:11::5] [WARN ] 2024-02-01 17:54:07.337 [EMAIL-child-action-worker-0] - Exiting getAllIPsByName() [ERROR] 2024-02-01 17:54:07.358 [EMAIL-child-action-worker-0] - Invalid Destination Address null [ERROR] 2024-02-01 17:54:07.366 [EMAIL-child-action-worker-0] - EmailChildWorkerVerticle::handleSendEmail: Exception while sending email! java.lang.NullPointerException: null at com.dell.enterprise.common.integration.lib.action.reactiveactions.reactiveactionemail.EmailChildWorkerVerticle.handleSendEmail(EmailChildWorkerVerticle.java:126) ~[reactiveactionemail-0.0.1-SNAPSHOT.jar:?] at io.vertx.core.impl.AbstractContext.dispatch(AbstractContext.java:100) ~[vertx-core-4.1.6.jar:4.1.6] at io.vertx.core.impl.WorkerContext.lambda$emit$0(WorkerContext.java:59) ~[vertx-core-4.1.6.jar:4.1.6] at io.vertx.core.impl.WorkerContext.lambda$execute$2(WorkerContext.java:104) ~[vertx-core-4.1.6.jar:4.1.6] at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) ~[vertx-core-4.1.6.jar:4.1.6] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_382] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_382] at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.97.Final.jar:4.1.97.Final] at java.lang.Thread.run(Thread.java:750) ~[?:1.8.0_382]

Cause

OpenManage Enterprise 4.x has a newer SMTP configuration model that is expecting a new required 'timeout' configuration parameter. When older configuration data is migrated from 3.10, it does not contain the timeout value or the authentication credentials. Also, the SMTP authentication credentials, if used previously, are not refreshed post migration or after restoring from backup.

Resolution

Recover from this condition by editing the existing Email Configuration from the application settings in the UI. Browse to Application Settings -> Alerts and expand the Email Configuration section.If leveraged, reenter the authentication password.Next, modify the SMTP Timeout value.Click apply to save the settings.Lastly, connect to the virtual console and restart the services from the Text User Interface (TUI). After the service restart is completed, the previous missing SMTP configuration data is updated and email actions will resume.

Support Cases