Description of problem: Following parameters settings do not generate error after notifier service restart, as expected: 1) MAIL_USER=-111 (negative number) 2) MAIL_PORT=123 (wrong number) 3) HTML_MESSAGE_FORMAT=blabla (should be true/false) Version-Release number of selected component (if applicable): SI24.5 How reproducible: always
(In reply to comment #0) > Description of problem: > Following parameters settings do not generate error after notifier service > restart, as expected: > 1) MAIL_USER=-111 (negative number) > 2) MAIL_PORT=123 (wrong number) What's wrong with this? > 3) HTML_MESSAGE_FORMAT=blabla (should be true/false) > > Version-Release number of selected component (if applicable): > SI24.5 > > How reproducible: > always
The missing validation for these parameters do not point user to the problem of which event notification fail.
We should understand exactly what validation we need for the configuration.
Tested on sf-8: 1) MAIL_USER=-111 (negative number) -> Do not fail notifier restart 2) MAIL_PORT=60000 (wrong number) -> Do not fail notifier restart 3) HTML_MESSAGE_FORMAT=blabla -> Fail notifier service restart: Error: HTML_MESSAGE_FORMAT must be true or false [FAILED]
Ilanit, Valid mail port range is 1 to 65536. So in your case it shouldn't be restarted. Noam, please check what happened to the user and boolean.
Ilanit, Both HTML message format and mail port were verified. We have a fix for the user as a part of bug 885436, so please verify this BZ.
Verified on sf-8, as mentioned in comment 8.
3.2 has been released