Feature requests

Feature Request: Native Postmark API Integration
We would love to see native support for the Postmark API as an additional sending method alongside SendGrid. Many businesses already use Postmark for all transactional email because of its outstanding deliverability, reliability, and developer experience. It would be great if MailPoet could leverage the same infrastructure for newsletters and marketing automations without relying on SMTP. Why this matters Using Postmark via SMTP works well, but it has several disadvantages compared to a native API integration: Slower delivery of large campaigns due to SMTP overhead. Less reliable throughput for high-volume newsletters. No access to Postmark-specific features such as Message Streams, Tags, Metadata, and server-side optimizations. Additional SMTP configuration instead of a simple API token. A native API integration would provide faster campaign delivery while maintaining MailPoet's existing features such as segmentation, automations, open tracking and click tracking. Requested features Native Postmark API authentication using Server API Token. Support for Broadcast Message Streams. Optional support for Transactional Message Streams. Ability to select the Message Stream from within MailPoet. Support for Tags and Metadata. Optional webhook integration for bounces, spam complaints and delivery events where appropriate. Why Postmark? Postmark has become a popular choice for companies that value high deliverability and a simple, reliable infrastructure. Many WordPress sites already use Postmark for WooCommerce, Gravity Forms and WordPress system emails. Native MailPoet support would allow users to consolidate all email sending on one platform while avoiding SMTP bottlenecks. This would be a valuable addition alongside the existing SendGrid integration and would likely be appreciated by many professional users.
0
Blank MailPoet admin pages (Subscribers & Emails) on WordPress 7.0.1
Hi, I’m having a persistent issue with blank MailPoet admin pages on my site and would appreciate some help. Environment WordPress version: 7.0.1 MailPoet version: 5.33.1 (just updated from 5.27.0) PHP version (from Site Health): 8.2.31 Site: danielagelbrich.de Symptoms All MailPoet admin pages like “Subscribers” and “Emails” are completely blank in the content area. The HTML source shows the wrapper and a <div id="subscribers_container"></div>, plus MailPoet variables such as mailpoet_segments and mailpoet_subscribers_count = 383, so data seems to be present. The main React container (#subscribers_container) never renders the interface. JavaScript console errors On the mailpoet-subscribers admin page I consistently see: Uncaught ReferenceError: MailPoet is not defined at mailpoet_mailpoet-js-after:2:1 Uncaught ReferenceError: Parsley is not defined at mailpoet_admin_vendor-js-after:2:1 So the “after” inline scripts for MailPoet and the admin vendor bundle run, but the global objects MailPoet and Parsley are not defined at that moment. Network tab Filtering for “mailpoet” on the same page shows: admin.php?page=mailpoet-subscribers – 200 (document) Several CSS files: mailpoet-wp-components….css?ver=7.0.1 mailpoet-plugin….css?ver=7.0.1 mailpoet-admin….css?ver=7.0.1 mailpoet-dataviews….css?ver=7.0.1 CSS is loading fine. The JS errors reference mailpoet_mailpoet-js-after and mailpoet_admin_vendor-js-after, but the base script handles apparently don’t provide MailPoet / Parsley when those “after” snippets execute. Troubleshooting steps already taken Tested with multiple browsers: Brave (Shields off), Chrome, Firefox, Safari – same blank pages and same console errors. Updated WordPress from an older version to 7.0.1. Updated MailPoet from 5.27.0 to 5.33.1. Installed “Health Check & Troubleshooting” and enabled Troubleshooting Mode: Only MailPoet active, default theme, all other plugins disabled in this mode. The MailPoet admin pages are still blank with the same MailPoet is not defined and Parsley is not defined errors. Because the issue persists even with only MailPoet active in troubleshooting mode, it seems not to be a classic plugin/theme conflict. It looks like the admin JS is either not correctly initialized or the “after” scripts are running before the base scripts define MailPoet and Parsley. Question Is this a known issue with MailPoet 5.33.1 on WordPress 7.0.1, and is there a workaround or patch so that the Subscribers/Emails admin pages will render again? If you need more logs or full system status, I can provide them. Thanks in advance for your help.
2
Allow Posts Blocks Inside Structured Newsletter Sections and Column-Based Layouts
As a long-time MailPoet user, I would like to request the ability to place Posts blocks inside specific newsletter sections and column-based layouts. In previous versions of MailPoet, creating structured newsletters with clearly defined sections was much more flexible. Today, Posts blocks can only be inserted as full-width blocks because nested columns are not supported. This creates significant workflow limitations for publishers who organize their newsletters into multiple editorial sections. For example, my newsletter contains sections such as: Opening Exhibitions Accompanying Exhibition Events Closing Exhibitions When I want to place a post inside one of these sections, I cannot simply insert the Posts block where it belongs. Instead, I must first insert the Posts block elsewhere and then manually move or recreate the teaser image, title, and text content using separate blocks. This process is repetitive, time-consuming, and prone to errors. The current workaround may be acceptable for occasional newsletters, but for weekly publications with multiple posts and structured editorial content, it significantly reduces efficiency. I believe many publishers, magazines, bloggers, cultural institutions, and content-driven organizations would benefit from: Allowing Posts blocks inside column-based layouts Supporting nested layouts where technically possible Providing more flexible placement options for Posts blocks within newsletter sections If you have experienced similar limitations, please vote for this feature request so the MailPoet team can prioritize a more flexible newsletter editor in future releases. Thank you for your support.
0
Add a bounce probe feature like in groups.io that would let us handle bounces without having to go thru yout tech support.
If you go to https://groups.io/helpcenter/manual/generalinfo/general/bounce_handling.htm you will see their application gives administrators the ability to send a "bounce probe" email to a member whose email was put on their bounce list. If the member replies, it is automatically removed from their bounce list -- without having to ask the user to send an email then having to forward over to tech support like we have to currently do with MailPoet. From that page "The overall bounce handling process in Groups.io is: Step 1: On receiving a bounce for the first time, the system tries to determine—through a combination of the type of bounce and the frequency of the bouncing—whether the account is bouncing often enough and seriously enough to require action. Step 2: If action is required, the system sets the account’s status to Bouncing, stops sending group emails to it, and begins trying to reach the account holder via bounce probe emails notifying them that the account is bouncing. Step 3: If the account holder: Responds to one of the bounce probes: The account is taken out of bounce handling and goes back to normal. Does not respond to any bounce probes within a certain period of time: The system sets the account’s status to Bounced and stops sending emails of any kind to it. When an account is Bouncing or Bounced, the system takes these actions: Logs entries in the activity logs of all the account’s groups stating that the account is bouncing, to inform group moderators. Displays a blue B (for a Bouncing account) or a red B (for a Bounced account) next to the account’s email address in the member lists of all its groups. Includes the account in the “Bouncing” member lists of its groups. (The account continues to appear in the regular member lists as well.) The affected members are notified by email that they are Bouncing or Bounced. They are also given a chance to “unbounce” their accounts through a special page at the Groups.io site whenever they are logged in. ! Important: Group owners and moderators cannot do anything to “unbounce” members’ accounts. Members must address the underlying problem themselves."
0
Load More