SMTP broken with last update
-
With the last update to Mailpoet, checking “Authentication No” apparently doesn’t work because it results in an error that authentication failed, even if it wasn’t supposed to authenticate. I am running this WordPress instance in a Docker container, and the SMTP server is running on its host. There is no need for authentication–and, in fact, it is ill advised because it means leaving a username and password in the database.
Expected behavior: Checking “Authentication No” should not result in an authentication failure.
Viewing 5 replies - 1 through 5 (of 5 total)
Viewing 5 replies - 1 through 5 (of 5 total)
- The topic ‘SMTP broken with last update’ is closed to new replies.