nathvi V. a11n

Hi there @yuppyquokka

Sorry to hear about the trouble with your subscription forms! That error message usually means MailPoet was unable to send the opt-in confirmation email at the moment someone tried to subscribe.

Here are the most common causes:

1. Plan not yet approved — Every new MailPoet Sending Service subscription goes through a manual review. If your plan is still pending, confirmation emails won’t go out. You can check this under MailPoet > Settings > Key Activation — if it says “pending approval,” you’ll need to wait for the review or check your email for any questions from the MailPoet team.
2. Sending paused or suspended — If sending has been paused on your account for any reason, subscription forms will show this error. You’d typically see a notice in your MailPoet dashboard if this is the case.
3. Domain not verified — MailPoet now requires domain authentication (SPF/DKIM/DMARC) for all plans using the MailPoet Sending Service. If your domain isn’t verified, sending will be blocked. You can check and set this up from your MailPoet.com account under “My Sender Domains”
4. FROM email address issue — Make sure your “From” address under MailPoet > Settings > Basics is on your own domain (e.g., [email protected]) and not a free email like Gmail or Yahoo.
5. Caching conflict — If you’re using a caching plugin, the MailPoet security token can get cached and cause form errors. Try excluding the page with the form from your cache, or test with caching temporarily disabled.

Since you mentioned trying two different keys, could you double-check on the Key Activation tab that the correct, approved key is active and showing a green “valid” status?

To help investigate further, could you share:

• Your website URL so we can look up your account
• A screenshot of your MailPoet > Help > System Status page

That will help us pinpoint the issue quickly.

Hi @sauge Thanks for reaching out and for the detailed description of what you’ve done so far — it’s really helpful!

Great job completing the domain authentication with all 4 DNS records. That was an important step.

The error “Sending is waiting to be retried” combined with the queue freezing at 0/1 suggests there may be something else going on beyond the domain verification itself. To help narrow this down, could you try these steps and share the results?

1. Re-validate your MailPoet key Go to MailPoet → Settings → Key Activation and click the “Validate” button. This refreshes the connection to our sending service and can sometimes clear stuck states after a configuration change. More info: Sending Does Not Work – Key Activation Issues

2. Check your Task Scheduler connection Go to MailPoet → Help → System Status and check the Task Scheduler section. Is it showing “Connection successful” or “Connection unsuccessful”? If you can share a screenshot of the full System Status page, that would be very helpful.

3. Check for any notices on the MailPoet Emails page Go to MailPoet → Emails in your WordPress dashboard. Do you see any banner or notice at the top about sending being paused or suspended? What Happens When Sending is Paused

Please share back the results of these three checks and we can go from there!

Hi there,

Thanks for reaching out! I’ve looked into both email addresses and removed them from our sending service’s suppression list. They should be able to receive your emails again.

On your end, please:

1. Go to MailPoet → Subscribers, filter by Bounced
2. Change both subscribers’ status back to Subscribed
3. Send a test email to confirm delivery

Even valid addresses can end up on our suppression list — common causes include the recipient’s mail server being temporarily unavailable, a full mailbox, or accumulated temporary delivery failures over a few weeks. When this happens, the address gets blocked server-side, which is why changing the status back to “Subscribed” in your dashboard didn’t stick — our system syncs bounce data approximately every 48 hours and would flip them back.

One recommendation to help prevent future issues:

Your domain has DKIM authentication set up , but I noticed there’s no DMARC record configured. Since both recipients are on Microsoft/Outlook — which has been tightening authentication requirements — adding a basic DMARC record can help. You can add this DNS TXT record:

• Name: _dmarc
• Value: v=DMARC1; p=none;

Full guide here: Email Authentication: SPF, DKIM, DMARC

If these addresses get flagged again after this fix, please reach out via MailPoet support so we can investigate the specific bounce codes.

More info: Bounce Management in MailPoet

Hope that helps!

Hi @wedgemaster

Thank you for the details and the screenshot.

