In ACF, if email failed to go out because the message itself had a problem - incorrect mail server, etc. - one could literally open the file, fix it, and respool it. To my dismay, I discovered that how Lucee handles email is a rather closed system.
One first must find the message under the web admin “Tasks”, and review what’s wrong. For some reason, i have a bunch of messages that are “timing out”, even though the web app is currently sending messages just fine. So SOMETHING in the message is incorrect. However, i see no way to get to the actual raw email/content to see what it’s trying to do. I can only “delete” or “execute” the task. But the task must be depending on a message SOMEWHERE, yes? The timeout appears to be related to either an authentication issue, or a port issue, or something… either way, when the task runs, it seems the SMTP server info is baked into the MESSAGE instead of relying on the SMTP server that’s currently configured and working for the web app.
This is Not Good™ as one should be able to correct email(s) and re-queue them. Sometimes messages ARE important, cannot be regenerated easily, and should be able to be handled manually.
Am I missing something?