Default Email Server option not working after an upgrade to DPA 2025.x

After upgrading to SolarWinds Database Performance Analyzer (DPA) version 2025.x, some users have reported that the Default Email Server option no longer functions as expected. This issue prevents DPA from properly sending automated email alerts and notifications, impacting visibility into database performance issues. Since timely alerts are critical for DBAs who rely on DPA to monitor and respond to performance problems, the disruption can create unnecessary blind spots in production monitoring.

The problem has been traced to a compatibility issue with the angus-mail-2.0.1.jar library packaged with DPA. This outdated mail component interferes with the email server configuration after the upgrade, effectively breaking the integration. Until SolarWinds releases an official patch, DBAs and system administrators can implement a simple but effective workaround to restore functionality. The fix involves making a backup copy of the problematic JAR file and removing it from the DPA installation so that the application can bypass the faulty library.

By stopping the DPA application, backing up and deleting the angus-mail-2.0.1.jar file, and then restarting the application, the Default Email Server option is restored and resumes normal operation. This process is low risk, requires no code modifications, and can be performed quickly on most environments. With this workaround in place, DBAs can continue receiving critical alerts and ensure uninterrupted database performance monitoring while waiting for an official hotfix or update from SolarWinds.

Example of Error:

DPA was unable to send the message due to the following error:

com.confio.iwc.mail.exceptions.MailException: Error sending mail:
jakarta.mail.MessagingException: Could not convert socket to TLS; nested
exception is: java.io.IOException: Can't verify identity of server:
dpasmtp2.solarwinds.com.

Check the DPA Web Client logs for more details.

A fix is planned for a future release of DPA. In the meantime, use the workaround below.

In order to utilize the Default email server feature:

1. Stop DPA. 

2. Navigate to:   

`C:\Program Files\SolarWinds\DPA\iwc\tomcat\webapps\iwc\WEB-INF\lib\` 

3. Backup the file `angus-mail-2.0.1.jar` by copying it outside the DPA installation directory. 

4. Delete the original `angus-mail-2.0.1.jar` file from the directory. 

5. Start DPA. 

If DPA fails to start after the change, restore the ‘angus-mail-2.0.1.jar ‘ file to it’s original location, and Restart DPA again.