I can see from your system information that your site has only 36 subscribers, so receiving a notification about exceeding 9,000 subscribers is definitely not expected — there appears to be a discrepancy between your actual subscriber count and what our system is reporting.

This isn’t something we can troubleshoot through the forum, as we would need to look into your specific account on our end to understand where this number is coming from.

Could you please contact our support team directly through this form so that we can investigate your account and resolve this? Please include the same details you shared here (your system info and the screenshot of the notification) so the team has everything they need.

Hi @matashaes

Thank you for reaching out!

We’ve checked your account and can confirm that an email was sent to you last Wednesday (April 29) with details about the status of your verification.

Your MailPoet plan approval is currently on hold because your website appeared to be under construction or inaccessible at the time of review. As part of our standard verification process, we need to be able to review your site’s content before approving a plan, in line with our anti-spam policy.

Once your website is ready and publicly accessible, please reply to the email you received from us, and our team will review your site and proceed with the approval.

Hi @jaclynsmom
Thanks for your response! The good news is that the main MailPoet connections on your site are all working:

• Task Scheduler: connection successful
• MailPoet Sending Service: connection successful
• Cron: running, no errors

What stands out is the Sending Queue — it shows 0 sent emails and every task table (scheduled, running, completed, paused, cancelled) is completely empty. That means MailPoet isn’t generating any send jobs at all, which would explain why nothing is arriving.

A couple of things to check:

1. Re-validate your API key I noticed the key was recently updated. To make sure the plugin is fully connected with the new key, please go to MailPoet → Settings → Key Activation and click Verify. Confirm it shows the key as valid and the plan as active. Even when the MSS connection test passes, a key mismatch can prevent actual email dispatch.

2. How are you sending the preview? When you send a preview email, are you using the “Send a preview” button from within the email editor? After clicking it, does MailPoet show any confirmation message or error, or does it appear to do nothing?

3. Subscriber status after form submission When a new subscriber signs up via your form, do they appear in MailPoet → Subscribers? If so, what status do they show — Unconfirmed, Subscribed, etc.?

4. System Info (text) Could you copy and paste the full text from MailPoet → Help → System Info into your reply? That will show us the exact sending method, From address, and other configuration details that aren’t visible in the System Status screenshot.

Since the connections are all healthy but no emails are being generated, the issue is likely in how the emails are being triggered or in a specific configuration detail. The System Info text should help us pinpoint that.

Hi @jrrsantacruz

Thanks for sharing the error details.

The errors indicate that some of MailPoet’s database tables are missing (jr_mailpoet_segments, jr_mailpoet_settings). We’ve seen similar cases before — this typically happens after an incomplete site migration, database restore, or installation issue.

Here’s what we’d suggest trying:

1. Back up your site and database first.
2. Deactivate MailPoet from the Plugins page.
3. Delete MailPoet completely (this removes plugin files only).
4. Reinstall MailPoet from Plugins > Add New and activate it.

When MailPoet activates, it will attempt to recreate its required database tables. In many cases this resolves the issue, though it’s not guaranteed depending on the state of the database.

If the errors persist after reinstalling:

• Check with your hosting provider whether the MailPoet tables were lost during a migration or backup restore — they may be able to restore them from a more complete backup.
• Let us know if anything changed or if you see different errors, and we’ll help from there.

Some helpful references:

• Re-installing / Updating the Plugin via FTP
• How to Migrate MailPoet Database Tables

Hi @hoppylorinc

Thanks for reaching out.

A MailPoet key can only be activated on one site/URL at a time — a subdomain counts as a separate site, even if it’s part of the same main domain: https://kb.mailpoet.com/article/194-instructions-to-activate-your-mailpoet-key

So if the key is already active on your main domain, it won’t validate on the subdomain setup as well.

You have two options:

1. Move the key — If you only need MailPoet active on the subdomain setup, you can disconnect the key from the current site first and then activate it on the new one: https://kb.mailpoet.com/article/249-how-to-change-the-domain-associated-with-a-key
2. Get a second plan — If you need both sites sending at the same time, each site would need its own separate plan/key.

Let us know if you have any questions!