Missy a11n

Hello! I’m not completely clear on what you’re asking. Can you please describe your inquiry a bit more?

Thank you for the URL! It looks like our team emailed you on Jan 24 with some follow up questions. Did you receive that?

You can submit a follow-up ticket here or respond to our email from January. Thanks!

Hi there,

Thank you for reaching out to Woo Support!

This is a known issue and should be resolved by updating to version 4.43.0 which was released earlier this week.

Please do let us know if you have already updated to version 4.43.0, however, and we’ll be happy to investigate further. Cheers! 👋🌟

Hi there! You can use your own domain by setting up DKIM and DMARC on your sending account. Here’s our documentation on what it is and how to set it up: https://kb.mailpoet.com/article/295-spf-dkim-dmarc

Hi there! Could you please share the URL of the site you’re attempting to send through?

Hi there!

It looks like your Post Notification emails were affected by a known issue with MailPoet. Versions 1.41.x and 1.42.x were affected by this issue, where some Post Notification emails would become “stuck” in sending mode, unable to complete the sending of the last few emails on your list.

This issue has now been resolved in version 1.43.0 of the plugin. Please upgrade your plugin to this version as soon as possible.

That said, if you have any remaining Post Notification emails stuck in sending status, these will need to be cleared to allow new Post Notification emails to go out. You will need to locate any stuck emails under MailPoet > Emails and hover over them to reveal the pop-out menu, then use that menu to “Move to Trash”.

Once all stuck emails are trashed, future Post Notifications should go out without becoming stuck in the queue.

Hi @mubiesam –

It looks like you need to run an update on the Gutenberg: by Gutenberg Team – 9.9.1 plugin. I would recommend backing up your entire site and database and running any available updates to WordPress and all plugins.

If that does not resolve the error, another of your plugins or your theme may be conflicting with WooCommerce. You can read more about plugin and theme conflicts in our Self-Service Guide.

Here’s how you can figure out which one may be causing the problem:

Before you start

• First, please make sure you have a good backup in place of your full site and database. Most hosting companies have this included in the subscription, but you could also consider using a service like Jetpack. If something goes wrong, it’s nice to know that you can restore your site.
• Second, I would suggest to install a plugin called Health Check & Troubleshooting. This is a plugin developed by the WordPress community and it allows you to disable plugins without effecting your current site visitors.

How to test for conflicts
In order to test for conflicts using Health Check & Troubleshooting:

1. Go to Tools > Site Health > Troubleshooting.
2. Select Enable Troubleshooting Mode. This will disable all your plugins and set your theme to a default one.
3. Go to Plugins. There you can enable WooCommerce by selecting Enable While Troubleshooting.
4. Try to reproduce the problem. If the problem is resolved, it’s clearly a conflict. Now we need to figure out which plugin is causing this conflict.
5. If you can’t reproduce the problem with only WooCommerce enabled, go ahead and re-enable the other plugins one by one. Test after each one until the problem occurs again – this will tell you which plugin is conflicting.
6. If you are unable to reproduce the problem with the rest of your plugins enabled it could be your theme causing the conflict. To test for this, please enable your original theme at your WordPress Dashboard in the Troubleshooting Mode section at the top (it will look similar to this: https://d.pr/i/bbvkLY). In the Troubleshooting window, you’ll be able to see a dropdown with available themes. Choose the one you normally use. Try reproducing the problem you’re experiencing. If you can reproduce it, your theme is the source of the conflict.

Once you’ve done that, please check out How to test for plugin and theme conflicts and follow the steps there. Please let us know how that goes.`

Hi @patriziagarciaa –

Apologies for the delayed response!

It’s pretty common for emails to get rejected by email providers when the email is generated by _localhost_, which is what WordPress does by default. To remedy this issue, you’ll need to set up an SMTP email plugin to send mail for you. The free plugin WP SMTP is a good option for that.

If that doesn’t help resolve the issue, pease have a look at our Email FAQ page here for some of the most common reasons why emails do not send and how to correct them. You can also reach back out to us for assistance, of course. 🙂