AP9631 fw 5.1.5 email problem

[Anonymous user]

Hello,

I have problem with time settings when NM card sends notification emails: it doesn't set timezone in mail header, but writes corrected local time, so email looks like this:

From:
Reply-To:
To:
Subject: UPS: No longer on battery power.
Date: Tue, 18 Oct 2011 10:18:59 +0000
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ right local time with wrong timezone, must be 10:18:59 +0400
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="--TRECK-MIME-MULTIPART-BOUNDARY"
Message-ID:
X-Spam-Ystatus: hits=-1000
X-KSE-AntiSpam-Interceptor-Info: protection disabled
X-KSE-Antivirus-Interceptor-Info: scan successful
X-KSE-Antivirus-Info: Clean
X-Auto-Response-Suppress: DR, OOF, AutoReply
Resent-Message-Id:
Resent-Date: Tue, 18 Oct 2011 10:19:22 +0400

----TRECK-MIME-MULTIPART-BOUNDARY
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding:

Name : XXXX
Location : XXXXX
Contact : XXXXX

http://XXXX
http://XX.XX.XX.XX
http://FE80::XX
Serial Number : XXXX
Date : 10/18/2011
Time : 10:18:59
^^^^^^^^^^^^^^^^^^ right local time

Code : 0x010A

Informational Events - UPS: No longer on battery power.

----TRECK-MIME-MULTIPART-BOUNDARY--


UPS details:

Model Number: AP9631
Hardware Revision: 05
Manufacture Date: 09/15/2010
Management Uptime: 83 Days 21 Hours 38 Minutes

Application Module
Name: sumx
Version: v5.1.5
Date: Feb 25 2011
Time: 09:12:15

APC OS (AOS)
Name: aos
Version: v5.1.5
Date: Oct 7 2010
Time: 13:38:43

APC Boot Monitor
Name: bootmon
Version: v1.0.2
Date: Jan 21 2010
Time: 13:35:57

[Anonymous user]

Time zone is fixed, thank you.
But few more notes:
- Both of our AP9631 failed to upgrade language pack from first time. All other software was successfully upgraded, but on langpack it just said "ERROR" and that's all. After stop-start ftp service on UPS i've run second upgrade procedure and it upgraded just fine.
- IPv6 is not supported for smtp and firmware upgrade.
- When using language pack, email subjects created far less informative. For example messages about user logon-logout have subjects cut at 60th char, but english one is more then 80 chars long.

[BillP]

hmm, i havent seen the language pack issue yet. i was under the impression any service supported IPv6, including SMTP. how do you know it doesnt work? meaning, did you can get an error message when using your IPv6 address or ? which pack are you using and notice the email subjects being cut off?

[Anonymous user]

I have A and AAAA in DNS for my smtp-server so i've just put it's name in "Local SMTP Server:" field. After that ups doesn't even try to use AAAA record and sends all email to A. If i put IPv6 address or DNS name with only one AAAA record (without A-record), then on smtp test it says "Test e-mail failed; SMTP configuration error."
Also, when you have manually configured IPv6 address in notification mails there are only link-local addresses, as you can read in message example in first post.
By the way, IPv6 in SNMPv1 works just fine for now.

English,French,Russian,Chinese,Japanese,Korean

[BillP]

i am sure down the line we will offer the update utility and it will suport IPv6 but not just yet. i will also see if someone can look at the IPv6/SMTP to see if we have a problem with that.

which specific language out of that pack did you use and notice the smaller email subject? that way we can check it here and see what's what. i think one of the issues is multi-byte character sets so they might have chopped it off for a specific issue with other sets besides ASCII.

[BillP]

ok. i am getting someone to address this for a future firmware version. which email client do you use? does it not render the subject properly either? i haven't seen it myself but some testing is done on Thunderbird for an email client and it renders properly. once we know, then it will speed up a proper fix to ensure we are fully complying to RFCs if we aren't already.

[Anonymous user]

It's Thunderbird 7.0 win32 and subject is readable, and there is a little mess in modern rfcs about utf-8 in header fields. But i mostly talk about less information provided by subject, no ip addresses in it is a really annoying thing.

[Anonymous user · Accepted solution]

Russian

Also, subject should be encoded in the way such as "=?utf-8?xxxxx", but i see plain utf-8 without any encoding.