Requests and complaints…
They do complain about having to have an SMTP server. Prefer it was more automated.
Requests and complaints…
They do complain about having to have an SMTP server. Prefer it was more automated.
Seems like I’ve been wrong about 99.9% having an SMTP server, and some of your customers are small enough to not have it.
I think it’s kinda obvious that it would be beneficial for them to be able to set up a webhook “(e.g. for Discord)” instead of maintaining an SMTP server.
Also, I can speak from the middle-sized company perspective. The average user/admin can be skilful/determined enough to set up an additional webhook (for example, for critical notifications), but not skilful/determined enough to deploy an smtp relay to messenger as a workaround or, moreover, complain to the devs.
I understand the business perspective of things enough to accept the customer-driven approach that “SMTP is good enough”. However, seeing so many webhook-alike services being supported it is honestly a bit surprising that something as simple as a webhook is not supported.
I’m a homelab user and would like to integrate my NTFY service into TrueNAS.
I understand this might not be a revolutionary change, but this would be a win to add any webhook integration rather than just with discord.
I think focusing on this just being a discord request is making it smaller than it is.
Opening up these options allows other avenues for users to use other applications & get their logs their way.
If we were to focus on this just being a discord addition (which again it shouldn’t be) it could be a good win for the users that I’m around since a lot of negative sentiment has built up from what I’ve heard about the middleware change & the removal of other features in gold eye.
To me, there’s a lot of merit in working on this to give your users more options & give them a win to try & drive back the negativity.
Great news! This feature request has been transferred to our internal roadmap for detailed scoping and assessment.
Thank you to everyone who voted and contributed to the discussion. Your input has been invaluable in helping us understand the community’s needs and use cases for this feature.