Not saying we won’t make improvements here, and an official announcement is still forthcoming, but the future of building add-ons will be the XF CLI which no longer depends on Closure Compiler at all and is relatively CI/CD friendly.
https://github.com/xenforo-ltd/cli
I looked into this further, but the original assessment was correct. Even if we tried to handle synchronous errors, we can't reliably classify this error as a bounce because the response code and message are too ambiguous and list several possible causes.
The message appears to come from Exim...
Assuming the previous file health check passed, the file would have been modified sometime between that check and this one. Unfortunately, it's not possible for me to say what modified it or why.
You might compare it against the file from a fresh download to see if the differences offer any...
This file is included as part of an AWS library bundled with XenForo. It's intended for development purposes and isn't used by XenForo itself.
The file health check indicates that its contents differ from those in the original distribution, but this alone doesn't suggest that your installation...
You could create an icon BB-Code and then use that in the phrase instead. Otherwise there's not really a way of getting them to appear in posts, they're rendered via HTML.
Nothing went wrong exactly, we just limit the render-depth of BBCode for security and performance reasons. These posts have some extreme nesting. The posts can be edited to remove them.
The issue isn’t so much that these don’t represent genuine bounces, it’s that they’re being handled synchronously when the email is sent instead of asynchronously by accepting the message and reporting the bounce to the bounce inbox later which is what our bounce handling mechanisms have always...