{"id":152483,"date":"2025-04-11T10:47:29","date_gmt":"2025-04-11T10:47:29","guid":{"rendered":"https:\/\/postmansmtp.com\/?p=152483"},"modified":"2026-03-10T09:28:37","modified_gmt":"2026-03-10T09:28:37","slug":"we-heard-you-post-smtp-v3-1-4-is-live-with-key-bug-fixes","status":"publish","type":"post","link":"https:\/\/postmansmtp.com\/es\/we-heard-you-post-smtp-v3-1-4-is-live-with-key-bug-fixes\/","title":{"rendered":"We Heard You! Post SMTP v3.1.4 Is Live with Key Bug Fixes"},"content":{"rendered":"\n

At Post SMTP, we don\u2019t just build tools\u2014we build trust. When our users speak, we listen closely and act fast. That\u2019s exactly what happened recently when a couple of users flagged some issues after updating to a newer version.<\/p>\n\n\n\n

Today, we\u2019re excited to announce the release of Post SMTP v3.1.4<\/strong>, where we’ve tackled those problems head-on.<\/p>\n\n\n\n

Let\u2019s walk you through what\u2019s been fixed and why it matters to us\u2014and to you.<\/p>\n\n\n\n

What Were The Issues, and How This All Started<\/strong><\/h2>\n\n\n\n

This release is a direct response to the feedback we received from dedicated users who noticed odd behavior after upgrading from v3.1.3 to the latest version.<\/p>\n\n\n\n

To be precise, they have reported two issues:<\/p>\n\n\n\n

    \n
  1. \u00abSent To\u00bb Field Missing in Logs<\/li>\n\n\n\n
  2. Queued Emails Incorrectly Marked as Failed<\/li>\n<\/ol>\n\n\n\n

    Let’s discuss them in detail:<\/p>\n\n\n\n

    Issue #1: \u00abSent To\u00bb Field Missing in Logs<\/strong><\/h3>\n\n\n\n

    One user pointed out that emails sent programmatically using wp_mail() suddenly stopped displaying the \u00abSent To\u00bb field in the Post SMTP logs. Even though the emails were actually being delivered (and showing as \u00abSuccess\u00bb), the recipient information was missing from the logs screen, making it harder to verify who exactly received the email.<\/p>\n\n\n\n

    Note:<\/strong> This type of issue occurs very rarely.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    Issue #2: Queued Emails Incorrectly Marked as Failed<\/strong><\/h3>\n\n\n\n

    This issue came from the Post SMTP Pro<\/a> users, who reported that emails queued for delivery were being flagged as \u00abFailed\u00bb in the dashboard\u2019s recent logs screen\u2014even though they were showing \u201cQueued\u201d in the main logs screen.<\/p>\n\n\n\n

    Both issues caused confusion. And while the functionality behind the scenes was still working to an extent, the logs\u2014the place you go to confirm, verify, and troubleshoot email delivery\u2014were not reliable.<\/p>\n\n\n\n

    Now, check out how we\u2019ve fixed the issues.<\/p>\n\n\n\n

    How We Fixed the Issues<\/strong><\/h2>\n\n\n\n

    After investigating the reports, our development team identified and addressed both problems. Here\u2019s what\u2019s been resolved in the new version:<\/p>\n\n\n\n

    \u2705 FIXED #1:<\/strong> We fixed the bug that prevented the \u201cTo\u201d field from displaying in the logs. Now, whether your emails are sent manually or programmatically, the recipient details appear correctly in the log entries.<\/p>\n\n\n\n

    \"\"<\/figure>\n\n\n\n

    \u2705 FIXED #2:<\/strong> We also addressed the false \u201cFailed\u201d status being shown for queued emails in the dashboard\u2019s recent logs screen. Logs now reflect the real delivery status, giving you accurate insights.<\/p>\n\n\n\n

    These changes have been fully implemented in the new v3.1.4 release<\/strong>, available for all users of the free version of Post SMTP.<\/p>\n\n\n\n

    What You Need To Do \u2014Update to Post SMTP v3.1.4 Now!<\/strong><\/h2>\n\n\n\n

    If you\u2019ve been affected by either of these issues\u2014or if you simply want the most stable and user-friendly version of Post SMTP\u2014we highly recommend updating to version 3.1.4<\/strong> today. The fix is live and ready for you.<\/p>\n\n\n\n