With OS2.3, Nimble has added some important SMTP configuration options, thus providing additional methods for sending out email alerts from a Nimble Storage array (e.g. via an Office 365 account).
Alerts are identifiers about specific actions that occur on a Nimble Storage group of arrays. Prior to version 2.3 of the Nimble OS, you could configure a simple, or regular, SMTP relay of email alerts. In version 2.3 and later versions, you can configure either a regular or a secure Simple Mail Transfer Protocol (SMTP) relay.
To configure a regular SMTP relay, specify the SMTP server, port, from email address and to email addresses. Choose not to use authentication.
To configure a secure SMTP relay, specify the same fields as you do for a simple relay, plus choose an authentication type and an encryption type, and specify the secure SMTP username and password.
You can see the new Email Alerts configuration screen, showing all the available options:
In Nimble OS 2.3 the port is now configurable, and you have a choice of using Authentication; prior to this we only allowed an Unauthenticated Relay on Port 25.
e.g. SMTP setting for Office365
Server name: smtp.office365.com
Encryption method: TLS
Here is where you enter your credentials for authentication:
Specify the username for the SMTP account. The Username value must start with an alphabetic character and can be up to 64 alphanumeric characters. The following special characters are also valid, as long as a dot (period) is not the last character: + (plus sign) - (hyphen or dash) _ (underscore) . (period)
Specify the password for the SMTP account. The Password value can be up to 255 printable characters. The password is not hashed.
You are also able to choose which level of encryption is used:
Retain the default of None or select the encryption type. Selecting any type other than None requires using username and password authentication.
None means that email alerts are unencrypted.
STARTTLS means that secure SMTP over transport layer security (TLS) is used.
The STARTTLS encryption option can be an appropriate choice if you implemented cloud-based email.
SSL/TLS means that secure sockets layer (SSL) with transport layer security (TLS) is used. The SSL version is not subject to CVE-2014-3566, the POODLE vulnerability in SSLv3.
The SSL/TLS encryption option can be an appropriate choice if you have a secure SMTP server installed on your network.
You are now ready to send email alerts via an alternative to Unauthenticated Relay only.