Would be great to see a linear chart per day/week/month regarding how many users subscribed

It’s easier to collect information and get replies by adding a poll or survey to your emails. - [As seen in ReplyButton.com ]

Please can you add a simple tweak to allow me to schedule my newsletters according to the recipient's time zone.... I've just left MailChimp to try MailPoet and I now think I need to move back to Mailchimp as there are so many basic features not available

I have a membership site where members (WordPress users) should always and automatically become Subscribed because the website has a ‘legitimate interest’, as meant by the GDPR, in being able to reach the members by e-mail for important issues. However, I also need the two-step sign-in because I have certain other lists, that non-members can subscribe to as well. I have tried to confirm the WordPress users through different automation plugins upon their membership purchase. Nothing helps. WordPress users are always unconfirmed. If I enable subscribing to a list via registration form, I have double confirmation mails. One from membership plugin and another one from MailPoet. Special lists like WordPress users or WooCommerce users should have a possibility to be confirmed by default.

Resend a newsletter or campaign to those who did not open the first email

When getting the list of mail lists from mailpoet, I would like to be able to see if the list is visible to be managed. The use case is to programmatically check if a user is subscribed to all of the lists that are manageable by them. I have attached a patch that adds a 'display' attribute to the list array returned by getLists() that implements this feature. If you would kindly integrate it others could benefit and I wouldn't need to manage this patch myself. diff --git a/mailpoet/lib/API/MP/v1/Segments.php b/mailpoet/lib/API/MP/v1/Segments.php index f7ce734ea..ab59789e2 100644 --- a/mailpoet/lib/API/MP/v1/Segments.php +++ b/mailpoet/lib/API/MP/v1/Segments.php @@ -196,6 +196,7 @@ class Segments { 'created_at' => ($createdAt = $segment->getCreatedAt()) ? $createdAt->format(self::DATE_FORMAT) : null, 'updated_at' => $segment->getUpdatedAt()->format(self::DATE_FORMAT), 'deleted_at' => ($deletedAt = $segment->getDeletedAt()) ? $deletedAt->format(self::DATE_FORMAT) : null, + 'display' => $segment->getDisplayInManageSubscriptionPage(), ]; } }

I would like to be able to invoke an API that resends a confirmation email to a user --- the same way I can do through the mailpoet subscribers page. The use case is a user subscribes to a newsletter, and tries to sign up again. Since they are an existing user I would like the ability to resend the confirmation email programmatically. I have made a patch that exposes sendConfirmationEmail as a published API. If you would integrate it everyone else could benefit and I wouldn't have to maintain it myself. diff --git a/mailpoet/lib/API/MP/v1/API.php b/mailpoet/lib/API/MP/v1/API.php index 04b14d2b9..d620f2d8a 100644 --- a/mailpoet/lib/API/MP/v1/API.php +++ b/mailpoet/lib/API/MP/v1/API.php @@ -100,6 +100,10 @@ class API { return $this->subscribers->getSubscribersCount($filter); } + public function sendConfirmationEmail($subscriberId) { + return $this->subscribers->sendConfirmationEmail($subscriberId); + } + public function isSetupComplete() { return !( $this->changelog->shouldShowWelcomeWizard() diff --git a/mailpoet/lib/API/MP/v1/Subscribers.php b/mailpoet/lib/API/MP/v1/Subscribers.php index 40230ecc3..4d0a99013 100644 --- a/mailpoet/lib/API/MP/v1/Subscribers.php +++ b/mailpoet/lib/API/MP/v1/Subscribers.php @@ -253,6 +253,30 @@ class Subscribers { return $this->subscriberListingRepository->getCount($listingDefinition); } + /** + * @throws APIException + */ + public function sendConfirmationEmail($subscriberId) { + $subscriber = $this->subscribersRepository->findOneById($subscriberId); + if ($subscriber instanceof SubscriberEntity) { + try { + if ($this->confirmationEmailMailer->sendConfirmationEmail($subscriber)) { + return; + } else { + throw new APIException( + sprintf(__('Confirmation email failed to send: %s', 'mailpoet'), + APIException::CONFIRMATION_FAILED_TO_SEND)); + } + } catch (\Exception $e) { + throw new APIException( + sprintf(__('Confirmation email failed to send: %s', 'mailpoet'), strtolower($e->getMessage())), + APIException::CONFIRMATION_FAILED_TO_SEND); + } + } else { + throw new APIException(__('The subscriber does not exist.', 'mailpoet'), APIException::SUBSCRIBER_NOT_EXISTS); + } + } + /** * @param array $filter { * Filters to retrieve subscribers.

When a sending issue occurs, the service is paused, then we can't check all the time the service on all our websites. In case of Agency Licence = service will be affected on many services Then mailpoet lift the limitation. At this point 2 things can happen : - First the plugin set on the website resumes services and starts to send email again automatically - Second the plugin waiting for manual intervention of admin to resume the sending service. In both cases, if the service has been paused for 1 or more sprint, the website will send few emails to subscribers at the same time. This doesn't help to manage our spam rate. It would be great to have a warning showing that it still has few emails in the sending pool, and need to check it before resumes services.

Following WP actions would be great additions to integrate other plugins or custom logic: unconfirmed subscriber was created subscriber confirmed opt-in subscriber details updated subscriber was added to list subscriber was removed from list subscriber custom field was updated an email was sent to a subscriber subscriber opened an email subscriber clicked a link in an email And following WP filters that allow us to sanitize/modify content: save custom field value to DB get custom fields for manage-subscription-page (to allow us to sort/change labels or even remove fields from a form/page) newsletter full body rendered (like the filter "mailpoet_rendering_post_process", but after shortcodes were rendered, with $subscriber details) generate newsletter subject (allow us to customize the subject via a filter) ----- Note: Most of those actions aim towards the Automation feature-request and allows developers to customize the Subscriber workflow. The Filters allow us to customize the contents of the emails, based on user interaction. Sample use cases that I want to implement using those actions/filters: User opened an email but did not click the link: I want to add an extra sentence in the next email, via the filter. User was added to a list: I want to automatically generate a one-time-discount code for that user and store it in a custom field. The Manage-Subscription page should not display the custom field with the discount code, as the user is not allowed to change the value. User received two emails without opening them: I'd like to modify the email subject of the third email

You should really optimize how you save the email sending queue in the table _mailpoet_sending_queue. On my websites, for the bigger one, this table is several Go and continues to increase with time... until the server crash. Why are you saving each email in plain HTML in the database? You should save only one version of the global email and then optimize to call this email for each user... not save each email in the table, I have dozen of thousands of the same emails in my table... Really, they're a lot of improvements to be done here! It's ok for small websites but for bigger ones it's not really possible.