strikingwebsolutions

I can also confirm from my side that the latest version is working for us.

Thanks!

I think you are correct in that “traditionally” 587 utilization was associated with TLS / Authentication; however, numerous ISPs block 25 and therefore, as a result, really have pushed the industry norm from 25 to 587 (with or without TLS).

It’s a local exchange server that is on the same internal network – we use 587 and no, we do not use TLS. If your software is requiring TLS on 587 that’s not in line with the behavior of the former application and is a terrible change on your part.

I had to downgrade to 1.8.9 plugin version to get past this error.
From what I’m seeing, the plugin is forcing STARTTLS when trying to send an email and our email server doesn’t support that so all emails were failing.
I checked the postman database record in wp_options and it is set to none so there is some type of code level error that is enforcing this and not adhering to user settings. I also noticed when I change the user settings for auth to none it doesn’t save that either as the gui continues to reflect starttls (even though the database reflects none as originally mentioned).