gmakhs I have it in production use for my business and a charity and it's been fine for over a year and half. Enhance is used buy some companies that have 100's of servers. Adam refers to it as production ready and I don't disagree... lacking features isn't the same as not being production ready. Sure there are changes/challenges to deal with.
Wither it's production ready for your use case is entirely up to you. It is safe in the wild and doing what it's design to do.
@XN-Matt Yes this wasn't a good one, and app servers need to be able to limit from allowing PHP mail. I've recently finally switched to a smart host and now I wish I could block all php mail, that said php mail IS blocked now anyway by the smart rely as it lacks sufficient SPF headers, but still.
Right now I am currently testing out adding a server wide php.ini directive:
disable_functions = mail
An end user can undo/modify it on the CP. (It's to stop bots.)
I don't think it works, even after container and webserver resets I seem to be able to send mail via php. 😐