Post notification emails no longer being sent

Hi there @noise,

Thanks for sharing that entry from the log file. However, this is an INFO message, which basically confirms that the post notification email was successfully triggered; it is not an error message. So this is good news – at least MailPoet is catching that a new post was made and is attempting to send the Post Notification message.

Can you share with us:

• the affected site’s System Info – this is under MailPoet > Help on the “system info” tab, just copy and paste it
• screenshots of MailPoet > Help on the “system status” tab -> this is very long so it might take a few screenshots to get it all in
• a screenshot of MailPoet > Emails on the “Post Notification” tab -> in particular, click the “view history” button next to your post notification email and grab what it shows there

Please do blur out any sensitive data about your site before sharing.

Thank you!

Thanks

System Info

name: --------
email: -------------
PHP version: 8.3.16
MailPoet Free version: 5.6.3
MailPoet Premium version: N/A
MailPoet Premium/MSS key: 58d023031a11c7cc**
WordPress version: 6.7.1
Database version: 8.0.41
Web server: Apache
Server OS: Linux server.foobar.com 5.14.0-503.21.1.el9_5.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jan 12 09:45:05 EST 2025 x86_64
WP info: WP_MEMORY_LIMIT: 256M - WP_MAX_MEMORY_LIMIT: 512M - WP_DEBUG: - WordPress language: en_US - WordPress timezone: America/St_Johns
PHP info: PHP max_execution_time: 600 - PHP memory_limit: 512M - PHP upload_max_filesize: 128M - PHP post_max_size: 128M
Multisite environment?: No
Current Theme: Tracklister (version 1.0.0)
Active Plugin names: Divi-Blog-Extras/divi-blog-extras.php, advanced-custom-fields-pro/acf.php, classic-editor/classic-editor.php, classic-widgets/classic-widgets.php, custom-post-type-ui/custom-post-type-ui.php, disable-gutenberg/disable-gutenberg.php, divi-machine/divi-machine.php, email-encoder-bundle/email-encoder-bundle.php, indexnow/indexnow-url-submission.php, jetpack/jetpack.php, mailpoet/mailpoet.php, ninja-forms-style/ninja-forms-style.php, ninja-forms-uploads/file-uploads.php, ninja-forms/ninja-forms.php, ns-category-widget/ns-category-widget.php, regenerate-thumbnails/regenerate-thumbnails.php, w3-total-cache/w3-total-cache.php, webp-converter-for-media/webp-converter-for-media.php, wordfence/wordfence.php, wordpress-seo/wp-seo.php, wp-widget-disable/wp-widget-disable.php, wps-hide-login/wps-hide-login.php
Sending Method: PHPMail
MailPoet Sending Service: Is reachable: Yes - Ping response: 200 HTTP status code - API key state: valid - Premium key state: valid_underprivileged
Sending Frequency: 80 emails every 15 minutes
MailPoet sending info: Send all site's emails with: default WordPress sending method - Task Scheduler method: Action Scheduler - Default FROM address: [email protected] - Default Reply-To address: [email protected] - Bounce Email Address: [email protected]
MailPoet Cron / Action Scheduler: Status: active - Is reachable: Yes - Ping URL: https://canadaslotcarracing.ca?mailpoet_router&endpoint=cron_daemon&action=ping - Ping response: pong - Last run start: 2025-01-30 12:44:54 - Last run end: 2025-01-30 12:44:54 - Last seen error: None
Total number of subscribers: 14
Plugin installed at: 2024-10-08 14:26:51
Installed via WooCommerce onboarding wizard: false
Sending queue status: Status: Unknown - Started at: 2025-01-28 20:38:09 - Emails sent: 0 - Retry attempts: 0 - Last seen error: None
Data inconsistency status: Orphaned sending tasks: 0 - Orphaned sending task subscribers: 0 - Sending queue without newsletter: 0 - Orphaned subscriptions: 0 - Orphaned links: 0 - Orphaned newsletter posts: 0

Hi there @noise,

Thanks for sharing this information, it was very helpful.

Looking this over, I’m not seeing any errors with actual sending. It looks like the Post Notification last sent out a notification on January 14, and it ran through successfully.

