10-31-2023, 03:18 PM
Thank you for your reply and I understand this limitation of the notification implementation.
I was not intending to use Google as the SMTP server but using that as a well known email provider, although it no longer permits authentication by username/password.
I will configure a dedicated email account for testing HBSF notifications.
Can I suggest that this form be updated in a future release to indicate that "SMTP authentication" must be an email address or the error message to show which field is invalid? (I would then have used a different email account for testing notifications.)
I was not intending to use Google as the SMTP server but using that as a well known email provider, although it no longer permits authentication by username/password.
I will configure a dedicated email account for testing HBSF notifications.
Can I suggest that this form be updated in a future release to indicate that "SMTP authentication" must be an email address or the error message to show which field is invalid? (I would then have used a different email account for testing notifications.)