Pesky Message | MailPoet 3 (New)

Hey @generosus,

Thank you for getting in touch with us and we apologize for the confusion.

To answer your question directly, the main conflict between MailPoet 3 and WP Mail SMTP is that MailPoet has its own email sending system, which prevents WP Mail SMTP from sending emails.

This conflict has caused issues and quite a bit of confusion when users intended on sending emails using WP Mail SMTP.

Based on your usage, you don’t seem to be using MailPoet 3 in a conflicting way, so you can remove that particular notice by using the below code snippet.

add_filter( 'wp_mail_smtp_conflicts_is_conflicting_plugin', function ( $conflict, $plugin ) {

 return isset( $plugin['slug'] ) && $plugin['slug'] === 'mailpoet/mailpoet.php' ? false : $conflict;
}, 10, 2 );

In case it helps, here’s a tutorial with the most common ways to add custom code like this: https://www.wpbeginner.com/beginners-guide/beginners-guide-to-pasting-snippets-from-the-web-into-wordpress/.

For the most beginner-friendly option in the guide above, I’d recommend using the Code Snippets plugin: https://www.wpbeginner.com/plugins/how-to-easily-add-custom-code-in-wordpress-without-breaking-your-site/. This will protect your code from updates and keep it easy to manage right within your WordPress admin area.

I hope this helps! Could you please let me know if I can clarify any of the information above or provide you with more details?

Thank you! ??

Hi @dakeg,

Impressive. Thank you for the quick reply, info, and code snippet.

To assist you and others, MailPoet 3 (New) offers two options to send emails and none conflict with your plugin.

When using the MailPoet 3 (New) email sending service, the only thing that users need to do is leave blank the “Reply-to” field. This setting still allows you to use the “Force from Email” setting provided by WP Mail SMTP.

Details: https://prnt.sc/NyZZoelhulC9 and https://prnt.sc/LbWP24kDY7kC

Result: As the sender’s email address, we are using [email protected] with WP Mail SMTP, and [email protected] with MailPoet 3 (New). They both work great.

So, in short, instead of the pesky message added via your plugin, perhaps you guys can work out a solution with the developers of MailPoet (code adjustments) and/or update your knowledge base accordingly.

MailPoet 3 (New) is an excellent plugin and used by over 500K customers, so rest assured, they are not going to deactivate it because of your plugin.

The pesky message — in our view — is unacceptable.

If something was missed, please us know ??

Thank you.

Hey @generosus,

Thank you for understanding, sharing your feedback, and for that handy tip about MailPoet 3.

I’ll share this with the rest of our team and consider how best to move forward from here ??

Hey @generosus,

Appreciate the feedback and the insights – it was very helpful!

The gist of things is that this change was well-intentioned, but we missed the mark a bit.

With the popularity of both plugins, our support team is regularly helping users that are confused or in a bind when using both solutions.

So we know it’s a valid (and growing) concern since we see it firsthand, frequently.

This notice was added as we try to mitigate/help with that.

That said, as you outlined, both plugins can in fact work together with no issues when configured correctly.

So we’ll be releasing a minor update soon that removes this notice.

In the future, we’ll introduce another notice that is more surgical, meaning it only will show if we see that configurations are set in such a way that is likely causing conflict. This notice will be specific to the problem and link to a detailed doc we’ll create that explains the problem with clear steps to address them ??

This way we’re still addressing the problem, but more accurately.

Thanks again for your detailed and honest feedback, it really helped bring this to our attention and plan the next steps.

Jared

Hey @jaredatch,

Wow! Excellent update and response time. One of many reasons why we use your plugin.

We downloaded and activated your latest plugin version, V3.5.1, and deleted the code snippet provided by your team. Everything is now working perfectly (both plugins).

Again, thank you.