Hey @vurvargurgar
Thanks for reporting this and for sharing the details.
It looks like you received 4.0.0-beta.1, which was a pre-release build that was inadvertently made available through the production release channel. The issue you’re seeing with the fallback configuration is related to that beta build.
We have now released Post SMTP 4.0.1 as the latest stable version, which includes the necessary fixes.
Please update to 4.0.1 and try configuring the fallback SMTP again. You should no longer encounter the “Outgoing Mail Server Hostname and Port cannot be empty” error when enabling or disabling the fallback option.
We apologize for the confusion caused by the unintended beta release, and appreciate you reporting the issue.
If you continue to face issue after updating to v 4.0.1, We are here to assist you.
Why is the stable version not just being pushed as a regular update through your release channel instead of pointing users to download as a zip outside of the wordpress environment?
Hello @vurvargurgar ,
We completely understand your concern. The 4.0.1 release has already been submitted and released from our side through the standard WordPress.org release process.
One point worth mentioning is that WordPress.org’s plugin distribution/update system can take several hours to propagate a newly released version to all sites. As a result, 4.0.1 may not become available immediately for every installation after the release. We’re monitoring the rollout and working to ensure the corrected version reaches affected sites as quickly as possible.
Again, we’re sorry for the disruption caused by the unintended beta release, and we appreciate you bringing this compatibility issue to our attention.
Hello @vurvargurgar ,
The updated release is now available. Please update the plugin to the latest version and check the issue again.
If you still encounter the same issue after updating, please let us know.
