Feature requests

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