Title: Post SMTP Release Update Last modified: August 25, 2026 --- # Post SMTP Release Update * Plugin Support [M Aqib Khan](https://wordpress.org/support/users/aqibkhan9/) * (@aqibkhan9) * [1 week, 5 days ago](https://wordpress.org/support/topic/post-smtp-release-update/) * Hello Post SMTP family! * We recently identified an issue in our release process that caused a pre-release build, 4.0.0-beta.1, to be published to the production release channel instead of the intended **3.10.0** release. * We have since addressed the release issue and have released **[Post SMTP 4.0.1](https://drive.google.com/file/d/1nXpElBX9FLsHpYW3Q8I1FFLHoHXl_728/view?usp=sharing) as the latest stable version**. * If you received the 4.0.0-beta.1 build, we recommend updating to **4.0.1**, which is the current stable release. * We apologize for the unexpected update and any confusion this may have caused. We appreciate your patience and continued trust in Post SMTP. Viewing 3 replies - 1 through 3 (of 3 total) * [Sim Architect](https://wordpress.org/support/users/thesimarchitect/) * (@thesimarchitect) * [1 week, 5 days ago](https://wordpress.org/support/topic/post-smtp-release-update/#post-19002093) * Hello! I would like to know how I update the database as your “learn about migration” button sends me to a generic instructions page about the fallback feature (I tried uploading a screenshot but they won’t host the image here), which I don’t want to set up right now, but just to have the plugin up to date and working normally like before. * Thanks in advance for instructions on how to fix this. I tried getting help from AI but nothing I did so far worked. * I pushed your zip file and now it’s rolled back to version 3.10. I had to turn auto updates OFF. I hope I don’t have any technical problems due to your beta version changing something that’s not compatible with version 3.10 on my database. * I assume others will face the same problem, it would be nice if you could list recommended steps for us to take to avoid issues and it would be nice if you released a version 4.0.1 even if it’s the 3.10 you provided on your zip code to fix it for everybody without requiring research. * I’ll look forward towards what to do next. * Have a great day! - This reply was modified 1 week, 5 days ago by [Sim Architect](https://wordpress.org/support/users/thesimarchitect/). * Plugin Support [M Aqib Khan](https://wordpress.org/support/users/aqibkhan9/) * (@aqibkhan9) * [1 week, 5 days ago](https://wordpress.org/support/topic/post-smtp-release-update/#post-19002655) * Hey [@thesimarchitect](https://wordpress.org/support/users/thesimarchitect/) , * Thank you for taking the time to explain what happened. We sincerely apologize for the confusion and inconvenience this has caused. * First, you do not need to manually update the database or configure Fallback SMTP. The “Learn about migration” message you’re seeing was part of the 4.0.0- beta.1 build that was inadvertently distributed through the stable release channel. That beta was not intended to be released to production. * We have now corrected the release and Post SMTP 4.0.1 is available as the latest stable version. We recommend updating directly to 4.0.1 once it becomes available in your WordPress dashboard. * Regarding your rollback to 3.10, we understand why you did that. At this point, there is no need to perform any additional database migration manually. We have also taken the necessary steps to address the compatibility issues introduced by the beta release. * If 4.0.1 is not showing in your WordPress dashboard immediately, please don’t be concerned. WordPress.org can take several hours to propagate a newly released plugin version across its update network, so availability may be staggered between sites. You can simply check again later. * For now, we’d recommend: 1. Once 4.0.1 is offered, update directly to that version. 2. Do not perform any manual database migration or enable Fallback SMTP just to resolve this notice. * We completely understand your concern about the beta potentially leaving changes behind when rolling back to 3.10. We are actively reviewing this as part of the release issue, and if you experience any unexpected behavior after the rollback, please let us know so we can investigate it with you. * We apologize again for the unexpected beta release. You were right to flag the confusing migration instructions, and we appreciate you bringing this to our attention. * [Sim Architect](https://wordpress.org/support/users/thesimarchitect/) * (@thesimarchitect) * [1 week, 5 days ago](https://wordpress.org/support/topic/post-smtp-release-update/#post-19002754) * Thank you very much for clarifying we’re safe with the rollback! * So far I had no problem with your “3.10” version above (I had messages successfully delivered since then). I updated it with the “4.0.1” and I don’t see the message from 4.0 Beta, thankfully. * Have a great day/evening! Viewing 3 replies - 1 through 3 (of 3 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fpost-smtp-release-update%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/post-smtp/assets/icon-128x128.gif?rev=3209655) * [Post SMTP – Complete Email Deliverability and SMTP Solution with Email Logs, Alerts, Backup SMTP & Mobile App](https://wordpress.org/plugins/post-smtp/) * [Frequently Asked Questions](https://wordpress.org/plugins/post-smtp/#faq) * [Support Threads](https://wordpress.org/support/plugin/post-smtp/) * [Active Topics](https://wordpress.org/support/plugin/post-smtp/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/post-smtp/unresolved/) * [Reviews](https://wordpress.org/support/plugin/post-smtp/reviews/) ## Tags * [database](https://wordpress.org/support/topic-tag/database/) * [update](https://wordpress.org/support/topic-tag/update/) * 3 replies * 2 participants * Last reply from: [Sim Architect](https://wordpress.org/support/users/thesimarchitect/) * Last activity: [1 week, 5 days ago](https://wordpress.org/support/topic/post-smtp-release-update/#post-19002754) * Status: not a support question