I had a look at your website but it looks like the posts there are not dated, so I couldn’t tell if there had been a more recent blog post than January 14. If there was a more recently one than that date, it didn’t fire the Post Notification at all.

Potential reasons could be:

• if you are copying older posts to repurpose them, or editing the content of older posts and changing the date on them, this will NOT re-trigger the post notification email. It only works with freshly created posts from scratch using the Post > Add New interface.
• if the post notification email has some conditions on it -> for example, tied to specific categories or tags -> this might cause it not to fire if new posts don’t meet that criteria
• DIVI post builder -> it appears your site is using the DIVI builder to create blog posts; this should work but could be a potential source of conflict. You could test this by making sure to create your next blog post using Posts > Add New and creating it using the Gutenberg editor to verify the issue is not DIVI related.

I also had a look at your MailPoet account and I see that your domain name **is not verified.** This can definitely cause issues with your sending, and cause your subscribers to not receive your messages as they will be marked by email readers as spam.

To resolve this, you will need to add four specific fieldname/value pairs to your domain name DNS settings. This is usually done via your website hosting account, and you can ask your website host for assistance if you run into trouble. Please give it a try using the instructions here:
https://kb.mailpoet.com/article/295-spf-dkim-dmarc

Hi

It was working fine before, so the not sending is a recent thing – there has been no changes to the server. The other site is identical but IS sending post notification emails.

We are using the webiste’s email server which was working fine, no mailpoets mail server.

THere has been two posts since the 14 which have not sent.

As I said it has been working fine for all those other emails so not sure why its not working now.

Hi there @noise,

Can you confirm that:

• the two posts since January 14 were brand new posts, created via Posts > Add New, and were not re-purposed older posts or copied content from older posts?
• the two posts since January 14 were created using the Gutenberg editor, and not DIVI?

In addition, can you share a screenshot of your Post Notification email’s Automatic Latest Content block, showing the criteria and settings in the right hand column?

Lastly, my note about validating your domain may not seem like the root cause here, but in general it is good practice and will go far towards protecting your online reputation. While it may not be directly related to this issue, to avoid future issues we strongly recommend validating your domain as soon as possible.

Hi.

Not sure if this is a language issue? Apologies if so.

1. Mailpoet worked fine before the latest update. It sent all the emails that were divi based (actually CPTs). You can see that in the records. Using the servers email servers
2. MailPoint on THE EXACT same site (theme, database, literally on the same account on the same server) which started at the same time, with the same plugins has been working constantly all along.
3. The mailserver passes all test for local email setting with the proper dkim settings as tested at MXToolbox. As we’re using our own email server, adding anything related to other servers that are not related to our IT backbone dosent make any sense,

Let me know if this isn’t clear.

Hello again @noise ,

Thank you for your patience as we continue troubleshooting this issue. I completely understand your frustration, especially since everything was working fine before the latest update, and I appreciate the details you’ve provided so far.

Could you please head over to Tools > Scheduled Actions in your WordPress dashboard and check the Failed section? Specifically, look for the “mailpoet/cron/daemon-trigger” action and let us know:

• Has it been failing?
• Or is it triggering as expected?

Possible Causes & Solutions:

Since we don’t see a clear error message in the logs, it’s possible that something went wrong during the update. Here are a couple of options to resolve this:

– Rollback to the Previous Version of MailPoet

• Use the WP Rollback plugin to revert to an earlier version:
  ?? WP Rollback Plugin
• OR manually download the previous version here:
  ?? Download Older Versions (Scroll down to the Advanced Options section)
• Then install it via FTP using this guide:
  ?? Reinstalling MailPoet via FTP

– Reinstall MailPoet
If rolling back isn’t ideal, you can reinstall the MailPoet plugin to ensure all files are correctly set up:
?? How to Reinstall MailPoet

Important Note:

These steps won’t erase any data from MailPoet, but just to be safe, I highly recommend backing up your database before proceeding.

Let me know what you find in the Scheduled Actions log, and if the rollback or reinstall helps! I appreciate your patience, and I’m happy to assist further if needed.

Thanks, I managed to get it working, although not quite sure how.

Hi there @noise,

Good to hear it is working again, although it is frustrating not to know what happened! But at least we can move forward from here.

If you do figure out the source of the issue, please do share here for the benefit of our community.

In the meantime, happy mailing!