Email Notification Configuration problems

[shortstop20_apc]

This was originally posted on APC forums on 2/12/2014

---

Hello,

We have about 100 APC UPS devices here on campus. All are monitored using Network Management cards. Some are older versions, some are newer, so they have a mix and match of firmware as well.

Recently, after updating all of the "UPS Network Management Card 2" cards on campus to  v6.0.6 I noticed my email notifications sent from cards running v6.0.6 showed the sender as my email address. Older cards running v3.7.2 are still sending out Notification Emails as normal, they use the email address I specify under "From Address".

Here's the configuration I am using on all cards, regardless of software version.

DNS server is the same on all cards.

From Address: *Name-of-UPS@ourdomain.com*    <-------------This is what I should see as the "From" address when I receive a notification from the UPS, I'm seeing my email address instead.

SMTP Server: *hostname of our email server*

Port: 25

No Authentication

Use SSL/TLS: Never

Require CA Root Certificate: Not enabled(unchecked)

Under the Recipients tab:

To Address: *myemailaddress@ourdomain.com*

Format: Long

Server: Recipient

No Authentication

Require CA Root Certificate: Not enabled(unchecked)

Any help is appreciated.

Thanks,

Joel

[BillP]

This reply was originally posted by Angela on APC forums on 2/12/2014

---

How did you configure the NMC2's for notifications - did you load a config.ini from an older card on to the new management card? Or configure these from scratch via the web?

It'd also be helpful to see a config.ini file, if possible, from both systems if you can. (Instructions here on how to download config.ini -> How can I download Event, Data, Configuration, and Debug files from my Network Management Card? | FA...)

[shortstop20_apc]

This was originally posted on APC forums on 2/12/2014

---

Yes, I did load a config.ini from an older card to the newer card. I suppose maybe that caused a glitch after I upgraded to v6.0.6 on the NMC2's.

I'll try to upload the configs later when I have a chance.

[BillP]

This reply was originally posted by Angela on APC forums on 2/13/2014

---

I am not sure but I might me able to tell when I see what config was loaded to the 6.0.6 NMC (which maybe some keywords or values are different) and then what the current config.ini is at least to see if we can fix it. Thanks!

[shortstop20_apc]

This was originally posted on APC forums on 2/13/2014

---

Thanks Angela,

Could I possibly PM or email the configuration files to you?

I'm hesitant to post them up on the public forum since I would be revealing IP Addresses of our DNS servers, my email address, etc.

[BillP]

This reply was originally posted by Angela on APC forums on 2/13/2014

---

Hi again,

Yes, you can remove any IP information if you'd like or I'll also send you an email offline so you can send the files that way.

[shortstop20_apc]

This was originally posted on APC forums on 2/13/2014

---

I replied to your email.

[BillP]

This reply was originally posted by Angela on APC forums on 2/13/2014

---

Thanks!

Hope you don't mind that I share one thing for those that see this thread. You informed me that what you did was:

Around a year ago I did a mass configuration on all devices(via APC INI utility) using the same config in order to get consistent configurations on all devices. At that time, all NMC/NMC2 were running the older software, version 3.
A few months ago, I updated all NMC2’s to v6.0.6 and that’s when I noticed that email notifications from these devices were not as they were before.

So for NMC1 v3.X.X and actually NMC2 was at v5.X.X but it was very similar to v3.X.X, many config.ini values and keywords were the same. For 6.0.6, it is another animal if you will and there are many differences.

One thing I wanted to make sure was known was as outlined here (Things To Consider When Upgrading or Downgrading a Network Management Card 2 (NMC2) Device between v...), when you upgrade to v6.X.X, there are a few issues. 1.) The SMTP server info gets ported over incorrectly unfortunately and 2.) By design, the email notification events, intervals, frequency, etc are reset because it is not possible to keep them during the upgrade just because the firmwares are so different.

What I would recommend to ensure the most stability (theoretically anyway if there was not a problem currently) is to configure events the way you like it via the web on v6.0.6 then download that config.ini file with the correct syntax for v6.X.X and use that on your v6.X.X cards. Unfortunately, then we have this issue (Network Management Card 2 config.ini upload for event notification settings does not enable events i...) which is supposed to be fixed any day now with a v6.1.1 with the SMTP server info copying over wrong.

Going back to your original issue, I am going to look and see if I can replicate that I discovered you're using recipients mail setting which I know I don't test with often. We'll also see if we can get around having to use recipients mail setting and then I don't believe that issue will exist.

[shortstop20_apc]

This was originally posted on APC forums on 2/13/2014

---

Thanks Angela, that is helpful.

We have found that by entering email credentials under "Outgoing Mail Configuration" and changing the Server setting under Recipients to "Local" that the emails are then sent with the correct "From" address.

I'm still confused as to why this is needed on NMC2's and not NMC's though. The NMC's can send emails showing the correct "From" address without any credentials as well as using "Recipient" but the NMC2's cannot.

[BillP]

This reply was originally posted by Angela on APC forums on 2/13/2014

---

I have to think it's a bug. If I confirm I see the same behavior, I'll go ahead and log an issue on it for review.

[shortstop20_apc]

This was originally posted on APC forums on 2/13/2014

---

Thanks for your help Angela.

[BillP · Accepted solution]

This reply was originally posted by Angela on APC forums on 2/13/2014

---

No problem. And yes, I did confirm it and just entered a request to get it fixed.

Let me know if you need any more help.