Email Notifications fail after upgrade to v6.0.6

[Anonymous user]

I just finished a batch upgrade of AP9630/31s from 5.1.7 to 6.0.6.  After the upgrade I notice I wasn't receiving any email from the UPSs.  I guess the upgrade had reset the smtp server settings.  I didn't think this was too big of a problem because I have a script that can ftp my config.ini to all the UPSs.  However that did not fix the problem.  I figured out that I still have to open the smtp settings page, click apply(don't change any settings, just click apply), then test the email receipt and then everything is good.  I assume this is not normal.  Any workaround to this?  I really don't want to have to do this 159 times.  I also noticed in some cases that if I add a new user via mass ftp'ing the config.ini, I still have to test that email recipient before it starts sending email.

--Corby

[Anonymous user]

I'm having similar issues as well. After I uploaded new .ini files to re-set the 'from' address for outgoing mail to 200-ish UPSes, it still wasn't working. I noticed that if I go in via telnet and type 'email', the route is "local", and it works if I change it to "custom". In the web-management system, the equivalent is configuration -> notification -> e-mail -> recipients, click recipient address, change "server" to "custom", at which point it un-greys the SMTP server information I entered on the e-mail notification server page (or via .ini upload).

I can't find any differences between ini files when the server/route is set to 'local' vs. 'custom'. I could write an expect script to fix all my UPSes, but as uploading a .ini file is already part of our install procedure, I'd like it to happen at that point for new UPSes rather than creating an additional step for our installers. Is that at all possible?

[BillP]

I logged a bug personally on the mapping of local SMTP server when you ugprade from v5.1.X to v6.0.X because the local SMTP server was mapping to Custom SMTP instead of Local SMTP where then the settings for Server for the particular recipient were still on Local which was blank after the upgrade. That will be fixed in a future version. I too just changed my setting to Custom and it was fine but still required me to have to do that to get my notifications working.

I believe the value you'll want to see if its using Custom or not is EmailReceiver1UseCommon=disabled - if its set to Custom, you'll see it say disabled and when it is enabled, it will be set to use the route defined in EmailReceiver#Route value (local or recipients).

Now that we're talking about it, that might be one of those things I see if we can make more clear for the future.

I also missed this original post some how so Corby A, please let me know if you still need help with that.

[Anonymous user]

That helps, but it doesn't do me any good because mass configuration via ftp'ing .ini files doesn't change any of the configs.  If I set one card to use local or custom servers, download the config.ini, then upload it to another NMC2, the receiving card doesn't change its config.  I also suffer from the same as this http://forums.apc.com/message/48825#48825

[Anonymous user]

Angela, I am seeing EmailReceiver1UseCommon=disabled in the downloaded config file, and that's also what I'm uploading, but it always says 'local' when I view the configuration via telnet/web. so if I'm understanding you correctly that that's supposed to change it to 'custom', I guess something might not be working right.

[BillP]

Ok let me see here.

Ok, my mistake # 1 - I checked my card and my recipient was on local server, not custom when I checked this Sorry.

I'm changing it now, then redownloading my config.ini. Not all that much changed though.. hmm.

Anyway, here are the fields I see relating to a custom SMTP server for recipient 1.

EmailReceiver1Enable=enabled

EmailReceiver1Address=

EmailReceiver1Format=Long

EmailReceiver1UseCommon=disabled

EmailReceiver1FromName=UPS(at)mydomain.com

EmailReceiver1ServerName=

EmailReceiver1Port=25

EmailReceiver1Auth=enabled (i enabled it)

EmailReceiver1Username=testing (my authentication username)

EmailReceiver1SSLMode=none (i am using plain text authentication)

I think the key is going to be filling out UseCommon=disabled and then the custom server is still under EmailReciever#ServerName.

[Anonymous user]

OK, I think I figured it out. You talked about EmailReceiver#Route earlier, and I tried it, but I think I didn't have the 'C' in Custom capitalized, so when it didn't work, I just removed that line. I also didn't think I'd seen it in the downloaded config file, but I checked a couple other UPSes, and there it was, set to 'Local'. What you had in post 5 was basically what I was using, so putting it all together, it looks like it works.

EmailFromName=my_sender@example.com

EmailServerName=my_server.example.com

EmailServerPort=25

EmailServerAuth=disabled

EmailServerUsername=User

EmailServerSSLMode=none

EmailServerCertRequired=disabled

EmailServerCertFilename=""

EmailReceiver1Enable=enabled

EmailReceiver1Address=my_recipient@example.com

EmailReceiver1Format=Long

EmailReceiver1Language=enUs

EmailReceiver1UseCommon=disabled

EmailReceiver1Route=Custom

EmailReceiver1FromName=my_sender@example.com

EmailReceiver1ServerName=my_server.example.com

EmailReceiver1Port=25

EmailReceiver1Auth=disabled

EmailReceiver1Username=User

EmailReceiver1SSLMode=none

EmailReceiver1CertRequired=disabled

EmailReceiver1CertFilename=""

Thank you!

[BillP]

No problem. But I am still confused because I had mine set to custom and nowhere in my config.ini did it say the word Custom. If it works, fine, but maybe there is something wrong here. I will look further into it on Monday.

[Anonymous user · Accepted solution]

I just finished a batch upgrade of AP9630/31s from 5.1.7 to 6.0.6.  After the upgrade I notice I wasn't receiving any email from the UPSs.  I guess the upgrade had reset the smtp server settings.  I didn't think this was too big of a problem because I have a script that can ftp my config.ini to all the UPSs.  However that did not fix the problem.  I figured out that I still have to open the smtp settings page, click apply(don't change any settings, just click apply), then test the email receipt and then everything is good.  I assume this is not normal.  Any workaround to this?  I really don't want to have to do this 159 times.  I also noticed in some cases that if I add a new user via mass ftp'ing the config.ini, I still have to test that email recipient before it starts sending email.

--Corby