@gea, Currently, I am unsure about napp-it email alerts reliably working. I've had on and off problems in the distant past (OmniTI days) with napp-it email alerts, but I have mitigated it by writing some critical jobs independently of napp-it and eventually a napp-it update fixes the built-in email. Now, there appears to have been major changes. I have TLS email enabled, but the menu no longer gives that option and it doesn't appear to be honored anymore, but it still appears in the Job opt3. Whenever I do an email test through napp-it it fails because it now only uses your standard email script. I've tried to follow your email flow, but with all the duplicate email scripts and options I gave up. Besides, any patches there get overwritten with any napp-it update.
My mail provider prefers port 465 TLS, but will also accept port 587 STARTTLS. I know the Pearl Net::SMTP::TLS module you use has been depreciated for many years and maybe that's the problem. Anyhow, I also use a Pearl script for my external critical jobs and use the regular Net::SMTP module you use for standard email because it has had TLS support for years. I just set the options to SSL=1 and Port=465 and it is currently working correctly. It also works with Port=587 followed by the line starttls().
So, I guess what I'm asking is maybe more of a request if Net::SMTP::TLS is broken. Can the napp-it email system be standardized on Net::SMTP and utilize an option for port and protocol? It appears to work with all major email providers, even allow for those with non-standard ports and would seem to simplify your email handling scripts.
Also, I seem to have had many issues lately with OmniOS/napp-it and I am aware of many of the changes under the hood. I've mitigated many of the issues by using http instead of https after seeing some of your recent comments. Also, upgraded from r151038 to r151040 but too early to tell if that hurt or helped.
My mail provider prefers port 465 TLS, but will also accept port 587 STARTTLS. I know the Pearl Net::SMTP::TLS module you use has been depreciated for many years and maybe that's the problem. Anyhow, I also use a Pearl script for my external critical jobs and use the regular Net::SMTP module you use for standard email because it has had TLS support for years. I just set the options to SSL=1 and Port=465 and it is currently working correctly. It also works with Port=587 followed by the line starttls().
So, I guess what I'm asking is maybe more of a request if Net::SMTP::TLS is broken. Can the napp-it email system be standardized on Net::SMTP and utilize an option for port and protocol? It appears to work with all major email providers, even allow for those with non-standard ports and would seem to simplify your email handling scripts.
Also, I seem to have had many issues lately with OmniOS/napp-it and I am aware of many of the changes under the hood. I've mitigated many of the issues by using http instead of https after seeing some of your recent comments. Also, upgraded from r151038 to r151040 but too early to tell if that hurt or helped.