Separate S.M.A.R.T. email addresses with spaces
If adding more than one e-mail address i smartd service gui, you get an error.
Doc should say that SMART emails should be separated with spaces
Fix poor representation of validation errors for elements of lists that are only splitted by middleware_clean
smartd config uses commas to separate emails so let's store it that way
fix(oldguit): Show smart_email as space-separated instead of comma-separated
fix(oldgui): Show smart_email as space-separated instead of comma-separated
#11 Updated by Dru Lavigne about 1 year ago
- Subject changed from more than one e-mail addresse in smartd problem to Separate S.M.A.R.T. email addresses with spaces
- Target version changed from 11.3 to 11.2-BETA1
- Needs Merging changed from Yes to No
Master PR: https://github.com/freenas/freenas/pull/1103
- Needs Doc changed from Yes to No
- File SMARTemailnotificationaddresses-2018-06-13.png SMARTemailnotificationaddresses-2018-06-13.png added
Currently, the legacy UI allows email addresses to be entered using commas or spaces.
The webui only allows space separated entries. See SMARTemailnotificationaddresses-2018-06-13.png The screenshot shows comma and web seperated entries, and the error given.
Both UIs display email addresses in the comma separated form.
Asked Vladimir to clarify the following:
Are email addresses stored comma separated, and should be entered comma separated?
Should we allow comma or space separated entries? (both?)
Should the UI display multiple emails address entries in space or comma separated format?
Once we get these answer, I'll update this ticket to get everything updated/corrected.
The webui tooltip (and userguide entries) need to be updated to reflect that multiple notification email addresses can be entered, and the prefered format.
Fails testing in the new UI. Emails can be separated by spaces, but using ', ' or ',' causes an error. This is problematic when multiple emails were added via spaces, since they are changed to comma separation which fails when you save settings.
This also occurs in the old UI. It's fine for input to be validated by separating with spaces, but when they are changed to commas that causes the input to fail. When configuring the service the previously entered emails should probably be parsed back into space separation.