wegi01

I had the issue that manually created standard newsletters were not sending:

• Clicking “Send” only showed a short spinner.
• The newsletter did not appear under Scheduled or Sent.
• Automatic post notification emails still worked.
• In Status → System Status, the MailPoet Sending Service, cron and sending queue were all reported as OK, but there were 0 scheduled tasks and 0 sent emails.

What I did

1. Checked MailPoet System Status
   Confirmed that:
   • MailPoet Sending Service was connected.
   • Task Scheduler and sending queue were running and had no errors.
     This told me the sending engine itself was fine, but no jobs were being created.
2. Noticed the “Authenticate your domain” warning
   In the newsletter editor I saw a warning at the top:“Authenticate the domain to send emails as weginger-photography.at”
   That was the key: my sender domain was not authenticated.
3. Opened the “Manage sending domain” / authentication popup
   In MailPoet I clicked on “Authenticate” for my domain and saw that no DNS entries were found.
   MailPoet showed the required DNS records:
   • 2× CNAME (mailpoet1._domainkey, mailpoet2._domainkey → dkim1.sendingservice.net, dkim2.sendingservice.net)
   • 1× TXT (_mailpoet with a long verification code)
   • 1× TXT (_dmarc with v=DMARC1; p=none;)
4. Added the DNS records at my hosting provider
   At my DNS host (world4you) I opened the DNS zone for weginger-photography.at and:
   • Added CNAME:
     • mailpoet1._domainkey → dkim1.sendingservice.net
     • mailpoet2._domainkey → dkim2.sendingservice.net
   • Added TXT:
     • _mailpoet → the exact verification string from MailPoet
   • I already had a _dmarc TXT record with v=DMARC1; p=none;, so I left that as it was.
5. Verified DNS in MailPoet
   After saving the DNS entries and waiting a few minutes, I went back to the sender domain / authentication popup in MailPoet and clicked “Verify DNS records” until all entries turned green and the domain was marked as authenticated.
   The red “Authenticate the domain…” warning in the editor disappeared.
6. Tested sending again
   Then I created a simple test newsletter and clicked “Send”:
   • The email was correctly added to the sending queue in System Status.
   • The test newsletter was delivered to my inbox.
   • Manually created newsletters now send normally again.

So in my case the root cause was an unauthenticated sender domain when using the MailPoet Sending Service.
Once I added the required DNS records and authenticated the domain, the “Send” button started working properly and newsletters were actually queued and sent.

Thanks for your support!!