In version 15 the Distribution Service’s underlying architecture was updated to use Microsoft's .NET SMTP client in preparation to support authenticated SMTP, SSL, and other email security features. In switching the network communication layer from a custom implementation of all the required SMTP commands to the .NET library, we lost the ability to trace all traffic sent over the wire but tried to maintain useful error reporting if the SMTP connection encountered any problems. Unfortunately, there was an error condition that was missed which caused the cryptic "EmailV2 failed" error to be output. This was addressed for OnBase 16 under SCR 228339 to provide a better message for errors encountered throughout the process. We hope that administrators will not need a deep understanding of the email commands at the protocol level to troubleshoot issues with the Distribution Service. Low level protocol information can still be obtained using external tracing using built-in .NET Framework tools for socket level tracing or using a packet analyzer tool (e.g. Wireshark, Microsoft Message Analyzer). If error conditions arise that require this deeper understanding, please contact your first line of support to submit a ticket back to our development team and we will investigate these issues to help track them down without these tools in a future version if possible.
Regards,
